hack.sale
RU EN

Arcane and Ancient: PIN and Hyper-V errors

Inspect Windows Hello and hypervisor startup using supported Windows controls. Requirements depend on the product; deleting system files is unnecessary.

One guide covers every cheat from this brand — the steps are identical.

Identify the required configuration first

  1. Please make sure PIN is not set in Windows sign-in options and manually disable Hyper-V using dgreadiness tool concerns sign-in and virtualization checks.
  2. Do not disable Hyper-V for every product: some Ancient builds, including Rust, require it enabled. Match the game, CPU and current guide.
  3. Confirm an alternative sign-in password and preserve the BitLocker recovery key before changes. For an organization-managed PC, consult its administrator.

Windows Hello settings

  1. Use Win + I → Accounts → Sign-in options and locate PIN (Windows Hello). If your product requires it disabled, use the supported removal control.
  2. If removal is unavailable, check the Windows Hello-only sign-in setting and management policies. Do not manually delete credential folders.
  3. Restart and confirm you can sign in using the alternative method. Microsoft reference: https://support.microsoft.com/en-us/accounts-billing/security/sign-in-options-in-windows

Hyper-V without deleting files

  1. If your build requires the hypervisor disabled, inspect Hyper-V and Virtual Machine Platform in Windows Features. WSL, virtual machines and security features may depend on them.
  2. To disable hypervisor startup, use bcdedit /set hypervisorlaunchtype off in an administrator terminal, then restart. Restore automatic startup with bcdedit /set hypervisorlaunchtype auto.
  3. BIOS SVM/VT-x and the Windows hypervisor are different settings. Retain the hardware virtualization required by the product instead of disabling it indefinitely.
  4. Microsoft on Hyper-V conflicts: https://learn.microsoft.com/en-us/troubleshoot/windows-client/application-management/virtualization-apps-not-work-with-hyper-v. BCDEdit parameters: https://learn.microsoft.com/en-us/windows-hardware/drivers/devtest/bcdedit--set

If the message remains

  1. Do not take ownership of or delete C:\Windows\System32\hvix64.exe or hvax64.exe. They are system files; removing them is not a supported Hyper-V configuration method.
  2. Provide support the error screenshot, Windows build, product, processor and restart results after supported changes.
  3. Main procedures: https://hack.sale/en/instructions/arcane-instructions/ and https://hack.sale/en/instructions/ancient-instructions/

Applies to

← All guides