Classic Shell: Forum

Overnight, without my knowledge or consent W10 did an update (seems like a major one) and disabled CS saying it was not compatible. Now, I cannot re-install 4.3.0. When running the installation program an error pops up "CS requires Windows 7 or later".
Any ideas how to solve this?

Many thanks

Download the Utility from: http://www.mediafire.com/download/3uker ... tility.exe and remove Classic Shell (you can choose to keep your settings). Then reinstall the latest version from http://www.classicshell.net.

_________________
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.

Removed ok, but still same error when trying to install.

Download the installer again. Also check the Compatibility tab in the EXE properties and see if there is some compatibility setting to run as another version if Windows.

Also, what is your edition of Windows 10? Home, Pro, Enterprise or Education? And what build? (You can check the build by running winver.exe).

_________________
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.

Hi, thanks for your replies.

I've tried downloading the installer again and it is still the same error.
I have W10 Home.

Am I the only one having this issue?

Download the Classic Shell Utility from here: http://www.classicshell.net/downloads/
Run it, save a log file, and send it to me.

Here is the log from the CS utility

Everything checks out. I don't know why the installer would think you are running on older version than Windows 7.
Use the compatibility tab to tell it you are on Windows 8 or something.

Same thing happened to me when the latest W10 update installed this morning. There was a message saying that Classic Shell had been disabled because it was not compatible with the latest W10 update. Now I am going nuts trying to get to important stuff. Literally, in order to find my Documents folder, I finally had to scroll down that whole left bar of icons for stuff I don't want, don't need and will never use, click on Windows System, and select My PC to at last find my Documents folder and my Pictures folder. And I had to do a web search just to find out how to do a restart. I'll try the suggestion here, but in the meantime I hope Classic Shell developers are working hard on a new version that will work with this newest W10 mishmash.

UPDATE: I used the uninstall tool to uninstall Classic Shell, then installed the newest version.....and it worked!!! What a relief. /me huggles all the hardworking Classic Shell developers. And the OP on this thread too.

@dionaea - are you saying that you too are getting an error that "Classic Shell requires Windows 7 or later"?

No, the message I got was when the newest W10 update finished installing. It said Classic Shell was disabled because it was incompatible with the newest update. I had the previous version of Classic Shell, so by installing your newest update of Classic Shell, it's working again.

This is the same for me also. After the latest Windows 10 update finishes, it posts a message that the program Classic Shell is not compatible with this version of Windows (similar verbiage) and has been removed. Classic Shell has been removed. After reinstalling the same version that was on there before (4.3.0) it is working correctly. This is likely just plain and blatant illegal monopoly tactics that Microsoft gets away with all of the time, especially given that when Windows 10 preview initially came out it disabled Classic Shell from installing by its installer filename and not by its characteristics, something that blatantly and carelessly indicated its intentions (you could change the installer name and it would work).

Just to update you that I'm still unable to re-install CS. The installer still believes the OS is <W7.
Any chance to let me know what exactly the installer is checking when deciding what OS it is on?

Thanks

Just looked at the log file that I sent you and noticed a line
"Windows version (reported): 6.02"
followed by
Windows version (registry): Windows 10 Home 6.3
Is it at all possible that the installer is using the reported OS version instead of the one in the registry?

OK, I feel silly for not recognizing this earlier: I'm so used to using the Total Commander file manager that I actually never use Windows Explorer. BUT, it turned out that when TC runs another program (like CS installer) it does substitute the OS version with whatever it thinks is right.
Running the CS installer from Windows Explorer worked fine and I'm happy that CS is up and running again on my laptop.
Thanks, and apologies for this confusion.

@DrVolodya, you could report this behavior to the developer of Total Commander so he can fix it.

_________________
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.