Help
DragIn1 Support
Installing, troubleshooting, shortcuts, and how to reach a human when none of it helps.
Installing
- Download
DragIn1-Setup.exefrom GitHub Releases. One file, no admin rights, installs just for you. - Run it. When SmartScreen appears, click More info then Run anyway.
- DragIn1 opens as a small always on top window in the bottom right of your screen. That window is the shelf.
Windows 10 and 11. Needs .NET Framework 4.x, which is already present on every Windows 10 and 11 machine, so there is nothing else to install.
Using it
Troubleshooting
Windows says “Windows protected your PC”
Click More info, then Run anyway. This is SmartScreen reacting to software that has not built up reputation, not a detection of anything in the file.
It reappears on every new release, because SmartScreen ties reputation to a specific file hash and each release is a new file.
What SmartScreen actually checks→I dropped an attachment on DragIn1 and nothing appeared
Give it a second. On a slow connection the source may still be downloading the attachment, and DragIn1 waits for it rather than failing early.
If it still does not appear, the source app may be one we have not seen yet. Report it with the app name and build number and we will take a look.
The DragIn1 window keeps disappearing behind other windows
Right-click the DragIn1 window and turn on Always on top. It is on by default, but it can be switched off by accident.
A destination still rejects the file after I drag it out of DragIn1
This one is worth reporting. Once a file leaves DragIn1 it is an ordinary Windows file drag, so a destination that refuses it is unusual and probably a bug on our side.
Include the destination app or website and what happened when you dropped.
Where did my captured files go?
Everything DragIn1 captures is written to %LOCALAPPDATA%\DragIn1\ on your own machine, and cleaned up automatically after seven days.
Right-click an item and choose Show in folder to open its location.
Can I use it on a managed work computer?
Usually yes. The installer is per-user and needs no administrator rights, and it installs no services, drivers, shell extensions or scheduled tasks.
If your organisation blocks unsigned executables, the code signing policy and the public build workflow are the documents your IT team will want.
Code signing policy→My antivirus flagged it
Verify the SHA256 against the release first. If it does not match, do not run it and please open an issue immediately.
If it matches, it is a false positive on an unsigned binary. You can also build from source yourself in about two seconds and skip our binary entirely.
Multi-file drags, huge attachments, or unusual filenames
These are the cases most likely to have rough edges, and they are the most useful bug reports we get. If something misbehaves, tell us what the drag contained.
Verifying your download
Every release publishes a SHA256 computed by the same public workflow that built the binary. To check what you downloaded:
Get-FileHash DragIn1-Setup.exe -Algorithm SHA256Compare the result with SHA256.txt on the release. If it does not match, do not run the file, and please open an issue so we can look into it.
Uninstalling
Settings → Apps → Installed apps → DragIn1 → Uninstall.
It asks whether to keep the files it captured. Nothing is left behind either way: no services, no drivers, no shell extensions, no scheduled tasks.
Still stuck?
Bug reports are genuinely welcome, especially for a source app whose drags are not captured, a destination that rejects a drag out of DragIn1, or anything involving multi-file drags, very large attachments, or unusual filenames.
Helpful things to include
- Which app you dragged from, and its version or build number
- Where you were trying to drop it
- Whether anything appeared in the DragIn1 window at all
- Your Windows version (10 or 11)