Jump to content


Honorary Members
  • Posts

  • Joined

  • Last visited


0 Neutral

Profile Information

  • Location

Recent Profile Visitors

8,606 profile views
  1. Hi @Porthos, You're certainly right; in this case it really would be "at own risk" as the last update was .....
  2. Hi, I have already mentioned this in a previous topic (sorry, couldn't find it back right now): I see that Cyberfox is still listed here but this browser doesn't exist anymore (since quite a long time now) ... Thank you.
  3. Hi @exile360, Thanks a lot for this detailed and useful explanation. Just for info, I made the following test: uninstalled MB with the Support Tool (without new installation after the reboot), installed the latest stable version with the online installer, updated to the latest beta version. This time program and CU were updated at the same time (meaning: in one step), no reboot required. Again, thanks for your time ...
  4. I guess I wasn't clear enough in my first post; here more explanations ... In previous versions, the updates happened in 2 steps as described in this topic: https://forums.malwarebytes.com/topic/260121-update-to-version-41171-cu-10927/?tab=comments#comment-1386375 This time it all happened in one step through a required reboot. So my question is: will this be the standard procedure from now on ? Thank you.
  5. Hi @exile360, Do you have any thoughts about my question in the first post ? Thank you !
  6. I tested it and no problem here (result is 0x1) as you can see from the screenshot.
  7. @boombastik, Can't give you an answer on this because I have "Fast startup" disabled (as I'm using an SSD) ...
  8. Hi, Installed on top of the previous version without any problem. I noticed a new intermediary window (proposition to install MBG); to end the installation a reboot was required and after that I noticed that, this time, the program and the CU were updated at the same time. This wasn't the case with previous versions but I suppose that this will be now the new procedure (?) ... Just asking ... - Win10 20H2 - Build 19042.572 -
  9. And it was the case in the past; the mention "Beta" was present just after"Premium" in the title bar (that's why I included the screenshot in my first post). If I remember well it was still present in the beta versions 4.0 and got lost with the beta versions 4.1 .....
  10. I agree with you ..... but ..... it should normally be mentioned somewhere .....
  11. Hi, Running MB Premium - CU 1.0.955 which is a beta version but there is no mention of it in the main title bar (see screenshot) ...
  12. throkr

    False positive

    The following site is blocked: www.info-coronavirus.be Please review as this is an official site from the Belgian Government. Thank you.
  13. @LiquidTension, anything new concerning this issue ? ..... Thank you.
  14. I understand that; my point is (was) that a reader of this report could think that it was made with ransomware protection enabled (which isn't the case), unless I tell him that I disabled the protection whilst MBST was running ..... Or am I missing something here ? My external HDDs are connected but not always running (= powered ON) and not visible in File Explorer. After running MBST, if I make them visible again in File Explorer (by turning the power switch on the HDD to ON), I see that the drive letter has been changed. BTW today I made a test: I left the HDDs ON (visible in File Explorer) whilst running MBST and this has the same effect; once you set the HDD to OFF and again to ON, the drive letters in File Explorer are changed. Attached you'll find the logs, except the Process Monitor Log (apparently not allowed, file to big) so I uploaded it here: https://www.transfernow.net/Ba0joK062020 Here you go (no child processes present) MB ARW + LOGS.zip mbst-grab-results.zip
  15. @LiquidTension The new beta CU 1.0.931 did not fix this issue; ransomware protection still has to be disabled before starting the tool to have the zip file created with the correct infos (*) (this is important !). I have now more important infos for you: with 1.0.931: if you rerun MBST after a first complete execution (with ransomware protection disabled), you'll still have to disable ransomware protection (this wasn't the case with CU 1.0.927, as we saw earlier) if you don't disable ransomware before starting the tool, it gets stuck at the second step "Run FRST" (as I mentioned it earlier in this topic). If you disable ransomware protection whilst the tool is stuck (= still running), it will immediately go further and the logs are created (*) BUT they are incorrect as they don't reflect the reality: in mb-checkresults.txt, under ARW Controller Config it says Protection State: enabled (which is wrong as the protection was disabled whilst MBST was running). My attached logs reflect this "wrong" situation. After running the tool, I noticed that all the drive letters of my non-connected (position "OFF" during the scan) external HDD drives were changed (this doesn't affect USB drives, at least for me). This is important as I use one of these external HDD drives for my backups ... Well, I hope that my explanations are clear enough and that it will help ..... mbst-grab-results.zip
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.