The thing is: Last monday I got of from work and I found my PC with no internet connection. I checked if the modem was OK and then the cable that connects the PC to the Modem and it was also OK. The modem has WiFi sharing as well and I check all the other devices and all of them were connected through it. So I tried to find what was wrong with the computer, which runs a windows 10 pro. First I opened the device manager, found the netword card adapter driver, disabled it to re-enable (wich is a basic thing to do if the driver is not doing so great), but then the device disapeared completly, even from the adapter option....I couldn't see it anymore, anywere, as if somehow the driver and the hadware were uninstalled. So I though "damn, I'm gonna have to buy another netword card and install it". But then I tought of doing what I sould've done in the first place: Run an Anti Virus scan....since Avast was really bugging me a few weeks back, I uninstalled it, then upgraded to Windows 10 and I have been using the windows defender, wich I want your opinion about it as well, since it allowed a hacktool:win32/autokms to infect my PC. When the windows defender complete scan finished and detected this virus, I told it to delete it and reboot (which was necessary to completetly remove the infection)....when the PC restarted, for a few minutes I was amazed because the network was connected again and the network adapter was showing in the device manager...but, a couple of minutes later...the driver disapeared again and the internet connection dropped to never come back up again...so I ran another scan, but this time, nothing was found.....I ran the system in safe mode with network, but still it couldn't connect (but the driver was there again)...really creepy situation....so....please, what should I do now? Should I backup my computer and format it (in windows 10 they call it restore)....is there a free antivirus software that is good enough to find the traces of the virus windows defender couldn't remove (if there was really any left)....please, help me.....thanks
That being told, if any evidence of illegal OS, software, cracks/keygens or any other will be revealed, any further assistance will be suspended. If you are aware that there is this kind of stuff on your machine, remove it before proceeding!
The same applies to any use of P2P software: uTorrent, BitTorrent, Vuze, Kazaa, Ares... We don't provide any help for P2P, except for their removal. All P2P software has to be uninstalled or at least fully disabled before proceeding!
Due to the lack of feedback this topic is closed to prevent others from posting here. If you need this topic reopened, please send a Private Message to any one of the moderating team members. Please include a link to this thread with your request. This applies only to the originator of this thread.
Other members who need assistance please start your own topic in a new thread. Thanks!
I had compiled a simple hello world program in C with the MinGW compiler using the command line. As it had finished compiling, windows defender popped up and detected a virus (Trojan:Win32/Fuery.C!cl).
EDIT: I deleted the path variable of C:/MinGW and added CodeBlock's MinGW compiler. I then used the command line to compile the same C file again and had uploaded the .exe file to VirusTotal. This time, 0 engines detected. So I have come to the conclusion that, the MinGW compiler that I had installed was creating this problem.
This is what I did: I removed the PATH Variable of C:\MinGW and added CodeBlock's MinGW compiler (CodeBlocks/MinGW/bin). I used the command line to compile the same C file, and had uploaded the .exe to VirusTotal. No engines detected this file!
Since you wrote that program and you know it isn't actually a Trojan, it's obviously a false positive. You should submit the file to them at so they can figure out why it's triggering the false positive and fix it. (If it happens with everything you compile, just sending them one will suffice.) In the meantime, you should add an exclusion to Windows Defender for the folder that you compile your executables in.
I ran into this after installing MinGW on 01-08-20(dd-mm-yy).For me it was also Windows Defender, the way to - hopefully temporarily- get rid of this is to add an exception for the folder your compilation output will reside in.The Microsoft website states these steps to add an exclusion:
I had a similar problem. I figured out that the following dll was missing: mingw32-libmingwex-dll. Once I installed it via "MinGW Installation Package", I didn't have the problem anymore.I hope this can help others.
I had the same problem (having a freshly compiled executable on a clean machine, accused of carrying malware), however when updating a project with VS2022, originally done in VS2015 and using VB. After compiling and taking the executable to the installation folder, a few seconds after replacing the old executable, Windows Defender detected a virus (Win32/Nuqel!pz), removed it from the run folder and quarantined it. My client, who needed to use the new version, had to put the executable as an exception, which is a reduced security condition.
d3342ee215