[SOLVED] Server 2019 - Can't do updates - Error: 1009 The configuration registry database is corrupt

guyonphone · May 12, 2023

Hi,

I am running server 2019 Hyper-v VM.
I am unable to perform windows update "2023-05 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5026362)"
I get error 0x800703f1
I noticed that I was also having some strange networking issues where on this VM only I would have issues where downloads would pause to 0kb/s and then start downloading again after some time.
I attempted to update the Hyper-V Nic Drivers but then got this error:

I did some research and did the 3 DISMs:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

and

SFC /Scannow

They came back clean showing no corruption. However I still get the above even after a reboot.
Did some more research and discovered that I could check %windows%\INF\setupapi.dev.log for additional info.

Code:

>>>  [Device Install (DiShowUpdateDevice) - VMBUS\{F8615163-DF3E-46C5-913F-F2D2F965ED0E}\{1F7B76A1-492A-434C-A4A2-23DDE88B49D5}]
>>>  Section start 2023/05/12 11:27:48.784
      cmd: "C:\Windows\system32\mmc.exe" C:\Windows\system32\devmgmt.msc
     dvi: {DIF_UPDATEDRIVER_UI} 11:27:48.786
     dvi:      Default installer: Enter 11:27:48.797
     dvi:      Default installer: Exit
     dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 11:27:48.801
     ndv: {Update Driver Software Wizard - VMBUS\{F8615163-DF3E-46C5-913F-F2D2F965ED0E}\{1F7B76A1-492A-434C-A4A2-23DDE88B49D5}}
     ndv:      Search options: 0x00000203
     ndv:      Searching currently installed INF
     dvi:      {Build Driver List} 11:27:50.865
     dvi:           Searching for hardware ID(s):
     dvi:                vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}
     dvi:                vmbus\{1f7b76a1-492a-434c-a4a2-23dde88b49d5}
     dvi:           Searching for compatible ID(s):
     dvi:                vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}
!!!  inf:           Error (0x000003f1) searching for 'vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}'.
!!!  inf:           Error 1009: The configuration registry database is corrupt.
!!!  inf:           Error (0x000003f1) searching published INFs.
!!!  inf:           Error 1009: The configuration registry database is corrupt.
!    inf:           InfSearch error
!    inf:           Error 1009: The configuration registry database is corrupt.
     dvi:      {Build Driver List - exit(0x00000000)} 11:27:50.912
     ndv:      Searching default INF path
     dvi:      {Build Driver List} 11:27:50.915
     dvi:           Searching for hardware ID(s):
     dvi:                vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}
     dvi:                vmbus\{1f7b76a1-492a-434c-a4a2-23dde88b49d5}
     dvi:           Searching for compatible ID(s):
     dvi:                vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}
