richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 7, 2024 #21 Unsuccessful again - CBS.log attached. Attachments CBS.log 1.8 MB · Views: 1
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 7, 2024 #22 I need to see the following log, created after your update attempt. Please go to C:\Windows\INF Copy the file setupAPI.dev.log Please attach it to your reply post Getting late where I am, so it will be tomorrow before I see your reply.
I need to see the following log, created after your update attempt. Please go to C:\Windows\INF Copy the file setupAPI.dev.log Please attach it to your reply post Getting late where I am, so it will be tomorrow before I see your reply.
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 7, 2024 #23 No worries, thanks for all your help thus far. setupapi.dev.log attached. Attachments setupapi.dev.log 2.8 MB · Views: 3
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 8, 2024 #24 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: 3
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 11, 2024 #25 Hi Gary, sorry for the slow response. Output from the latest SFCFixScript below: SFCFix version 3.0.2.1 by niemiro. Start time: 2024-03-12 08:33:38.463 Microsoft Windows Server 10 Build 17763 - amd64 Using .txt script file at C:\Users\User\Desktop\SFCFix\SFCFixScript.txt 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 1 datablocks. Finish time: 2024-03-12 08:34:02.165 Script hash: K0AZppfO219+jC0X9fjAFteQoTapGYDzw1myK/7VtLQ= ----------------------EOF-----------------------
Hi Gary, sorry for the slow response. Output from the latest SFCFixScript below: SFCFix version 3.0.2.1 by niemiro. Start time: 2024-03-12 08:33:38.463 Microsoft Windows Server 10 Build 17763 - amd64 Using .txt script file at C:\Users\User\Desktop\SFCFix\SFCFixScript.txt 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 1 datablocks. Finish time: 2024-03-12 08:34:02.165 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 11, 2024 #26 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 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. 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 204 bytes · Views: 3
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 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. 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 12, 2024 #27 SFCFix Output ******************** SFCFix version 3.0.2.1 by niemiro. Start time: 2024-03-13 16:01:07.668 Microsoft Windows Server 10 Build 17763 - amd64 Using .txt script file at C:\Users\cycadmin\Desktop\Update Troubleshooting\SFCFix\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\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-13 16:01:08.817 Script hash: 9Mhr0gOxbZV8SPQg9iR2TPwgO/ULSHFduUO25lomgb4= ----------------------EOF----------------------- CBS.log attached. Attachments CBS.log 17.8 KB · Views: 1
SFCFix Output ******************** SFCFix version 3.0.2.1 by niemiro. Start time: 2024-03-13 16:01:07.668 Microsoft Windows Server 10 Build 17763 - amd64 Using .txt script file at C:\Users\cycadmin\Desktop\Update Troubleshooting\SFCFix\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\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-13 16:01:08.817 Script hash: 9Mhr0gOxbZV8SPQg9iR2TPwgO/ULSHFduUO25lomgb4= ----------------------EOF----------------------- CBS.log attached.
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 13, 2024 #28 Latest CBS.log looks good, please try updating your machine again. If successful please let me know. If not, please post the CBS.log created after your update attempt.
Latest CBS.log looks good, please try updating your machine again. If successful please let me know. If not, please post the CBS.log created after your update attempt.
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 17, 2024 #29 Hi Gary, thank you that has resolved the issue on the one device. Can I post the CBS.log for the second device with a similar issue? Or would you like me to create a new post? Either way, I really appreciate the time taken to troubleshoot the issue, I will be making a donation for sure!
Hi Gary, thank you that has resolved the issue on the one device. Can I post the CBS.log for the second device with a similar issue? Or would you like me to create a new post? Either way, I really appreciate the time taken to troubleshoot the issue, I will be making a donation for sure!
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 17, 2024 #30 Glad to hear you're now able to update your machine. Better if you start a new topic for the second device, as it will minimise any chance for confusion. If you post a link to your new topic in this one, then I'll know when you've created it, and unless some other helper picks up your topic before I do, then I'll be able to reply to it.
Glad to hear you're now able to update your machine. Better if you start a new topic for the second device, as it will minimise any chance for confusion. If you post a link to your new topic in this one, then I'll know when you've created it, and unless some other helper picks up your topic before I do, then I'll be able to reply to it.
richmolasses Member Joined Feb 29, 2024 Posts 24 Mar 19, 2024 #31 Hi Gary, I have created the new post here Thanks again for all your assistance.
Gary R Forum Moderator, Security Analyst, Windows Update Analyst Staff member Joined Aug 13, 2021 Posts 3,159 Mar 20, 2024 #32 Thanks. I've replied to your new topic, so we'll continue with things over there.