S Speedysurf Active member Joined Dec 24, 2022 Posts 32 Mar 27, 2024 #41 see files ... Attachments CBS.log 2.6 MB · Views: 1 SFCFix.txt 2.8 KB · Views: 1
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,739 Location The Netherlands Mar 27, 2024 #42 Here's the next fix. Step 1. 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. Step 2. Reboot the server and run the following DISM command and post the result. If it fails attach a new copy of the CBS log. Code: DISM /online /cleanup-image /RestoreHealth Attachments SFCFixScript.txt 989 bytes · Views: 2
Here's the next fix. Step 1. 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. Step 2. Reboot the server and run the following DISM command and post the result. If it fails attach a new copy of the CBS log. Code: DISM /online /cleanup-image /RestoreHealth
S Speedysurf Active member Joined Dec 24, 2022 Posts 32 Mar 27, 2024 #43 files ... Attachments CBS.log 1.9 MB · Views: 1 SFCFix.txt 6.1 KB · Views: 2
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,739 Location The Netherlands Mar 28, 2024 #44 Here's the next fix. Step 1. 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. Step 2. Reboot the server and run the following DISM command and post the result. If it fails attach a new copy of the CBS log. Code: DISM /online /cleanup-image /RestoreHealth Attachments SFCFixScript.txt 1 KB · Views: 2
Here's the next fix. Step 1. 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. Step 2. Reboot the server and run the following DISM command and post the result. If it fails attach a new copy of the CBS log. Code: DISM /online /cleanup-image /RestoreHealth
S Speedysurf Active member Joined Dec 24, 2022 Posts 32 Mar 28, 2024 #45 DISM without errors. Thank you.
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,739 Location The Netherlands Mar 28, 2024 #46 Great, please attempt to update again. If it fails attach a new copy of the CBS logs.
S Speedysurf Active member Joined Dec 24, 2022 Posts 32 Mar 28, 2024 #47 cbs file Attachments CBS.zip 5.7 MB · Views: 1
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,739 Location The Netherlands Mar 28, 2024 #48 Please attempt to update again with Process Monitor running. Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try updating the system just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link. 6. Attach also a new copy of the CBS logs for the time stamps.
Please attempt to update again with Process Monitor running. Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try updating the system just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link. 6. Attach also a new copy of the CBS logs for the time stamps.
S Speedysurf Active member Joined Dec 24, 2022 Posts 32 Mar 28, 2024 #49 Files: Logfile.zip Attachments CBS.zip 5.7 MB · Views: 2
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,739 Location The Netherlands Mar 28, 2024 #50 Rich (BB code): 3/28/2024 11:41:47 AM TiWorker.exe RegQueryValue HKLM\COMPONENTS\CanonicalData\Deployments\microsoft-w..anguagepack_31bf3856ad364e35_10.0.20348.1_e36cd6cf81089858\i!CBS_microsoft-windows-fsrm-core-base-package~31bf3856ad364e35~am_27e315d595e1b5bd NAME NOT FOUND Length: 0 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 with Process Monitor running. If it fails again attach also a new copy of the CBS logs. Attachments SFCFixScript.txt 3.1 KB · Views: 3
Rich (BB code): 3/28/2024 11:41:47 AM TiWorker.exe RegQueryValue HKLM\COMPONENTS\CanonicalData\Deployments\microsoft-w..anguagepack_31bf3856ad364e35_10.0.20348.1_e36cd6cf81089858\i!CBS_microsoft-windows-fsrm-core-base-package~31bf3856ad364e35~am_27e315d595e1b5bd NAME NOT FOUND Length: 0 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 with Process Monitor running. If it fails again attach also a new copy of the CBS logs.
S Speedysurf Active member Joined Dec 24, 2022 Posts 32 Mar 28, 2024 #51 Thank you. The update has now gone through. Great.
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,739 Location The Netherlands Mar 28, 2024 #52 You're welcome. Glad to here this server is up-to-date now... I will mark this thread as solved.