[Server2012R2Upd3 x64] "We couldn't complete the update"

[Sysnative Windows Update]

attempt to install only the December update and if it fails, attach CBS.log.

 

[kcstueber]

Hi,

I did the December update only, and got the same result. Attached is the CBS.

 

[Sysnative Windows Update]

Please manually download the February update 2018 and see if you get the same result.

 

[kcstueber]

Hi,

I did KB4074594 manually. The result was the same. If it helps, the pattern has always been, I restart after the installation, it goes through the restart and does 9% of updating during shut down, after the splash screen, it give the message we couldn't complete the updates, undoing changes, then it restarts again, and appears to attempt the update again, gives the same we couldn't complete the update, and brings me to the log in. Attached is the new CBS.

 

[Sysnative Windows Update]

Please attach setupapi.dev.log and setupapi.app.log.

 

[kcstueber]

Here you go:

 

[Sysnative Windows Update]

I need some more information on the host machine.

1. What OS?
2. Is it fully patched?
3. What AV is installed on the host if any?
4. What AV exclusions are set (only if AV is installed)
5. What is the make/model of the server?
6. Where are the VMs stored? Is it local storage on the HyperV server, iSCSI target or something else?
7. How much memory, CPU cores, HDDs does the host have?
8. Has the memory been tested?

 

[kcstueber]

Hi,

I appreciate all of your time and effort to resolve this. At this point, I believe the best course of action is to do a rebuild of the Server. I have another DC with AD running in the Domain. I can switch all of the Services on our troublesome Server over. It shouldn't be too much of a hassle, and troubleshooting the WU issue, may use more time.

Thanks again,

Kurt

 

[Sysnative Windows Update]

Thank you. The decision is all yours. If you like, we can continue troubleshooting the Server.

Best of luck,
Mihael