Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launching msedge.exe with --no-sandbox command line switch #141

Open
michasanyi opened this issue Apr 4, 2024 · 2 comments
Open

Launching msedge.exe with --no-sandbox command line switch #141

michasanyi opened this issue Apr 4, 2024 · 2 comments
Labels
feature New feature or request

Comments

@michasanyi
Copy link

Hi there,
Since version 119 on some machines edge browser is not able to run due to the following error:

"Code Integrity determined that a process (\Device\HarddiskVolume2\Program Files (x86)\Microsoft\Edge\Application\msedge.exe) attempted to load \Device\HarddiskVolume2\Windows\System32\sysfer.dll that did not meet the Microsoft signing level requirements."

The mentioned sysfer.dll is part of Symantec Endpoint Protection, which is used in our company. However if msedge.exe is started with --no-sandbox command line switch, then edge browser is able to run well (however there is a security risk).
Our tests use only web pages written by us, that's why it is sure that those web pages do not contain any harmful viruses.
It would be nice if there was a way to have msedgedriver to launch edge browser with --no-sandbox switch. I guess a new option could be added to EdgeOptions.
Thanks in advance,
michasanyi

@michasanyi michasanyi added the feature New feature or request label Apr 4, 2024
@michasanyi
Copy link
Author

I had a look into structure of EdgeDriverService. It has a property named CommandLineArguments, but it has only getter. Adding setter to it would solve my problem.

@michasanyi
Copy link
Author

There might be a simpler and more general solution:
It looks from the verbose log that msedge.exe is searched for first in the current directory, then in the current user's \AppData\Local\Microsoft\Edge\Application\ folder, finally in C:\Program Files (x86)\Microsoft\Edge\Application.
If shortcut to msedge.exe was searched for also (before checking if exe is present in the mentioned folders), then any additional command line argument could be set in the shortcut.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant