6.1.32 is unusable

[macattack12]

I read the other thread, I am not running hyper V, verified all check boxes are unchecked in W10-64bit windows features settings dialog. Also MS Application Guard is not installed, I'm running Avira AV also so Defender is inactive completely.
With 6.1.32 installed I reran the 6.1.30 release installer and now all VM's work fine as they did before this new release, Linux Mint, Win8.1 and Win10 where none of these 3 would even boot with the new release.

Please advise.

[AndyCot]

What is the "other thread"?

Allot of people are not disabling hyper-v as just turning it off via the features does not necessarily turn it off. using the correct bcdedit will ensure it is turned off or on.

Can you please supply a log for 6.1.30 and 6.1.32 so it can be analyzed by other more knowledgeable forum users.

[macattack12]

There are many threads appearing about issues with 6.1.32 causing all kinda of crawling speeds of VM's, here's one > viewtopic.php?f=2&t=105267

What I know is I was running 6.1.30 and my Linux Mint VM was running perfect, Win 8.1-64bit and Win 10-64bit VMs running perfect, I upgraded to 6.1.32 w/o any issue and then Linux Mint would boot and basically freeze after you opened a file explorer or terminal window, the Windows VM's were worse, they would attempt to boot and basically lock up. I had to use the "Power Off" options for all 3 of these VM's as there was no other way to even get control to shut them down, as none were usable any more at any level of control, no mouse, no keyboard, nothing.

I then re-download the older 6.1.30 version, installed it over the top of the terrible running 6.1.32 and now all 3 VM's perform as well as ever. So log or not, I'm not going to take the time to produce a log as again there are all kinds of problems being reported about 6.1.32 if you just take the time to review or search the forum. Whomever promoted .32 to release status without testing needs to go back and test it, find and fix the issue. Nothing else changed on my W10-64bit pc to cause this issue as proven by just overwriting a non working .32 instance with and old .30 and everything is fine again, its the .32 release that has problems.

[mpack]

There are many threads appearing about issues with 6.1.32

Every post in this forum is about a problem with some release, as the people with no problems don't tend to post about it. And yes, most of the recent posts will be about the current release, i.e. 6.1.32.

6.1.32 definitely has a couple of problems, in my mind they are minor and easily avoided except for those on Win10 or Win11 hosts who insist on enabling Hyper-v.

We can't tell if that applies to you until you provide a zipped VM log. If you refuse to do that then the discussion is over.

I'm going to move this topic to "Windows Hosts" since said discussion doesn't seem to concern the guest OS.

[AndyCot]

@macattack12 can you please supply a log from 6.1.30 and 6.1.32 so they can be analyzed to see what problem you may have as there are a few different ones and you have not given any info to help analyzing what the root case of your problem is.