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

4.0.1 core.jar Flagged as Trojan on Windows 10 #543

Closed
Mitch-at-Beaudry opened this issue Aug 24, 2022 · 2 comments
Closed

4.0.1 core.jar Flagged as Trojan on Windows 10 #543

Mitch-at-Beaudry opened this issue Aug 24, 2022 · 2 comments
Labels
Duplicate This issue or pull request already exists

Comments

@Mitch-at-Beaudry
Copy link

Description

After downloading and unzipping Processing to the Downloads or Documents directories on Windows 10, running <processing.exe> does not launch the software. No logo, no PID in the Task Manager. Upon further inspection, it appears Windows Defender Safe Screen is identifying the <core.jar> file as a Trojan and "quarantining" it.

It appears nearly identical to this closed issue from Processing 3.3.7 back in 2018.

Expected Behavior

Processing 4 launches after double clicking <processing.exe>

Current Behavior

Processing 4 does not launch

Steps to Reproduce

  1. Download Processing 4.0.1, Windows (Intel 64-bit) on a Windows 10 machine
  2. Unzip the downloaded file to the same directory (presumably Downloads)
  3. Open the unzipped directory and double click <processing.exe>

Your Environment

  • Processing version: 4.0.1
  • Operating System and OS version: Windows 10 Version 10.0.19043
  • Other information: Reproduced on two separate machines, one of which was factory reset.

Possible Causes / Solutions

No amount of setting changes in Windows Defender allowed the <core.jar> file to remain intact for more than a few seconds before being quarantined. My workaround:

  1. Move the unzipped Processing directory to the machine's "Program Files" directory
  2. Copy <core.jar> from the zipped directory into the new directory
  3. Run <processing.exe>
    It seems that the admin permissions of "Program Files" circumvents the Windows Defender Safe Screen process from deleting the <core.jar> file.
@Mitch-at-Beaudry
Copy link
Author

Apologies, looks like this is a duplicate of issue #541

@Mitch-at-Beaudry Mitch-at-Beaudry closed this as not planned Won't fix, can't repro, duplicate, stale Aug 24, 2022
@benfry benfry added the Duplicate This issue or pull request already exists label Sep 23, 2022
@github-actions
Copy link

This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants