F5F Stay Refreshed Software Operating Systems Deleted a storage device, currently unable to start (missing windload.efi file)

Deleted a storage device, currently unable to start (missing windload.efi file)

Deleted a storage device, currently unable to start (missing windload.efi file)

X
xFunnyman
Member
Find
192
08-29-2022, 10:10 PM
#1
Need assistance. I had two NVMe drives in my PC; I removed one to use as an external drive and formatted it. Now I'm trying to boot, but it fails with the error "windload.efi missing." It wasn't the OS drive, so I don’t know why. The OS drive is the second NVMe, and I have Windows 10 installed on a bootable USB stick. Could you help? Edit: I originally installed Windows on one drive and then reinstalled it on the other. Is it possible that the boot partition stayed on the first drive after removal and formatting, which is why it doesn’t boot even though Windows is on the second drive in my PC?
Reply
Reply
X
xFunnyman
08-29-2022, 10:10 PM #1

Need assistance. I had two NVMe drives in my PC; I removed one to use as an external drive and formatted it. Now I'm trying to boot, but it fails with the error "windload.efi missing." It wasn't the OS drive, so I don’t know why. The OS drive is the second NVMe, and I have Windows 10 installed on a bootable USB stick. Could you help? Edit: I originally installed Windows on one drive and then reinstalled it on the other. Is it possible that the boot partition stayed on the first drive after removal and formatting, which is why it doesn’t boot even though Windows is on the second drive in my PC?

Reply
Reply
S
sst04
Member
Find
208
08-29-2022, 10:10 PM
#2
Attempted repair but it didn’t work for your PC
Reply
Reply
S
sst04
08-29-2022, 10:10 PM #2

Attempted repair but it didn’t work for your PC

Reply
Reply
C
connor8c
Member
Find
163
08-29-2022, 10:10 PM
#3
The two M.2 drives weren't randomly connected. EDIT: The user mentioned the OS drive was the second NVMe device. If true, Windows could have defaulted to placing the missing file on the first NVMe, likely because it was the boot drive or intended for RAID configuration. This might clarify the situation. Edited June 5, 2022 by An0maly_76 Revised, more info
Reply
Reply
C
connor8c
08-29-2022, 10:10 PM #3

The two M.2 drives weren't randomly connected. EDIT: The user mentioned the OS drive was the second NVMe device. If true, Windows could have defaulted to placing the missing file on the first NVMe, likely because it was the boot drive or intended for RAID configuration. This might clarify the situation. Edited June 5, 2022 by An0maly_76 Revised, more info

Reply
Reply
S
Sofi41505
Member
Find
149
08-29-2022, 10:10 PM
#4
This problem involves a malfunctioning Windows setup. The system believes it's assisting by using the previously discovered boot manager. The person who created this should be addressed. Fix details available at the provided link.
Reply
Reply
S
Sofi41505
08-29-2022, 10:10 PM #4

This problem involves a malfunctioning Windows setup. The system believes it's assisting by using the previously discovered boot manager. The person who created this should be addressed. Fix details available at the provided link.

Reply
Reply