Troubleshoot and Diagnostic Policy not started

I am having some trouble with my wireless connection so I clicked on "troubleshoot" as one of the good things about Windows 7 is that the "troubleshoot" actually works!

Not this time though because I get the message, "diagnostics policy not running", so I went to services and started it manually only to get the message, "the diagnostic policy service started and stopped", so it is a catch 22 situation.

Here is a pic showing the messages



Any ideas?

I also noticed Diagnostic service host and system host could not be started (option greyed out), they were set to manual start so I put them on automatic but the diagnostic policy will still not run, I still get the started and stopped message.

I changed these to auto as a guess for a fix but I will change them back now and not guess anymore in case I make things worse.

Anak said:

There are several repairs to try:

1.)

• System Restore To several days to whenever you feel the problem started.

2.)

• SFC /SCANNOW At least three times.

3.)

• Go to device manager.
• Uninstall all the network devices including the network card.(Don't delete the driver)
• Restart the computer and it should automatically find and install the network card and the driver for it.

4.)

• Check to make sure your security programs are not blocking it.

5.)

• Copy/paste msconfig into run box, make sure Normal startup is selected.

I changed these to auto as a guess for a fix but I will change them back now and not guess anymore in case I make things worse.

How did it work or did it not? I do not think you would have caused any harm, auto or auto(delayed start) would be the prefered setting.

Scroll down for Black Viper’s Windows 7 Service Pack 1 Service Configurations | Black Viper's Website | www.blackviper.com

He recommends, Automatic (Started)

Thanks Anak! What a comprehensive answer. :)

1. about to try it, but I only have one system restore point and I don't know when the problem started...but yea about to try it.

2. ran it once so far, it did find something and repaired it but it was unrelated. Will try it a few more times.

3. did that, didn't work

4. how can I check? I bet it is bloody BitDefender causing problems, again!

5. done that, normal was already selected.

Changing Diagnostic service host and system host to auto start did not help, no.

Thanks again, I will report back after system restore etc.

Anak said:

As I have suggested in #3 the underlying cause could be a corrupted driver. #1 and #2 might help with that.

Just noticed....Are you replying to solutions by number?

3. did that, didn't work

#3 Reinstalling the drivers did not work?

Yes I was replying by the numbers you used. :)

Reinstalling the driver did not work.

I have ran scannow twice more - didn't work.

System restore did not work, the restore point was only 3 days old and who knows when the problem started.

That only leaves - 4. security program affecting it. Could be that, Bit Defender is newly installed and has already caused one (unrelated problem). I am only using it for antivirus and firewall. I don't know how to check if it could be causing this problem or not.

I suppose a repair install might help or I might just re-install Windows as this a fairly new install and there are a few things that I would do differently this time anyway.

I have done last known configuration, didn't work.

I will have a look at BitDefender again, I have had a quick look and couldn't see anything but I will have a better look later on today.

If Avast is second choice here, what is first, MSE?

I won't be doing a repair install or fresh install anytime soon, I would still like to know what is causing this problem.


Thanks again Anak. :)