Windows update Services WSUS error in post install

bswhipp · 2025-01-13T13:57:36-0500

I think I was having issues uninstalling WebServer stuff because it wanted to uninstall .ner 4.8 Features WCF Services HTTP Activation which in stalled by default in Server 2025 and is unable to be unchecked. So I was starting to reinstall other features and got the errors above. Now upon reboot, got the back screen with circle. Can access the server drives remotes ly but GUI is not coming up.

ChatGPT · 2025-01-13T13:58:10-0500

It seems like the server has entered a stuck state upon reboot (black screen with spinning circle), likely caused by conflicts or pending operations tied to IIS and .NET Framework 4.8 WCF Services during installation/uninstallation attempts. This is compounded by the fact that Server 2025 installs specific features by default, which appeared unremovable or misconfigured, further disrupting reboot.
The fact you can still remotely access the drives means the server isn't entirely offline, and we can use recovery techniques to repair the boot process, clear pending changes, and restore the GUI.

Steps to Recover Your Server

Step 1: Boot into Safe Mode

Safe Mode allows booting without engaging unnecessary services/features (like IIS or .NET Framework) that may be blocking the login GUI.

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.
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

If Safe Mode isn’t available or the server still hangs at the spinning circle, use recovery tools.

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
```
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

A common cause of stuck reboots is pending configurations for features or servicing updates. Clearing these can allow the server to boot.

Delete Stuck Pending Files:
- In the Command Prompt from recovery or Safe Mode:
  Code:
```
bash
     del /f /q C:\Windows\WinSxS\pending.xml
```

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

Set Pending Operations to Resolved:
Run:
Code:
```
bash
   dism /image:X:\ /cleanup-image /revertpendingactions
```
- Replace X: with the mounted drive letter of your system.
Reboot the Server:
Code:
```
bash
   shutdown /r /t 0
```

Step 4: Reinstall Features Post-Recovery

Once the server boots normally, reinstall and repair features incrementally to avoid conflicts.

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

Add IIS and other required components cautiously:

Code:

bash
   Install-WindowsFeature Web-Server -IncludeManagementTools

Step 5: Repair the Installation

If the server is still unstable, repair the system using an in-place upgrade.

Boot into the server and mount the Windows Server 2025 ISO.
Run the following:
Code:
```
bash
   setup.exe
```
Choose:
- Upgrade this PC now.
- Keep personal files and applications.

This process refreshes the Windows installation, fixing core issues with features like .NET Framework, IIS, and Component Store corruption.

Summary

To recover your server:

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

Let me know how each step goes, or any additional error messages you encounter. We’ll restore full functionality!

bswhipp · 2025-01-13T13:59:38-0500

Upon reboot, GUI is stuck at black screen with circle. Can get to drives of the server but no GUI.

ChatGPT · 2025-01-13T14:00:18-0500

The black screen with a spinning circle issue typically indicates that the server is failing to load the GUI (Graphical User Interface) session during the boot process. This can happen due to:

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

You can recover the server by disabling any pending changes, repairing boot-critical components, and regaining access through Safe Mode or Recovery Environment.

Steps to Recover from Spinning Circle GUI Issue

Step 1: Force Boot into Safe Mode

Safe Mode disables non-essential services and features, giving you access to address the underlying issue.

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.
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

If booting into Safe Mode doesn’t work, or Advanced Boot Options cannot be accessed, you’ll need to use Recovery Tools.

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.
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

Pending feature installations/removals are common causes of this issue. Clear them manually.

1. Delete Pending Operations

From Command Prompt, delete the pending operations file:
Code:
```
bash
   del C:\Windows\WinSxS\pending.xml
```
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.
Reboot into normal mode:
Code:
```
bash
   shutdown /r /t 0
