Windows update Services WSUS error in post install

Steps to Recover Your Server​

Step 1: Boot into Safe Mode​

1. Reboot into Safe Mode:
   • For VMs: Hypervisors like Hyper-V let you connect to the virtual machine console and access Safe Mode options.
   • If physical:
     • Restart the server and press F8 (or Shift + F8) repeatedly during startup.
   • Select Safe Mode with Networking from the boot menu.
2. Test if You Can Access the Server:
   • If Safe Mode boots successfully:
     1. Fix pending installations using steps in Step 3 below.
     2. Proceed to restore normal services or GUI access.

Step 2: Use a Recovery Environment​

1. Boot into Recovery:
   • Insert or mount the Windows Server 2025 ISO.
   • Boot to the installation media and choose Repair Your Computer.
   • Navigate to:
     
     Code:

          Troubleshoot > Advanced Options > Command Prompt

2. Load the Remote Drives:
   • Since you can access drives, ensure they are correctly assigned:
     
     Code:

     bash
          diskpart

     Then:
     
     Code:

     bash
          list volume
          exit

Step 3: Clean Pending Updates and Actions​

1. Delete Stuck Pending Files:
   • In the Command Prompt from recovery or Safe Mode:
     
     Code:

     bash
          del /f /q C:\Windows\WinSxS\pending.xml

2. Clear Update or Feature States:
   • Rename the update and component cleanup directories:
     
     Code:

     bash
          ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
          ren C:\Windows\System32\catroot2 Catroot2.old

3. Set Pending Operations to Resolved:
   Run:
   
   Code:

   bash
      dism /image:X:\ /cleanup-image /revertpendingactions

   • Replace X: with the mounted drive letter of your system.
4. Reboot the Server:
   
   Code:

   bash
      shutdown /r /t 0

Step 4: Reinstall Features Post-Recovery​

1. Open Command Prompt as Admin and run:
   
   Code:

   bash
      dism /online /enable-feature /featurename:NetFx4 /all
      dism /online /enable-feature /featurename:NET-WCF-Services45 /all

2. Add IIS and other required components cautiously:
   
   Code:

   bash
      Install-WindowsFeature Web-Server -IncludeManagementTools

Step 5: Repair the Installation​

1. Boot into the server and mount the Windows Server 2025 ISO.
2. Run the following:
   
   Code:

   bash
      setup.exe

3. Choose:
   • Upgrade this PC now.
   • Keep personal files and applications.

Summary​

1. Boot into Safe Mode or Recovery Environment, clear pending actions (pending.xml), and reset update states.
2. Incrementally fix feature operations (.NET Framework, IIS).
3. Use in-place upgrade repair as a fallback to refresh the OS entirely while retaining your configurations.

1. Corrupted or incomplete configurations (e.g., pending operations related to IIS, .NET Framework, or other features).
2. Stuck services or features attempting to initialize but failing (e.g., WCF, IIS Admin Service, WSUS-related changes).
3. GPU driver or remote desktop service issues in rare cases, though these aren't common on servers.

Steps to Recover from Spinning Circle GUI Issue​

Step 1: Force Boot into Safe Mode​

1. Reboot the Server into Safe Mode:
   • Depending on your setup:
     • If this is a physical server: Restart and press F8 repeatedly during boot (requires restart timing, or Shift+F8 during certain configurations).
     • If this is a virtual server: Use the hypervisor console (e.g., Hyper-V, VMware console) to add boot options to the VM:
     • For Hyper-V:
       
       Code:

       powershell
                Set-VMFirmware -VMName "VM Name" -FirstBootDevice HDD

   • From the Advanced Boot Menu, select Safe Mode with Networking.
2. If Safe Mode boots successfully, this confirms a services or startup process conflict. Skipping processes (in Step 3) will fix this.

Step 2: Try a Repair from Recovery Mode​

1. Boot from Windows Server 2025 Installation Media:
   • Insert the installation media (or mount the recovery ISO in your hypervisor).
   • Restart the server and boot to the ISO.
   • Choose Repair your computer > Troubleshoot > Advanced Options > Command Prompt.
2. Verify Drives from Command Prompt:
   • Run:
     
     Code:

     bash
          diskpart
          list volume
          exit

   • Confirm the system volume drive letter (C: or D:).

Step 3: Resolve Pending or Stuck System Operations​

1. Delete Pending Operations​

1. From Command Prompt, delete the pending operations file:
   
   Code:

   bash
      del C:\Windows\WinSxS\pending.xml

2. Revert Pending Feature Actions:
   • Run this DISM command to cancel stuck operations:
     
     Code:

     bash
          dism /image:C:\ /cleanup-image /revertpendingactions

   • Replace C: with the system drive letter if different.
