[🐛 Bug]: selenium-manager.exe being blocked as malware

[HernJer]

What happened?

After upgrading from 4.14.1 to 4.15.0, selenium-manager.exe gets blocked by software like Carbon Black.

How can we reproduce the issue?

.

Relevant log output

![image](https://github.com/SeleniumHQ/selenium/assets/87041628/67b84785-e10f-469b-a611-29404df718ea)

Operating System

Windows Server 2012 R2

Selenium version

4.15.0

What are the browser(s) and version(s) where you see this issue?

na

What are the browser driver(s) and version(s) where you see this issue?

na

Are you using Selenium Grid?

na

[github-actions]

@HernJer, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[bonigarcia]

Sorry for the inconvenience. I suppose this issue is caused by using the stable-i686-pc-windows-gnu target to build Selenium Manager for Windows in Selenium 4.15.0. But since this target is only required for the debug version of Selenium Manager in Windows, I think we can revert to stable-i686-pc-windows-msvc for the release version (which seems safer than the gnu one in the eyes of antivirus, for some reason). We can use stable-i686-pc-windows-gnu only for the debug version (this will include the debug symbols used for troubleshooting).

I created a PR to change how Selenium Manager is built in CI: #13134

@HernJer Can you please have a try with the new binary?

1. Download the new binary from here: selenium-manager_windows-x32
2. Uncompress it and replace it with your local Selenium Manager at C:\agent\runner\selenium.webdriver\4.15.0\manager\selenium-manager.exe
3. Test again and share the results here.

Thanks

[HernJer]

@bonigarcia - that seem to have done the trick. thanks! i am also sending the file to my IT Sec team to fully vet.

will this be packaged on a new version so i can update my references?

[bonigarcia]

Great to know, thanks @HernJer. Yes, this new Selenium Manager Windows binary will be shipped with next Selenium release.

[vikramtechforall]

@bonigarcia was this change incorporated in 4.16? because i am still observing the issue with selenium-manager.exe

[titusfortner]

We're still working to get the binaries signed which should fix the issue.

[vikramtechforall]

Thanks @titusfortner! Is there an ETA on the same? is there a temporary file which we could try to make sure that's going to work fine with our firewall/proxy settings?

[titusfortner]

I'm not sure what you mean by a temporary file. What we have isn't signed and might flag security checks if they are stringent. I'm not sure the current status of it as it is our fiscal sponsor who is running down the requirements for us, and we haven't had a chance to follow up in a while.

[HernJer]

Any change this can this be reopened until it's actually resolved? Don't want this to fall down the cracks.

[titusfortner]

It's being tracked here — #12935

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.