Guide

How to Use DenuvOwO Hypervisor Releases

Follow the steps below carefully before using a DenuvOwO Hypervisor release. Always revert the changes after use and return to normal secure mode.

These instructions may temporarily change Windows security-related settings. Only run files you trust, understand what is being changed, and revert the changes after use.

  1. Step 1Enable virtualization

    Make sure virtualization is enabled in your BIOS: VT-x for Intel or AMD-V / SVM for AMD.

  2. Step 2Run VBS.cmd

    Run VBS.cmd in the game folder.

  3. Step 3Apply system changes

    Press 1 to make the necessary changes to the system.

  4. Step 4Reboot your PC

    Reboot the computer.

  5. Step 5Disable DSE

    In the loading menu, press F7 to disable DSE.

  6. Step 6Run the game as admin

    Run the game .exe file as administrator.

  7. Step 7Play

    Start the game and play normally.

  8. Step 8Run VBS.cmd again

    After playing, run VBS.cmd again.

  9. Step 9Revert changes

    Press 3 to revert the changes that were made.

  10. Step 10Reboot normally

    Reboot normally back into secure mode.

Always revert the changes after use and return to normal secure mode.

FAQ

Setup questions

+Why do I need to enable virtualization?

DenuvOwO Hypervisor releases rely on CPU virtualization extensions to initialize. Without them enabled in the BIOS, the release cannot run.

+What are VT-x and AMD-V / SVM?

VT-x is Intel's CPU virtualization extension. AMD-V (sometimes labelled SVM) is the AMD equivalent. Both are toggled in the BIOS/UEFI setup.

+Why do I need to revert changes after use?

The setup temporarily changes Windows security-related settings. Reverting restores your system to normal secure mode once you are done playing.

+What should I do before running VBS.cmd?

Extract the release into the game folder, close the game, and only run VBS.cmd if you trust the source you downloaded it from.

+Should I run the game as administrator?

Yes. After applying the changes and rebooting, the game .exe should be launched as administrator so the release can hook properly.