[SOLVED] Reply to Old thread: Windows server 2019 and kb5034127 wont install

If you'd let me know that earlier then I wouldn't have closed your previous topic.

OK, your latest CBS.log looks clear, so please try updating your machine.

If successful please let me know, if not please post the CBS.log created after your update attempt.


But before doing any of that I have a question ...... which DRIVERS.zip file did you use to replace your existing DRIVERS file, the first one I posted, or the second, because if you used the first one, then you need to replace it with the second one.

The tool I used to create the first one didn't run as expected, and thankfully the mistake was spotted by one of my colleagues (Maxstar) which is why I had to post a corrected file.
 
Gary R said:
If you'd let me know that earlier then I wouldn't have closed your previous topic.

OK, your latest CBS.log looks clear, so please try updating your machine.

If successful please let me know, if not please post the CBS.log created after your update attempt.


But before doing any of that I have a question ...... which DRIVERS.zip file did you use to replace your existing DRIVERS file, the first one I posted, or the second, because if you used the first one, then you need to replace it with the second one.

The tool I used to create the first one didn't run as expected, and thankfully the mistake was spotted by one of my colleagues (Maxstar) which is why I had to post a corrected file.
Click to expand...
Im sorry. Had a busy week :( I used the second one. Im updating now. Giving you a reply when im done.
 
Gary R said:
If you'd let me know that earlier then I wouldn't have closed your previous topic.

OK, your latest CBS.log looks clear, so please try updating your machine.

If successful please let me know, if not please post the CBS.log created after your update attempt.


But before doing any of that I have a question ...... which DRIVERS.zip file did you use to replace your existing DRIVERS file, the first one I posted, or the second, because if you used the first one, then you need to replace it with the second one.

The tool I used to create the first one didn't run as expected, and thankfully the mistake was spotted by one of my colleagues (Maxstar) which is why I had to post a corrected file.
Click to expand...
Hi

Still not working.
 

Attachments

Please go to .... C:\Windows\INF .... and post me a copy of your .... setupAPI.dev.log
 
Thanks.

It's almost midnight here, so it will be tomorrow morning (my time GMT) before I get a chance to look at your log.

In the meantime, can you please supply me with the latest copy of your DRIVERS file (which may have been partially updated by your update attempt, and therefore different to the one I modified earlier).
 
Gary R said:
Thanks.

It's almost midnight here, so it will be tomorrow morning (my time GMT) before I get a chance to look at your log.

In the meantime, can you please supply me with the latest copy of your DRIVERS file (which may have been partially updated by your update attempt, and therefore different to the one I modified earlier).
Click to expand...
 

Attachments

Need to consult with my colleagues on what I've found in your logs. This may take some time. I'll get back to you as soon as possible.
 
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 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.
1p8eDnI.gif

  • 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

SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-02-18 18:10:04.625
Microsoft Windows Server 10 Build 17763 - amd64
Using .txt script file at C:\Users\admin\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.
Successfully traced component amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d.
Package_412_for_KB5022286~31bf3856ad364e35~amd64~~10.0.1.7.5022286-939_neutral2

[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.4499.1.5\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.



[4: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4499.1.5\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.



[5: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.3887.1.7\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.



[6: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.3887.1.7\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.



[7: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4131.1.10\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.4131.1.10\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.



[9: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4377.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.



[10: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4377.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.



[11: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4252.1.13\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.



[12: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4252.1.13\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.



[13: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4737.1.6\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.



[14: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4737.1.6\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.



[15: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4645.1.14\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.



[16: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4645.1.14\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.



[17: 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.



[18: 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.



[19: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4974.1.9\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.



[20: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4974.1.9\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.



[21: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4851.1.5\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.



[22: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4851.1.5\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.



[23: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5206.1.3\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.



[24: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5206.1.3\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.



[25: 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.



[26: 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.



[27: 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.



[28: 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.
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-02-18 18:10:52.696
Script hash: S+sMsIPx7/qRxmip9WKb1usYAGS2jPQkMfCEprUNyLc=
----------------------EOF-----------------------
Click to expand...
 
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.
1p8eDnI.gif

  • 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

Hi

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-02-18 20:09:19.459
Script hash: ykg9pcpZd8XW9xlJb8ZJlYYmA2/7D+1HncqJCQ4/Vp8=
----------------------EOF-----------------------
Click to expand...
 

Attachments

OK, latest CBS.log looks good, please try updating again.

If successful please let me know.

If not, please post the CBS.log created after your update attempt.
 
You're welcome. Glad we were able to help.
 
You must log in or register to reply here.

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

Back
Top