LinkinForcer
-
Posts
36 -
Joined
-
Last visited
Content Type
Events
Profiles
Forums
Posts posted by LinkinForcer
-
-
Hello,
Today during a scan Malwarebytes detected Launchbox.dll as malware.ai. I just scanned my computer two days ago without issue. Launchbox has not been updated since. I'm guessing this is a false positive. What are your thoughts?
-
Hello,
I ran a scan of my computer with AdwCleaner and this popped up.
Is it a false positive? I know I have had to tell Malwarebytes to ignore a few files I have used to mod some video games I have. The files are safe but Malwarebytes doesn't like them. I'm not sure if this registry key has anything to do with them or not.
Any help would greatly be appreciated!
The following is what comes up on the AdwCleaner detection, I've also attached an image of the detection:
PUP.Optional.Legacy
Registry Key:
HKLM\Software\Wow6432Node\\Classes\CLSID\{8BF0126F-A5B7-4720-ABB2-2414A0AF5474}
-
Just an update guys, the Malwarebytes Adwcleaner seems to have done the job. It found 3 items. One was a registry key that was quarantined and the other two were the ask and aol toolbars from Google Chrome. It cleaned the items and now nothing shows on the scan with ESET. I'll do another test later and post the results before I go to bed.
-
Yeah that’s no problem. Like I said I don’t use Chrome for anything really. I only had installed to take advantage of one of their plugins.
-
Im honestly thinking about uninstalling Google Chrome all together. Only reason I installed it was to use VidIQ.
-
-
It shouldn’t have been a third party installer. As a matter of fact I have no idea where these files came from. The file path leads back to the MBAM services folder inside the install directory for Malwarebytes which is even more confusing.
I’ll use the program you listed and see if it works.
-
Hey guys,
So today I ran a scan with ESET and I constantly get 3 warnings everytime. One is for Win32/SmartFileAdvisor.B potentially unwanted program and the other two are for Win32/Bundled.Toolbar.Google.D potentially unsafe program. They are all tied back to the MBAM Service that is run by Malwarebytes. Even after cleaning them and ESET reporting that they were cleaned by deleting them they seem to get caught again by ESET during another scan after a restart or after shutting the computer down and then turning it back on.
Are these files false positives? They didn’t show up until after I installed Google Chrome from what I can tell.
Any advice on this matter will be greatly appreciated!
Note: A full scan with Malwarebytes comes up clean.
-
Updated and removed file from exclusion. Scanned both the folder and file 3 times. All is good! Thanks for the fast fix!
-
OK after I restored it and excluded it. GeForce Experience is working 100% again!
-
Be quick when excluding it because it will grab it again lol For some reason they had it listed twice in my quarantine.
-
OK Thanks!
-
I've got the original file. I'm going to put it back onto my pc and exclude it and see what happens. Or do you guys think I should just leave it be for now?
-
Thank God I'm not the only one!
-
OK so I was just sitting at my computer and had been for a while. I wasn't surfing the web or anything as I was doing other things. I got an alert that Malwarebytes had quarantined a Trojan. It asked me to restart the computer to complete the removal of the malware so I did. When I looked at the log it told me that a file named Ontology.dll was the culprit and labeled it as a Trojan.Crypt. I just ran a full scan thew other day and everything was fine. NVIDIA has not updated in a while for me so its not like I updated the drivers or programs that use the graphics card.
End result is that Ontology.dll is no longer on my computer but Im thinking this could have been a false positive as it is part of the NVIDIA software.
Does anyone have any information on this?
-
Ah OK....I'm in the US....I just didn't get it for some reason. I'm super tired. Sorry guys lol
-
Oh lol OK. So is that like a thumbs up or did I do something wrong or what?
-
Sorry I'm on my phone maybe it's not showing for me? Is it a picture or something?
-
What that mean?
-
Well I just realized that I was still running 3.1 so I updated to 3.2. So far so good.
-
Hey guys,
So today I opened malwarebytes to run a scan as I do every so often. When I did it was like my lifetime license was deactivated. Only thing is it was fine yesterday. I went ahead and reentered the license info and everything activated. I clicked on update as it stated it needed an update. When I did that it opened my web browser and took me to a page to renew my license. I found this odd as I have a lifetime license so I closed the browser and saw that malwarebytes had updated and I ran a scan which came back fine.
Does anyone know why this happened? Was this just a glitch in the software?
-
Yes it does. Thank you for your response.
-
Trust me I have a true anti-virus as well. My only concern was the scan time and number of files it was scanning. It takes less time and scans less files that my AV.
I just want to make sure that it is operating normally and that it's supposed to scan less files than what I was use to in the previous version of MBAM.
-
Ok I know that 3.0 is scanning faster as a feature but I just want to make sure that it's working properly.
If I run a custom scan with all boxes checked off on the left and all my hard drives checked off it takes about 30 minutes to complete that scan.
I remember it used to take around an hour and 30 minutes. Just wish I could remember how many files it scanned. It's scanning around 450,000 files for me. My anti-virus scans millions of files on a custom scan.
I know that they are different programs but should malewarebytes scan millions of files as well like my anti-virus does? Again I am doing a custom scan with all boxes checked off on the left and all my drives selected.
LaunchBox.DLL False Positive?
in File Detections
Posted
I was just able to check this thread. Sorry I couldn't get back earlier.
@saw-ny that is the exact issue I had with mine.
Since they have uploaded everything I'll wait for a response to this thread.