Classic Shell: Forum

Hey folks,

I have quite a few Win 10 machines under administration where the users that are using it do not have Admin rights. When Win 10 1607 updated to 1703 my users got the “Classic shell needs to configure itself for the new OS” dialog but they could not execute it because they didn’t have admin rights. In a test env I found that this will happen again when 1709 lands on these machines.

I found this thread in the forums: http://www.classicshell.net/forum/viewtopic.php?f=7&t=5735

That suggest:
1) In the registry, open HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run, and find the value "Classic Start Menu". Replace the "-autorun" parameter with "-startup". This will stop the upgrading.
2) After the upgrade of Windows, run regsvr32 %windir%\System32\StartMenuHelper64.dll (or StartMenuHelper32.dll for 32-bit Windows)

This works but I am questioning do I need to re-register the StartMenuHelper64.dll still? (This will be tricky to pull off in my environment)

I used the Nirsoft dll registration viewer and noticed that StartMenuHelper64.dll is already registered even after the update to 1703 (which makes sense since if every update causes the system to lose their 3^rd party dll registrations that would be a nightmare!)

So the question is can I get away with simply setting option 1 only from above on my systems? Or is the dll re-registration an absolute requirement? Cause it would be a lot simpler for roll outs where I install Classic Shell and the change the reg key right after and not worry about this.

Thanks in advance!

The helper DLL does more than just update it's COM registration.
It hooks into Explorer in a special way to make it possible for the start menu to launch as soon as you log in, not after 10 seconds (like other auto-start programs).
That registration is lost between Windows updates.