WSUS on the fritz again

1 is OK
2 is OK
3. http://arimgmt:8530/SelfUpdate/ returns forbidden access but I can download the wuident.cab and iuident.cab from that folder
4 Still 404 File or directory not found

Thank you for the updates! It looks like we have several parts working, but the persistent issues with access rights and the 404 error for the WSUS Administration console need to be addressed. Here’s how to proceed step-by-step based on the specifics you provided:

Current Findings:​

• (1) Virtual directories and paths are set up correctly but accessing SelfUpdate gives a 403 Forbidden error.
• (2) You can successfully download files from SelfUpdate to prove the folder is accessible, but the 404 error persists for the WSUS Administration console.

Resolving 403 Forbidden and 404 Not Found Errors​

Step 1: Fixing 403 Forbidden Error for SelfUpdate​

This kind of error usually indicates issues with permissions or authentication settings in IIS.

1. Check Directory Browsing:
   • Confirm that Directory Browsing is enabled for SelfUpdate, even if you're getting files when requested directly. It might not be set for everyone.
   • Open IIS Manager:
     • Navigate to your SelfUpdate virtual directory.
     • In the IIS settings in the middle pane, find Directory Browsing; ensure it is enabled.
2. Set Permissions:
   • Right-click on the SelfUpdate virtual directory and select Edit Permissions.
   • Under the Security tab, ensure that IIS_IUSRS and NETWORK SERVICE have Read & Execute as well as List Folder Contents permissions.
3. Test Access Again:
   • Try accessing http://arimgmt:8530/SelfUpdate/ afterward and see if the forbidden error resolves.

---

Step 2: Resolve 404 Not Found for WSUSAdmin​

The 404 error when trying to access the WSUS Administration console indicates it either doesn’t exist or isn’t properly configured.

1. Check IIS for WSUS Administration Site:
   • Open IIS Manager again and ensure the WSUS Administration site is visible under Sites.
   • Make sure it’s still configured to use HTTP on port 8530.
