If you see the error message No physical memory is available at the location required for the Windows Boot Manager, The system cannot continue when you try to start your computer, then this post will help you. This issue mainly occurs if the motherboard’s BIOS gets corrupted. However, there are other reasons too that may cause this error.
Fix No physical memory is available at the location required for the Windows Boot Manager
If the System can not continue error keeps troubling you, follow these steps to fix it:
- Repair the Boot Manager
- Run Startup Repair Tool
- Troubleshoot using Safe Boot
- Roll Back Windows Update/Upgrade
- Update BIOS
Now, since you cannot boot Windows normally, you may have to try and boot in Safe Mode or into Advanced Startup options screen to be able to carry out the fixes. You will need to make use of the Command Prompt. For some strange reason if you can boot in Safe Mode but cannot access the Advanced Startup Options screen, when in Safe Mode, you may use the Command Prompt to boot Windows directly to Advanced Startup Settings screen.
1] Repair the Boot Manager
A damaged or corrupted Boot Manager is one of the main reasons why this error message may occur. Follow these steps to repair your Boot Manager.
Since you cannot boot Windows normally, you will need to press F8 while booting the system to the Windows Recovery Menu, then click on Troubleshoot > Advanced options to get into the Automatic Repair menu.
Click on the command prompt and type in the following commands, one after the other:
bootrec/fixmbr bootrec/fixboot bootrec/rebuildbcd
Exit and now go ahead and reboot your system. In some cases, you may need to run some additional commands:
bootsect /nt60 SYS or bootsect /nt60 ALL
2] Run Startup Repair tool
The Startup Repair Tool automatically diagnoses and repairs complex startup problems. These diagnostics include analyzing startup log files to determine the cause of the problem. Follow the steps mentioned above to reach the Advanced options screen and then click on Startup Repair.
Once done restart your PC and check if the issue is fixed.
3] Troubleshoot using Safe Boot
Performing a Safe Boot ensures the operating system loads with minimal system files and device drivers. No programs or add-ons run in Safe Boot mode. Here’s how you can perform a safe boot:
- Press the Windows key + R to open the Run dialog box.
- Type msconfig and hit Enter.
- Navigate to the Boot tab and check the Safe Boot option.
- Under Safe Boot, check the Network option as you’ll need internet to run Virtual Machine.
- Click on Apply and then Ok to save the changes.
- Restart your computer; once done, it will now boot into the Safe Boot mode.
- Now open Task Manager and check which services and startup programs are loading.
4] Roll back Windows Update/Upgrade
If the issue occurred after Windows Updates, you might consider uninstalling the Update. To uninstall an update, follow these steps:
- Press the Windows key + R to open the Run dialog box.
- Type appwiz.cpl and hit Enter.
- In the Uninstall or view a program page click on View Installed Updates.
- Right-click on the recently installed update and select Uninstall.
5] Update BIOS
If none of the above steps were able to help you, update the Motherboard’s BIOS. It’s possible an outdated or corrupted BIOS is the real culprit. On updating the BIOS, your PC should start functioning normally.
How do you fix not enough physical memory is available to power on this virtual machine with its configured settings?
To fix this, you need to shut down unnecessary applications and services. Doing so will free up enough memory to launch Virtual Machine. But if you could switch on the virtual machine in the past, try rebooting the host computer. Rebooting the host device can allow you to use more memory than specified.
Read: The Virtual Machine Management service encountered an error while configuring the hard disk.
How do I fix insufficient physical memory?
As we know, insufficient physical memory can lead to slow performance on VMWare Virtual Machine. These are usually caused by memory shortages, updated configuration, and system glitches. You can fix these by running VMware as an administrator and update it to the latest version.