Discuss the 6.1.28 release

This is for discussing general topics about how to use VirtualBox.
arudnev
Oracle Corporation
Posts: 39
Joined: 20. Feb 2018, 14:59

Discuss the 6.1.28 release

Post by arudnev »

Discuss the VirtualBox 6.1.28 release here.
You can download the release here.
VirtualBox 6.1.28 is a maintenance release.

Changelog is here.
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Discuss the 6.1.28 release

Post by mpack »

6.1.28 adds a Windows 11 guest template. Note however that this works by indirectly provoking the well known Win11 registry tweaks that make Win11 compatible with older hardware. It does not make VirtualBox compatible with the declared requirements of Win11 - that is something apparently planned for the future.

So to forestall the inevitable "my VM still fails the Win11 compatibility checks" posts, please see this topic for an explanation.

To summarise the important post there:
fth0 wrote: VirtualBox 6.1.28 provides Windows 11 as a guest OS version, and an unattended installation that should automatically set the necessary registry keys. It provides neither a virtual TPM nor Secure Boot, so one of the known methods have to be used to circumvent the Windows 11 requirements.
BlueLagoon
Posts: 25
Joined: 18. Jun 2015, 07:24

Re: Discuss the 6.1.28 release

Post by BlueLagoon »

Hardware = Dell Inspiron 15 7591 Laptop

Current Host –
Windows 10 Home 21H1 Build 19043.1288 (Qt5.6.2)
VirtualBox 6.1.28 r147628 (Qt5.6.2)
Windows Update says - This PC can run Windows 11

Current Guest –
Windows 10 Pro 21H1 Build 19043.1288
Windows Update says - This PC currently doesn’t meet all the system requirements for Windows 11
PC Health Check says – This PC must support Secure Boot also TPM 2.0 must be supported and enabled on the PC


Sorry for being a bit thick, but in light of the above can I still upgrade the Host to Windows 11 and the existing Guest, still running Window 10, will still work?
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Discuss the 6.1.28 release

Post by mpack »

I had a Windows 11 guest running quite sweetly in 6.1.26, so yes of course you can do the same in 6.1.28. The only difference with the latter is that it automates some of the tricks I had to pull, such as downloading a specialized media creation tool.

Windows 11 as a host is a separate issue. Win11 is not yet listed as a supported host in the user manual, but I believe that some users have successfully tried it.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Discuss the 6.1.28 release

Post by scottgus1 »

Windows 10 as a VM should still work.
BlueLagoon
Posts: 25
Joined: 18. Jun 2015, 07:24

Re: Discuss the 6.1.28 release

Post by BlueLagoon »

Thank you mpack and scottgus1
foobunny
Posts: 7
Joined: 12. Oct 2021, 15:38

Re: Discuss the 6.1.28 release

Post by foobunny »

mpack wrote:6.1.28 adds a Windows 11 guest template. Note however that this works by indirectly provoking the well known Win11 registry tweaks that make Win11 compatible with older hardware. It does not make VirtualBox compatible with the declared requirements of Win11 - that is something apparently planned for the future.

So to forestall the inevitable "my VM still fails the Win11 compatibility checks" posts, please see this topic for an explanation.

To summarise the important post there:
fth0 wrote: VirtualBox 6.1.28 provides Windows 11 as a guest OS version, and an unattended installation that should automatically set the necessary registry keys. It provides neither a virtual TPM nor Secure Boot, so one of the known methods have to be used to circumvent the Windows 11 requirements.
This means that a clean install of a Windows 11 VM would not work, but that installing a Windows 10 VM using the Windows 11 template and then upgrading it to Windows 11 would work. Is that correct?

Edit: Never mind, I answered my own question. I followed these steps: created a new VM from the Windows 11 template, installed Windows 10 21H1 in the VM, install the Guest Additions in the VM and rebooted, ran the Windows 11 setup. The setup returned "This PC doesn't currently meet Windows 11 system requirements. Here's why: The PC must support TPM 2.0. The PC must support Secure Boot."

I'll just wait for version 7.0.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Discuss the 6.1.28 release

Post by scottgus1 »

foobunny wrote:This means that a clean install of a Windows 11 VM would not work, but that installing a Windows 10 VM using the Windows 11 template and then upgrading it to Windows 11 would work. Is that correct?
Apparently not:
fth0 wrote:VirtualBox 6.1.28 provides Windows 11 as a guest OS version, and an unattended installation that should automatically set the necessary registry keys. It provides neither a virtual TPM nor Secure Boot
This looks to me like Windows 11 will install in 6.1.28 if an unattended installation is made, so registry hacks can be made to allow 11 for a non-TPM VM. Note Mpack's first post above.

So no raw unchanged Windows 11 installs yet. But hacked 11 installs are apparently possible.
scottgus1
Site Moderator
Posts: 20965
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Discuss the 6.1.28 release

Post by scottgus1 »

Please see Klaus's post here: for instructions on installing "registry-hacked" no-TPM Windows 11 in 6.1.28:
viewtopic.php?f=6&t=104042&p=506704#p506704
mingle
Posts: 63
Joined: 6. Jun 2015, 07:55

Re: Discuss the 6.1.28 release

Post by mingle »

Just installed 6.1.28 on a Windows 10 Pro 64-bit host.

Running Linux Mint 19.3 guests.

It seems a heck of a lot snappier than 6.1.26! Applications open in half the time and the entire guest-system feels super-responsive.

Very happy.

Cheers,

Mike.
Etepetete
Posts: 400
Joined: 7. Oct 2009, 10:19
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Slackware 14.2
Location: Berlin

After updating, VM will not start

Post by Etepetete »

After updating to version 6.1.28 I receive the following error message, when I start my VM.

Code: Select all

Für die virtuelle Maschine Slackware 14.2 konnte keine neue Sitzung eröffnet werden.

Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED).

Fehlercode: 
E_FAIL (0x80004005)
Komponente: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

The start is aborted.
Logs attached
Slackware_14.2-2021-10-22.zip
Log files
(29.85 KiB) Downloaded 18 times
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Discuss the 6.1.28 release

Post by mpack »

@Etepetete: according to the devs, some NEM (i.e. Hyper-v API) code under Win10 got broken while trying to make it Win11 compatible. If you are unwilling to disable Hyper-v then you should revert to 6.1.26 for now. No doubt a fix will soon be available as a test build, or simply wait for the next release.
Etepetete
Posts: 400
Joined: 7. Oct 2009, 10:19
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Slackware 14.2
Location: Berlin

Re: Discuss the 6.1.28 release

Post by Etepetete »

@mpack: Thanks for the quick response. I'll wait for the fix.
Best regards
jvachez
Posts: 2
Joined: 25. Oct 2021, 09:16

Re: Discuss the 6.1.28 release

Post by jvachez »

It's impossible to go back to version 6.1.26, 6.1.28 is breaking VM (VERR_NEM_VM_CREATE_FAILED error when going back on 6.1.26 with Windows 10 template).
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Discuss the 6.1.28 release

Post by mpack »

jvachez wrote:It's impossible to go back to version 6.1.26, 6.1.28 is breaking VM (VERR_NEM_VM_CREATE_FAILED error when going back on 6.1.26 with Windows 10 template).
That makes no sense. There is a known problem in 6.1.28, on Windows (<11) hosts only, which AFAIK cannot possibly be affecting you if you reverted to 6.1.26.

So what you actually have is a VERR_NEM_VM_CREATE_FAILED error, not a bug, and not new in 6.1.28. For resolution, put that word into Google along with "site:forums.virtualbox.org".
Post Reply