[WorksForMe] Risky to update from 412 to latest version?

[Dabola]

In my stationary PC (win7-64) I have a rather old version of VB; 4.12. This is due to a Mac guest. That one is not so important any longer so I would like to try to update VB to a more up to date version/latest. Would that be risky to make in one single step?

Close down all the guests, make a copy of the .Virtualbox folder, perhaps remove all the snapshots before. What do you think?

[socratis]

In my stationary PC (win7-64) I have a rather old version of VB; 4.12. This is due to a Mac guest.

OSX guests are only supported on Apple hardware (which you do not seem to have). See "OSX guests on non-Apple hardware".

I would like to try to update VB to a more up to date version/latest. Would that be risky to make in one single step?

No, not really. It should be a straight-forward process, provided that you follow your own instructions which are spot-on!

No saved states, VMs completely shutdown, preferably no snapshots either.

BTW, there's no 4.12 VirtualBox, there's 4.0.12, 4.1.12, 4.2.12 and 4.3.12. Can you be more precise?

[Dabola]

Yes, I know about the Apple limitation. Anyhow it funked with the old version. As in which is 4.1.10r76836. Installed August 2015.

Do you think it will reduce the risk if i make a intermediate step by installing a version approx two years old? Start and stop the guests and then finally update to the lastest version. Less risky?

[socratis]

I don't think that it's going to be less risky. I've never had any problems switching from 4.x to 5.x to 6.x. But take a backup first, as you mentioned, if anything goes bad you can still restore from the backup...

[Dabola]

Thank you very much for your advice, socratis.

Then I will try tonight to jump directly to the latest version. I have faced problems before and got saved by the backup so why not this time....

[socratis]

Nice... Let us know if you run into any snugs...

[Dabola]

The update from v 4.1.1 tø 6.0.1 went well. Everything looked okay. After two weeks I started to make the first changes inside the guests. Snapshots.. Due to a new audio system/driver I faced some problem with a Win7-64 expecially for audio/music. When this was solved I updated the GuestAdd. for 5-6 other Win-guests. Then I made a mistake. Before restarting the guest I wanted to check if it was possible to start the old Mac guest I installed by v 4.1.1. No, it wasn't. But I let the guest grab the mouse, and didn't succeed to bring it back to the host. Neither by the keyborard, nor putting the cable into another usb-port or any other way. I was stressed up and make a mistake; I cutted the electricity to the stationary computer. After restarting and running VB I could see that 3 win-guests are Inaccessible. No copies.

For sure its because I updated the GuestAdd. and cutted the power before closing VB properly. Are there any hope for me to save these 3 guests. Same error message for all 3. The 1st look like this:

Cannot attach medium 'C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso' {4e9bd7a7-2bee-4f9c-9fe0-8990bc989a5d}: medium is already associated with the current state of machine uuid {cd617fea-0c58-4fc5-a88b-19b32ad44ff9}!.
Result Code:
VBOX_E_OBJECT_IN_USE (0x80BB000C)
Component:
MediumWrap
Interface:
IMedium {ad47ad09-787b-44ab-b343-a082a3f2dfb1}

**************'
The same problem two years ago here viewtopic.php?f=2&t=84364&p=400445&hili ... le#p400445 was solved by editing the .vbox file. Ive never edited that before. Could this be a way to start? (All the other guests are Powered Off already - except the 3 other Inaccessible). (I am not able to Show Log either -greyed out).

Could it be an idea to start the 3 other win guests where I updated the GuestAdd. and remove the GuestAdd.iso?

I look forward to your advice.

[socratis]

The update from v 4.1.1 tø 6.0.1 went well. Everything looked okay.

Then I can close this thread as [WorksForMe].

I wanted to check if it was possible to start the old Mac guest

I already told you there will be a discussion of OSX guests on non-Apple hardware:

OSX guests are only supported on Apple hardware (which you do not seem to have). See "OSX guests on non-Apple hardware".

Any such threads are locked, and if you keep on doing that, you're going to be banned.

I was stressed up and make a mistake; I cutted the electricity to the stationary computer.

That's not "a mistake", that's a recipe for a disaster!

For sure its because I updated the GuestAdd. and cutted the power before closing VB properly

We're going to need some evidence about that, but not here, open a new thread with an appropriate title. We like to observe the "One issue, one thread" rule...