Remote Session Launcher won't launch sessions due to Chrome 63 bug

[support]

Part of setting up the Remote Session Launcher requires you to configure your browser to add in a custom Passwordstate protocol.  This is normally a once off process, however if you clear your cache in the browser this will reset the protocol section. If you are running the latest stable build of Chrome (build 63), then attempting to add this protocol will not save, and hence our remote session  launcher will not be able to connect to any machines.

 

This was identified as a Chrome bug in December 2017 and has been patched in the next development version of Chrome.

 

If you find you cannot launch any sessions, either because it is the first time setting up the remote session launcher or you have cleared your cache, then there's a couple of workarounds:

 

• Uninstall Chrome and reinstall an old version.  Then Perform the Configure Browser section in our Remote Session Launcher set up page before Chrome automatically updates
• Unlikely, but if you had a backup of your C:\Users\<username>\AppData\Local\Google\Chrome\User Data\Default\preferences file that contained the protocol "psrsl:false" in it, you could copy this file back into your google profile and overwrite the existing file
• Install Google Canary, and perform the "Configure Browser" option, which will write the "psrsl:false" protocol to the C:\Users\lsand\AppData\Local\Google\Chrome SxS\User Data\Default\preferences file.  Potentially you could then copy this into your normal Chrome profile location listed above

 

Hopefully you will not have seen this issue and the next stable version of Chrome will patch it, but these workarounds are an option for you, even if they are not the nicest:(

 

Regards,

Support.