Control Panel Crashes

from Stardock Forums

Windows 10 recently upgraded on May 13, 2017.  Now, Windows Control Panel crashes whenever I open it.  I configured Windowblinds (version 10.62) in the Configuration "per application" section to "Total Exclusion" Config.exe, but Windowblinds appears to ignore that optional command and Control Panel still crashes.  Control Panel only opens for a split second before it crashes, but I think I still see evidence of Windowblinds re-configuring the Control Panel.  What can I do to fix this problem?

windowblinds
6,715 views 5 replies
Reply #1 from WinCustomize Forums Top

Hi tortoise14, 

My laptop recently updated Windows 10 and I had the exact same problem, the Control Panel crashed when I opened it.  I've updated at least ten computers to the latest Creators Edition of Windows 10, and the only one I had a problem with is my laptop.

I don't think it's Windowblinds that is causing the issue.  My desktop is running the same version of Windows 10, and the Control Panel works perfectly.  I have Windowblinds running on both systems.

If anyone knows what could be causing the problem, it would be great to get it solved.

Thank you!

Reply #2 from WinCustomize Forums Top

What kind of laptop? I have a Toshiba with an AMD processor, running the latest Win10 version. WindowBlinds runs perfectly and the control panel I have no problem with. 

SoundPackager - Customize the Windows sound scheme
Reply #3 from Stardock Forums Top

The first thing to check is what if WindowBlinds is not running?  Does it still crash?

I did see a Start10 user report a similar crash so are you also running that?

In testing here we are not seeing any issues but it could be some third party control panel add on.

One other thing to check, are you using the option to hide the ribbon control and are you using anything which alters explorer itself?

Reply #4 from WinCustomize Forums Top

Is it only Control Panel that crashes or are other Windows features affected?  I had an issue with Control Panel and Administrative Tools crashing. It turned out that BITS [Background Intelligent Transfer Service] had somehow become corrupted and needed to be repaired, which I was able to do by typing sfc/ scannow in Command Prompt, pressing 'Enter'.

If yours is the same or a similar issue perhaps this remedy will also assist you. :)