Explorer.exe — где находится в Windows 10?
- Описание
- Разбираемся
- Вывод
Приветствую друзья! Данная расскажет где находится пожалуй один из самых главных компонентов операционной системы, без которого пользоваться последней невозможно.
Описание
Explorer.exe — процесс оболочки Windows, программы Проводник, расположен всегда только в директории C:\Windows.
Разбираемся
- Explorer.exe — наверно самый главный компонент, отвечающий за работу пользовательского интерфейса Windows, этот процесс является программой Проводник.
- Без данного процесса невозможно посмотреть содержимое папок, нельзя увидеть файлы, не будет меню Пуск, без него будет только одна заставка. Но запущенными программами при этом можно пользоваться.
- explorer.exe это системный процесс, поэтому запускаться должен только из системной директории: C:\Windows, когда запуск происходит из другого каталога — необходимо срочно проверить ПК на вирусы следующими утилитами: Dr.Web CureIT, AdwCleaner, HitmanPro.
Чтобы узнать где находится explorer.exe — откройте диспетчер задач, активируйте вкладку Подробности, далее найдите explorer.exe, кликните правой кнопкой > выберите пункт открыть расположение:
Должна открыться папка C:\Windows:
What makes explorer.exe unable to start?
I install an update yesterday and now explorer.exe is unable to start. I can still access Task Manager, and from there I can open other programs. However explorer.exe doesn’t start, nor yield any error. Running ms-settings:display yields this error: Other things that doesn’t help:
| Command | What happens |
|---|---|
| sfc /scannow | Windows Resource Protection did not find any integrity violations. |
| bcdedit /set safeboot network | Booting to safemode success, but it still fails to run explorer.exe |
| chkdsk | Windows has scanned the file system and found no problems. |
| Get-ComputerRestorePoint | Nothing returns |
| eventvwr or devmgmt.msc | I don’t know what to look for |
Here are the list of recent updates:
wmic qfe list Caption CSName Description FixComments HotFixID InstallDate InstalledBy InstalledOn Name ServicePackInEffect Status http://support.microsoft.com/?kbid=5029921 OOKERLAPTOP Update KB5029921 NT AUTHORITY\SYSTEM 9/15/2023 https://support.microsoft.com/help/5012170 OOKERLAPTOP Security Update KB5012170 NT AUTHORITY\SYSTEM 12/7/2022 https://support.microsoft.com/help/5030310 OOKERLAPTOP Update KB5030310 NT AUTHORITY\SYSTEM 9/27/2023 OOKERLAPTOP Update KB5028756 NT AUTHORITY\SYSTEM 7/26/2023 OOKERLAPTOP Update KB5030508 NT AUTHORITY\SYSTEM 9/27/2023 According to winver , I’m using Windows 11 Home 22H2 (22621.2361).
Find which explorer.exe is controlling the taskbar?
I tend to leave my computer on for weeks at a time. The only issue I have with this is that the task bar flakes out after a number of days. Usually this takes the form of not rendering icons in the start menu. It can go as far as just not rendering anything in the start menu. Restarting the Explorer process works well to fix this in Windows 10. Rather than manually trying to figure out which one of the explorer.exe tasks is handling the task bar and restarting it, I’d like to write a powershell script that does this. How would I programmatically determine which instance of explorer.exe is currently responsible for the task bar?
asked Feb 17, 2018 at 23:59
16.3k 4 4 gold badges 39 39 silver badges 62 62 bronze badges
3 Answers 3
A slightly more concise alternative to veefu’s helpful answer:
Note: Similarly, no guarantees: The method relies on the .MainWindowTitle property of the taskbar-owning File Explorer instance reflecting the taskbar‘s window title, which happens to be empty, unlike the title of actual File Explorer windows — this appears to be the case on at least Windows 10 and Windows 7 (haven’t tried others):
Get-Process explorer | ? MainWindowTitle -eq '' # returns taskbar-owning Explorer process If other users could be logged on and you must limit the processes inspected to the current user’s, run the following from an elevated console:
Get-Process -IncludeUserName explorer | ? MainWindowTitle -eq '' | ? UserName -eq (whoami) Robust, but more complex approach:
Using Add-Member -MemberDefinition , you can define a helper type and method that finds the handle (HWND) of the process that owns the taskbar window, utilizing a P/Invoke signature to call a Windows API functions; note that you’ll incur an on-demand compilation performance penalty the first time you call this in a session. Tip of the hat to Klaidonis for helping me simplify the code.
# Define a helper type and method for getting a window's handle # (HWND) by its class name and title. $helperType = Add-Type -PassThru -Name "WinApiHelper$PID" -MemberDefinition @' [DllImport("user32.dll", SetLastError=true)] public static extern IntPtr FindWindow(string lpszClass, string lpszWindow); '@ # Locate the explorer.exe process that created the taskbar, # via window class "Shell_TrayHwnd" and an empty title. Get-Process explorer | ? MainWindowHandle -eq ($helperType::FindWindow("Shell_TrayWnd", '')) As for when multiple File Explorer processes may exist (based on trial and error — do tell me if I got things wrong):
- If multiple users are logged on interactively (whether remotely or not), each such user may have one or more Explorer processes running, as described below.
- An interactively logged-on user has at least one Explorer process, which owns the taskbar and the desktop — it may or may not have actual File Explorer windows open; let’s call it the Explorer shell process.
- If File Explorer’s Launch folder windows in a separate process view option is:
- OFF (the default): all windows you create interactively are owned by the Explorer shell process — no new process is created.
- ON: the first window you create interactively spawns one new Explorer process and all subsequently opened windows are then owned by that same new process.
- In other words: If you only ever open File Explorer windows interactively, you either have one ( Launch folder windows in a separate process OFF) or up to two ( Launch folder windows in a separate process ON) Explorer processes.
If you create Explorer windows programmatically, it is a different story — see next point.
- For instance, a command such as explorer /e,c:\ creates a new Explorer process every time.
где находиться файл explorer.exe
брат,я про проводника виндос «explorer.exe а не ie explorer (браузер ) !
Prop Cp.Знаток (334) 6 лет назад
Иди нахрен с виндовс фикс дебил сраный
Похожие вопросы
Ваш браузер устарел
Мы постоянно добавляем новый функционал в основной интерфейс проекта. К сожалению, старые браузеры не в состоянии качественно работать с современными программными продуктами. Для корректной работы используйте последние версии браузеров Chrome, Mozilla Firefox, Opera, Microsoft Edge или установите браузер Atom.