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

Windows defender popup is shown even though exclusion was added already #1770

Closed
2 tasks done
mderveeuw opened this issue Mar 22, 2024 · 7 comments · Fixed by #1772
Closed
2 tasks done

Windows defender popup is shown even though exclusion was added already #1770

mderveeuw opened this issue Mar 22, 2024 · 7 comments · Fixed by #1772
Assignees
Labels
bug Something isn't working

Comments

@mderveeuw
Copy link

Steps to reproduce

From a fresh JDT installation and clean workspace:

  • Launch JDT
  • Click Exclude Eclipse IDE from being scanned to improve performance. in Windows Defender Exclusion Check that pops up, and proceed
  • Exit JDT
  • Launch JDT again

I expected:

The Windows Defender Exclusion Check to not show

But got:

The popup shows every time

image

Tested under this environment:

  • Windows 11 Pro 10.0.22631 Build 22631
  • Eclipse IDE for Java Developers (includes Incubating components)

Version: 2024-03 (4.31.0)
Build id: 20240307-1437

Community

  • I understand reporting an issue to this OSS project does not mandate anyone to fix it. Other contributors may consider the issue, or not, at their own convenience. The most efficient way to get it fixed is that I fix it myself and contribute it back as a good quality patch to the project.
@mderveeuw mderveeuw added the bug Something isn't working label Mar 22, 2024
@merks
Copy link
Contributor

merks commented Mar 22, 2024

Does the absolute path of the installation or the user home folder contain spaces or non-ascii characters?

@mderveeuw
Copy link
Author

@merks it does indeed, I see now that this is likely a duplicate of #1757

@merks
Copy link
Contributor

merks commented Mar 22, 2024

Yes, that’s why I ask. Could you share an anonymized sample of the path so we can be sure that case is covered?

@HannesWell HannesWell self-assigned this Mar 22, 2024
@HannesWell
Copy link
Member

Thanks for the report. Looking at the shared screenshot the white-space in the path is probably the cause of the problem, just like in #1757

The PR #1772 should also fix this.

@HannesWell
Copy link
Member

Just verified locally that only space in the path breaks persisting the applied exclusions. Using one of the following paths works as expected

  • C:\pathWithë
  • C:\pathWithÖ

So #1772 as it is should be sufficient.

@HannesWell
Copy link
Member

@mderveeuw if you are interested you can try out tomorrows Integration build from https://download.eclipse.org/eclipse/downloads/ in order to verify it really works as expected.

@mderveeuw
Copy link
Author

@HannesWell the latest build works for me, thanks for the fix!

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

Successfully merging a pull request may close this issue.

3 participants