Jump to content

fmendoza

Staff
  • Content Count

    6
  • Joined

  • Last visited

About fmendoza

  • Rank
    New Member

Recent Profile Visitors

960 profile views
  1. fmendoza

    Update = Uninstalled

    @jgullock @Trime2x1 Thank you for reporting your issues. Can I have you both run the mb-check tool from https://downloads.malwarebytes.com/file/mb3_check and provide the mb-check-results.zip Also provide all "Uninstall Log" from your temp folder (%temp% or C:\Users\[yourusername]\AppData\Local\Temp) The uninstall logs you'll be looking for will look something like this: "Uninstall Log 2017-09-01 #001.txt" Even if you have already resolved your upgrade issue, I would like to analyze the underlying causes of your upgrade problem with these logs.
  2. Yes it seems that the Malwarebytes Beta was released when Microsoft pulled the update, and you successfully updated it when the update was rereleased. The article would best explain the cause of your issue since I've not been successful in seeing a blocked update from my testing.
  3. Thank you both for the logs. I would like to take some time to analyze the logs and run through some troubleshooting. The tests I have ran with a touchscreen laptop did not reproduce the update issue.
  4. @siliconman01 thanks for clarifying. Can you provide me FRST and mb-check logs of the computer(s) that have the issue? I have a touchscreen laptop in hand so I can give that a check. @keverne would you also be able to provide me with an FRST and mb-check log? Create and obtain Farbar Recovery Scan Tool (FRST) logs Download FRST and save it to your desktop Note: You need to run the version compatible with your system. You can check here if you're not sure if your computer is 32-bit or 64-bit Double-click to run FRST and when the tool opens click "Yes" to the disclaimer Press the "Scan" button This will product two files in the same location (directory) as FRST: FRST.txt and Addition.txt Leave the log files in the current location, they will be automatically collected by mb-check once you complete the next set of instructions Create and obtain an mb-check log Download MB-Check and save to your desktop Double-click to run MB-Check and within a few second the command window will open, press "Enter" to accept the EULA then click "OK" This will produce one log file on your desktop: mb-check-results.zip This file will include the FRST logs generated from the previous set of instructions
  5. @siliconman01 I have been looking into this issue. I have a W10 Pro 64bit Build 15063.483 VM with MB 3.2.0.1959 installed. I was not able to reproduce your issue. I did another attempt with the MB 3.2 Beta and Kaspersky Internet Security 2018 installed. I am seeing that the update was not being found on first attempt, but the next attempt to update finds the KB4032188 update. Kaspersky installed alone does cause this issue. This is interesting but I'll have to investigate more to see if this combination could be the culprit. I have a laptop with W10 Pro Build 15063.483 and MB 3.2 Beta installed. I checked for windows updates and it found and downloaded KB4032188 fine. @keverne Since you are seeing this too, do you have any other anti-virus programs running on your PC?
×

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.