Windows update Services WSUS error in post install

Steps to Resolve WSUS Installation When SCCM doesn’t Resolve Conflicts​

Step 1: Deep-Clean Residual SCCM WSUS Configuration​

1. Fully Remove WSUS with SCCM Configurations​

1. Uninstall the WSUS Features:
   
   Code:

   bash
      Remove-WindowsFeature -Name UpdateServices, UpdateServices-Services, UpdateServices-DB -IncludeManagementTools

2. Delete SCCM-Specific Content:
   • Navigate to the SCCM WSUS folder (default: E:\SCCM\WSUS) or wherever SCCM stored WSUS updates.
   • Delete the WSUSContent folder and UpdateServicesPackages directory.
3. Clean the WSUS Registry Keys (Because SCCM modifies them):
   • Open Registry Editor (regedit) and navigate to:
     
     Code:

          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services

   • Delete the entire Update Services key.
   • Check for leftover SCCM hooks under:
     
     Code:

          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates

4. Restart the server.

Step 2: Ensure a Clean IIS Environment​

1. Remove Existing WSUS IIS Configuration​

1. Open IIS Manager (inetmgr).
2. Delete the WSUS Administration site (if it exists).
3. Remove any residual virtual directories under any other IIS site:
   • Content
   • SelfUpdate

2. Reset IIS to Defaults​

1. Reset IIS:
   
   Code:

   bash
      dism /online /cleanup-image /restorehealth

2. Clear IIS config and start fresh:
   
   Code:

   bash
      iisreset /force

3. Reinstall IIS required features for WSUS:
   
   Code:

   powershell
      Install-WindowsFeature Web-Server, Web-WebServer, Web-Net-Ext45, Web-ASPNET

Step 3: Validate the Database​

1. Drop SUSDB if Corrupted or Incomplete​

1. Open SQL Server Management Studio (SSMS).
2. Connect to the database engine:
   • WID:
     
     Code:

          np:\\.\pipe\MICROSOFT##WID\tsql\query

   • SQL Instance: Custom SQL Server instance.
3. Check the SUSDB database for corruption:
   
   Code:

   sql
      SELECT * FROM tbSchemaVersion;

4. If the database is incomplete, drop it:
   
   Code:

   sql
      DROP DATABASE SUSDB;

5. Allow wsusutil.exe to recreate the database during the next postinstall.

Step 4: Retry WSUS Postinstall After Full IIS/IIS and Path Reset​

1. Retry the WSUS postinstall command:
   
   Code:

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

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services

Step 5: Gather Logs and Deeper IIS Diagnostics​

1. IIS Logs:​

• Locate:
  
  Code:

       HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services

  1
• Review errors related to WSUS sites or directories, such as 404 (missing path) or 401 (permissions).

2. Enable Windows Tracing to Debug Startup Failures:​

1. Enable verbose Event Viewer diagnostics:
   
   Code:

        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services

   2
2. Check:
   
   Code:

        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services

   3

3. Use Debugging Tools for IIS:​

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services

• Fix through:
  
  Code:

       HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services

  5

If Issues Persist​

1. Share relevant IIS logs, postinstall log snippets, or any other errors logged in Event Viewer or setup logs (e.g., WSUSSetup.log).
2. Detail SCCM’s exact configuration or what’s currently installed, as it might require disabling additional settings in SCCM before WSUS can work standalone again.

Steps to Resolve WSUS SQL Configuration Issues​

Step 1: Verify SQL Server Connectivity​

1. Test SQL Connectivity:
   • Open SQL Server Management Studio (SSMS) on the server hosting the WSUS SQL database.
   • Connect to the relevant SQL Server instance:
     
     Code:

          <YourSQLServerName>\<YourSQLInstance>

     Example:
     
     Code:

          SQLServer01\WSUSINST

2. Locate the SUSDB Database:
   • Check if the SUSDB database exists in the SQL instance.
   • Query its properties to confirm it’s intact:
     
     Code:

     sql
          USE SUSDB;
          SELECT * FROM tbSchemaVersion;

   • If SUSDB doesn’t exist or the query fails, it may have been corrupted or removed during previous failed WSUS installations.
3. Fix Missing or Corrupt SUSDB:
   • If the database is missing or corrupted, drop it to allow the WSUS postinstall to recreate it:
     
     Code:

     sql
          DROP DATABASE SUSDB;

4. Ensure WSUS-Related SQL Permissions:
   • NT AUTHORITY\NETWORK SERVICE or a custom WSUS service account must have db_owner rights to the SQL Server instance.
   • Grant permissions via SQL Server:
     
     Code:

     sql
          USE master;
          CREATE LOGIN [NT AUTHORITY\NETWORK SERVICE] FROM WINDOWS;
          ALTER SERVER ROLE sysadmin ADD MEMBER [NT AUTHORITY\NETWORK SERVICE];

Step 2: Run the Postinstall Command with SQL Options​

wsusutil.exe postinstall SQL_INSTANCE_NAME="<YourSQLServerName>\<YourSQLInstance>" CONTENT_DIR="D:\WSUS\WSUSCONTENT" /logfile:C:\Temp\WSUSPostInstallLog.txt

• Note:
  • If your SQL instance is the Default Instance, simply use:
    
    Code:

         SQL_INSTANCE_NAME="MSSQLSERVER"

Step 3: Investigate Logs and Permissions​

1. WSUS Postinstall Logs:
   • Check:
     
     Code:

          C:\Temp\WSUSPostInstallLog.txt

2. SQL Logs:
   • Open SQL Server Management tools and review error logs:
     
     Code:

          <SQLInstallPath>\Log

   • Look for connection attempts, permission errors, or database issues.

Step 4: Clean Up Residual SQL/WSUS Configuration​

1. Drop the Existing SUSDB Database:
   
   Code:

   sql
      DROP DATABASE SUSDB;

2. Remove WSUS Users or Roles in SQL:
   • Open SQL Security Settings and delete improperly leftover logins, like:
     
     Code:

          SQLServer01\WSUSINST

     0

Step 5: Manual SQL Server Verification (Advanced)​

1. Inspect SQL SUSDB Tables:​

• Check schema integrity:
  
  Code:

       SQLServer01\WSUSINST

  1
• Verify relationships:
  
  Code:

       SQLServer01\WSUSINST

  2

2. Fix SQL Instance if Corrupt:​

• Restart the SQL Server instance hosting WSUS:
  
  Code:

       SQLServer01\WSUSINST

  3

Step 6: IIS Recheck for SQL Integration​

1. Inspect Application Pools:
   • Ensure WsusPool exists and is set to use:
     • .NET CLR Version v4.0
     • Integrated Pipeline Mode.
2. Manually Create Directories (If Missing):
   • Content Path:
     • Create IIS content folder in: D:\WSUS\WSUSCONTENT.
   • Database Connection:
     • Ensure WSUS attempts to use the SQL instance during postinstall.

Potential SCCM Impact​

1. If SCCM has already been integrated with SQL, additional locks or configuration overrides could conflict with the manual WSUS installation process.
   • Temporarily disconnect SCCM from WSUS (disable SUP role on SCCM).
   • Fully complete the WSUS installation before re-enabling SCCM.

Next Debugging Steps​

1. Key snippets from the WSUSPostInstallLog.txt file.
2. Any unexpected findings in IIS or SQL logs.

Step 1: Back Up Your IIS Configuration (Including HP Site)​

Option 1: Use appcmd to Back Up IIS Entirely​

1. Open Command Prompt as Administrator.
2. Use the following command to back up IIS configurations:
   
   Code:

   bash
      appcmd add backup "HPWebsiteBackup"

   • This creates a full IIS configuration backup (including sites, bindings, and SSL certificates) and stores it under:
     
     Code:

          %windir%\system32\inetsrv\backup\HPWebsiteBackup

Step 2: Export the Specific HP Site Configuration​

1. Open Command Prompt as Administrator.
2. Use the following command to list all sites in IIS:
   
   Code:

   bash
      appcmd list site

   • Identify the site name or ID of the HP site (e.g., HPUpdateSite).
