Forceflow wrote: ↑Fri May 10, 2019 11:00 am
Just checked on a totally different system (my laptop), and that error has been in the logs there since January as well.
A regular expression on "*nvapi.dll" that's a bit too aggressive?
Yeah that's a bit too dangerous.
It's not really a *nvapi.dll in the code but it work almost like that.(kinda bad)
I will need to fix this properly.
But for fax fix I did manually exclude the file in question for the next version until I pop out a solid solution.
I had a look on Github, but couldn't immediately spot the error. I see a big config file where "nvapi.dll" is listed, but couldn't really figure out how it's handled