A successful first run is not merely four windows opening at once. It is a verified chain in which DKPanel checks the machine, imports data safely, selects a suitable group and exposes the state of every slot.
DKPanel runs locally on Windows x64. Account passwords and Steam Guard data are not uploaded to the web dashboard: the website handles subscriptions and licensing while game account data stays on your computer.
What to prepare before setup
Start with the environment rather than the launch button. Steam and CS2 must be installed, while ordinary Steam and CS2 processes must be closed. Built-in preflight separately checks Windows x64, application paths, the native helper, Windows protection and available memory.
24 GiB or more passes as PASS. Between 12 and 24 GiB produces a warning. Below 12 GiB blocks multi-instance use. This is a technical readiness check, not a promise of equal performance on every machine.
For the standard automated cycle, prepare at least four accounts with a valid password and shared_secret. The automatic queue uses verified Prime accounts by default. A separate setting can allow non-Prime and unchecked records, but Weekly Care Package is unavailable without Prime.
Check what is already ready
This list does not scan or store anything. It helps you avoid missed steps; DKPanel still performs the final technical preflight.
DKPanel launches local clients; it does not replace the game installation.
The first run, in order
- 01
Download DKPanel from your account
One subscription activates on one machine. Do not move the installation or local database to bypass binding; manage machines through the account dashboard.
- 02
Import accounts through the preview
Open Accounts, select Import, choose the credentials file and maFile folder. Review matches and issues before confirming. Account import guide →
- 03
Refresh profiles and verify Prime
The profile action refreshes Profile Level, XP and Wingman statistics; the bulk action checks Prime and Weekly Care Package. A network failure remains an error instead of becoming a false all-clear status.
- 04
Review maps and the combat cycle
At least one map must be enabled under Combat cycle settings. DKPanel requires a consistent set of round variations for every selected map; an unsafe configuration blocks the run until corrected.
- 05
Run preflight with Check
Resolve every FAIL row. The administrator warning does not always block a run, but scoped process-mutex access can require elevation. For 2–4 windows, acknowledge experimental multi-instance use in settings.
- 06
Keep Auto selected and start the automated cycle
Do not manually select four accounts when you want normal rotation. DKPanel builds the queue, selects a close group and replaces completed slots after a verified level-up.
Normal states during launch
Each slot moves in sequence: queued, profile preparation, Steam launch, authentication, CS2 launch and running. Four windows do not start as one uncontrolled burst; the delay helps bind every Steam and CS2 process to the correct account.
If Action required or Launch error appears, do not manually start a second client over the existing one. Open the journal, find the safe event code and address that cause. Stop automation ends the long-running loop, while Close all instances separately closes the managed process trees.
What DKPanel cannot guarantee
- Steam does not officially document or guarantee several simultaneous local clients.
- Automation can conflict with Steam rules and cannot eliminate account restrictions.
- The 190–210 weekly range comes from observed runs; up to 280 is an upper estimate, not a promise.
- Steam, CS2, network failures or incomplete reward data can stop the safe workflow and require review.