Classic Shell: Forum

Although I have selected the option to start CS on windows startup, this does not happen. I have to launch the setting menu first after which CS works. I am using Win 10. Does anyone have a fix for this annoying problem? Thanks.

Throw a shortcut to the classic shell settings in this folder:
C:\Users\blood\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

Then right click this shortcut, select properties, and add -launch to the end of the text in the target field

This should run classic shell with a bit of a delay (5~10 seconds after startup) but automatically

Thanks for the quick response.
CS still does not load automatically. I wonder if I am using the correct shortcut.
This is what I entered in the shortcut field and placed in the startup folder: "ClassicStartMenu.exe - launch"
Is this correct?

Download the Classic Shell Utility from here: http://www.classicshell.net/downloads
Run it, choose the setting to save a system log, and send that log to me. You can attach it here or drop it into the mediafire drop folder.

The -launch text should be outside the quotes

For me its:
"C:\Program Files\Classic Shell\ClassicExplorerSettings.exe" -launch

i have windows in e drive so and i am not getting C:\Users\blood\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup should i use E:\Users\blood\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup ?

If that is your classic shell install directory...
basically look for this file: ClassicExplorerSettings.exe
and thats the directory you need.

Also if you do as IVO said, he can get to the real root of the issue and fix it proper (so itl startup right away)

I'm having the EXACT same problem right now! I've had to reinstall windows 10 AGAIN because of it's psychotic personality problems. The install before this one my CM worked fine, as it always has. But now, it doesn't start! I've tried EVERYTHING and it won't start automatically. I have to manually start it. I'm thinking W10 is killing it or something, but the install just before this one it was working fine, could they have put an update in there to ignore CM -autorun this quickly? Please, I would really like some help on this. Is CM going to me a manual program from now on or do I just have a buggy install?

Im on a fairly recent build 1709 ver 16299.371 and classic shell works fine. also its unlikely they have or ever will release an 'intentional' patch to break classic shell. Not that they have to, because there are so many ways it happens naturally
When you installed, did you just download the installer and run it on the new copy of windows? or try to copy the folder from your old copy? (probably not, but I thought I'd ask)

I don't know if this is applicable with CS or not, however I'm using it often (thanks to Windows 10... ).
Open regedit (Win+r):
- for 32 bit system, find "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run", add a new value, call it "ClassicShell" and edit the path (empty) with the path to ClassicShell.exe.
- for 64 bit system. find "HKEY_LOCAL_MACHINE\SOFTWARE\Wow64Node\Microsoft\Windows\CurrentVersion\Run" and do the same as above.