Windows update Services WSUS error in post install

Steps to Resolve "Feature Unknown" for .NET WCF HTTP Activation​

Step 1: List Recognizable Features​

1. Run the command to list all available and unrecognized features:
   
   Code:

   bash
      dism /online /get-features /format:table

   • Look for anything related to:
     • NET-Framework-45
     • NET-WCF-TCP-Activation45
     • WCF-HTTP-Activation
     • NET-WCF-Services45
2. What to look for:
   • If you see no WCF features: The component store likely has missing data.
   • If WCF components are grayed/unavailable (e.g., Disabled with Payload Removed): This confirms a corrupted Component Store or missing source files.

Step 2: Reinstall/Repair .NET Framework​

1. Reinstall .NET Framework Core Features:
   • Run:
     
     Code:

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

   • This enables .NET Framework 4.8 alongside its foundation features.
2. Validate WCF Features After Reinstallation:
   • Check feature availability:
     
     Code:

     bash
          dism /online /get-features /format:table

3. Retry Removing WCF HTTP Activation:
   
   Code:

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

Step 3: Repair the Component Store​

1. Run DISM RestoreHealth Command (No Source):
   
   Code:

   bash
      dism /online /cleanup-image /restorehealth

2. If DISM Fails to RestoreHealth:
   • Mount the Windows Server 2025 ISO (to, say, D:).
   • Perform a restorehealth with a valid source for missing components:
     
     Code:

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

   • Replace D: with the correct drive letter where the ISO is mounted.

Step 4: Reset Orphaned Features in Component Store​

1. Run Component Cleanup Commands:
   • Perform this to clear unnecessary cached components:
     
     Code:

     bash
          dism /online /cleanup-image /startcomponentcleanup

2. Delete Pending CBS or Feature Store Actions:
   • Navigate to:
     
     Code:

          C:\Windows\WinSxS

   • Delete any file named pending.xml, if present:
     
     Code:

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

3. Reboot the server and retry running the restorehealth or feature disable command.

Step 5: Rebuild Feature with Manual Files​

1. Extract the sxs Files from the ISO:
   • Mount the Windows Server ISO (e.g., D:).
   • Copy the files for NET-WCF-HTTP-Activation45 into a temporary folder:
     
     Code:

     bash
          xcopy D:\sources\sxs\* C:\Temp\SXS\ /s /e

2. Run DISM Against the Extracted Files:
   • Add the feature manually using the copied files:
     
     Code:

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

     0

Step 6: Refresh the Windows Feature Repository​

1. Mount Windows Server 2025 ISO:
   • Open the ISO you’ve used as a source file.
2. Perform an In-Place Upgrade Repair:
   • Run setup.exe from the ISO and select:
     • Upgrade this PC.
     • Retain files and settings.
   • This will reinstall the entire operating system while keeping applications and configurations intact.
3. Post-Repair Cleanup:
   • Retry dism /get-features to confirm WCF features are listed.
   • Re-enable or remove .NET WCF HTTP Activation as necessary.

Step 7: Examine Logs for Specific Errors​

1. DISM Logs:
   • Location:
     
     Code:

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

     1
   • Look for:
     • Missing resource errors such as source files could not be found.
     • Errors referencing WCF or HTTP Activation.
2. CBS Logs (Servicing Issues):
   • Location:
     
     Code:

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

     2
   • Search for:
     • 0x800f0922.
     • 0x800f080c.
     • Relevant .NET WCF feature errors.

Summary​

1. Repair the .NET Framework dependencies.
2. Restore missing metadata in the Component Store.
3. Fix or remove orphaned entries in Windows servicing (CBS).
4. Perform a full in-place upgrade if necessary.

Steps for Restoring Windows Server from Backup​

Step 1: Verify Your Backup​

1. Ensure the Backup is Intact:
   • Confirm the backup files (e.g., from Windows Server Backup, third-party tools, or VM snapshots) are up to date and complete.
   • Verify the backup contains all critical data, configurations, and system state files necessary for the restoration.
2. Identify the Type of Backup:
   • Full server backup or Hyper-V virtual machine (VM) snapshot.
   • Bare-metal recovery (includes system state, drives, and OS).

Step 2: Boot into Recovery Mode​

1. For Physical Machines:
   • Use your Windows Server 2025 ISO or a recovery USB drive to boot into recovery mode.
   • Select Repair your computer > Troubleshoot > System Image Recovery.
2. For Virtual Machines:
   • Restore from a VM snapshot (most hypervisors have native tools for rolling back).

Step 3: Restore from Backup​

Option 1: System Image Recovery​

1. From the recovery tools menu, select Recovery from System Image.
2. Follow the prompts to locate your backup on:
   • A network share.
   • External storage (USB, NAS, etc.).
   • Backup disks.
3. Start the recovery process and restart when complete.

Option 2: Hypervisor Snapshot Recovery​

1. Open your hypervisor (e.g., Hyper-V, VMware, etc.).
2. Select the VM and restore a snapshot or backup.
3. Restart the VM and validate services after recovery.

Option 3: Third-Party Backup Tools​

1. Launch the respective tool on a recovery environment or management PC.
2. Point to your backup source, select the destination server or VM, and restore the system.

Step 4: Post-Recovery Validation​

1. Validate WSUS and IIS:
   • Confirm that the WSUS server and IIS configuration files were restored correctly.
   • Test control of Update Services and WSUS Console.
2. Check SQL Database (if applicable):
   • Start SQL Server and confirm that critical WSUS databases (like SUSDB) are intact.
3. Troubleshoot Pending Errors:
   • Check Event Viewer > System Logs for errors related to the restoration.
   • Ensure services like WSUS, IIS (W3SVC), and MSSQL start correctly.
4. Run Necessary Updates:
   • Ensure a backlog exists for critical updates that may not have been applied prior to the restore.

Step 5: Backup Validation and Preventive Measures​

1. Confirm that the backup strategy is working and conduct regular backups moving forward.
2. Address the root causes of the original server crash:
   • Restore servicing stack updates and test updates.
   • Monitor .NET Framework or IIS behavior closely for unresolved issues.

Final Notes​

1. Errors or Failures:
   • Search the log for entries associated with Failed, CBS[I]E[/I], or specific error codes (e.g., 0x800F0922, 0x800F081F, or 0x800F080C).
2. Timed Events:
   • Look for events or status logs matching the time of your failed feature installation attempts.
3. Pending Actions:
   • Check if the log references pending.xml or indicates incomplete feature operations.

1. Provide Key Sections:
   • Focus on entries around the time you tried installing features.
   • Search for the terms like "error", "failed", or specific error codes (e.g., 0x800f0922, 0x800f080c).
2. Upload the File:
   • Upload the C:\Windows\Logs\CBS\CBS.log file here, and I can analyze it for you.
   • Alternatively, you can provide a compressed .zip version of the log if it’s too large.
3. Use Keywords:
   • If you open the file with a text editor (e.g., Notepad) and search for related lines, just copy-paste the critical sections containing errors.

DISM Command to Repair the Image​

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

Command Breakdown​

• dism: Deployment Image Servicing and Management tool.
• /online: Targets the running Windows installation on the current server.
• /cleanup-image: Operates on the Windows component store (WinSxS).
• /restorehealth: Repairs corruption in the image by replacing damaged or missing files.
• /source:wim:F:\sources\install.wim:1:
  • This specifies the path to the Windows image source (from your mounted ISO drive F:).
  • The :1 index refers to the correct edition within install.wim (you can confirm the right index in Step 1 below).
• /limitaccess: Forces DISM to use the files in the provided source (and not download from Windows Update).

Steps to Repair Image with ISO​

Step 1: Confirm the WIM Index​

1. Run this command to list available editions in the WIM file:
   
   Code:

   bash
      dism /get-wiminfo /wimfile:F:\sources\install.wim

