H
HopefulComputerScientist
Guest
I have a dual-boot laptop with Ubuntu 18.04.2 and Windows 10 Home Edition. I can't get to the sign in screen in Windows because it always tries to perform a Startup Repair and fails. I've tried using System Restore: when using the most recent restore point, the Startup Repair problem persists. When using the second most recent point (and last I have), before a Windows Update I get the 0x81000204 error message. Here's what I've tried so far:
dism /export-image /SourceImageFile:G:\sources\install.wim /SourceIndex:1 /DestinationImageFile:C:\install.wim /Compress:max /CheckIntegrity
(G: is the drive letter of the Windows bootable USB I created earlier). It ran without throwing out any errors.
dism /Image:C: /Cleanup-Image /RestoreHealth /Source:Wim:C:\install.wim /LimitAccess
dism /Image:C: /Cleanup-Image /RestoreHealth /Source:Wim:C:\install.wim:1 /LimitAccess
As suggested in the Configure a Windows Repair Source Microsoft page, I've also tried to use a Windows side-by-side folder from the bootable USB, by running:
dism /Image:C: /Cleanup-Image /RestoreHealth /Source:G:\sources\SxS
Tried mounting the install.wim image first in my Windows primary partition by running the following command, which I found somewhere I can't remember:
dism /mount-wim /wimfile:C:\install.wim /index:1 \mountdir:C:\Images\mounted
This operation ran successfully. I then ran
dism /Image:C: /Cleanup-Image /RestoreHealth /Source:C:\Images\mounted
as suggested in point 1 of the Configure a Windows Repair Source page.
I've tried diffrent indexes (1, 2 and 3), deleting the "Wim:" part from /Source:Wim:C:\install.wim, using the bootable USB directly as the /Source drive, creating a bootable USB in a Windows computer (in that case it comes with a install.esd which I handled acording to this guide. I've successfully ran
DISM /Image:C: /Cleanup-Image /StartComponentCleanup and
DISM /Online /Cleanup-Image /AnalyzeComponentStore
I've run an offline SFC which returned Windows Resource Protection found corrupt files but was unable to fix some of them.
Every single time I ran dism /Cleanup-Image /RestoreHealth commands I got the warning "The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir option to point to a folder with sufficient scratcg space. The recommended size is at least 1024 MB". I don't know if this made any difference.
But most importantly (and cause of much frustratrion) I always get the
"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 (...)
The DISM log file can be found at X:\windows\Logs\DISM\dism.log"
I've looked through the log files and I can find what I suppose are relevant messages like
2019-07-24 07:56:02, Info CBS Exec: Addsource called, Session: 6768_7899109, Client: DISM Package Manager Provider, from GPO: No, Path: C:\install2.wim
2019-07-24 07:56:02, Warning CBS The alternate source path directory could not be accessed [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2019-07-24 07:56:02, Info CBS Failed to add new file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2019-07-24 07:56:02, Info CBS Failed to add alternate file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2019-07-24 07:56:02, Info CBS Failed adding alternate source directory [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2019-07-24 07:56:02, Warning DISM DISM Package Manager: PID=6768 TID=6792 CBS AddSource failed with HRESULT=0x8007007b! - CDISMPackageManager::Internal_Finalize
2019-07-24 07:55:55, Warning DISM DISM Provider Store: PID=6736 TID=6740 Failed to load the provider: X:\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-07-24 07:55:55, Info DISM DISM WIM Provider: PID=6736 TID=6740 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2019-07-24 07:55:55, Info DISM DISM VHD Provider: PID=6736 TID=6740 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2019-07-24 07:55:55, Warning DISM DISM Provider Store: PID=6736 TID=6740 Failed to retrieve the Provider Instance. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)
2019-07-24 07:55:55, Info DISM DISM VHD Provider: PID=6736 TID=6740 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2019-07-24 07:55:55, Info DISM DISM Imaging Provider: PID=6736 TID=6740 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
[6736] [0x80070002] FIOReadFileIntoBuffer
1381): O sistema não conseguiu localizar o ficheiro especificado.
[6736] [0xc142011c] UnmarshallImageHandleFromDirectory641)
[6736] [0xc142011c] WIMGetMountedImageHandle2897)
2019-07-24 07:55:55, Info DISM DISM WIM Provider: PID=6736 TID=6740 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2019-07-24 07:55:55, Info DISM DISM Imaging Provider: PID=6736 TID=6740 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
2019-07-24 07:55:55, Info DISM DISM Imaging Provider: PID=6736 TID=6740 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2019-07-24 07:55:55, Info DISM DISM Manager: PID=6736 TID=6740 physical location path: C:\ - CDISMManager::CreateImageSession
and later
2019-07-24 08:08:39, Error CSI 00000043@2019/7/24:08:08:39.495 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2019-07-24 08:08:39, Info CSI 00000044@2019/7/24:08:08:39.557 Corruption detection complete. numCorruptions = 65, Disp = 1.
2019-07-24 08:08:39, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2019-07-24 08:08:39, Info CSI 00000045@2019/7/24:08:08:39.557 CSI Transaction @0x2bd46b75570 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id 'TI5.6768_7899109:1/'
and afterwards a huge amount of "Not able to find replacement file for component (...)"
2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-sechealthui.appxmain_31bf3856ad364e35_10.0.17134.407_none_94c831bd33ee8579, file SecHealthUI.exe from any local source
2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-s..emsettingsthreshold_31bf3856ad364e35_10.0.17134.441_none_011ac95e3400d5eb, file SystemSettings.dll from any local source
2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6, file BingMaps.dll from any local source
2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6, file mos.dll from any local source
later still
2019-07-24 08:08:39, Info CBS =================================
2019-07-24 08:08:39, Info CBS Checking System Update Readiness.
2019-07-24 08:08:39, Info CBS
2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-sechealthui.appxmain_31bf3856ad364e35_10.0.17134.407_none_94c831bd33ee8579\SecHealthUI.exe
2019-07-24 08:08:39, Info CBS Repair failed: Missing replacement payload.
2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-s..emsettingsthreshold_31bf3856ad364e35_10.0.17134.441_none_011ac95e3400d5eb\SystemSettings.dll
2019-07-24 08:08:39, Info CBS Repair failed: Missing replacement payload.
2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6\BingMaps.dll
2019-07-24 08:08:39, Info CBS Repair failed: Missing replacement payload.
2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6\mos.dll
So this makes me suspect I'm doing something wrong with the DISM source specification and maybe the replacement for /Online argument (I've tried /Image:C:\Windows and it didn't work), but I can't find out what. So my question is, given all of this information
Is there a way to successfully run dism to repair my Windows image and if so, what is it?
Thank you for your patience and sorry for such a long post.
Best regards
Continue reading...
- Following this guide with several adaptations due to not being able to boot into into Windows:
- Ran the Command Line from the Recovery Environment (have used both the RE Windows takes me to after Startup Repair fails and the one accessible by booting from a Windows bootable USB)
- Replaced /Online by /Image:C:
- Downloaded the Windows 10 ISO image from the official website, then created a Windows bootable USB following the first method on this guide.
- Used this guide to see which intall.wim files were inside the install.wim file inside the sources folder. There are a total of 13 editions, 3 of them pertaining to Windows 10 Home: the "regular one", one called Windows 10 Home N and one called Windows 10 Home Single Language.
- Ran the following command to extract the (what I think is) relevant edition to my Windows primary partition:
dism /export-image /SourceImageFile:G:\sources\install.wim /SourceIndex:1 /DestinationImageFile:C:\install.wim /Compress:max /CheckIntegrity
(G: is the drive letter of the Windows bootable USB I created earlier). It ran without throwing out any errors.
- Added the argument /Source with several differente variations:
dism /Image:C: /Cleanup-Image /RestoreHealth /Source:Wim:C:\install.wim /LimitAccess
dism /Image:C: /Cleanup-Image /RestoreHealth /Source:Wim:C:\install.wim:1 /LimitAccess
As suggested in the Configure a Windows Repair Source Microsoft page, I've also tried to use a Windows side-by-side folder from the bootable USB, by running:
dism /Image:C: /Cleanup-Image /RestoreHealth /Source:G:\sources\SxS
Tried mounting the install.wim image first in my Windows primary partition by running the following command, which I found somewhere I can't remember:
dism /mount-wim /wimfile:C:\install.wim /index:1 \mountdir:C:\Images\mounted
This operation ran successfully. I then ran
dism /Image:C: /Cleanup-Image /RestoreHealth /Source:C:\Images\mounted
as suggested in point 1 of the Configure a Windows Repair Source page.
I've tried diffrent indexes (1, 2 and 3), deleting the "Wim:" part from /Source:Wim:C:\install.wim, using the bootable USB directly as the /Source drive, creating a bootable USB in a Windows computer (in that case it comes with a install.esd which I handled acording to this guide. I've successfully ran
DISM /Image:C: /Cleanup-Image /StartComponentCleanup and
DISM /Online /Cleanup-Image /AnalyzeComponentStore
I've run an offline SFC which returned Windows Resource Protection found corrupt files but was unable to fix some of them.
Every single time I ran dism /Cleanup-Image /RestoreHealth commands I got the warning "The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir option to point to a folder with sufficient scratcg space. The recommended size is at least 1024 MB". I don't know if this made any difference.
But most importantly (and cause of much frustratrion) I always get the
"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 (...)
The DISM log file can be found at X:\windows\Logs\DISM\dism.log"
I've looked through the log files and I can find what I suppose are relevant messages like
2019-07-24 07:56:02, Info CBS Exec: Addsource called, Session: 6768_7899109, Client: DISM Package Manager Provider, from GPO: No, Path: C:\install2.wim
2019-07-24 07:56:02, Warning CBS The alternate source path directory could not be accessed [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2019-07-24 07:56:02, Info CBS Failed to add new file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2019-07-24 07:56:02, Info CBS Failed to add alternate file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2019-07-24 07:56:02, Info CBS Failed adding alternate source directory [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2019-07-24 07:56:02, Warning DISM DISM Package Manager: PID=6768 TID=6792 CBS AddSource failed with HRESULT=0x8007007b! - CDISMPackageManager::Internal_Finalize
2019-07-24 07:55:55, Warning DISM DISM Provider Store: PID=6736 TID=6740 Failed to load the provider: X:\Sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2019-07-24 07:55:55, Info DISM DISM WIM Provider: PID=6736 TID=6740 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2019-07-24 07:55:55, Info DISM DISM VHD Provider: PID=6736 TID=6740 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2019-07-24 07:55:55, Warning DISM DISM Provider Store: PID=6736 TID=6740 Failed to retrieve the Provider Instance. - CDISMProviderStore::Internal_GetProvider(hr:0x80004005)
2019-07-24 07:55:55, Info DISM DISM VHD Provider: PID=6736 TID=6740 [C:\] is not recognized by the DISM VHD provider. - CVhdImage::Initialize
2019-07-24 07:55:55, Info DISM DISM Imaging Provider: PID=6736 TID=6740 The provider VHDManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
[6736] [0x80070002] FIOReadFileIntoBuffer
1381): O sistema não conseguiu localizar o ficheiro especificado.[6736] [0xc142011c] UnmarshallImageHandleFromDirectory
641)[6736] [0xc142011c] WIMGetMountedImageHandle
2897)2019-07-24 07:55:55, Info DISM DISM WIM Provider: PID=6736 TID=6740 [C:\] is not a WIM mount point. - CWimMountedImageInfo::Initialize
2019-07-24 07:55:55, Info DISM DISM Imaging Provider: PID=6736 TID=6740 The provider WimManager does not support CreateDismImage on C:\ - CGenericImagingManager::CreateDismImage
2019-07-24 07:55:55, Info DISM DISM Imaging Provider: PID=6736 TID=6740 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage
2019-07-24 07:55:55, Info DISM DISM Manager: PID=6736 TID=6740 physical location path: C:\ - CDISMManager::CreateImageSession
and later
2019-07-24 08:08:39, Error CSI 00000043@2019/7/24:08:08:39.495 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2019-07-24 08:08:39, Info CSI 00000044@2019/7/24:08:08:39.557 Corruption detection complete. numCorruptions = 65, Disp = 1.
2019-07-24 08:08:39, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2019-07-24 08:08:39, Info CSI 00000045@2019/7/24:08:08:39.557 CSI Transaction @0x2bd46b75570 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id 'TI5.6768_7899109:1/'
and afterwards a huge amount of "Not able to find replacement file for component (...)"
2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-sechealthui.appxmain_31bf3856ad364e35_10.0.17134.407_none_94c831bd33ee8579, file SecHealthUI.exe from any local source
2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-s..emsettingsthreshold_31bf3856ad364e35_10.0.17134.441_none_011ac95e3400d5eb, file SystemSettings.dll from any local source
2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6, file BingMaps.dll from any local source
2019-07-24 08:08:39, Info CBS Repr: Not able to find replacement file for component amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6, file mos.dll from any local source
later still
2019-07-24 08:08:39, Info CBS =================================
2019-07-24 08:08:39, Info CBS Checking System Update Readiness.
2019-07-24 08:08:39, Info CBS
2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-sechealthui.appxmain_31bf3856ad364e35_10.0.17134.407_none_94c831bd33ee8579\SecHealthUI.exe
2019-07-24 08:08:39, Info CBS Repair failed: Missing replacement payload.
2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-s..emsettingsthreshold_31bf3856ad364e35_10.0.17134.441_none_011ac95e3400d5eb\SystemSettings.dll
2019-07-24 08:08:39, Info CBS Repair failed: Missing replacement payload.
2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6\BingMaps.dll
2019-07-24 08:08:39, Info CBS Repair failed: Missing replacement payload.
2019-07-24 08:08:39, Info CBS (p) CSI Payload Corrupt (n) amd64_microsoft-windows-mapcontrol_31bf3856ad364e35_10.0.17134.619_none_f523e5336089c1e6\mos.dll
So this makes me suspect I'm doing something wrong with the DISM source specification and maybe the replacement for /Online argument (I've tried /Image:C:\Windows and it didn't work), but I can't find out what. So my question is, given all of this information
Is there a way to successfully run dism to repair my Windows image and if so, what is it?
Thank you for your patience and sorry for such a long post.
Best regards
Continue reading...