3. Export the specific site:
   
   Code:

   bash
      appcmd list site "HPUpdateSite" /config /xml > C:\Backup\HPWebsiteConfig.xml

Step 3: Backup Site Content (Manually)​

1. Open File Explorer.
2. Locate the physical path for your HP site's content:
   • This path is listed under the site settings in IIS Manager (e.g., C:\inetpub\hpupdate).
3. Copy the entire folder to a backup directory:
   • Example:
     
     Code:

          C:\Backup\HPWebsiteContent\

Step 4: Uninstall IIS Completely​

1. Open PowerShell as Admin and run the following:
   
   Code:

   powershell
      Remove-WindowsFeature Web-Server -IncludeManagementTools

2. Navigate to remove leftover configuration:
   • Delete:
     
     Code:

          C:\inetpub

     Code:

          %windir%\system32\inetsrv

3. Restart your server after removing IIS.

Step 5: Reinstall IIS​

1. Install IIS and the necessary management tools:
   
   Code:

   powershell
      Install-WindowsFeature Web-Server, Web-WebServer, Web-Mgmt-Tools

2. Restart IIS to apply the new configuration:
   
   Code:

   bash
      iisreset

Step 6: Restore the HP Website​

Option 1: Restore Entire IIS Backup​

1. Apply the original IIS backup (if you backed up everything):
   
   Code:

        %windir%\system32\inetsrv\backup\HPWebsiteBackup

   0
   • Restart IIS to reload configurations.

Option 2: Restore Specific HP Site​

1. Import the HP site's configuration:
   
   Code:

        %windir%\system32\inetsrv\backup\HPWebsiteBackup

   1
   • Verify the site appears in IIS Manager.
2. Validate the physical path:
   • Copy the backed-up website content (e.g., C:\Backup\HPWebsiteContent) back to its original physical path if necessary.

Step 7: Verify HP Website​

1. Open IIS Manager and ensure the HP site is listed and its bindings (ports, hostnames) are intact.
2. Test the HP site in your browser:
   
   Code:

        %windir%\system32\inetsrv\backup\HPWebsiteBackup

   2

Notes​

• SSL Certificates: If the HP site uses SSL, also back up and rebind the associated certificate after restoring the site.
• WSUS Postinstall: Once IIS is clean, retry the WSUS installation without interference.

Steps to Cleanly Remove IIS and Its Dependencies​

Step 1: Force Removal Using DISM​

1. Open Command Prompt as Administrator.
2. Run the following command to remove IIS and all dependencies:
   
   Code:

   bash
      dism /online /disable-feature /featurename:IIS-WebServerRole /remove

3. Restart the server and retry uninstalling IIS if it still hangs or fails.

Alternative (Specific Components):​

If the full IIS role still fails, try targeting components individually:

Bash:

dism /online /disable-feature /featurename:IIS-WebServer
dism /online /disable-feature /featurename:IIS-WebServerManagementTools

Step 2: Remove IIS Registry Entries (Manually, If Needed)​

1. Open Registry Editor (regedit).​

1. Back up the registry (File > Export, just to be safe).
2. Navigate to the IIS-related registry keys:
   
   Code:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IISAdmin
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC

3. Delete these keys.
4. Remove any additional leftovers in these default file locations:
   
   Code:

      C:\Windows\System32\inetsrv\
      C:\inetpub\

Step 3: Repair and Reset System State​

1. Use DISM to Repair Image:​

• Open Command Prompt as Administrator:
  
  Code:

  bash
       dism /online /cleanup-image /restorehealth

• Allow this command to check and replace corrupted system components.

2. Run System File Checker:​

bash
   sfc /scannow

• This will check for and repair corrupt system files.

3. Reboot the Server:​

• Once DISM/SFC succeed, confirm the server boots cleanly before retrying IIS removal steps.

Step 4: Boot Into Safe Mode​

1. Reboot into Safe Mode:​

• On reboot, press F8 or Shift + F8 (depending on server setup).
• Choose Safe Mode from the boot menu.

