CODEWITHSUNDEEP
windowsbatch-fileexplorertaskkill
mythofechelon
mythofechelon

Reputation: 3782

Restarting explorer.exe only opens an explorer window

The Problem

In one part of a batch file (kind of, see Extra Information) I need to restart Explorer, so I use the, tried-and-tested method of

taskkill /f /im explorer.exe >nul
explorer.exe

Then this happens

  1. explorer.exe is successfully terminated
  2. explorer.exe is started (see Image 2), but only an Explorer window opens, which I am left with indefinitely (see Image 1)

I can then only properly restart Explorer by starting a new task from Task Manager, as, I'm assuming, Win + R is part of Explorer.

Extra Information

Now, I say "kind of" as I'm running the batch file from a self-executing SFX archive, created with WinRAR. So, when executed, the contents of the archive are extracted to %temp% and a user-defined file (usually a boot-strapper and, in this case, my batch file) is run upon successful extraction.

So far, I've deduced

  1. explorer.exe definitely is being fully killed.
  2. The batch file definitely is called and executed correctly, as it runs and everything else in the script works as designed, except for the line that starts explorer.exe
  3. The command to restart Explorer isn't "badly timed", or anything, as I've tried delaying it.
  4. The batch file works perfectly when manually extracted from the archive, so it's not a problem with the compression or extraction processes.
  5. Even with commands like start explorer.exe | cmd.exe Explorer doesn't restart properly, so it's definitely not a problem with the .bat file.

I can confirm that it works on Windows XP and Windows 7 x86 but not Windows 7 x64 (which is my system).

Status

At the moment, I'm suspicious of WinRAR, as I've proved that the code itself works. So, I'm creating the self-executing SFX with different versions of WinRAR. So far, I've tried versions:

and had the same results every time.

I submitted a bug report to [email protected] yesterday and got a reply from Eugene Roshal himself this morning

Hello, SFX module uses ShellExecuteEx to start a setup application. Normally it works well. I do not know why Explorer decides to switch to windowed mode. Now I built a small standalone program

#include <windows.h>    
void main()
{
  SHELLEXECUTEINFO si;
  memset(&si,0,sizeof(si));
  si.cbSize=sizeof(si);
  si.lpFile="test.bat";
  si.nShow=SW_SHOWNORMAL;
  ShellExecuteEx(&si);
}

which runs test.bat with contents as in your sample. This program shows exactly the same behavior as WinRAR SFX, so Explorer is started in window.

and a second email this morning

Sorry, no advice now. I replaced ShellExecuteEx with CreateProcess

#include <windows.h>
void main()
{
  STARTUPINFO si;
  PROCESS_INFORMATION pi;
  memset(&si,0,sizeof(si));
  si.cb=sizeof(si);
  CreateProcess(NULL,"test.bat",NULL,NULL,TRUE,0,NULL,NULL,&si,&pi);
}

but result is the same. I tried to use other SW_ flags like SW_SHOWDEFAULT or SW_RESTORE with ShellExecuteEx also as "open" and "explore" lpVerb, but it does not help. For now I do not understand the logic behind this windowed versus desktop mode.

I realise the outlook is grim but, I hope that's of help to someone..

Proof / Evidence

Link to an SFX archive demonstrating this, if anyone wants it: https://dl.dropbox.com/u/27573003/Social%20Distribution/restart-explorer.exe

image 1

image 2

You may notice here that I'm running the commands inside a VM (as denoted by VMwareTray.exe) but it is not a VM-caused conflict. I've tested the exact same files on my own host system (which is the same OS) and have had the same results.

Update

I'm experiencing similar "works outside of an SFX archive but not from one" problems when using REG ADD in a completely different project. I just don't think SFX archives play nice with batch files.

Upvotes: 24

Views: 34390

Answers (15)

book777
book777

Reputation: 13

To see the start panel you need to execute the explorer.exe from the system32 folder

taskkill /im explorer.exe /f

cd %WINDIR%\system32
start %WINDIR%\explorer.exe

Upvotes: 0

sparrowt
sparrowt

Reputation: 2968

I had this same problem and found that all the solutions here still didn't work from a batch script.

None of these worked completely:

start explorer.exe
start explorer
explorer.exe
explorer

