Install troubleshooting
Fixes for the most common install and connection problems: blocked downloads, failed sign-in, and wrong-project context.
The fixes below cover the problems people hit most often when getting started. Still stuck? Contact support.
The download is blocked or won’t open
Multilo is digitally signed (publisher INTUTO4U LLC), but a brand-new release has little download history yet, so Windows SmartScreen or antivirus tools sometimes flag it out of caution — not because anything is wrong with the file. If Windows says “Windows cannot access the specified device, path, or file… you may not have the appropriate permissions”, or the installer simply won’t open, work through these steps in order:
- Unblock the file. Right-click the downloaded
Multilo-…-win-x64.exe→ Properties. If you see “This file came from another computer” near the bottom of the General tab, tick Unblock, then Apply → OK, and open it again. - Let it through SmartScreen. If a blue “Windows protected your PC” box appears, click More info → Run anyway.
- Restore it from your antivirus. If the file disappears after downloading or is locked, your antivirus most likely quarantined it. Open Windows Security → Virus & threat protection → Protection history (or your third-party antivirus), find Multilo, and choose Restore / Allow on device. It’s a false positive on a signed app, so it is safe to allow.
- Re-download and run as administrator. A partial download can also fail to open — download again from the official download page, then right-click the installer → Run as administrator.
On a company-managed PC that still blocks it, ask your IT admin to allow the signed installer from INTUTO4U LLC, or contact support.
Sign-in won’t complete
If the one-click multilo:// link doesn’t open the app (common behind corporate firewalls or strict antivirus), use the connection key instead — copy it from multilo.com/connect and paste it into the app. Also check your system clock is correct, since token validation is time-sensitive.
“Already up to date”
If the app reports it’s up to date but you expected a newer build, the update may not have rolled out to your platform yet, or it will apply on the next restart. Confirm your version under Settings → About and compare it against the changelog.
Agent acts on the wrong project
Agents work in the context of the active project. If an agent edits or cites something unexpected, confirm which project and document are open before you run it. Each project is fully isolated — its library and context never leak into another.
Reset is cheap
Most issues clear up after restarting the app and reconnecting your account. Your files are local and untouched, so a restart never risks your work.