WSUS on the fritz again

Uninstalling both WSUS and IIS entirely, then reinstalling them, can indeed help reset any configuration issues that may be causing persistent problems. Your plan to do this and then restore from the backup created earlier should cover all aspects needed to get everything functioning properly again.

Here’s a Step-by-Step Plan:​

Step 1: Backup Your Current IIS Configuration​

Before proceeding with uninstallation, ensure that your IIS configuration and any required settings are backed up.
  1. Open Command Prompt as Administrator.
  2. Run the Backup Command:
    Code: 
    bash
appcmd add backup "PreIISUninstallBackup"

Step 2: Uninstall WSUS and IIS​

  1. Through Server Manager:
    • Go to Manage > Remove Roles and Features.
    • Uncheck Windows Server Update Services under roles.
    • Also, uncheck Web Server (IIS) under server roles.
    • Follow through with prompts to complete the uninstallation.
    • Reboot when prompted to ensure any changes take effect.

Step 3: Verify Cleanup​

  1. Check for Remnant Files:
    • After reboot, verify that relevant directories like:
      Code: 
       C:\Program Files\Update Services\
C:\inetpub\wwwroot\WSUS\
      are completely cleared out, or consider manually deleting any remnants related to WSUS and IIS.

Step 4: Reinstall IIS​

  1. Add IIS Again:
    • Go back to Add Roles and Features in Server Manager.
    • Select Web Server (IIS) and include necessary features (be sure ASP.NET and others are checked).
    • Follow through with the installation.

Step 5: Reinstall WSUS​

  1. Add WSUS Again:
    • In Add Roles and Features, check Windows Server Update Services and include all the required features.
    • Complete the installation process and ensure no errors occur.

Step 6: Restore IIS Configuration​

  1. Restore Using AppCmd:
    Run the following command to restore your IIS configuration from backup:
    Code: 
    bash
appcmd restore backup "PreIISUninstallBackup"

Step 7: Check and Configure Again​

  1. Verify IIS Settings:
    • Open IIS Manager and ensure that the WSUS Administration site is present and configured correctly.
    • Check the virtual directories again for required configurations and access permissions.
  2. Final Configuration:
    • Run the WSUS postinstall command:
      Code: 
      bash
wsusutil.exe postinstall SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS"

Step 8: Test the Setup​

  1. Access the WSUS Administration Console:
    • Navigate to:
      Code: 
      plaintext
http://<YourServerName>:8530/WSUSAdmin
    • Confirm that the site loads without issues.
  2. Check SCCM Integration:
    • Verify the Software Update Point (SUP) in SCCM is working as expected after restoring configurations.

Summary​

  • Uninstalling both WSUS and IIS, then reinstalling with a clean configuration, can help resolve persistent errors.
  • Ensuring that you backup your current settings will allow quick recovery of any required configurations afterwards.
After taking these steps, let me know how the restore and reinstall efforts pan out. We’re progressively pushing through to a stable system—keep up the great work!
 
I understand how frustrating it is to still see the same error after going through all the trouble of uninstalling and reinstalling. The COMException (0x80070003) indicates that there are still issues involved with the paths or IIS configuration when running the WSUS postinstall command.

Let's Dive into More Focused Troubleshooting Steps:​

Step 1: Analyze IIS Configuration Thoroughly​

  1. Recheck the IIS Site Configuration:
    • Open IIS Manager.
    • Make sure the WSUS Administration site is present and properly set up.
    • Confirm that the following virtual directories are showing:
      • ApiRemoting30
      • ClientWebService
      • ServerSyncWebService
      • DssAuthWebService
    • If any are missing, recreate them as mentioned previously, ensuring that they point correctly to their physical paths.
  2. Physical Path Check:
    • Navigate directly in File Explorer to verify that the paths for each directory are indeed valid. Confirm:
      • For example, C:\Program Files\Update Services\WebServices\ClientWebService should physically exist.

Step 2: Review Application Pool Identity​

  1. Check Application Pool for WSUS:
    • In IIS, go to Application Pools.
    • Ensure that the WsusPool is running under the Network Service account or a specific service account with the right permissions.

Step 3: Check File Permissions​

  1. Validate Permissions:
    • Ensure that both IIS_IUSRS and NETWORK SERVICE have Read and Execute permissions on:
      • D:\WSUS
      • C:\Program Files\Update Services
  2. Default Document Settings:
    • Under IIS for the WSUS Administration site, check Default Document to ensure a valid document is set (like default.aspx).

Step 4: Retry WSUS Postinstall Command with Diagnostic Options​

  1. Run the Command Again:
    After ensuring pathways, permissions, and configurations are all correctly set:
    Code: 
    bash
wsusutil.exe postinstall SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS"
  2. If that fails, attempt with the -skipIISConfig option to bypass IIS setup:
    Code: 
    bash
wsusutil.exe postinstall -skipIISConfig SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS"

Step 5: Collect More Detailed Logs​

  1. If the error persists, checking more logs remains key:
    • IIS Logs in:
      Code: 
       C:\inetpub\logs\LogFiles\W3SVC1\
    • Look for request failure codes that align with your attempts.
  2. Event Viewer:
    • Check under Application logs for additional error messages that might provide insight into what's failing.

Final Thoughts​

If the steps above don’t yield success and the error persists, we could look into creating a more isolated environment for WSUS or directly reinstalling using a different method. Each piece of information gathered from logs can significantly help us unravel the longer-standing issues.
Please keep me posted on how things progress after trying these recommendations! We're committed to resolving this effectively.
 
I understand how frustrating it is to continue facing the same issue with WSUS despite the numerous troubleshooting steps we’ve gone through. Since the COMException (0x80070003) persists during the WSUS postinstall process, let's focus on isolating the specific cause.

Here’s a Consolidated Approach to Troubleshoot Further:​

Step 1: Confirm the Physical Path for WSUS​

  1. Ensure the Content Directory Exists:
    • Go to D:\WSUS\WSUSCONTENT using File Explorer.
    • Confirm that this directory is present and contains the necessary subfolders and files that WSUS requires.

Step 2: Check the Database Connection​

  1. Verify SQL Server Setup:
    • Ensure your SQL instance (e.g., ARIMGMT) is running and accessible.
    • Open SQL Server Management Studio (SSMS) and try connecting to your SQL instance.
    • Confirm that SUSDB exists and is intact.
  2. Test Database Access:
    • In SSMS, run:
      Code: 
      sql
USE SUSDB;
SELECT * FROM tbSchemaVersion;
    • If it connects successfully and returns results, the database setup is likely fine.

Step 3: Validate Permissions and Identity for SQL User​

  1. User Rights:
    • Open SQL Management Studio and right-click on the SUSDB database.
    • Navigate to Properties > Permissions, ensure that the account you’re using for WSUS has db_owner rights.
  2. Windows Service Configuration:
    • Make sure SQL Server service is set to use an appropriate account with permissions, typically NT AUTHORITY\NETWORK SERVICE.

Step 4: Configure or Repair IIS Specifically for WSUS​

  1. Check IIS Settings:
    • Open IIS Manager and verify that the WSUS Administration site is properly listed and bound to port 8530.
  2. Virtual Directory Configuration:
    • Ensure all necessary virtual directories are defined correctly and pointing to the correct physical paths.
  3. Temporary Removal & Recreation:
    • If some directories still present as application icons but not functioning, consider removing them and re-creating them as needed in IIS.

