Closed MetaFight closed 7 years ago
I can't seem to reproduce this. I'm hoping the person who raised the problem will come back and provide some more details.
Not sure if this helps, but Windows Defender identifies the trojan as this. I just downloaded latest release directly from Releases page, wasn't even able to run the .exe
@ujell thanks, that does help. I'm going to pull the last release until I can figure this out.
Cheers.
@ujell out of curiosity, could you share your OS version and Windows Defender "threat definition version"? I still can't seem to reproduce this issue.
@MetaFight Windows 10 Pro, Version 1703, Build 15063.138 If thread definition version is the same with Antivirus/Antispyware version then 1.241.890.0
@ujell Thanks.
I'm on a slightly more recent build of Windows 10 than your, however we have the same Windows Defender version.
I've scanned the 1.2.0.0 and 1.3.0.0 builds and they report as clean. I'm confused :|
Anyway, I just built 1.3.0.1 removing the "Start automatically with Windows" thing from the installer. Hopefully that will help.
Could you give it a try?
https://github.com/PerfectlyCromulentLtd/PowerBuddy/releases/tag/1.3.0.1
@MetaFight Seems like it works! Windows Defender didn't automatically warned me so I also manually scanned the file, no threads found.
@ujell thanks!
Resolved by 941a843
See comments:
The NSIS functionality probably writes to the registry "Run" key. I'm assuming this is frowned upon nowadays leading to Windows Defender reporting it as a Trojan.
I'll find a more modern/sensible way of doing this.