Windows Explorer shuts down automatically when running appwiz.cpl

carwiz · 22 Jul 2014

Yes, you did suggest that the software could've been installed under a single user or in a user restricted folder. I replied that I didn't know how that could be since I installed most programs in program file folders. Anyway, that didn't lead to a solution.

When you install programs for a single user, that works fine. When utilities or software are installed for all users, they need to run as administrator. Some installers will ask you if want the software available for all users or a single user. I didn't keep your uploaded files showing the startups but, as I recall, some were system level but most were user level.

Why did you recommend that I uninstall the IObit uninstaller? What did you see in the minidump file I sent you that indicated that IObit uninstaller was the source of the problem?

You said the problem occurred when you clicked on programs and features. There was a call to a module within the stack I didn't immediately recognize. I also noticed the IObit driver being loaded. Nearly everyone on this site who has ever worked with dumps for any length of time will recognize IObit software. It's a prime suspect for system BSODs and/or program crashes. A single uninstall is the quickest way to eliminate known problem software.

I started the clean boot testing by disabling ASC in msconfig / services but Explorer still crashes.

The problem with simply suppressing the startup of software doesn't necessarily stop the loading of drivers for that software as already mentioned. And therein lies the problem since the drivers may have installed filters, or "hooks" as some of us old guys refer to them, that can still cause problems. And that's why I suggest suppressing all startups except those indicated. If the problem continues after that, there's no sense continuing and you have to start uninstalling software.

I'll send you a PM on another mater.

accordeoniste · 23 Jul 2014

When you install programs for a single user, that works fine. When utilities or software are installed for all users, they need to run as administrator. Some installers will ask you if want the software available for all users or a single user. I didn't keep your uploaded files showing the startups but, as I recall, some were system level but most were user level.

Will it help, then, to uninstall the third-party software that's user level and re-install it as administrator?

The problem with simply suppressing the startup of software doesn't necessarily stop the loading of drivers for that software as already mentioned. And therein lies the problem since the drivers may have installed filters, or "hooks" as some of us old guys refer to them, that can still cause problems. And that's why I suggest suppressing all startups except those indicated. If the problem continues after that, there's no sense continuing and you have to start uninstalling software.

I'll send you a PM on another mater.

If the problem turns out to be due to third party software conflicts or incorrect addressing, will it behoove me to bring it to the attention of the software vendor? Or is my only recourse to either replace or remove the software if the drivers are the cause of the problem?

By the way, I'm not far away from becoming an old guy myself, so the H-word (hooks) is okay with me. I have a slight preference for "Sunday drivers" when referring to errant software. :)

accordeoniste · 12 Aug 2014

I still have the problem with Explorer crashing. I performed the clean boot / startup procedure. Right after disabling several services and start-up programs, Explorer didn't crash in standard mode, but sometimes crashed in Safe Mode. The crashing only happens when I start appwiz.cpl or run Control Panel / Programs & Features. Most of the time when I do that, Explorer doesn't crash.

Yesterday Explorer crashed in the evening, in standard mode, after Windows had been running for most of the day. The faulting module path, according to the Event Viewer, is C:\Windows\SYSTEM32\ntdll.dll. Previously it was msi.dll. Does anyone know whether the problem is with ntdll.dll, or with a conflict involving Explorer? I can provide system files for analysis.