Problem with windows Diagnostics Troubleshooting with "error 0x80004005" [A problem is preventing the troubleshooter from starting.]

Question

All of the Diagnostic Troubleshooters have the same message  "A problem is preventing the troubleshooter from starting" and error code 0x80004005.

All of the troubleshooter wizards have this complete message with their own individual parts.

An error occurred while troubleshooting:

A problem is preventing the troubleshooter from starting.

Individual parts:

Package ID: AeroDiagnostic

Path: C:\Windows\diagnostics\system\Aero

Error code: 0x80004005

Source: Engine

Users: SWIFTYCORTEX\SwiftyCortex

Context: Elevated

Package ID: DisplayQualityDiagnostic

Path: Non-local Package

Error code: 0x80004005

Source: Engine

Users: SWIFTYCORTEX\SwiftyCortex

Context: Elevated

Package ID: NetworkDiagnosticsInbound

Path: C:\Windows\diagnostics\system\Networking

Error code: 0x80004005

Source: Engine

Users:  SWIFTYCORTEX\SwiftyCortex

Context: Elevated

Package ID: NetworkDiagnosticsWeb

Path: C:\Windows\diagnostics\system\Networking

Error code: 0x80004005

Source: Engine

Users: SWIFTYCORTEX\SwiftyCortex

Context: Elevated

Package ID: NetworkDiagnosticsNetworkAdapter

Path: C:\Windows\diagnostics\system\Network

Error code: 0x80004005

Source: Engine

Users: SWIFTYCORTEX\SwiftyCortex

Context: Elevated

Package ID: PrinterDiagnostic

Path: Unknown

Error code: 0x80004005

Source: Engine

Users: SWIFTYCORTEX\SwiftyCortex

Context: Elevated

Package ID: MaintenanceDiagnostic

Path: C:\Windows\diagnostics\scheduled\Maintenance

Error code: 0x80004005

Source: Engine

Users: SWIFTYCORTEX\SwiftyCortex

Context: Elevated

Package ID: WindowsUpdateDiagnostic

Path: Non-local Package

Error code: 0x80004005

Source: Engine

Users: SWIFTYCORTEX\SwiftyCortex

Context: Elevated

I know this is not all of the trouble shooters, but this gives you idea of what is going on. The only time there is a different message, is when I selected the Openwith for a .dll file, the only program to choose from was Diagnostic Troubleshooting Wizard. It returned with this message:

An error occurred while loading the troubleshooter:

An unexpected error occurred. The troubleshooting wizard can't continue.

Package ID: Unknown

Path: Unknown

Error code: 0x80070057

Source: Command line

Users: SWIFTYCORTEX\SwiftyCortex

Context: Elevated

If anyone knows what is causing this with the Diagnostic Troubleshooting Wizard, and what the default program for .dll files, please help me.

Thank you very much in advance.

Answer 1

Here's an unexpected answer, I have been searching google for literally hours for this and no one had it but I accidentally figured it out when a Fixit didn't work and referred to a temp file, My temp path I changed in the environment variables to point to a Ram Drive, Seems Trouble Shooter doesn't play nicely with Ram Drives so I put it back to C:TEMP and HAD to reboot (not sure if it would work with temp path set to an external hard drive). Very annoying, I set it to Ram Drive because its faster and it doesn't matter if it gets fragmented.

So many people go on about sfc/scannow which can't possibly fix the problem because its not a cause of files being corrupted.

So go to control panel and look at the top left search box, Type env (you don't have to type the whole work environment) look down click edit system environment variables click yes if asked, look down the window that opens click on Environment Variables and check that the TEMP and TMP Variables are set to your C: drive, I don't remember the default so I set mine to C:TEMP, The default may have been C:WINDOWS\TEMP.  Please do not type C:\  the \ seems to cause a problem.

Hope this helps :-), Please let me know.

Answer 2

thank you!!! I have the same exact problem - using a ram disk and troubleshooting fails - having problems with photo metro app shutting down also fixed when temp was moved back to default locations.

Answer 3

Here's an unexpected answer, I have been searching google for literally hours for this and no one had it but I accidentally figured it out when a Fixit didn't work and referred to a temp file, My temp path I changed in the environment variables to point to a Ram Drive, Seems Trouble Shooter doesn't play nicely with Ram Drives so I put it back to C:TEMP and HAD to reboot (not sure if it would work with temp path set to an external hard drive). Very annoying, I set it to Ram Drive because its faster and it doesn't matter if it gets fragmented.

So many people go on about sfc/scannow which can't possibly fix the problem because its not a cause of files being corrupted.

So go to control panel and look at the top left search box, Type env (you don't have to type the whole work environment) look down click edit system environment variables click yes if asked, look down the window that opens click on Environment Variables and check that the TEMP and TMP Variables are set to your C: drive, I don't remember the default so I set mine to C:TEMP, The default may have been C:WINDOWS\TEMP.  Please do not type C:\  the \ seems to cause a problem.

Hope this helps :-), Please let me know.

T H A N K    Y O U ! :)

Answer 4

Yes, very similarly I had set TEMP and TMP to a "D" drive which has failed and no longer present.

Answer 5

Hi SwiftyCortex,

As per the problem description, I understand that, you have an issue with Diagnostic Troubleshooters performance, I would request to send us additional information as listed below to assist you better.

Have you made any changes to the computer prior to this issue?

You may try the following methods and check the issue status.

Method 1:

Perform SFC scan and check the issue status.

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

http://support.microsoft.com/kb/929833

Method 2:

Perform system restore to a system restore point where everything was fine.

System Restore.

http://windows.microsoft.com/en-US/windows7/products/features/system-restore

Hope this information is helpful. If the issue still persists, I would request you to reply us with troubleshooting result to assist you further. We’ll be happy to assist you.