dannyrgez
New Member
Posts: 7
OS: Windows 10 Home 22H2 19045
Theme: Windows 2000
CPU: Intel i9 12900k
RAM: 32 GB
GPU: RTX 4070
|
Post by dannyrgez on May 24, 2024 17:03:56 GMT -8
  When trying to configure the WinClassic theme on Windows 10, all of the sudden all my apps just broke. I can't open any of them, including settings, windows security, microsoft store, etc. Instead I get the "Class not registered error". I've already tried repairing MS VS C++ 2015-2022 Redistributable, and tried re-registering the apps with this powershell command Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} though out of luck, any ideas? Thanks! |
|
|
|
Post by enderboy on May 24, 2024 22:42:33 GMT -8
Use classic theme uwp fix from windhawk
|
|
|
|
Post by OrthodoxWin32 on May 25, 2024 2:36:50 GMT -8
dannyrgez This error usually occurs when explorer.exe is not registered as a shell, this is not supposed to be related to the classic theme.
|
|
dannyrgez
New Member
Posts: 7
OS: Windows 10 Home 22H2 19045
Theme: Windows 2000
CPU: Intel i9 12900k
RAM: 32 GB
GPU: RTX 4070
|
Post by dannyrgez on May 25, 2024 6:08:08 GMT -8
dannyrgez This error usually occurs when explorer.exe is not registered as a shell, this is not supposed to be related to the classic theme. I see, how would I fix this? |
|
dannyrgez
New Member
Posts: 7
OS: Windows 10 Home 22H2 19045
Theme: Windows 2000
CPU: Intel i9 12900k
RAM: 32 GB
GPU: RTX 4070
|
Post by dannyrgez on May 25, 2024 6:08:55 GMT -8
Use classic theme uwp fix from windhawk Tried that too, didn't work for me... |
|
|
|
Post by OrthodoxWin32 on May 25, 2024 7:01:23 GMT -8
I see, how would I fix this? There may be a problem with Explorer. Did you notice anything strange when starting it ? |
|
dannyrgez
New Member
Posts: 7
OS: Windows 10 Home 22H2 19045
Theme: Windows 2000
CPU: Intel i9 12900k
RAM: 32 GB
GPU: RTX 4070
|
Post by dannyrgez on May 25, 2024 10:10:47 GMT -8
I see, how would I fix this? There may be a problem with Explorer. Did you notice anything strange when starting it ? Nothing strange, explorer.exe opens up normally and I can browse folders and directories. Though apps still would not open, I've tried many things including sfc /scannow, and DISM... though no luck. I've created a restore point prior to configuring the classic theme, restoring it did the trick. Now I believe it might had something to do with downloading mods from Windhawk, though I don't know for certain. |
|
|
|
Post by OrthodoxWin32 on May 25, 2024 10:42:38 GMT -8
Nothing strange, explorer.exe opens up normally and I can browse folders and directories. Though apps still would not open, I've tried many things including sfc /scannow, and DISM... though no luck. I've created a restore point prior to configuring the classic theme, restoring it did the trick. Now I believe it might had something to do with downloading mods from Windhawk, though I don't know for certain. OK, thanks to the restore point, you will be able to start from scratch. What method did you use to activate the classic theme ? |
|
dannyrgez
New Member
Posts: 7
OS: Windows 10 Home 22H2 19045
Theme: Windows 2000
CPU: Intel i9 12900k
RAM: 32 GB
GPU: RTX 4070
|
Post by dannyrgez on May 25, 2024 11:31:12 GMT -8
Nothing strange, explorer.exe opens up normally and I can browse folders and directories. Though apps still would not open, I've tried many things including sfc /scannow, and DISM... though no luck. I've created a restore point prior to configuring the classic theme, restoring it did the trick. Now I believe it might had something to do with downloading mods from Windhawk, though I don't know for certain. OK, thanks to the restore point, you will be able to start from scratch. What method did you use to activate the classic theme ? Method I used was using the classic theme try program, along with copying the installed programs from Project 2000 in a VM and copying some system32, registry keys, and sysWoW files from there too, it wasn't until I installed some mods from Windhawk is when the class not registered error started to occur, not sure which mod that did it, it had to do with an explorer mod I think. |
|
