A pair of scripts that fix the "view-only / no click or input" problem on DWService remote sessions, and open a full-control session in a single double-click.
No installer. No external dependencies. No data leaves your machine apart from the standard DWService API calls.
This repo has two halves. You only need to read the README in the half you're using.
| Folder | For which computer? | What it does | Read this |
|---|---|---|---|
Main/ |
The PC you control from (the controller) | launcher that creates a full-control session and opens it in your browser | Main/README.md |
Target/ |
The PC you control to (the remote) | repair that fixes "view-only" at the system level | Target/README.md |
- Go to the remote PC.
- Copy
Target/DWService_FullControl_Fix.batonto its Desktop. - Double-click it. Approve the UAC prompt. Wait. Done.
- Try the session again from the controller PC.
Full details: Target/README.md
- On the controller PC, open the
Main/folder. - Double-click
ForceFullControl_Launcher.bat. - Paste your DWService API key, then API secret (hidden input). Done — browser opens.
Full details: Main/README.md
The repair script self-elevates through UAC, then runs a fully automatic
sequence: it locates the DWAgent install path, backs up the agent database
and config, fixes the service configuration and failure-actions, adds
firewall allow-rules for both agent executables, adds Windows Defender
folder + process exclusions, flushes DNS, and — if sqlite3.exe is
present — schema-checks the permission database and updates any
view/readonly/limited rows to full. Then it briefly disables
Defender real-time monitoring and stops any known third-party security
suite (13 vendors covered), restarts DWAgent so it can re-register its
input hooks, waits 15 seconds, and re-enables every protection it
turned off. Every action is timestamped to a log file on your Desktop;
secrets and device IDs are masked.
If a kernel-mode EDR refuses to back off, the log tells you so and points to Safe Mode + re-run as the guaranteed manual fallback.
| Component | Where | Requirement |
|---|---|---|
| Windows | Both | Windows 10 or Windows 11 |
| PowerShell | Both | 5.1 (ships with Windows) or newer |
| Admin rights | Target | Yes — the script self-elevates through UAC |
| Admin rights | Main | No |
| DWService account | Main | Yes — with an API key (Settings → API Keys on the DWService site) |
| DWService Agent | Target | Yes — installed and registered to your account |
sqlite3.exe |
Target | Optional. Drop next to the BAT to enable the database-permission repair step |
DWService/
├─ README.md ← you are here
├─ Main/ ← controller-side
│ ├─ README.md
│ ├─ ForceFullControl_Launcher.bat ← double-click this
│ └─ ForceFullControl.ps1 ← the actual script
└─ Target/ ← target-side
├─ README.md
└─ DWService_FullControl_Fix.bat ← double-click this on the remote PC
For specific problems, see the README in the relevant folder:
- Controller-side issues (PowerShell policy, API errors, no agents found): Main/README.md
- Target-side issues (UAC, DWAgent not found, still view-only after fix): Target/README.md