Classic Shell: Forum

Is there any reason why the Classic Shell automatically loads the Libraries at bootup?

Classic Shell does not automatically load Libraries at bootup. Unless you mean something else by "Libraries" and "bootup".

I'm sorry, but if I do not run Classic Shell, Windows 8 boots normally. As soon as I reactivate Classic Shell, the Libraries folder appears on the screen desktop. I check the processes and sure enough, Windows Explorer is running.

Sounds like a bug (one i haven't heard of); are you running anything else that might affect this behavior?, which version of classic shell are you running (if your running beta try the stable, and if your running the stable try the beta.

I still don't get it. What do you mean "Libraries folder appears on the screen desktop"? And of course the Explorer process is running. I always runs. It is the process that provides the desktop and the taskbar.

Running Version 3.6.6. Tried dropping everything from the Start Menu . . . didn't help.

There are two instances of Explorer.exe running. The first one gives me the desktop. The second one is the problem. I can't delete it, change the properties (grayed out), or even rename it. If I kill this second process, the Libraries folder disappears from the desktop (full view showing all the folders).

William

I see. So you are saying that when you log in you automatically get a Windows Explorer window opened on Libraries.
This probably means you have it started automatically either from the Startup folder, from a scheduler task, or something like that.
Very early attempts by people to skip the Metro screen involved running Explorer like that and some tutorials on the net still recommend it. For t he record, Classic Shell has never used that method. So look at the startup folder or the scheduler or the Run registry key to see if Explorer is started from there.

Rebooted, rechecked Start Menu, Process Explorer, Task Scheduler. Of course, the second Explorer is active in the Start Menu with instructions to open Library. Process Explorer shows both Explorers running. FYI: PID for the first (correct Explorer) is 1380; the second has a PID of 3650.

Checked the Run and Run Once with Regedit --- all four locations were clean.

William

Here is the command line for the second instance of Explorer:

C:\WINDOWS\explorer.exe /factory,{ceff45ee-c862-41de-aee2-a022c81eda92} -Embedding

As I mentioned earlier, I cannot find a way of editing or deleting this.

William

Few things to try:
Search the registry for that command line, or at least that GUID part. Also search for "explorer.exe". Maybe you'll get lucky
See in Process Explorer which process is the parent of the second Explorer
Disable the Classic Shell service. If you suspect Classic Shell is the cause, this will confirm it
If you determine that the Classic Shell service is at fault, I'd recommend you upgrade to the latest beta version 3.9.3. It doesn't use a service

Try to use Sysinternals' excellent Autoruns tool to determine what is opening the 2nd unwanted folder at startup. It is much more comprehensive than Task Manager and shows all locations from where programs are loaded at startup.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

Spent the better part of yesterday evening trying all the suggestions -- nothing works. Still get two versions of Exploer opening and I cannot delete or access the second unwanted instance. Regeit will not allow any changes to the specific entry; therefore, the second Exploer opens with /factory xxxxxx /embidding.

William

Wait, are you saying that you found this in the registry but you can't edit the registry entry? What is the key/value that you found?

Here's the exact command in Regedit that loads the unwanted Explorer and Libaries:


C:\WINDOWS\explorer.exe /factory,{ceff45ee-c862-41de-aee2-a022c81eda92} –Embedding
Also did uncheck "Multiple copies of Exploerer" -- didn't help.

William

yeah, that's the command, but where is it in the registry? What is the full path to the key and what is the value name?

“C:\WINDOWS\explorer.exe /factory,{ceff45ee-c862-41de-aee2-a022c81eda92} –Embedding” is in HCL/RunMRU/b/REG_SZ/[command line] and HLM/RunMRU/b/REG_SZ/[command line].

So did you try going to Control Panel -> Folder Options -> View tab and uncheck the option: "Restore previous folder windows at logon" if it is checked? Then try restarting and see if Explorer opens again.

_________________
Links to some general topics:

● Compare Start Menus

● Read the Search box usage guide.

I am a Windows enthusiast and helped a little with Classic Shell's testing and usability/UX feedback.

Looks like you have abbreviated something. There is no such thing as HCL. Also the path seems incomplete.
Either way, RunMRU and REG_SZ are not keys that Classic Shell deals with at all.
You may try taking ownership of the key and then delete it (or at least rename it).

HCL - HKEY_LOCAL_MACHINE --- It was a typo on my part -- sorry.

Well, if HCL is HKEY_LOCAL_MACHINE, then what is HLM? Either way, I've never seen a key "RunMRU" directly under any of the root keys. Also I've never seen a key REG_SZ. This is a value type, not a key name. It appears something is gone wrong on your machine.