Bad Windows 7 service???

?

You may have to edit the service startup registry entries with the OS offline.

It may be best all around to back up the user data, then nuke and pave. Wipe the drive (use, e.g., DBAN), partition, format, and reinstall.

Note, however, that Win 7 is not susceptible to Conficker, so it is quite likely something else. And any other system should be patched by now - especially after last patch Tuesday.

to both suggesstions Thank You... I have disabled all uneccessary start up items in MSconfig=no change... and the process is not currently running it does show stopped, (no dependencies,) It is set to auto and dont know when/if it might be running but I have been fighting some weird network share drive access issues for all users and no other users have that service listed in their machines....So it is something that is not supposed to be there...but it just wont let me remove it, set to manual or disable it....The description does say something about it being a windows diagnostic service ( but I think it is lying to me) and I just want to eliminate it to make sure it is not affecting any of my other issues.

Thanks for the ideas!

Do you know how to edit the registry?

I see three ways to deal with this, two are safe and one is risky. The risky way may result in you doing it the safe way in the end, if you stuff it up.

safe way 1 - copy all data, format c: the hard drive and rebuild it.

safe way 2 - see if you can disable it in within MSCONFIG run in the Command Mode.

risky way - copy all data, run Regedit in the command mode (I assume this still works in Win 7 as I don't have a copy), go through the registry entries for the local machine until you find the entries with this name, and delete the entry. The registry entry to start looking in would be Microsoft>Windows>Current>Run

With this sort of problem is the nuke and re-install. I have seen many a tech become obsessed with an elegant solution to this sort of problem, waste a week going around in circles before ending up with a nuke and re-install. Someone has to pay for the fix, be it an employer or customer, so if you are not likely to sort it in a few hours, nuking is the most cost effective fix.

It would make such an attempt infinitely easier.

Not sure if this helps : 03.07.2010 13:58
ytiilqryep _ZOOM_SAYS:
ghyKVa wtrvmbrubqeg, [url=http://uwgsnwaybhid.com/]uwgsnwaybhid[/url], [link=http://jffjtgstsqqp.com/]jffjtgstsqqp[/link], http://podypmzgyqqx.com/
Got it from : http://joomla.aafc.dk/index.php? option=com_zoom&Itemid=31&page=view&catid=5&key=1&hit=1

Thanks to NRGZ from Xda-Developers and ppcgeeks for this great beta build wm 6.5.1 rom build for the cdma touch pro 2.
Got it from: http://digitaldiscountproducts.com/WP/tag/nrgz/

Not sure what all this is but, if I were you, I'd use KILLDISK on that drive and re-load. Just because a given AV says 'it's clean' doesn't mean it really is clean. AV products have to know what is and is not a virus (spyware) BEFORE they can disinfect same. Not a single AV product that I know of had a clue about STUXNET, and we know what happened there.