Jump to content

cybot

Members
  • Content Count

    201
  • Joined

  • Last visited

About cybot

  • Rank
    Advanced Member

Recent Profile Visitors

1,161 profile views
  1. that.... that is not a steam address being used..... I don't know what that 7k7k.com is for, but I don't think it's from steam or the game that got blocked, World of Goo.
  2. this address is for Steam Content servers I.E. Game updates. Steam said their was an update for one of my games, World of Goo. But MBAM blocked the download. I tried scanning the url with virustotal, and only one site said the site was malicious, FORTINET. a check with their website, confirmed that this IP address registered as being malicious. I don't know why they think so. In order to even get anything from the steam content servers, you need to meet the following requirements: have Steam installed on your PC/MAC.Linux system registered steam account purchase a license for the game from the steam store installed steam game on the end users system. Malwarebytes www.malwarebytes.com -Log Details- Protection Event Date: 5/11/19 Protection Event Time: 4:47 PM Log File: 178b4f80-7447-11e9-8dc5-00d86104a727.json -Software Information- Version: 3.7.1.2839 Components Version: 1.0.586 Update Package Version: 1.0.10562 License: Premium -System Information- OS: Windows 10 (Build 17763.475) CPU: x64 File System: NTFS User: System -Blocked Website Details- Malicious Website: 1 , , Blocked, [-1], [-1],0.0.0 -Website Data- Category: Trojan Domain: steam.naeu.qtlglb.com IP Address: 157.185.160.14 Port: [64063] Type: Outbound File: E:\Program Files (x86)\steam\Steam.exe (end)
  3. don't suppose you or the MBAM dev team would be willing to reveal what the bug that seemingly everyone was having was that was triggering the popup?
  4. Using Windows 7 Ultimate SP1 x64 and MBAM 3.7.1.2839 and component pacakage 1.0.538, no freezes here. two things I could suggest though. try setting up your system so only M$ services and MBAM start up at boot and see if the freezes still occur, and also (while everything else is still loading at boot), try out the software process lasso. If it is unable to solve the issue automatically (by doing better process management that what windows is capable of doing) , it might at least point out if there is a program conflict that is causing the freeze. I originally got process lasso back when I was running win10 in 2015. but after I was forced to go back to windows 7, I have continued using it. It's a great program. *NOTE to forum mods - sorry for plugging another companies program here. Don't know what the rules on this are, so I'm apologizing just in case.
  5. I have got the messages too, here are my logsmbst-grab-results.zip mbst-grab-results.zip
  6. no I haven't. don't know what went wrong that time, maybe it was a freak, once in a million chance occurrence. subsequent upgrades have gone smoothly.
  7. I keep receiving a pop up from MBAM. it says something about helping to fix bugs, and it says to report it if the pop up happens more than once, Well, it has happened over three times now, so here I am. I ran the MBAM support tool, and it did *something* and said mbam was fixed. It would be nice in future versions - if possible, for the support tool to give details on what fixes were performed by the support tool, like maybe some sort of change log or something. anyways, I have included the gathered logs. if anything else is needed to be uploaded, "just ask and yee shall receive". mbst-grab-results.zip
  8. I can provide the exported eset smart security premium settings. I am a little reserved about doing so though.. eset smart security premium has a password manager and I don't want any of that data going out. also I have passworded the access to the settings of the program. the only changes that have been made recently to ESET was the adding of exclusions to the directories and executables that are for MBAM, but that was several months ago and at mbam support staff direction. the only recent ESET blocks come from the parental blocking which I have setup to block online advertising and sites known for spreading malicious content (jscript Trojans, drive by downloads, malware, etc....). The only recent detections have been for a non-malicious type files detected as a hacktool (it was a HEX editor that allowed editing of memory and disk contents that I was using for a school project). MBAM also detected and tried to block this software. I guess security/AV is real sensitive these days about anything that might be used to allow illegally obtained software (again, not what I was using the 'hacktool' software for) to be run. Not that that is a bad thing since the crack/hacks for illegal software often contain viruses and Trojans and the like. Anyways.... did the logs I sent contain any info on the running of the setup file that failed due to a access is denied error? I could not find it on my own when I tried too look for it. Since the esetconfig.xml could potentially contain sensitive personal data I will send it via PM.
  9. was just perusing the gathered log files and I noticed a slight error in the generated log MBST-check-results. it isn't anything major, more like a slight oversight. the log lists my primary and secondary drives as being 1Tb in size. this is incorrect. both drives are 2Tb is size. or when formatted, 1.80 and 1.81 Tb (respectively) in size. it seems the program which generates the log is either unable to detect the .80(.81) after the 1, or is rounding the size down, not up. (I was taught back in the day that when rounding, anything over 5 should be rounded up so 1.80 should be detected as 2). like I said, it isn't anything major, just an oversight or something. the percent of free space was accurate (I think), it's just the detected size of the drive.
  10. mbst-grab-results.zipmbst-grab-results.zipoops didn't see the note from liquidtension. Yes I am willing to send any log I might have. just keep in mind that the MBAM directories got emptied out during the failed setup run. this possibly includes any logs that got created during the failed setup run. I noticed that MBAM now has a link to the support tool in the settings>about tab. I also noticed the support tool now has a repair function. That's awesome! I will add that to my troubleshooting steps next time I have an issue. mbst-grab-results.zip
  11. I am no longer having any issues. I was just reporting a bug I ran into when I ran the latest version of mbam setup
  12. Windows 7 Ultimate SP1 x64 I do not need help, this is simply a report of a bug I encountered while trying to install re-install MBAM 3.6.1.2711 I booted up my system today and was told by MBAM that my real-time protection was no longer working. while running through various normal troubleshooting steps, I discovered In the system event logs, that there was an error saying that MBAM could not start real-time protection because it could not find a specified file. my system is clean and has no corruption, so knowing sometimes this happens, I decided to download the latest version from the website and do a setup upgrade/reinstall. everything was going fine until I suddenly received an error message that said "Setup was unable to create the directory "c:\programdata\malwarebytes\mbamservice". Error 5 : Access is denied." I have manually checked the directory, and the directory, if it existed originally, no longer exists, or any other file in the "c:\programdata\malwarebytes\" directory. I know for a fact that there were files there previously. I don't know why setup is unable to create files there suddenly. setup was also unable to rollback changes. this is most likely due to what ever is blocking setup from installing mbam in the first place. running setup a second time, the process succeeded, which makes me believe it was a bug in the setup software. real-time protection also started working again after setup successfully ran.
  13. between now and when I last posted, I performed a reset operation on the surface pro. I did choose to keep personal files, but all installed apps got removed. there weren't very many apps to begin with installed, so it wasn't a problem. when I went to reinstall mbam (latest version), I thought I would have to go and track down my license info, but much to my surprise, mbam was already activated with my license info. when I looked at the event viewer, there were still messages about mbam, but they were only informational, no errors, or warnings about mbam were present. If this is the solution to those 0xc00000005 and 0xc00000035 errors, this poses a problem for me and many other windows 7 OEM users, as normally we don't have the OS installation files for doing a repair or even a clean install. in my case, my only options seems to be do a factory restore, or upgrade to windows 8 Pro or windows 10 Pro (I have valid licenses for both). for now I will use what repair options I have available to see if I can get anywhere, mainly chkdsk, sfc, and dism.
  14. tried to go back to thelast version of mbam (3.3.1) that was on the surface since it did not cause any errors, but as soon as it started to update the definitions, the exploit protection turned off and the event viewer said the anti exploit service could not start because it was not a valid win32 application. I don't know if this is because of an error in the update files, or because I was using an old version of mbam.
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.