2. Use DISM or PowerShell to Retry IIS Removal:​

• Remove IIS again now that no IIS-related processes are active:
  
  Code:

  bash
       dism /online /disable-feature /featurename:IIS-WebServerRole /remove

Step 5: Fresh IIS Installation​

1. Reinstall IIS with its required tools:
   
   Code:

   bash
      Install-WindowsFeature Web-Server -IncludeAllSubFeature -IncludeManagementTools

2. Restart the server and ensure IIS is working correctly.

What Next If None of These Work?​

1. Share any error messages or logs from Event Viewer related to the failed roles, reboot, or installation processes.
   • Path to look at:
     
     Code:

          Applications and System in Event Viewer

2. Attempt an in-place upgrade repair of Windows Server, replacing all damaged components while keeping your configurations:
   • Mount the Windows Server 2025 ISO.
   • Run setup.exe and choose Upgrade this PC to repair the system.

Resolution Steps for Stuck IIS Removal​

Step 1: Analyze the Error in DISM Logs​

1. Open the DISM log file to identify the exact cause of the failure:
   • Location:
     
     Code:

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

   • Look for entries related to IIS-WebServer or disable-feature.
2. If you find entries indicating problematic components that DISM cannot disable, note them. Components such as IIS-ManagementTools or IIS-W3SVC modules are often the culprits.

Step 2: Use Safe Mode to Eliminate Dependency Locks​

1. Reboot the server and enter Safe Mode:
   • Restart and press F8 (or Shift+F8 for some setups).
   • Choose Safe Mode with Networking from the Advanced Boot Options menu.
2. Retry DISM from Safe Mode:
   
   Code:

   bash
      dism /online /disable-feature /featurename:IIS-WebServer /remove

3. If Safe Mode doesn’t work, proceed with the next steps below.

Step 3: Manually Remove IIS Files and Registry Keys​

1. Terminate IIS-Related Processes​

• Open Command Prompt as Administrator:
  
  Code:

  bash
     net stop W3SVC
     net stop IISADMIN
     net stop WAS

  • These commands stop the World Wide Web Publishing Service, IIS Admin service, and Windows Process Activation Service.

2. Delete IIS-Related Files​

• Navigate to these locations and delete them:
  
  Code:

     C:\inetpub
     C:\Windows\System32\inetsrv

• These directories contain the main IIS configurations and runtime files.

3. Remove IIS Registry Entries​

1. Open Registry Editor (regedit).
2. Navigate to:
   
   Code:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IISAdmin
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WAS

3. Delete the above keys one by one.
4. Reboot the server after removal to ensure a clean slate for IIS.

Step 4: Repair Windows Image​

1. Run Advanced DISM Repair:​

bash
   dism /online /cleanup-image /restorehealth

• This command will repair corrupted system files, which may be preventing IIS from being removed properly.

2. Follow With SFC Repair:​

bash
   sfc /scannow

• This checks and repairs system file integrity.

Step 5: Reinstall IIS​

1. Reinstall IIS from scratch:
   
   Code:

   bash
      Install-WindowsFeature Web-Server -IncludeAllSubFeature -IncludeManagementTools

2. Restart IIS and confirm it’s working:
   
   Code:

   bash
      iisreset

Alternative Solutions if All Else Fails​

1. Use In-Place Windows Upgrade:
   • This approach repairs all core Windows components (including IIS) while keeping your data intact.
   • Mount the Windows Server 2025 ISO and run setup.exe, selecting Upgrade this PC now.
2. Consider Starting Fresh:
   • If IIS removal remains impossible and server functionality is severely impacted, a clean rebuild of the server might be more efficient.

Let Me Know​

• Any relevant excerpts from the C:\Windows\Logs\DISM\dism.log file.
• Any specific error messages or behaviors during manual removal.

Steps to Resolve 0x800f0922 on .NET WCF Services​

Step 1: Reinstall NET-WCF-HTTP-Activation45 from DISM​

1. Open Command Prompt as Administrator.
2. Reinstall WCF HTTP Activation:
   
   Code:

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

