Windows Update fails - Win2K12R2

[BDC]

I am having difficulties with a Windows Server 2012R2. This issue has apparently been going on for some time.

When I attempt to install updates, the updates appear to install, but... actually do not.

Windows will transition to the "Installing Updates" screen, install up to 8% and then start the reboot. After rebooting, I get the dreaded "We couldn't complete the updates. Undoing changes."

I had to reboot the system this morning... install updates to 8%, reboot, "We couldn't complete the updates. Undoing changes."

[This cycle (install up to 8%, reboot, undo changes) has been going on for months... and I have had no luck figuring out what is causing the issue.]

After the morning reboot, I followed the instructions. Details below.

Windows CBS logs can be found here: C - Windows - Logs - CBS.zip - Google Drive

Any assistance would be greatly appreciated.

Step 2 - Run SFC Scan
- sfc /scannow
-- Message
-- Windows Resource Protection did not find any integrity violations.

Step 3 - SURT / DISM Scan
- Dism /Online /Cleanup-Image /RestoreHealth
--
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Image Version: 6.3.9600.17031
[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was
repaired.
The operation completed successfully.

Step 4 - Run SFCFix
- Ran as Administrator
--
SFCFix version 3.0.1.0 by niemiro.
Start time: 2019-01-23 12:32:42.269
Microsoft Windows Server 2012 R2 Update 3 - amd64
Not using a script file.
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-01-23 12:33:11.517
----------------------EOF-----------------------

BDC

 

[Sysnative Windows Update]

Hello and welcome! Please attempt the updates again and attach: C:\Windows\Logs\CBS.log and C:\Windows\Inf\setupapi.dev.log.

You have driver issues, so I'd like to get a screenshot of a fully expanded Device Manager as well.

 

[BDC]

Hi SysNative,

The original CBS logs (with everything) should be available here.

I have attached the latest CBS log (the server says it needs a reboot; won't be able to reboot until tonight) as well as the Setupapi.dev.log in the attached compressed file.View attachment CBS and Setupapi.rar. After I reboot the system tonight, I will upload another set of the latest CBS log and Setupapi.dev.log.

I have also attached screenshots of the expanded Device Manager, including hidden devices.
​

View attachment Captures.rar

Additional background: This is a virtual Windows Server 2012 R2. It was moved to a new Windows Server 2012 R2 host a while ago; I have been told the old host (also Win2K12R2) was Bitlocker encrypted; the current host is not (yet).

Thank you again for any assistance.

 

[Sysnative Windows Update]

Okay, provide logs after reboot and then I'll see what I can do.

 

[BDC]

I have rebooted the server & had the same issues (no suprise). Updated CBS and setupapi logs attached View attachment 20190129 - 2 - Updates.rar.

Thanks again for all your assistance.

BDC

 

[Sysnative Windows Update]

Note: The following fix will automatically reboot your Server!

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.