2. Look for the one matching your OS build and edition (e.g., "Datacenter" or "Standard") and note the Index Number.
3. Modify the command if necessary:
   
   Code:

   bash
      dism /online /cleanup-image /restorehealth /source:wim:F:\sources\install.wim:<index> /limitaccess

Step 2: Perform the Image Repair​

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

• Validate the integrity of your system files.
• Replace missing or corrupted files using the source provided in the ISO.
• Bypass any reliance on Windows Update for downloading components.

Step 3: Reboot After Successful Repair​

shutdown /r /t 0

Notes & Common Errors​

1. If You Receive a "Source Files Could Not Be Found" Error:
   • Ensure the ISO is mounted and that the F:\sources\install.wim exists. Alternatively, switch to esd if you’re using a compressed ISO:
     
     Code:

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

2. Log Locations for Debugging:
   • If the repair fails, check the logs for specifics:
     • DISM: C:\Windows\Logs\DISM\dism.log
     • CBS: C:\Windows\Logs\CBS\CBS.log

Let Me Know How It Goes!​

Steps to Upload the Log File:​

1. Locate the Log File:
   • For DISM:
     
     Code:

          C:\Windows\Logs\DISM\dism.log

   • For CBS:
     
     Code:

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

2. Compress the File:
   • Right-click the file (e.g., CBS.log) > Send to > Compressed (zipped) folder.
   • This reduces the file size and ensures it uploads smoothly.
3. Upload the File:
   • Use the "Attach File" or Upload option available in this interface to upload the log file.

Option 1: Extract Key Sections from the Logs​

1. Open the Log File:
   • For DISM:
     
     Code:

          C:\Windows\Logs\DISM\dism.log

   • For CBS:
     
     Code:

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

2. Search for Errors:
   • Look for keywords:
     • Error
     • Failed
     • Terms like 0x800f0922, 0x800f080c, CBS_E_UNKNOWN_UPDATE.
3. Copy Those Sections:
   • Highlight any problematic sections and paste them here for analysis.

Option 2: Share Critical Highlights​

1. The last ~30 lines of the log file.
2. Sections immediately around the time the DISM or WSUS feature installation failed.

Option 3: Manually Summarize​

1. The source path (e.g., F:\sources\install.wim) is incorrect or invalid.
2. The ISO image being used doesn’t match the installed version of Windows Server.
3. The Component Store (WinSxS) is severely corrupted and cannot locate critical files.

Step 1: Confirm the Mounted ISO Source​

1. Mount the Windows Server ISO:
   • Ensure your ISO is mounted (e.g., as drive F:) and locate install.wim:
     
     Code:

          F:\sources\install.wim

     If install.wim doesn’t exist and you see install.esd, proceed to Step 2 for updated instructions.
2. Verify the ISO Build:
   • Check the ISO’s version matches your installed Windows Server version:
     • Run:
       
       Code:

       bash
              winver

     • Example: Windows Server 2025 Build 26100.xxxx.
     • Open DISM to verify editions inside the install.wim file:
       
       Code:

       bash
              dism /get-wiminfo /wimfile:F:\sources\install.wim

       Make sure you are using the matching build and edition (e.g., 'Datacenter' or 'Standard').
3. Update to a Newer ISO if Needed:
   • If the mounted ISO doesn’t match, download the latest version of Windows Server for your build.

Step 2: Correct DISM Command Depending on File Type​

1. If You Have install.wim:
   • Use this command to specify the WIM as the source:
     
     Code:

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

2. If You Have install.esd (Compressed):
   • Use this command:
     
     Code:

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

Step 3: Repair the Servicing Stack​

1. Run DISM to Repair the Servicing Stack:
   
   Code:

   bash
      dism /online /cleanup-image /startcomponentcleanup

2. Remove Pending Updates if Stuck:
   
   Code:

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

3. Retry the DISM Command.