Step 5: Run Postinstall Command with Diagnostics​

  1. Execute Postinstall Command:
    • After verifying configurations and permissions, run the following once again:
      Code: 
      bash
wsusutil.exe postinstall SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS"
  2. Error Handling:
    If you see the same error again:
    • Attempt using:
      Code: 
      bash
wsusutil.exe postinstall -skipIISConfig SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS"

Step 6: Review Page File Access via IIS​

If issues continue to persist:
  1. Check Directory Browsing:
    • Revisit your access to:
      Code: 
      plaintext
http://localhost:8530/ClientWebService
    • Note whether it resolves correctly. If similar errors arise, permissions on these directories may still be problematic.

Step 7: Collect More Useful Logs​

  1. If the error persists, focus on the Event Viewer and IIS logs for any nuanced information indicating where configurations might be breaking.

Summary​

  • Confirm the accessibility of the content directory and paths expected by WSUS.
  • Validate that the SQL Server instance is operational and that WSUS has necessary permissions to interact with it.
  • Revisit and adjust IIS virtual directory configurations where necessary, and run the WSUS postinstall command again.
If these efforts do not yield results, providing specific errors or details from the logs after trying these steps can help narrow down the issue further. Let me know how everything goes! We’ll tackle this together!
 
That sounds like a solid plan! Ensuring that DISM returns no errors is crucial since it helps establish a stable foundation for your OS and avoids any corruption that might be affecting the WSUS installation and configuration process.

Steps to Ensure DISM Completes Successfully:​

  1. Run the DISM Command:
    • Use one of the following commands based on whether you’re pointing to mounted sources:
      Code: 
      bash
dism /online /cleanup-image /restorehealth /source:wim:<path_to_ISO>\sources\install.wim:1 /limitaccess
    • Ensure that you replace <path_to_ISO> with the correct mounted ISO drive letter.
  2. Monitor DISM Output:
    • Watch for successful healing messages or, if errors arise, document exactly what they are.
    • After DISM completes, run:
      Code: 
      bash
sfc /scannow
    • This will further check the integrity of system files and assist in repairing anything still amiss.

Follow Up​

Once you've ensured that DISM runs without errors, let me know the outcomes and if everything checked out well. We can then proceed with the WSUS setup or reinstallation steps armed with a stable environment.
Feel free to reach out anytime if questions arise during this process—I'm here to help! Good luck with the DISM run!
 
DSIM failed here are the error logs
2024-12-11 15:42:32, Info DISM DISM Package Manager: PID=28156 TID=28228 CBS session options=0x20100! - CDISMPackageManager::Internal_Finalize
2024-12-11 15:44:43, Info DISM DISM Package Manager: PID=28156 TID=28224 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
2024-12-11 15:44:43, Error DISM DISM Package Manager: PID=28156 TID=28228 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
2024-12-11 15:44:43, Error DISM DISM Package Manager: PID=28156 TID=28228 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2024-12-11 15:44:43, Error DISM DISM Package Manager: PID=28156 TID=28228 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
2024-12-11 15:44:43, Error DISM DISM Package Manager: PID=28156 TID=28228 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2024-12-11 15:44:43, Error DISM DISM Package Manager: PID=28156 TID=28228 Failed to restore the image health. - CPackageManagerCLIHandler:rocessCmdLine_CleanupImage(hr:0x800f081f)
2024-12-11 15:44:43, Error DISM DISM Package Manager: PID=28156 TID=28228 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2024-12-11 15:44:43, Info DISM DISM Package Manager: PID=28156 TID=28228 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2024-12-11 15:44:43, Info DISM DISM Package Manager: PID=28156 TID=28228 Finalizing CBS core. - CDISMPackageManager::Finalize
2024-12-11 15:44:43, Info DISM DISM Manager: PID=28120 TID=28124 Closing session event handle 0x234 - CDISMManager::CleanupImageSessionEntry
2024-12-11 15:44:43, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
2024-12-11 15:44:43, Info DISM DISM.EXE:
2024-12-11 15:44:43, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
2024-12-11 15:44:43, Info DISM DISM.EXE:
 
It looks like the DISM command is still encountering the 0x800f081f error, which indicates that the source files for the requested operations cannot be found. This issue suggests that there is likely a configuration or accessibility problem when DISM is trying to reference the specified paths or files.

Here’s how to address the 0x800f081f error:​

Step 1: Verify the Mounted ISO Again​

  1. Ensure the ISO is Properly Mounted:
    • Make sure you have the Windows Server 2022 ISO mounted correctly.
    • Confirm that the install.wim file exists in the path:
      Code: 
       D:\sources\install.wim
  2. Check for the Correct Index:
    • Run the following command to confirm the presence of the image and ensure the correct index number to use:
      Code: 
      bash
dism /Get-WimInfo /WimFile:D:\sources\install.wim
    • Take note of the index corresponding to your Windows edition (e.g., Standard, Datacenter).

Step 2: Explicitly Specify the Source When Running DISM​

Run the DISM command explicitly using the valid source and index:
Bash: 
dism /online /cleanup-image /restorehealth /source:wim:D:\sources\install.wim:<correct_index> /limitaccess
Replace <correct_index> with the appropriate index you found from the previous command.

Step 3: Allow Windows Update Access​

  1. Disable WSUS Temporarily:
    • Open Group Policy Editor (gpedit.msc).
    • Navigate to:
      Code: 
       Computer Configuration -> Administrative Templates -> Windows Components -> Windows Update
    • Disable the setting "Specify intranet Microsoft update service location".
    • Run:
      Code: 
      bash
gpupdate /force
  2. Retry Running DISM:
    Bash: 
    dism /online /cleanup-image /restorehealth
    This allows DISM to access Microsoft Update to retrieve files if local sources are still failing.

Step 4: Temporary FS Repair​

If the previous steps don’t succeed, consider troubleshooting your filesystem:
  1. Check Disk for Errors:
    Run a check disk operation:
    Code: 
    bash
chkdsk C: /f
    • This will check the integrity of your filesystem and fix any errors found.

Step 5: Look at CBS.log For Additional Clarity​

  1. After the above procedures, if DISM fails again, check:
    Code: 
     C:\Windows\Logs\CBS\cbs.log
  2. Focus on relevant lines around the time of failure—it may highlight missing files or particular components.

Final Notes​

This approach focuses on re-establishing access to necessary files, ensuring an orderly processing of repairs, and acknowledging the potential errors surrounding your installation. If issues remain after trying this, please let me know how the results pan out regarding DISM, and we’ll keep iterating until we reach a resolution!
 
