Narcan HWID Spoofer TEMP

Preparation

Before running the software, make sure your PC is configured correctly. Certain Windows features, virtualization settings, security software, and background applications can interfere with normal operation.

Important: Only change system security settings when you understand the consequences. Avoid disabling Windows security protections unless absolutely necessary.

Initial Setup

This guide covers the recommended BIOS and Windows settings to ensure the software operates correctly.

BIOS / UEFI Settings

Virtualization

Enable hardware virtualization in your BIOS/UEFI:

Intel: Enable VT-x / VT-d

AMD: Enable SVM

Windows Settings

Check Windows Features and make sure unnecessary virtualization components are not interfering with the software.

Common components include:

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Sandbox
• WSL 2

Restart your PC after making changes.

Known Issues & Fixes

Below are some of the most common issues users may encounter.

Issue 1: “Took more than 60s to allocate workspace.”

Fix: Restart your PC and try again.

A reboot will usually clear the issue.

Issue 2: “No Hardware Virtualization Capabilities Found.”

Fix: Enable virtualization in your BIOS/UEFI.

Intel CPUs: Enable VT-x / VT-d

AMD CPUs: Enable SVM

Save your BIOS changes and restart your PC.

Issue 3: “GPU Driver Requires an Update.”

Fix: Update your NVIDIA/AMD graphics driver to the latest available version from the manufacturer's official software.

Restart your PC after updating if necessary.

Issue 4: “Hyper-V is enabled.”

Hyper-V and related virtualization features can sometimes conflict with software that requires direct access to virtualization features.

Recommended Fix

Open Windows Features and review the following components:

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Sandbox
• WSL 2

If you do not need these features, disable the relevant ones and restart your PC.

Issue 5: “Failed to get permissions.”

Possible Cause

Another application may be preventing access. Common causes include:

• Antivirus software
• Windows Security
• Other security software
• Anti-cheat software
• Background system utilities

Fix

Close unnecessary background applications and restart your PC.

If the problem continues, contact support with the exact error message and your system specifications.

⚠️ Avoid permanently disabling security software simply to resolve an error.

Issue 6: “A VPN or network filter driver is active.”

VPNs, DNS applications, and network-filtering software can install background drivers that interfere with certain applications.

Fix

Temporarily close or disable unnecessary VPN, DNS, and network-filtering applications, then restart your PC.

Examples include:

• VPN clients
• Network monitoring software
• DNS filtering applications
• Network optimization utilities

If the issue persists after everything is closed, contact support.

Issue 7: “Something went wrong. Restarting PC.”

Fix: Restart your computer and try again.

The software may require a fresh system session before running correctly.

Issue 8: “There was an error loading the Hyper-V.”

Fix:

1. Restart your computer.
2. Try running the software again.
3. If the problem occurs repeatedly, contact support.

Issue 9: “Stuck at 11%”

This can indicate that the application is unable to access or modify required system resources.

Recommended Fix

1. Restart your PC.
2. Close unnecessary background applications.
3. Check that your storage drives are functioning normally.
4. Make sure Windows is fully updated.
5. Try running the application again.

If the issue continues, provide support with a screenshot of the error and your system specifications.

Issue 10: Permanent BSOD

Permanent BSOD

If your PC consistently crashes with a blue screen even after multiple restarts, the issue may be related to incompatible hardware, drivers, or system configuration.

Recommended action: Stop running the software and contact support. Provide the BSOD error code if available.

Occasional BSOD

If a blue screen occurs only once under unusual circumstances, restart your PC and check whether the problem returns.

Repeated crashes should always be investigated rather than repeatedly ignored, because computers apparently enjoy making their problems everyone else's problem.

Hyper-V Troubleshooting

Hyper-V Appears to Be Running

Hyper-V may appear disabled while other Windows virtualization components are still active.

Understanding the Problem

Windows virtualization can remain active through related components such as:

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Sandbox
• WSL 2
• Core Isolation / Memory Integrity
• Device Guard
• Credential Guard

If virtualization-based security or another hypervisor is active, software that requires a different virtualization environment may not operate correctly.

Solution 1: Review Windows Virtualization Features

Open Turn Windows features on or off and review the following:

• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform
• Windows Sandbox
• WSL 2

Disable features you do not use, then restart your computer.

Solution 2: Check for Background Virtualization Services

Even when Hyper-V appears disabled, other Windows security or virtualization features may still be active.

Check:

Core Isolation / Memory Integrity

1. Open Windows Security
2. Select Device Security
3. Open Core isolation details
4. Review Memory integrity

Only change this setting if you understand the security implications.

Windows Security Features

Also check whether your system uses:

• Device Guard
• Credential Guard
• Windows Sandbox
• WSL 2
• Virtual Machine Platform

Restart your PC after making configuration changes.

Solution 3: Verify Your Configuration

If you continue receiving Hyper-V-related errors, verify your Windows configuration and check whether another virtualization component is active.

You can use Windows' built-in system information tools to review your current hypervisor and virtualization configuration.

If the problem remains after a restart and configuration check, open a support ticket and include:

• The exact error message
• Your CPU model
• Your GPU model
• Windows version
• A screenshot of the error
• Whether virtualization is enabled in BIOS/UEFI

This gives support enough information to diagnose the issue without having everyone play detective with a broken Windows install.