3. Reinstall its dependencies (if needed):
   
   Code:

   bash
      dism /online /enable-feature /featurename:NET-Framework-45-Features /all

4. Reboot the server to apply the changes:
   
   Code:

   bash
      shutdown /r /t 0

Step 2: Repair .NET Framework 4.8 Components​

1. Run DISM for .NET Framework 4.8 Repair:
   
   Code:

   bash
      dism /online /cleanup-image /restorehealth

2. Perform a .NET Framework Repair:
   • Download and run the official .NET Framework Repair Tool:
     Download Here.
   • Follow the prompts to repair .NET Framework 4.8.

Step 3: Remove the WCF Feature Forcefully​

1. Use DISM to remove the feature directly:
   
   Code:

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

2. Manually clean up remnants:
   • Open Registry Editor (regedit) and navigate to:
     
     Code:

          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Net Framework Setup\NDP\v4\Full

   • Verify that the keys for .NET Framework 4.8 are intact. If corrupted, delete and reset them.
3. Reboot the server.

Step 4: Reset the Windows Servicing Stack​

1. Reset Windows Update Components:
   
   Code:

   bash
      net stop wuauserv
      net stop cryptSvc
      net stop bits
      net stop msiserver
      ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
      ren C:\Windows\System32\catroot2 catroot2.old
      net start wuauserv
      net start cryptSvc
      net start bits
      net start msiserver

2. Reboot the server, then retry uninstalling the WCF feature:
   
   Code:

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

Step 5: Check Windows Update for Pending Fixes​

1. Run:
   
   Code:

   bash
      wuauclt.exe /detectnow

   This manually triggers Windows Update.
2. Apply updates and reboot the server.

Step 6: Use SFC to Check and Repair System Files​

1. Run the following:
   
   Code:

   bash
      sfc /scannow

   • This will repair integral Windows system files, including .NET Framework components.
2. Afterward, retry the removal command:
   
   Code:

   bash
      dism /online /enable-feature /featurename:NET-Framework-45-Features /all

   0

Step 7: Logs and Additional Debugging​

1. Open the DISM log file:
   
   Code:

   bash
      dism /online /enable-feature /featurename:NET-Framework-45-Features /all

   1
   • Look for lines mentioning NET-WCF-HTTP-Activation45 or related errors to pinpoint dependencies causing the failure.
2. Check CBS.log:
   • Location:
     
     Code:

     bash
        dism /online /enable-feature /featurename:NET-Framework-45-Features /all

     2
   • Review for detailed servicing stack errors (e.g., missing components).

Next Steps After Resolving 0x800f0922​

1. Retrying IIS Removal:
   
   Code:

   bash
      dism /online /enable-feature /featurename:NET-Framework-45-Features /all

   3
2. Reattempt WSUS installation and postinstall once IIS and .NET are fully reset.

1. The feature is partially uninstalled or corrupted, leaving behind an invalid state.
2. The feature isn't listed as available because it's not part of the installed Windows Server features set due to component corruption or servicing issues.
3. The Windows feature store (Windows servicing stack) isn't properly synchronized or updated.

Resolution for 0x800f080c​

Step 1: Recheck Available Features List​

1. Run the following to list all available features:
   
   Code:

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

   • Look for a feature name like NET-WCF-HTTP-Activation45 or similar .NET Framework components.
2. If you do not see the specific feature listed, it may be because:
   • The feature was removed from the system or corrupted.
   • A valid source (e.g., an ISO or mounted installation media) is unavailable.

Step 2: Use an ISO Source to Restore Features​

1. Verify Windows Server ISO is Available:
   • Mount the Windows Server 2025 ISO (e.g., to drive D:).
2. Re-run DISM with Source Paths:
   • Point DISM explicitly to the installation media for .NET Framework 4.8:
     
     Code:

     bash
          dism /online /enable-feature /featurename:NET-WCF-HTTP-Activation45 /source:D:\sources\sxs /limitaccess

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

Step 3: Reset Servicing Stack​

1. Repair the Servicing Stack:
   • Run:
     
     Code:

     bash
          dism /online /cleanup-image /restorehealth