!!!  inf:           Error (0x000003f1) searching for 'vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}'.
!!!  inf:           Error 1009: The configuration registry database is corrupt.
!!!  inf:           Error (0x000003f1) searching published INFs.
!!!  inf:           Error 1009: The configuration registry database is corrupt.
     sig:           {_VERIFY_FILE_SIGNATURE} 11:27:55.950
     sig:                Key      = wnetvsc.inf
     sig:                FilePath = C:\Windows\inf\wnetvsc.inf
     sig:                Success: A valid signature was found in an installed catalog
     sig:                Cat: 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_4899_for_KB5010427~31bf3856ad364e35~amd64~~10.0.1.9.cat'
     sig:           {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 11:27:55.971
     dvi:           Created Driver Node:
     dvi:                HardwareID   - VMBUS\{F8615163-DF3E-46c5-913F-F2D2F965ED0E}
     dvi:                InfName      - C:\Windows\inf\wnetvsc.inf
     dvi:                DevDesc      - Microsoft Hyper-V Network Adapter
     dvi:                Section      - netvsc_Device
     dvi:                Rank         - 0x00ff0000
     dvi:                Signer Score - INBOX
     dvi:                DrvDate      - 06/21/2006
     dvi:                Version      - 10.0.17763.2452
     dvi:      {Build Driver List - exit(0x00000000)} 11:27:56.128
     dvi:      {DIF_SELECTBESTCOMPATDRV} 11:29:23.776
     dvi:           Default installer: Enter 11:29:23.779
     dvi:                {Select Best Driver}
     dvi:                     Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:                     Selected Driver:
     dvi:                          Description - Microsoft Hyper-V Network Adapter
     dvi:                          InfFile     - c:\windows\inf\wnetvsc.inf
     dvi:                          Section     - netvsc_Device
     dvi:                {Select Best Driver - exit(0x00000000)}
     dvi:           Default installer: Exit
     dvi:      {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 11:29:23.791
     sto:      {Setup Import Driver Package: c:\windows\inf\wnetvsc.inf} 11:29:23.816
!    sto:           Unable to determine presence of driver package. Error = 0x000003F1
     inf:           Provider: Microsoft
     inf:           Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318}
     inf:           Driver Version: 06/21/2006,10.0.17763.2452
     sto:           {Copy Driver Package: c:\windows\inf\wnetvsc.inf} 11:29:23.840
     sto:                Driver Package = c:\windows\inf\wnetvsc.inf
     sto:                Flags          = 0x00000007
     sto:                Destination    = C:\Users\<REDACTED>\AppData\Local\Temp\{1d082c88-23ae-5b44-bd03-d86d636aa7f6}
     sto:                Copying driver package files to 'C:\Users\<REDACTED>\AppData\Local\Temp\{1d082c88-23ae-5b44-bd03-d86d636aa7f6}'.
     flq:                Copying 'c:\windows\inf\wnetvsc.inf' to 'C:\Users\<REDACTED>\AppData\Local\Temp\{1d082c88-23ae-5b44-bd03-d86d636aa7f6}\wnetvsc.inf'.
!!!  flq:                Error installing file (0x00000002)
!!!  flq:                Error 2: The system cannot find the file specified.
!    flq:                     SourceFile   - 'c:\windows\inf\netvsc.sys'
!    flq:                     TargetFile   - 'C:\Users\<REDACTED>\AppData\Local\Temp\{1d082c88-23ae-5b44-bd03-d86d636aa7f6}\netvsc.sys'
!!!  cpy:                Failed to copy file 'c:\windows\inf\netvsc.sys' to 'C:\Users\<REDACTED>\AppData\Local\Temp\{1d082c88-23ae-5b44-bd03-d86d636aa7f6}\netvsc.sys'. Error = 0x00000002
!!!  flq:                SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT.
!!!  flq:                Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
!!!  flq:                Failed to commit copy queue. Error = 0x000003e3
!!!  flq:                FileQueueCommit aborting
!!!  flq:                Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
!!!  sto:                Failed to copy driver package to 'C:\Users\<REDACTED>\AppData\Local\Temp\{1d082c88-23ae-5b44-bd03-d86d636aa7f6}'. Error = 0x00000002
     sto:           {Copy Driver Package: exit(0x00000002)} 11:29:23.889
     sto:      {Setup Import Driver Package - exit (0x00000002)} 11:29:23.893
!!!  ndv:      Driver package import failed for device.
!!!  ndv:      Error 2: The system cannot find the file specified.
     dvi:      {DIF_UPDATEDRIVER_UI} 11:38:40.180
     dvi:           Default installer: Enter 11:38:40.192
     dvi:           Default installer: Exit
     dvi:      {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 11:38:40.195
     ndv:      {Update Driver Software Wizard - VMBUS\{F8615163-DF3E-46C5-913F-F2D2F965ED0E}\{1F7B76A1-492A-434C-A4A2-23DDE88B49D5}}
     ndv:           Search options: 0x00000203
     ndv:           Searching currently installed INF
     dvi:           {Build Driver List} 11:38:42.239
     dvi:                Searching for hardware ID(s):
     dvi:                     vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}
     dvi:                     vmbus\{1f7b76a1-492a-434c-a4a2-23dde88b49d5}
     dvi:                Searching for compatible ID(s):
     dvi:                     vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}
