Jump to content

bilago

Members
  • Posts

    12
  • Joined

  • Last visited

Reputation

0 Neutral
  1. I tried both these, and also cleared the cache of Google Chrome, and I still have the same error message:
  2. When I try to access the following location: gtav-modmanager.ddns.me I get a blocked message from malwarebytes. Ok, so I added an exclusion. The pop up no longer appears but I still get in chrome: "Unable to access the network ERR_NETWORK_ACCESS_DENIED" That domain redirects to the following: http://bluefruitgaming.co.uk/bilago/So I try to go there directly and I get: "Unable to access the network ERR_NETWORK_ACCESS_DENIED" I don't get a popup from malwarebytes but I add an exclusion anyway. This does not change the error message. I then turn off malware web protection and it works perfectly fine. Here is a screenshot of my exclusions. What do I need to do to fix this? I am a premium user.
  3. This website is a false positive, I know because I'm the owner of the site. It's really strange however, when I type hxxp://gameswithenemies.comwith web protection on, I get ERR_NETWORK_ACCESS_DENIED in Chrome, but no message from malwarebytes that a website was blocked. I tried adding the website to the exclusion list, with no avail. The only way to get it to work is to turn off web protection entirely and restart chrome. Please fix this Thanks
  4. You really should do fact checking before making claims for other companies and "what they support". If you honestly dont think M$ supports Symlinking, go ahead and take a look at http://msdn.microsoft.com/en-us/library/windows/desktop/aa365680(v=vs.85).aspx The symlinks are only there for badly programmed software that look for hard C:\ paths. All two folders that are moved off drive C:\ are done via registry changes. I could delete all the symlinks right now, and windows will function perfectly. The reason the logs show that rules.ref is on Drive D:\, is because I moved the reference of programdata in the registry as a test to see if MBAM didn't like its current location of c:\programdata You're making it quite clear that you lead a very close minded approach to Windows and to troubleshooting for this company, which is not much of an issue since this site is geared towards malware removal, not Development support. The fact that MBAM isn't touching a single symlinked folder and that the issue only happens once real-time file protection is enabled, that there is a pretty major design flaw in the development of this software, as the one on one agent has even stated himself. You might as well be blaming my Bluetooth mouse at this point. I understand that some of you are volunteers helping out, and you deal with a lot of users on here who cant navigate their own way outside of a web browser. Even still, solutions such as "reinstall windows", "stop doing 'xxxx' because I don't understand how it works" isn't troubleshooting. I gave very specific, reproducible steps that causes an error with the software. At this point this thread just needs to be directed to someone who can note this as a software bug and create a ticket with development to investigate.
  5. A quick google for " 93.115.83.250" shows that IP for Freevpn.me ... If you're using freevpn.me willingly then perhaps mbam's web filter needs to whitelist that IP. if you're not using that VPN knowingly, then you are indeed infected with something redirecting traffic through that VPN service.
  6. Thanks for your feedback. Perhaps you don't see the benefit of segregating your OS files from Your documents and programs, but that debate isn't going help figure out the source of the issue with MBAM. To clarify, MBAM is 100% residing on my Hard disk C:\. I'm also aware of those Event logs... none of them indicate any real issue... 3/4/2014 8:16:32 AM, Error: Service Control Manager [7023] - The Peer Name Resolution Protocol service terminated with the following error: %%-2140995069 3/4/2014 8:16:32 AM, Error: Service Control Manager [7001] - The Peer Networking Grouping service depends on the Peer Name Resolution Protocol service which failed to start because of the following error: %%-2140995069 3/4/2014 8:16:32 AM, Error: Microsoft-Windows-PNRPSvc [102] - The Peer Name Resolution Protocol cloud did not start because the creation of the default identity failed with error code: 0x80630203. That is because I have disabled homegroups 3/4/2014 7:55:35 AM, Error: Service Control Manager [7023] - The WinDefend service terminated with the following error: %%-2147024894 3/3/2014 8:21:51 PM, Error: Microsoft-Windows-WindowsUpdateClient [20] - Installation Failure: Windows failed to install the following update with error 0x80070643: Definition Update for Windows Defender - KB915597 (Definition 1.167.838.0). That is because I have Windows defender turned off. 3/4/2014 7:55:34 AM, Error: Service Control Manager [7026] - The following boot-start or system-start driver(s) failed to load: iZ3DInjectionDriver That is because I turned off the iZ3D device driver (third party 3d video conversion software) 3/4/2014 10:37:21 AM, Error: Microsoft-Windows-DistributedCOM [10016] - The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8BC3F05E-D86B-11D0-A075-00C04FB68820} and APPID {8BC3F05E-D86B-11D0-A075-00C04FB68820} to the user Bill-PC\Guest SID (S-1-5-21-1338594204-595557290-1314017537-501) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool. That is because I set extremely strict Group policy restrictions for the guest account (helps prevent people from getting my computer infected) Note: The issues I have with MBAM are on the admin account, not the guest. 3/3/2014 11:48:08 AM, Error: Service Control Manager [7000] - The MBAMScheduler service failed to start due to the following error: The system cannot find the file specified. 3/3/2014 10:41:26 AM, Error: Service Control Manager [7000] - The MBAMService service failed to start due to the following error: The system cannot find the file specified. That is probably left over remnants while going to and from MBAM 2.0 I have no problems or have to do any special maintenance on my system... Every piece of software I've run - new or legacy works great, but MBAM... The tone of your reply , and the reply of the one on one agent seem to be grasping for excuses to not help resolve the issue. Windows natively runs multiple symlinks by default on the Windows Operating system (WinSXS is a great example). To point to irrelevant event logs and point to the use of different partitions to store different types of data seems to be more of a brush off than actual troubleshooting.
  7. I'm not quite clear on the reasoning to lead you to conclude that I'm "Installing and using the product in an unsupported fashion". If i'm not installing the program to a symlinked directory, and the definition file (rules.ref) is also not being stored on a symlinked directory, how can that difference have any relevance to the issue that when MBAM is launched via the File Protection module icon in the system tray, it fails to validate the current definition file? For clarity of my issue I created a separate thread as suggested by a member here. That post includes all of my log files.
  8. To clear up your confusion: Yes, I created a new Topic based off that other thread as you suggested... Yes I reverted back to 1.75 since I have more issues than a corrupt database with the beta Yes, I have a ticket with help desk, but the agent is trying to defer me to this forum instead of one on one help Yes, The agent asked me to run ComboFix on my computer. I re-ran all the scans. These reflect my current system setup. Let me know if there is any other clarifications you need. Addition.txt attach.txt CheckResults.txt dds.txt FRST.txt
  9. My appologies. I forgot that I installed 2.0 as a "fix" to my 1.x issue before I ran those scans. The issue I'm having is with 1.x . My apologies for the confusion.
  10. All logs are attached. I've narrowed the issue down to a single, reproducible problem. If I try to launch MBAM's GUI from the system Tray Icon. (the one that shows up when you enable realtime protection), it says my database is corrupt or missing. If I launch MBAM's GUI directly from MBAM.exe, or its respective shortcut on my desktop, it works fine. At first I thought the Onclick() event associated to the system tray icon was causing my rules.ref to delete, however upon setting rules.ref to read-only, the file remains yet I still get a "Corrupt or Missing" error message. This test makes me conclude that this method of opening MBAM's GUI starts the program in a way that cannot read my rules.ref file. My system is slightly modified, but I don't see how this could be related. I symlinked my program files (x86) folder to D:\ . I installed MBAM to C:\MalwareBytes\ as a precaution which does not resolve the issue. ComboFix.txt dds.txt attach.txt
  11. I already have all these logs while working with Support one on one (only help i was given was a direction to this thread), I can post them in a new thread though. Thanks.
  12. I know this is a year old.. but I'm having the same issue and I also symlinked program files from C: to D: However my registry already had the path change to D: If I run the GUI from mbam.exe, I do not get a corrupt database message, but if I open the program from the system tray icon, I do. I tried to set rules.ref and database.conf to read-only... and I still get the corrupt error message, but they do not delete. So it seems that the issue isn't that its being deleted, therefor its giving an error message, but instead the Onclick() event tied to the system tray icon launches the program in a way that thinks that the current rules.ref is corrupt. If someone from the MBAM team could supply me with the onclick() event tied to the system tray icon for further troubleshooting would be greatly appreciated.
Back to top
×
×
  • 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.