[SOLVED] Windows (Cumulative) Updates failing to install [Server 2016]

bcmaze · May 10, 2022

Just to make sure we are on the same page, I export it as "Registry Hive Files (*.*)"?

Because doing so the exported file has no extension and then the upload to the forum will not work.
Thats why I just added .txt extention to allow the upload here in the Forum.
You just can remove the .txt so you have that exported registry hive file.

Or did I miss something?

I attached a ZIP with two files...
One with an .reg extension is obviously the "Registration Files" export in the screenshot above.
One with no extension is the "Registry Hive Files" export in the screenshot above (arrow).

x BlueRobot · May 11, 2022

Rich (BB code):

HKEY_LOCAL_MACHINE\Maze\DriverInfFiles\usbport.inf
    (Default)    REG_MULTI_SZ    usbport.inf_amd64_5422ad1fd389c7d8
    Active    REG_SZ    usbport.inf_amd64_48cb2f2481ad4968

Rich (BB code):

HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\usbport.inf
    (Default)    REG_MULTI_SZ    usbport.inf_amd64_48cb2f2481ad4968\0usbport.inf_amd64_91de451ed92f4ad1
    Active    REG_SZ    usbport.inf_amd64_48cb2f2481ad4968

Thank you, a few of things to verify:

Could you please verify the exact build number of the server using winver.
Could you please confirm that the %systemroot%\System32\DriverStore\FileRepository\usbport.inf_amd64_91de451ed92f4ad1 directory exists
Could you please confirm that the %systemroot%\System32\DriverStore\FileRepository\usbport.inf_amd64_5422ad1fd389c7d8 does not exist

bcmaze · May 11, 2022

1. Based on winver its Version 1607 (Build 14393.2515)

2. NOT CONFIRMED! The directory %systemroot%\System32\DriverStore\FileRepository\usbport.inf_amd64_91de451ed92f4ad1 doesn't exist.
3. NOT CONFIRMED! The directory %systemroot%\System32\DriverStore\FileRepository\usbport.inf_amd64_5422ad1fd389c7d8 exists.

x BlueRobot · May 12, 2022

Thank you, could you please provide your DRIVERS hive:

Upload Drivers Hive[/B]

Navigate to C:\Windows\System32\config
Right-click on the current DRIVERS file and select copy
Note: If you get an error that the file is in use, reboot your computer and then try again.
Right-click on your Desktop and select paste
Right-click on the DRIVERS file on your Desktop and select Send To -> Compressed (zipped) Folder
Upload the zip from your Desktop to a file sharing service such as Dropbox or OneDrive or SendSpace and include the link with your reply.

bcmaze · May 13, 2022

Find enclosed the link to the zipped DRIVERS file:

DRIVERS.zip (898.92KB) - SendSpace.com

x BlueRobot · May 13, 2022

Unfortunately, I'm getting a scheduled maintenance page when trying to download the file from SendSpace, would you mind uploading the file to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free ?

bcmaze · May 13, 2022

Here we go: DRIVERS.zip

x BlueRobot · May 13, 2022

Could you please create a backup of your system and then run the attached FRST fix script using the following instructions:

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. Download the attached fixlist.txt 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

bcmaze · May 13, 2022

Thanks.

When runnig FRST64.exe as administrator with a domain Admin user I got a "Error: Access Denied" (Fehler: Zugriff verweigert) message in Fixlog.txt:

Running FRST64.exe as SYSTEM did the trick:

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 11-05-2022
Ran by SYSTEM (13-05-2022 14:43:46) Run:5
Running from D:\tmp\FRST
Loaded Profiles: adm_xxxxx & CitrixTelemetryService
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
Reg: reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\usbport.inf /ve /t REG_MULTI_SZ /d usbport.inf_amd64_48cb2f2481ad4968 /f
*****************

Error: (0) Failed to create a restore point.

========= reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\usbport.inf /ve /t REG_MULTI_SZ /d usbport.inf_amd64_48cb2f2481ad4968 /f =========

Der Vorgang wurde erfolgreich beendet.



========= End of Reg: =========


==== End of Fixlog 14:43:47 ====

"Der Vorgang wurde erfolgreich beendet." means something like "the process was completed successfully".

In registry I can see the entry:

x BlueRobot · May 13, 2022

Okay, it looks like it has managed to successfully update that value, I assume that (Standard) is how the German localisation of Regedit displays the (Default) key? Could you please try and apply the cumulative update again?