2. Resynchronize Features with the Feature Store:
   • Reset the servicing stack by renaming the SoftwareDistribution and Catroot2 folders:
     
     Code:

     bash
          net stop wuauserv
          net stop cryptSvc
          net stop bits
          net stop msiserver
          ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
          ren C:\Windows\System32\catroot2 catroot2.old
          net start wuauserv
          net start cryptSvc
          net start bits
          net start msiserver

3. Retry enabling or disabling the feature:
   
   Code:

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

Step 4: Manually Verify Components in Registry​

1. Open Registry Editor:
   
   Code:

      regedit

2. Navigate to:
   
   Code:

      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages

3. Search for any entries like:
   • Microsoft-Windows-NetFx4-WCF-HTTP-Activation
   • If found, inspect the state of the package. A Disabled or Partially Removed state suggests corruption.
4. If entries are incomplete, remove them and restart the system.

Step 5: Run SFC to Repair Missing System Files​

sfc /scannow

• If missing or corrupted files are found, Windows will attempt to replace them.

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

Step 6: Full In-Place Upgrade or Restore​

1. Mount Windows Server ISO.
2. Run setup.exe and choose Upgrade.
   • This will repair Windows while keeping your files and configurations intact.

Logs to Examine​

1. DISM Log:
   
   Code:

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

2. CBS.log:
   
   Code:

   bash
        dism /online /enable-feature /featurename:NET-WCF-HTTP-Activation45 /source:D:\sources\sxs /limitaccess

   0

Next Steps​

Steps to Resolve Unknown Feature (Feature Unavailable)​

Step 1: Verify If the Feature Exists in the Windows Image​

1. Run the following command to examine if the feature exists in the Windows Server installation:
   
   Code:

   bash
      dism /online /get-featureinfo /featurename:NET-WCF-HTTP-Activation45

   • If the error persists (The feature name is unknown), this confirms the system is missing references to this feature in its current configuration state.
2. List All Recognized Features:
   • Double-check the list of available features to confirm none are partially named:
     
     Code:

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

   • Search the output for similar names like NET-Framework45, WCF, or HTTP.

Step 2: Reset the Feature Store Using ISO​

1. Mount Windows Installation Media (ISO):
   • Mount the Windows Server 2025 ISO and note the drive letter (e.g., D:).
2. Rebuild the Feature Store:
   • Use DISM to repair $sources\sxs (Windows feature repository):
     
     Code:

     bash
          dism /online /enable-feature /featurename:NetFx4 /source:D:\sources\sxs /limitaccess

   • Retry enabling WCF HTTP Activation:
     
     Code:

     bash
          dism /online /enable-feature /featurename:NET-WCF-HTTP-Activation45 /source:D:\sources\sxs /limitaccess

3. Restart the server and recheck the feature store.

Step 3: Manually Investigate CBS and Servicing Stack​

1. Check CBS Logs for Errors:
   • Open:
     
     Code:

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

   • Search for Failed to find feature errors. This may hint at specific dependencies or services missing.
2. Force Reset the Servicing Stack:
   • Open Command Prompt as Administrator and run:
     
     Code:

     bash
          dism /online /cleanup-image /startcomponentcleanup

3. Retry enabling or disabling the feature:
   
   Code:

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

Step 4: Reinstall All .NET Framework Components​

1. Uninstall the .NET Framework 4.8 feature to reset dependencies:
   
   Code:

   bash
      dism /online /disable-feature /featurename:NetFx4 /remove

2. Reinstall .NET Framework:
   
   Code:

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

3. Reinstall WCF dependencies:
   
   Code:

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

Step 5: In-Place System Repair​

1. Use the mounted Windows Server 2025 ISO and run:
   • Run setup.exe and choose Upgrade this PC.
   • This will repair the Windows installation while keeping files and settings intact.

Key Logs and Further Debugging​

1. DISM Logs:
   
   Code:

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

   0
   • Look for lines mentioning the missing feature set, or why it is marked as unknown.
2. CBS Logs for pending feature state issues:
   
   Code:

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

   1

Next Steps​

