Troubleshot
New member
- Apr 1, 2020
- 2
Hi there,
This is posted here after trying to post this in the general windows help and information - windows 10 section. Lets see, as I am not after how to use windows etc.....
After a power surge when coming out of hibernation windows crashed. Windows 10 Pro x64 then went into automatic repair which fails to diagnose a problem and so enters a loop. Where it is not possible to go into safe mode for all of the possibilities. Discovered an issue with the 1909 build of windows after this incident; it contains some corrupt files (via other pc's also on the same build of windows 10) which is most likely the store that only DISM can repair and then SFC can have a go at repair. However on the windows 10 pro x64 pc this is not now possible and both these fail as remedies via command prompt even when these are run from a DVD booting WinRE. In this scenario windows is divided over two drives, the c: which has system32 and the rest with all other files on e: - there is a <JUNCTION> link between e: and c: for the user folder. e: is a ramdisk generated by windows recovery and a problem in itself. Please note it is not possible to get logs (e:\recovery\windowsRE\winre.wim\system32\logfiles\srt\srttrail.txt) as it/they do not exist and system32 is minimal whilst housed on c:, well it is possible for the DISM logs only when taken from x:. I have done the following troubleshooting to get windows up and running with no success:
1) BOOTREC
/fixmbr - repairs.
/rebuildbcd - rebuilds.
/fixboot - access denied.
2) CHKDSK
If dismounted works fine locating no errors. This closed a process, amd64_ which was probably in WinSxS.
No disk errors at all (via chkdsk), and this had only been checked and passed positively days before.
3) SFC (From recovery off hard disk and via DVD so windows repair offline)
Windows Resource Protection cannot perform required operation.
4) DISM (From recovery off hard disk and via DVD offline) - tried from e: and then c:
Tried a number of combinations. However for anything online the response is does not support servicing WinPE with /online.
For offline usual errors are 2, 3, 50, 1639 with the best I can get as, does not support this request but also gets unable to access image.
Tried Revertpendingactions - same problems ...
Tried mounting a wim point and using scratchdir.
Least problem options:
a) DISM /image:e:\ /cleanup-image /restorehealth /source:wim:x:\sources\install.wim:1
Er 3 ... does not support
b) DISM /Online /cleanup-image /restorehealth /source:f:\test\mount\windows !!!!
Er 50 does not support winpe - nothing new here.
c) DISM /image:e:\ /scratchdir:e:\tmp /cleanup-image /restorehealth
Er 3 the request is not support
d) DISM /mount-image /imagefile:x:\sources\install.wim /index:1 /mountdir:c:\mount
Er 2 Cannot find file.
Another error is to do with not possible on a windows vista or earlier, if this is not so check the SSShim.DLL file is present. This file exists in system32 (not present on c:) and in winsxs (on e:) where it is present.
Does anybody know how to get windows repaired and booting for this scenario, starting with DISM? Before I just re-installed windows with a clean installation - experienced similar problem once before.
I do have some DISM logs from X: but they are not that informative. Did mention e:\ was not a wim mount point.
All the best. :)
This is posted here after trying to post this in the general windows help and information - windows 10 section. Lets see, as I am not after how to use windows etc.....
After a power surge when coming out of hibernation windows crashed. Windows 10 Pro x64 then went into automatic repair which fails to diagnose a problem and so enters a loop. Where it is not possible to go into safe mode for all of the possibilities. Discovered an issue with the 1909 build of windows after this incident; it contains some corrupt files (via other pc's also on the same build of windows 10) which is most likely the store that only DISM can repair and then SFC can have a go at repair. However on the windows 10 pro x64 pc this is not now possible and both these fail as remedies via command prompt even when these are run from a DVD booting WinRE. In this scenario windows is divided over two drives, the c: which has system32 and the rest with all other files on e: - there is a <JUNCTION> link between e: and c: for the user folder. e: is a ramdisk generated by windows recovery and a problem in itself. Please note it is not possible to get logs (e:\recovery\windowsRE\winre.wim\system32\logfiles\srt\srttrail.txt) as it/they do not exist and system32 is minimal whilst housed on c:, well it is possible for the DISM logs only when taken from x:. I have done the following troubleshooting to get windows up and running with no success:
1) BOOTREC
/fixmbr - repairs.
/rebuildbcd - rebuilds.
/fixboot - access denied.
2) CHKDSK
If dismounted works fine locating no errors. This closed a process, amd64_ which was probably in WinSxS.
No disk errors at all (via chkdsk), and this had only been checked and passed positively days before.
3) SFC (From recovery off hard disk and via DVD so windows repair offline)
Windows Resource Protection cannot perform required operation.
4) DISM (From recovery off hard disk and via DVD offline) - tried from e: and then c:
Tried a number of combinations. However for anything online the response is does not support servicing WinPE with /online.
For offline usual errors are 2, 3, 50, 1639 with the best I can get as, does not support this request but also gets unable to access image.
Tried Revertpendingactions - same problems ...
Tried mounting a wim point and using scratchdir.
Least problem options:
a) DISM /image:e:\ /cleanup-image /restorehealth /source:wim:x:\sources\install.wim:1
Er 3 ... does not support
b) DISM /Online /cleanup-image /restorehealth /source:f:\test\mount\windows !!!!
Er 50 does not support winpe - nothing new here.
c) DISM /image:e:\ /scratchdir:e:\tmp /cleanup-image /restorehealth
Er 3 the request is not support
d) DISM /mount-image /imagefile:x:\sources\install.wim /index:1 /mountdir:c:\mount
Er 2 Cannot find file.
Another error is to do with not possible on a windows vista or earlier, if this is not so check the SSShim.DLL file is present. This file exists in system32 (not present on c:) and in winsxs (on e:) where it is present.
Does anybody know how to get windows repaired and booting for this scenario, starting with DISM? Before I just re-installed windows with a clean installation - experienced similar problem once before.
I do have some DISM logs from X: but they are not that informative. Did mention e:\ was not a wim mount point.
All the best. :)
