How to fix “Profile failed to start” error

Written by Yelena V ( Updated on April 29th, 2025 )

Updated on April 29th, 2025

Is your profile refusing to start and throwing the “Profile failed to start” error? Don’t worry – we’ve got you covered. Let’s troubleshoot this together!

Reconnect the agent

Reconnecting the agent is easy, and it typically resolves connection hiccups – follow the article How to disconnect and reconnect the agent and see if it helps.

Check storage type

Check if your profile uses local or cloud storage:

Local storage: profiles can only be accessed on the device they were created on – you can’t launch them elsewhere
Cloud storage: profiles are accessible from any device, making switching seamless

So, if you create a local profile on device X and try to launch it on device Y, you will get this error. If possible, launch the profile on the same machine you used to create it. This is the fastest way to get things running again.

Check proxy status

A faulty proxy might be the culprit – use the guide How to test a proxy to see if your proxy is working. If it doesn't, the profile won't be able to launch.

Refresh components

Deps

This action is completely safe! It refreshes the app components needed for Multilogin to work smoothly. No data will be lost during the process, so you're good to go! 😊

Avoid deleting the mlx folder, as this may result in a complete or partial data loss.

Disconnect the agent
Go to the mlx folder:
1. Windows: C:\Users\%username%\mlx
2. macOS: /Users/%username%/mlx
3. Linux: /home/%username%/mlx
Delete the deps folder
Connect the agent to get things rolling
Start any profile – this will automatically kick off the components download process

Nothing helps?

We will be more than happy to look into the issue further! Send us logs so that we can take a closer look.

Logs

Recreate the issue or wait until the error message appears
Archive the logs folder found in these locations:
1. Windows: C:\Users\%username%\mlx
2. macOS: /Users/%username%/mlx
3. Linux: /home/%username%/mlx
Email support at [email protected] with:
1. A clear description of the issue
2. The archived logs folder attached

Common errors

Contact Us