ERROR: Failed to load the NVRAM store from the file

[oracle_VM]

When a VM is starting the following error arises:

Failed to load the NVRAM store from the file (VERR_INVALID_NAME).
Can't attach Nvram Storage driver (VERR_INVALID_NAME).
Result Code:
E_FAIL (0X80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

How to fix this?

[scottgus1]

This is apparently a new error, web-searching it doesn't return any results here on the forum.

Was this an imported VM, or did you make it yourself?

[mpack]

A VM log wouldn't go amiss.

[oracle_VM]

It is an imported VM .ova file. I found a solution to only change the name of the VM, the error is gone now.
Thanks for your replies.

[scottgus1]

Thanks for the update. What was the old name, and what did you change it to? Maybe there's a bug to be squished.

[KillSwitch]

I had this same issue

My VM was CF2021 WIN11 DJ

i changed it to just CF2021 and boots fine

[scottgus1]

My VM was CF2021 WIN11 DJ

i changed it to just CF2021 and boots fine

Intriguing, KillSwitch, thanks for the report!

I see that the failing VM name had spaces, and the successful VM name had none. Maybe an NVRAM store file can't have spaces in the name? Or there is a "lack of double quotes" bug?

Could you please try renaming the VM to something completely different, two letters and a space between:

A B

Then see if it imports. If it does not, rename to a single letter:

A

and try again. Please let us know what happens.

[diegoatwa]

When a VM is starting the following error arises:

Failed to load the NVRAM store from the file (VERR_INVALID_NAME).
Can't attach Nvram Storage driver (VERR_INVALID_NAME).
Result Code:
E_FAIL (0X80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

How to fix this?

Had the same issue, renaming the machine didn't work for me.

What solved my problem was to delete the `*.nvram` file that is in the home folder of the VM

Details of how this issue arose
After an external error filled the hosting disk in `/var/log/syslog` with repeated logs, the hosting restarted without turning off the VM, after clearing the `syslog` and starting the hosting the VM presented the same error that our friend mentioned above.

[scottgus1]

Interesting, Diego! Though I wonder, since "nv" means non-volatile, if deleting it could be a problem for the OS?

Please check on the space-in-the-name idea above and see if it fits your situation.

[Epicwinner101]

When a VM is starting the following error arises:

Failed to load the NVRAM store from the file (VERR_INVALID_NAME).
Can't attach Nvram Storage driver (VERR_INVALID_NAME).
Result Code:
E_FAIL (0X80004005)
Component:
ConsoleWrap
Interface:
IConsole {6ac83d89-6ee7-4e33-8ae6-b257b2e81be8}

How to fix this?

Had the same issue, renaming the machine didn't work for me.

What solved my problem was to delete the `*.nvram` file that is in the home folder of the VM

Details of how this issue arose
After an external error filled the hosting disk in `/var/log/syslog` with repeated logs, the hosting restarted without turning off the VM, after clearing the `syslog` and starting the hosting the VM presented the same error that our friend mentioned above.

Legend!! I was having this same issue, renaming the VM did nothing but soon as I deleted the .nvram file the VM booted perfect.

[Götterfleisch]

Same problem, renaming does not work, no nvram file in VM folder.

I am trying to move my VM's to another internal disk, 9 VM's work fine, only one remains with the nvram error.

This was the only one with a snapshot. It was an old snapshot so I deleted it and then it worked to move this VM without error.

Maybe this will help someone.

[Glootie]

[RESOLVED] Just remove the <vm name>.nvram where the vm is stored

[RodneyA]

In case anyone is still having issues. I imported the latest Parrot 6.1 Security Edition (this was an ova). What was happening is that is was failing to create any nvram file for me to delete (to have it recreated) and this was causing non-start errors. After trying several methods mentioned, I went to settings -> system -> motherboard and unchecked "Enable EFI (for special OS's only) and unchecked all but the Hard disk option. I ran it and it gave me a "cannot find boot media..." which I expected, I went back into the same settings, checked the Enable EFI and the Optical, ran it and it created the nvram file and is up and running. Hope this helps.

[zombodotcom]

Had this issue either because I made it as a startup with this script which boots it at start of windows. I also upgraded to windows 11 at the same reboot.

woops

Code: Select all

I have an example of how to autostart a VirtualBox VM during Windows startup. I'm running Windows 10, but it shouldn't be much different on Windows Server 2016.

The startup folder on my system is:

    C:\Users\chriwill\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

In that folder I placed a batch file kubuntu.bat with following content:

"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" startvm kubuntu --type headless

In my example the VM is named kubuntu. You'll have to change it for your instance.

Addon:

If you need help finding the startup folder on your windows instance press keys Windows + R and enter shell:startup.

Reference: 8.19. VBoxManage startvm

Got the error.

Deleted the .nvram

Booted right back up.

Running Home assistant VM

[FMJ999]

I got the issue after VM import.
> Deleting the .nvram file didn't t help
> Renaming the VM didn't t help
Still the same error

But ... Then I closed the Virualbox Manager + restarted it and .... voilà ! Enjoy !