Looks Like problem is with CBS Here is the errors
2024-12-12 08:17:20, Info CSI 00000004 CSI Store 2931893078896 initialized
2024-12-12 08:17:20, Info CSI 00000005 StoreCorruptionRepair transaction begun. WcpVersion: [l:38]'10.0.20348.2750 (WinBuild.160101.0800)'.
2024-12-12 08:17:20, Info CSI 00000006@2024/12/12:13:17:20.499 Starting corruption detection (InnerFlags=2)
2024-12-12 08:17:20, Info CBS FLOW: Entering stage: CheckCsi
2024-12-12 08:17:52, Info CSI 00000007 Hashes for file member [l:16]'IIS6 Manager.lnk' do not match.
Expected: {l:32 ml:33 b:c671aba9e75b1b9431e3331dd1f8a75f1e192d2570f72e58c64a594054d42693}.
Actual: {l:32 b:d372a543681d5d2b9f7c5a5be4099489bd8ba77b3e734029aaac5ecb3043bffc}.
2024-12-12 08:17:52, Info CSI 00000008 Warning: Unable to repair payload file ([l:16]'IIS6 Manager.lnk') for component ([l:94 ml:140]'amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.143_none_69b5e8a33c16ae8a') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:17:53, Info CSI 00000009 Hashes for file member [l:15]'IIS Manager.lnk' do not match.
Expected: {l:32 ml:33 b:65dc4556c43f8a4c693ba3e3fb8fa22a1b7138d2eb9b11411d0714da285c825e}.
Actual: {l:32 b:00bda0c9f045b1a7d1a9a32ff74ce2002a66e2edac81450254b67a0714fa8b54}.
2024-12-12 08:17:53, Info CSI 0000000a Warning: Unable to repair payload file ([l:15]'IIS Manager.lnk') for component ([l:100 ml:140]'amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.1787_none_302474c6ed69f247') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:17:53, Info CSI 0000000b Hashes for file member [l:23]'tls_branding_config.xml' do not match.
Expected: {l:32 ml:33 b:045852938e96aa28197993a6efc401407d94185aff8c13172ad3252ff711ba45}.
Actual: {l:32 b:49c898176d9ad8669bb1761a62e4fddb9da3b98f8cc3a311db7ac374bc4d2c37}.
2024-12-12 08:17:53, Info CSI 0000000c Warning: Unable to repair payload file ([l:23]'tls_branding_config.xml') for component ([l:101 ml:140]'amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1970_none_f6ceeebeb5fb9c23') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:18:14, Info CSI 0000000d Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
Expected: {l:32 ml:33 b:d89ab0d7cf6262145ab3517febd26dbb95297bdf0adb72d551746f4e409eb089}.
Actual: {l:32 b:cfa5c1d46b882f7980fbacca01c6cfe80aad5ec96392d3f839dbd7ef27f40321}.
2024-12-12 08:18:14, Info CSI 0000000e Warning: Unable to repair payload file ([l:20]'LServer_PKConfig.xml') for component ([l:101 ml:140]'amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2582_none_acb12089639c01ab') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:18:37, Info CSI 0000000f Hashes for file member [l:23]'tls_branding_config.xml' do not match.
Expected: {l:32 ml:33 b:045852938e96aa28197993a6efc401407d94185aff8c13172ad3252ff711ba45}.
Actual: {l:32 b:49c898176d9ad8669bb1761a62e4fddb9da3b98f8cc3a311db7ac374bc4d2c37}.
2024-12-12 08:18:37, Info CSI 00000010 Warning: Unable to repair payload file ([l:23]'tls_branding_config.xml') for component ([l:101 ml:140]'amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.2849_none_f6d5f2aab5f717fd') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:18:47, Info CSI 00000011 Hashes for file member [l:15]'IIS Manager.lnk' do not match.
Expected: {l:32 ml:33 b:65dc4556c43f8a4c693ba3e3fb8fa22a1b7138d2eb9b11411d0714da285c825e}.
Actual: {l:32 b:00bda0c9f045b1a7d1a9a32ff74ce2002a66e2edac81450254b67a0714fa8b54}.
2024-12-12 08:18:47, Info CSI 00000012 Warning: Unable to repair payload file ([l:15]'IIS Manager.lnk') for component ([l:100 ml:140]'amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.2849_none_30157808ed75d945') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:18:47, Info CSI 00000013 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
Expected: {l:32 ml:33 b:d89ab0d7cf6262145ab3517febd26dbb95297bdf0adb72d551746f4e409eb089}.
Actual: {l:32 b:cfa5c1d46b882f7980fbacca01c6cfe80aad5ec96392d3f839dbd7ef27f40321}.
2024-12-12 08:18:47, Info CSI 00000014 Warning: Unable to repair payload file ([l:20]'LServer_PKConfig.xml') for component ([l:101 ml:140]'amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2849_none_ac8c102563b8a389') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:18:49, Info CSI 00000015 Hashes for file member [l:16]'IIS6 Manager.lnk' do not match.
Expected: {l:32 ml:33 b:c671aba9e75b1b9431e3331dd1f8a75f1e192d2570f72e58c64a594054d42693}.
Actual: {l:32 b:d372a543681d5d2b9f7c5a5be4099489bd8ba77b3e734029aaac5ecb3043bffc}.
2024-12-12 08:18:49, Info CSI 00000016 Warning: Unable to repair payload file ([l:16]'IIS6 Manager.lnk') for component ([l:95 ml:140]'amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.2849_none_2962aeafe4645b4d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:19:20, Error CSI 00000017@2024/12/12:13:19:20.735 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2024-12-12 08:19:20, Info CSI 00000018 Direct SIL provider: Number of files opened: 129230.
2024-12-12 08:19:20, Info CSI 00000019@2024/12/12:13:19:20.770 Corruption detection complete. numCorruptions = 8, Disp = 1.
2024-12-12 08:19:21, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2024-12-12 08:19:21, Info CSI 0000001a@2024/12/12:13:19:21.155 CSI Transaction @0x2aaa15f5400 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id 'TI5.31149208_663159610:1/'

2024-12-12 08:19:21, Info CSI 0000001b@2024/12/12:13:19:21.156 CSI Transaction @0x2aaa15f5400 destroyed
2024-12-12 08:19:21, Info CBS Repr: CSI Store check completes
2024-12-12 08:19:21, Info CBS FLOW: Entering stage: CheckStagedPackages
2024-12-12 08:19:22, Info CBS Appl:Feature On Demand package without explicit comparator, using GE on build version
2024-12-12 08:19:22, Info CBS Appl:Feature On Demand package without explicit comparator, using GE on build version
2024-12-12 08:19:22, Info CBS Appl:LCU package and revision compare set to explicit
2024-12-12 08:19:22, Info CBS Package Format: PSFX
2024-12-12 08:19:22, Info CBS Delta Format: ForwardOnly
2024-12-12 08:19:22, Info CBS Generate playback status for m_fGeneratePlaybackDeltaWhenPackageHasReverseDeltas: 0
2024-12-12 08:19:22, Info CBS Generate playback status for m_fShouldGeneratePlaybackDeltas: 1
2024-12-12 08:19:22, Info CBS KIR Feature_PlaybackDeltaGeneration is enabled
2024-12-12 08:19:22, Info CBS Repr: Staged package check completes
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.1787_none_302474c6ed69f247\IIS Manager.lnk in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.1787_none_302474c6ed69f247, file IIS Manager.lnk from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1970_none_f6ceeebeb5fb9c23\tls_branding_config.xml in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1970_none_f6ceeebeb5fb9c23, file tls_branding_config.xml from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2582_none_acb12089639c01ab\LServer_PKConfig.xml in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2582_none_acb12089639c01ab, file LServer_PKConfig.xml from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.2849_none_f6d5f2aab5f717fd\tls_branding_config.xml in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.2849_none_f6d5f2aab5f717fd, file tls_branding_config.xml from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.2849_none_30157808ed75d945\IIS Manager.lnk in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.2849_none_30157808ed75d945, file IIS Manager.lnk from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.2849_none_2962aeafe4645b4d\IIS6 Manager.lnk in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.2849_none_2962aeafe4645b4d, file IIS6 Manager.lnk from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2849_none_ac8c102563b8a389\LServer_PKConfig.xml in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2849_none_ac8c102563b8a389, file LServer_PKConfig.xml from any local source
2024-12-12 08:19:22, Info CBS Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
2024-12-12 08:19:22, Info CBS Exec: Clients specified using local source only.
2024-12-12 08:19:22, Info CBS Repr: The system configuration is not qualified for Windows Update download, skip WU.
2024-12-12 08:19:22, Info CBS Failed to collect corrupted payload, try repair as much as possible [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Info CBS Repr: Finished collecting payload.
2024-12-12 08:19:22, Info CBS FLOW: Entering stage: RepairCbs
2024-12-12 08:19:22, Info CBS Repr: Finished repairing CBS Store.
2024-12-12 08:19:22, Info CBS FLOW: Entering stage: RepairCsi
2024-12-12 08:19:22, Info CSI 0000001c Creating NT transaction (seq 1)
2024-12-12 08:19:22, Info CSI 0000001d Created NT transaction (seq 1) result 0x00000000, handle @0x22ed4
2024-12-12 08:19:22, Info CSI 0000001e Transaction UoW: {62d49eeb-b886-11ef-b9a5-00155d02b302} for BeginTransaction
2024-12-12 08:19:22, Info CSI 0000001f@2024/12/12:13:19:22.795 Beginning NT transaction commit...
2024-12-12 08:19:22, Info CSI 00000020 Transaction UoW: {62d49eeb-b886-11ef-b9a5-00155d02b302} for CommitTransaction
2024-12-12 08:19:22, Info CSI 00000021@2024/12/12:13:19:22.800 CSI perf trace:
CSIPERF:TXCOMMIT;5651
2024-12-12 08:19:22, Info CSI 00000022 StoreCorruptionRepair transaction completed.
2024-12-12 08:19:22, Info CBS Repr: Finished repairing CSI store.
2024-12-12 08:19:22, Info CBS FLOW: Entering stage: RemoveStagedPackages
2024-12-12 08:19:22, Info CBS Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Info CBS
2024-12-12 08:19:22, Info CBS =================================
2024-12-12 08:19:22, Info CBS Checking System Update Readiness.
2024-12-12 08:19:22, Info CBS
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (l) (Fixed) amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.143_none_69b5e8a33c16ae8a\IIS6 Manager.lnk
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.1787_none_302474c6ed69f247\IIS Manager.lnk
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1970_none_f6ceeebeb5fb9c23\tls_branding_config.xml
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2582_none_acb12089639c01ab\LServer_PKConfig.xml
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.2849_none_f6d5f2aab5f717fd\tls_branding_config.xml
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.2849_none_30157808ed75d945\IIS Manager.lnk
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.2849_none_2962aeafe4645b4d\IIS6 Manager.lnk
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2849_none_ac8c102563b8a389\LServer_PKConfig.xml
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS
2024-12-12 08:19:22, Info CBS Summary:
2024-12-12 08:19:22, Info CBS Operation: Detect and Repair
2024-12-12 08:19:22, Info CBS Operation result: 0x800f081f
2024-12-12 08:19:22, Info CBS Last Successful Step: Remove staged packages completes.
2024-12-12 08:19:22, Info CBS Total Detected Corruption: 8
2024-12-12 08:19:22, Info CBS CBS Manifest Corruption: 0
2024-12-12 08:19:22, Info CBS CBS Metadata Corruption: 0
2024-12-12 08:19:22, Info CBS CSI Manifest Corruption: 0
2024-12-12 08:19:22, Info CBS CSI Metadata Corruption: 0
2024-12-12 08:19:22, Info CBS CSI Payload Corruption: 8
2024-12-12 08:19:22, Info CBS Total Repaired Corruption: 1
2024-12-12 08:19:22, Info CBS CBS Manifest Repaired: 0
2024-12-12 08:19:22, Info CBS CSI Manifest Repaired: 0
2024-12-12 08:19:22, Info CBS CSI Payload Repaired: 1
2024-12-12 08:19:22, Info CBS CSI Store Metadata refreshed: True
2024-12-12 08:19:22, Info CBS Staged Packages:
2024-12-12 08:19:22, Info CBS CBS Staged packages: 0
2024-12-12 08:19:22, Info CBS CBS Staged packages removed: 0
2024-12-12 08:19:22, Info CBS
2024-12-12 08:19:22, Info CBS Total Operation Time: 130 seconds.
2024-12-12 08:19:22, Info CBS Ensure CBS corruption flag is clear
2024-12-12 08:19:22, Info CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
2024-12-12 08:19:22, Info CBS CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download results: <none>
2024-12-12 08:19:22, Info CBS Count of times corruption detected: 1
2024-12-12 08:19:22, Info CBS Seconds between initial corruption detections: -1
2024-12-12 08:19:22, Info CBS Seconds between corruption and repair: -1
2024-12-12 08:19:22, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Info CBS Reboot mark cleared
2024-12-12 08:19:22, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2024-12-12 08:19:22, Info CBS Winlogon: Deregistering for CreateSession notifications
2024-12-12 08:19:22, Info CBS Exec: Processing complete, session(Corruption Repairing): 31149208_663159610 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Error CBS Session: 31149208_663159610 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Info CBS Session: 31149208_663159610 finalized. Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800f081f]
2024-12-12 08:19:22, Info CBS Deleting directory: \\?\C:\WINDOWS\CbsTemp\31149208_663159610\
2024-12-12 08:19:22, Info CBS Moving directory from \\?\C:\WINDOWS\CbsTemp\31149208_663159610\ to \\?\C:\WINDOWS\CbsTemp\{2B6A1075-C606-4D14-997D-A2FBE7AA6F87}
2024-12-12 08:19:22, Info CBS Deletion of: \\?\C:\WINDOWS\CbsTemp\{2B6A1075-C606-4D14-997D-A2FBE7AA6F87} successful
 
Server Update Services** as well.
  1. Check for Clean Removal:
    • After uninstalling, ensure that the following directories are deleted or emptied:
      Code: 
       C:\Program Files\Update Services\
C:\inetpub\wwwroot\WSUS\
  2. Reboot the server to apply changes.
  3. Reinstall IIS and WSUS:
    • Add the Web Server (IIS) role and then the WSUS role back through Server Manager.

Step 4: Utilize AppCmd for Backup and Restore​

After successful reinstallation and configuration:
  1. Use the appcmd utility to backup current IIS settings before making significant changes or configurations:
    Code: 
    bash
appcmd add backup "WSUS_BeforeReinstall"
  2. Proceed with the postinstall Command after reinstallation of WSUS:
    Code: 
    bash
wsusutil.exe postinstall SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS"

Summary​

The critical aspects moving forward are ensuring the integrity of components (like IIS), confirming necessary files are present and uncorrupted, and utilizing the proper source for any repairs.
If you can run a clean uninstall/reinstall, coupled with correct permissions and configuration checks, that should ultimately resolve these issues.
Please keep me posted on your progress, share new logs or error messages if they occur, and we can continue to troubleshoot until a resolution is achieved!
 
Got it! Since you're trying to repair the Windows image with DISM and are still encountering issues, let's focus on resolving this effectively. Given that you are receiving the 0x800f081f error, this indicates that DISM requires the correct source files to complete the operation. Here’s how to proceed:

Steps for Repairing with DISM​

Step 1: Prepare the Source WIM File​

  1. Ensure the ISO is Mounted Properly:
    • Confirm that your Windows Server 2022 ISO is mounted correctly and accessible.
    • Verify that the install.wim file exists:
    • Check the path to ensure it is available at:
      Code: 
       D:\sources\install.wim
  2. Check the Index:
    • Determine the index number for the correct image by using:
      Code: 
      bash
dism /Get-WimInfo /WimFile:D:\sources\install.wim
    • Take note of the specific index number corresponding to the installed version.

Step 2: Run DISM Using the Proper Source​

  1. Execute the DISM Command:
    Here’s the command again with the correct parameters to use the source:
    Code: 
    bash
dism /online /cleanup-image /restorehealth /source:wim:D:\sources\install.wim:<index_number> /limitaccess
    • Replace <index_number> with the correct value from the previous step.
  2. Monitor the Output:
    • Observe the DISM process for any errors or confirmation messages.

Step 3: Correcting Any Source File Issues​

If you continue to experience the 0x800f081f error:
  1. Try with ESD:
    If your mounted ISO has an install.esd file, try using that instead:
    Code: 
    bash
dism /online /cleanup-image /restorehealth /source:esd:D:\sources\install.esd:<index_number> /limitaccess
  2. Ensure Network Access:
    • Reconfirm your Windows Update settings. If you previously disabled WSUS, ensure that it allows access to Microsoft Update.

Step 4: Analyze CBS.log​

  1. Check for Corruption or Specific Errors:
    Review the CBS.log located at:
    Code: 
     C:\Windows\Logs\CBS\cbs.log
    • Look for entries during the time of the last DISM run to understand what specific files are causing problems.

Final Option: In-Place Upgrade Repair if DISM Fails​

If you still encounter barriers with DISM:
  1. Run setup.exe from the Mounted ISO:
    • Follow the prompted steps for an upgrade while keeping settings and files intact.
    • This method repairs missing files and corrupted components.

Conclusion​

Repairing the image through DISM is a solid way to ensure your Windows components are correct and operational. If the errors persist after carefully following these steps, there may be deeper issues requiring specialized attention through an in-place upgrade.
Let me know how the DISM command progresses, and what outcomes arise afterward. We’ll get this back on track!
 
I did this. The CBS Log is showing
2024-12-12 08:17:20, Info CSI 00000004 CSI Store 2931893078896 initialized
2024-12-12 08:17:20, Info CSI 00000005 StoreCorruptionRepair transaction begun. WcpVersion: [l:38]'10.0.20348.2750 (WinBuild.160101.0800)'.
2024-12-12 08:17:20, Info CSI 00000006@2024/12/12:13:17:20.499 Starting corruption detection (InnerFlags=2)
2024-12-12 08:17:20, Info CBS FLOW: Entering stage: CheckCsi
2024-12-12 08:17:52, Info CSI 00000007 Hashes for file member [l:16]'IIS6 Manager.lnk' do not match.
Expected: {l:32 ml:33 b:c671aba9e75b1b9431e3331dd1f8a75f1e192d2570f72e58c64a594054d42693}.
Actual: {l:32 b:d372a543681d5d2b9f7c5a5be4099489bd8ba77b3e734029aaac5ecb3043bffc}.
2024-12-12 08:17:52, Info CSI 00000008 Warning: Unable to repair payload file ([l:16]'IIS6 Manager.lnk') for component ([l:94 ml:140]'amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.143_none_69b5e8a33c16ae8a') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:17:53, Info CSI 00000009 Hashes for file member [l:15]'IIS Manager.lnk' do not match.
Expected: {l:32 ml:33 b:65dc4556c43f8a4c693ba3e3fb8fa22a1b7138d2eb9b11411d0714da285c825e}.
Actual: {l:32 b:00bda0c9f045b1a7d1a9a32ff74ce2002a66e2edac81450254b67a0714fa8b54}.
2024-12-12 08:17:53, Info CSI 0000000a Warning: Unable to repair payload file ([l:15]'IIS Manager.lnk') for component ([l:100 ml:140]'amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.1787_none_302474c6ed69f247') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:17:53, Info CSI 0000000b Hashes for file member [l:23]'tls_branding_config.xml' do not match.
Expected: {l:32 ml:33 b:045852938e96aa28197993a6efc401407d94185aff8c13172ad3252ff711ba45}.
Actual: {l:32 b:49c898176d9ad8669bb1761a62e4fddb9da3b98f8cc3a311db7ac374bc4d2c37}.
2024-12-12 08:17:53, Info CSI 0000000c Warning: Unable to repair payload file ([l:23]'tls_branding_config.xml') for component ([l:101 ml:140]'amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1970_none_f6ceeebeb5fb9c23') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:18:14, Info CSI 0000000d Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
Expected: {l:32 ml:33 b:d89ab0d7cf6262145ab3517febd26dbb95297bdf0adb72d551746f4e409eb089}.
Actual: {l:32 b:cfa5c1d46b882f7980fbacca01c6cfe80aad5ec96392d3f839dbd7ef27f40321}.
2024-12-12 08:18:14, Info CSI 0000000e Warning: Unable to repair payload file ([l:20]'LServer_PKConfig.xml') for component ([l:101 ml:140]'amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2582_none_acb12089639c01ab') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:18:37, Info CSI 0000000f Hashes for file member [l:23]'tls_branding_config.xml' do not match.
Expected: {l:32 ml:33 b:045852938e96aa28197993a6efc401407d94185aff8c13172ad3252ff711ba45}.
Actual: {l:32 b:49c898176d9ad8669bb1761a62e4fddb9da3b98f8cc3a311db7ac374bc4d2c37}.
2024-12-12 08:18:37, Info CSI 00000010 Warning: Unable to repair payload file ([l:23]'tls_branding_config.xml') for component ([l:101 ml:140]'amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.2849_none_f6d5f2aab5f717fd') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:18:47, Info CSI 00000011 Hashes for file member [l:15]'IIS Manager.lnk' do not match.
Expected: {l:32 ml:33 b:65dc4556c43f8a4c693ba3e3fb8fa22a1b7138d2eb9b11411d0714da285c825e}.
Actual: {l:32 b:00bda0c9f045b1a7d1a9a32ff74ce2002a66e2edac81450254b67a0714fa8b54}.
2024-12-12 08:18:47, Info CSI 00000012 Warning: Unable to repair payload file ([l:15]'IIS Manager.lnk') for component ([l:100 ml:140]'amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.2849_none_30157808ed75d945') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:18:47, Info CSI 00000013 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
Expected: {l:32 ml:33 b:d89ab0d7cf6262145ab3517febd26dbb95297bdf0adb72d551746f4e409eb089}.
Actual: {l:32 b:cfa5c1d46b882f7980fbacca01c6cfe80aad5ec96392d3f839dbd7ef27f40321}.
2024-12-12 08:18:47, Info CSI 00000014 Warning: Unable to repair payload file ([l:20]'LServer_PKConfig.xml') for component ([l:101 ml:140]'amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2849_none_ac8c102563b8a389') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:18:49, Info CSI 00000015 Hashes for file member [l:16]'IIS6 Manager.lnk' do not match.
Expected: {l:32 ml:33 b:c671aba9e75b1b9431e3331dd1f8a75f1e192d2570f72e58c64a594054d42693}.
Actual: {l:32 b:d372a543681d5d2b9f7c5a5be4099489bd8ba77b3e734029aaac5ecb3043bffc}.
2024-12-12 08:18:49, Info CSI 00000016 Warning: Unable to repair payload file ([l:16]'IIS6 Manager.lnk') for component ([l:95 ml:140]'amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.2849_none_2962aeafe4645b4d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2024-12-12 08:19:20, Error CSI 00000017@2024/12/12:13:19:20.735 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2024-12-12 08:19:20, Info CSI 00000018 Direct SIL provider: Number of files opened: 129230.
2024-12-12 08:19:20, Info CSI 00000019@2024/12/12:13:19:20.770 Corruption detection complete. numCorruptions = 8, Disp = 1.
2024-12-12 08:19:21, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2024-12-12 08:19:21, Info CSI 0000001a@2024/12/12:13:19:21.155 CSI Transaction @0x2aaa15f5400 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id 'TI5.31149208_663159610:1/'

2024-12-12 08:19:21, Info CSI 0000001b@2024/12/12:13:19:21.156 CSI Transaction @0x2aaa15f5400 destroyed
2024-12-12 08:19:21, Info CBS Repr: CSI Store check completes
2024-12-12 08:19:21, Info CBS FLOW: Entering stage: CheckStagedPackages
2024-12-12 08:19:22, Info CBS Appl:Feature On Demand package without explicit comparator, using GE on build version
2024-12-12 08:19:22, Info CBS Appl:Feature On Demand package without explicit comparator, using GE on build version
2024-12-12 08:19:22, Info CBS Appl:LCU package and revision compare set to explicit
2024-12-12 08:19:22, Info CBS Package Format: PSFX
2024-12-12 08:19:22, Info CBS Delta Format: ForwardOnly
2024-12-12 08:19:22, Info CBS Generate playback status for m_fGeneratePlaybackDeltaWhenPackageHasReverseDeltas: 0
2024-12-12 08:19:22, Info CBS Generate playback status for m_fShouldGeneratePlaybackDeltas: 1
2024-12-12 08:19:22, Info CBS KIR Feature_PlaybackDeltaGeneration is enabled
2024-12-12 08:19:22, Info CBS Repr: Staged package check completes
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.1787_none_302474c6ed69f247\IIS Manager.lnk in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.1787_none_302474c6ed69f247, file IIS Manager.lnk from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1970_none_f6ceeebeb5fb9c23\tls_branding_config.xml in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1970_none_f6ceeebeb5fb9c23, file tls_branding_config.xml from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2582_none_acb12089639c01ab\LServer_PKConfig.xml in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2582_none_acb12089639c01ab, file LServer_PKConfig.xml from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.2849_none_f6d5f2aab5f717fd\tls_branding_config.xml in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.2849_none_f6d5f2aab5f717fd, file tls_branding_config.xml from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.2849_none_30157808ed75d945\IIS Manager.lnk in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.2849_none_30157808ed75d945, file IIS Manager.lnk from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.2849_none_2962aeafe4645b4d\IIS6 Manager.lnk in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.2849_none_2962aeafe4645b4d, file IIS6 Manager.lnk from any local source
2024-12-12 08:19:22, Info CBS Failed to GetFile from WIM sandbox process [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Error CBS Failed to look for file WinSxS\amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2849_none_ac8c102563b8a389\LServer_PKConfig.xml in some alternate sources [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2024-12-12 08:19:22, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2849_none_ac8c102563b8a389, file LServer_PKConfig.xml from any local source
2024-12-12 08:19:22, Info CBS Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
2024-12-12 08:19:22, Info CBS Exec: Clients specified using local source only.
2024-12-12 08:19:22, Info CBS Repr: The system configuration is not qualified for Windows Update download, skip WU.
2024-12-12 08:19:22, Info CBS Failed to collect corrupted payload, try repair as much as possible [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Info CBS Repr: Finished collecting payload.
2024-12-12 08:19:22, Info CBS FLOW: Entering stage: RepairCbs
2024-12-12 08:19:22, Info CBS Repr: Finished repairing CBS Store.
2024-12-12 08:19:22, Info CBS FLOW: Entering stage: RepairCsi
2024-12-12 08:19:22, Info CSI 0000001c Creating NT transaction (seq 1)
2024-12-12 08:19:22, Info CSI 0000001d Created NT transaction (seq 1) result 0x00000000, handle @0x22ed4
2024-12-12 08:19:22, Info CSI 0000001e Transaction UoW: {62d49eeb-b886-11ef-b9a5-00155d02b302} for BeginTransaction
2024-12-12 08:19:22, Info CSI 0000001f@2024/12/12:13:19:22.795 Beginning NT transaction commit...
2024-12-12 08:19:22, Info CSI 00000020 Transaction UoW: {62d49eeb-b886-11ef-b9a5-00155d02b302} for CommitTransaction
2024-12-12 08:19:22, Info CSI 00000021@2024/12/12:13:19:22.800 CSI perf trace:
CSIPERF:TXCOMMIT;5651
2024-12-12 08:19:22, Info CSI 00000022 StoreCorruptionRepair transaction completed.
2024-12-12 08:19:22, Info CBS Repr: Finished repairing CSI store.
2024-12-12 08:19:22, Info CBS FLOW: Entering stage: RemoveStagedPackages
2024-12-12 08:19:22, Info CBS Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Info CBS
2024-12-12 08:19:22, Info CBS =================================
2024-12-12 08:19:22, Info CBS Checking System Update Readiness.
2024-12-12 08:19:22, Info CBS
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (l) (Fixed) amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.143_none_69b5e8a33c16ae8a\IIS6 Manager.lnk
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.1787_none_302474c6ed69f247\IIS Manager.lnk
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.1970_none_f6ceeebeb5fb9c23\tls_branding_config.xml
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2582_none_acb12089639c01ab\LServer_PKConfig.xml
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.20348.2849_none_f6d5f2aab5f717fd\tls_branding_config.xml
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-iis-managementconsole_31bf3856ad364e35_10.0.20348.2849_none_30157808ed75d945\IIS Manager.lnk
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-iis-legacysnapin_31bf3856ad364e35_10.0.20348.2849_none_2962aeafe4645b4d\IIS6 Manager.lnk
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.20348.2849_none_ac8c102563b8a389\LServer_PKConfig.xml
2024-12-12 08:19:22, Info CBS Repair failed: Missing replacement payload.
2024-12-12 08:19:22, Info CBS
2024-12-12 08:19:22, Info CBS Summary:
2024-12-12 08:19:22, Info CBS Operation: Detect and Repair
2024-12-12 08:19:22, Info CBS Operation result: 0x800f081f
2024-12-12 08:19:22, Info CBS Last Successful Step: Remove staged packages completes.
2024-12-12 08:19:22, Info CBS Total Detected Corruption: 8
2024-12-12 08:19:22, Info CBS CBS Manifest Corruption: 0
2024-12-12 08:19:22, Info CBS CBS Metadata Corruption: 0
2024-12-12 08:19:22, Info CBS CSI Manifest Corruption: 0
2024-12-12 08:19:22, Info CBS CSI Metadata Corruption: 0
2024-12-12 08:19:22, Info CBS CSI Payload Corruption: 8
2024-12-12 08:19:22, Info CBS Total Repaired Corruption: 1
2024-12-12 08:19:22, Info CBS CBS Manifest Repaired: 0
2024-12-12 08:19:22, Info CBS CSI Manifest Repaired: 0
2024-12-12 08:19:22, Info CBS CSI Payload Repaired: 1
2024-12-12 08:19:22, Info CBS CSI Store Metadata refreshed: True
2024-12-12 08:19:22, Info CBS Staged Packages:
2024-12-12 08:19:22, Info CBS CBS Staged packages: 0
2024-12-12 08:19:22, Info CBS CBS Staged packages removed: 0
2024-12-12 08:19:22, Info CBS
2024-12-12 08:19:22, Info CBS Total Operation Time: 130 seconds.
2024-12-12 08:19:22, Info CBS Ensure CBS corruption flag is clear
2024-12-12 08:19:22, Info CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
2024-12-12 08:19:22, Info CBS CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download results: <none>
2024-12-12 08:19:22, Info CBS Count of times corruption detected: 1
2024-12-12 08:19:22, Info CBS Seconds between initial corruption detections: -1
2024-12-12 08:19:22, Info CBS Seconds between corruption and repair: -1
2024-12-12 08:19:22, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Info CBS Reboot mark cleared
2024-12-12 08:19:22, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2024-12-12 08:19:22, Info CBS Winlogon: Deregistering for CreateSession notifications
2024-12-12 08:19:22, Info CBS Exec: Processing complete, session(Corruption Repairing): 31149208_663159610 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Error CBS Session: 31149208_663159610 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Info CBS Session: 31149208_663159610 finalized. Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-12-12 08:19:22, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800f081f]
2024-12-12 08:19:22, Info CBS Deleting directory: \\?\C:\WINDOWS\CbsTemp\31149208_663159610\
2024-12-12 08:19:22, Info CBS Moving directory from \\?\C:\WINDOWS\CbsTemp\31149208_663159610\ to \\?\C:\WINDOWS\CbsTemp\{2B6A1075-C606-4D14-997D-A2FBE7AA6F87}
2024-12-12 08:19:22, Info CBS Deletion of: \\?\C:\WINDOWS\CbsTemp\{2B6A1075-C606-4D14-997D-A2FBE7AA6F87} successful
2024-12-12 08:21:23, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2024-12-12 08:21:23, Info CBS TiWorker signaled for shutdown, going to exit.
2024-12-12 08:21:23, Info CBS Deleting the contents of directory: \\?\C:\WINDOWS\CbsTemp
2024-12-12 08:21:23, Info CBS Deletion of: \\?\C:\WINDOWS\CbsTemp successful
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2024-12-12 08:21:23, Info CBS Execution Engine Finalize
2024-12-12 08:21:23, Info CBS Execution Engine Finalize
2024-12-12 08:21:23, Info CBS Lock: Lock removed: TiWorkerClassFactory, level: 30, total lock:3
2024-12-12 08:21:23, Info CBS Lock: Lock removed: CCbsWorker, level: 5, total lock:2
2024-12-12 08:21:23, Info CBS Ending the TiWorker main loop.
2024-12-12 08:21:23, Info CBS Starting TiWorker finalization.
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2024-12-12 08:21:23, Info CBS CBS Engine already deactivated
2024-12-12 08:21:23, Info CBS CBS Engine already deactivated
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: CoreResourcesUnload
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: SessionManagerFinalize
2024-12-12 08:21:23, Info CBS Lock: Lock removed: CSIInventoryCriticalSection, level: 64, total lock:10
2024-12-12 08:21:23, Info CBS Lock: Lock removed: CCbsSessionManager, level: 11, total lock:9
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: WcpUnload
2024-12-12 08:21:23, Info CSI 00000023 Direct SIL provider: Number of files opened: 4.
2024-12-12 08:21:23, Info CSI 00000024 Direct SIL provider: Number of files opened: 2.
2024-12-12 08:21:23, Info CSI 00000025 Direct SIL provider: Number of files opened: 66755.
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: DrupUnload
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: CfgMgr32Unload
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: DpxUnload
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: TurboStackUnload
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: CbsEsdUnload
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: CbsOneSettingsFinalize
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: CbsEventUnregister
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: AppContainerUnload
2024-12-12 08:21:23, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2024-12-12 08:21:23, Info CBS Ending TiWorker finalization.
2024-12-12 08:21:23, Info CBS Ending the TrustedInstaller main loop.
2024-12-12 08:21:23, Info CBS Starting TrustedInstaller finalization.
2024-12-12 08:21:23, Info CBS Winlogon: Stopping notify server
2024-12-12 08:21:23, Info CBS Winlogon: Unloading SysNotify DLL
2024-12-12 08:21:23, Info CBS Lock: Lock removed: WinlogonNotifyLock, level: 8, total lock:6
2024-12-12 08:21:23, Info CBS Ending TrustedInstaller finalization.
 
Thank you for sharing the detailed log output. Based on these entries, particularly the continuous 0x800f081f error, it becomes evident that there are crucial files in the CBS (Component-Based Servicing) store that DISM cannot access or repair, particularly related to IIS and WSUS functionalities.

Breakdown of the Core Issues:​

  1. Corrupted or Missing Files:
    • The log entries indicate that action was taken on files like IIS6 Manager.lnk, which cannot be found or repaired.
    • The overall message suggests that necessary replacement files are missing from the expected locations.

Key Steps to Address These Issues​

Step 1: Access the CBS.log Directly​

  1. Examine CBS.log:
    • Open the CBS.log located at:
      Code: 
       C:\Windows\Logs\CBS\cbs.log
    • Look for specific error messages regarding file paths that could pinpoint missing components. Prioritize details concerning corruption status and missing paths that could relate back to your setup and configuration.

Step 2: Attempt to Repair the System from ISO Again​

  1. Ensure the ISO is Mounted:
    • Confirm that the Windows Server 2022 ISO is mounted correctly and accessible.
  2. Run the following DISM command again with the correct source:
    • Using the correct index:
      Code: 
      bash
dism /online /cleanup-image /restorehealth /source:wim:D:\sources\install.wim:<correct_index> /limitaccess
      Ensure that the <correct_index> corresponds to the version of Windows Server 2022 that your installation is currently using.

Step 3: Use a Different Repair Option​

If the DISM commands continue to fail:
  1. Perform an In-Place Upgrade Repair:
    • Running setup.exe from your mounted ISO will allow the installer to replace any corrupted system files while preserving existing applications and settings.
      Code: 
      bash
D:\setup.exe
    • Select the Upgrade option during the installation process.

Potential Last Resort​

This method often resolves unresolvable component issues by refreshing the system without full reinstallation.

Step 4: Reassess the WSUS Installation Requirements​

If after all fixes WSUS still fails to install:
  1. Check for Dependencies:
    • Ensure all prerequisites are intact and review IIS settings specifically for WSUS before trying another install.

Next Steps​

  • Look into the CBS.log for specifics of what files are corrupt or missing.
  • Try the previously mentioned DISM commands and, if they continue to fail, shift to the in-place repair with the ISO.
Let me know how it all goes and if you have specifics from the CBS logs or any new error codes after these efforts! We’re working to get this resolved together!
 
That sounds like a reasonable approach! An in-place upgrade can be a powerful solution to restore any missing or corrupted files, especially when DISM and SFC have not resolved the issues effectively.

Steps for Performing the In-Place Upgrade​

  1. Ensure the Windows Server 2022 ISO is Mounted:
    • Verify that the ISO is accessible. If you haven't already, mount the ISO file on your server.
  2. Run the Setup:
    • Open a command prompt or navigate to the mounted ISO in File Explorer.
    • Execute the following command:
      Code: 
      bash
D:\setup.exe
      (Make sure to replace D: with the drive letter your ISO is assigned to.)
  3. Follow the Installation Wizard:
    • Select Upgrade this PC now and follow the prompts to keep your files and applications intact.
  4. Complete the Upgrade:
    • The upgrade process may take some time, depending on your server's resources. Follow any on-screen instructions.
  5. Post-Upgrade Verification:
    • After the upgrade is complete, check if WSUS functions correctly:
      • Attempt to access the WSUS Administration Console via:
        Code: 
        plaintext
http://arimgmt:8530/WSUSAdmin
    • Run the WSUS postinstall command again:
      Code: 
      bash
wsusutil.exe postinstall SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS"
  6. Monitor Logs for Errors:
    • Once upgraded, if issues appear, examine WSUSSetup.log and IIS logs for any persistent configuration mistakes.

Conclusion​

By running the in-place upgrade, you should resolve many underlying issues without significantly disturbing your current configurations. Let me know how it goes or if any blockers surface during the process! We’re aiming for a fully functional WSUS setup soon!
 
Ran inplace upgrade and then DSIM to check and all is good.
Ran wsusutil.exe postinstall SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS"
Still failed with same error.
 
I appreciate the update! It’s great to hear that after the in-place upgrade, DISM ran successfully and checked out okay. However, I understand the frustration of still encountering the same "The system cannot find the path specified" error when executing the postinstall command for WSUS.

Focused Next Steps to Diagnose and Resolve the Issue​

Step 1: Validate Current Paths and Permissions​

  1. Confirm CONTENT_DIR:
    • Make sure the directory D:\WSUS exists and contains the necessary WSUS folders. The complete path should ideally include any expected subdirectories required for updates.
  2. Check Folder Permissions:
    • Ensure that the D:\WSUS directory has the right permissions set:
      • Right-click on the directory > Properties > Security tab.
      • Include accounts like IIS_IUSRS, NETWORK SERVICE, and ensure they have Read, Write, and Modify permissions.

Step 2: Investigate the WSUS Directory Structure​

  1. Look Inside D:\WSUS / Expected Files:
    • Ensure the expected files and folders are present:
      • WSUS might rely on the structure like:
      • Content (which should be populated after postinstall).
      • Other folders related to updates and configurations.

Step 3: SQL Server Configuration Check​

Since you are using SQL:
  1. Database Connection:
    • Double-check the connection to your SQL Server instance (ARIMGMT):
      • Open SQL Management Studio (SSMS) and connect to the instance.
      • Run a query against the SUSDB database:
        Code: 
        sql
USE SUSDB;
SELECT * FROM tbSchemaVersion;
    • Validate that you can retrieve data confirming that the database and its structure are intact.
  2. User Permissions:
    • Confirm the WSUS-related SQL Server account has db_owner permissions on SUSDB.

Step 4: Review Your WSUS Setup Configuration​

  1. Remove/Regenerate IIS Virtual Directories:
    • If virtual directories for WSUS are not linked correctly, follow these steps:
      • Open IIS Manager > Right-click on WSUS Administration > Check its virtual directories like ClientWebService, ApiRemoting30, etc.
      • Remove problematic virtual directories and re-add them as demonstrated before.

Step 5: Retry WSUS Postinstall Command​

  1. Final Attempt:
    After ensuring everything is correctly configured and permissions are intact, reattempt the WSUS postinstall:
    Bash: 
    wsusutil.exe postinstall SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS"
  2. If continues failing, adding -skipIISConfig as discussed earlier:
    Bash: 
    wsusutil.exe postinstall -skipIISConfig SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS"

Final Thoughts​

It’s crucial that all aspects—directory structures, permissions, SQL database configurations—align properly for WSUS to function without errors. If after these steps the installation doesn't succeed and logs still show the same error, revisit any setups or layers that might obscure correct operation.
Please keep me updated on the latest outcomes from these checks, and if you have specific log entries that clarify the issue, sharing those will help greatly in troubleshooting further!
 
Thanks for the update. It’s encouraging to hear that the in-place upgrade and DISM checks went well, but I understand your frustration at still encountering the same error with the WSUS postinstall command.

Key Issues Recap​

The persistent error—“The system cannot find the path specified”—indicates unresolved issues with either the paths referenced in the command or lingering misconfigurations in IIS or the SQL connection.

Detailed Steps to Resolve WSUS Postinstall Issues​

Step 1: Verify the Content Directory Structure​

  1. Confirm Directory Exists:
    • Navigate to D:\WSUS in File Explorer. Ensure that D:\WSUS\WSUSCONTENT exists and contains appropriate subdirectories for WSUS updates.
  2. Path Confirmation:
    • Ensure that Content, Updates, or other necessary WSUS-related folders are present. If the directory structure is incorrect or missing, WSUS will not function correctly.
  3. Check Directory Permissions:
    • Right-click on D:\WSUS and go to Properties > Security.
    • Ensure that the service accounts needed for WSUS (such as NETWORK SERVICE) have Read, Write, and Modify permissions.

Step 2: Validate SQL Server Setup​

  1. Check SQL Instance Configuration:
    • Open SQL Server Management Studio (SSMS).
    • Confirm that your SQL instance ARIMGMT is running and that SUSDB exists.
  2. SQL Permissions:
    • Make sure that the WSUS service account has the necessary permissions (at least db_owner) for the SUSDB database. You can do this in SSMS:
      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];

Step 3: Check IIS Configuration Before Retry​

  1. Open IIS Manager:
    • Ensure that your WSUS Administration site is visible under Sites.
  2. Review Application Pools:
    • Confirm that the WsusPool is running under the correct identity (typically NetworkService).
  3. Verify Virtual Directories:
    • Right-click on WSUS Administration and check all virtual directories:
      • ClientWebService
      • ApiRemoting30
      • ServerSyncWebService
    • Each must point to valid paths on your system.

Step 4: Retry the Postinstall Command​

  1. Run:
    Code: 
    bash
wsusutil.exe postinstall SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS\WSUSCONTENT"
  2. With Skip Option:
    If it still fails, try:
    Code: 
    bash
wsusutil.exe postinstall -skipIISConfig SQL_INSTANCE_NAME="ARIMGMT" CONTENT_DIR="D:\WSUS\WSUSCONTENT"

Step 5: Collect Additional Logs​

If the postinstall command fails again:
  • Check the IIS logs for specific failed requests in:
    Code: 
     C:\inetpub\logs\LogFiles\W3SVC1\
  • Once again, review the specific event logs in Event Viewer under Applications, which may provide more context around WSUS’s failures.

Final Thoughts​

The issues typically revolve around misconfigured paths or services not having the correct access to components it relies on. Working through these checks should help nail down the issues you’re facing.
Let me know how these steps worked out, and feel free to share any new error messages or results from the logs as you go! We’ll get WSUS back online smoothly!
 
You must log in or register to reply here.

Similar threads

AA20-283A: APT Actors Chaining Vulnerabilities Against SLTT, Critical Infrastructure, and Elections Organizations
Replies
0
Views
3K
News
VIDEO Announcing Windows 10 Insider Preview Build 21364
Replies
0
Views
1K
News
Announcing Windows 10 Insider Preview Build 21277
Replies
0
Views
2K
News
  • Solved
Windows 7 Complex Problem with Windows 7 (again)
2
Replies
30
Views
5K
kemical
Announcing Windows 10 Insider Preview Build 17704
Replies
0
Views
2K
News