WSUS on the fritz again

Steps to Verify Using SHA256:​

1. Open Command Prompt or PowerShell:
   • You can use either the command line or Powershell to compute the hash.
2. Run the SHA256 Hash Command:
   • Use the following command (make sure you replace with the actual file path to your ISO):
     
     Code:

     bash CertUtil -hashfile "" SHA256

   • Compare the Output Hash:
     • Once you see the computed SHA256 hash in your terminal, compare it against the hash listed on the download site to confirm it matches exactly.

Example Command Output​

• The format will resemble:
  
  Code:

   SHA256 hash of file :

1. If Hashes Don’t Match:
   • If the hash you computed does not match what’s listed on the download site, the ISO may be corrupt, and you should re-download it from a trustworthy source.

Confirm Integrity Before Proceeding​

• If the hash is accurate and matches perfectly, proceed with the steps we discussed earlier (like mounting the ISO and using it in your DISM commands).
• If the hash doesn’t match, skip trying any repairs with that ISO until you have a correctly verified version.

Steps to Repair Using the Valid ISO​

1. Mount the ISO:
   • If it’s not already mounted, right-click the ISO file and select Mount. Note the drive letter assigned (e.g., D:).
2. Run the DISM Command with Source Option:
   • Use the following command to point to the install.wim file from your mounted ISO:
     
     Code:

     bash dism /online /cleanup-image /restorehealth /source:wim:D:\sources\install.wim:1 /limitaccess

   • Replace D: with the actual drive letter where your ISO is mounted.
3. Monitor the Output:
   • Wait for the command to finish and watch for any errors or confirmation of success.
   • If DISM completes successfully, it means the component store was repaired.
4. Run System File Checker (SFC):
   • After a successful DISM action, run:
     
     Code:

     bash sfc /scannow

   • This will further check integrity and repair system files.
5. Reboot the Server:
   • Once both DISM and SFC have completed, restart the server to finalize any changes.
6. Retry WSUS Configuration:
   • After rebooting, attempt to run the wsusutil postinstall command again:
     
     Code:

     bash wsusutil.exe postinstall SQL_INSTANCE_NAME="YourInstanceName" CONTENT_DIR="D:\WSUS\WSUSCONTENT"

If You Encounter Further Errors​

• If issues persist during the postinstall execution:
  • Check the WSUSSetup.log and IIS logs for any updated errors.
  • Focus on errors similar to previous communications, like those related to IIS configuration or path findability.

Final Notes​

• If the DISM actions don’t resolve your issues, we might need to explore deeper into the WSUSSetup.log for additional clues. Please keep me posted on the results once you execute these commands!

Steps to Troubleshoot DISM Error 0x800f081f​

Step 1: Use the Correct Source from the Mounted ISO​

1. Verify Index Number:
   • Run this command to confirm the index:
     
     Code:

     bash dism /Get-WimInfo /WimFile:D:\sources\install.wim

   • Note down the actual index number for your version of Windows Server 2022. If the first index returns a mismatch, try using that specific index in the following command.
2. Run DISM with Exact Source:
   Run DISM again, ensuring the source parameter is absolutely correct:
   
   Code:

   bash dism /online /cleanup-image /restorehealth /source:wim:D:\sources\install.wim: /limitaccess

   Replace with the correct number found from your Get-WimInfo command.

Step 2: Check for File Path Issues​

• Since 0x800f081f can also be caused by file path errors or environmental issues:
  • Make sure there are no special characters or spaces in your path.
  • Temporarily move the ISO to a simpler directory such as C:\ISO\ and remount it.

Step 3: Confirm Permissions​

• The account you're running the commands under must have appropriate permissions:
  • Right-click the Command Prompt or PowerShell > Run as Administrator.
  • Ensure that the Windows account has full access to both the mounted ISO and its folders.

Step 4: Accessing Windows Updates Online​

1. Disable WSUS Temporarily:
   Ensure your server can reach Microsoft Update by disabling the "Specify intranet Microsoft update service location" setting in Group Policy:
   • Open Group Policy Editor (gpedit.msc).
   • Navigate to:
     
     Code:

      Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update

   • Disable the setting, then force a policy refresh:
     
     Code:

     bash gpupdate /force

2. Run The Following DISM Command:
   Allow it to attempt to pull files from Microsoft directly:
   
   Code:

   bash dism /online /cleanup-image /restorehealth

Step 5: Examine CBS.log and Use an Alternative Source​

