How to Fix VirtualBox VM Inaccessible Error on Windows 11

Your VirtualBox virtual machine suddenly shows as Inaccessible with a Document is empty error, and you cannot start it. This happens because VirtualBox cannot read the .vbox configuration file for that VM. The file is either empty, corrupted, or missing entirely. Your actual virtual disk data (the .vdi or .vmdk file) is almost always untouched. The steps below walk you through recovering your VM.

What Causes the VirtualBox VM Inaccessible Error

VirtualBox stores each virtual machine’s settings in a .vbox file, which is an XML document. When this file gets corrupted or wiped, VirtualBox cannot load the VM and marks it as inaccessible.

Why does this happen:

• A sudden system shutdown or power loss while VirtualBox was writing the config
• A disk write error or storage failure on the host drive
• Antivirus software quarantining or modifying the .vbox file
• A failed VirtualBox update or migration to a new host machine
• Accidental deletion or overwrite of the .vbox file

Fix 1: Replace the .vbox File with the .vbox-prev Backup

Every time VirtualBox saves your VM settings, it creates a .vbox-prev backup of the previous state. This is the fastest fix when your .vbox file is empty or corrupted.

1. Open File Explorer and navigate to your VM folder. The default path is:
   C:\Users\YourUsername\VirtualBox VMs\VMName\
2. Look for a file named VMName.vbox-prev in the same folder.
3. Copy VMName.vbox-prev and rename the copy to VMName.vbox, overwriting the broken file.
4. Open VirtualBox and check whether the VM loads correctly.

If VirtualBox still shows the VM as inaccessible after this, move to the next fix.

Fix 2: Re-Register the VM Without Removing It

When VirtualBox loses the pointer to your VM’s .vbox file but the file itself is fine, you can re-register the VM directly without removing anything. This avoids any risk of accidentally selecting Delete All Files.

1. Open Oracle VM VirtualBox Manager.
2. Click the Machine menu and choose Open (not Add).
3. In the file dialog, navigate to your VM folder: C:\Users\YourUsername\VirtualBox VMs\VMName\
4. Select the .vbox file (for example, Windows 11.vbox) and click Open.
5. The VM reappears in the list with a normal status.
6. Try starting it to confirm it works.

Fix 3: Manually Recreate the .vbox Configuration File

If neither the .vbox file nor the .vbox-prev file is recoverable, you can recreate the configuration manually. This requires you to know your original VM settings such as OS type, RAM, and the path to your virtual disk.

1. Open Notepad or any text editor.
2. Paste the following XML template and fill in your VM details:

<?xml version="1.0"?>
<VirtualBox xmlns="http://www.virtualbox.org/" version="1.19-windows">
  <Machine uuid="{YOUR-UNIQUE-UUID}" name="VMName" OSType="Windows11_64" snapshotFolder="Snapshots" lastStateChange="2024-01-01T00:00:00Z">
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid="{DISK-UUID}" location="VMName.vdi" format="VDI" type="Normal"/>
      </HardDisks>
    </MediaRegistry>
    <Hardware>
      <CPU count="2"/>
      <Memory RAMSize="4096"/>
      <Display VRAMSize="128"/>
    </Hardware>
    <StorageControllers>
      <StorageController name="SATA" type="AHCI" PortCount="1">
        <AttachedDevice type="HardDisk" port="0" device="0">
          <Image uuid="{DISK-UUID}"/>
        </AttachedDevice>
      </StorageController>
    </StorageControllers>
  </Machine>
</VirtualBox>

3. Replace VMName with your actual VM name, set the correct OSType, and point location to your existing .vdi or .vmdk file.
4. For the UUID values, generate new ones using PowerShell:

[guid]::NewGuid()

5. Save the file as VMName.vbox inside your VM folder.
6. Add the VM back to VirtualBox using Machine > Add and test it.

Fix 4: Repair the Global VirtualBox.xml File

If all your VMs show as inaccessible at once, or VirtualBox itself opens with a Document is empty error, the problem is not in any individual VM. The global registry file at C:\Users\YourUsername\.VirtualBox\VirtualBox.xml is corrupted. Renaming it forces VirtualBox to generate a fresh one, then you re-register your VMs manually.

1. Close VirtualBox completely. Open Task Manager and confirm no VirtualBox.exe process is running.
2. Open File Explorer and navigate to C:\Users\YourUsername\.VirtualBox\.
3. Rename VirtualBox.xml to VirtualBox.OLD.
4. If a file named VirtualBox.xml-prev exists in the same folder, rename it to VirtualBox-prev.OLD as well.
5. Launch VirtualBox again. It creates a new empty VirtualBox.xml and shows no VMs.
6. Use Machine > Open to browse to each VM’s .vbox file and re-add them one by one.
7. Check whether all VMs load correctly.

Fix 5: Restore the VM Folder to Its Original Location (VERR_PATH_NOT_FOUND)

The VERR_PATH_NOT_FOUND error appears when you move, rename, or copy the VM folder to a different location after adding it to VirtualBox. VirtualBox still looks for the folder at the old path and cannot find it.

1. Open Oracle VM VirtualBox Manager and hover your mouse over the inaccessible VM. The tooltip shows the exact folder path VirtualBox expects, for example D:\VirtualBox VMs\Windows 11.
2. Open File Explorer and search your drives, Desktop, Downloads, or any external storage to find the current location of your VM folder with the .vbox file.
3. Once you find it, move the entire VM folder back to the exact path shown in the tooltip. Make sure the folder name also matches exactly.
4. If you renamed the folder, right-click it and select Rename to restore the original name.
5. Reopen VirtualBox and check whether the VM is accessible again.

If moving the folder back is not possible (for example, the original drive is gone), use Machine > Open to re-register the VM from its new location instead.

Fix 6: Check File Permissions on the VM Folder

If VirtualBox cannot read or write to the VM folder, it may report the VM as inaccessible even when the .vbox file looks intact.

1. Open File Explorer and right-click your VM folder.
2. Select Properties, then go to the Security tab.
3. Click Edit and make sure your user account has Full Control.
4. Apply the changes and restart VirtualBox.

You can also reset permissions from an elevated Command Prompt using icacls:

icacls "C:\Users\YourUsername\VirtualBox VMs\VMName" /grant YourUsername:F /T

Replace YourUsername and VMName with your actual values.

Fix 7: Disable Antivirus Interference

Antivirus software sometimes locks or modifies VirtualBox configuration files, especially on first launch or after a signature update.

1. Open your antivirus or Windows Security settings.
2. Add your VirtualBox VMs folder to the exclusions or exceptions list.
3. The default path to exclude is C:\Users\YourUsername\VirtualBox VMs\.
4. Restart VirtualBox and check if the VM recovers.

Fix 8: Repair or Reinstall VirtualBox

A broken VirtualBox installation can corrupt how it reads and writes VM configuration files. Repairing it restores missing components without removing your VMs.

1. Press Win + R, type appwiz.cpl, and press Enter.
2. Find Oracle VirtualBox in the list and click Change.
3. Select Repair and let the installer finish.
4. If repair does not help, uninstall VirtualBox completely, download the latest version from virtualbox.org, and reinstall.
5. After reinstalling, add your VMs back using Machine > Add.

Related Guides

• How to Fix VirtualBox Error in SUPR3HardenedWinReSpawn
• Virtual Media Manager Not Showing in VirtualBox (How to Fix)
• How to Install and Set Up VirtualBox on Windows 11

Frequently Asked Questions