New
#21
Is it just partition Q that macrium doesn't show - does it show the other partitions on that disk (G and H ) ?I was trying to do what Kyhi described.
Is it just partition Q that macrium doesn't show - does it show the other partitions on that disk (G and H ) ?I was trying to do what Kyhi described.
Did you give the esp partition a drive letter so you can browse to it with bootice?
then browse to driveletter:\EFI\Microsoft\boot folder and pick up the bcd file.
Not sure what the problem is with macrium - possibly it doesn't like the fat32 or maybe it is too small.
Here is what I do.
1) create 1GB fat32 partition
2) Mount Macrium Rescue Iso as a drive
3) copy all files from iso to fat32 partition
4) create WinPE boot entry using easybcd v2.4 (imo easier than bootice)
No third party tools required, just follow the easy steps shown in this tutorial: Macrium Reflect - Create a Rescue Partition
Kari
Yet it was not followed and you choose a different approach...I was trying to do what Kyhi described.
That did not yield the required results..
So it was followed by another method of converting disk layout...
Sorry, but the process followed was not the one I had suggested..
Q: is perhaps an unfortunate choice of letter for this partition. It could be specifically excluded because Microsoft may use Q: for MS Office click-to-run.
https://docs.microsoft.com/en-us/off...n-installationDrive Q (or sometimes drive R) appears when users install an Office 2010 product or suite that is deployed through Click-to-Run.
Here is what I suspect happened..
By default windows 10 being the only OS present... Have the default timeout as 0
Basically win10 is set to the default Boot with a default selection time of 0
that way it rolls (Boots) right into windows 10 without showing the Metro Boot loader screen..
By using bootice to add the ramdisk option for macrium - which appeared to succeed
The Metro Boot loader w/ Boot Options was not show on the reboot because the default time out is still set to 0 (zero) so the options where not displayed... Since it was not seen - the disk structure was changed...
Open the RUN box and type msconfig
go to boot tab & post pic....