VMware Workstation

 View Only
  • 1.  Windows Host Increased Memory Usage - VBS Redux

    Posted Nov 26, 2024 08:48 AM

    The latest Windows 11 24h2 (and prior with updates?) have introduced a new security model in the kernel.    That security model relies on HyperV and incurs a performance hit in CPU and memory.   On my system I lose 2GB of memory to the 'Secure System' process.    I've been trying to disable and/or remove it.   Have had no success.   And now you can see posts from Microsoft how this is affecting gaming and other software.    No matter what I do MSINFO32 reports VBS running (unless I disable virtualization in the bios).   Hopefully MS will sort this out and come out with a better solution.



  • 2.  RE: Windows Host Increased Memory Usage - VBS Redux

    Posted Nov 27, 2024 10:08 AM

    > The latest Windows 11 24h2 (and prior with updates?) ...

    For what it's worth, I don't have Windows 11 24H2, but did go through disabling VBS just this week on a new 23H2 system.

    I used the 'System Information' utility to see what VBS things were active. (In my case 'Hyper-V' was not listed as installed as a windows component).

    Everyone may have different things being the 'last holdout', but I went through the listed set of 'active'/running Virtual cased things and got rid of them one by one until all that was left running was 'VBS'.

    In my case I ended up having to 

      *) Turn off Core-isolation

      *) Use Group Policy editor to set the 'Turn on Virtual Based Security' policy

          to 'disabled'. (This supposedly also turns off Credential Guard').

    After deactivating all the individual things I could find, I finally went to an admin. command prompt and did the

       "bcdedit /set hypervisorlaunchtype off'

    thing and rebooted. That did the trick in my case. 

    But as a caveat that transition caused all the things in Windows Hello to be 'lost'. (Maybe because the secrets were part of the VBS stuff?).

    I don't know if that helps you or not.

    At any rate, I'm now hoping the eventual update to 24H2 won't break things for me again..