Tweak will make Your seven easier ;)

marco said:

See this thread: explorer.exe

It seems that using this tweak causes each explorer window you open to start a new explorer.exe thread (regardless of the "Launch folder windows in a separate process" setting under Folder Options/View tab). In the experience of more than just myself some of those duplicate threads don't get released properly. When using this tweak I would find a whole window full of left over explorer.exe tasks using up memory after a few days.

Not happening on my install of the RTM. I do recall a similar affect in a much earlier build.

Maybe there's some other factor involved too then. I'm using RTM as well. As soon as I remove the shortcut parameters the behavior goes away.

marco said:

Maybe there's some other factor involved too then. I'm using RTM as well. As soon as I remove the shortcut parameters the behavior goes away.

I stand corrected. My earlier post was wrong. I was looking at a sorted task list.

Thanks - I needed a problem to investigate.

brb

Actually, the post here is not valid and does cause the error reported by marco.

The correct string is
%windir%\explorer.exe /n,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

As always, the Shark is on the ball.

Airbot said:

Ah, didn't read the whole thing. The tutorial has both %windir% and %systemroot%, the latter posted by Limneos a few posts down the tutorial. I do not use the tweak, if Antman says the %windir% string works properly, and not the %systemroot%, then perhaps it should be brought to Brinks attention in the tutorial, so the %systemroot% strings can be taken out, or an warning issued about it.

I think it is the addition of [ c, ] that breaks it.

I don't think it is the choice of env vars, but I could be wrong. No research performed other than testing the two strings.

%windir%\explorer.exe /n,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}
%systemroot%\explorer.exe /n, /c, ::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

Shark007 said:

Antman said:

Actually, the post here is not valid and does cause the error reported by marco.

The correct string is
%windir%\explorer.exe /n,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

As always, the Shark is on the ball.

The tweak itself is bad on Windows 7 systems no matter what path you use.

It opens a new explorer.exe process each time you use the shortcut
and does not close that new process when closing the window.

If I use the shortcut once, a single additional instance of Explorer occurs. Subsequent clicks toggle min/max. Closing the window does NOT kill the process. Add'l clicks do indeed create new instances of explorer that behave properly (min/max).

This is odd. I used a similar (maybe the same) tweak in my unactivated wzor RTM 16385. While I did not specifically look for this affect, I am certain I would have noticed multiple explorer instances - since I have the bad habit of closing windows instead of min/maxing.

In my previous install, I had two icons on the TaskBar. One opened computer - and had a separate set of jumplist items from the original (and co-existing icon). I do not know how I did that. Somewhere in this forum, I have posted a screenshot of this setup.

That arrangement did not cause multiple unkillable instances of explorer.

To further complicate matters, I just experienced a non-dying instance of explorer using the default config. THe difference being that I just toggled ON the launch new process via Tools/Folder Options.