Discuss the 6.1.32 release

[arudnev]

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

Changelog is here.

[Thomas16093]

Hello,

So, I don't really know what"s happening with my virtualbox/machine all i know is it's started after upgrading to VirtualBox 6.1.32.
To explain it the better i can, when I want to install a Windows 10/11 guest virtualbox will be very glitch ( screen flashing black ) after the first restart of the installation.
Windows 10 will stay on a black screen.
Windows 11 will be setup without any actions and will arrive to a login screen. And if I try to login a message will appear about the session was closed because of DWM.

I configured my VM with : 2 cores, 4096 Mo of RAM, 70 GB of storage and VboxSVGA (3D acceleration, 256MB) + EFI.

All of this problems keeps happening even after downgrading back to 6.1.30 and even after a complete uninstall of VirtualBox
All my other VMs ( Win 10/7 or Ubuntu ) work perfectly, I just can't create a new one.

Is someone has already had a problem like this and manage to solve it ?

Thanks in advance.

Windows 10 Home 64 Bit
VirtualBox 6.1.30
VirtualBox Extension Pack Version: 6.1.30 r148432 on host
No addition on guest ( doesn't work )
Hyper-v is active because of WSL 2

[twilliams_on]

Forgive me I put this in the wrong forums.

When I upgrade to 6.1.32, the guest randomly freezes, and needs to be restarted.

Host: Windows 10

Guest Mint Linux

[AndyCot]

If you go back to 6.1.30 does this fix LM freezing?

[mpack]

Please provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

[twilliams_on]

Actually going back to 6.1.30, works thank you.

[AndyCot]

I had the same problem and going back fixed it. Looks like 6.1.32 is a buggy release like 6.1.28 was, but different bugs this time.

[mpack]

Looks like 6.1.32 is a buggy release like 6.1.28 was

If you have evidence of bugs in 6.1.32 then you should be describing that evidence in the 6.1.32 discussion topic. Unforunately that seems to be the one topic you have not posted this info in.

IMO, encouraging people - as a first resort - to scurry back to the comfy blanky surroundings of the previous version will get us nowhere. If VirtualBox has bugs then we need to pin down the details so the devs can fix them and thereby improve the product for all of us. Hiding from the bugs will not do that.

In fact, I think I'm going to move all these posts to the discussion topic.

[Kilgore]

I am running into something very similar. All of my Win10 images will boot to black. I have not tried removing and downgrading yet. Will try to load an image and see what it does as well and will report back. Let me know if removing Virtual Box and re-installing 6.1.30 resolves.

[HorstS]

W7 64 bit and Ubuntu 20 64 bit do not boot (at least not within 20 minutes).
kali (64 bit) ends on console level without GUI

W7 32 bit works ok and so does tails
With 6.1.30 everything worked fine.
Host is W10 64

[mpack]

Please attached a zipped VM log when making a problem report.

[Kilgore]

FYI. I downgraded to version 6.1.30. Everything works now. Not sure what causes 6.1.32 to blow up. I'm glad I ran this on a test box before I deployed it to my main workstation.

[mpack]

Not sure what causes 6.1.32 to blow up.

And neither will the rest of us be able to help until someone provides evidence. So far, every time someone provides the evidence the problem is immediately solved. So this notion that 6.1.32 has a problem seems to be based entirely on hearsay.

[twilliams_on]

Are these the logs you need?

[twilliams_on]

Here is another example here