Differences

This shows you the differences between two versions of the page.

--- fuss:vmware [2017/02/22 18:30] – external edit 127.0.0.1
+++ fuss:vmware [2025/07/06 04:47] (current) – [VeraCrypt Incompatibility with VMWare] office
@@ Line 12: / Line 12: @@
 monitor_control.disable_directexec = "TRUE"
 </code>
+====== Change Boot Order ======
+Shockingly, for an enterprise-grade software, there is no easy option to change the boot order via the virtual machine settings. The general recommendation is to boot the virtual machine and "quickly" press <key>F2</key> in order to access the VM BIOS and then change the boot order - however, that may not work if the VM boots too fast.
+One way around this issue is to edit the VM ".vmx" settings file directly and configure the boot order manually:
+<code>
+bios.bootOrder = "cdrom,floppy,hdd"
+</code>
+and then reload the virtual machine in VMWare workstation for the settings to take effect.
+====== VeraCrypt Incompatibility with VMWare Physical Drives ======
+{{fuss:fuss_vmware_veracrypt_incompatibility_with_vmware_physical_drives.png}}
+It seems that VeraCrypt loads a driver that impedes access to a physical disk such that loading a virtual machine on a host where VeraCrypt is installed may fail with errors along the lines of access to the drive being denied. There are a number of workarounds out there, for example, to remove the read-only flag from the drive but all of the fixes seem to just address the symptom that the drive can't be accessed. One solution is to uninstall VeraCrypt completely from the host machine in order to allow the guest to start.