No physical memory is available at the location required for the Windows Boot Manager. The system can not continue.

Anonymous
2022-10-18T21:44:49+00:00

I have a Dell Latitude E6530 laptop that somehow went south after a pulled a USB stick out of the computer while the BIOS screen was showing. All the data in all the partitions including Windows 10 PRO are intact. I can view all the files in the directories. The problem is the system just won't boot. This system originally had Windows 7 PRO that I updated to Windows 10 PRO. The system is UEFI capable and I have enabled the legacy roms in the BIOS and I have the Boot Sequence set to Legacy. the hard disk layout is NOT UEFI. It is MBR. When I try to boot all devices that are on the boot options menu (F12 when the BIOS screen appears), I have 2 Legacy Boot Devices: the Internal Hard Drive and the DVD/CD drive, but when I attempt to boot form either of them (LEGACY), I get the "No physical memory..." message. I can only boot devices that are UEFI such as the DVD/CD or an external USB bootable stick. I have run the memory test diagnostic on the computer 4 times. No problems. I have run chkdsk the computer a couple times. No problems. I have tried to rebuild the BCD, but with the latest ISO, I get access error for bootrec /fixboot. If I drop back to ISO 1703, bootrec /fixboot works, but I get "The requested system device cannot be found" when trying to execute bootrec /RebuildBcd. I feel like the whole problem is because I cannot boot legacy devices. To make matters worse I tried to reninstall Windows from the ISO DVD, but it won't let me do it. I just really want to be able to boot Windows hopefully without reinstalling or losing *anything* since all my data is there still, but until I can successfully "restore" Legacy Boot options working, I don't think I can. Any help appreciated.

Jordan Krim

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

65 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-11-06T03:14:08+00:00

    That's how it all started a few years ago; you cloned the D630 to the E6530, IIRC. OK, it's worth a try. If you get the "No physical memory..." error, it will sound like a BIOS problem on the E6530 to me. I don't anticipate any other error (if it is still booting well on the D630). On the E6530. it should start switching drivers. Good luck. (But I wish I could think harder.)

    Was this answer helpful?

    0 comments
  2. MR_MEOW 3,706 Reputation points
    2022-11-06T01:53:08+00:00

    UEFI /efi requires a Fat32 formatted partition to show up properly in the bios menu picker. "Surprise 😁 "

    The boot config should be minimal time out value of 15 normal is 30.

    There is a bypass for booting into .efi mode

    There is also a bypass on bcd edit to get ur pc in windows environment in 45 seconds bypassing win logins with windows loaded.

    The uefi / legacy is usually flashed on to your ram or bootloader chip.

    Also under legacy boot mode make sure u can pick the hdd

    uefi boot works for Windows 10 and up. I am running a windows 10 on a legacy boot right now. Just letting you know that it is possible.

    If you can take a screen shot of your bios boot options i could tell you what to pick.

    [XDA-DEVLOPER]

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-11-06T01:22:09+00:00

    Yes. It all looks good as you show.

    I cloned with Macrium the HD in the older laptop running Win 7 to the problem HD from the E7530. It took 5 hours for these 1 TB drives. When I put it back into the E6530 booting Windows 7 gave the "No physical..." message so maybe Macrium cloning is not working or there is a problem with the E6530 HW. I am now closing the D630 HD to the E6530 HD using LazeSoft sector by sector copy. It looks like it will take many hours.

    Jordan

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-11-05T16:21:24+00:00

    That's incredible. Once again it looks like the process got to the brink -- all the way to the Windows boot manager -- before the failure. It didn't put up a boot menu because it's a single boot. But just as with the IBM manager, it should at this point be loading the OS. Does the BCD still look like this...?...

    BCDEdit <<<Show BCD

    BCDEdit /Store C:\Boot\BCD <<<Do If prior failed

    Image

    Instead of C:, it might refer to HarddriveVolume3. Then, do these find the files...?...

    DIR /a C:\BootMGR <<<Is BootMGR there?

    DIR /a C:\Windows\System32\Winload.exe <<<Is Winload.exe there?

    But use the letter that is in the BCD. And, maybe, with a List Vol, verify it actually is the letter that is on the Windows volume.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-11-05T14:38:58+00:00

    I tried that. Didn't work.

    Jordan

    Was this answer helpful?

    0 comments