G Gardinho Active member Joined Jun 3, 2023 Posts 41 Monday at 4:50 AM #61 DISM failed. Logs attached. Thanks for persisting with this... Attachments CBS.zip 12.9 MB · Views: 1 SFCFix.txt 22.8 KB · Views: 1
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,886 Location The Netherlands Monday at 4:59 AM #62 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. 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 2.2 KB · Views: 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. 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
G Gardinho Active member Joined Jun 3, 2023 Posts 41 Monday at 5:08 AM #63 This time it failed at 48% instead of 41% Attachments CBS.zip 12.5 MB · Views: 2 SFCFix.txt 17.1 KB · Views: 1
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,886 Location The Netherlands Monday at 5:13 AM #64 Some registry keys we have restored before are beeing flagged again. And due the number of corrupted RTM keys / payloads it might be better to perform a repair install with the Server 2022 ISO. In-place upgrade Server 2022 with the MSDN (Retail) ISO. Navigate to the URL below and sign-in with your MSDN registered account. https://msdn.microsoft.com/subscriptions/securedownloads/ Use the search field to find and download the correct ISO file. Mount the Windows Server ISO and run Setup.exe. Use the option Download updates, drivers, and optional features (recommended) and click Next. Note: If you don't want to update during the in-place upgrade, press Change how setup downloads updates and select Not right now - !!! Not recommended !!! When the following screen is prompted enter your (25 digit) product key. Note: Do not use the public KMS key as listed here. In the next screen, select the image of the installed Windows Server edition and click Next. Then accept the EULA. To perform a in-place upgrade, you need to check keep personal files and apps. Then click Next. After clicking Next, an upgrade process will start checking for updates, when this is ready click install to start the in-place upgrade.
Some registry keys we have restored before are beeing flagged again. And due the number of corrupted RTM keys / payloads it might be better to perform a repair install with the Server 2022 ISO. In-place upgrade Server 2022 with the MSDN (Retail) ISO. Navigate to the URL below and sign-in with your MSDN registered account. https://msdn.microsoft.com/subscriptions/securedownloads/ Use the search field to find and download the correct ISO file. Mount the Windows Server ISO and run Setup.exe. Use the option Download updates, drivers, and optional features (recommended) and click Next. Note: If you don't want to update during the in-place upgrade, press Change how setup downloads updates and select Not right now - !!! Not recommended !!! When the following screen is prompted enter your (25 digit) product key. Note: Do not use the public KMS key as listed here. In the next screen, select the image of the installed Windows Server edition and click Next. Then accept the EULA. To perform a in-place upgrade, you need to check keep personal files and apps. Then click Next. After clicking Next, an upgrade process will start checking for updates, when this is ready click install to start the in-place upgrade.
G Gardinho Active member Joined Jun 3, 2023 Posts 41 Monday at 5:24 AM #65 I think because of the way we deploy updates (SCCM) and the fact that we have several machines like this it´s probably not going to be a manageable solution to do in-place upgrades. If there is no more we can do with this I´ll see if the local IT departments will deploy the new image to the affected laptops. I´ve been trying to solve this problem for ages and this was the last hope. I don´t want to waste any more of your time on it. I really appreciate the effort. 18 scripts were executed on the machine!
I think because of the way we deploy updates (SCCM) and the fact that we have several machines like this it´s probably not going to be a manageable solution to do in-place upgrades. If there is no more we can do with this I´ll see if the local IT departments will deploy the new image to the affected laptops. I´ve been trying to solve this problem for ages and this was the last hope. I don´t want to waste any more of your time on it. I really appreciate the effort. 18 scripts were executed on the machine!
Maxstar Windows Update Moderator, Security Analyst Staff member Joined Aug 16, 2015 Posts 10,886 Location The Netherlands Monday at 5:33 AM #66 You're welcome. Deploying a new image would be the best way to resolve this issue on all the afftected systems, also because we don't make any progress...
You're welcome. Deploying a new image would be the best way to resolve this issue on all the afftected systems, also because we don't make any progress...