Oh... what a MONDAY morning...
A check in the eventlog shows that some updates were installed during the weekend.
So - what now ? remove updates or.... ask google.
Ahh - I was not alone with this problem.
First, I ended up here: https://blogs.technet.microsoft.com/wsus/2016/04/22/what-you-need-to-know-about-kb3148812-part-two/
Well, I didn't install KB3148812, so this could not be my problem, but an update on the page pointed me to this site: https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/
And from here, I was pointed to the page for KB3159706, which I found was installed on my WSUS server: https://support.microsoft.com/en-us/kb/3159706
As it stated... you needed a manual process to finish this update.
The command: "wsusutil.exe postinstall /servicing" fixed my problem.
After running the command I could start the wsus service again.
No comments:
Post a Comment