richmolasses Member Joined Feb 29, 2024 Posts 24 Feb 29, 2024 #1 When attempting to install KB5034768, KB5034683, KB5034127 on a Windows Server 2019 VM I am receiving an update error 0x800703f1. Currently, it is only affecting two of our VM's within our environment. Other Servers have managed to install these updates OK. Noted [HRESULT = 0x800703f1 - ERROR_BADDB] is shown a number of times within the CBS log file. I have tried the following: SFC SFC /Scannow Result: Windows Resource Protection did not find any integrity violations. DISM DISM /Online /Cleanup-Image /RestoreHealth No component store corruption detected. Components Scanner ==== Repair Log ==== No possible repairs ==== Warnings ==== None Any assistance would be appreciated, I have uploaded the CBS zip and ComponentsScanner log. Attachments CBS VM1.zip 12.9 MB · Views: 3 ComponentsScannerVM1.txt 653 bytes · Views: 3
When attempting to install KB5034768, KB5034683, KB5034127 on a Windows Server 2019 VM I am receiving an update error 0x800703f1. Currently, it is only affecting two of our VM's within our environment. Other Servers have managed to install these updates OK. Noted [HRESULT = 0x800703f1 - ERROR_BADDB] is shown a number of times within the CBS log file. I have tried the following: SFC SFC /Scannow Result: Windows Resource Protection did not find any integrity violations. DISM DISM /Online /Cleanup-Image /RestoreHealth No component store corruption detected. Components Scanner ==== Repair Log ==== No possible repairs ==== Warnings ==== None Any assistance would be appreciated, I have uploaded the CBS zip and ComponentsScanner log.
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 1, 2024 #2 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. Please attach it to your next post. The file may sometimes be too large to upload here, if so please upload to a file sharing service. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Please post me the link to the file
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. Please attach it to your next post. The file may sometimes be too large to upload here, if so please upload to a file sharing service. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Please post me the link to the file
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 3, 2024 #3 Hi Gary, Thanks for your response. Please see the attached DRIVERS file. Attachments DRIVERS.zip 635.7 KB · Views: 3
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 3, 2024 #4 Warning: this fix is specific to the user in this thread, and no one else should follow these instructions. 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. You should now have the DRIVERS file that we will be using to replace your current one. Next ... Navigate to C:\Windows\System32\config Right-click on the current DRIVERS file and select Rename. Rename it to DRIVERS.old 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 Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Attachments DRIVERS.zip 635.8 KB · Views: 4
Warning: this fix is specific to the user in this thread, and no one else should follow these instructions. 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. You should now have the DRIVERS file that we will be using to replace your current one. Next ... Navigate to C:\Windows\System32\config Right-click on the current DRIVERS file and select Rename. Rename it to DRIVERS.old 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 Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 3, 2024 #5 I have completed the driver file swap and attached the cbs.log after running the Dism command. Attachments CBS.log 138.1 KB · Views: 2
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 3, 2024 #6 Latest CBS.log is not flagging anything that I can see, so please try updating your machine If successful please let me know. If not, please post me the CBS.log created after your update attempt. PS .... it's almost 11pm here, so it will probably be tomorrow morning (my time GMT) before I see your reply.
Latest CBS.log is not flagging anything that I can see, so please try updating your machine If successful please let me know. If not, please post me the CBS.log created after your update attempt. PS .... it's almost 11pm here, so it will probably be tomorrow morning (my time GMT) before I see your reply.
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 3, 2024 #7 Failure to install on the updates again, appears to be the same [HRESULT = 0x800703f1 - ERROR_BADDB] error. CBS.log file attached. Attachments CBS.log 1.4 MB · Views: 2
Failure to install on the updates again, appears to be the same [HRESULT = 0x800703f1 - ERROR_BADDB] error. CBS.log file attached.
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 4, 2024 #8 Please go to C:\Windows\INF Copy the file setupAPI.dev.log Please attach it to your reply post
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 4, 2024 #9 Hi Gary, setupAPI.dev.log file attached. Attachments setupapi.dev.log 2.6 MB · Views: 3
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 4, 2024 #10 Download SFCFix.exe and save it to your desktop. Download the attachment SFCFixScript.txt and also save it on your desktop. Save any work you have open, and close all programs. 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 Open the file, then copy and paste its content in your next reply. Attachments SFCFixScript.txt 23 bytes · Views: 8
Download SFCFix.exe and save it to your desktop. Download the attachment SFCFixScript.txt and also save it on your desktop. Save any work you have open, and close all programs. 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 Open the file, then copy and paste its content in your next reply.
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 4, 2024 #11 Script ran successfully, output below: ****************************** SFCFix version 3.0.2.1 by niemiro. Start time: 2024-03-05 12:24:33.733 Microsoft Windows Server 10 Build 17763 - amd64 Using .txt script file at C:\Users\User\Desktop\SFCFixScript.txt [0] FileScan:: [0: 2] C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\oposdrv.inf Expected: UNKNOWN Found: uEAix0km7JhbhxXXwfCZkfV2jPLLLU1OkCSB2X0bYSI= Expected: 10.0.17763.348 Found: Version number not available. Failed to trace component amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d with return code -3. [C:\Windows\INF\oposdrv.inf] [1: 1] C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf File is untraceable. Found: NNy8mUknVenTfBSiNFcDf6TqSp7+GKmmxhefaRxDMf0= Version number not available. Trace not available. [2: 1] C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf File is untraceable. Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE= Version number not available. Trace not available. [3: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5122.1.11\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf File is untraceable. Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE= Version number not available. Trace not available. [4: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5122.1.11\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf File is untraceable. Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg= Version number not available. Trace not available. [5: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5329.1.4\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf File is untraceable. Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE= Version number not available. Trace not available. [6: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5329.1.4\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf File is untraceable. Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg= Version number not available. Trace not available. [7: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5458.1.12\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf File is untraceable. Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE= Version number not available. Trace not available. [8: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5458.1.12\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf File is untraceable. Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg= Version number not available. Trace not available. FileScan:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2024-03-05 12:24:47.130 Script hash: K0AZppfO219+jC0X9fjAFteQoTapGYDzw1myK/7VtLQ= ----------------------EOF-----------------------
Script ran successfully, output below: ****************************** SFCFix version 3.0.2.1 by niemiro. Start time: 2024-03-05 12:24:33.733 Microsoft Windows Server 10 Build 17763 - amd64 Using .txt script file at C:\Users\User\Desktop\SFCFixScript.txt [0] FileScan:: [0: 2] C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\oposdrv.inf Expected: UNKNOWN Found: uEAix0km7JhbhxXXwfCZkfV2jPLLLU1OkCSB2X0bYSI= Expected: 10.0.17763.348 Found: Version number not available. Failed to trace component amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d with return code -3. [C:\Windows\INF\oposdrv.inf] [1: 1] C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf File is untraceable. Found: NNy8mUknVenTfBSiNFcDf6TqSp7+GKmmxhefaRxDMf0= Version number not available. Trace not available. [2: 1] C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf File is untraceable. Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE= Version number not available. Trace not available. [3: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5122.1.11\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf File is untraceable. Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE= Version number not available. Trace not available. [4: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5122.1.11\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf File is untraceable. Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg= Version number not available. Trace not available. [5: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5329.1.4\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf File is untraceable. Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE= Version number not available. Trace not available. [6: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5329.1.4\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf File is untraceable. Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg= Version number not available. Trace not available. [7: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5458.1.12\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf File is untraceable. Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE= Version number not available. Trace not available. [8: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5458.1.12\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf File is untraceable. Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg= Version number not available. Trace not available. FileScan:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2024-03-05 12:24:47.130 Script hash: K0AZppfO219+jC0X9fjAFteQoTapGYDzw1myK/7VtLQ= ----------------------EOF-----------------------
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 5, 2024 #12 WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system. Download the attachment SFCFixScript.txt and save it on your desktop. Save any work you have open, and close all programs. 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 Open the file, then copy and paste its content in your next reply. Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Attachments SFCFixScript.txt 208 bytes · Views: 9
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system. Download the attachment SFCFixScript.txt and save it on your desktop. Save any work you have open, and close all programs. 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 Open the file, then copy and paste its content in your next reply. Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 5, 2024 #13 Fix output below: SFCFix version 3.0.2.1 by niemiro. Start time: 2024-03-06 13:25:56.564 Microsoft Windows Server 10 Build 17763 - amd64 Using .txt script file at C:\Users\User\Desktop\SFCFixScript.txt [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\System32\DriverStore\FileRepository Successfully created directory tree \\?\C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742. Successfully copied file C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf to C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.inf. Successfully restored ownership for C:\Windows\System32\DriverStore\FileRepository Successfully restored permissions on C:\Windows\System32\DriverStore\FileRepository PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 1 datablocks. Finish time: 2024-03-06 13:25:57.457 Script hash: MBpjHPaqjH7sTPA1wWdLIDv2sKGIaWcEDfTAbWjMEpE= ----------------------EOF----------------------- cbs.log file attached. Attachments CBS.log 264.9 KB · Views: 3
Fix output below: SFCFix version 3.0.2.1 by niemiro. Start time: 2024-03-06 13:25:56.564 Microsoft Windows Server 10 Build 17763 - amd64 Using .txt script file at C:\Users\User\Desktop\SFCFixScript.txt [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\System32\DriverStore\FileRepository Successfully created directory tree \\?\C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742. Successfully copied file C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf to C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.inf. Successfully restored ownership for C:\Windows\System32\DriverStore\FileRepository Successfully restored permissions on C:\Windows\System32\DriverStore\FileRepository PowerCopy:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 1 datablocks. Finish time: 2024-03-06 13:25:57.457 Script hash: MBpjHPaqjH7sTPA1wWdLIDv2sKGIaWcEDfTAbWjMEpE= ----------------------EOF----------------------- cbs.log file attached.
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 6, 2024 #14 Log looks good. Please try updating your machine. If successful please let me know. If not, please post me the CBS.log created after your update attempt.
Log looks good. Please try updating your machine. If successful please let me know. If not, please post me the CBS.log created after your update attempt.
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 6, 2024 #15 Still an error on the last update attempt, file attached. Attachments CBS.log 1.1 MB · Views: 3
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 6, 2024 #16 Can you please send me a new copy of your DRIVERS hive file .... 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. Please attach it to your next post. The file may sometimes be too large to upload here, if so please upload to a file sharing service. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Please post me the link to the file
Can you please send me a new copy of your DRIVERS hive file .... 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. Please attach it to your next post. The file may sometimes be too large to upload here, if so please upload to a file sharing service. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Please post me the link to the file
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 6, 2024 #17 Gary R said: Can you please send me a new copy of your DRIVERS hive file .... 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. Please attach it to your next post. The file may sometimes be too large to upload here, if so please upload to a file sharing service. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Please post me the link to the file Click to expand... New drivers DRIVERS.ZIP attached. Attachments DRIVERS.zip 635.7 KB · Views: 1
Gary R said: Can you please send me a new copy of your DRIVERS hive file .... 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. Please attach it to your next post. The file may sometimes be too large to upload here, if so please upload to a file sharing service. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Please post me the link to the file Click to expand... New drivers DRIVERS.ZIP attached.
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 6, 2024 #18 Warning: this fix is specific to the user in this thread, and no one else should follow these instructions. 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. You should now have the DRIVERS file that we will be using to replace your current one. Next ... Navigate to C:\Windows\System32\config Right-click on the current DRIVERS file and select Rename. Rename it to DRIVERS.old 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 Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Attachments DRIVERS.zip 635.8 KB · Views: 1
Warning: this fix is specific to the user in this thread, and no one else should follow these instructions. 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. You should now have the DRIVERS file that we will be using to replace your current one. Next ... Navigate to C:\Windows\System32\config Right-click on the current DRIVERS file and select Rename. Rename it to DRIVERS.old 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 Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 6, 2024 #19 Gary R said: Warning: this fix is specific to the user in this thread, and no one else should follow these instructions. 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. You should now have the DRIVERS file that we will be using to replace your current one. Next ... Navigate to C:\Windows\System32\config Right-click on the current DRIVERS file and select Rename. Rename it to DRIVERS.old 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 Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Click to expand... Completed as per the above, CBS.log attached. Attachments CBS.log 138.1 KB · Views: 1
Gary R said: Warning: this fix is specific to the user in this thread, and no one else should follow these instructions. 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. You should now have the DRIVERS file that we will be using to replace your current one. Next ... Navigate to C:\Windows\System32\config Right-click on the current DRIVERS file and select Rename. Rename it to DRIVERS.old 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 Next ... Click Search button and type Command Prompt From the results, right click on the Command Prompt icon, and select Run as administrator A Command Window will open. Copy paste the command below into it, then press Enter Dism /Online /Cleanup-Image /RestoreHealth Once DISM has finished running ... Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply. If the file is too large, upload it to a file sharing service, and post me the link. Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline Click to expand... Completed as per the above, CBS.log attached.
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 7, 2024 #20 Latest CBS.log looks clean, so please try updating your computer again. If successful please let me know. If not, please post the CBS.log created after your update attempt.
Latest CBS.log looks clean, so please try updating your computer again. If successful please let me know. If not, please post the CBS.log created after your update attempt.