VM has become 'inaccessible' - Vagrant no longer working

Question

For some reason this morning when I run \'vagrant up\' I get the following error (this has worked absolutely fine for over a year)

Your VM has b         


        

Answer 1

this works for me:

In my "C:\Users{user}\VirtualBox VMs{vm-id}" folder are two files

• {vm-id}.vbox-prev
• {vm-id}.vbox-tmp

Renaming from "{vm-id}.vbox-tmp" to "{vm-id}.vbox" solved my problem and i can call "vagrant up"