S
SnookRed
Guest
Working with a pretty new computer and experiencing indoctrination into Windows 10. Experimenting with image capture & apply using dism with WinPE. Pretty good success achieved when working on a single disk. However, trying to create another version of a system that is working fine on a second disk has hit a snag. All the operations (e.g., capture, apply, and edit bcd) seemed to work as expected with no error. The only difference between this attempt and several successful ones is that the newly applied image resides on a different disk drive. However, after selecting the new system on the boot menu the screen goes dark except for the small circular twirling icon beside the mouse pointer and it stays like that indefinitely. The twirling ICON and muse pointer look just like what you see normally for a short while after signing in but in that case the underlying Windows do get displayed.
It seemed like booting in "safe mode" is something that should be tried. The boot menu provides a dialogue for doing this. However, it always boots to the same system which is the instance that works fine rather than the one that is failing. I even edited the BCD to make sure the failing system is designated as the default but that had no affect on this problem.
Therefore the question becomes how to force safe mode? Note: I am using WinPE in addition to the functioning instances on the other hard drive which means that I could mount the failing system and make some changes if that would help.
While Windows 7 has been working fine for years without ever creating a need to do something like this I do seem to recall that operational NT and XP systems could be booted from removable media and I did make a point of keeping such available for times like these. Is there any possibility that such an obvious capability has been preserved for Windows 10?
More...
It seemed like booting in "safe mode" is something that should be tried. The boot menu provides a dialogue for doing this. However, it always boots to the same system which is the instance that works fine rather than the one that is failing. I even edited the BCD to make sure the failing system is designated as the default but that had no affect on this problem.
Therefore the question becomes how to force safe mode? Note: I am using WinPE in addition to the functioning instances on the other hard drive which means that I could mount the failing system and make some changes if that would help.
While Windows 7 has been working fine for years without ever creating a need to do something like this I do seem to recall that operational NT and XP systems could be booted from removable media and I did make a point of keeping such available for times like these. Is there any possibility that such an obvious capability has been preserved for Windows 10?
More...