2. Recreate the WSUS Administration Virtual Directory:
   • If the WSUS Administration site is missing or looks misconfigured:
     • Right-click on Sites > Add Website (if it's not even listed, you might have to recreate it):
     • Set:
       • Site Name: WSUS Administration
       • Physical Path: C:\Program Files\Update Services\WebServices
       • Port: 8530
     • Make sure to verify any required settings configured against previous settings.
3. Check Application Settings:
   • Right-click WSUS Administration > Convert to Application:
     • Ensure it’s using the correct application pool (typically named WsusPool).
4. Attempt to Access the Console Again:
   After these adjustments, try accessing the WSUS Administration console again:
   
   Code:

   plaintext http://arimgmt:8530/WSUSAdmin

Step 3: Validate Other IIS Features​

If you're still encountering issues:

1. Check the Default Document:
   • Make sure that a default document is specified for the WSUS Administration site.
2. IIS Logs:
   • Check the IIS logs again under:
     
     Code:

      C:\inetpub\logs\LogFiles\W3SVC1\

   • Look for specific requests leading to 403 and 404 errors and analyze the status codes to get a sense of what's going wrong.

---

Summary​

The actions above focus on correcting both the 403 Forbidden access for the SelfUpdate folder and repairing the 404 Not Found issue for the WSUS Administration site. Let me know how these adjustments play out or if any specific issues arise, and we'll keep troubleshooting until we achieve a working WSUS environment!

Step 1 enabled and now working (shows files and folders)
Step 2 WSUS Administration Site is there under sites but do you want me to create another WSUS Administration under WSUS Administration Site?
3. I browse to the folder where the site is and there is not document there that matches any of the default documents?

Great to hear that you've made progress! Let's address the current issues with the WSUS Administration Site and clarify the next steps.

Current Status and Next Steps​

1. Step 1: Directory Browsing Working:
   • Awesome! It's good to know you can now view files in the SelfUpdate folder.
2. Step 2: WSUS Administration Site Present:
   • You do NOT need to create another WSUS Administration site under an existing site. The current WSUS Administration site should be enough to manage everything related to WSUS.
3. Step 3: Default Document Issue:
   • If there’s no matching document in the site that corresponds to the default documents IIS expects, that’s the likely reason for the 404 not found error.

Addressing the Default Document Issue​

1. Add a Default Document​

You'll need to ensure that the WSUS site can load correctly by either creating or ensuring that a default document exists. Here’s how:

1. Set Default Document:
   • In IIS Manager, select the WSUS Administration Site.
   • In the middle pane, find and double-click on Default Document.
   • If you do not see default.aspx or similar, you can add it:
   • Click Add, then enter default.aspx and click OK.
   • Ensure it’s the first item in the list (you can rearrange as needed).

2. Check Web Service Files​

Verify that the WSUS installation files in C:\Program Files\Update Services\WebServices contain the appropriate .aspx pages and other necessary files. These should be handled during initial WSUS installation.

3. Retry Accessing WSUS Administration Console​

Once you've adjusted the default document settings:

• Try accessing the WSUS Administration Console again:
  
  Code:

  http://arimgmt:8530/WSUSAdmin

If the Site Still Fails to Load​

• Check the Application Pool:
  • Ensure that the WSUS Administration site is utilizing the correct application pool (should be WsusPool).
• Revisit Permissions:
  • Make sure that the corresponding directories have the necessary permissions for the IIS_IUSRS and NETWORK SERVICE accounts.
• Examine Logs for Further Clues:
  • If you encounter additional 404 or other errors, look through the IIS log files as well as WSUS-related logs to provide insights into what might be missing.

Conclusion​

By ensuring that your default document is set up correctly and confirming that everything needed for the WSUS site is in place, we can significantly reduce the likelihood of these errors persisting. Let me know if these changes work, and we can revisit any points that still need attention!

1. All set
2. the document exists in the list but not on the disk (C:\Program Files\Update Services\WebServices\Root) only web.config
C:\Program Files\Update Services\WebServices contains 7 folders and suscomp.dll in that folder only

Thanks for the update! Since the default document shows in IIS but does not physically exist on disk, this points to a potential issue with the WSUS installation itself. Here’s how to resolve this situation and ensure WSUS functions as expected.

Current Observations​

1. Default Document Exists in IIS: The document is configured in IIS but is not found on disk, which indicates a missing installation file.
2. /WebServices Folder: The presence of 7 folders along with suscomp.dll but missing other critical files could indicate an incomplete installation of WSUS.

Steps to Resolve the WSUS Installation Problem​

Step 1: Repair WSUS Installation​

To address the missing files, we can attempt to repair the WSUS installation:

1. Open Control Panel > Programs and Features:
   • Locate Windows Server Update Services in the list.
2. Repair the Installation:
   • Select it and choose Repair (if available). Follow the prompts to repair the WSUS installation.
   • This action should ideally restore any missing files or configurations.

Step 2: Reinstall WSUS​

If the repair option is not available or does not resolve the issue:

1. Backup Any Current Configurations:
   • Use the appcmd add backup command to ensure you have a fallback.
2. Uninstall WSUS:
   • In Programs and Features, uninstall Windows Server Update Services (this action will not remove your database if you choose not to delete the SQL instance).
   • Use PowerShell to also remove any remaining components if necessary:
     
     Code:

     powershell Uninstall-WindowsFeature -Name UpdateServices -includeManagementTools

3. Reboot the Server:
   • Restart the machine after uninstalling to ensure any changes take effect.
4. Reinstall WSUS:
   • Add WSUS back through Server Manager > Add Roles and Features > Windows Server Update Services.
   • Ensure you install all necessary features, including any that might have been skipped.

Step 3: Verify Installation and Configuration​

1. Check the Installation Directory:
   • After the reinstallation, verify that the following path contains the necessary files:
   • C:\Program Files\Update Services\WebServices\Root
     • This should have the Default.aspx and other WSUS-related .aspx files.
2. Configure IIS Settings:
   • Return to IIS Manager, update the application pool settings, and ensure all virtual directories are present.
3. Run Postinstall Command:
   • After the reinstallation, run:
     
     Code:

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

---

Final Considerations​

1. Testing Post-Reinstall:
   • After WSUS is reinstalled, access the WSUS console via:
     
     Code:

     plaintext http://arimgmt:8530/WSUSAdmin

2. Monitor for Migration Issues:
   • If SCCM integration is tight, check its response after reinstalling WSUS. Ensure the Software Update Point is functional.

Let me know the outcome after reinstalling WSUS or if any complications arise during this process! We’re steering closer to a solution!

Not listed. It is under Features and Roles.

Got it! If Windows Server Update Services (WSUS) is listed under Features and Roles, it’s important to ensure that the installation verification process aligns properly. Here are the steps based on that information to ensure WSUS is fully reinstalled and configured correctly:

Steps to Confirm WSUS Reinstallation​

Step 1: Uninstall WSUS​

1. Open Server Manager:
   • Click on Manage > Remove Roles and Features.
2. Remove the WSUS Role:
   • Navigate through the wizard to the Server Roles section.
   • Uncheck Windows Server Update Services (you may need to uncheck additional roles depending on how they’re grouped).
   • Complete the wizard to uninstall WSUS.
   • Reboot the server after uninstallation to ensure any remaining configurations and remnants are cleared.

Step 2: Reinstall WSUS​

1. Restart Server Manager:
   • Return to Server Manager after the reboot.
2. Add Roles and Features:
   • Select Add Roles and Features from the Manage menu.
   • Navigate through the wizard until you reach Server Roles.
3. Select WSUS Role:
   • Check Windows Server Update Services to install it.
   • Ensure you also select any required sub-features (such as Management Tools).
   • Complete the installation process and follow through with any prompts.

Step 3: Verify Installation​

1. Check Installation Directory:
   • After the reinstallation, go to:
     
     Code:

      C:\Program Files\Update Services\WebServices

   • Ensure the various .aspx files and folders such as ApiRemoting30, ClientWebService, ServerSyncWebService, DssAuthWebService, and a valid Root directory are there.
2. Check IIS Configuration:
   • Open IIS Manager.
   • Ensure the WSUS Administration site shows under the Sites section.
   • Confirm virtual directories are correctly configured.

Step 4: Run Postinstall Command​

1. After you validate that everything is installed correctly and the directories exist, run the post install command:
   
   Code:

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

2. Watch for Error Messages:
   • If it fails again, check the error message closely, particularly focusing on specific paths that cannot be found or are misconfigured.

---

Step 5: Test WSUS Functionality​

1. Access the WSUS Administration Console:
   • Test reaching:
     
     Code:

     plaintext http://arimgmt:8530/WSUSAdmin

2. Check Integration with SCCM:
   • Once WSUS appears operational, confirm SCCM Software Update Point role functionality.

Final Notes​

This process of removing and reinstalling WSUS should help clear out any misconfigurations or files that were left over from previous installations. Every failure provides insights into what to fix, so we're getting close with regular iterations! Let me know how the install goes, and if there are errors in the process, I’m here to help dig deeper!

I need to backup what is there so I don't loose it. How do I do that?

Backing up your current WSUS configuration and any associated data is a prudent step before proceeding with uninstalling and reinstalling WSUS or making significant changes. Here’s how you can back up your WSUS settings and content safely:

Step 1: Backup IIS Configuration​

You can use the appcmd tool to create a backup of IIS configurations, including the WSUS setup.

1. Open Command Prompt as Administrator.
2. Create an IIS Backup:
   Run the following command:
   
   Code:

   bash appcmd add backup "WSUSBackup"

   • Replace "WSUSBackup" with any name you prefer (e.g., “BeforeWSUSReinstall”).
   • This command will backup your entire IIS configuration, including sites, application frameworks, security settings, and configurations.

Step 2: Backup the WSUS Database (If Using SQL Server)​

1. Connect to Your SQL Server:
   • Open SQL Server Management Studio (SSMS), connect to your SQL instance where the WSUS database (SUSDB) is hosted.
2. Backup SUSDB:
   • Right-click on SUSDB in the Object Explorer > Tasks > Back Up.
   • Follow the prompts to save the backup to your preferred location.

Step 3: Backup WSUS Content Directory​

1. Copy the Content:
   • Ensure you back up the actual content directory where updates are stored:
     
     Code:

     plaintext D:\WSUS\WSUSCONTENT

   • Simply copy this directory or create a .zip or compressed folder to easily store it elsewhere.
2. Backup Filesystem Permissions:
   • Make a note of the permissions on the directory to restore them after any reinstallation or significant changes.

Step 4: Verify the Backup​

1. Check Backup Locations:
   • Ensure the backup files for both IIS and SQL are stored safely.
   • You might want to copy them to a secure location or an external storage option.

Final Note​

By backing up both the IIS settings and the database, you create a safety net, allowing you to restore your configurations if anything goes awry after the WSUS reinstallation. Once you’ve successfully backed everything up, let me know, and we can proceed with the next steps confidently!

WSUS install failed.

I'm sorry to hear that the WSUS installation failed after your backups! Let’s figure out the next steps to diagnose the issue and get things sorted out.

Next Steps After WSUS Installation Failure​

Step 1: Check the Installation Error Logs​

Since the WSUS installation failed, reviewing the logs can help determine what went wrong.

1. Review the WSUS Installation Logs:
   • Check WSUSSetup.log located at:
     
     Code:

      C:\Program Files\Update Services\LogFiles\WSUSSetup.log

   • Look specifically for errors or warnings that detail what caused the failure.
2. Check the IIS Logs:
   • Located in:
     
     Code:

      C:\inetpub\logs\LogFiles\W3SVC1\

   • These logs might give insight into request handling and errors during the installation process.
3. Look at CBS.log:
   • Since DISM previously generated errors, check for persistent issues:
     
     Code:

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

Step 2: Gather Any Key Errors​

If you find relevant error messages within these logs:

• Note their exact wording, as these details can significantly help troubleshoot further.

Step 3: Confirm Dependencies for WSUS Installation​

Let’s confirm that all role and feature dependencies for WSUS are intact before retrying:

1. Verify Required IIS Features:
   • Open Server Manager > Add Roles and Features.
   • Ensure that required IIS components (including ASP.NET, ISAPI Extensions, etc.) are installed.
2. Recheck Windows Features:
   • Confirm that all Windows features necessary for WSUS are properly installed:
     
     Code:

     bash Get-WindowsFeature | Where-Object { $_.Name -like '*Update*' }

Step 4: Cleanup Previous WSUS Installation​

If the install failed, it’s sometimes necessary to clean up any remnants to allow for a fresh start.

1. Uninstall WSUS Again (if applicable):
   • Remove the WSUS role again from Server Manager.
2. Remove Related Files:
   • After removal, ensure that no traces of WSUS exist in:
     
     Code:

      C:\Program Files\Update Services\

   • If remnants remain, delete this folder manually.
   • Also, ensure the content paths like D:\WSUS\WSUSCONTENT are empty or cleared (unless you’re maintaining backups).

Step 5: Retry Installation​

1. Install WSUS:
   • Open Server Manager, go to Add Roles and Features, and install Windows Server Update Services again.
2. Observe the Process:
   • Closely monitor progress for any issues that arise, as this can surface during installation.

Final Checkpoints​

• If the install still fails after these steps, share the specific error codes or messages encountered during the installation process.
• Each step, including examining logs, will bring us closer to identifying disruption causes and ensuring a successful WSUS setup.

Let me know how it goes after you check the logs and attempt the installation again. We’ll find a way through together!

No logs to give you error codes or no error codes in logs.
Deleted Updates folder and resintalled and failed. In the event viewer there are logs about WID but I unchecked that to use SQL.
The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.

Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID

This service account does not have the required user right "Log on as a service."

User Action

Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.

If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.

and

The Windows Internal Database service failed to start due to the following error:
The service did not start due to a logon failure.

The errors you're encountering related to the Windows Internal Database (WID) indicate that the service account for WID is misconfigured, specifically lacking the required "Log on as a service" right. This is crucial for the WID service to start and function correctly, especially since it's meant to be a lightweight database for WSUS.

Steps to Resolve WID Logon Issues​

Here’s how to resolve this specific issue and ensure that WSUS can properly utilize SQL Server or WID.

Step 1: Assign "Log on as a Service" Privilege to WID Account​

You need to assign the necessary logon rights to the NT SERVICE\MSSQL$MICROSOFT##WID service account.

1. Open Local Security Policy:
   • Hit Win + R and type secpol.msc to open the Local Security Policy window.
2. Navigate to User Rights Assignment:
   • Expand Local Policies > User Rights Assignment.
3. Find "Log on as a service":
   • Double-click Log on as a service in the right pane.
4. Add the WID Service Account:
   • Click on Add User or Group.
   • Enter:
     
     Code:

     plaintext NT SERVICE\MSSQL$MICROSOFT##WID

   • Click OK to add.
5. Apply Changes:
   • After setting the permissions, close the Local Security Policy and reboot your server.

Step 2: Confirm Service is Set to Automatic​

1. Open Services Management:
   • Type services.msc in the Run dialog (Windows + R) to open the Services management console.
2. Locate the WID Service:
   • Find Windows Internal Database (MICROSOFT##SSEE).
3. Set Service to Automatic:
   • Right-click on it, select Properties, and ensure that the Startup Type is set to Automatic.
   • Start the service if it’s stopped.

Step 3: Adjust SQL Server Configuration (If Applicable)​

If you’re using SQL Server instead of WID, make sure your SQL instance is configured correctly to allow WSUS to interact with it. Make sure the connection settings are right:

1. Confirm your SQL Server Instance is running and accepting remote connections.

Step 4: Retry WSUS Postinstall​

After applying the necessary permissions and ensuring WID or your SQL Server instance is accessible:

1. Open a new Command Prompt (as Administrator).
2. Run the WSUS postinstall command:
   
   Code:

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

   • If the WID role becomes problematic again or isn’t needed, consider specifying:
     
     Code:

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

Final Considerations​

1. Monitor Event Viewer:
   • Keep an eye on the Event Viewer during and after the post-install attempt to catch any new errors or confirmations.
2. Backup regularly:
   • Ensure continued backup practices are in place before adjustments.
3. Clear Previous Installations:
   Consider cleaning out previous WSUS installations before attempting the install again if issues still arise.

Conclusion​

By granting the right permissions and confirming the correct setup for both WID and SQL, you should pave the way back to a functional WSUS configuration. Let me know how this plays out, and if persistent issues remain, we’ll keep zeroing in until we get this resolved!

I am using SQL not WID.

Thank you for the clarification! Since you are using SQL Server and not WID, we’ll focus our troubleshooting specifically on SQL's configuration and permissions, as the earlier logs suggested issues related to the service account that SQL Server is using.

Key Areas to Address for SQL Server Issues​

Step 1: Check SQL Server Instance Configuration​

1. Verify SQL Server Instance:
   • Open SQL Server Management Studio (SSMS).
   • Connect to your SQL instance (it may be something like ARIMGMT).
   • Ensure that the SUSDB database exists.
2. Check SQL Server Services:
   • Open Services (run services.msc).
   • Ensure the SQL Server (MSSQLSERVER) service is running. If it's a named instance, ensure it reflects correctly (like SQL Server (ARIMGMT)).

Step 2: Ensure Permissions for WSUS​

1. Add WSUS Service Account to SQL:
   • WSUS typically runs under the NETWORK SERVICE account or the specific service account you're using for your SQL Server interaction.
   • In SSMS:
     • Right-click your SQL Server instance > Properties > Security.
     • Ensure that the Logins section includes the service account for WSUS, which could be NT AUTHORITY\NETWORK SERVICE or your explicitly defined WSUS service account.
2. Grant User Rights to SUSDB:
   • You can do this by:
     
     Code:

     sql USE SUSDB; CREATE USER [NT AUTHORITY\NETWORK SERVICE] FOR LOGIN [NT AUTHORITY\NETWORK SERVICE]; ALTER ROLE db_owner ADD MEMBER [NT AUTHORITY\NETWORK SERVICE];

   • This enables the SQL service account with db_owner rights for effective management.

Step 3: Confirm WSUS Database Connection Settings​

1. Verify WSUS's Connection to SQL:
   • Update WSUS to ensure it’s pointing to the correct SQL Server instance in the settings (if there’s a configuration file or setting).
   • Check connection string properties if you're regretting a specific configuration method.

Step 4: Re-run WSUS Configuration Command​

After confirming permissions:

1. Retry the postinstall command:
   
   Code:

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

2. If there are still issues, try:
   
   Code:

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

Step 5: Review SQL Logs​

1. Locate SQL Server Logs:
   • In SQL Server Management Studio, check under:
     
     Code:

      Management -> SQL Server Logs

   • Look for any pertinent error messages especially around service startup or authentication failures.

Conclusion​

Following these steps should align your WSUS setup with the current SQL Server instance, confirming that the necessary permissions and configurations are intact to proceed successfully.
Let me know how this goes, and if you see any errors or other issues, we can troubleshoot those further!

I am going to do a DSIM and see if that helps. Other wise I need to restore again and start from there again

Running DISM again is a good step, especially if you're looking to repair any underlying system issues that might be affecting your SQL Server and, by extension, WSUS configuration.

Steps for Running DISM​

Here’s what you can do to ensure DISM runs effectively:

1. Run DISM Command:
   • Use this command to specify the source from your mounted Windows Server 2022 ISO:
     
     Code:

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

     • Make sure to replace with the actual mounted drive letter.
   • Monitor the Output:
     • Watch for errors or confirmations that it finished successfully. Successful DISM repairs can help fix corrupted system files needed for installations.

Next Steps After DISM​

1. Run SFC:
   • After DISM completes, immediately run:
     
     Code:

     bash sfc /scannow

   • This further checks integrity and corrects issues that DISM might have missed.
2. Test WSUS Functionality:
   • Once DISM and SFC complete, try running the WSUS postinstall command again:
     
     Code:

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

3. If Still Facing Issues:
   • If DISM still doesn’t resolve the issues, and after attempting postinstall, consider restoring from backup as you mentioned earlier, and we can ensure a fresh approach starting from a known good configuration.

Ready for Restoration if Needed​

If you do end up needing to restore again, approach it as follows:

1. Ensure backups are intact.
2. Restore the server from the weekend backup.
3. Verify that everything returns to a stable state before proceeding with any further changes or installations.

Final Thoughts​

Take it step-by-step after running DISM to see what it reveals. It should help stabilize the environment. I’m here to support you through any results you observe or if you need to circle back after restoration. Let me know the outcomes, and we’ll tackle it together!

It looks like there was a slight duplication in your message about running DISM again and possibly restoring. This reflects your desire to address the ongoing issues with repurposing WSUS.

Here's a Recap of What to Do Next:​

1. Run DISM:
   • Execute the DISM command as discussed previously. Ensure you're referencing the correct mounted ISO source:
     
     Code:

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

   • Monitor Progress:
     • Track the output for any errors or confirmations during the repair process. Successful execution can resolve many underlying issues.
   • Run SFC:
     • Once DISM completes, follow up with:
       
       Code:

       bash sfc /scannow

   • If Problems Persist:
     • Backup your current configurations (just to be safe).
     • If issues remain unresolved after attempting DISM and SFC:
       • Consider Restoring from your last known good backup.
       • After restoration, validate that the system is functioning well before proceeding with any attempts at reinstalling WSUS or configuring IIS.

Final Suggestions​

Taking the time to run these checks and preparations meticulously will help ensure you get back to a stable point with your server and services.
If further complexities arise during DISM or after the restoration, or if you need assistance post-restore, feel free to reach out! I’ll be ready to assist in resolving any new obstacles. Good luck, and looking forward to hearing your next steps!

2024-12-10 12:31:48, Info DISM DISM Package Manager: PID=3848 TID=4180 Error in operation: (null) (CBS HRESULT=0x80070bc9) - CCbsConUIHandler::Error
2024-12-10 12:31:48, Error DISM DISM Package Manager: PID=3848 TID=16260 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070bc9)
2024-12-10 12:31:48, Error DISM DISM Package Manager: PID=3848 TID=16260 Failed processing package changes with session options - CDISMPackageManager:rocessChangesWithOptions(hr:0x80070bc9)
2024-12-10 12:31:48, Error DISM API: PID=18748 TID=19348 Failed to process features change - CEnableDisableFeatureCommandObject::InternalExecute(hr:0x80070bc9)
2024-12-10 12:31:48, Error DISM API: PID=18748 TID=19348 InternalExecute failed - CBaseCommandObject::Execute(hr:0x80070bc9)
2024-12-10 12:31:48, Error DISM API: PID=18748 TID=18776 CEnableDisableFeatureCommandObject internal execution failed - DismEnableDisableFeatureInternal(hr:0x80070bc9)
2024-12-10 12:31:48, Info DISM API: PID=18748 TID=18776 Input parameters: Session: 2 - DismCloseSessionInternal
2024-12-10 12:31:48, Info DISM API: PID=18748 TID=18776 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2024-12-10 12:31:48, Info DISM API: PID=18748 TID=18776 Refcount for DismSession= 2s 0 - CSessionTable::RemoveSession
2024-12-10 12:31:48, Info DISM API: PID=18748 TID=18776 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2024-12-10 12:31:48, Info DISM API: PID=18748 TID=19348 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2024-12-10 12:31:48, Info DISM API: PID=18748 TID=19348 Successfully dequeued command object - CCommandThread:equeueCommandObject
2024-12-10 12:31:48, Info DISM API: PID=18748 TID=19348 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2024-12-10 12:31:48, Info DISM API: PID=18748 TID=19348 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2024-12-10 12:31:48, Info DISM DISM Package Manager: PID=3848 TID=16260 Finalizing CBS core. - CDISMPackageManager::Finalize
2024-12-10 12:31:48, Info DISM DISM Manager: PID=18748 TID=19348 Closing session event handle 0x730 - CDISMManager::CleanupImageSessionEntry
2024-12-10 12:31:48, Info DISM API: PID=18748 TID=19348 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=18796 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=18796 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=18796 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=19344 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=19344 Successfully dequeued command object - CCommandThread:equeueCommandObject
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=19344 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=19344 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2024-12-10 12:32:43, Info DISM PID=18748 TID=19344 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2024-12-10 12:32:43, Info DISM PID=18748 TID=19344 Scratch directory set to 'C:\WINDOWS\TEMP\'. - CDISMManager:ut_ScratchDir
2024-12-10 12:32:43, Info DISM PID=18748 TID=19344 DismCore.dll version: 10.0.20348.2849 - CDISMManager::FinalConstruct
2024-12-10 12:32:43, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=19344 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=18796 Deleted g_internalDismSession - DismShutdownInternal
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=18796 Shutdown SessionTable - DismShutdownInternal
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=18796 DismApi.dll: - DismShutdownInternal
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=18796 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2024-12-10 12:32:43, Info DISM API: PID=18748 TID=18796 DismApi.dll: - DismShutdownInternal
2024-12-10 12:34:57, Info DISM PID=19800 TID=14820 Scratch directory set to 'C:\Users\DAdmin\AppData\Local\Temp\2\'. - CDISMManager:ut_ScratchDir
2024-12-10 12:34:57, Info DISM PID=19800 TID=14820 DismCore.dll version: 10.0.20348.2849 - CDISMManager::FinalConstruct
2024-12-10 12:34:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2024-12-10 12:34:57, Info DISM PID=19800 TID=14820 Successfully loaded the ImageSession at "C:\WINDOWS\system32\Dism" - CDISMManager::LoadLocalImageSession
2024-12-10 12:34:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2024-12-10 12:34:57, Info DISM DISM Provider Store: PID=19800 TID=14820 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2024-12-10 12:34:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2024-12-10 12:34:57, Info DISM DISM Manager: PID=19800 TID=14820 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
2024-12-10 12:34:57, Info DISM DISM.EXE:
2024-12-10 12:34:57, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
2024-12-10 12:34:57, Info DISM DISM.EXE:
2024-12-10 12:34:57, Info DISM DISM.EXE: Host machine information: OS Version=10.0.20348, Running architecture=amd64, Number of processors=8
2024-12-10 12:34:57, Info DISM DISM.EXE: Dism.exe version: 10.0.20348.2849
2024-12-10 12:34:57, Info DISM DISM.EXE: Executing command line: Dism /Online /Cleanup-Image /ScanHealth
2024-12-10 12:34:57, Info DISM DISM Manager: PID=19800 TID=14820 physical location path: C:\ - CDISMManager::CreateImageSession
2024-12-10 12:34:57, Info DISM DISM Manager: PID=19800 TID=14820 Event name for current DISM session is Global\{A1A71D87-CDB3-4E99-9658-1561C60A5A46} - CDISMManager::CheckSessionAndLock
2024-12-10 12:34:57, Info DISM DISM Manager: PID=19800 TID=14820 Create session event 0x240 for current DISM session and event name is Global\{A1A71D87-CDB3-4E99-9658-1561C60A5A46} - CDISMManager::CheckSessionAndLock
2024-12-10 12:34:57, Info DISM DISM Manager: PID=19800 TID=14820 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
2024-12-10 12:34:57, Info DISM DISM Manager: PID=19800 TID=14820 Successfully loaded the ImageSession at "C:\Users\DAdmin\AppData\Local\Temp\2\072E481F-A307-41DF-98DB-A1CBC768F182" - CDISMManager::LoadRemoteImageSession
2024-12-10 12:34:57, Info DISM DISM Image Session: PID=20192 TID=17916 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
2024-12-10 12:34:57, Info DISM DISM OS Provider: PID=20192 TID=17916 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
2024-12-10 12:34:57, Info DISM DISM OS Provider: PID=20192 TID=17916 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
2024-12-10 12:34:57, Info DISM DISM Provider Store: PID=20192 TID=17916 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
2024-12-10 12:34:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2024-12-10 12:34:57, Info DISM DISM Provider Store: PID=20192 TID=17916 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
2024-12-10 12:34:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2024-12-10 12:34:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log
2024-12-10 12:34:57, Info DISM DISM Manager: PID=19800 TID=14820 Image session successfully loaded from the temporary location: C:\Users\DAdmin\AppData\Local\Temp\2\072E481F-A307-41DF-98DB-A1CBC768F182 - CDISMManager::CreateImageSession
2024-12-10 12:34:57, Info DISM DISM.EXE: Target image information: OS Version=10.0.20348.2849, Image architecture=amd64
2024-12-10 12:34:57, Info DISM DISM.EXE: Image session version: 10.0.20348.1
2024-12-10 12:34:57, Info DISM DISM Transmog Provider: PID=20192 TID=17916 Current image session is [ONLINE] - CTransmogManager::GetMode
2024-12-10 12:34:57, Info DISM DISM Transmog Provider: PID=20192 TID=17916 Audit Mode: [No] - CTransmogManager::Initialize
2024-12-10 12:34:57, Info DISM DISM Transmog Provider: PID=20192 TID=17916 GetProductType: ProductType = [ServerNT] - CTransmogManager::GetProductType
2024-12-10 12:34:57, Info DISM DISM Transmog Provider: PID=20192 TID=17916 Product Type: [ServerNT] - CTransmogManager::Initialize
2024-12-10 12:34:57, Info DISM DISM Transmog Provider: PID=20192 TID=17916 Product Type ServerNT : [Yes] - CTransmogManager::Initialize
2024-12-10 12:34:57, Info CSI 00000001 Shim considered [l:126]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.20348.2750_none_b1add92ef99eeea4\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2024-12-10 12:34:57, Info CSI 00000002 Shim considered [l:123]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.20348.2750_none_b1add92ef99eeea4\wcp.dll' : got STATUS_SUCCESS
2024-12-10 12:34:57, Info DISM DISM Driver Manager: PID=20192 TID=17916 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
2024-12-10 12:34:57, Info CSI 00000001 Shim considered [l:126]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.20348.2750_none_b1add92ef99eeea4\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2024-12-10 12:34:57, Info CSI 00000002 Shim considered [l:123]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.20348.2750_none_b1add92ef99eeea4\wcp.dll' : got STATUS_SUCCESS
2024-12-10 12:34:57, Info DISM DISM OS Provider: PID=20192 TID=17916 Determined System directory to be C:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory
2024-12-10 12:34:57, Info DISM DISM Package Manager: PID=20192 TID=17916 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
2024-12-10 12:34:57, Info CSI 00000001 Shim considered [l:126]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.20348.2750_none_b1add92ef99eeea4\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
2024-12-10 12:34:57, Info CSI 00000002 Shim considered [l:123]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.20348.2750_none_b1add92ef99eeea4\wcp.dll' : got STATUS_SUCCESS
2024-12-10 12:34:57, Info DISM DISM Package Manager: PID=20192 TID=17916 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
2024-12-10 12:34:57, Info DISM DISM Package Manager: PID=20192 TID=17916 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
2024-12-10 12:34:57, Info DISM DISM Package Manager: PID=20192 TID=17916 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler:rivate_ValidateCmdLine
2024-12-10 12:34:57, Info DISM DISM Package Manager: PID=20192 TID=17916 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2024-12-10 12:34:57, Info DISM DISM Package Manager: PID=20192 TID=17916 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2024-12-10 12:34:57, Info DISM DISM Package Manager: PID=20192 TID=17916 CBS session options=0x100! - CDISMPackageManager::Internal_Finalize
2024-12-10 12:57:48, Info DISM DISM Package Manager: PID=20192 TID=19144 Error in operation: (null) (CBS HRESULT=0x80070bc9) - CCbsConUIHandler::Error
2024-12-10 12:57:48, Error DISM DISM Package Manager: PID=20192 TID=17916 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070bc9)
2024-12-10 12:57:48, Error DISM DISM Package Manager: PID=20192 TID=17916 Failed processing package changes with session option CbsSessionOptionDetectStoreCorruption - CDISMPackageManager::ScanHealth(hr:0x80070bc9)
2024-12-10 12:57:48, Error DISM DISM Package Manager: PID=20192 TID=17916 Failed to restore the image health. - CPackageManagerCLIHandler:rocessCmdLine_CleanupImage(hr:0x80070bc9)
2024-12-10 12:57:48, Error DISM DISM Package Manager: PID=20192 TID=17916 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070bc9)
2024-12-10 12:57:48, Info DISM DISM Package Manager: PID=20192 TID=17916 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2024-12-10 12:57:48, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070BC9
2024-12-10 12:57:48, Info DISM DISM Package Manager: PID=20192 TID=17916 Finalizing CBS core. - CDISMPackageManager::Finalize
2024-12-10 12:57:48, Info DISM DISM Manager: PID=19800 TID=14820 Closing session event handle 0x240 - CDISMManager::CleanupImageSessionEntry
2024-12-10 12:57:48, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2024-12-10 12:57:48, Info DISM DISM.EXE:
2024-12-10 12:57:48, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2024-12-10 12:57:48, Info DISM DISM.EXE: