|
|
Post by zdunklee on Aug 11, 2011 8:30:59 GMT -5
My computer won't connect to the internet after it screwed up during a Microsoft update. I can't run the troubleshooting because the diagnostic policy service won't start even when trying to force it to work. Any suggestions would be great since I've spent countless hours the last two days attempting to find a solution.
I should also mention that system restore fails to correct the problem as well.
As a side note, sorry for any misspelled words...I have to use my phone and autocorrect acts weird at times.
|
|
|
|
Post by zdunklee on Aug 11, 2011 18:10:53 GMT -5
Well, not sure what I did...but my computer finally did enough of a system restore to get the internet back again...fucking Microsoft and their failed update system...never going to let that shit happen again.
|
|
|
|
Post by Rebel on Aug 11, 2011 22:08:10 GMT -5
Oh, good. I thought "System Restore" when I read the first half of your post and then couldn't think of any simple suggestions when I read that didn't work.
What version of Windows do you have? Updates are a pain in the ass on 7--they seem to come every day and make your machine take forever to start up and shutdown while they are installing, but at least 7 seems to do a good job of recovering from a fail.
|
|
|
|
Post by Rebel on Aug 11, 2011 22:09:18 GMT -5
On second thought, I do have a decent suggestion for if that happens to you again. Boot into Safe Mode, go into Add/Remove programs, click "Show Updates" and uninstall whichever recent updates might have been causing your problem.
|
|
|
|
Post by zdunklee on Aug 11, 2011 23:43:53 GMT -5
On second thought, I do have a decent suggestion for if that happens to you again. Boot into Safe Mode, go into Add/Remove programs, click "Show Updates" and uninstall whichever recent updates might have been causing your problem. That would be a great idea...except that when it fails during an update it doesn't show up as being installed. I spent countless hours trying to fix the problem. Apparently is involves registry permissions being messed up and doesn't allow anything from windows firewall to the dhcp protocol or troubleshooter to work at all, among other less important services. From what I read on every tech support site I found Microsoft has had this same issue since Vista and still has no solution that works every time. I tried no less than 10 different fixes that worked for other people and not one of them worked. I basically said fuck it and started trying system restore before the system booted up from every possible restore point...luckily one of them actually worked. |
|
|
|
Post by Dino on Aug 12, 2011 11:05:16 GMT -5
My wife had a similar problem yesterday. It looked like it was going to update and when she restarted her screen was black for about an hour she didn't know what to do so she just let it sit and was going to wait until I got home (not that I knew what to do either) but it finally booted. Must have been something with this weeks update.
|
|
|
|
Post by Opus on Aug 12, 2011 12:01:51 GMT -5
Microsoft has this stupid Driver Signing policy. Basically what it is, they have hardware manufacturers submit the driver software to them while the product is in development or being updated.
Microsoft then analyzes the driver, tests it on a bunch of configurations to verify that it won't conflict with anything else, and puts a bunch more red tape processes that tie it up for months/years. Once this is done, they approve a driver and put it on Windows Update.
In the meantime, the hardware may have gone through multiple revisions, and require an updated driver. But since the new driver has not been digitally signed, win updates gives precedence to the one that is signed and installs it, thus breaking the operability of the device.
I have had HUGE headaches with network cards and sound cards because of this. It's hard to download a driver for a network card when it can't go online.
|
|
|
|
Post by Rebel on Aug 12, 2011 14:02:55 GMT -5
Microsoft has this stupid Driver Signing policy. Basically what it is, they have hardware manufacturers submit the driver software to them while the product is in development or being updated. Microsoft then analyzes the driver, tests it on a bunch of configurations to verify that it won't conflict with anything else, and puts a bunch more red tape processes that tie it up for months/years. Once this is done, they approve a driver and put it on Windows Update. In the meantime, the hardware may have gone through multiple revisions, and require an updated driver. But since the new driver has not been digitally signed, win updates gives precedence to the one that is signed and installs it, thus breaking the operability of the device. I have had HUGE headaches with network cards and sound cards because of this. It's hard to download a driver for a network card when it can't go online. True. I NEVER take Windows Update drivers for my Win XP machines because it's too risky. Not much choice for my Win 7 machine, because sometimes it's the only way to get a 64-bit driver. |
|
|
|
Post by zdunklee on Aug 12, 2011 18:10:15 GMT -5
Yea, after I got it working again all the updates installed fine...but I did make sure to do them one at a time to make sure I knew which one was going to screw up. I found thousands of threads on my specific problem which was this: www.techsupportforum.com/forums/f217/cannot-start-the-diagnostic-policy-service-187329.htmlHowever, not many methods did much of anything because apparently in the middle of security updates if it screws up the registry permissions get all kinds of messed up and then ALL the internet based processes can't connect to anything. Oh and it makes it so Event Viewer can't open either...good luck figuring out the problem without that little guy... |
|
|
|
Post by potthole on Aug 13, 2011 0:07:59 GMT -5
Updates are a pain in the ass on 7--they seem to come every day and make your machine take forever to start up and shutdown while they are installing YES! And to make things worse for me, I've got two external hard drives hooked up to my 7 machine and when it tries to validate an upgrade (or whatever the specific phrasing) upon start up, it never completes the task, Therefore, when I shut down at the end of the day, the whole stinking upgrade starts from again scratch. It's gotten to the point that I just unplug the drives when I don't need to use them. |
|
