Why does version 23H2 feel way more stable than 24H2?

Because 23h2 are 22h2 ( + little package to indicate we are 23h2 )

 

24H2 is just piece of crap from Microsoft

 

Keep win10 , skip any update, disconnect any dns. if you need to go on web, fireup a virtualmachine with linux with firefox and all is fine. Putting update blindly is the best way to destroy a system .. or loose 1-2 hr to put back a backup..

 

Of course you can, and I do on all PCs that pass through my hands and my remote hands :

Code:

bcdedit /set {current} hypervisorlaunchtype off
reg add HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard /v EnableVirtualizationBasedSecurity /t reg_dword /d 0 /f
reg add HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity /v Enabled /t reg_dword /d 0 /f

For some PCs (like HP ProBook) , BIOS UEFI override/enforce VBS , so entering BIOS UEFI to disable it is required.

 

and on some Asus based systems with AMD cpus (both laptops and desktop motherboards), VBS in the BIOS/UEFI is listed as "Secure Virtual Machine" or SVM. turning off SVM mode in bios/uefi disables VBS completely

 

edit: Wrong.
SVM is the hardware virtualization at AMD called VMX at Intel.
Required for virtualization.

 

I did all the below tweaks and it still show Virtualization Based Security is Enabled on my Windows 11 24H2

Spoiler: Disable Virtualization Based Security

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard]
"EnableVirtualizationBasedSecurity"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\CredentialGuard]
"Enabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity]
"Enabled"=dword:00000000
"ChangedInBootCycle"=hex(b):40,76,a1,c4,e6,10,db,01

Spoiler: Disable Windows Defender Credential Guard

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeviceGuard]
"LsaCfgFlags"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"LsaCfgFlags"=dword:00000000

Spoiler: Disable Virtualization Based Security from Group Policy

1. Run gpedit. msc.
2. Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard.
3. Double click Turn on Virtualization Based Security.
4. Select Disabled.
5. Click OK.
6. A reboot might be required.

I also went in BIOS on my Alienware m16 laptop and set secure boot to off and disabled TPM based security but no luck

 

To disable VBS in 24H2, all you had to do was disable Windows Hello in Device Guard in the registry in this way:

• On the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\WindowsHello path, you need to change the value of the DWORD parameter "Enabled" to 0
• After restarting your PC, VBS should be turned off
• At the same time, oddly enough, the ability to log in to an account via Windows Hello (in particular, using a PIN code) still remains

 

I did that and also disabled Windows hello via Group Policy, still didn't work

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Suggest to reduce telemetry switch from pro to education sku

Use massgrave hwid