We have seen cases where a web application script has been created using Google Chrome but when running it in the preferred environment the Chrome application will not start the preferred website. Similar to the image below:
This issue came from a configuration that was pushed to chrome via GPO's the exact configuration was:
--user-data-dir (Configures the directory that Google Chrome will use for storing user data)
This was set, in the case of the example, to a network drive. Which is against the best practices of chrome. Changing this setting to the profile of the user / default location "%localappdata\Google\Chrome\User Data\ " fixes the issue.