BatchPatch Forums Home › Forums › BatchPatch Support Forum › endless WU search
- This topic has 4 replies, 2 voices, and was last updated 9 years, 8 months ago by doug.
-
AuthorPosts
-
April 20, 2015 at 3:25 pm #9083boosterParticipant
Dear team,
A search for update on a particular server is currently stuck. This server was update with BP in March, no reported issue. I guess this is not a BP level error, but maybe your WU expertise can point me in the right direction?
So far here is the behaviour and what I tried
1/ search: endless, stuck in “searching” on BP side. the local server logs timestamp were not updated too. The WU cab file is well copied (ADMIN$ accessible), PSEXECSVC started, and BP agent started.
2/ Stopping the WU service is always problematic, stuck in stopping with not specific error in the windowsupdate.log
3/ starting the WU troubleshooter ends (if I kill the WU service during the process) with small correction error
I do not have the possibility to restart the server whenever I want, next maintenance plans a rename of softwaredistribution+WU agent update+reboot
Anything else I can check?
Regards
Booster
April 20, 2015 at 3:36 pm #10840dougModeratorBooster – It sounds like you’re on the right track. I’m not sure how long you left it running before you decided to stop the service and decided that it was running endlessly. However, I think you’re correct that it’s not a BP issue. I’ve seen some cases, in particular when using the WsusScn2.cab file, where a search can take a very long time. If a computer doesn’t have free RAM and plenty of CPU horsepower, it can take a very long time for it to parse the WsusScn2.cab file. However, I think your plan of restarting the machine and renaming the softwaredistribution folder is a good bet.
Good luck.
-Doug
April 20, 2015 at 4:03 pm #10817boosterParticipantHi Doug,
I let it run for more than 2 hours, not really endless but close ;). I’ve requested the maintenance, hope it will help.
thanks for your answer
Regards
Booster
April 21, 2015 at 3:11 pm #10797boosterParticipantFollow up:
The previous mentioned actions did not solved the problem, here below the steps needed in my case:
1/ open admin cmd.exe and type
DISM.exe /Online /Cleanup-image /Restorehealth
(https://support.microsoft.com/en-us/kb/947821?wa=wsignin1.0)
2/ wuauclt.exe /resetauthorization /detectnow
These steps were necessary after the following ones, successful but not solving the issue
– reboot
– sfc /scannow
– rename softwaredistribution folder
– WU agent update to last version (manual KB install)
– Windows update reset (https://support.microsoft.com/en-us/kb/971058)
– wuauclt.exe /resetauthorization /detectnow (without dism first)
Regards
Booster
April 21, 2015 at 4:58 pm #10802dougModeratorInteresting! Thanks for the follow-up. Glad you got it figured out.
-Doug
-
AuthorPosts
- You must be logged in to reply to this topic.