BioForce90

The task manager issue was fixed for the current account, but I had never tested it on other accounts until recently. By root access, I was referring to the fact that the account I am currently using, and the one that we fixed the issue with was my root administrator account, that has complete access to things normal admin accounts do not have.

I have two other accounts, but only care about one of them because the other one I made as a copy of the first. They both have admin rights, but not root access. I cannot extent task manager on either of them. What do you want me to show in the screenshot?

This is a home computer, and I use P2P torrenting mostly for secure downloads, although I wouldn't doubt that the virus got onto my pc through a torrent file

Here you go. Also, we did manage to fix all the issues with THIS account, but I found out a few minutes ago that the problem still persists on other accounts, and the CPU64, Desktop-64, and process executables are not in the files there. I couldn't find them in the registry, although that may be because I don't know where exactly to look. SecurityCheck.txt

ESET.txt

Sure. I am in the process of the ESET scan right now as well. Quarantine.zip

Neither one of them are returning. In fact, the folders that they were in are also gone, and I don't see them running in the background through task manager, which I can now check through.

OH! The issue seems to be fixed now! I don't see the files anywhere and I can extend the task manager.

Fixlog.txt

SearchReg.txt

Addition.txt FRST.txt

The virus executable still managed to reinstall itself onto the windows partition, and the problem persists.

I cannot seem to find any sort of log for the offline scan, and I believe this is because Windows Defender gets overruled by third-party antivirus. I had to manually enable Defender because of McAfee on my pc, and even then, I cannot find the log. I am attaching McAfee's log on what they found on my pc since I did the scan.

Fixlog.txt

Just as I posted my previous reply, CPU64.exe showed back up again.