!!!  inf:                Error (0x000003f1) searching for 'vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}'.
!!!  inf:                Error 1009: The configuration registry database is corrupt.
!!!  inf:                Error (0x000003f1) searching published INFs.
!!!  inf:                Error 1009: The configuration registry database is corrupt.
!    inf:                InfSearch error
!    inf:                Error 1009: The configuration registry database is corrupt.
     dvi:           {Build Driver List - exit(0x00000000)} 11:38:42.319
     ndv:           Searching default INF path
     dvi:           {Build Driver List} 11:38:42.324
     dvi:                Searching for hardware ID(s):
     dvi:                     vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}
     dvi:                     vmbus\{1f7b76a1-492a-434c-a4a2-23dde88b49d5}
     dvi:                Searching for compatible ID(s):
     dvi:                     vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}
!!!  inf:                Error (0x000003f1) searching for 'vmbus\{f8615163-df3e-46c5-913f-f2d2f965ed0e}'.
!!!  inf:                Error 1009: The configuration registry database is corrupt.
!!!  inf:                Error (0x000003f1) searching published INFs.
!!!  inf:                Error 1009: The configuration registry database is corrupt.
     sig:                {_VERIFY_FILE_SIGNATURE} 11:38:50.455
     sig:                     Key      = wnetvsc.inf
     sig:                     FilePath = C:\Windows\inf\wnetvsc.inf
     sig:                     Success: A valid signature was found in an installed catalog
     sig:                     Cat: 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_4899_for_KB5010427~31bf3856ad364e35~amd64~~10.0.1.9.cat'
     sig:                {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 11:38:50.532
     dvi:                Created Driver Node:
     dvi:                     HardwareID   - VMBUS\{F8615163-DF3E-46c5-913F-F2D2F965ED0E}
     dvi:                     InfName      - C:\Windows\inf\wnetvsc.inf
     dvi:                     DevDesc      - Microsoft Hyper-V Network Adapter
     dvi:                     Section      - netvsc_Device
     dvi:                     Rank         - 0x00ff0000
     dvi:                     Signer Score - INBOX
     dvi:                     DrvDate      - 06/21/2006
     dvi:                     Version      - 10.0.17763.2452
     dvi:           {Build Driver List - exit(0x00000000)} 11:38:50.766
     dvi:           {DIF_SELECTBESTCOMPATDRV} 11:38:59.124
     dvi:                Default installer: Enter 11:38:59.127
     dvi:                     {Select Best Driver}
     dvi:                          Class GUID of device changed to: {4d36e972-e325-11ce-bfc1-08002be10318}.
     dvi:                          Selected Driver:
     dvi:                               Description - Microsoft Hyper-V Network Adapter
     dvi:                               InfFile     - c:\windows\inf\wnetvsc.inf
     dvi:                               Section     - netvsc_Device
     dvi:                     {Select Best Driver - exit(0x00000000)}
     dvi:                Default installer: Exit
     dvi:           {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 11:38:59.141
     sto:           {Setup Import Driver Package: c:\windows\inf\wnetvsc.inf} 11:38:59.166
!    sto:                Unable to determine presence of driver package. Error = 0x000003F1
     inf:                Provider: Microsoft
     inf:                Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318}
     inf:                Driver Version: 06/21/2006,10.0.17763.2452
     sto:                {Copy Driver Package: c:\windows\inf\wnetvsc.inf} 11:38:59.186
     sto:                     Driver Package = c:\windows\inf\wnetvsc.inf
     sto:                     Flags          = 0x00000007
     sto:                     Destination    = C:\Users\<REDACTED>\AppData\Local\Temp\{8d9856cf-15da-1a40-a1d0-04000feb7a96}
     sto:                     Copying driver package files to 'C:\Users\<REDACTED>\AppData\Local\Temp\{8d9856cf-15da-1a40-a1d0-04000feb7a96}'.
     flq:                     Copying 'c:\windows\inf\wnetvsc.inf' to 'C:\Users\<REDACTED>\AppData\Local\Temp\{8d9856cf-15da-1a40-a1d0-04000feb7a96}\wnetvsc.inf'.
!!!  flq:                     Error installing file (0x00000002)
!!!  flq:                     Error 2: The system cannot find the file specified.
!    flq:                          SourceFile   - 'c:\windows\inf\netvsc.sys'
!    flq:                          TargetFile   - 'C:\Users\<REDACTED>\AppData\Local\Temp\{8d9856cf-15da-1a40-a1d0-04000feb7a96}\netvsc.sys'
!!!  cpy:                     Failed to copy file 'c:\windows\inf\netvsc.sys' to 'C:\Users\<REDACTED>\AppData\Local\Temp\{8d9856cf-15da-1a40-a1d0-04000feb7a96}\netvsc.sys'. Error = 0x00000002
!!!  flq:                     SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT.
!!!  flq:                     Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
!!!  flq:                     Failed to commit copy queue. Error = 0x000003e3
!!!  flq:                     FileQueueCommit aborting
!!!  flq:                     Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
!!!  sto:                     Failed to copy driver package to 'C:\Users\<REDACTED>\AppData\Local\Temp\{8d9856cf-15da-1a40-a1d0-04000feb7a96}'. Error = 0x00000002
     sto:                {Copy Driver Package: exit(0x00000002)} 11:38:59.291
     sto:           {Setup Import Driver Package - exit (0x00000002)} 11:38:59.295
!!!  ndv:           Driver package import failed for device.
!!!  ndv:           Error 2: The system cannot find the file specified.
     ndv:      {Update Driver Software Wizard exit(00000002)}
<<<  Section end 2023/05/12 11:57:41.048
<<<  [Exit status: FAILURE(0x00000002)]

Notice I am getting: Error 1009: The configuration registry database is corrupt.

I then found this: DISM Error 1009 - The configuration registry database is corrupt

Tried running the command in recovery shell:

DISM /Image:C:\ /ScratchDir:C:\Scratch /Cleanup-Image /RevertPendingActions

Got the following:

I feel as though I have exhausted my knowledge of how to resolve this issue, I believe I have a corrupt Hive and I would be interested in getting some further advice. Thanks in Advance!
Please see attached files

guyonphone · May 12, 2023

I just found this:

Finally, an *actual* solution to 0x800703f1 and 0xca00a000 errors in Windows Update besides reinstall

Thoughts?, looks like the author of that post actually links back to sysnative.com

all roads lead back here :)

