VMware应用程序是一些最流行的用于创建和管理虚拟机的应用程序。但是，用户在操作时遇到各种问题的情况并不少见。例如，在启动新创建的虚拟机时，它无法加载，但随后会抛出一条错误消息，提示找不到操作系统(Operating system is not found)。
未找到 VMware 操作系统
VMware引导错误并非特定操作系统或安装介质独有。当您尝试从错误的ISO(ISO)文件安装操作系统或从物理存储安装但未正确配置VMware时，您可以获得它。
使用不同的Windows(Windows)版本时会弹出此错误消息。在本节中，我们将探讨VMware启动错误的各种原因，并寻找修复它的最佳方法，接下来。
- 您的虚拟机文件已损坏。
- 创建虚拟机时，您没有指示VMware从物理存储介质中读取数据。
- 您要从中创建虚拟机的ISO文件不是可引导的。(ISO)
- PXE启动延迟时间太短。
如何修复此 VMware 启动错误
在这里，我将向您展示用于修复VMware启动问题的一般方法。如果VMware无法找到您的操作系统，您应该查看上一节中概述的问题原因。
从中，您可能会确定确切的原因并选择适用于您的案例的故障排除技术。
- 确认 ISO 是可引导的。
- 用BIOS(BIOS)重新制作虚拟机。
- 如果从物理驱动器安装，请告知VMware 。
- 增加 PXE 引导延迟时间。
如果您不确定如何执行上述操作，请继续阅读本指南。以下是这些解决方案的详细说明。
1]确认ISO是可引导的
你需要在你的虚拟机上挂载一个ISO文件，而且这个(ISO)ISO必须是一个可启动的操作系统才能工作。但是，并非每个ISO文件都是可引导的。其中一些实际上是操作系统更新。
因此，在针对VMware(VMware)启动错误进行更复杂的故障排除技术之前，首先要确认ISO是可启动的。如果ISO无法启动，那么您必须获得一个可启动的 ISO。另一方面，如果您发现ISO是可引导的，则可以开始修复。
阅读(Read)：VMware 桥接网络不工作或检测。
2]使用不同的设置重新创建(Re-create)虚拟机
如果您使用的是可引导的ISO，而VMWare找不到您的操作系统，那么第二个怀疑机器没有配置UEFI。在创建 VM 的过程中，如果您选择UEFI，您可能会遇到这些启动错误。您需要返回，创建一个新的虚拟机，并将其设置为BIOS而不是UEFI。这是做什么：
启动 VMware(Launch VMware)并从左侧菜单中转到Home。从右侧 选择New Virtual Machine并点击(New Virtual Machine)Next。
选择安装源，然后点击 下一步(Next)按钮。如果您使用 VM Fusion或VMware工作站，请取消 选中Easy Install复选框。
根据主机操作系统的硬件选择您喜欢的虚拟机类型。现在， 从要求您在“典型(Typical)”和 “自定义”之间进行选择的下一页中选择 “自(Custom)定义”(Custom)。
为新虚拟机命名并选择要保存的目录。
修改最大磁盘大小并选择存储虚拟磁盘的方式。单击 下一步(Next)按钮。
您可以以任何您认为合适的方式配置硬件设置，也可以保留默认设置。最后，单击完成(Finish)按钮。
此时，您可以运行新的虚拟机来检查引导错误是否不再出现。
3] 如果从物理驱动器安装，请告知VMware
许多从可启动磁盘安装操作系统的用户遇到 操作系统未找到(Operating system not found)启动错误，因为他们没有指出要从哪个驱动器启动。为防止出现此问题，VMware应该知道您是从该特定驱动器安装它。
启动VMware应用程序。右键单击(Right-click)有问题的虚拟机，然后单击 设置(Settings)。
导航到 硬件 (Hardware )选项卡并从设备列表中选择 CD/DVD (SATA)。
将连接(Connection)更改 为 使用物理驱动器(Use physical drive)。
单击(Click)下拉菜单并选择包含ISO文件的驱动器。点击 OK按钮保存您的设置。
阅读(Read)：VMware Workstation 无法进入 Unity 模式。
4]增加(Increase)PXE启动延迟时间
您的虚拟机配置可能会导致VMware尝试PXE引导。这可能是您遇到的引导错误的根源，因为您可能无法足够快地进入Windows Installer屏幕。(Windows Installer)
VMware只允许您在一个简短的窗口中按任意键启动到 Windows Installer(press any key to boot into Windows Installer)。因此，解决此问题的一个好方法是将启动延迟增加到 6 秒或更多。
首先，关闭所有打开的虚拟机，然后关闭VMware应用程序。
启动文件资源管理器(File Explorer)并转到以下目录：
C:\Users\[your username}\Documents\Virtual Machines
请记住将上面路径中的[您的用户名]([your username])部分替换为您的实际用户帐户名。
在此目录中，双击出现问题的特定机器的文件夹并找到其 .VMX文件。使用智能文本编辑器（例如Notepad ++）打开此文件。
如果您看不到文件扩展名，本指南将帮助您在文件夹中显示文件扩展名。(show file extensions)
在打开的文档中，转到文本的底部，然后粘贴以下代码：
bios.bootDelay = "6000"
现在保存文档并关闭您的文本编辑器。
让我们知道这是否对您有用。
相关(Related)：syswow64 vmnat.exe 进程是(What is syswow64 vmnat.exe process)什么？
Fix VMware operating system not found Boot error
VMware applications are some of the most popular for creating and managing virtual machines. However, it’s not uncommon to see users experience a variety of problems when operating them. For example, when booting a newly created virtual machine, it fails to load but then throws an error message that says the Operating system is not found.
VMware operating system not found
The VMware boot error is not exclusive to specific operating systems or installation media. You can get it when you attempt to install the operating system from a bad ISO file or when installing from physical storage without properly configuring VMware for it.
This error message pops up when working with different Windows editions. In this section, we’ll explore the various causes of the VMware boot error and look into the best ways to fix it, next.
- Your virtual machine files are corrupted.
- When creating the virtual machine, you didn’t instruct VMware to read from a physical storage media.
- The ISO file from which you want to create the virtual machine is not a bootable one.
- The PXE boot delay period is too brief.
How to fix this VMware boot error
Here, I’ll show you the general methods used to fix the VMware boot problem. If VMware is unable to find your operating system, you should go over the causes of the issue outlined in the above section.
From those, you can likely nail the exact cause and pick the troubleshooting technique that applies to your case.
- Confirm that the ISO is bootable.
- Re-make the virtual machine with BIOS.
- If installing from a physical drive, let VMware know.
- Increase the PXE boot delay period.
If you’re not sure how to carry out the above operations, then continue reading this guide. Below are detailed explanations for these solutions.
1] Confirm that the ISO is bootable
You need to mount an ISO file on your virtual machine, and this ISO has to be a bootable OS to work. However, not every ISO files are bootable. Some of them are actually operating system updates.
Therefore, before going into more complex troubleshooting techniques for the VMware boot error, first, confirm that the ISO is bootable. If the ISO is not bootable, then you have to get a bootable one. On the other hand, if you find that the ISO is bootable, you can then begin the repair.
Read: VMware Bridged network not working or detecting.
2] Re-create the virtual machine with different settings
If you’re using a bootable ISO, and VMWare cannot find your operating system, a second suspect it that the machine isn’t configured with UEFI. In the course of creating the VM, if you selected UEFI, you are likely to run into these boot errors. You need to go back, create a new virtual machine, and set it to BIOS and not UEFI. Here’s what to do:
Launch VMware and from the left-hand menu, go to Home. Select New Virtual Machine from the right section and hit Next.
Choose the installation source and then hit the Next button. If you use VM Fusion or VMware workstation, unmark the Easy Install checkbox.
Select your preferred type of virtual machine based on the hardware of the host operating system. Now, select Custom from the next page where you are asked to choose between Typical and Custom.
Name the new virtual machine and select the directory to save it.
Modify the maximum disk size and select how you want to store the virtual disk. Click the Next button.
You can configure the hardware settings any way you seem fit or leave the default settings. Finally, click on the Finish button.
At this point, you can run the new virtual machine to check that the boot error no longer shows up.
3] If installing from a physical drive, let VMware know
Many users who install operating systems from a bootable disk run into the Operating system not found boot error because they didn’t point out the drive from which to boot. To prevent this problem, VMware should be aware that you’re installing it from that specific drive.
Launch the VMware application. Right-click on the problematic virtual machine and click on Settings.
Navigate to the Hardware tab and select CD/DVD (SATA) from the list of devices.
Change the Connection to Use physical drive.
Click on the dropdown menu and choose the drive that contains the ISO file. Strike the OK button to save your settings.
Read: VMware Workstation cannot enter Unity mode.
4] Increase the PXE boot delay period
The configuration of your virtual machine could cause VMware to attempt to PXE boot. This could be the root of the boot error you’re experiencing because you may not be able to get into the Windows Installer screen fast enough.
VMware allows you only a brief window to press any key to boot into Windows Installer. Therefore, a great way to tackle this issue is to increase the boot delay to 6 seconds or more.
First, shut down all open virtual machines and then close the VMware application.
Launch File Explorer and go to the following directory:
C:\Users\[your username}\Documents\Virtual Machines
Remember to replace the [your username] part in the path above to your actual user account name.
In this directory, double-click on the folder of the specific machine that’s giving issues and find its .VMX file. Open this file with a smart text editor (such as Notepad ++).
This guide will help you show file extensions in the folder if you do not see them.
In the open document, go to the bottom end of the text and then paste the code below:
bios.bootDelay = "6000"
Save the document now and close your text editor.
Let us know if this worked for you.
Related: What is syswow64 vmnat.exe process?
