1. What Is This?
D2R Multi is a multi-boxing / multi-account manager for Diablo II: Resurrected on Windows. It solves three problems:
- Multi-instance: Run multiple D2R clients simultaneously on one PC.
- One-click account switching: Switch between multiple Battle.net accounts without re-logging.
- Truly password-free: Log in once per account, then launch directly into the game.
One-sentence principle: Each game account = an independent Windows local user. The tool swaps Battle.net’s
product.dbsnapshot, cleans D2R’s instance lock, then launches Battle.net as the target user.
2. Prerequisites
| Requirement | Details |
|---|---|
| OS | Windows 10 / 11 (64-bit) |
| Privileges | Must run as Administrator |
| Battle.net Path | C:\Program Files (x86)\Battle.net — fixed, no custom drives |
| Battle.net Install Scope | Must check “Install for all users of this computer” |
| D2R Game Path | Flexible, can be on any drive |
| Account Type | Local Windows accounts only (no Microsoft accounts, no domain accounts) |
[!WARNING] If you previously installed Battle.net on another drive, you must uninstall and reinstall to the default path with “Install for all users of this computer” checked. This is a hard requirement for the cross-user permission mechanism.
Getting the Tool
Go to the D2R Multi Dedicated Download Page to get the latest version:
- Setup (Recommended): NSIS installer with auto-update support.
- Portable: Extract and run, config alongside the executable.
3. First Launch
3.1 Run as Administrator
Right-click d2r-rust.exe → “Run as administrator”. Optionally, check “Run this program as an administrator” in Properties → Compatibility for permanent elevation.
3.2 Initialization Wizard
On first launch (no config detected), the wizard offers:
- New Config: Start fresh, write config to default data directory.
- Load Existing Config: Point to a folder containing
config.json(portable/migration).
3.3 Data Directory
Config, snapshots, and logs are stored in the “data directory”. View/change it under Settings → Data Management. Log file: data_dir\logs\d2r-multiplay.log.
4. How It Works: Core Concepts
4.1 One Account = One Windows User
Battle.net stores login state, config, and cache per-user under %AppData%. By binding each game account to a separate Windows user, multiple Battle.net accounts can stay online simultaneously without cross-contamination.
The tool launches Battle.net as the target user via CreateProcessWithLogonW, making login states naturally persistent.
4.2 product.db Snapshot Rotation
Battle.net’s Agent.exe is a machine-wide singleton that reads C:\ProgramData\Battle.net\Agent\product.db in real time to determine “which install/path to use.”
The launch sequence:
Backup current snapshot → Kill Battle.net + Agent → Inject target account’s product.db → Launch Battle.net as target user
When Agent restarts, it reads the target account’s path configuration, preventing cross-contamination.
4.3 D2R Instance Lock
D2R creates a named kernel object DiabloII Check For Other Instances to block second instances. It is an Event object, not a Mutex. The tool closes this lock before launching a new instance — this is what “Clean Mutex Locks” actually does.
4.4 “Double-Online” and Snapshot Saving
“Double-online” = a user’s Battle.net + D2R are both running simultaneously — the only moment when product.db is guaranteed to match the running D2R. The tool auto-saves snapshots only at this moment.
[!IMPORTANT] The last-launched account needs manual snapshot saving. Auto-backup happens on the next launch, so the final account has no “next time” to trigger it. After finishing, click “Save Snapshot” on that account. When using sequences, click the green “Finish & Back Up” button after all accounts are launched.
5. Creating Windows Ghost Users
You can create local Windows users directly within the tool, or via system tools:
- Open
lusrmgr.msc(Local Users and Groups) - Or use the tool’s built-in Toolbox → Local Users and Groups entry
[!TIP] Newly created users must log in once to complete Windows initialization (desktop files, etc.), then switch back. This is a mandatory Windows process — the tool cannot bypass it.
6. Adding and Managing Accounts
6.1 Account Manager
The “Account Manager” page lists all accounts in a table: avatar, Windows user, Battle.net ID, game path, notes.
Click “Add Account” to open the editor:
| Field | Description |
|---|---|
| User Binding | Select existing Windows user or create a new one |
| Password | Target user’s Windows password (required for cross-user launch) |
| Avatar | 7 class icons: Amazon / Sorceress / Necromancer / Paladin / Barbarian / Druid / Assassin |
| Notes & Battle.net ID | For identification (e.g. “Main·Sorc”, “Mule”), also used for window titles |
| Game Path | Usually auto-captured, can be manually set |
6.2 First-Time Setup Flow
- Under your main account, manually log in to each Battle.net account (and launch D2R once) so each ghost user’s
%AppData%gets Battle.net config. - Switch back to your main account, add account entries in the tool for each ghost user.
- Manually save a snapshot: Switch to the account, launch once, wait for Battle.net to appear, then click “Save Snapshot”.
- One-click launch works from then on.
7. Dashboard and Launching
Two view modes:
- Card View: Visual grid, best for a few accounts.
- List View: Dense table, best for 10+ accounts.
Status indicators:
- Blue = Battle.net online for this account.
- Green = D2R online for this account.
Launch modes:
| Button | Behavior |
|---|---|
| Launch Game | Switch identity and launch D2R directly |
| BNet Only | Switch environment and open Battle.net (for manual login/region/update) |
| Force Launch (amber) | Shown when conflicts detected, kills processes first |
7.1 Soft Launch Pacing
To prevent launching a second account before the first one’s Battle.net has started (which would cause conflicts), the tool has built-in soft pacing. Wait a few seconds, or use “Force Launch” to bypass.
8. Sequence Auto-Launch
For launching multiple accounts in batch, use Sequence Presets:
- Create sequences in Settings (P1, P2, P3 slots).
- Add accounts to a sequence, drag to reorder.
- Click “Start Sequence” to launch all accounts in order.
After completion, a sequencer mini-window floats on top. Click the green “Finish & Back Up” to save the last account’s snapshot.
9. Toolbox
| Tool | Purpose |
|---|---|
| Process/Handle Explorer | Inspect and close individual handles |
| Clean Mutex Locks | Manually close D2R instance lock |
| Clean Archives | Clear Battle.net cache (fix update loops) |
| Stop Processes | Kill residual Battle.net processes |
| Fix Folder Permissions | Grant Users group full control via icacls |
| Directory Mirror (Junction) | Create isolated directory junctions for multi-client |
| System Reset | One-click kill processes + clear config/cache |
| Diagnostics | User permission checks, path permission checks |
10. Common Issues
Mirror “stuck updating”?
Usually a permissions issue. Use the toolbox “Fix Folder Permissions” feature, or manually add Users group full control to the mirror directory.
Battle.net directory not found?
Battle.net must be installed at C:\Program Files (x86)\Battle.net with “Install for all users” checked. Game files can be anywhere.
“Not initialized” error after setup?
Newly created Windows users must log in once for initialization. Switch to the ghost user’s desktop, wait for the “Welcome” screen to finish, then switch back.
Browser redirect not responding / redirect back to BNet stuck?
Switch to the ghost user’s desktop, set the browser as default, and check “Always allow” when confirming the Battle.net protocol callback.
11. Disclaimer
- Must run as Administrator, otherwise system handles cannot be cleaned.
- Handle operations may trigger AV software; add to whitelist if needed.
- This tool is for technical exchange only. Any consequences (bans, losses) are the user’s responsibility. This project is not affiliated with Blizzard Entertainment.