This might be an off question for this forum, but seeing as this is place is filled with people who actually knows their way around these things I figured I might as well ask.
My scenario is as follows:
Windows Update suddenly stops working properly, whenever run it first triggers trustedinstaller.exe which uses a static 25% cpu for a minute or so, after which an instance of svchost.exe takes over using the same amount of cpu (not isolated to once core but one is primarily higher in usage than the rest). Using ProceXP to check what is happening it just shows wuaueng.dll in the hundreds of millions of delta cycles (only info I saved before I got ignored the problem).
After trying ALL of the suggested fixes listed on windows website (fixit, reinstall, reinit, you name it) I ended up just turning the service off and ignoring it.
Over the course of two months I tested it every now and then, just to find it eating up my cpu and doing visibly nothing.
I only reboot the computer when I have done these tests, else it stays on.
Now today I went to install an old game (first install since windows update started acting up) and it did not boot up, so I checked the event viewer to see if it had anything listed. What I found was a ton of warnings that Office 15 had tried to edit the registry (I did not install this, so apparently MS sniped it onto my comp somehow... which kinda makes me worried). After uninstalled it I started wondering if windows update might have restarted itself and autodownloaded it. And lo and behold... the darn thing suddenly works!
I have done nothing at all on this comp the past two months but written documents, watched some sports and played some games... but somehow the "error" has fixed itself.
Now after writing far too long of a story, my questions are simply: How did this fix itself? And What makes these errors occur in the first place? (not the first time it has done so for me, last time I formatted the computer)
If anything I want to try and avoid having this happen again, should I be the culprit myself.
Again terribly sorry if this is a bit off the topic at hand.
Y.S
Reborn
My scenario is as follows:
Windows Update suddenly stops working properly, whenever run it first triggers trustedinstaller.exe which uses a static 25% cpu for a minute or so, after which an instance of svchost.exe takes over using the same amount of cpu (not isolated to once core but one is primarily higher in usage than the rest). Using ProceXP to check what is happening it just shows wuaueng.dll in the hundreds of millions of delta cycles (only info I saved before I got ignored the problem).
After trying ALL of the suggested fixes listed on windows website (fixit, reinstall, reinit, you name it) I ended up just turning the service off and ignoring it.
Over the course of two months I tested it every now and then, just to find it eating up my cpu and doing visibly nothing.
I only reboot the computer when I have done these tests, else it stays on.
Now today I went to install an old game (first install since windows update started acting up) and it did not boot up, so I checked the event viewer to see if it had anything listed. What I found was a ton of warnings that Office 15 had tried to edit the registry (I did not install this, so apparently MS sniped it onto my comp somehow... which kinda makes me worried). After uninstalled it I started wondering if windows update might have restarted itself and autodownloaded it. And lo and behold... the darn thing suddenly works!
I have done nothing at all on this comp the past two months but written documents, watched some sports and played some games... but somehow the "error" has fixed itself.
Now after writing far too long of a story, my questions are simply: How did this fix itself? And What makes these errors occur in the first place? (not the first time it has done so for me, last time I formatted the computer)
If anything I want to try and avoid having this happen again, should I be the culprit myself.
Again terribly sorry if this is a bit off the topic at hand.
Y.S
Reborn
