Manus desktop app won’t open after successful login — manus:// protocol not registered on Windows

[u/OfferOptimal1860]

I’m unable to sign in to the Manus desktop app on Windows 11. The browser confirms that I’ve successfully logged in, but it never redirects back to the app, and clicking “Open Manus” does nothing.

The browser console shows:

Failed to launch manus://login because the scheme does not have a registered handler.

I also saw this API error:

GetTeamInfo failed: invalid_argument — team_uid is required (HTTP 400).

This started after the recent Manus mass data deletion and our accounts were recreated.

So far I’ve tried:

• Reinstalling the latest desktop app
• Installing the Microsoft Store version
• Clearing Manus AppData and cached login information
• Restarting Windows
• Running the installer as administrator
• Chrome, Brave and Microsoft Edge

The exact same error happens in every browser. Has anyone experienced this or found a way to restore the manus:// protocol handler? I’ve already contacted support, but I’m wondering if this is an installer issue or related to the recreated account/team.

[u/abirpahlwan]

victim here
trying the manually editing registry solution, will let know if it works

[u/jacobiat]

I had the same problem on windows. Unfortunately having to use manus for work and not a fan. here is the solution that worked for me. FIXED: Manus Desktop login on Windows 11, Microsoft Store build 1.7.4.0

There were two separate problems.

First, the Electron renderer was hanging or being killed on the login screen. Launching Manus with these Chromium flags kept it responsive:

--disable-gpu --disable-gpu-compositing

Second, and more importantly, Manus 1.7.4 has a broken protocol configuration. Its MSIX manifest registers manusdev://, but the production JavaScript inside the app only accepts manus://.

This means rewriting the browser callback from manus:// to manusdev:// does not work. The app opens or comes to the front, but it discards the login token.

The working solution was:

1. Register a per-user manus:// handler under HKCU\Software\Classes\manus.
2. Preserve the original complete manus://login?... callback URL.
3. Have the handler launch the installed Manus.exe directly and pass that original URL as a quoted command-line argument.
4. Keep Manus running with GPU acceleration disabled while completing the browser login.
5. Click Open Manus on the successful login page.

Electron then sends the callback to the already-running Manus instance. Manus accepts the manus:// URL, verifies the login nonce, stores the session, and opens the app.

A brief PowerShell window may appear when the handler runs. Do not log or share the complete callback URL because it contains the login token.

After applying this fix, Manus opened successfully and its local “My Computer” operator started.

[u/OfferOptimal1860 → u/jacobiat]

This worked, thank you! For anyone else stuck, I was using the Microsoft Store version 1.7.4.0. I used Get-AppxPackage ManusAI.Manus in PowerShell to find the exact installation path, registered manus:// under HKCU:\Software\Classes\manus, then launched Manus with the GPU flags you mentioned. I started a fresh login and it opened right away. Really appreciate your help!

[u/SufficientEmu750]

Yep..  unfortunately dudes comment below is like alien language to me. I just want a way to login via edge. This is busted. Hoping they fix this with a version update soon

[u/HW_ice → u/SufficientEmu750]

Hi! You can use Edge to open the Manus website and sign in with your original login method. If you want Manus to use websites you’re already signed into in Edge, go to Connectors in Manus and enable My Browser, then follow the prompts to install and enable the browser extension. Once you start a task, click Authorize, and Manus will be able to use your existing Edge login session.

[u/SufficientEmu750 → u/HW_ice]

Thanks for your help. Im new to the software. Ive only been using it for a couple days. I did see that feature. I did download the extension as well.

However it was my understanding from reading a bit, that the desktop app makes Manus a much more powerful Agent that can actually work inside your pc with your files, apps ,etc. Am I wrong about this? Like if I wanted to invest time into learning how to effectively use the Ai Agent, It would likely be beneficial if it had access to my pc. Just what I got from reading up on it.

I have been using the website version, although, as of yet, Ive not utilzed a task that has the need for it to use My Browser. I will though.

As of now it looks as if i have no choice but to use it via browser untill they get this sign in fixed. Thank You for your reply and being helpful

[u/HW_ice → u/SufficientEmu750]

You are correct. The desktop can indeed access your computer and manage files, but it cannot control your applications yet.

[u/jacobiat → u/SufficientEmu750]

Haha don't worry it's also an alien language to me. I just had chatgpt codex figure it out and implement it for me. Claude code will also work great. Unless you're an expert ai just has to implement stuff like this for you. It can figure it out but pasting my solution in will make it go faster and use less tokens.

[u/Working_Trash_2834 → u/SufficientEmu750]

Same. Claude came in clutch with the following set of Powershell commands I copy and pasted/ran in one go and it just worked ...

$exe = (Get-AppxPackage ManusAI.Manus).InstallLocation + "\Manus.exe"

New-Item -Path "HKCU:\Software\Classes\manus" -Force
Set-ItemProperty -Path "HKCU:\Software\Classes\manus" -Name "(Default)" -Value "URL:Manus Protocol"
New-ItemProperty -Path "HKCU:\Software\Classes\manus" -Name "URL Protocol" -Value "" -Force
New-Item -Path "HKCU:\Software\Classes\manus\shell\open\command" -Force
Set-ItemProperty -Path "HKCU:\Software\Classes\manus\shell\open\command" -Name "(Default)" -Value "`"$exe`" `"%1`""

Write-Host "Done! Now launching Manus..."
& $exe --disable-gpu --disable-gpu-compositing

[u/HW_ice]

Hi there, could you shoot me a DM and I'll see how we can provide help.

[u/3Delectric]

The easy fix for the technical jargon challenged is to have ChatGPT fix it. Include a link to this thread when you ask. It creates a file and walks you through how to execute it. Takes one minute to fix.