2

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 some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported 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 the feature. For more information on specifying a source location, see http://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 the feature. For more information on specifying a source location, see http://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 GB
    Backups and Disabled Features : 2.41 GB
    Cache and Temporary Data : 252.40 MB
    

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

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

    The operation completed successfully.


Additional Information

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

net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc
Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\*.*"
rmdir %systemroot%\SoftwareDistribution /S /Q
rmdir %systemroot%\system32\catroot2 /S /Q
regsvr32.exe /s atl.dll
regsvr32.exe /s urlmon.dll
regsvr32.exe /s mshtml.dll
netsh winsock reset
netsh winsock reset proxy
net start bits
net start wuauserv
net start appidsvc
net 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 components
00005f54 [SR] Beginning Verify and Repair transaction
00005f57 [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 complete
00005f76 [SR] Committing transaction
00005f7b [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 – 0x3000D
The 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 Value ProfilesDirectory in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList to a location other than the default.

10
  • You have logs to check - that's the next step. Note that CBS logs are additive, same file covers all attempts right back. You can thin the data using findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" which will save the errors to a new file on your desktop.
    – Tetsujin
    Commented Apr 29, 2023 at 15:48
  • Perhaps you should first attempt to do an in-place repair install of your current Windows version - which is what?
    – harrymc
    Commented Apr 29, 2023 at 16:29
  • You will have to parse the logs and provide the relevant information required to diagnose your issue. Disable Developer Mode. The error you received is more than likely caused by it being enabled.
    – Ramhound
    Commented Apr 29, 2023 at 16:59
  • @harrymc - They are running 1709.
    – Ramhound
    Commented Apr 29, 2023 at 16:59
  • We also require SetupErr.log
    – Ramhound
    Commented Apr 29, 2023 at 17:07

1 Answer 1

1

First, be sure to change the ProfilesDirectory value in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList to the default %SystemRoot%\Users.

Next, attempt to do an in-place repair install of your current Windows version, which is apparently Windows 10 1709.

You should download the ISO for this version, open it up and run setup.exe. This is described in detail in the article How to Do a Repair Install of Windows 10 with an In-place Upgrade.

If this fails, your setup is in a too-bad shape to be recovered, so you will need to install the latest version of Windows 10 from scratch.

Getting an ISO for version 1709 is not easy, since Microsoft doesn't cooperate. I list below one source that I have found. Remember that this ISO is about 4 GB in size, so you should look for a fast download.

Rufus can create bootable USB, but also has a repository of old ISO versions. See the article
How to download older ISO versions of Windows 10. Rufus is a safe site.

1
  • @Brian - Be sure you edit your question instead of submitting a temporary comment. Only editing question will notify users.
    – Ramhound
    Commented Apr 29, 2023 at 18:13

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .