WarDogs
Arc Raiders
PUBG
Bodycam
Mistfall: Hunter
Escape from Tarkov: Arena
PUBG Black Budget
Fortnite
War Tundra
Battlefield 6
Minecraft
Roblox
Russian Fishing 4
Valorant
Oxide Survival - Rust Mobile
Path of Exile 2
Standoff 2
Active Matter
Arma Reforger
Arma 3
Neural Cheat
Dead by Daylight
Foxhole
Delta Force Mobile
Dune Awakening
PUBG Mobile
Squad
Rainbow Six Siege
Unturned
Dota 2
Deadside
The Division 2
GeoGuessr
Enlistod
Stella Sora
Arknights: Endfield
Honkai Star Rail
Blue Archive
Zenless Zone Zero
Neverness to Everness
Meccha Chameleon
Marathon
Sea of Thieves
Path of ExileStealth Rust Full and Lite: launch, hotkeys and error checks
Start with the edition: Full and Lite have distinct instructions
Check the item in your order: Stealth Full and Stealth Lite differ in controls as well as features. A file with Stealth in its name is not necessarily the right loader. Use the current download and sequence for your purchased edition.
If you are still choosing, read our Full versus Lite comparison. This guide covers preparation and troubleshooting. Before activation, confirm when the subscription starts and the device-binding rules.
Windows and CPU: use exact specifications
The listings name Windows 10/11 and Intel/AMD processors with AVX support. Check the CPU model and instruction set against its manufacturer's specifications; do not replace AVX with an assumed AVX2 requirement. Use winver for the exact Windows version and compare it with current instructions.
An unsupported-OS message does not mean every update should be rolled back blindly. First confirm the supported build. Modified lightweight Windows installations may omit components, so the Windows 10 or 11 label alone does not establish compatibility.
UEFI, GPT and Secure Boot: check before changing
Full lists GPT and UEFI, while both editions list Secure Boot Disabled as a requirement. View BIOS mode in msinfo32. These describe product compatibility; they do not make boot-setting changes a harmless formality.
- If your system differs, obtain instructions for the actual motherboard and configuration first. Before changing boot settings or partitioning, back up data and keep the encryption recovery key available if encryption is enabled. Avoid changing several BIOS settings at once from an unrelated video.
First launch and restart
Use the current loader supplied through your order instructions, confirm the edition and enter the key through the prescribed process. If the instructions include boot preparation and an automatic restart, do not interrupt that stage by cutting power. Follow the stated Rust launch sequence afterwards.
Record an error before retrying. Partition recovery, Windows reinstallation and random commands are not first-line fixes. If the issue began after a Rust patch, check product status and the game version separately, including beta-branch participation.
Key, subscription, HWID and connection
For a wrong-key message, first match the game, loader edition and order. For an expired key, check the subscription. Bad HWID requires following the binding-support process, especially after hardware changes; a new Windows account or random spoofer is not a substitute for the seller's reset procedure.
If the product is frozen for an update, check announcements and support; reinstalling Windows will not resolve that state. Record network errors in full and confirm server availability. Current error wording is in the Stealth documentation. Do not post the key in a public chat.
Boot-partition errors, missing DLLs and blue screens
Messages about boot part, GPT, partition size or free space require separate boot-preparation diagnosis. Record the exact message and disk information first. Do not delete partitions or system files based on abbreviated chat advice; the consequences can affect Windows startup.
For missing MSVCP140.dll, check the official Microsoft Visual C++ Redistributable instead of downloading an individual DLL. For a .NET error, confirm the required runtime version. With a blue screen, record the stop code and named driver. Avoid a blanket BIOS reset or removal of all vendor utilities without a specific diagnosis.
How to report a problem
In one message, include Full or Lite, order number, Windows build, CPU, BIOS mode and the failing stage. Attach the error and a screenshot without the key, then list recent game, OS, hardware or setting changes. Explain whether the loader opens and whether the problem appears before or after restart.
Find contact channels and the process in our GameBreaker support guide. For a visual introduction, watch the Full review and Lite review. Check current requirements and terms on the product pages rather than relying on a video's publication date.