BUG: Failed to load unit 'HGCM' (VERR_INVALID_PARAMETER)

[bar10dr]

Just got this one myself.

Easiest way to get out of it is just to re-create the folders, start the virtual image up, remove the shares and then delete the folders again.

[DougguoD]

Similar problem solved similarly...

I had very similar issue, but unlike most posts here, I had a fresh install Virtualbox 4.1.18.
No upgrades whatsoever. No snapshots whatsoever.

I saved my state after a couple hours of work on an airplane in my RHEL 5 64 bit guest. When reloading the saved state, same error. This post pointed me at Shared Folders which was the correct direction.

I decided to remove the ONE shared folder I had (configured with the "Make Permanent" checkbox only) while the VM was active and running in the middle of all my work (not sure why the UI lets you remove a shared folder while running if it can cause problems). Saved the state (no snapshots). Attempted to load the saved VM later in the day and got this generic error. My vbox xml file correctly reflected that the <SharedFolders /> node was indeed empty. However, once I manually re-added the one shared folder I had active before saving (pointing to a folder on my windows 7 host desktop) then the snapshot loaded like nothing happened. Lesson learned... properly shut down the guest OS before removing shared folders from the VM settings menu. For linux guest, confirm that mount/fstab/df don't indicate any remaining references to the shared folder after a clean stop, remove shared folders, restart... then the shared folders are removed safely from the configuration. Test a saved state reload to confirm problem is gone.



Thanks for saving me from having to lose my saved state and redo hours of work. Hope this helps someone else out there too.

[mors]

.. once I manually re-added the one shared folder I had active before saving then the snapshot loaded like nothing happened...

This solution worked for me too -- I re-added old shared folder into *.vbox configuration file and snapshot started without any problems. (VBox x64 version 4.2.6 r82870; Host: Windows 7 x64, Guest: Ubuntu 12.04 x64)

[Noquierospam1]

has a simple XP host under debian with kernel 3.2

shut VM down and told to save state.

tried to load VM with state from within a vnc4server session. Got this error message.

loaded VM from regular X. not problem. shutdown VM. got back to vnc, started it from scratch (no saved execution state). all worked.

[paulosilva888]

Suggestion, that solved my problem:
1. clone your virtual machine: just as a security procedure
2. discard saved state of the cloned machine
3. the machine will start again and you lost nothing, or maybe just the last changes done

I hope this helps you !!!

[caot]

in case that some else might run into the issue, here is a solution:

while the vbox is starting, kill the process, then you will see the vbox is aborted. then Start, you will see it works.

[Marikawn]

I too created a series of snapshots then deleted a parent of my current snapshot. This gave me the HGCM error in question. I had a shared drive but didn't have to mess with it at all.

My problem was SOLVED by simply opening up Virtual Box, right clicking on my VM and selecting 'Discard saved state...'

After that my VM was able to start normally.