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

bug: Windows Defender Smartscreen prevented an unrecognized app from starting #1134

Open
2 tasks done
ath0mas opened this issue Oct 18, 2023 · 4 comments
Open
2 tasks done
Labels
bug Something isn't working

Comments

@ath0mas
Copy link
Contributor

ath0mas commented Oct 18, 2023

Is this an issue specifically with Appium Inspector?

  • I have verified that my issue does not occur with Appium, and should be investigated as an Appium Inspector issue

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Downloading the latest exe file available, currently 2023.10.1, and starting it is blocked by Windows Defender SmartScreen.

(in French for me)
Capture d'écran 2023-10-19 003704

It is possible to manually bypass this, but it still blocks automatic installs and should be fixed. please

Expected Behavior

The installer starts without being blocked by Windows Defender SmartScreen.

Operating System

Windows

Appium Inspector Version

2023.10.1

Appium Version

No response

Further Information

No response

@ath0mas ath0mas added the bug Something isn't working label Oct 18, 2023
@eglitise
Copy link
Collaborator

I tried version 2023.4.1 and it also had this issue (although for me the error showed unknown publisher), so it doesn't seem to be related to any recent changes.
@jlipps Maybe this is something to do with the build machine on the Azure side? From what I can tell, it needs the CSC_LINK and CSC_KEY_PASSWORD env vars, which are already being retrieved here, but maybe they're missing or are not valid anymore?

@SaptooAji
Copy link

SaptooAji commented May 15, 2024

Hey guys, having the same problem here. I installed the latest version, namely 2024.3.4, and looks like the issue is still open. Any suggestions to overcome this?

@eglitise
Copy link
Collaborator

Just click More info -> Run anyway.

@JonathanStefanov
Copy link

Hi, this is still an issue if it is a company owned computer and the bypass is then not possible
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants