Upgrade from 6.1.26 to 6.1.28 Breaks All VMs
Upgrade from 6.1.26 to 6.1.28 Breaks All VMs
Same issue on Windows10, reverted back to 6.1.26. I don't understand why they tell you to update when the new version destroys all your VM's!.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Upgrade from 6.1.26 to 6.1.28 Breaks All VMs
You don't actually think the devs knew the new version would 'destroy all your VM's'? Kind of makes it hard to build a good reputation if they did, eh? Don't let's be silly...
.28 introduced an unexpected bug. The 'destroyed' VMs should be resurrected under 6.1.26.
.28 introduced an unexpected bug. The 'destroyed' VMs should be resurrected under 6.1.26.
Re: Upgrade from 6.1.26 to 6.1.28 Breaks All VMs
How about making a sticky post about the 6.1.28 issue?
Another suggestion, but it will not go down well is to pull the windows 6.1.28 release.
Another suggestion, but it will not go down well is to pull the windows 6.1.28 release.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Upgrade from 6.1.26 to 6.1.28 Breaks All VMs
I'd guess that many (if not the majority of) users with VirtualBox on Windows hosts have Hyper-V disabled, because VirtualBox VMs are slow otherwise. In consequence, VirtualBox 6.1.28 works well for them.AndyCot wrote:Another suggestion, but it will not go down well is to pull the windows 6.1.28 release.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Upgrade from 6.1.26 to 6.1.28 Breaks All VMs
We already have the Discuss the 6.1.28 release topic, I don't see any need for a second topic to discuss version specific release issues.AndyCot wrote:How about making a sticky post about the 6.1.28 issue?
Locking this one.