Avast says that there is a suspicious file(CDVDnull)
#1
The weird thing is
v1.3.1-1415-g9bb990e - everything is fine
v1.3.1-1416-gb6f78d8 - suspicious file detected(CDVDnull but there is no change to that file in that rev)
And I keep getting that message on every rev till the latest beta(including)
Reply

Sponsored links

#2
Again? First it was with padnull and now this lol.

Welp, report to avast again, it should get fixed with an update to the definitions.
AMD Ryzen 5 3600 @ 3.60~4.20 GHz | Corsair Vengeance LPX 32 GB (2x16GB) DDR4-3200
MSI GeForce GTX 1660 Super @ 6 GB | Samsung 980 1TB | Windows 10 Pro x64 (22H2)
Reply
#3
I just find it strange...no change to the file(according to github)but there is some change(according to avast)
Edit:The file size is different
Reply
#4
It's because of the change to VS2015 that the file is different. That's also what triggered padnull to be detected.
[Image: XTe1j6J.png]
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Reply
#5
Hmm,yes.
On exactly that rev(1416),CDVDnull have totally different imports and one of the files tells me that it need vc2015
Reply
#6
Yeah 1416 was the first version we compiled with VS2015.
[Image: XTe1j6J.png]
Gaming Rig: Intel i7 6700k @ 4.8Ghz | GTX 1070 TI | 32GB RAM | 960GB(480GB+480GB RAID0) SSD | 2x 1TB HDD
Reply




Users browsing this thread: 1 Guest(s)