[SOLVED] Windows Server 2016 Cumulative Updates failing to install

[NTo]

Hi,
the file is attached.

 

[Maxstar]

I'll need to setup a new VM with the same updates to compare some things in relation to the latest logs. I will do this over the weekend, especially since these kinds of driver issues are quite complicated.

Have a nice weekend and I keep you posted.

 

[Maxstar]

Hi,

Please run FRST again with system privileges with the following fix.

Start the

Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[NTo]

Hi,

I hope you had a good weekend.
The new Fixlog.txt ist attached.

 

[Maxstar]

Hi,

Please reboot the server and attempt to update. If it fails attach a new copy of the CBS logs as well as a copy of the setupapi.dev.log.

 

[NTo]

Hi,

the update failed again, logs are attched.

 

[Maxstar]

Hi,

Please do the following to perform a filesscan for another driver.

• Download the attachment SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

 

[NTo]

Hi,

the SFCFix.txt is attached.

 

[Maxstar]

You have attached a part of the CBS log as (SFCFix.txt), it does not contain the result of the script in post #47?

 

[NTo]

Hi,

oops, something went wrong, here is the right one.

 

[Maxstar]

Open an elevated command prompt and run the following command. Attach Dirlist.txt to your next post.

dir /s /a %systemroot%\System32\DriverStore\FileRepository\basicrender.inf_amd64_da1c21668d0f5953 > "%userprofile%\Desktop\Dirlist.txt"

 

[NTo]

The file is attached.

 

[Maxstar]

Start the

Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

Afterwards reboot the server and attempt to update. If it fails attach a new copy of the CBS logs as well as a copy of the setupapi.dev.log.

 

[NTo]

Hi,

unfortunately it failed again, logs are attached.

 

[Maxstar]

Please attach a new copy of the DriverDatabase subkey.

Export registry key as hive file.

• Open the Start menu of Windows and type CMD.
• When you see Command Prompt on the list, select the option Run as administrator.
• Copy and paste the following commands one at a time into the command prompt and press enter after each.

reg save "HKLM\SYSTEM\DriverDatabase" "%userprofile%\Desktop\DriverDatabase.hiv"

• Once done, a file will appear on your desktop, called DriverDatabase.hiv.
• ZIP this file and attach it to your next reply.

 

[NTo]

Hi,
the Zip is attached.

 

[Maxstar]

Sorry, I've made a stupid mistake in the last script, I created a new key instead of changing the corrupted key.

Here's the correct fix.

Start the

Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[NTo]

Hi,

here is the Fixlog.txt, i had to run it with System permissions.

 

[Maxstar]

Yes, all these fixes need to be run with system permissions.

Please reboot the server and try to update again.

 

[NTo]

Hi,

it failed again, logs are attached.