A Windows Server 2019 (1809) reported an error when installing patch update, 0x800703f1

yuyi

Member
Joined
May 5, 2022
Posts
10
如何操作来解决这个问题
 

Attachments

  • ab92c7bbac0e08d14e9f1efff6ade54.png
    ab92c7bbac0e08d14e9f1efff6ade54.png
    169.3 KB · Views: 3
Rich (BB code):
2022-04-28 13:57:25, Info                  CBS    Perf: Doqe: Staging started.
2022-04-28 13:57:25, Info                  CBS    Doqe: [Forward] Staging driver updates, Count 81
2022-04-28 13:57:26, Info                  CBS            STAGE index: 63, phase: 1, result 1009, inf: oposdrv.inf
2022-04-28 13:57:26, Info                  CBS    Doqe: Recording result: 0x800703f1, for Inf: oposdrv.inf
2022-04-28 13:57:26, Info                  CBS    DriverUpdateStageUpdates failed [HRESULT = 0x800703f1 - ERROR_BADDB]
2022-04-28 13:57:26, Error                 CBS    Doqe: Failed staging driver updates [HRESULT = 0x800703f1 - ERROR_BADDB]

Could you please provide the following log file: %systemroot%\Inf\setupapi.dev.log.
 
Thanks, could you please provide your DRIVERS hive using the following instructions:

Upload Drivers Hive
  1. Navigate to C:\Windows\System32\config
  2. 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.
  3. Right-click on your Desktop and select paste
  4. Right-click on the DRIVERS file on your Desktop and select Send To -> Compressed (zipped) Folder
  5. 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.
 
Thanks, could you please create a backup of your system and then replace your current DRIVERS hive with the one attached. Afterwards, please attempt to update again.
 

Attachments

Okay, could you please provide the CBS log? You'll need to do that for each time the update fails. It isn't any good just simply stating that it didn't work.
 
Rich (BB code):
2022-05-19 08:48:45, Info                  CBS    Doqe: [Forward] Installing driver updates, Count 81
2022-05-19 08:48:45, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2022-05-19 08:48:45, Info                  CBS    Doqe: Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2022-05-19 08:48:45, Info                  CBS    Perf: Doqe: Install ended.
2022-05-19 08:48:45, Info                  CBS    Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2022-05-19 08:48:45, Error                 CBS    Startup: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2022-05-19 08:48:45, Info                  CBS    Startup: Rolling back KTM, because drivers failed.

It seems like there is going to be driver package corruption, could you please provide your setupapi.dev.log as you did before?
 
I looked at the log. It didn't update anything. It seems to be at a standstill
 
Rich (BB code):
[Boot Session: 2022/05/19 08:48:16.500]

>>>  [Install Driver Updates]
>>>  Section start 2022/05/19 08:48:45.700
      cmd: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.2744_none_56c4cd13993792d6\TiWorker.exe -Embedding
     sto: Image State        = Specialized
     sto: Image Architecture = amd64
     sto: Transaction        = CbsDriversAndPrimitives
     sto: Driver Updates     = 81
!    inf: Unable to load INF: 'C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.inf'(00000003)
!    inf: Error 3: The system cannot find the path specified.
!!!  inf: Invalid INF 'C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.inf', parsing error on line 0. Code = 1002
!!!  sto: Failed to get version info for driver update 'C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.inf'. Error = 0x00000003
<<<  Section end 2022/05/19 08:48:45.950
<<<  [Exit status: FAILURE(0x00000003)]

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.

Afterwards, please try and update again. If it fails, then please provide the latest CBS log along with the setupapi.dev.log.
 

Attachments

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

Back
Top