because they all either opened a window (and didn't show the taskbar again), or the batch script then hung thereafter and couldn't execute any more commands

I found that this line in the batch file did work (after killing explorer.exe):

start "" "%windir%\explorer.exe"

and also allowed other commands to be executed after it in the script

Upvotes: 10

Arnoud Mulder
Arnoud Mulder

Reputation: 179

When you run explorer.exe from an 32-bit application in 64-bit windows, the path will be redirected to the SysWOW64 directory which contains the 32-bit explorer.exe.

In XP64 it wasn't not such a big deal. In the taskmanager you can see the 32-bit explorer.exe running but it did start as the shell. In Windows 10 (as I came to this problem, it looks like it is introduced in Windows 7), the 32-bit explorer.exe is a stub which creates a new instance of the 64-bit explorer.exe. It probably passes a path on the commandline here so the 64-bit explorer.exe opens a window instead of starting the shell.

So it is still like before that you can control whether a window or a shell should be started by starting explorer.exe with or without a path as commandline parameter.

Instead, you should force starting the 64-bit explorer.exe from the 32-bit application and all is ok. To do this, one method is using the sysnative directory as mentioned above. But another method is to use Wow64DisableWow64FsRedirection/Wow64RevertWow64FsRedirection.

I did the latter and can confirm it works nicely. For both CreateProcess and ShellExecuteEx API.

Upvotes: 2

Matt
Matt

Reputation: 81

For restarting explorer.exe, this worked for me.

powershell.exe Stop-Process -processname explorer

Upvotes: 3

kenner116
kenner116

Reputation: 1

Try adding a explorer.exe key to App Paths in the registry.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\explorer.exe

(Default) C:\Windows\explorer.exe

Path C:\Windows

or copy the following to notepad and save it as a .reg file then run it:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\explorer.exe] @="C:\Windows\explorer.exe" "Path"="C:\Windows"

Upvotes: 0

Mike Hadden
Mike Hadden

Reputation: 1

What worked for me in Windows 7 64 bit was "C:\Windows\expstart.exe" or just expstart.exe

Upvotes: 0

user4839775
user4839775

Reputation:

Use this (.bat with administrative privileges) in x64 or x86

tasklist /fi "imagename eq explorer*" | find /i "explorer*"
if not errorlevel 1 (taskkill /f /im "explorer*") else (
start %windir%\explorer.exe

Upvotes: 0

Paweł Liszka
Paweł Liszka

Reputation: 330

Have same issue with Visual Studio.

What works for me (Win 7 Pro 64bit):

PPM on Project name select "Properties"

Configuration Properties > Build Events > Pre-Build Event

taskkill /im explorer.exe /f

Configuration Properties > Build Events > Post-Build Event

start "" "C:\Windows\explorer.exe"

But this make other problem (the IDE is frozen after the explorer runs) and now I'm only able to restart the IDE to run build command again...

Upvotes: 0

Alex
Alex

Reputation: 1

Easy Context Menu

Just right-click on the desktop and choose Restart Windows Explorer. Enjoy!

Screenshot of the configuration

Upvotes: -6

panda-34
panda-34

Reputation: 4209

Try

%windir%\explorer.exe
start %windir%\explorer.exe
start /d%windir% explorer.exe

Upvotes: 1

Doug Benham
Doug Benham

Reputation: 13

I think user1631170 is on to something, "I wonder if some part of Win-RAR is running in 32-bit mode? Could you even start explorer64 running from a 32-bit process? I am pretty certain that Windows won't do that."

When I start explorer.exe from ProcessHacker (32-bit process manager), I get an explorer window.

But I can force it to start the 64-bit explorer with this:

%systemroot%\sysnative\cmd.exe /c start /B explorer.exe

sysnative is a keyword that Windows recognizes to bypass the file system redirection for 32-bit/64-bit (http://msdn.microsoft.com/en-us/library/windows/desktop/aa384187(v=vs.85).aspx Enjoy!

Upvotes: 16

Zombo
Zombo

Reputation: 1

I do not understand why, but it will only for me if using the full path, regardless of your PATH variable.

%windir%\explorer

Upvotes: 0

mythofechelon
mythofechelon

Reputation: 3782

The other day, I was having a look through some of WinRAR's more advanced options and came across this tab:

enter image description here

As soon as I saw that I suspected it to be part of the problem and solution, as this issue only ever occurs on Windows 7 x64.

As suspected, using the Default64.SFX module instead of the default Default.SFX module entirely fixed the issue. Finally.

Upvotes: 0

Bali C
Bali C

Reputation: 31251

I have seen similar problems before doing this in C#. The process had to be invoked by calling explorer shell rather than explorer window, but I haven't had any problems in batch.

Try using this:

taskkill /im explorer.exe /f
explorer

The difference between the other answers being explorer rather than explorer.exe which has caused problems before for me.

This works on my Win7 x64 PC.

Hope this helps!

Upvotes: 0

Jacob Seleznev
Jacob Seleznev

Reputation: 8141

This works in Windows 7:

taskkill /f /IM explorer.exe
start explorer.exe
exit

Upvotes: 7

Related Questions