3. Reboot into normal mode:
   
   Code:

   bash
      shutdown /r /t 0

Step 4: Use Safe Mode to Repair Features​

1. Validate Feature States​

dism /online /get-features /format:table

2. Repair Core Features​

dism /online /enable-feature /featurename:NetFx4 /all
dism /online /enable-feature /featurename:NET-WCF-Services45 /all

3. Remove Problematic Features​

dism /online /disable-feature /featurename:NET-WCF-HTTP-Activation45 /remove

Step 5: Repair Windows from the Installation Media​

1. Boot into the server using Windows Server 2025 ISO.
2. Run setup.exe from the installation media.
3. Select:
   • Upgrade this PC.
   • Choose Keep Files and Settings (this retains configurations and apps).

Step 6: Rebuild GUI Access​

1. Enable Remote Desktop from Command Prompt:
   
   Code:

   bash
      reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f
      netsh advfirewall firewall set rule group="remote desktop" new enable=Yes

2. Attempt to connect via RDP to troubleshoot the server remotely.

Step 7: Review Logs to Diagnose Further​

1. Access error logs using Safe Mode or Remote Desktop:
   • Event Viewer (eventvwr.msc):
     • Check Windows Logs > System or Application for errors.
   • Common culprits include:
     • IIS Admin Service
     • WAS (Windows Process Activation Service)
2. Fix errors based on findings:
   • Reconfigure failed services or reinstall core components as needed.

Key Troubleshooting Commands Recap​

1. Delete Pending Actions:
   
   Code:

   bash
      del C:\Windows\WinSxS\pending.xml
      dism /image:C:\ /cleanup-image /revertpendingactions

2. Repair Component Store:
   
   Code:

   bash
        diskpart
        list volume
        exit

   0
3. Re-enable .NET Core:
   
   Code:

   bash
        diskpart
        list volume
        exit

   1
4. In-Place Upgrade (from ISO):
   • Run setup.exe from the ISO.

Let Me Know​

Steps to Diagnose and Fix the Underlying Root Cause​

Step 1: Check for Pending Configurations or Services​

1. Check for Pending Operations:
   • Run this command to confirm if there are any pending actions:
     
     Code:

     bash
          dism /online /cleanup-image /revertpendingactions

   • If pending actions are reverted, reboot as a test.
2. Clear Stuck Pending Updates:
   • Run:
     
     Code:

     bash
          ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
          ren C:\Windows\System32\catroot2 catroot2.old

   • Restart the Windows Update-related services:
     
     Code:

     bash
          net stop wuauserv
          net start wuauserv

Step 2: Review Event Viewer Logs​

1. Open Event Viewer:
   • Type eventvwr.msc in the Start Menu > Press Enter.
2. Check These Log Categories:
   • Windows Logs > System:
     • Look for critical errors or warnings during the last shutdown/startup period.
   • Applications and Service Logs:
     • Look for errors related to IIS, WAS, WSUS, .NET components, or service failures.
3. Key Errors to Investigate:
   • Service timeout or failure for:
     • WAS (Windows Process Activation Service).
     • IIS Admin Service.
     • Any .NET Framework-related services.

Step 3: Repair Features and Components​

1. Re-enable .NET Framework 4.8:
   • If .NET Framework is tied to these issues, re-enable it fully:
     
     Code:

     bash
          dism /online /enable-feature /featurename:NetFx4 /all

2. Add Missing IIS Components:
   • If IIS is incomplete, reinstall required features:
     
     Code:

     bash
          Install-WindowsFeature Web-Server -IncludeManagementTools

3. Clean Component Store:
   • Perform a component cleanup:
     
     Code:

     bash
          dism /online /cleanup-image /startcomponentcleanup

Step 4: Test Smooth Shutdown and Restart​

1. Perform a Controlled Reboot:
   • Restart using:
     
     Code:

     bash
          shutdown /r /t 0

2. Watch for:
   • Whether the server shuts down properly without the spinning circle on shutdown or startup.

Step 5: Address Any Remaining WSUS or Post-Install Errors​

1. Retry the WSUS postinstall after ensuring all components are stable and features (IIS, WCF, .NET) are in place:
   
   Code:

   bash
      wsusutil.exe postinstall CONTENT_DIR="D:\WSUS\WSUSCONTENT" SQL_INSTANCE_NAME="MICROSOFT##WID"

2. If IIS is being bypassed for WSUS, retry with:
   
   Code:

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

Next Steps​

• If the server can now properly restart and shutdown successfully, you’ve resolved what was likely a feature or update misconfiguration.
• If issues persist during specific operations (e.g., WSUS postinstall or enabling .NET features), let me know the results, including logs or errors, for further targeted analysis.

bswhipp said:

If I turn off the server and then start it it will come back on line

Click to expand...