Windows 10: Different Windows 10 boot sequence / different display with new efi partition

I have no clue if this is the right subreddit to ask such a question, so please redirect me if this is the wrong place!

I wanted to clean up my secondary drive today and realized that there was a efi partition and a recovery partition on it, while my primary drive with my windows installation on it had no efi partition on it (only two recovery and the primary partition). I followed this guide to create an efi partition on the primary drive and I was able to boot from it. However, I realized that the boot sequence (or at least the display) is different now! Instead of 'black screen + ASRock logo --> black screen + loading circle --> login screen', it goes from 'black screen + ASRock logo --> windows icon + loading circle --> black screen + loading icon --> login screen', and takes significantly longer to boot (about 10 seconds I'd say). Can anybody make sense of this?

submitted by /u/Jogius
[link] [comments]

:)

 

UNMOUNTABLE_BOOT_VOLUME after creating new EFI System Partition

Hello,

On my laptop (Acer Swift 3) I dual boot Windows 10 (stock Windows, not Acer's version) and Arch Linux, recently I ran out of space on my EFI System Partition (ESP) while trying to install a different Linux kernel, so I copied out all of the files on the
ESP, created a new, bigger one and copied all of the files back on. After removing and re-adding the boot options using the EFI shell, Linux booted fine (from rEFInd) but Windows no longer boots - every time it blue screens with UNMOUNTABLE_BOOT_VOLUME. I
have already tried:

• deleting /boot/EFI/Microsoft and /boot/EFI/Boot/bootx64.efi, then running `bcdboot /l en-gb /s s: /f UEFI` from a recovery disk - same problem
• running various `bootrec` commands, some said "Access Denied" (what???) and some claimed there are no valid Windows partitions even though one is mounted at C:
• Startup Repair - did not find any problems
• reinstalling Windows - the installer says it will reboot and continue afterwards, when it reboots it dumps me at the main installer menu, without having made any progress
• looking at EFI NVRAM variables - it is impossible to tell which of these actually affect the Windows boot manager
• `sfc /scannow` - it was a shot in the dark and lo and behold it did nothing

Any help getting Windows to boot again will be greatly appreciated.

 

M.2 SATA to NVME clone: Windows 10 won't boot

Problem: Windows partition won't boot after cloning M.2 SATA drive to M.2 NVME. Simply returns to BIOS splash screen are restarts boot sequence.

Background: Cloning process was simple raw dd copy. Drive had EFI, Windows 10, and Linux partitions. Cloning preserved exact partition sequence, sizes, and UUIDs.

Linux partition needed minor tweaks to /etc/fstab due to the device names being different (/dev/nvme0n1px vs. /dev/sdax), but boots fine.

The disk is GPT, and I believe the original Windows 10 was UEFI - the Linux installation definitely was.

Boot sequence brings up Linux 'grub' menu first. Choosing the EFI partition then brings up Windows EFI boot menu. Fresh Windows install (see below) boots fine from here, old install fails.

Attempts at solution: I did a fresh Windows install in a spare partition and it boots fine. Using the new Windows installation, I've edited the BCD entry for my original Win 10 install. I have
the correct BCD device, osdevice, and path.

Questions:

• What else needs to be done to make Windows boot again?
• Are there any config file or registry changes that need to be made to account for the SATA to NVME move?
• How do I see boot error messages for a UEFI boot failure? No errors displayed and no log files that I can find in Windows or EFI partitions...

 

Move EFI partition

its to enable win 10 to update to its anniversary edition.. it cant do this due to lack of C drive space i have had a quick try with the trial version of easus.. it didnt seem to be able to do what i want..

i am assuming i cant just delete the efi partition but maybe i could.. as yet i havnt even figured out how to get into the bios of the thing.. maybe that should be my next step.. *Smile

diskpart could probably do it but figuring out how (it aint that user friendly) might be difficult without step by step instructions..

trog