Windows 10 Control Panel issues

Hey there!
Whenever I try to open the Control Panel on Windows 10, it pops up for a split second and then just vanishes—poof.
Has anyone else run into this glitch, and does anyone know a quick fix?

I ran into this exact same headache. If you’ve got the guts to mess with the registry:
Hit Win + x, type regedit, and hit enter.
Hunt down this path: HKEY_CURRENT_USER\SOFTWARE\Classes\Local Settings\Software\Microsoft\Windows\Shell. Wipe out everything sitting under BagMRU and Bags.
Reboot the rig and try opening the Control Panel again.
Let me know if that actually worked.

Cleared out everything from BagMRU, though there wasn't anything in Bags to begin with.
Sadly, no luck here—zero points. It's still doing the exact same thing. It pops up for a second or two and then just vanishes.
Did you actually get it to work on your end?

https://www.google.com/amp/www.thewin...en-windows/amp

Sent from my ASUS_Z00AD via Tapatalk

Andrew Peterson2 said:https://www.google.com/amp/www.thewin...en-windows/amp

Sent from my ASUS_Z00AD via Tapatalk

I tried booting into Safe Mode—works perfectly there—but as soon as I switch back to normal mode, the issue pops right back up.

Honestly, you should just go through with a hard reset or hit the recovery option. The whole thing is pretty much automated, and you can usually tell it not to wipe your old files—but for heaven's sake, make a backup first... just to be safe. It’ll save you a massive headache and hopefully finally kill off that bug once and for all.

Sent from my ASUS_Z00AD via Tapatalk

Andrew Peterson2 said:Honestly, you should just go through with a hard reset or hit the recovery option. The whole thing is pretty much automated, and you can usually tell it not to wipe your old files—but for heaven's sake, make a backup first... just to be safe. It’ll save you a massive headache and hopefully finally kill off that bug once and for all.

Sent from my ASUS_Z00AD via Tapatalk

I hear you, though. I've tried everything under the sun and nothing worked. Eventually, I realized the OS has to be set to English for it to actually function properly. If you try running it in American English settings when the system expects something else, that's exactly when this mess happens.

Try hitting Win + R on your keyboard, then just type in control and hit enter