24H2, VirtualBox 7.1.4, Guest OS Callee RC: E_INVALIDARG (0x80070057) Solution I found


Mark K

Well-known member
Member
Local time
10:35 AM
Posts
457
OS
Windows 11 Pro
Note - mostly documenting this for my reference and others if needed.

I run VirtualBox 7.1.4 r164945 (Qt6.5.3) in Windows 11 Pro x64 (Host OS), the same setup on several computers.

Guest OSes: Linux Mint / Windows 10 Pro / Windows 11 Pro.

Among these Windows computers (Host OS), I copy the "\VirtualBox VMs\<Guest_OS>" to the other computers. I have been doing this for years without a problem. Save tremendous time with setup and configurations.

Now when I copy a Guest OS ("\VirtualBox VMs\<Guest_OS>") from one computer to another, I now keep receiving the following error message:
Code:
Failed to open virtual machine located in C:/<Guest_OS_Path>/Linux Mint/Linux Mint.vbox.

Callee RC:
E_INVALIDARG (0x80070057)

Here are the files in the Linux Mint (Guest OS) folder:
-----
C:\<Guest_OS_Path>\VirtualBox VMs\Linux Mint
\Logs\*
\Linux Mint.nvram
\Linux Mint.vbox
\Linux Mint.vbox-prev
\Linux Mint.vdi
-----

I found in this article that if you keep rebuilding a new Guest OS entry, then manually add the *.VDI file, you can get the Guest OS to run again. I have been doing this a lot lately and wanting a quick solution to keep these Guest OSes running.

Reference: [Solved] E_INVALIDARG 0x80070057

Through trial-and-error after finding no real solutions via Google searches, I found that editing the guest OS *.vbox file can correct this error:

For instance, I edited the \VirtualBox VMs\Linux Mint.vbox file with removing the Image uuid tag within DVDImages:

From this:
Code:
      <HardDisks>
        <HardDisk uuid="{fed30fbc-6449-4642-a501-b6a57d620a6e}" location="Linux Mint.vdi" format="VDI" type="Normal"/>
      </HardDisks>
      <DVDImages>
        <Image uuid="{40f2d25c-adac-4a91-8cb6-c89a0c485850}" location="C:/Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso"/>
      </DVDImages>

to this:

Code:
      <HardDisks>
        <HardDisk uuid="{fed30fbc-6449-4642-a501-b6a57d620a6e}" location="Linux Mint.vdi" format="VDI" type="Normal"/>
      </HardDisks>
      <DVDImages>
      </DVDImages>

This allows me to add the Guest OS in to VirtualBox and run it without any errors.

There may be other ways to correcting this error, I just found this method to solve the error for my Guest OSes in VirtualBox.
 
Windows Build/Version
Windows 11 Pro 26100.2605

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell 16 Plus DB16255
    CPU
    AMD Ryzen AI 7 350 w/ Radeon 860M 50 TOPS
    Motherboard
    Dell 0PKMHG
    Memory
    32GB LPDDR5X 7500 MT/s
    Graphics Card(s)
    AMD Radeon 860M integrated (shared memory)
    Sound Card
    Stereo speakers (2.5 W x 2 = 5 W total peak)/Realtek SounzReal/Dolby Atmos
    Monitor(s) Displays
    Displays: 16" 1920 x 1200 (Full HD+/WUXGA) 300 nits 60Hz *** Samsung - 27” Odyssey FHD IPS 240Hz G-Sync Gaming Monitor
    Screen Resolution
    1920x1080 @ 60Hz
    Hard Drives
    EG6 KIOXIA 1TB NVME
    Case
    Ice Blue
    Cooling
    "dual-fan" or "enhanced" air-cooling system
    Mouse
    Logitech M650 Wireless/Bluetooth
    Internet Speed
    800/600 Fiber
Thank you for this post.
Having gone over to the dark side (Linux Manjaro, KDE Plasma) I run Win 11 in VirtualBox for the odd thing I can't do in Linux.
I also run Kubuntu and try out other distributions quite regularly. Just for the hell of it, really - all on separate SSDs, swapping them out. Thirty second job.
Like you, I install the VMs on a separate drive, so after swapping out OS SSDs they should work - but recently stopped working without fresh installs of the guest OS.
Anyhow, yesterday I decided to scour the web for a solution to the error message again, and up popped your post.
Sorted within 5 mins and Win11 VM running perfectly again.
I noted that the 'DVD Images text' in the file pointed to the old location for the Win11 installation iso which had been moved when I re-arranged my back up drive folders.
Once again, thanks :-)
 

My Computer

System One

  • OS
    Manjaro KDE
    Computer type
    PC/Desktop
Note - mostly documenting this for my reference and others if needed.

