Windows Server 2019 - Windows Updates get to 8% and then rollback

Rich (BB code):
[0: 3] C:\Windows\WinSxS\amd64_dual_usbaudio2.inf_31bf3856ad364e35_10.0.17763.592_none_d128a5b61462af61\usbaudio2.inf
 Expected: UNKNOWN Found: BrvI9njWgMOSdjaTskRUOH2PEHlnfXk/CN5Z1rFGR2I=
 Expected: 10.0.17763.592 Found: Version number not available.
Failed to trace component amd64_dual_usbaudio2.inf_31bf3856ad364e35_10.0.17763.592_none_d128a5b61462af61 with return code -3.

 [C:\Windows\INF\usbaudio2.inf]
 [C:\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.inf]

Rich (BB code):
[17: 1] C:\Windows\WinSxS\amd64_dual_usbaudio2.inf_31bf3856ad364e35_10.0.17763.592_none_d128a5b61462af61\usbaudio2.inf
 Expected: UNKNOWN Found: BrvI9njWgMOSdjaTskRUOH2PEHlnfXk/CN5Z1rFGR2I=
 Expected: 10.0.17763.592 Found: Version number not available.
Successfully traced component amd64_dual_usbaudio2.inf_31bf3856ad364e35_10.0.17763.592_none_d128a5b61462af61.
Package_600_for_KB4512578~31bf3856ad364e35~amd64~~10.0.1.5.4512578-772_neutral2

Let's repair the hardlinks for the above component. It should be hardlinked to the Driver Store copy and your Inf folder.

SFCFixScript.txt

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.[/list]
 

Attachments

Okay, let's try the same but using fsutil instead. Could you please open an elevated command prompt and then enter the following commands:

Rich (BB code):
fsutil hardlink create C:\Windows\INF\usbaudio2.inf C:\Windows\WinSxS\amd64_dual_usbaudio2.inf_31bf3856ad364e35_10.0.17763.592_none_d128a5b61462af61\usbaudio2.inf

fsutil hardlink create C:\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.inf C:\Windows\WinSxS\amd64_dual_usbaudio2.inf_31bf3856ad364e35_10.0.17763.592_none_d128a5b61462af61\usbaudio2.inf
 
Yes I'm getting the same issue trying with those commands too.

Elevated command prompt

Error: Access is denied.
 
Could you please boot into Safe Mode and then run the same commands from there?
 
I've ran cmd as the system account using psexec and the first command worked.

Now if I run fsutil.exe hardlink list C:\Windows\INF\usbaudio2.inf I see

\Windows\INF\usbaudio2.inf
\Windows\WinSxS\amd64_dual_usbaudio2.inf_31bf3856ad364e35_10.0.17763.592_none_d128a5b61462af61\usbaudio2.inf

Running the second command says
Error: Cannot create a file when that file already exists.

Do you want me to try installing the CU again?
 
Rich (BB code):
fsutil hardlink list C:\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.inf

Could you please post the output for the above? If it's similar to the Inf directory output then please run SFC using sfc /scannow and then post the CBS log.
 
No it's not quite the same, only lists one line

\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.inf

I've tried running the command in safe mode now and they also give error access is denied.
 
Last edited:
The following two scripts should work, I've just tried them on my virtual machine. Please run the Delete script first followed by the Hardlink script. The file should automatically be copied from the WinSxS folder to your DriverStore folder. Please ensure that you create a suitable backup beforehand.
 

Attachments

Output from the scripts

sfcfix.zip (1.38KB) - SendSpace.com


Results of sfc /scanow

Code:
C:\Temp>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
 
It seems like you got the access denied error on the creation of the hardlink for some reason? Could you please either use psexec as you did before or try using Safe Mode with the following command:

Rich (BB code):
fsutil hardlink create C:\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.inf C:\Windows\WinSxS\amd64_dual_usbaudio2.inf_31bf3856ad364e35_10.0.17763.592_none_d128a5b61462af61\usbaudio2.inf
 
Running the command with psexec -s allows the hardlink to be added. I've attached the output along with the logs from an CU install attempt.

files.zip (166.30KB) - SendSpace.com

tsprint.inf is also being mentioned in the log, I think you pointed that out earlier. Will that also be causing a similar issue to usbaudio2.inf ?
 
Will that also be causing a similar issue to usbaudio2.inf ?
I think it's similar, although, I tend to focus on one particular error with driver store issues because often fixing the first issue leads to the other issues getting resolved automatically.

Rich (BB code):
     sto: {Unstage Driver Package: C:\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.inf} 16:17:11.231
     sto:      {DRIVERSTORE DELETE BEGIN} 16:17:11.231
     sto:      {DRIVERSTORE DELETE BEGIN: exit(0x00000000)} 16:17:11.231
     idb:      {Unregister Driver Package: C:\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.inf} 16:17:11.231
!!!  idb:           Failed to open driver INF file object 'usbaudio2.inf'. Error = 0x00000002
!!!  idb:           Failed to unregister driver package 'C:\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.inf'. Error = 0x00000002
     idb:      {Unregister Driver Package: exit(0x00000002)} 16:17:11.247
     sto:      {DRIVERSTORE DELETE END} 16:17:11.247
     sto:      {DRIVERSTORE DELETE END: exit(0x00000000)} 16:17:11.247
!!!  sto:      Failed to delete driver package from Driver Store. Error = 0x00000002
     sto: {Unstage Driver Package: exit(0x00000002)} 16:17:11.247

It appears to be having trouble opening that .inf file for some reason? I'm wondering if there is some kind of permissions issue with that particular file or it's still corrupt?

Could you please run the attached script, it will simply copy the .inf file to a .zip folder on your desktop called usbaudio2.zip. Please attach the .zip to your next post.
 

Attachments

The inf file itself looks perfectly fine. I'm leaning towards some kind of odd permissions issue with that file or folder.

Could you please run the attached SFCFix script and then post the output?
 

Attachments

Rich (BB code):
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-03-17 18:13:24.307
Microsoft Windows Server 10 Build 17763 - amd64
Using .txt script file at C:\Users\Desktop\SFCFixScript.txt [0]

RepairPermissions::
Failed to identify winsxs copy for file C:\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.inf. There may be file or hardlink damage.
Failed to identify winsxs copy for file C:\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.inf. There may be file or hardlink damage.
Failed to identify winsxs copy for file C:\Windows\System32\DriverStore\FileRepository\usbaudio2.inf_amd64_3e0646bbacd51a3d\usbaudio2.sys. There may be file or hardlink damage.
RepairPermissions:: directive failed to complete successfully.

Failed to process all directives successfully.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2022-03-17 18:13:24.401
Script hash: bdjbeZcGpYaJmNXoRJrdc9ObMS91oDwHq13XyUAAF+I=
----------------------EOF-----------------------

Let's try it a different way and repair the permissions from the source directory which should be WinSxS because of the hardlink we created earlier. Could you please try the attached script with SFCFix?
 

Attachments

Hmm, let's delete the entire folder and then replace it again.

SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top