Windows 10 1709 Won't Upgrade / DISM Errors

I am trying to install a more current version of Windows 10 but everything I have tried has failed. I don't know if problems with sfc /scannow and DISM are related but the latter is also problematic. I ran chkdsk /f /r before attempting sfc and DISM.

What I Have Tried

1. From Windows Update, version 1803
2. From Windows Update, version 1903
3. From Windows Update, version 21H2
4. From a USB created by Windows Media Creator, version 22H2

Windows Image Repair Attempts

1. SFC /scannow returns the error:

   Windows Resource Protection found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. Forexample C:\Windows\Logs\CBS\CBS.log. Note that logging is currently notsupported in offline servicing scenarios.

2. DISM /online /cleanup-image /restorehealth returns the error:

   Error: 0x800f081f

   The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore thefeature. For more information on specifying a source location, seehttp://go.microsoft.com/fwlink/?LinkId=243077.

   The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

3. DISM /online /cleanup-image /restorehealth /source:D:\install.wim (from 22H2 iso) returns the error:

   Error: 0x800f081f

   The source files could not be found.Use the "Source" option to specify the location of the files that are required to restore thefeature. For more information on specifying a source location, seehttp://go.microsoft.com/fwlink/?LinkId=243077.

   The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

4. Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore returns

   Component Store (WinSxS) information:

   Windows Explorer Reported Size of Component Store : 9.42 GB

   Actual Size of Component Store : 9.09 GB

   Shared with Windows : 6.42 GBBackups and Disabled Features : 2.41 GBCache and Temporary Data : 252.40 MB

   Date of Last Cleanup : 2023-04-29 09:57:40

   Number of Reclaimable Packages : 0Component Store Cleanup Recommended : No

   The operation completed successfully.

Additional Information

I attempted to remedy my problems using the following guide (guide):

net stop bitsnet stop wuauservnet stop appidsvcnet stop cryptsvcDel "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\*.*"rmdir %systemroot%\SoftwareDistribution /S /Qrmdir %systemroot%\system32\catroot2 /S /Qregsvr32.exe /s atl.dllregsvr32.exe /s urlmon.dllregsvr32.exe /s mshtml.dllnetsh winsock resetnetsh winsock reset proxynet start bitsnet start wuauservnet start appidsvcnet start cryptsvc

In doing this, I discovered that appidsvc is not running and will not run because of a bad digital signature. I am not sure if this contributes to the problem or not

Additionally, in the CBS log, I found the following appear multiple times (which appear to be different sfc /scannow sessions):

00005f53 [SR] Repairing 4 components00005f54 [SR] Beginning Verify and Repair transaction00005f57 [SR] Cannot verify component files for Microsoft-Hyper-V-Drivers-Hypervisor, version 10.0.16299.1087, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, manifest is damaged (true)00005f5a [SR] Cannot verify component files for Microsoft-Hyper-V-3dVideo, version 10.0.16299.726, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, manifest is damaged (true)00005f5d [SR] Cannot verify component files for Microsoft-OneCore-IsolatedUserMode-Common, version 10.0.16299.1059, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, manifest is damaged (true)00005f60 [SR] Cannot verify component files for Microsoft-OneCore-IsolatedUserMode-Kernel, version 10.0.16299.699, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, manifest is damaged (true)00005f61 [SR] Repair complete00005f76 [SR] Committing transaction00005f7b [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

Upon seeing this, I figured I would try to remove Hyper-V to see what difference if any it would make. I received the following error when attempting to do so: The component store has been corrupted. Error 0x80073712

Additional Information

After trying to repair with an in-place "upgrade" of the same version, I received the following error. I am presently trying troubleshooting with guides I am finding online. I will report any new information as it comes.

0x80070004 – 0x3000DThe installation failed in the FIRST_BOOT phase with an error during MIGRATE_DATE operation.

Update

I found a setuperr.log in C:\$WINDOWS.~BT\Sources\Rollback. Here are its contents:

Error SP CSetupPlatformOSSwitchCheckpoint::Rollback: Deleting of "C:\Windows.old" directory failed.[gle=0x00000091]Error IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Rollback: Failed to create WinPE rollback directory: C:\$WINDOWS.~BT\Sources\Rollback\WinPE[gle=0x000000b7]

The file setupact.log has a lot of entries similar to the following:

 Warning SP SPMoveFileWithShortName: Failed to move \\?\c:\Windows\INF\3ware.PNF to \\?\c:\Windows.old\Windows\INF\3ware.PNF, error: 0x00000002

Information I didn't realize was important at the time

I had changed the Expandable String ValueProfilesDirectory in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList to a location other than the default.