Step 4: Use Windows Update to Fetch Components​

1. Modify your command:
   
   Code:

   bash
      dism /online /cleanup-image /restorehealth

   • This allows DISM to connect to Microsoft servers and download the missing features.

Step 5: Perform an In-Place Upgrade​

1. Mount the ISO and run:
   
   Code:

   bash
      setup.exe

2. Select:
   • Upgrade this PC now.
   • Keep personal files and apps.
3. After the upgrade:
   • Retry feature-related operations or WSUS postinstall without errors.

Recap of Critical Commands​

1. For WIM:
   
   Code:

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

2. For ESD:
   
   Code:

   bash
          winver

   0
3. Allow Windows Update:
   
   Code:

   bash
          winver

   1

Step 1: Wait for StartComponentCleanup Completion​

1. This process will:
   • Remove unused, superseded, or orphaned components.
   • Reduce servicing-state-related conflicts.
2. If startcomponentcleanup completes without errors:
   • Proceed to retry the /restorehealth command as follows:
     
     Code:

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

3. If startcomponentcleanup Fails:
   • Share the error message it provides so we can address it directly.

Step 2: Retry the Repair Command​

1. Use this exact repair command to force DISM to work with the .wim file:
   
   Code:

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

2. Expected Output:
   • If successful, it will report "The restore operation completed successfully."

Step 3: Troubleshoot Persistent Issues​

Option 1: Delete Pending Operations​

1. Check if pending.xml exists (shows pending operations):
   • Run:
     
     Code:

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

     1. If found, delete it:
        
        Code:

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

2. Retry the restorehealth command after this cleanup.

Option 2: Sharing Error Results​

1. If New Errors Occur:
   • Let me know the specific error code/result from startcomponentcleanup.
2. Check Logs:
   Check the following for error details:
   • CBS Log:
     
     Code:

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

   • DISM Log:
     
     Code:

          C:\Windows\Logs\DISM\dism.log

Next Steps After Successful DISM Repair​

Step 1: Recheck Feature Availability​

1. List Available Features:
   
   Code:

   bash
      dism /online /get-features /format:table

2. Look for .NET Framework/WCF Features:
   • Focus on:
     • NET-WCF-HTTP-Activation45
     • NET-WCF-Services45
     • NET-Framework-45-ASPNET
     • NET-Framework-45-Core
3. If the Features Are Visible:
   • Attempt enabling or removing the feature:
     
     Code:

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

4. If Features Are Still Missing:
   • Proceed to repair .NET Framework as outlined in Step 3 below.

Step 2: Retry WSUS Postinstall (If Applicable)​

1. Run the WSUS Post-Install Command:
   
   Code:

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

2. If the -skipIISConfig flag was previously used, you can add it again:
   
   Code:

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

3. Validate Post-Install Success:
   • Monitor the WSUS installation logs:
     
     Code:

          C:\Users\<YourUsername>\AppData\Local\Temp\2\WSUS_PostInstall_<timestamp>.log

Step 3: Repair or Reinstall .NET Framework​

1. Repair/Reinstall .NET Framework Core Features:
   • Enable missing core frameworks first:
     
     Code:

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

2. Add or Repair Specific WCF Features:
   • Enable or reinstall WCF Services layer components:
     
     Code:

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

3. Test for Success:
   • Recheck feature recognition after enabling:
     
     Code:

     bash
          dism /online /get-features /format:table

4. If Errors Persist:
   • Share the new failure or log errors, and we’ll refine further.

Step 4: Finalize Cleanup​

1. Run Component Cleanup Again (Optional):
   
   Code:

   bash
      dism /online /cleanup-image /startcomponentcleanup

   • This ensures no unnecessary files remain in your Component Store.
2. Reboot Your Server:
   
   Code:

   bash
      shutdown /r /t 0

3. Validate All Critical Services After Boot:
   • Test WSUS, IIS, or other dependent tools for functionality.

Let Me Know​