Windows Update gone bad

G

Galmok

Active member
In my Windows 10 Pro, I decided to install some windows updates and now the update system has gone bad. It never ends its search for new updates. I have tried running the Windows Update Fixer from Microsoft, and it does report errors, and claims to fix them, the they don't actually get fixed.

I tried doing it manually, but I cannot end the Windows Update service.

What are my options?

Currently I am looking to separate out the windows update service into its own svchost in order to forcibly kill it:

sc config wuauserv type= own

and delete the C:\Windows\SoftwareDistribution folder and hope this fixes it.

Other suggestions?
 
In the C:\Windows\SoftwareDistribution\ReportingEvents.log I find many lines like these:

{25D0761A-71C8-42F2-9888-4802D0364524} 2017-05-13 07:43:13:890+0200 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 UpdateOrchestrator Success Software Synchronization Windows Update Client successfully detected 7 updates.

The lines differ in the GUID and the timestamp (approx 2 per minute).

But it has run for 11 hours (so far) like this, putting more and more lines into the file.

I know it says it has detected 7 updates, but the Settings->Update & Security->Update status keeps on searching, not allowing me to install the updates.
 
The WindowsUpdate.log file generated with PS:> Get-WindowsUpdateLog is worthless as all it contains a hundreds of lines like:

1601-01-01 01:00:00.0000000 1216 4520 Unknown( 149): GUID=a72d07b7-261a-320a-bf28-ef7b30c80d88 (No Format Information found).

Notice the timestamp. Numbers vary (except 1216 that is the process id).

I guess Microsoft still hasn't managed to make Windows Update avoid the seemingly endless loops. On our servers at work (WinSer2012), Windows update has been checking for updates for months now without stopping.
 
Well, I did as I wrote in the first post. I split out the windows service process into its own, reboot, kill WU process, rename away SoftwareDistribution (can delete now), started WU service, ran WU fixer for windows 10, rebooted, and shortly after WU finally stopped and let me know 2 updates were available.

As I couldn't stop the WU service the nice way, and I did not want to kill all the associated services (10+) also hosted by the svchost process, it was necessary to split out the WU service into its own process.

I am off to install some windows updates. I hope this can help someone stuck in the same spot.

NB: I do not know how to reintegrate the WU process into the original svchost process, but there is little harm done keeping it in its own process. It does consume slightly more memory, though.
 
Ok, this hasn't solved everything it seems. I did install one of the two updates, but the last one wont install:

Feature update to Windows 10, version 1703 - Error 0x80070522

The error code means:

0x80070522
The user doesn’t have required privilege or credentials to upgrade.
Ensure that you have signed in as a local administrator or have local administrator privileges.

But I have tried with my normal login (which is in the Administrators group) as well as with the Administrator login, both with the same result.

If anyone has any idea how to solve this, I am listening. :)
 
No idea on how to solve but I'm listening as well.

Hope you can get this worked out Galmok :up:
 
The manual install of 1703 worked without issues. Windows Update also appears to work, although I have to find a way to prevent it from auto-installing when it feels like it. I had it fixed previously to only install when I ordered it to, but that behavior has stopped. Grrr.
 
You must log in or register to reply here.
Back
Top