R6 Lite
Prepare R6 Lite, follow the launch sequence, and find the fix for your loader error.
1. Check your system
- Use a standard Windows 10/11 Home or Pro installation. The documented builds are 1909–25H2 with at least 16 GB RAM.
- Enable hardware virtualization in firmware: Intel VT-x or AMD SVM/AMD-V. Check the product’s graphics requirements before changing integrated GPU settings.
- Review Anti-Virus Setup and the error-specific instructions before making security changes. Save your work: first-time setup can restart Windows.
2. Prepare your overlay
- Open either Medal or Discord as administrator and keep its game overlay enabled.
- Keep focus on the monitor where you want the overlay to appear while starting the loader.
3. Open and activate the loader
- Use the R6 Lite loader from Downloads. Extract it locally, then open it.
- Paste your license key into the loader using the right mouse button, then press Enter.
- Follow its prompts. The first setup may restart the PC; reopen the loader afterward. If using the loader’s optional hardware tools, open Ubisoft Connect or Epic Games Launcher first.
4. Launch Rainbow Six Siege
- Wait until the loader finishes and its command window closes before starting the game. Do not close it while it downloads or loads.
- Reach the game’s main menu and allow up to three minutes for initialization. Press Insert to toggle the menu.
- The supplier’s setup is intended for the main menu rather than the shooting range. If the menu or ESP does not appear, check the R6-specific error entry below.
Troubleshooting
R6 error codes: 21076, 25234, 17685, 37713, 48525, 91341
Open Windows + R and enter %localappdata%/Ubisoft/r6s. The supplier needs the current RainbowSix.exe / QB build to investigate these codes. Contact Bear support for the upload instructions and include your error code.
R6 ESP does not work / menu does not appear
Wait for initialization in the main menu. If it still fails, contact support with your current game build. The supplier requests the RainbowSix.exe / QB file found under %localappdata%/Ubisoft/r6s for build-specific diagnosis.
Failed to initialize spoofer
The loader offers more than one HWID Virtualizer option. The supplier recommends trying the alternate option for this particular initialization error.
Low FPS with Medal
In Medal, open Clip Settings and switch off Capture Clips. Check game performance again with the overlay running.
Overlay / ESP off-center
Move the Windows taskbar back to the bottom of the screen, then press the overlay key once to refresh its position.
Loader is empty / does not load
Check antivirus and other anti-cheat logs for a blocked component. Vanguard and FACEIT are documented conflicts. Resolve the identified conflict and retry after restarting.
Failed to repair Hyper-V files automatically
This can occur on custom or optimized Windows builds whose hypervisor files differ from standard Windows. Confirm that you are using an official Windows installation and ask support to inspect the repair failure.
Manually disable Hyper-V using DG Readiness
- The supplier uses Microsoft’s Device Guard and Credential Guard readiness tool for this error. Disabling those features changes Windows security; confirm this is the required fix for your system first.
- Download the Microsoft tool below and extract it. Open PowerShell as administrator in the extracted folder.
- For that PowerShell session, the documented commands are Set-ExecutionPolicy Unrestricted -Scope Process, followed by .\DG_Readiness_Tool_v3.6.ps1 -Disable.
- Restart and review the firmware confirmation screen if it appears. Have your account password and recovery key available. Use the PIN recovery guide if sign-in stops working.
Failed to download font-7
Restart Windows and retry. If the download remains blocked, test with a VPN and contact support if it still fails.
Loader closes within 1–3 seconds
Install or repair the Microsoft Visual C++ x64 runtime linked below, even if it is already installed, and restart Windows before retrying.
Unknown error while disabling Hyper-V
The supplier provides a separate backup-and-disable repair utility. Request the current approved file from Bear support rather than using a tool for a different product. Extract the complete archive and keep its backup files together.
Failed to set value
Send Bear support the complete message and your Windows version. The supplier does not publish a separate self-service fix for this error.
Loader restarts the PC more than three times
Stop the repeated launch attempts. Review the DG Readiness entry above with support; the supplier directs this restart loop to the same Device Guard / Credential Guard repair.
PIN is set in Windows sign-in options
Check Settings → Accounts → Sign-in options and confirm you have a working account password. Review the PIN recovery guide before changing sign-in settings. The supplier also directs this error to its DG Readiness repair sequence.
Unsupported firmware
The documented boot configuration requires GPT for the Windows disk and compatible UEFI firmware. Check your existing configuration before conversion; ask support to plan the change with a backup.
CRITICAL_PROCESS_DIED / BSOD while loading
Allow the loader to finish downloading and loading. Closing it midway is the documented trigger. If a crash happens without closing it, keep the stop code and contact support.
Mapper error
Check that your Windows version is supported and is an official build. The supplier recommends changing to a supported build when a specific build fails; confirm the required version with support before reinstalling.
Failed to download files (1)
Retry the download and install pending Windows updates if the failure continues.
No available servers were found
Check Bear’s status page and Discord announcements for maintenance. If there is no outage, retry the network connection or test a VPN.
Virtual disk / RAID disk is present
The supplier lists RAID, virtual disks and Intel RST drivers as incompatible. Check your storage configuration and any iaStor services. Changing controller modes can stop Windows from booting; get a migration plan from support before changing them.
Failed to map memory
- Confirm at least 16 GB RAM and keep the extracted loader on a local disk rather than OneDrive or another cloud folder.
- Disable unnecessary third-party Startup apps in Task Manager and restart. Try the loader soon after Windows starts.
- Use Microsoft Autoruns to inspect leftover startup entries. Ask support before changing unfamiliar entries or drivers.
Incorrect HWID
Contact support with your hardware configuration and recent system changes. The supplier checks disk, motherboard and network identifiers. A missing WMIC command on newer Windows is not, by itself, proof that Windows needs reinstalling.
Failed to spoof hardware identifier (0x4)
Restart and retry once. The supplier identifies another active hardware-identifier tool as a possible conflict; close the conflicting tool before another attempt.
Failed to load dependencies (1)(-5)
The supplier calls for a product-specific registry fix but the published page does not provide the file. Request the current repair file from Bear support and include this exact code.
Incompatible HWID / HWID mismatch
Restart Windows and retry. If the binding still fails, contact Bear support to request a hardware reset.
Failed to load dependencies
Check for blocked dependencies and conflicting antivirus or FACEIT/Vanguard drivers. Restart after resolving the identified conflict.
Enable AMD-V / SVM
Enable SVM / AMD-V in your motherboard’s firmware, save the change and restart. The exact menu name depends on the motherboard.
Enable Intel VT-x
Enable Intel Virtualization Technology / VT-x in firmware, save and restart.
VT-x / VMX / SVM is not supported
Confirm firmware virtualization is enabled first. The supplier has an additional PowerShell repair for this error; ask support to validate the current script for your Windows build before applying it.
Error 0x302
Restart Windows and retry the loading sequence.
SPACES disk is present
The supplier flags Microsoft Storage Spaces as incompatible. Inspect Control Panel → Storage Spaces. Removing a pool can erase its data; back it up and contact support before changing the storage layout.
Intel Rapid Storage Technology detected
Check whether RAID/RST is enabled and whether iaStor drivers remain installed. Follow a supported RAID-to-AHCI migration procedure with support; switching the firmware setting alone can prevent Windows from starting.
Intermittent black screen
Install current Windows updates. The supplier’s specific black-screen article is for Delta Force/ABI; for a repeating Siege issue, provide support with your display and overlay configuration.
Failed to delete hvax.exe (1)
This involves Windows hypervisor files. Contact support with your Windows build and virtualization settings before altering system files.
Failed to initialize render
Check that the game uses a supported dedicated graphics adapter and that the required overlay is configured. The supplier lists integrated graphics as a possible conflict; verify your display routing before changing firmware graphics settings.
Unload a third-party hypervisor
Restart first. If it persists, check for virtual-machine or other hypervisor software and ask support which conflicting component must be stopped or removed.
Enable AHCI disk mode
The supplier requires AHCI instead of IDE/RAID for this configuration. Check the current controller mode and obtain a migration plan before changing it on an existing Windows installation.
AES instruction set is not supported
Check whether your processor supports AES and whether firmware exposes an AES setting. A processor without AES support cannot gain it through a loader reinstall.
