In this post, we are going to look at the Automation 360 Started Debugging this Browser alert message displayed on browsers.

Automation 360 Started Debugging this Browser

Automation 360 Started Debugging this Browser Issue

For me, this issue started occurring recently post upgrading the Chrome browser. I found that the registries are missing after the Chrome browser update.

Post that I observed the same issue on the Edge browser. It’s strange to find that this was also due to a missing registry key.

Refer our other posts on A360 topics

Automation 360 Started Debugging this Browser Solution\Workaround

Now, we know the cause of this issue. let’s try to fix this by creating the missing registry and the value would be browser extension ID.

I have done it for Chrome, please do the same for Edge browser as well.

Registry Path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Google\Chrome\ExtensionInstallForcelist

Right-click on the ExtensionInstallForcelist key –> New –> String Value and enter the Value data.

Automation 360 Started Debugging this Browser

 

Hope this helps! If it does, spread the word and help others as well by sharing this post.

Happy Automation 🤖



Source link

By i53gf