Orchestrator problems. Studio and Robot no available licenses

[loginerror (Maciej Kuźmicz)]

This specific post should fix that:

Error Message When Attempting to Report an Error Message

Hi @roger1 Welcome to our UiPath Forum I will make this post public because it could be information that will prove useful to other users as well. I was able to easily reproduce this error on my end and I reported it to our team. First, I am happy that our first run Studio experience went flawlessly for you. Main thing that makes it possible is the default simplified setup that you get out-of-the-box. Mainly, by signing up to Orchestrator from your Studio for the first ti…

Some settings will look slightly different on a new Cloud account, but the crucial bits will be the same.

It comes down to the fact that machine key connection is not fully compatible with the latest changes to the default settings in Orchestrator.
This setting in Orchestrator forces your Assistant and Studio to use the sign in and does not allow for the machine key connection:

This is why it might be easier to workaround it by using the method of connecting your Studio/Assistant as per my post above. It then uses two licenses - the attended which is fully compatible with sign-in for the Assistant/Studio, and unattended runtime to allow you to run processes from Orchestrator on that machine.