Discuss the VirtualBox 7.2.0_RC1 release here

[galitsyn]

You can download the release here.
Changelog is here.

[Air Force One]

At the end of the GA installation, the guest OS just crashed and rebooted this way, without presenting the dialog for reboot now or later. But this sometimes happens in the betas. Otherwise everything works fine till now, and all missing translations are also here now.

[Simple07]

Uninstalled VirtualBox 7.1.12 and deleted the Oracle folder, also deleted Vbox* files from Windows\System32\Drivers.
Installed VirtualBox 7.2.0_RC1.

- Windows XP 32bit starts but fails to install Guest Additions 7.2.0 (error at the installing INF drivers' stage). But Guest Additions 7.1.12 installs successfully.

- Windows 7 32bit 2CPU starts fine and installs Guest Additions 7.2.0 successfully; all is well here.

- Windows 11 Build 27898 2CPU, it will kick open a black screen, but Windows 11 will not start. Tried different settings, to no avail. But changing the number of CPUs from 2 CPU to 1 CPU, 3 CPUs or 4CPUs starts Windows 11. However, at 3 or 4 CPUs Windows 11 is deadly slow and gets stuck at VirtualBox starting screen with the rotational ring frozen, even after increasing the allocated memory.

At 1 CPU, 6GB memory, Windows 11 starts fine but freezes when installing Guest Additions at the installing driver stage. Guest Additions installed fine, having increased the memory to 8GB. Reducing the memory to 6GB or 7GB and reinstalling Guest Additions freezes again!

One more comment, uninstalling Guest Additions from Windows 11 causes the same freezing effect even at 8GBs. Something is not quite right with memory manipulation/allocation? By the way, some behavior seems to be inherited from 7.1.xx.

I hope the developers are reading our comments as it would be futile if we are testing and reporting issues that the users cannot fix and the developers are not concerned about. Not every issue has an error code!

[multiOS]

@Simple07

I suspect that the Development Team will have difficulty following through problem reports that do not include supporting VBox.logs or Installation logs that show the issue(s) described, but must admit that I'm also a bit confused about the Beta feedback requirements as the RC1 Release announcement closing sentence states:

Please discuss the release here. If you want to report issues needing tracking, use https://github.com/VirtualBox/virtualbox/issues.

To use the GitHub Issue Tracker route does, of course, require GitHub User Registration; and I would hazzard a guess that not all members of this VirtualBox Forum/Beta Testers will welcome a GitHub Registration requirement. Those that do, I suspect, may well turn away from use of the User Forum and move their future issues/questions entirely to the GitHub Issues Page.

[Simple07]

Today, I downloaded and installed VirtualBox-7.2.0_RC1-170131-Win the same way as explained previously, this release seems to work fine with the installed Windows XP.

Alas, it does not operate the installed Windows 11 if 2 CPUs are allocated, but it would run on 1 allocated CPU. I removed the installed Windows 11 Build 27898 and prepared a new VM for Windows 11 Build 27919:
- The ISO will boot if 1 CPU is allocated but it will not install (2 CPUs minimum requirement).
- The ISO will NOT boot to perform installation if 2 CPUs are allocated (installation cannot be performed, like the previous RC1 release).
- The ISO Does boot and install if 3 CPUs are allocated (speed seem ok).

After the successful installation, Windows will boot with 1, 3 and 4 CPUs, but NOT 2 CPUs.
Guest Additions installs successfully, but Windows 11 crashes when trying to uninstall Guest Additions.