Software⏱️ 3 min read📅 2026-06-11

How to Fix: Virtual Box VERR_FILE_NOT_FOUND error after copying virtual machines

VirtualBox VERR_FILE_NOT_FOUND error after copying virtual machines, how to fix and restore.

Quick Answer: Check if the .vdi file is in the correct location and has the correct permissions. Try using the integrated export functionality instead of manually copying files.

📋 Table of Contents

  1. 🔍 Why This Happens
  2. 🛠️ Step-by-Step Verified Fixes
  3. ✨ Wrapping Up

The VirtualBox VERR_FILE_NOT_FOUND error is a frustrating issue that can occur when trying to start virtual machines on Ubuntu 18.04 after migrating from Windows 10. This error is typically caused by missing or corrupted files, which can be due to incorrect file copying during the migration process.

Restoring the virtual machines and resolving this error requires attention to detail and a methodical approach. In this guide, we will walk you through the steps to resolve the issue and get your virtual machines up and running again.

🔍 Why This Happens

  • The primary reason for this error is that VirtualBox requires specific file formats (.vbox, .vdi) to be present in the virtual machine folder. When these files are copied incorrectly during migration, they can become corrupted or missing, leading to the VERR_FILE_NOT_FOUND error.
  • Another possible cause is that the file formats were not correctly converted during the migration process. This can happen if the export functionality was used instead of copying the files manually.

🛠️ Step-by-Step Verified Fixes

Re-Export Virtual Machines using the Integrated Export Functionality

  1. Step 1: Open VirtualBox and select the VMs that you want to restore.
  2. Step 2: Go to File > Export > Save as... and choose the correct file format (.vbox, .vdi).
  3. Step 3: Select the folder where you want to save the exported files and click 'Save'.
  4. Step 4: Repeat this process for each virtual machine you want to restore.

Manually Repair Corrupted Files

  1. Step 1: Locate the .vbox file in the folder and check its integrity using a tool like `checksum` or `md5sum`.
  2. Step 2: Compare the checksums with the original values to identify any corrupted files.
  3. Step 3: Use a tool like `fix-vbox-file` to repair the corrupted files. Note: This command is specific to Ubuntu and may not work on other Linux distributions.
  4. Step 4: Repeat this process for each virtual machine you want to restore.

✨ Wrapping Up

Restoring your virtual machines requires patience and attention to detail. By following these steps, you should be able to resolve the VERR_FILE_NOT_FOUND error and get your virtual machines up and running again on Ubuntu 18.04.

Did this fix your problem?

If not, try searching for specific error codes.

🔍 Search Error Database

❓ Frequently Asked Questions

🛠️ Related Fixes

How to Fix: Pc crashes shortly after launching game (rainbow

Fix Pc crashes shortly after launching game (rainbow six siege). Compl

How to Fix: Installing an APK on a locked down phone

Installing an APK on a locked down phone: Try using a rooted device, e

How to Fix: New PC build- no signal and no clue

Fix New PC build- no signal and no clue. Complete troubleshooting guid