Fix 'Windows cannot find C:\ProgramData\Microsoft\Windows\Start Menu\Programs'
You open an app shortcut or Start Menu and get this error. Happens after a bad uninstall or a registry cleaning tool goes rogue. Here's how to fix it.
You click a shortcut in the Start Menu — maybe a game launcher, a PDF reader, or even just the Settings icon — and instead of opening, Windows throws up a box that says "Windows cannot find 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs'." The shortcut icon might even be blank or show a generic file symbol.
This usually happens right after you've uninstalled a program using a third-party uninstaller, or after you ran a registry cleaner like CCleaner. I had a client last month whose receptionist ran a "clean up" tool that nuked the entire Start Menu folder. Took me longer to explain what happened than to actually fix it.
Why this happens
The C:\ProgramData\Microsoft\Windows\Start Menu\Programs folder is where Windows stores shortcuts that appear for all users on the machine. When that folder gets deleted — either by a rogue uninstall script or an overzealous cleaner — every shortcut that points into it breaks. And since Windows itself relies on that folder for things like Accessories, System Tools, and administrative shortcuts, you get that error for built-in apps too.
Sometimes it's not even the whole folder that's gone — just the Programs subfolder inside Start Menu. But the error message is the same.
The fix: recreate the folder structure
Skip the registry edits and the SFC scans — they won't help here because the folder is just plain missing. You need to put it back. Here's how.
- Open File Explorer and navigate to
C:\ProgramData\Microsoft\Windows\Start Menu. If you can't seeProgramData, type it directly in the address bar or enable hidden items under View > Show > Hidden items. - Check if the
Programsfolder exists. If it does, open it and see if it's empty. If it's missing or empty, you'll recreate it. - Right-click an empty space inside the
Start Menufolder, select New > Folder, and name it exactlyPrograms(case doesn't matter on NTFS, but get the spelling right). - Now the shortcuts need to go back. The easiest way is to open the Start Menu yourself and drag existing shortcuts into the new folder. But there's a faster method.
- Press Win + R, type
shell:common programs, and hit Enter. If the folder still exists somewhere, this opens it. If not, you'll get the same error. That's fine — move to step 6. - Open another File Explorer window and go to
C:\ProgramData\Microsoft\Windows\Start Menu. Right-click theProgramsfolder you created, select Properties, then the Security tab. Click Advanced. At the top next to Owner, click Change and typeSYSTEM. Click Check Names, then OK. Check the box "Replace owner on subcontainers and objects" and apply. This gives Windows permission to write to it. - Now the real trick: open Command Prompt as Administrator and run this command:
mklink /J "C:\ProgramData\Microsoft\Windows\Start Menu\Programs" "%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs"
That creates a junction (a symlink) that points the missing folder back to where Windows expects it. If you get an error that the path already exists, delete the Programs folder you created (it's empty anyway) and re-run the command.
Had a client last month whose entire print queue died because of this — the printer shortcuts were all broken. Junction fixed it in 10 seconds.
If the error still shows up
If shortcuts are still broken after recreating the folder, you've got a corrupted user profile or a deeper permission issue. Try these two things:
- Create a new local user account and see if the error happens there. If it doesn't, your profile is messed up. Migrate your data and delete the old profile via Advanced System Settings > User Profiles.
- Check Group Policy — run
gpedit.mscand go to User Configuration > Administrative Templates > Start Menu and Taskbar. Look for any policy that hides or redirects the Programs folder. If one is enabled, set it to Not Configured.
After that, the error should be gone. If not, you're looking at a repair install of Windows — but I've only had to do that twice in 8 years. Usually this folder fix is all you need.
Was this solution helpful?