No profile could be launched

The message carries a reason after the full stop. That reason is the actual cause, and the five below are what it usually says.

If the line ends without a reason, start with the open limit: it refuses before anything is tried.

The app counts how many profiles are open and refuses to open one more past the computed ceiling. The number comes from the memory on this machine, not from a fixed twelve.

Close a window and try again. The refusal names the count it stopped at.

You have more profiles than the plan opens. This happens after signing out, after a paid plan ends, or when profiles were added around the app. The refusal names the limit and the number of profiles.

The oldest profiles within the limit open; the rest are marked “Over the limit”: they are kept and visible, and you can export them, but they do not start. To open such a profile, move one of the opening ones to the Recycle bin: the Recycle bin erases nothing, and you can bring a profile back once a place is free.

A paid plan gives more profiles. Signing in to a free account gives the same limit as not signing in.

Without signing in there is a second refusal of the same kind: as many profiles are already open as the limit allows. This happens when ARMANOS Browser windows outlived an app crash. Another profile opens once you close one of the open ones.

When signed in, a refusal of the same kind comes when the browser of a profile that was moved to the Recycle bin or is over the limit is running, and the app does not know it and cannot close it: it runs outside the app. The refusal names that browser. Close its windows, and the profile opens.

The limit without signing in is one for the whole computer. Profiles of accounts on this computer that you signed out of stand in the same queue: the oldest open, and the refusal names how many profiles there are here and in other accounts. A second copy of the installed app on its own folder (the --user-data-dir option) does not open profiles without signing in and says that it works when signed in.

A profile opens in the ARMANOS Browser engine. If the app cannot find it, nothing launches and the reason says so.

Open the engine settings and point the app at the file. The app refuses a file it cannot execute rather than saving it and failing later.

Before every launch the app checks the proxy: it asks the address services for the exit country through the proxy itself. A proxy that gives no answer in 12 seconds does not open the profile, and neither does a proxy that refuses the connection, whose address is not found or that does not accept the login.

Your real address is not used in any case: a profile never goes out around its proxy. The profile stays closed for another reason: a window without a working proxy opens no site, and without a checked exit its clock and language could not be set to match the address.

The profile row says why: a red dot next to the proxy and a short label, for example «No answer · 12:14». Check again runs a new check, and Change proxy opens the proxy picker of that row.

If the profile is set to rotate before every launch, a failed rotation stops the launch. The message says the profile was NOT opened.

That is the point: you asked for a new address exactly when the old one cannot be used.

Reproduce the failure, then collect the evidence rather than describing it. Write through Help → Write to support: a report with the version, the system, the chosen engine and the app's recent notifications goes with the message.

Put the exact time and the profile name in the message. A message that says only «it does not work» costs you a day.