[SOLVED] Windows Server 2019 VDI golden image KB5044277 failed

[Maxstar]

Hi,

Here's the next fix.

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

• Save any work you have open, and close all programs.
• 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.

Afterwards attempt to update, if it fails attach an new copy of the CBS logs and the Setupapi.dev.log.

 

[hey_tim]

Unfortunately it failed again, attached are the files as requested

 

[Maxstar]

!!!  idb:           Failed to publish 'C:\Windows\System32\DriverStore\FileRepository\tsgenericusbdriver.inf_amd64_d011bdda17fe2622\tsgenericusbdriver.inf'. Error = 0x00000490

Hi,

Yes, but with another error this time. So please do the following.

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

• Save any work you have open, and close all programs.
• 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.

Afterwards attempt to update, if it fails attach an new copy of the CBS logs and the Setupapi.dev.log.

 

[hey_tim]

Still no luck, attached are the files as requested.

 

[Maxstar]

Do yo have a very similar machine? If so, please provide a copy of the DriverDatabase of that machine because the VDI image is missing a lot of entry's in the registry.

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 command into the command prompt and press enter.

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.

 

[hey_tim]

It's funny you mention a similar machine, we do... However the same issue is present on that system as well. I believe it's even the same update that was failing. I would like to clarify, you would like the hive export from the machine we have been working on, is that correct?

 

[Maxstar]

Hi,

No I meant a copy of a similar machine without any issues. But here's the next fix.

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

• Save any work you have open, and close all programs.
• 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.

Afterwards attempt to update, if it fails attach an new copy of the CBS logs and the Setupapi.dev.log.

 

[hey_tim]

Looks like it failed again, attached are the files as requested.

 

[Maxstar]

Hi,

Yes, but we'll need to replace a number of registry entry's! Here's the next fix.

Note: I am hesitant to offer a complete copy of the affected subkey, so therefore I provide only seperate fixes for the issues reported in the Setupapi.dev.log.

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

• Save any work you have open, and close all programs.
• 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.

Afterwards attempt to update, if it fails attach an new copy of the CBS logs and the Setupapi.dev.log.

 

[hey_tim]

Files attached as requested.

 

[Maxstar]

Here's the next fix.

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

• Save any work you have open, and close all programs.
• 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.

Afterwards attempt to update, if it fails attach an new copy of the CBS logs and the Setupapi.dev.log.

 

[hey_tim]

Files aa requested.

 

[Maxstar]

Here's the next fix.

Question: are you able able to create a snapshot / image after this fix to rebuild the complete registry key?

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

• Save any work you have open, and close all programs.
• 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.

Afterwards attempt to update, if it fails attach an new copy of the CBS logs and the Setupapi.dev.log.

 

[hey_tim]

Update failed, attached are the files requested. I was able to promote the disk we have been working on into a test mode which let me create a new maintenance disk. We should be able to try your fix for rebuilding the complete registry key.

 

[Maxstar]

Hi,

Please run this fix in your testing environment.

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

• Save any work you have open, and close all programs.
• 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.

Afterwards attempt to update, if it fails attach an new copy of the CBS logs and the Setupapi.dev.log.

 

[hey_tim]

Attached are the files as requested.

 

[Maxstar]

Here's the next fix for the testing environment.

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

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip 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.

Afterwards attempt to update, if it fails attach an new copy of the CBS logs and the Setupapi.dev.log.

 

[hey_tim]

Attached are the files as requested

 

[Maxstar]

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 command into the command prompt and press enter.

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.

 

[hey_tim]

File attached as requested.