If it fails, then please provide the latest CBS log and the setupapi.dev.log as you did before.

bcmaze · May 13, 2022

x BlueRobot said:
Okay, it looks like it has managed to successfully update that value, I assume that (Standard) is how the German localisation of Regedit displays the (Default) key?

Exactly! "Standard" = "Default"

Just started the online update again and will post the result soon.
Many thanks for your time and patience!

x BlueRobot · May 15, 2022

Okay, please let me know how it goes and provide the CBS log if it fails.

bcmaze · May 16, 2022

Hi,
I had to redo the update because someone rebooted the machine and the CBS logs got overwritten...
So the Servicing Stack Update for 2022-05 went fine but the 2022-05 CU failed again.

Attached there is a CBS.zip which contains all the CBS log files for CU 2022-05 install (unfortunately the CBS.log are splitted in three files).
Additionally I attached the setupapi.dev.log.

x BlueRobot · May 16, 2022

Rich (BB code):

2022-05-16 11:04:23, Info                  CBS    Doqe: Recording result: 0x80070002, for Inf: sdstor.inf
2022-05-16 11:04:23, Info                  CBS    DriverUpdateStageUpdates failed [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-05-16 11:04:23, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Rich (BB code):

     idb:      {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\sdstor.inf_amd64_54d057b18d021cc5\sdstor.inf} 11:04:23.361
     idb:           Created driver package object 'sdstor.inf_amd64_54d057b18d021cc5' in SYSTEM database node.
     idb:           Driver INF file object 'sdstor.inf' already exists in SYSTEM database node.
!!!  idb:           Failed to query processor architecture for 'sdstor.inf_amd64_58b083db2df58457'. Error = 0x00000002
!!!  idb:           Failed to register driver package 'sdstor.inf_amd64_54d057b18d021cc5' against 'sdstor.inf'. Error = 0x00000002
!!!  idb:           Failed to register driver package 'C:\Windows\System32\DriverStore\FileRepository\sdstor.inf_amd64_54d057b18d021cc5\sdstor.inf'. Error = 0x00000002
     idb:      {Register Driver Package: exit(0x00000002)} 11:04:23.361
     sto:      {DRIVERSTORE IMPORT END} 11:04:23.361
     sto:      {DRIVERSTORE IMPORT END: exit(0x00000000)} 11:04:23.361
     sto:      Rolled back driver package import.
!!!  sto:      Failed to import driver package into Driver Store. Error = 0x00000002

It seems like the same issue as last time but with a different driver package. Could you please try the attached FRST fix script? Afterwards, please try and update again and then post the CBS log along with the setupapi.dev.log.

bcmaze · May 17, 2022

Thanks for the reply.

I had to run FRST64.exe as SYSTEM again to get the things fixed but it looks OK:

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 11-05-2022
Ran by SYSTEM (17-05-2022 08:16:52) Run:7
Running from D:\tmp\2022-05-17_FRXLIST
Loaded Profiles: adm_xxxxx & CitrixTelemetryService
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
Reg: reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\sdstor.inf /ve /t REG_MULTI_SZ /d sdstor.inf_amd64_54d057b18d021cc5 /f
Reg: reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\sdstor.inf /v Active /t REG_SZ /d sdstor.inf_amd64_54d057b18d021cc5 /f
*****************

Error: (0) Failed to create a restore point.

========= reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\sdstor.inf /ve /t REG_MULTI_SZ /d sdstor.inf_amd64_54d057b18d021cc5 /f =========

Der Vorgang wurde erfolgreich beendet.



========= End of Reg: =========


========= reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\sdstor.inf /v Active /t REG_SZ /d sdstor.inf_amd64_54d057b18d021cc5 /f =========

Der Vorgang wurde erfolgreich beendet.



========= End of Reg: =========


==== End of Fixlog 08:16:53 ====

The cumulative update, unfortunately, failed again.
Find attached the CBS.zip and setupapi.dev.log file

x BlueRobot · May 17, 2022

Rich (BB code):

     sto:      {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 09:15:48.119
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_tsusbhub.inf_31bf3856ad364e35_10.0.14393.5006_none_7fb7ce1ccfe3d23f\tsusbhub.inf' to 'C:\Windows\System32\DriverStore\FileRepository\tsusbhub.inf_amd64_e38da64d635170e2\tsusbhub.inf'.
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_tsusbhub.inf_31bf3856ad364e35_10.0.14393.5006_none_7fb7ce1ccfe3d23f\tsusbhub.sys' to 'C:\Windows\System32\DriverStore\FileRepository\tsusbhub.inf_amd64_e38da64d635170e2\tsusbhub.sys'.
     idb:      {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\tsusbhub.inf_amd64_e38da64d635170e2\tsusbhub.inf} 09:15:48.119
     idb:           Created driver package object 'tsusbhub.inf_amd64_e38da64d635170e2' in SYSTEM database node.
     idb:           Driver INF file object 'tsusbhub.inf' already exists in SYSTEM database node.
!!!  idb:           Failed to query processor architecture for 'tsusbhub.inf_amd64_8fc8b454c2989861'. Error = 0x00000002
!!!  idb:           Failed to register driver package 'tsusbhub.inf_amd64_e38da64d635170e2' against 'tsusbhub.inf'. Error = 0x00000002
!!!  idb:           Failed to register driver package 'C:\Windows\System32\DriverStore\FileRepository\tsusbhub.inf_amd64_e38da64d635170e2\tsusbhub.inf'. Error = 0x00000002
     idb:      {Register Driver Package: exit(0x00000002)} 09:15:48.119
     sto:      {DRIVERSTORE IMPORT END} 09:15:48.119
     sto:      {DRIVERSTORE IMPORT END: exit(0x00000000)} 09:15:48.119
     sto:      Rolled back driver package import.
!!!  sto:      Failed to import driver package into Driver Store. Error = 0x00000002

Rich (BB code):

2022-05-17 09:15:48, Info                  CBS    Doqe: Recording result: 0x80070002, for Inf: tsusbhub.inf
2022-05-17 09:15:48, Info                  CBS    DriverUpdateStageUpdates failed [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-05-17 09:15:48, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-05-17 09:15:48, Info                  CBS    Perf: Doqe: Staging ended.

Could you please try the attached FRST fix script? Afterwards, please try and update again and post the same log files as before if it fails. Unfortunately, we're going to just have to keep attempting to update until the driver package issues have been resolved.

bcmaze · May 17, 2022

Well... At least there is some progress...

CU-update failed again I assume this time it has something to do with "usbstor.inf_amd64_6efc63585e707e3f" :)

Fixlog:

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 11-05-2022
Ran by SYSTEM (17-05-2022 15:35:12) Run:8
Running from D:\tmp\2022-05-17_FRXLIST2
Loaded Profiles: adm_xxxxx & CitrixTelemetryService
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
Reg: reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\tsusbhub.inf /ve /t REG_MULTI_SZ /d tsusbhub.inf_amd64_e38da64d635170e2 /f
Reg: reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\tsusbhub.inf /v Active /t REG_SZ /d tsusbhub.inf_amd64_e38da64d635170e2 /f
*****************

Error: (0) Failed to create a restore point.

========= reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\tsusbhub.inf /ve /t REG_MULTI_SZ /d tsusbhub.inf_amd64_e38da64d635170e2 /f =========

Der Vorgang wurde erfolgreich beendet.



========= End of Reg: =========


========= reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\tsusbhub.inf /v Active /t REG_SZ /d tsusbhub.inf_amd64_e38da64d635170e2 /f =========

Der Vorgang wurde erfolgreich beendet.



========= End of Reg: =========


==== End of Fixlog 15:35:12 ====

Find attached the CBS.zip and setupapi.dev.log.

Thanks

x BlueRobot · May 17, 2022

Rich (BB code):

     sto:      {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 16:38:53.197
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_usbstor.inf_31bf3856ad364e35_10.0.14393.4704_none_b6465f96077789f0\usbstor.inf' to 'C:\Windows\System32\DriverStore\FileRepository\usbstor.inf_amd64_32a33ea3f03dff9e\usbstor.inf'.
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_usbstor.inf_31bf3856ad364e35_10.0.14393.4704_none_b6465f96077789f0\USBSTOR.SYS' to 'C:\Windows\System32\DriverStore\FileRepository\usbstor.inf_amd64_32a33ea3f03dff9e\USBSTOR.SYS'.
     idb:      {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\usbstor.inf_amd64_32a33ea3f03dff9e\usbstor.inf} 16:38:53.213
     idb:           Created driver package object 'usbstor.inf_amd64_32a33ea3f03dff9e' in SYSTEM database node.
     idb:           Driver INF file object 'usbstor.inf' already exists in SYSTEM database node.
!!!  idb:           Failed to query processor architecture for 'usbstor.inf_amd64_6efc63585e707e3f'. Error = 0x00000002
!!!  idb:           Failed to register driver package 'usbstor.inf_amd64_32a33ea3f03dff9e' against 'usbstor.inf'. Error = 0x00000002
!!!  idb:           Failed to register driver package 'C:\Windows\System32\DriverStore\FileRepository\usbstor.inf_amd64_32a33ea3f03dff9e\usbstor.inf'. Error = 0x00000002
     idb:      {Register Driver Package: exit(0x00000002)} 16:38:53.213

Please follow the same instructions as before. And yes, so the problem is the usbstor.inf_amd64_6efc63585e707e3f subkey doesn't exist anymore under HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages. I would recreate the subkey if your build was available, but unfortunately it isn't, therefore I've had to update the DriverInfFiles subkey to point to the driver package which it's importing.

bcmaze · May 17, 2022

Thank you for you patience.

Another try (CU update), another fail :)

Find Fixlog:

Code:

Fix result of Farbar Recovery Scan Tool (x64) Version: 11-05-2022
Ran by SYSTEM (17-05-2022 18:46:46) Run:9
Running from D:\tmp\2022-05-17_FIXLIST3
Loaded Profiles: adm_xxxxx & CitrixTelemetryService
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
Reg: reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\usbstor.inf /ve /t REG_MULTI_SZ /d usbstor.inf_amd64_32a33ea3f03dff9e /f
Reg: reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\usbstor.inf /v Active /t REG_SZ /d usbstor.inf_amd64_32a33ea3f03dff9e /f
*****************

Error: (0) Failed to create a restore point.

========= reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\usbstor.inf /ve /t REG_MULTI_SZ /d usbstor.inf_amd64_32a33ea3f03dff9e /f =========

Der Vorgang wurde erfolgreich beendet.



========= End of Reg: =========


========= reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\usbstor.inf /v Active /t REG_SZ /d usbstor.inf_amd64_32a33ea3f03dff9e /f =========

Der Vorgang wurde erfolgreich beendet.



========= End of Reg: =========


==== End of Fixlog 18:46:46 ====

Attached, as ususal CBS.zip and setupapi.dev.log

I guess next will be "wsynth3dvsc.inf_amd64_389b9d81ce9991d7"?

x BlueRobot · May 18, 2022

Rich (BB code):

     idb:      {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\wsynth3dvsc.inf_amd64_389b9d81ce9991d7\wsynth3dvsc.inf} 19:29:39.403
     idb:           Created driver package object 'wsynth3dvsc.inf_amd64_389b9d81ce9991d7' in SYSTEM database node.
     idb:           Driver INF file object 'wsynth3dvsc.inf' already exists in SYSTEM database node.
!!!  idb:           Failed to query processor architecture for 'wsynth3dvsc.inf_amd64_436bcb4e8b6896db'. Error = 0x00000002
!!!  idb:           Failed to register driver package 'wsynth3dvsc.inf_amd64_389b9d81ce9991d7' against 'wsynth3dvsc.inf'. Error = 0x00000002
!!!  idb:           Failed to register driver package 'C:\Windows\System32\DriverStore\FileRepository\wsynth3dvsc.inf_amd64_389b9d81ce9991d7\wsynth3dvsc.inf'. Error = 0x00000002
     idb:      {Register Driver Package: exit(0x00000002)} 19:29:39.403
     sto:      {DRIVERSTORE IMPORT END} 19:29:39.403
     sto:      {DRIVERSTORE IMPORT END: exit(0x00000000)} 19:29:39.403
     sto:      Rolled back driver package import.
!!!  sto:      Failed to import driver package into Driver Store. Error = 0x00000002

bcmaze said:
I guess next will be "wsynth3dvsc.inf_amd64_389b9d81ce9991d7"?

Of course!

[SOLVED] Windows (Cumulative) Updates failing to install [Server 2016]

Active member

Attachments

Administrator

Active member

Administrator

Active member

Administrator

Active member

Administrator

Attachments

Active member

Administrator

Active member

Administrator

Active member

Attachments

Administrator

Attachments

Active member

Attachments

Administrator

Attachments

Active member

Attachments

Administrator

Attachments

Active member

Attachments

Administrator

Attachments