One portable file.
Dusk is a single exe with no installer, no account and no licence key. It updates itself in place, which is the one thing that decides where you should put it: somewhere you can write to.
Dusk 1.0.0 for Windows
Read from the live update channel. Windows 10 or 11, x64
Download Dusk.exe- Version1.0.0
- Size~5.2 MB
- SHA-256 Published with each release
- Needs.NET 10 Desktop Runtime · Edge WebView2 Runtime
- GameMinecraft 1.8.9, any client (Lunar, Forge, Vanilla)
Why does Windows say this is dangerous?
Two separate reasons, and both are worth knowing
Dusk is not code signed. A signing certificate has not been bought, so Windows cannot tell you who published the file. Every unsigned download gets the same treatment regardless of what it does, and on first run you will see Windows protected your PC.
Dusk reads and writes another program's memory. That is how it works, and it is also exactly what antivirus heuristics watch for, so some scanners will flag it on behaviour alone. Detections like that usually come back under a generic name rather than a specific one, because nothing specific was found.
Getting past it
- On the blue Windows dialog, choose More info, then Run anyway.
- Or before you run it: right-click Dusk.exe, open Properties, tick Unblock at the bottom, then OK.
- If your antivirus quarantines the file, restore it and add an exclusion for the one folder you keep Dusk in.
Checking the file yourself
You should not take our word for it, so here is how to check. Compare the hash of what you downloaded against the SHA-256 on the left. In PowerShell:
Get-FileHash .\Dusk.exe -Algorithm SHA256
If those two strings match, the file is byte for byte the one we published. If they do not, delete it and download it again from this page. You can also put it through VirusTotal and read the results yourself.
Where to put it, and what it does on its own.
Keep it writable
Dusk replaces its own exe when it updates, so it needs a folder it can write to. Somewhere under your user folder works. Program Files does not, because Windows will block the swap and the update will fail every time.
Dusk updates itself
On launch Dusk checks a channel for a newer build, verifies the download against a SHA-256 before touching anything, then swaps and relaunches. If the check cannot reach the network it does nothing and says nothing.
Start Minecraft whenever
The menu opens straight away and does not wait for the game. You can set everything up at the title screen, or before Minecraft is even running. The sidebar tells you what it is attached to.
New to Dusk? The whole first run, from this download to your first armed module, is walked through on How it works.
What Dusk does not claim
These are the limits of the tool, stated with the same confidence as everything above. They are not warnings we were forced into.
Not undetectable, and not ban proof
Running outside the game avoids the artifacts a screenshare looks for in your files. It does not make Dusk invisible. A screenshare can still list running processes and open handles. Server-side anticheat judges the packets your client sends, and those look the same whether the input came from your hand or from a program.
The detectability meter exists precisely because this is true. It is described in the code as deliberately conservative and not a promise you will not be caught, and that is the right way to read it.
Hiding from screen capture is a compositor courtesy
The setting asks Windows to leave Dusk's windows out of captures, and that is honoured by OBS display, window and game capture, by Discord, Teams and Zoom, by the Snipping Tool and by print screen.
A phone camera, an HDMI capture card or a mirrored display sees everything. It also says nothing at all to the game or to a server. It describes what it does; it does not protect you from anything.
Bridge is beta
It works and it ships enabled if you turn it on, but it is the one module still being tuned, and it says so in the menu as well as here.
Minecraft 1.8.9 only, and Windows x64 only
This is the version competitive PvP plays on and the one this is built for. There is no support for newer versions, and none is planned. There is no macOS or Linux build.
The exe is not signed
Code signing has not been started, so Windows cannot tell you who published the file and will warn you on first run. Because Dusk reads and writes another program's memory, some antivirus tools will flag it on behaviour as well.
What to do about it, and how to verify the file is the one we published, is above. The hash is there for exactly that reason.