The thing is that I noticed after the initial SSD boot and with the bootflags changed, I no longer got the BSOD, but the Windows boot left me with dark screen with a busy icon and mouse pointer flashing when moving the mouse and strangely, a softly rattling HDD being used to start up. Use this solution at your own risk as data loss is possible when you make mistakes. I’m not sure why the powercfg command mentions Windows To Go because i’ts depricated and I cannot find any other reference in my installation.īottom line: it’s a long and complicated path to success, and specific knowledge of commandline tooling is needed. For me it’s not a problem because I don’t use it. Note: I can’t activate hibernation afterwards because of WIndows To Go issues. Power on the Mac with option and again EFI Boot SSD.Push the powerbutton of the Mac short, to force Windows to shutdown gracefully. In other posts it’s adviced to change this to 1c to prevent the BSOD. Start regedit and search for BootDriverFlags.You can also start DiskPart and do a select volumes command to see the different volumes (there should be one NTFS partition which is the SSD one).[optional[ after the prompt type set and look if all variables point to the same drive (for me C:).By now the system detects problems and gives you the option of a boot menu (F8).choose again EFI Boot SSD and watch the BSOD appear… again.Watch the BSOD appear… and the automatic reboot.Restart with option-key and choose EFI Boot SSD (by now you know what to guess :-)).Exit the cmd box and close the install window.This setting in itself is a non-destructive action: you can always set the id back to Windows Data Partition (see link for GUID) and the partition becomes accessible again. Change the GUID of this partition into something no longer recognizable as a Windows Data partition (for example Linux Reserverd GUID as I did) with the set id= option in DisPart.select this partition (see instruction on DiskPart tool).Search for the original partition on which Windows HDD Bootcamp was installed. Select Shift+Fn+F10 to start a cmd box (there will be no Windows install).Select option and select EFI Boot USB stick (SSD is also EFI boot, you’ve to guess a bit).I did not install/injected any drivers in the end my SSD will be used as the replacement for my HDD, so all the right drivers (video, keyboard, etc) are present (I checked this with dism, it showed that also applessd was installed in the original HDD windows version).Start MacOS and clone Windows to SSD drive (see instructions twocanoes).Disable hibernation and chkdsk file system with optional repair to get a ‘clean’ image.Remove all USB devices (I’m not sure if this is definitely neccessary but just in case).No SysPrep neccessary as I want to use the same hardware but with a faster SSD.USB Stick with Windows install + Apple bootcamp support drivers.Crucial 500Gb SSD with simple Fantec USB3.0 enclosure.Windows 10 PRO installed (maybe the PRO version matters -I’m not sure- due to Windows To Go functionality).Apple iMac late 2013 Catalina 10.15.4 with fusion config (128Gb SSD+1Tb HDD).I can give absolutely no guarantee this will work for everyone (always, always backup!), since this is a complex problem but if it can help some of you as a last resort I would be happy registry setting BootdriverFlags (though part of the solution, see below).used 8.2 beta version to inject a mass storage driver (applessd.sys).Inject bootcamp Windows drivers using method described by twocanoes.disabled hibernation and chkdsks to prevent dirty file system.What I’ve tried first after reading all the posts I could find: After trying numerous solutions from this forum and others, I finally found a way to clone an already installed Windows 10 bootcamp partition to an USB 3.0 external SSD. I write this topic as a possible solution of how to solve the dreaded ‘Inaccessible boot device’ BSOD.
0 Comments
Leave a Reply. |