Note: I'm finding that the VMMR0/CoreIntegrity problem appears to be fixed in VirtualBox 6.1.32.
I can now start Virtual Box VMs again with Core Integrity on. unlike 6.1.28 and 6.1.30
(Win 10 Pro 19044.1499 x64)
Discuss the 6.1.30 release
-
- Posts: 48
- Joined: 10. Dec 2012, 16:13
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Arch Linux, Windows
Re: Discuss the 6.1.30 release
I am still on VB 6.1.30. I have set the Update settings to check once a day for a new stable version. Every morning I get the message that a new version 6.1.32 is available. Today I thought I should look here in the forum and I noticed that 6.1.34 is available since about a week.
This means there is a minor bug in the update check: it does not report the latest version.
I have skipped 6.1.32 because of too many bug reports. 6.1.34 looks better, so I want to give it a try.
This means there is a minor bug in the update check: it does not report the latest version.
I have skipped 6.1.32 because of too many bug reports. 6.1.34 looks better, so I want to give it a try.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Discuss the 6.1.30 release
It looks like 6.1.34 was not registered on the download server (or source control system) with the correct release date, so the server apparantly thinks that 6.1.32 is still the latest release (a release can be called anything, so the fact that the label contains digits and some of those digits are higher... doesn't seem to mean anything).PeterE wrote:I should look here in the forum and I noticed that 6.1.34 is available since about a week.
This is mostly meaningless to us, the software itself still works fine, it just has the odd minor side effect here and there.
-
- 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: Discuss the 6.1.30 release
That's (mostly) deliberate behavior: New VirtualBox updates get manually unlocked on the VirtualBox update server, to give early adopters a chance to test before the masses get trapped by "new and improved bugs".PeterE wrote:This means there is a minor bug in the update check: it does not report the latest version.
-
- Posts: 48
- Joined: 10. Dec 2012, 16:13
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Arch Linux, Windows
Re: Discuss the 6.1.30 release
Ok, that's good to know...