At first, review the following articles and then check the "Possible causes" described below:
- Configure Chrome & Firefox for Web Automation
- Using Chrome Web Extension with Multiple Chrome Profiles
Possible cause #1
Possible cause #2
In Chrome browsers that have multiple extensions installed, reinstalling the add-on may fix this issue.
Possible cause #3
This issue can be hardware-related. If it persists, then it possibly means that the machine's hardware resources are limited.
Possible cause #4
The Robot may not have enough permissions to interact with Chrome. In order to check if this is the problem, run Process Studio with administrator rights. If this resolves the issue, then configure your Robot to run as admin as well. Check this article.
Possible cause #5
Go to Chrome's preferences document at C:>Users>(your_user_account)>AppData>Local>Google>Chrome>User Data>Default>Preferences and set the exit_type to “normal”. Check if this resolves the issue.
Possible cause #6
When Controls cannot be captured and the "Launch New Chrome" Action fails, we need to check the machine's "ComSpec" "Environment Variable". It is possible that "ComSpec" does not exist or it is misconfigured. It should be set as seen in the following screenshot: