ok, so i couldnt start the launcher due to an issue with a dll file, and i located one in my anti-virus quarantine folder. i checked and it hits as a trojan file, but unfortunately i was unable to find out for sure exactly what it is doing that causes it to read that way. (sometimes i can pinpoint what's triggering it on virus total but not this time).
has anyone else run into this or seen anything odd going on after installing or running the game? or know what's in the launcher dll that causes this?

just un\reinstalled the game and watched it. had more than one item this time, and actualy loaded the game the first two times (i didnt check if it was playable, but i saw that it did start the game).

(edit:added the failed check screen as well(which also reported that file it was unsigned). in addition to the 3 items listed, cylance also detects an issue with it)

the 3rd pic is the 2nd file (the mod_helper file)
please note that these could easily be false positives by my av(it triggered on gog installer since it was just the launcher for it and it wanted to connect and download more data, so it got flagged at the time).

im opening a support ticket with gog to see whats up, but in the mean time was wondering if anyone else knew anything.

EDIT: VTM:Bloodlines

If you want an answer you must first tell us which game yoou're talking about!

These are false positives caused by the Unofficial Patch for Bloodlines which is included in the GOG release.

ops! coulda sworn i listed it as vtm:bloodlines.
ive edited the post to include which one, thanks. ya thats what im hoping. do you have any info on these are causing false positives tho? (like do you remember where you found that info at or knowledge about whats going on? my concern there is that if this "unofficial patch" which is included -from what i can tell it wasnt made by gog?-was just tacked on that it could be (how do i say this) if they just slapped it in there i dont know if i can trust the source of it.

I can't help grinning a little. You are corresponding with Wesp who is responsible for the unofficial patch. If you want to know more about that patch then read the sticky at the top. In the meantime, from my point of view, this patch makes the game playable. And it certainly was not casually "tacked on" or "slapped in".

Not really, but the game mod loader which makes it possible to install the patch and other mods in parrallel is a hack of some original files and might accidentally show a signature that some antivirus files might recognize.

heh didnt know *that* lol ok, so the loader is what the .dll file is then? and since apparently you worked on this (thanks for taking time for me here btw), would you happen to have the original unmodified version of the games .dll still, or is this a completely custom creation?(just wondering for comparison is all, its no big deal)

and the way you say in parallel; is it possible to run the game w\o this patch or is it installed with the patch intertwined into the base code? (i ask because it dose create an folder that calls itself unofficial patch, but any .ini or .config i can find in the base folder sates that it is v1.2 (10.2 is only in the UPfolder. do i need to do something or is it already patched up to 10.2 and if so which of your up versions is it -base\+\etc-?)

(if it makes a difference, everything ive done is first tried with no modification to the game files\folder)



I should point out that I am not going to override my security system unless i can pinpoint what's going on (im competent, but not familiar with code\script really). that said, im not too worried, because if *or rather, when* i get around to finishing up my work on my old pc, im not too concerned about what i do with it, as it wont have any sensitive information on it(just run old games so i dont have to work as hard to make em work on windows 10 lol). heck, with the older os ill have, i might not even have it connected to anything-just xfer data to it and be done lol.

(not saying i suspect anything is hidden away in the .dlls, but i dont brake protocol on my main machine)

It was made for me by some other modders and the loader.dll file is new. You can read more in the loader-readme.txt! The loader fixes more basic stuff like the memory limit, the copy protection and the widescreen support, but all the gameplay fixes are in the folder you mentioned. I think GOG even creates a "legacy" shortcut, so if you use that you get the original...

quote
It was made for me by some other modders and the loader.dll file is new. You can read more in the loader-readme.txt!
end quote

i saw that, but while its helpful in what it dose, threes not much about the file itself (im kinda curious about how it works, but have no background in it)

quote
The loader fixes more basic stuff like the memory limit, the copy protection and the widescreen support, but all the gameplay fixes are in the folder you mentioned. I think GOG even creates a "legacy" shortcut, so if you use that you get the original...
end quote

ya, i found the legacy exe poking around in the gog app, although it also uses the same dll.

well, thank you for taking the time for me here to help, I apricate it.
I was kinda guessing it was a false positive (well, I am assuming that gog would check any post production files they included lol) and i think what it boils down to is that there is an unsigned part in the loader.dll, possible an issue with injection or the way it wants to control another part (if its doing something to alter or control monitor output or memory, i could see it being flagged by my system)

at this point im curious to hear back from gog as well, though this could be a known issue to them in which case they will just say the same thing.
but i have more than one pc to play this on - since its an older game, my old pcs will handle it just fine :) - so i will proly just do that. thanks again!

Know that triggering a reaction from your anti-virus is quite common with older GOG games due to the hacks used to make it work / copy protection free.

ya i can understand that.
ive been lucky so far, out of nearly 60 items, ive only had one (populous the beginning) just not work out for me (im betting it will on my old machine, so not worried), and only 2 av hits, this and the gog app itself amusingly (it was because the "installer" was really just the installer launcher, and it wanted to phone home to download the app itself).
actually, im a little surprised at times how well things run for me, and the rest i can usually figure something out or someone else has had that same issue and a solution found, or a lot of the time there is still a small community of ppl dedicated to a game that can help out.

edit: ya i was thinking about how you said that "hacks used". it reminded me of something posted about one of the fear games and its crap someone who decompiled it said he found, but if you actually check the registry, it dosnt make the entry for securom or w\e it was. in a "perfect" world, things would just work or be reprogramed like new, but in reality, this is about the best we can get for these old games-but im glad to have it lol. found a lota gems here from my younger days.

My approach to these virus messages: 1) double-check that people are playing it and there's no actual virus problem. 2) Assuming good results with that, try ignoring the message. 3) If AV is ridiculously fussy and demands action, then disable the AV and install my game.

pretty solid. and i use cylance, which is *ridiculously* fussy-it basically stops the file from even opening in the first place. and is only soso about actually telling me it did so lol. it i usually end up uninstall \ reinstalling something before finding out that it did anything lol. (tbf, i would rather my av be protective than too lax tho)