Author Topic: Really weird computer virus  (Read 1955 times)

No we shouldn't, we don't need the source of where the virus came from, we need to get rid of it lol
Think of it as a secondary task, helping johnny to identify what is and isn't safe to download to avoid problems in the future rather than just focusing on the current problem


Try malwarebytes.
Read the OP
helping johnny to identify what is and isn't safe to download to avoid problems in the future
I think Johnny knows, he probably just got unlucky. Happens to the best of us.



did you try malwarebytes

is the bug thing back again
after like 4 years of being dead

How do you even forget up this bad tho

Everyone is telling him to use Malwarebytes and the most recent versions of Malwarebytes now have Free Features gutted into the paid version.
Its more of a one use trial now.

I mean it should do the job but its not as good as it was.

If that doesn't work try rouguekiller, its a open source av, antimalware, and antispyware solution that gets rid of stuff even if it has to delete important .dlls, at the expense of restoring them with clean copies.

Also it kind of is important to know where that stuff came from so you can file a complaint with IC3 and get the stuff taken down and the creators of whatever the forget that was sued into oblivion.

Run Kaspersky Rescue Disk or something alike.


The startup tab on task manager has programs called Cpx, Msrtn32, and SpaceSoundPro. They look pretty suspicious. I disabled them, can't seem to do anything else. The only suspicious thing in Roaming is an empty folder named c, modified today. In AppData, there's a file named Local剜捯獫慴⁲慇敭屳呇⁁屖湥楴汴浥湥⹴湩潦. Should I delete it? Last modified yesterday though.

That's from GTA V for some reason, I have it too.

That's from GTA V for some reason, I have it too.
wtf cret get off his computer!!!

No we shouldn't, we don't need the source of where the virus came from, we need to get rid of it lol
It's important to identify the type of virus so we can verify if it's been removed properly by checking the existence of related programs and registry values.


since that's windows 10 i honestly believed the bluescreen
i know the way it looked changed between 7 - 8 so i could easily assume it changed again