```

Step 4: Use Safe Mode to Repair Features

Once the server boots into Safe Mode (or after pending actions are cleared), proceed with repairing features.

1. Validate Feature States

Run DISM from Safe Mode to check if features like .NET Framework or IIS are partially installed:

Bash:

dism /online /get-features /format:table

2. Repair Core Features

Repair possible corrupt features:

Bash:

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

3. Remove Problematic Features

If certain features are causing issues (e.g., WCF HTTP Activation):

Bash:

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

Step 5: Repair Windows from the Installation Media

If the GUI still doesn’t load, perform an in-place upgrade repair to reinstall all key Windows components.

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

This process rebuilds any corrupted services or feature states while preserving server settings.

Step 6: Rebuild GUI Access

Sometimes stuck Remote Desktop (RDP) or graphics rendering (GPU dependency) services cause GUI issues.

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

Attempt to connect via RDP to troubleshoot the server remotely.

Step 7: Review Logs to Diagnose Further

If the system boots but the GUI fails:

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)
Fix errors based on findings:
- Reconfigure failed services or reinstall core components as needed.

Key Troubleshooting Commands Recap

Delete Pending Actions:

Code:

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

Repair Component Store:

Code:

bash
     diskpart
     list volume
     exit

0

Re-enable .NET Core:

Code:

bash
     diskpart
     list volume
     exit

1

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

Let Me Know

Try these recovery steps and let me know how your server responds. Share any error messages or specific details if further troubleshooting is needed—I’ll guide you through!

bswhipp · 2025-01-13T14:01:15-0500

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

ChatGPT · 2025-01-13T14:01:56-0500

This behavior indicates that the server is able to recover a working state after a hard restart (power cycle), but it still hints at some underlying issue—likely related to feature servicing, services failing during shutdown/startup, or system corruption—that causes it to hang during a "soft reboot" or after pending operations.
Since the server is operational after turning it off and powering it back on, let’s take this opportunity to diagnose and resolve any root causes before it becomes a persistent or worse issue.

Steps to Diagnose and Fix the Underlying Root Cause

Step 1: Check for Pending Configurations or Services

Pending configurations during shutdown or startup might be causing the hang during "soft reboots."

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.

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

Errors during the shutdown or startup sequence will often appear in Event Viewer.

Open Event Viewer:
- Type eventvwr.msc in the Start Menu > Press Enter.
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.
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

Feature-related issues, especially with .NET Framework or IIS, could be contributing to this behavior.

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
```
Add Missing IIS Components:
- If IIS is incomplete, reinstall required features:
  Code:
```
bash
     Install-WindowsFeature Web-Server -IncludeManagementTools
```

Clean Component Store:

Perform a component cleanup:

Code:

bash
     dism /online /cleanup-image /startcomponentcleanup

Step 4: Test Smooth Shutdown and Restart

After performing the cleanup and feature repairs:

Perform a Controlled Reboot:
- Restart using:
  Code:
```
bash
     shutdown /r /t 0
```
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

If this issue originated from WSUS configurations:

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"
```

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.

We’re getting the server back to full stability—keep up the good work!

Mike · 2025-01-13T14:05:16-0500

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

Unplug it from the wall and never turn it back on

bswhipp · 2025-01-13T14:14:22-0500

dism /online /enable-feature /featurename:NET-WFC-Services45 /all returns
Feature name NET-WCF-Services45 is unknown.
A Windows feature name was not recognized.
Use the /Get-Features option to find the name of the feature in the image and try the command again.

bswhipp · 2025-01-13T14:35:10-0500

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
Install the latest PowerShell for new features and improvements! Migrating from Windows PowerShell 5.1 to PowerShell 7 - PowerShell PS C:\Users\DAdmin> Install-WindowsFeature NET-WCF-HTTP-Activation45

Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True No NoChangeNeeded {}

PS C:\Users\DAdmin> dism /online /enable-feature /featurename:NET-WCF-Services45 /all

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.1742

Error: 0x800f080c

Feature name NET-WCF-Services45 is unknown.
A Windows feature name was not recognized.
Use the /Get-Features option to find the name of the feature in the image and try the command again.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
PS C:\Users\DAdmin>

bswhipp · 2025-01-13T14:45:16-0500

CBS Log
2025-01-13 14:33:31, Info SXS Unloading registry hive: \Registry\Machine\SCHEMA
2025-01-13 14:33:31, Info CSI 0000000e Perf: LRU Cache Clear @0x13d226672e0
2025-01-13 14:34:32, Info CBS Module starts contributing to an existing logging session
2025-01-13 14:34:32, Info SXS TurboStack version 10.0.26100.1738 (WinBuild.160101.0800) loaded from C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.1738_none_a5031b637767a4e7
2025-01-13 14:34:32, Info CSI 0000000f@2025/1/13:19:34:32.320 WcpInitialize: wcp.dll version 10.0.26100.1738 (WinBuild.160101.0800)
2025-01-13 14:34:32, Info CSI 00000010 Perf: LRU Cache Initialize @0x13d22bc30d0; Maximum Size: 1024 MiB; Initial Elements: 8192
2025-01-13 14:34:32, Info SXS Initialized store, arch=amd64, style=Desktop, compact=false, windir=(null), sandbox=
2025-01-13 14:34:32, Info CBS Session: 31155698_729150183 initialized by client DISM Package Manager Provider
2025-01-13 14:34:32, Info CBS Enumerating Foundation package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.26100.1, this could be slow
2025-01-13 14:34:32, Info CBS Failed to get internal update: NET-WCF-Services45 in Package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.26100.1 [HRESULT = 0x800f080c - CBS_E_UNKNOWN_UPDATE]
2025-01-13 14:34:32, Info CSI 00000011 Perf: LRU Cache Clear @0x13d22bc30d0
2025-01-13 14:36:32, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

Dism Log

2025-01-13 14:34:32, Info CSI 00000001 Shim considered [l:123]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.1738_none_a5031b637767a4e7\wcp.dll' : got STATUS_SUCCESS
2025-01-13 14:34:32, Info DISM DISM Package Manager: PID=1548 TID=3964 Processing the top level command token(enable-feature). - CPackageManagerCLIHandler:

rivate_ValidateCmdLine
2025-01-13 14:34:32, Info DISM DISM Package Manager: PID=1548 TID=3964 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2025-01-13 14:34:32, Info DISM DISM Package Manager: PID=1548 TID=3964 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2025-01-13 14:34:32, Info DISM DISM Package Manager: PID=1548 TID=3964 Encountered the option "featurename" with value "NET-WCF-Services45" - CPackageManagerCLIHandler:

rivate_GetPackagesFromCommandLine
2025-01-13 14:34:32, Info DISM DISM Package Manager: PID=1548 TID=3964 Encountered an unknown option "featurename" with value "NET-WCF-Services45" - CPackageManagerCLIHandler:

rivate_GetPackagesFromCommandLine
2025-01-13 14:34:32, Error DISM DISM Package Manager: PID=1548 TID=3964 Failed to get the Update through CBS. - CDISMPackage::Internal_OpenFeature(hr:0x800f080c)
2025-01-13 14:34:32, Error DISM DISM Package Manager: PID=1548 TID=3964 Failed to get the underlying CBS Feature - CDISMPackage::OpenFeature(hr:0x800f080c)

Navigation section

Windows update Services WSUS error in post install

Member

Costly AI Model

Steps to Recover Your Server​

Step 1: Boot into Safe Mode​

Step 2: Use a Recovery Environment​

Step 3: Clean Pending Updates and Actions​

Step 4: Reinstall Features Post-Recovery​

Step 5: Repair the Installation​

Summary​

Member

Costly AI Model

Steps to Recover from Spinning Circle GUI Issue​

Step 1: Force Boot into Safe Mode​

Step 2: Try a Repair from Recovery Mode​

Step 3: Resolve Pending or Stuck System Operations​

1. Delete Pending Operations​

Step 4: Use Safe Mode to Repair Features​

1. Validate Feature States​

2. Repair Core Features​

3. Remove Problematic Features​

Step 5: Repair Windows from the Installation Media​

Step 6: Rebuild GUI Access​

Step 7: Review Logs to Diagnose Further​

Key Troubleshooting Commands Recap​

Let Me Know​

Member

Costly AI Model

Steps to Diagnose and Fix the Underlying Root Cause​

Step 1: Check for Pending Configurations or Services​

Step 2: Review Event Viewer Logs​

Step 3: Repair Features and Components​

Step 4: Test Smooth Shutdown and Restart​

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

Next Steps​

Windows Forum Admin

Member

Member

Member

Similar threads

Steps to Recover Your Server

Step 1: Boot into Safe Mode

Step 2: Use a Recovery Environment

Step 3: Clean Pending Updates and Actions

Step 4: Reinstall Features Post-Recovery

Step 5: Repair the Installation

Summary

Steps to Recover from Spinning Circle GUI Issue

Step 1: Force Boot into Safe Mode

Step 2: Try a Repair from Recovery Mode

Step 3: Resolve Pending or Stuck System Operations

1. Delete Pending Operations

Step 4: Use Safe Mode to Repair Features

1. Validate Feature States

2. Repair Core Features

3. Remove Problematic Features

Step 5: Repair Windows from the Installation Media

Step 6: Rebuild GUI Access

Step 7: Review Logs to Diagnose Further

Key Troubleshooting Commands Recap

Let Me Know

Steps to Diagnose and Fix the Underlying Root Cause

Step 1: Check for Pending Configurations or Services

Step 2: Review Event Viewer Logs

Step 3: Repair Features and Components

Step 4: Test Smooth Shutdown and Restart

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

Next Steps