Windows Explorer shuts down automatically when running appwiz.cpl

accordeoniste · 20 Jul 2014

Hi Carwiz,

Attached is a screenshot file of the sfc /scannow command I ran.

I uninstalled the IObit uninstaller program and rebooted. Windows Explorer crashed when I opened Programs and Features.

carwiz · 20 Jul 2014

Did you get a new dump? Upload that and the files from the BSOD diagnostic utility. I'll be back later this evening to take al look.

accordeoniste · 20 Jul 2014

Okay, Carwiz, I ran the SF Diagnostic tool and saved the results in a folder. Attached is the compressed folder and a new compressed .dmp file.

carwiz · 20 Jul 2014

Allow at least five minutes for the diagnostic utility to complete all the phases and resubmit the complete group.

Is this a development machine?

A Guy · 20 Jul 2014

See if you have a corrupt .cpl loading when you go to control panel.

Navigate to C:\windows\System32> In search box upper right type *.cpl> Double click on each of the .cpl files and see if they open normally

If one caused Explorer to crash, that is likely your suspect. If it is a 3rd party .cpl, uninstall that product. If it is a Windows .cpl, that is more difficult as you have already run SFC. A Guy

accordeoniste · 20 Jul 2014

carwiz said:

Allow at least five minutes for the diagnostic utility to complete all the phases and resubmit the complete group.

Is this a development machine?

Sorry about that, Carwiz. I re-ran the diagnostic utility. Attached is the updated .zip file with additional system info files. I'm sure that all were captured this time.

No, this isn't a development machine.

Slartybart · 21 Jul 2014

You mentioned errors in SFC that were fixed. It would behoove members to know what was corrupted.
You also mentioned having difficulty with Windows Updates.

Follow this tutoprial, since you ran SFC - you can skip step 2t, just do the SURT and log collection steps. the zip folder will have the SFC output from your previous runs in it.
Windows Update Posting Instructions

Thanks

accordeoniste · 21 Jul 2014

Slartybart,

I no longer need to troubleshoot Windows updates since that problem was solved after I performed a repair install. Since you asked which of my system files were corrupted, I'm attaching a compressed log file for your review. The log file was produced after I ran SFC the first time.

A Guy · 21 Jul 2014

Did you get a chance to test your .cpl files as suggested above? A Guy

Slartybart · 21 Jul 2014

accordeoniste said:

Slartybart,

I no longer need to troubleshoot Windows updates since that problem was solved after I performed a repair install. Since you asked which of my system files were corrupted, I'm attaching a compressed log file for your review. The log file was produced after I ran SFC the first time.

Thanks - it is a mess. Is this SFC before or after the repair install?

I don't understand your decision not to run SURT, but it is your decision. The utility is often useful for finding and fixing things not found and fixed by SFC.

I was focused on msi being reported as the culprit - there are a few ways to address that a wonky msi. Since the installer service is integral to Windows Update, SURT is the easiest first test solution.

There are some very talented members working on the issue, I'll sit this one out.

Good luck,

Bill
.