Sometimes a Windows virtual machine (VM) starts acting up in ways that are hard to troubleshoot. Windows may crash during startup, a recently installed driver may cause problems, or a software change may prevent the system from loading normally. In situations like these, Safe Mode can give you a clean environment for finding and fixing the problem.
Safe Mode starts Windows with only the most essential drivers and services. That makes it useful when you need to remove a problematic program, roll back a driver, check system files, or troubleshoot startup issues.
The tricky part is that a Windows VM does not always behave exactly like a physical PC during startup. Depending on whether you’re using Hyper-V, VMware Workstation, VMware Fusion, VirtualBox, or another virtualization platform, you may need to use a different way to reach the Windows recovery environment.
This guide walks you through the process step by step, explains several methods for entering Safe Mode, and covers what to do if the normal approach does not work.
Boot Windows VM in Safe Mode [Complete Guide]
1: Start Your Windows VM
First, open your virtualization software and start the Windows virtual machine you want to troubleshoot.
Allow the VM to begin its normal startup process. If Windows loads successfully, you can use Windows itself to enter the recovery options. If Windows crashes, freezes, or repeatedly restarts before you can reach the desktop, you can use the recovery-based methods described later.
Before making major changes, it is smart to create a VM snapshot or checkpoint if your virtualization platform supports one. A snapshot gives you a way to return to the earlier state if troubleshooting causes an unexpected problem.
2: Enter Windows Recovery Options From the Desktop
If your VM can reach the Windows desktop, entering Safe Mode is usually the easiest.
Open Settings, then go to System and select Recovery. Under the recovery options, find Advanced startup and select Restart now.
Windows will restart and display the Windows Recovery Environment. You will not be taken directly back to the desktop. Instead, Windows will present a recovery menu with several options.
Select Troubleshoot, then choose Advanced options.
From there, select Startup Settings. If Windows asks you to restart again, choose Restart.
After the VM restarts, Windows will display a list of startup choices. Select the option for Enable Safe Mode.
If you need internet access while troubleshooting, select Enable Safe Mode with Networking instead. Keep in mind that networking support loads additional components, so regular Safe Mode is generally preferable when internet access is not necessary.
3: Use the Shift + Restart Method
There is another convenient way to reach the same recovery environment.
From the Windows sign-in screen or Start menu, hold down the Shift key and select Restart.
Continue holding Shift while Windows restarts. The system should eventually display the Choose an option recovery screen.
Select Troubleshoot, followed by Advanced options, then Startup Settings. Select Restart when prompted.
Once the startup menu appears, choose Enable Safe Mode or Enable Safe Mode with Networking, depending on what you need.
This method can be especially useful when Windows is working well enough to display the sign-in screen, but you do not want to navigate through the normal Settings interface.
4: Use System Configuration if Windows Starts Normally
If Windows starts normally but you need Safe Mode on the next reboot, you can use System Configuration, commonly called MSConfig.
Press Windows + R to open the Run dialog. Type msconfig and press Enter.
When System Configuration opens, select the Boot tab. Find your Windows installation in the list, then select Safe Boot.
You can choose Minimal for standard Safe Mode or Network if you need networking.
Select Apply, then OK, and restart the VM.
Windows should now start in Safe Mode.
There is one important detail here. After you finish troubleshooting, open msconfig again and clear the Safe Boot option. If you leave it enabled, Windows can continue starting in Safe Mode on every reboot.
5: Force Windows Into Recovery When Normal Startup Fails
If the VM cannot reach the Windows desktop, you can intentionally interrupt startup to make Windows enter recovery mode.
Start the VM and wait for Windows to begin loading. Then interrupt the startup process by powering off or restarting the VM. Repeat this process a few times when necessary.
Windows can detect repeated failed startup attempts and eventually launch the Automatic Repair environment.
Once you see the recovery screen, select Advanced options.
Then go to Troubleshoot, select Advanced options, choose Startup Settings, and select Restart.
When the startup choices appear, select Enable Safe Mode.
This method is useful when a bad driver, startup application, or system configuration prevents Windows from reaching the login screen.
However, avoid repeatedly forcing the VM off during normal operation unless Windows is already stuck. Abruptly powering off a virtual machine can potentially cause file-system problems, particularly if the VM is actively writing data.
6: Use a Windows Installation ISO if Necessary
If Windows will not enter recovery mode automatically, you can use a Windows installation ISO attached to the VM’s virtual optical drive.
The exact process for attaching an ISO depends on your virtualization software. Generally, you configure the VM’s virtual CD/DVD drive to use the Windows ISO and then boot the VM from that virtual drive.
When Windows Setup appears, do not immediately select the option to install Windows.
Instead, look for the option to Repair your computer.
From the recovery environment, select Troubleshoot, then Advanced options.
You can then access recovery and startup tools. Depending on the Windows version and configuration, available options may include Startup Settings, Command Prompt, System Restore, and other recovery utilities.
If Startup Settings is available, use it to restart the VM and select Safe Mode.
7: Check That the VM Actually Entered Safe Mode
After Windows starts, you should be able to tell that you are in Safe Mode.
The Windows interface may look different, the screen resolution may be lower, and you will typically see Safe Mode displayed on the desktop.
Do not be alarmed if your VM’s display looks less polished than normal. Safe Mode intentionally loads a limited set of drivers and services.
This is exactly what makes it useful for troubleshooting.
Troubleshoot the Original Problem
Now that you’re in Safe Mode, focus on the issue that caused you to enter it.
If the problem started after installing a device driver, open Device Manager and investigate the recently changed hardware or driver. You may be able to roll back or uninstall the problematic driver.
If the issue started after installing an application, uninstall that application from Apps or the appropriate Windows settings area.
You can also check Task Manager and examine startup applications that may be causing Windows to behave incorrectly.
For suspected Windows system corruption, you can use administrative command-line tools such as System File Checker. Depending on the problem, DISM can also be useful for repairing the Windows component store.
The key idea is to make one change at a time. If you change several things simultaneously, it becomes much harder to determine which action actually fixed the problem.
Restart the VM Normally
After completing your troubleshooting, restart the Windows VM.
If you entered Safe Mode through Startup Settings, Windows should normally return to standard startup automatically.
If you used MSConfig, remember to remove the Safe Boot setting before restarting.
If Windows starts normally afterward, test the application or feature that originally caused the problem.
If the same issue returns, Safe Mode has still provided useful information. If Windows works correctly in Safe Mode but fails during a normal boot, that strongly suggests the problem may involve a third-party driver, startup application, or service that does not load in Safe Mode.
Faqs
Can I press F8 to enter Safe Mode on a Windows VM?
You can try, but F8 is not reliable on modern Windows installations. Modern versions of Windows generally use faster boot processes, which can make the traditional F8 method difficult or impossible to trigger.
The Windows Recovery Environment is usually the better approach.
Why does my VM boot too quickly for me to access startup options?
Virtual machines can start extremely quickly, especially when the guest operating system is already configured for fast startup.
Instead of trying to catch a keyboard shortcut during boot, use Settings > System > Recovery > Advanced startup when Windows is accessible.
If Windows cannot start normally, use the recovery process or boot from a Windows installation ISO.
Should I use Safe Mode with Networking?
Only if you actually need network access.
Standard Safe Mode loads fewer components and is usually the cleaner environment for troubleshooting. Use Safe Mode with Networking when your troubleshooting task specifically requires network connectivity.
Will Safe Mode delete my files?
No. Entering Safe Mode does not normally delete your personal files.
However, troubleshooting actions performed while in Safe Mode, such as uninstalling software, modifying system settings, or deleting files, can still have consequences. Always be careful when making system changes.
What if Safe Mode does not fix the problem?
Safe Mode is a troubleshooting environment, not a universal repair tool.
If Windows still fails, you can investigate System Restore, startup repair options, driver issues, system-file corruption, or other recovery tools. If the VM has a known-good snapshot or checkpoint, restoring it may also be appropriate.
Can I use Safe Mode on Windows 10 and Windows 11 VMs?
Yes. Windows 10 and Windows 11 both provide Safe Mode through the Windows Recovery Environment. The exact appearance of the menus can vary slightly depending on the Windows edition and configuration.
Does Safe Mode work differently on VMware, Hyper-V, and VirtualBox?
The Windows Safe Mode process is generally the same because Safe Mode is a feature of the Windows guest operating system.
What can differ is how you access the VM’s boot process, attach an installation ISO, send special keyboard commands, or create snapshots and checkpoints. Those parts depend on your virtualization platform.
Final Thoughts
Knowing how to boot a Windows VM in Safe Mode is one of those troubleshooting skills that can save a lot of time when Windows refuses to cooperate.
The easiest approach is usually to enter Advanced startup from Windows and navigate through Troubleshoot > Advanced options > Startup Settings. If Windows cannot reach the desktop, you can rely on recovery mode or a Windows installation ISO instead.
Once you’re in Safe Mode, resist the temptation to change everything at once. Identify what changed recently, investigate the likely driver, application, service, or system component, and make controlled changes.
For virtual machines, it’s also worth using snapshots or checkpoints before major troubleshooting work when appropriate. That gives you an additional safety net if a repair attempt does not go as planned.
Most importantly, remember what Safe Mode is telling you. If Windows works properly in Safe Mode but fails during a normal startup, the problem is often connected to something that loads during a regular boot. That clue can significantly narrow down the troubleshooting process.
With these methods, you should be able to start a Windows VM in Safe Mode, investigate common startup problems, make repairs, and return the VM to a normal Windows boot with much less guesswork.