guyonphone · May 13, 2023

Hi back with an update,

I got impatient, (this is not criticism I totally get support here is free and generously provided by volunteers!) and decided to try the procedure I linked above. Well... it didn't totally fix my problems BUT!, we have made progress! Now when I try to update the the hyper-v driver, I no longer get the error "Error: 1009 The configuration registry database is corrupt" instead I get the following:

Code:

>>>  [Stage Driver Updates]
>>>  Section start 2023/05/13 21:31:34.960
      cmd: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.4121_none_5703f42b990865ed\TiWorker.exe -Embedding
     sto: Image State        = Specialized
     sto: Image Architecture = amd64
     sto: Image OS Version   = 10.0.17763
     sto: Image Product Type = 3
     sto: Driver Updates     = 85
     sto: {Stage Driver Package: C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\oposdrv.inf} 21:31:55.466
!    sto:      Unable to determine presence of driver package 'oposdrv.inf'. Error = 0x000003F1
     inf:      {Query Configurability: C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\oposdrv.inf} 21:31:55.482
     inf:           Driver package uses WDF.
     inf:           Driver package 'oposdrv.inf' is configurable.
     inf:      {Query Configurability: exit(0x00000000)} 21:31:55.482
     sig:      Signer Score  = 0x0D000003 (Inbox)
     sto:      {DRIVERSTORE IMPORT BEGIN} 21:31:55.482
     sto:      {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 21:31:55.482
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\oposdrv.dll' to 'C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.dll'.
     flq:      Hardlinking 'C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\oposdrv.inf' to 'C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.inf'.
     idb:      {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.inf} 21:31:55.497
!!!  idb:           Failed to create driver package object 'oposdrv.inf_amd64_313106b94d0b5742' in DRIVERS database node. Error = 0x000003F1
!!!  idb:           Failed to register driver package 'C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.inf'. Error = 0x000003F1
     idb:      {Register Driver Package: exit(0x000003f1)} 21:31:55.497
     sto:      {DRIVERSTORE IMPORT END} 21:31:55.497
     sto:      {DRIVERSTORE IMPORT END: exit(0x00000000)} 21:31:55.497
     sto:      Rolled back driver package import.
!!!  sto:      Failed to import driver package into Driver Store. Error = 0x000003F1
     sto: {Stage Driver Package: exit(0x000003f1)} 21:31:55.497
!!!  sto: Failed to stage all driver updates. Error = 0x000003F1
!!!  sto: Failed to determine status of driver update 'C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\oposdrv.inf'. Error = 0x000003F1
!    sto: Could not unstage all driver updates. Error = 0x000003F1
<<<  Section end 2023/05/13 21:31:55.497
<<<  [Exit status: FAILURE(0x000003f1)]

Luckily, I found another post of someone who resolved this issue here:

[SOLVED] - Windows Server 2019 Standard VM - KB5010351 Won't Install - Found Driver Issue

I also went into safemode and deleted my softwaredistribution folder and renamed my catroot2 folder to catroot2.old, which I know I should probably have done before all of this, so yeah...

So I am now going to follow this procedure of replacing the DRIVERS file with that of a good VM! Wish me luck!

guyonphone · May 15, 2023

Hello,

The above process didn't seem to work originally, but this morning when I signed onto the machine it was asking to reboot for a pending update. I rebooted and it sat for a long time at "updating your computer 100%" and then finally it booted! and I have the following:

So I think either by luck, or hardwork I have finagled the machine into installing updates. Just for additional info I am going to re-add the CBS.log and rerun the components scanner. I still however cannot seem to update my Hyper-V Nic driver:

I am also adding my setupapi.dev.log for this please see attached.

guyonphone · May 15, 2023

Uploading most recent component scan:
At this point I think all I need help with is verification that my windows updates are fixed, and help with getting that dang driver updated which I just am now at a loss for as the logs aren't showing any errors!

guyonphone · May 18, 2023

I performed the following 6 commands, which the last 2 I had not tried before.

Dism.exe /online /Cleanup-Image /checkhealth
Dism.exe /online /Cleanup-Image /scanhealth
Dism.exe /online /Cleanup-Image /Restorehealth
sfc /scannow
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
Dism.exe /Online /Cleanup-Image /StartComponentCleanup

Unfortunately I am still running into the issue where when windows checks windows update for the Hyper-V Nic driver it just says file not found. Otherwise it looks like everything came back clean.

Maxstar · May 18, 2023

Hi and welcome to Sysnative,

Please provide a copy of your DRIVERS hive and a new copy of the setupapi.dev.log file as well as the result of SFCFIx.

Step 1.Upload your DRIVERS Hive

Navigate to C:\Windows\System32\config and locate the DRIVERS file.
Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named DRIVERS.ZIP on your desktop.
If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

Step 2.Upload a new copy of the setupapi.dev.log

Open Windows Explorer and browse to the C:\Windows\INF folder.
Right-click on the file setupapi.dev.log and choose Send to > Compressed (zipped) folder.
Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
Click on the Yes button here.

Attach the file setupapi.dev.zip in your next reply.

Step 3. Download

SFCFix and save it to your desktop.

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.

guyonphone · May 18, 2023

Hello! Thanks so much for your help!

attached are the requested.

Maxstar · May 18, 2023

Please run step 3 again with the attached file.

guyonphone · May 18, 2023

Please see attached.

guyonphone · May 18, 2023

I wanted to add, that if I need to copy files from another OS, I do have another functioning Server 2019 VM which does not have these issues.

Maxstar · May 18, 2023

The DRIVERS hive you have provided is damaged beyond repair, it is just 8 kB and - thus empty.. Do you have backups of this server?

guyonphone · May 18, 2023

I have the original DRIVERS hive, the one that I provided was one that I copied from an alternate server, when I copy it, it isn't 8k, it is like 3MB, something I am doing after copying it has reduced it's size. Please see the original drivers hive attached. To answer your question, yes, I also have backups if necessary.

Maxstar · May 19, 2023

Hi,

This hive is also corrupted, but here's the fixed hive.

Replace Drivers Hive Manually

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.

Download DRIVERS.ZIP and save to your desktop.
Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
Now we have the DRIVERS file that we will be using to replace your current one.
Navigate to C:\Windows\System32\config
Right-click on the current DRIVERS file and select rename. Rename it to DRIVERS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again.
Take the file from the Drivers folder on your desktop and paste it into C:\Windows\System32\config

guyonphone · May 19, 2023

That's It! You fixed it! I'm not getting the error! I really appreciate your help!!!
Do you mind if I ask how you repaired the corruption on the DRIVER hive?
Should I run any further DISM commands?

Thank You, Thank You, Thank You!!!

Maxstar · May 19, 2023

Hi,

You're welcome and glad we could help to resolve your problem.

guyonphone said:
Do you mind if I ask how you repaired the corruption on the DRIVER hive?

The DRIVERS hive was corrupted, because the primary and secondary sequence numbers dit not match, and this caused the I/O issue as you pointed out in the first post.

Rich (BB code):

     flq:                     Copying 'c:\windows\inf\wnetvsc.inf' to 'C:\Users\<REDACTED>\AppData\Local\Temp\{8d9856cf-15da-1a40-a1d0-04000feb7a96}\wnetvsc.inf'.
!!!  flq:                     Error installing file (0x00000002)
!!!  flq:                     Error 2: The system cannot find the file specified.
!    flq:                          SourceFile   - 'c:\windows\inf\netvsc.sys'
!    flq:                          TargetFile   - 'C:\Users\<REDACTED>\AppData\Local\Temp\{8d9856cf-15da-1a40-a1d0-04000feb7a96}\netvsc.sys'
!!!  cpy:                     Failed to copy file 'c:\windows\inf\netvsc.sys' to 'C:\Users\<REDACTED>\AppData\Local\Temp\{8d9856cf-15da-1a40-a1d0-04000feb7a96}\netvsc.sys'. Error = 0x00000002
!!!  flq:                     SPFQNOTIFY_COPYERROR: returned SPFQOPERATION_ABORT.
!!!  flq:                     Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
!!!  flq:                     Failed to commit copy queue. Error = 0x000003e3
!!!  flq:                     FileQueueCommit aborting
!!!  flq:                     Error 995: The I/O operation has been aborted because of either a thread exit or an application request.
!!!  sto:                     Failed to copy driver package to 'C:\Users\<REDACTED>\AppData\Local\Temp\{8d9856cf-15da-1a40-a1d0-04000feb7a96}'. Error = 0x00000002

guyonphone said:
Should I run any further DISM commands?

You can always run the following DISM command. If it fails attach a new copy of the CBS log.

Code:

DISM /online /cleanup-image /RestoreHealth

guyonphone · May 19, 2023

Everything came back clean! I really appreciate your help, I found some articles around using a HEX editor to fix registry corruption which I am going to look more into as I would like to learn more. Marking the issue as solved Thanks Again!

Maxstar · May 20, 2023

Hi,

You're welcome. Glad to hear there are no remaining issues...

[SOLVED] Server 2019 - Can't do updates - Error: 1009 The configuration registry database is corrupt

Member

Attachments

Member

Member

Member

Attachments

Member

Attachments

Member

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Member

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Moderator, Windows Update Expert, Security Analyst

Member

Moderator, Windows Update Expert, Security Analyst