1. The Component Store (WinSxS) has corruption.
2. There’s a dependency or feature lock caused by IIS or other services.
3. Pending system updates or servicing stack updates (SSUs) are missing or incomplete.

Steps to Fix 0x800f0922 for .NET 4.8 WCF Services HTTP Activation​

Step 1: Clear Pending Updates or Incomplete Feature Changes​

1. Delete Pending Servicing Operations:
   • Open Command Prompt as Administrator and run:
     
     Code:

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

2. Reset the Windows Update Component Store:
   • Stop update-related services:
     
     Code:

     bash
          net stop wuauserv
          net stop cryptSvc
          net stop bits
          net stop msiserver

   • Rename folders:
     
     Code:

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

   • Restart the services:
     
     Code:

     bash
          net start wuauserv
          net start cryptSvc
          net start bits
          net start msiserver

3. Reboot the Server and retry removing the WCF feature.

Step 2: Manually Stop Any Related Services​

1. Stop Related Services:
   
   Code:

   bash
      net stop W3SVC
      net stop WAS
      net stop NetTcpPortSharing

2. Re-attempt the uninstall:
   
   Code:

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

Step 3: Reset .NET Features​

1. Uninstall All .NET Related Features:
   
   Code:

   bash
      dism /online /disable-feature /featurename:NetFx4
      dism /online /cleanup-image /startcomponentcleanup

2. Reinstall .NET Framework 4.8:
   • Mount the Windows Server 2025 ISO and run:
     
     Code:

     bash
          dism /online /enable-feature /featurename:NetFx4 /source:D:\sources\sxs /limitaccess

Step 4: Repair Component Store​

1. Run Component Store Repair:
   
   Code:

   bash
      dism /online /cleanup-image /restorehealth

2. Retry Feature Removal:
   
   Code:

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

Step 5: Perform a Manual Cleanup​

1. Delete Registry Entries:​

1. Open regedit.
2. Navigate to:
   
   Code:

   bash
        net stop wuauserv
        net stop cryptSvc
        net stop bits
        net stop msiserver

   0
3. Find entries related to:
   • Microsoft-Windows-NetFx4-WCF-HTTP-Activation*.
   • Delete these entries.

2. Delete Files:​

1. Go to:
   
   Code:

   bash
        net stop wuauserv
        net stop cryptSvc
        net stop bits
        net stop msiserver

   1
2. Search for matching Microsoft.Net.WCF.HttpActivation directories and move them to a temporary backup.
3. Run:
   
   Code:

   bash
        net stop wuauserv
        net stop cryptSvc
        net stop bits
        net stop msiserver

   2

Step 6: Force Removal in Safe Mode​

1. Reboot into Safe Mode:
   • On reboot, press F8 or Shift + F8 and select Safe Mode.
2. Retry the removal in Safe Mode:
   
   Code:

   bash
        net stop wuauserv
        net stop cryptSvc
        net stop bits
        net stop msiserver

   3
3. Reboot into normal mode.

Step 7: Perform an In-Place Upgrade​

1. Mount the Windows Server 2025 ISO file.
2. Run setup.exe and choose Upgrade this PC.
   • This restores all system files and Windows features.
3. After the repair, retry the .NET WCF feature removal or installation process.

How to Verify Success​

1. Confirm the .NET feature state:
   
   Code:

   bash
        net stop wuauserv
        net stop cryptSvc
        net stop bits
        net stop msiserver

   4
   • Ensure NET-WCF-HTTP-Activation45 no longer appears.
2. Test .NET on IIS.
   • Restart IIS services:
     
     Code:

     bash
          net stop wuauserv
          net stop cryptSvc
          net stop bits
          net stop msiserver

     5

Key Logs to Investigate​

1. CBS Logs (CBS.log):
   
   Code:

   bash
        net stop wuauserv
        net stop cryptSvc
        net stop bits
        net stop msiserver

   6
2. DISM Logs (dism.log):
   
   Code:

   bash
        net stop wuauserv
        net stop cryptSvc
        net stop bits
        net stop msiserver

   7

Let Me Know!​