teampouce Well-known member Joined Jul 4, 2024 Posts 46 Jul 26, 2024 #41 done first the cumulative update of january appears : then ended : Thanks
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 14,003 Location The Netherlands Jul 26, 2024 #42 You can ignore error 0x80070643 and/or hide KB5034439 when BitLocker is not being used: Issues with KB5034439 on Windows Server 2022? This is how you can temporarily hide this update. Otherwise you'll need to resize the WinRE partition manually using the following instructions: KB5028997: Instructions to manually resize your partition to install the WinRE update - Microsoft Support
You can ignore error 0x80070643 and/or hide KB5034439 when BitLocker is not being used: Issues with KB5034439 on Windows Server 2022? This is how you can temporarily hide this update. Otherwise you'll need to resize the WinRE partition manually using the following instructions: KB5028997: Instructions to manually resize your partition to install the WinRE update - Microsoft Support
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 14,003 Location The Netherlands Jul 26, 2024 #44 This error is related to the latest LCU, not the other Security Update from January. Please attempt to update again with Process Monitor running and attach the PML trace file and the latest CBS logs.
This error is related to the latest LCU, not the other Security Update from January. Please attempt to update again with Process Monitor running and attach the PML trace file and the latest CBS logs.
teampouce Well-known member Joined Jul 4, 2024 Posts 46 Jul 26, 2024 #45 here requestes file after update attempt thanks Attachments Logfile1.zip 14.2 MB · Views: 1 CBS.zip 5.6 MB · Views: 2
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 14,003 Location The Netherlands Jul 26, 2024 #46 It seems the ProcMon trace was stopped to early or do you have set some filters to remove entry's from the original log?
It seems the ProcMon trace was stopped to early or do you have set some filters to remove entry's from the original log?
teampouce Well-known member Joined Jul 4, 2024 Posts 46 Aug 13, 2024 #47 Just back from vacation. Here files from today attempt. Thanks Attachments Logfile2.zip 39.2 MB · Views: 1 CBS.zip 5.5 MB · Views: 2
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 14,003 Location The Netherlands Aug 13, 2024 #48 Hi, Hope you had a great vacation... Here's the next fix. Download SFCFix and save it to your desktop. Warning: This fix was written specifically for this system. Do not run this fix on another system. Save any work you have open, and close all programs. Download the attachment SFCFix.zip and save it to your desktop. Drag the SFCFix.zip 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 Afterwards reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs. Attachments SFCFix.zip 424.7 KB · Views: 1
Hi, Hope you had a great vacation... Here's the next fix. Download SFCFix and save it to your desktop. Warning: This fix was written specifically for this system. Do not run this fix on another system. Save any work you have open, and close all programs. Download the attachment SFCFix.zip and save it to your desktop. Drag the SFCFix.zip 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 Afterwards reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs.
teampouce Well-known member Joined Jul 4, 2024 Posts 46 Aug 13, 2024 #49 Hi Yes it was great ! Unfortunatelly it failed again but with a new error code : here CBS.log do you need procmon trace ? Thanks Attachments CBS (2).zip 8 MB · Views: 1
Hi Yes it was great ! Unfortunatelly it failed again but with a new error code : here CBS.log do you need procmon trace ? Thanks
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 14,003 Location The Netherlands Aug 13, 2024 #50 A ProcMon trace is not needed this time. Warning: This fix was written specifically for this system. Do not run this fix on another system. Save any work you have open, and close all programs. Download the attachment SFCFix.zip and save it to your desktop. Drag the SFCFix.zip 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 Afterwards attempt to update again. If it fails attach a new copy of the CBS logs. Attachments SFCFix.zip 7.9 KB · Views: 1
A ProcMon trace is not needed this time. Warning: This fix was written specifically for this system. Do not run this fix on another system. Save any work you have open, and close all programs. Download the attachment SFCFix.zip and save it to your desktop. Drag the SFCFix.zip 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 Afterwards attempt to update again. If it fails attach a new copy of the CBS logs.
teampouce Well-known member Joined Jul 4, 2024 Posts 46 Aug 13, 2024 #51 still no luck Attachments CBS (3).zip 4.1 MB · Views: 2
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 14,003 Location The Netherlands Aug 13, 2024 #52 Another error this time, here's the next fix. Warning: This fix was written specifically for this system. Do not run this fix on another system. 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. Afterwards attempt to update again. If it fails attach a new copy of the CBS logs. Attachments SFCFixScript.txt 32.2 KB · Views: 1
Another error this time, here's the next fix. Warning: This fix was written specifically for this system. Do not run this fix on another system. 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. Afterwards attempt to update again. If it fails attach a new copy of the CBS logs.
teampouce Well-known member Joined Jul 4, 2024 Posts 46 Aug 14, 2024 #53 we progress 1 of 2 was installed, don't know if related to new tuesday patch : Then I restarted and try again but no luck : Last CBS log attached. Thanks Attachments CBS (4).zip 10.3 MB · Views: 1
we progress 1 of 2 was installed, don't know if related to new tuesday patch : Then I restarted and try again but no luck : Last CBS log attached. Thanks
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 14,003 Location The Netherlands Aug 14, 2024 #54 Hi, Here's the next fix. Warning: This fix was written specifically for this system. Do not run this fix on another system. 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. Afterwards reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs. Attachments SFCFix.zip 443.1 KB · Views: 2
Hi, Here's the next fix. Warning: This fix was written specifically for this system. Do not run this fix on another system. 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. Afterwards reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs.
teampouce Well-known member Joined Jul 4, 2024 Posts 46 Aug 15, 2024 #55 Hi it failed. CBS log in attachment thanks Attachments CBS (5).zip 8 MB · Views: 1
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 14,003 Location The Netherlands Aug 15, 2024 #56 Hi, Export SBS (SideBySide) hive Click on the Start button and type regedit When you see regedit on the list, right-click on it and select Run as administrator. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once. Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide Once selected, click File > Export.... Change the Save as type: to Registry Hive Files (*.*). Name this file SideBySide (with no file extension) and save it to your Desktop. Right-click on the saved file and choose Send > Compressed (zipped) Folder. Attach the .ZIP file to your next post. If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
Hi, Export SBS (SideBySide) hive Click on the Start button and type regedit When you see regedit on the list, right-click on it and select Run as administrator. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once. Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide Once selected, click File > Export.... Change the Save as type: to Registry Hive Files (*.*). Name this file SideBySide (with no file extension) and save it to your Desktop. Right-click on the saved file and choose Send > Compressed (zipped) Folder. Attach the .ZIP file to your next post. If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
teampouce Well-known member Joined Jul 4, 2024 Posts 46 Aug 15, 2024 #57 here registry hive export thanks Attachments SideBySide.zip 1.3 MB · Views: 1
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 14,003 Location The Netherlands Aug 15, 2024 #58 Please post also a new copy of the COMPONENTS hive. Upload your COMPONENTS hive. Navigate to C:\Windows\System32\Config and locate the COMPONENTS 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 COMPONENTS.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.
Please post also a new copy of the COMPONENTS hive. Upload your COMPONENTS hive. Navigate to C:\Windows\System32\Config and locate the COMPONENTS 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 COMPONENTS.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.
teampouce Well-known member Joined Jul 4, 2024 Posts 46 Aug 15, 2024 #59 here it is Attachments COMPONENTS.zip 16.5 MB · Views: 1
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 14,003 Location The Netherlands Aug 15, 2024 #60 Here's the next fix. Warning: This fix was written specifically for this system. Do not run this fix on another system. 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. Afterwards attempt to update. If it fails attach a new copy of the CBS logs. Attachments SFCFixScript.txt 2.8 KB · Views: 1
Here's the next fix. Warning: This fix was written specifically for this system. Do not run this fix on another system. 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. Afterwards attempt to update. If it fails attach a new copy of the CBS logs.