Solved Script for disabling Virtual Based Security on 24H2

I thought this could be useful for anyone who's having issues disabling VBS with 24H2.

I had issues getting VBS to turn off on my laptop after installing 24H2 but after some trial and error I've created a batch script to easily disable VBS and Device Guard.

Hopefully it will help anyone having the same issue.

For clarity, your script disables Virtualization-Based Security and not VBS Script.

Some of the Elevenforum members might be confused, since you're posting in General Support forum and not under Virtualization and WSL forum.

@garlin

Sorry for any confusion wasn't sure where the best place to post was.

For anyone curious I followed the information on Microsofts website to make this script.

Heres the link to the page i used

Thank you for updating the thread's title. Just as a reminder, a reboot is required after running the script.

Thank you for posting your script. I'm just getting started using 24H2 and your script was a big help. I let Windows update and when the computer restarted I received two error messages, StartAllBack wouldn't run and my NVIDA display driver stopped working. The basic driver would only recognize my 1st monitor. I tried removing the two updates that Windows would allow me too. After the restart I still had the same problems. When I went to Use Macrium to do a restore, App Control wouldn't let it run even though I had App Control turned off. I ran your script, restarted my computer and everything seem to be working as it should. I'm thinking that the update changed some settings in App Control that caused my problems. I'm thinking about turning Updates back on and see what happens.

@Winuser

I'm glad it helped.

I don't know much about app control since I've never used it. I'm guessing it's reliant on device guard which the script disables so that's probably why it worked.

Hopefully Microsoft will add a toggle in defender to turn this stuff off without having to rely on scripts.

andrewtjb said:

@Winuser

I'm glad it helped.

I don't know much about app control since I've never used it. I'm guessing it's reliant on device guard which the script disables so that's probably why it worked.

Hopefully Microsoft will add a toggle in defender to turn this stuff off without having to rely on scripts.

Click to expand...

I tried running Windows Update to reinstall the two updates and it happened again. I ran your script again and as far as I can tell everything is working again.