I have a UM773, a UM890 (nice) and an Asrock 8840U. Even though they are all recent AMD SoC's, they are need different configurations to disable VBS. Amazing. I now have to think that part of the issue is how Windows 11 24h2 interacts with the BIOS. Crazy.
Original Message:
Sent: Jan 21, 2025 02:21 AM
From: RaSystemlord
Subject: Windows and VBS Host
Good discussion opener - still, no other comments.
Yes, you might be right there - there are many choices and the responsibility is not that clear. Software company cannot possibly anticipate everything that these guys that you listed are doing.
However, based on the writings on these pages, is it just 17.6.x versions to blame? I haven't read any problems with 17.5.2 or before that. I tested that and by default there were no problems on 5 different OS cases (including win&linux).
It is still NOT that simple: I didn't have AMD with Win 11 (Win 10 with AMD I am using all the time as a Host) and I have no experience on Nested virtualization (because currently I have no use for that). Also, I paid no attention to VBS in my testing - maybe some (even typical) group policy would have made things differently?
Original Message:
Sent: Jan 18, 2025 10:14 PM
From: kasper
Subject: Windows and VBS Host
WIndows 11 24h2 and VBS. Its a crap shoot. Have to put the blame on Microsoft. Maybe AMD/Intel too.