Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

windows-latest chrome version unavaliable in registry

See original GitHub issue

Describe the bug The chrome version is unavailable in the registry unless you open chrome for the first time. This was discovered when trying to use pythons webdriver-manager to handle running the correct version of chromedriver. it uses the reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version command to get the chrome version. I added steps to my github workflow to manually open chrome with Start-Process -FilePath 'C:\Program Files\Google\Chrome\Application\chrome.exe' but sometimes it gets the version of chrome and other times it does not. Possibly due to the order that steps are run in? or a delay between chrome opening up properly and adding to the registry and the other workflow steps being run before that happens?

To Reproduce Steps to reproduce the behavior:

use the windows-latest for a github action
run a python script that uses the webdriver-manager
observe the output “Current google-chrome version is UNKNOWN”

an example of the used workflow can be found here and the python script used can be found here

Expected behavior webdriver-manager should be able to get the chrome version without taking extra steps as chrome is installed by default on windows-latest image. ubuntu-latest and macos-latest do not have this same issue.

Runner Version and Platform

2.287.1 windows-latest through github runners

What’s not working?

There actual error codes are related to my failed unit tests, But this is caused by having a mismatched chromedriver and chrome versions as webdriver-manager will get the latest chromedriver when it cant find the version of chrome.

The chrome version error is: "Could not get version for google-chrome with the any command: reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon" /v version"

Job Log Output

Runner and Worker’s Diagnostic Logs

Runner Diagnostic Logs

Issue Analytics

State:
Created 2 years ago
Comments:6

Top GitHub Comments

1reaction

ghostcommented, Feb 11, 2022

Done. The post can be found here

Thank you for your efforts in reproducing this bug and responding with the correct place to post this issue 😃

0reactions

ruvceskistefancommented, Feb 10, 2022

Hi @Pavocracy, We investigated the problem you reported and found that it was not a runner related issue. This issue concerns the GitHub actions platform more generally. Could you please post your feedback on the GitHub Community Support Forum which is actively monitored. Using the forum ensures that we route your problem to the correct team.