Seems strange that the dev seems to be keeping quiet on this, no? I’m not telling you to read every comment of every post, you can just skim the post titles. Then you’ll see multiple open issues and a few closed issues too going back 5 days to the latest BtS update.

Though I haven’t followed this project long enough to tell if this is just the way they normally behave.

Edit:

I’m back at my computer, so it’s easier to edit and add info now.

Some key points that have stuck out to me:

  • Previous version released in July only triggers 2 detections on Windows defender versus 29 for the most recent version: https://i.imgur.com/GIoH7eG.png

  • Users getting constantly pestered to update to the latest version: https://i.imgur.com/Oege3kU.png

  • Yeah, naturally, the dev is going to say it’s a false positive. Obviously. I’ve only mentioned that the dev has previously responded because some people barely skimmed through the issues and thought the dev simply hadn’t seen the latest open issue from only a few hours ago, when that is not the case.

  • Scary le Poo@beehaw.orgEnglish
    4·
    29 days ago

    It’s a dll injection. Of course it gets flagged as a virus, because technically it is. That doesn’t mean that it is malicious.

    Here is an example… On paper, reshade is a horrifically dangerous piece of software. It doesn’t get flagged only because it is well known and virus scanners have an exception for it.

    Any of these geniuses stopped to think that Spotify changing its code and altering the way that it interacts with the dll could result in more “detections”?