1. After running DISM with the mounted ISO, check the CBS.log:
   • This log may provide more granular error messages:
     
     Code:

      C:\Windows\Logs\CBS\cbs.log

2. Use Additional Repair Options:
   If issues persist beyond DISM, consider executing a full installation repair:
   • Mount the ISO again.
   • Navigate to the setup.exe file within the ISO and run it. Choose the Upgrade option to repair Windows while keeping settings in place.

Final Notes:​

Let's break down the resolution into actionable steps:​

Step 1: Verify Mounting and Location of the ISO​

1. Ensure the ISO is Mounted Correctly:
   • Verify the drive letter where the ISO is mounted.
   • Ensure all necessary files are accessible, especially install.wim or install.esd.
2. Recheck the Source Path:
   Run the following command to explicitly check the availability of install.wim or install.esd:
   
   Code:

   bash dism /Get-WimInfo /WimFile:D:\sources\install.wim

   • Confirm you get a valid response with the expected Windows Server 2022 images listed.

Step 2: Run DISM with Explicit Source Path​

1. If using install.wim:
   
   Code:

   bash dism /online /cleanup-image /restorehealth /source:wim:D:\sources\install.wim:1 /limitaccess

   This tells DISM which index to use.
2. If using install.esd (change the command for ESD) if needed:
   
   Code:

   bash dism /online /cleanup-image /restorehealth /source:ESD:D:\sources\install.esd:1 /limitaccess

Step 3: Ensure Network Access​

1. If the server is configured to connect through WSUS, temporarily disable that setting:
   • Navigate to Group Policy Editor (gpedit.msc).
   • Under:
     
     Code:

      Computer Configuration > Administrative Templates > Windows Components > Windows Update

   • Disable the "Specify intranet Microsoft update service location".
2. Run:
   
   Code:

   bash gpupdate /force

3. Retry the DISM command for the online repair.

Step 4: Analyze the CBS.log for Further Clues​

• Look into the CBS logs for additional hints on missing files:
  
  Code:

   C:\Windows\Logs\CBS\cbs.log

• Key pieces of information can include names of files DISM cannot locate or other errors indicating the nature of the failure.

Step 5: Additional Manual Repair Options​

1. In-Place Upgrade Repair:
   • Using the same ISO, run setup.exe. This option allows Windows to perform a repair and may clear existing corruption:
     
     Code:

     bash D:\setup.exe

     Choose to Upgrade while keeping data intact.
2. Create a Bootable USB:
   • If the ISO mounted method continues to fail, consider creating bootable media using tools like Rufus. Boot from this USB and run repairs.

Summary:​

• Mount your valid Windows Server 2022 ISO correctly and ensure all files are intact.
• Try explicitly specifying the source in the DISM command.
• Check CBS log for any missing file references.
• Consider performing an in-place repair if ongoing repair attempts fail.

Addressing the 0x800f081f Error​

Step 1: Ensure Proper Source Access​

1. Mount the Correct Windows Server 2022 ISO Again:
   • Make sure you've a good copy and it's mounted properly.
   • Ensure you're referencing the correct path when retrieving the install.wim.
2. Run DISM Targeting the ASCII-Based Image File:
   Execute the following command:
   
   Code:

   bash dism /online /cleanup-image /restorehealth /source:wim:D:\sources\install.wim:1 /limitaccess

   • Change D: with the actual mounted ISO path if needed.

Step 2: Try Accessing the Source from Windows Update​

1. Disable WSUS Configuration:
   You already noted earlier—ensure your Group Policies to not specify WSUS:
   • Go to Group Policy Editor (gpedit.msc):
     
     Code:

      Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update

   • Disable "Specify intranet Microsoft update service location".
2. Run DISM:
   Attempt to run:
   
   Code:

   bash dism /online /cleanup-image /restorehealth

Step 3: Complete Manual Installation of Components​

1. Use the ISO for a manual repair by launching setup.exe:
   • Navigate to the mounted ISO.
   • Run:
     
     Code:

     bash D:\setup.exe

   • Choose Upgrade and keep your files.

Step 4: Last Resort - Repair Windows​

1. Access MSI (Microsoft Installer) logs.
2. Reinstall any IIS components or core Windows features around the WSUS needs:
   
   Code:

   bash Install-WindowsFeature -Name Web-Server, Web-Common-Http, Web-Dyn-Compression, Web-Basic-Auth, Web-Windows-Auth, Web-Mgmt-Console

Final Steps if All Else Fails​

• Back up your current environment meticulously.
• As a last effort, consider rebuilding the server (which would be time-consuming but would guarantee a clean and functional state).

Next Steps​

1. Run the commands above for either direct mount of ISO OR attempt from Windows Update without the WSUS setting.
2. If there’s still a failure, let’s analyze CBS again for specifics on what’s failing to locate and work from there.

Steps During the In-Place Upgrade:​

1. Follow the On-Screen Prompts:
   • The setup will guide you through various options. Ensure you select Upgrade and choose to keep your files and applications.
2. Monitor the Install Process:
   • Keep an eye on the progress. Any errors or prompts should be addressed during installation.
3. Post-Upgrade Actions:
   • Once the upgrade completes, ensure to:
     • Restart the server if prompted.
     • Run Windows Updates manually to bring everything up to the latest version.
     • Recheck WSUS configuration to see if it now initializes correctly.

Testing WSUS After the Upgrade:​

1. Re-run the WSUS Post-Install Command:
   After confirming that the upgrade completes successfully:
   
   Code:

   bash wsusutil.exe postinstall SQL_INSTANCE_NAME="YourInstanceName" CONTENT_DIR="D:\WSUS\WSUSCONTENT"

2. Validate the Current WSUS Functionality:
   • Open the WSUS administration console and check for any errors.
   • Test your WSUS updates against your clients.

Next Steps After Upgrade​

• Gather logs from the WSUS installation:
  • Look specifically at the WSUSSetup.log and any IIS-related logs from your previous settings.

Step 1: Check Installed Hyper-V Features​

1. Open PowerShell with Administrator Privileges and check if Hyper-V features are currently enabled:
   
   Code:

   powershell Get-WindowsFeature -Name Hyper-V

2. Look for the Installed Features:
   • If Hyper-V is listed and installed, you'll need to decide whether to remove it (if it's not needed) or prepare to manage the upgrade correctly.

Step 2: Options Depending on Hyper-V Usage​

Option 1: If You Need Hyper-V and Want to Keep it:​

• Before upgrading, make sure that all Hyper-V virtual machines (VMs) are turned off and that you’re following best practices for Hyper-V:
  • Ensure your virtual network adapters (if any) are configured correctly.
  • Consider handling your Hyper-V setups according to Microsoft guidelines. You might need to check compatibility for any VMs or features you plan to keep.

1. Try Upgrading Using:
   • PowerShell or Windows Settings to ensure Hyper-V settings aren't conflicting.

Option 2: If Hyper-V is Unnecessary:​

• If you find that you don’t need Hyper-V features, consider disabling/removing Hyper-V before attempting the upgrade:
  
  Code:

  powershell Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All

• Reboot the server, then reattempt the in-place upgrade with the Windows Server 2022 ISO.

Step 3: Retry the Upgrade​

1. Attempt the in-place upgrade again by running:
   
   Code:

   bash D:\setup.exe

   (Ensure the ISO is mounted correctly.)

Step 4: Monitor Installation / Errors​

• Be attentive to any new prompts or errors that arise during the upgrade, especially if they pertain to existing configurations.

If Installation Continues to Fail​

• Any specific errors that pop up during the Hyper-V check or installation process.
• Key outputs from logs relating to Hyper-V or setup (often found in C:\$WINDOWS.~BT\Sources\Panther during setup).

Final Note​

Understanding the Situation​

1. Hyper-V Not Checked in Roles:
   • This could mean that the Hyper-V role is not installed as part of the standard roles list or that it exists as an update feature rather than a root role.
2. Install State - Available:
   • If the Hyper-V role is marked as available, it indicates that it is indeed present but may not be actively configured.
   • This can happen if Hyper-V was installed via PowerShell or other means without the full role being added formally in the GUI.

Step 1: Verify All Installed Features​

Get-WindowsFeature | Where-Object { $_.Name -like '*Hyper-V*' }

Step 2: Check Hyper-V Manager​

1. Open Hyper-V Manager (you can search for it in the Start Menu).
2. Verify the virtual machines (VMs) and network switches:
   • Ensure you have correctly configured network switches or external access.

Step 3: Check Installed Roles via PowerShell​

Get-WindowsFeature Hyper-V

• Look for:
  • Role Services: Ensure that essential components (like Hyper-V Virtual Machine Management) are listed.

Step 4: Remove/Repair Hyper-V if Necessary​

1. Run the following command in PowerShell:
   
   Code:

   Uninstall-WindowsFeature –Name Hyper-V –IncludeManagementTools

2. You may also check and remove any specific Hyper-V roles that you don’t intend to keep.

Step 5: Proceed with In-Place Upgrade Post-Configuration​

1. Retry the in-place upgrade with the Windows Server 2022 ISO:
   
   Code:

   bash D:\setup.exe

2. Follow the prompts for an upgrade, ensuring you've kept your files and settings.

Final Note​

• Consider directly reaching out to Microsoft support for Hyper-V related configuration complexities, especially if you aim for a successful in-place upgrade without needing a complete server installation to mitigate potential risks from existing setups.

Here’s How to Proceed:​

1. Leave Hyper-V Management Features as-is:​

2. Focus on Addressing WSUS Configuration Issues:​

Step-by-Step: Troubleshooting WSUS Postinstall​

1. Check WSUS Dependencies:
   Ensure all features required by WSUS are installed. Use PowerShell to check:
   
   Code:

   powershell Get-WindowsFeature | Where-Object { $_.Name -like '*Web*' }

   Make sure IIS-related features (Web-Server and all sub-features) are included as before.
2. Reconfirm the Content Directory:
   • Make sure:
     
     Code:

     bash D:\WSUS\WSUSCONTENT

   • Exists and has proper permissions.
3. Revisit the WSUS Postinstall Command:
   Since previous attempts failed due to path issues:
   • Make sure the command is correctly configured:
     
     Code:

     bash wsusutil.exe postinstall SQL_INSTANCE_NAME="YourInstanceName" CONTENT_DIR="D:\WSUS\WSUSCONTENT"

4. Run With Skipped IIS Config:
   If errors persist, try skipping IIS configuration to see if it allows completion:
   
   Code:

   bash wsusutil.exe postinstall -skipIISConfig SQL_INSTANCE_NAME="YourInstanceName" CONTENT_DIR="D:\WSUS\WSUSCONTENT"

5. Review Logs for Insight:
   • If the postinstall command fails again, check the WSUSSetup.log and IIS logs immediately after for any errors related to paths or configurations.

If Postinstall Still Fails with IIS-Related Errors​

1. Additional Verification Needed:
   • Look for mismatches in WSUS virtual directories if they’ve been altered or are missing.
   • Each directory (like Content, SelfUpdate, etc.) must point to valid existing locations.
2. Final Attempt for a Clean Retry:
   If everything else fails, be ready to run:
   
   Code:

   bash wsusutil.exe deletecontent wsusutil.exe reset

   • This will clean up and allow WSUS to attempt its configuration afresh.

Summary​

1. Keep Hyper-V Management Tools as they’re not causing issues.
2. Focus on refining the path settings and confirming directory permissions.
3. Retry the postinstall command, considering both standard and -skipIISConfig executions.
4. Review logs thoroughly for any persistent issues after each step.

Proceeding with the In-Place Upgrade​

1. Confirm the Hyper-V Notice:
   • When prompted regarding Hyper-V during the upgrade process, you should be able to confirm and proceed. The installation will assess the existence of the Hyper-V management tools along with any existing configurations.
   • Since Hyper-V is only a management layer in this case, it should not block the upgrade.
2. Ensure Backup:
   • Make sure that you have a current backup of your system, including crucial data, before proceeding. This will protect you from unforeseen issues during the upgrade.
3. Run the Setup:
   • Mount the Windows Server 2022 ISO if it's not already mounted.
   • Launch the upgrade by running:
     
     Code:

     bash D:\setup.exe

   • Follow the installation prompts carefully, ensuring you select Keep Files and Apps during the installation options.
4. Monitor the Upgrade Process:
   • Keep an eye on the installation. While it's processing, it may take some time depending on your server's resources and configurations.
5. Post-Upgrade Tasks:
   • Once the upgrade completes:
     • Ensure that WSUS and all server roles operate correctly.
     • Run Windows Updates after the upgrade to ensure all components are updated.
     • Re-run any WSUS configuration commands as necessary.

Post-upgrade Steps to Validate WSUS and IIS​

1. Verify WSUS Installation:
   • Check the functionality of the WSUS console.
   • Confirm that the postinstall command works without any issues:
     
     Code:

     bash wsusutil.exe postinstall SQL_INSTANCE_NAME="YourInstanceName" CONTENT_DIR="D:\WSUS\WSUSCONTENT"

2. Test Clients:
   • Send a manual update request from a client to ensure they can connect to WSUS and download updates.

Final Note​