I updated the UnAttended machine running UiPath Assistant version 24.10.14 to 25.10.11.
After entering the machine key and signing in on 25.10.11, I see a message saying “No License” and cannot use the Assistant.
Despite this issue, I am able to run processes from Orchestrator, which is quite confusing.
I tried uninstalling and reinstalling it once, but I ended up with the same screen.
When I tried LicenseTool.exe, I encountered this screen.
What else should I check?
Hello
First, I think it’s related to the Orchestrator connection, so LicenseTool.exe is not relevant. (It’s a tool for non-OC standalone licenses)
The Unattended Robot is basically unrelated to interactive sign-in via UiPath Assistant (although the authentication with the client ID/secret for OC is relevant), and a license is granted to RobotService when connecting to OC. So, if the execution commands from OC are being received, that part seems to be functioning normally.
The signal in the top right corner of the Assistant screen appears to be green, so it seems normal, but what message do you get when you hover the mouse over it?
Also, was the installation done in service mode?
Thank you as always.
LicenseTool.exe is not relevant, right?
The signal in the upper right shows “Status: Connected, Licensed.”
I had not been aware of the type of installation, but it seems to be a user mode installation.
Hello
I was able to reproduce it in my environment as well.
If the user signing in interactively has licenses such as Attended, the process will be displayed, but otherwise, it will not be shown. (If you enable the troubleshooting session, the process will be displayed even when not signed in interactively.)
It seems that starting with version 2025.10, the product specifications have become more rigorously applied to license agreements.
Thank you for the verification.
Is it impossible to run processes manually with the Unattended license of Assistant?
Given the above situation, if the user signing in does not have a valid Attended user license, it may be difficult to execute from Assistant. For a more accurate answer, it might be better to check with official support.
As a workaround, it seems that executing from the command line could work, so there might be an option to substitute that.
Thank you for your reply.
After signing out from the settings on the screen above, I saw “To check the automation here, enable the troubleshooting session in OC,” so I actually tried it.
After enabling “Set up troubleshooting sessions” in OC’s tenant > Monitoring > Unattended Sessions, a list of processes was displayed in the Assistant, and I was able to execute them as well.
I will trigger execution via Unattended, but since it has been set for manual execution by another person when I encounter an error in my absence, it becomes very troublesome if I cannot execute the process from Assistant… I will try contacting official support just in case.
Thank you.
As a reference, if you just need to rerun it, another person can log into the Orchestrator web interface and initiate the execution from there, or you could create a simple script to call the process execution API using PowerShell, which would allow execution from any terminal. This might be an alternative solution.
