[Solved] Windows Update now VM's Not Showing in Virtualbox
Posted: 13. Mar 2013, 18:34
The only thing that has happened is a windows security update.
This happens frequently, and normally causes no problem. But,
this time when I start Virtualbox, all of my virtual machines have
disappeared so this is what I see: I tried restoring from my backup, but my backup had no changes
to make, so the VirtuaBox VM,s direcory has not changed. I also
restored from the hidden folder .Virtualbox with no joy.
My Virtualbox folder is as it always has been: What could cause this problem, and how can I restore these VM's
As I say, nothing has changed in my directories. I am sure of this
because all of the checksums for the backups are correct.
How can this happen? Could it really be the result of a security
update. I am hesitant to back out the Microsoft updates because
I am not sure what problems that that may cause.
Does anyone have any ideas about this. Thanks in advance for
any help that You may have to offer.
I'm treating this with kid-gloves right now because I don't want
to repeat an experience I had before when I had to reconstruct all
of my Virtualbox VM's one at a time. I have considerable work
invested here, and last time it took 3 month of work to re-work
all of my VM's. This is what I want to avoid.
Help Please!!!
73
-grace
NNNN
z
This happens frequently, and normally causes no problem. But,
this time when I start Virtualbox, all of my virtual machines have
disappeared so this is what I see: I tried restoring from my backup, but my backup had no changes
to make, so the VirtuaBox VM,s direcory has not changed. I also
restored from the hidden folder .Virtualbox with no joy.
My Virtualbox folder is as it always has been: What could cause this problem, and how can I restore these VM's
As I say, nothing has changed in my directories. I am sure of this
because all of the checksums for the backups are correct.
How can this happen? Could it really be the result of a security
update. I am hesitant to back out the Microsoft updates because
I am not sure what problems that that may cause.
Does anyone have any ideas about this. Thanks in advance for
any help that You may have to offer.
I'm treating this with kid-gloves right now because I don't want
to repeat an experience I had before when I had to reconstruct all
of my Virtualbox VM's one at a time. I have considerable work
invested here, and last time it took 3 month of work to re-work
all of my VM's. This is what I want to avoid.
Help Please!!!
73
-grace
NNNN
z