Fixing “Classic Shell needs to configure itself for the new operating system”

If you use Classic Shell (Windows 8/10 Start menu replacement) every time you upgrade Windows your users will get hit with the message “Classic Shell needs to configure itself for the new operating system”.   If you are not an administrator on the machine, you will be prompted to enter an admin name and password in order to make the necessary changes.  If you are like me you hopefully have your users restricted to protect them from the internet and themselves.  If you do, then they will get this message over and over again until an administrator signs on and fixes the issue.

I have an easier way that I have used for some time now with Classic Shell.  Run this however you want. If you use SCCM you can run this after Windows has upgraded in your Task Sequence or as a separate Task Sequence that runs after an upgrade. If you are on a domain, you can just push out the registry key with the correct value and ONLY apply the GPO to the correct version of Windows 10. Each version will have a different value. This must be ran as an admin or as system for it to make the needed registry changes.


About The Author

I have worked in the computer repair field since the early 90's. I was a technician and then Coordinator of Computer Repair for Regional Education Service Agency II (RESA 2) for 18 years. I am currently working for Wayne County Schools as a Network Engineer/Technology Specialist. I am responsible for the schools Internet access, Wi-Fi, networks, servers, laptops, desktops, and their operating systems and software.

Related posts


  1. Martin Feuerstein

    I found this blogpost after preparation of Win 10 Upgrade in a domain environment – but we are using Classic Shell’s successor Open-Shell, so the script needs some modification
    – in line 45 the reg key has to be replaced by: “HKEY_LOCAL_MACHINE\SOFTWARE\OpenShell\OpenShell”
    – the value calculated in the script is too high by one compared to the official way of upgrading Open-Shell, so add “-1” at the end of line 42
    – the official method to upgrade is “%programfiles%\Open-Shell\StartMenu.exe” -upgrade (optional parameter: -silent)
    – the official method replaces line 56 to 63, according you don’t need to check the OS architecture and can leave out line 23 to 27 and replace the filename in line 22 with the path to StartMenu.exe.

    Mixed your solution with https github com /Open-Shell/Open-Shell-Menu/issues/167

  2. Mark Scarberry

    Thanks Martin for the info. The Winversion numbers listed in the script matched what was in the registry for each version of windows up to the time of the post after installing the program. I’m not sure why it would be off by one now when it wasn’t then.
    I have since just used the following command to fix the issue.
    You can run this as a step in a task sequence if you are using Microsoft SCCM or just run it via a GPO after an upgrade.

    cmd.exe /c “%ProgramFiles%\Open-Shell\StartMenu.exe” -upgrade -silent


Leave a Reply to Mark Scarberry Cancel Reply

Your email address will not be published. Required fields are marked *

seventy nine + = 82