I run VirtualBox 7.1.4 r164945 (Qt6.5.3) in Windows 11 Pro x64 (Host OS), the same setup on several computers.

Guest OSes: Linux Mint / Windows 10 Pro / Windows 11 Pro.

Among these Windows computers (Host OS), I copy the "\VirtualBox VMs\<Guest_OS>" to the other computers. I have been doing this for years without a problem. Save tremendous time with setup and configurations.

Now when I copy a Guest OS ("\VirtualBox VMs\<Guest_OS>") from one computer to another, I now keep receiving the following error message:
Code:
Failed to open virtual machine located in C:/<Guest_OS_Path>/Linux Mint/Linux Mint.vbox.

Callee RC:
E_INVALIDARG (0x80070057)

Here are the files in the Linux Mint (Guest OS) folder:
-----
C:\<Guest_OS_Path>\VirtualBox VMs\Linux Mint
\Logs\*
\Linux Mint.nvram
\Linux Mint.vbox
\Linux Mint.vbox-prev
\Linux Mint.vdi
-----

I found in this article that if you keep rebuilding a new Guest OS entry, then manually add the *.VDI file, you can get the Guest OS to run again. I have been doing this a lot lately and wanting a quick solution to keep these Guest OSes running.

Reference: [Solved] E_INVALIDARG 0x80070057

Through trial-and-error after finding no real solutions via Google searches, I found that editing the guest OS *.vbox file can correct this error:

For instance, I edited the \VirtualBox VMs\Linux Mint.vbox file with removing the Image uuid tag within DVDImages:

From this:
Code:
      <HardDisks>
        <HardDisk uuid="{fed30fbc-6449-4642-a501-b6a57d620a6e}" location="Linux Mint.vdi" format="VDI" type="Normal"/>
      </HardDisks>
      <DVDImages>
        <Image uuid="{40f2d25c-adac-4a91-8cb6-c89a0c485850}" location="C:/Program Files/Oracle/VirtualBox/VBoxGuestAdditions.iso"/>
      </DVDImages>

to this:

Code:
      <HardDisks>
        <HardDisk uuid="{fed30fbc-6449-4642-a501-b6a57d620a6e}" location="Linux Mint.vdi" format="VDI" type="Normal"/>
      </HardDisks>
      <DVDImages>
      </DVDImages>

This allows me to add the Guest OS in to VirtualBox and run it without any errors.

There may be other ways to correcting this error, I just found this method to solve the error for my Guest OSes in VirtualBox.
Solution worked for me! Thanks!
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    Laptop
    Manufacturer/Model
    Dell
Thank you for this post.
Having gone over to the dark side (Linux Manjaro, KDE Plasma) I run Win 11 in VirtualBox for the odd thing I can't do in Linux.
I also run Kubuntu and try out other distributions quite regularly. Just for the hell of it, really - all on separate SSDs, swapping them out. Thirty second job.
Like you, I install the VMs on a separate drive, so after swapping out OS SSDs they should work - but recently stopped working without fresh installs of the guest OS.
Anyhow, yesterday I decided to scour the web for a solution to the error message again, and up popped your post.
Sorted within 5 mins and Win11 VM running perfectly again.
I noted that the 'DVD Images text' in the file pointed to the old location for the Win11 installation iso which had been moved when I re-arranged my back up drive folders.
Once again, thanks :-)
Hi there
@krisdne
If you are using Linux with KDE particularly as a HOST machine - why bother with Virtual Box (I'm NOT saying it's no good BTW) but run KVM/QEMU instead -- it's got really great performance , nice easy GUI for Virtualmachine management, greate dynamic USB re-direction and is a Type 1 Hypervisor (similar to HYPER-V in Windows) and is part of the linux kernel.

Most of the Windows machines I run are VM's under KVM/QEMU. Install KVM/QEMU and the Virtual machine manager. Also download the virtio iso from the fedora site. This adds for Windows guests the equivalent to Virtual box additions etc. (Install the drivers on the GUEST BTW). For windows VM's simply use the "TPM emulator" and don't bother with secure boot.

Screenshot_20251207_111101.webp

CPU usage - minimal and when running nothing on Windows -- almost ZERO !!== another advantage is that if YOU log off the host the VM is still acessible to others who might have an account on the machine -- whereas things like Virtual box and Vmware workstation run under the USER's task so exit when that user logs off.

Another advantage on QEMU / KVM on Linux is that since it's part of the distro's software you don't get the odd problem such as kernel headers being out of date with parts of Vmware particularly after updates / upgrades.

Cheers
jimbo
 
Last edited:

My Computer

System One

  • OS
    Windows XP,11 Linux Fedora Rawhide pre-release 45
    Computer type
    PC/Desktop
    CPU
    2 X Intel i7
    Screen Resolution
    4KUHD X 2

Latest Support Threads

Back
Top Bottom