Jump to content

Recommended Posts

The latest version of Malwarebytes Home seems to be incompatible with the Windows 10 Insider Preview Build (18323-19H1).

All services except Exploit Protection are turned off and you can't turn them back on.

Restart does nothing.

Uninstall hangs until one of the Malwarebytes processes is manually terminated. Re-install works then the services turn themselves off again seconds later.

Anyone else having this issue?

Share this post


Link to post
Share on other sites

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes 3 Help forum.

 

If you are having technical issues with our Windows product, please do the following: 

Spoiler

If you haven’t already done so, please run the Malwarebytes Support Tool and then attach the logs in your next reply:

NOTE: The tools and the information obtained is safe and not harmful to your privacy or your computer, please allow the programs to run if blocked by your system.

  1. Download Malwarebytes Support Tool
  2. Once the file is downloaded, open your Downloads folder/location of the downloaded file
  3. Double-click mb-support-X.X.X.XXXX.exe to run the program
    • You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Click Yes to consent.
  4. Place a checkmark next to Accept License Agreement and click Next
  5. You will be presented with a page stating, "Get Started!"
  6. Click the Advanced tab
    Repair menu_arrows.png
     
  7. Click the Gather Logs button
    Advanced_arrows.png
     
  8. A progress bar will appear and the program will proceed with getting logs from your computer
    Advanced Gather Logs_arrows.png
     
  9. Upon completion, click a file named mbst-grab-results.zip will be saved to your Desktop. Click OK
    Advanced Gather Logs completed_arrows.png
     
  10. Please attach the file in your next reply. Before submitting your reply, be sure to enable "Notify me of replies" like so:
     notify me.jpeg  

Click "Reveal Hidden Contents" below for details on how to attach a file:
 

Spoiler

To save attachments, please click the link as shown below. You can click and drag the files to this bar or you can click the choose files, then browse to where your files are located, select them and click the Open button.

mb_attach.jpg.220985d559e943927cbe3c078b
 

One of our experts will be able to assist you shortly.

 

If you are having licensing issues, please do the following: 

Spoiler

For any of these issues:

  • Renewals
  • Refunds (including double billing)
  • Cancellations
  • Update Billing Info
  • Multiple Transactions
  • Consumer Purchases
  • Transaction Receipt

Please contact our support team at https://support.malwarebytes.com/community/consumer/pages/contact-us to get help

If you need help looking up your license details, please head here: https://support.malwarebytes.com/docs/DOC-1264 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

Share this post


Link to post
Share on other sites

Hello @Kabutocub and :welcome:

Do you have the ability to do a fallback to Windows 10 Insider Preview Build 1903's 18317?

If so, that may be that system's temporary resolution till a Malwarebytes Staffer/Developer can weigh in.

Please reply with a mbst-grab using post #2 above before you fallback.

Thank you.

cc: @tetonbob @LiquidTension @AdvancedSetup

Edited by 1PW

Share this post


Link to post
Share on other sites

Experiencing the same issue on my Insider Build test machine with Windows 10 Insider Preview Build (18323-19H1) for Windows 10x64 PRO.

Used the mb-support tool to fully remove MBAM.  An attempt to re-install fails with a statement by the MBAM installer that the Anti-Rootkit DDA driver cannot be installed and to reboot.  MBAM restarts but all protection is off.  On reverting it to the Free version, it will scan okay.  Will submit a mbst-grab shortly.

 

mbst-grab-results.zip

Edited by siliconman01
Added mbst-grab-results

Share this post


Link to post
Share on other sites

Hello @siliconman01:

If you have the ability to fall back to 18317, would you?

Thank you for the mbst-grab.

Share this post


Link to post
Share on other sites
7 minutes ago, 1PW said:

Hello @siliconman01:

If you have the ability to fall back to 18317, would you?

Thank you for the mbst-grab.

Sorry...have already locked in 18323.  Cleaned out previous version.

Share this post


Link to post
Share on other sites

I can't roll-back either. Had to uninstall MBytes for the time being. Monitoring this thread and other forums until I can download an updated version.

Share this post


Link to post
Share on other sites

@Kabutocub  Did the issue occur prior to installing 18323 (19H1)?

@siliconman01 Thank you for the logs. Please carry out the Process Monitor instructions below and provide the generated file.

MgeHyNE.png Run Process Monitor

  • Please download run_procmon.bat using the link below.
    https://malwarebytes.box.com/s/he92cwwd71sa0w7waiub8wx69ymb5d4i
  • Open your Downloads folder.
  • Double-click CX41PDv.png run_procmon.bat. Click Yes if prompted by AVOiBNU.jpg User Account Control.
  • Note: If you are prompted by Windows SmartScreen, click More info followed by Run anyway.
  • A black Command Prompt window will appear.
  • When prompted to carry out the tasks, please do the following:
    • Try to launch Malwarebytes and wait for the DDA Driver error.
    • Don't click Yes to restart.
  • Once done, click inside the Command Prompt window and press Y on your keyboard followed by Enter.
  • Upon completion, a file named HSPwQfy.png procmon-log.zip will be saved to your Desktop. Please attach the file in your next reply.
  • Note: If the file is too large, you will be provided instructions to upload the file to a file hosting website (wetransfer.com).

Share this post


Link to post
Share on other sites

Same issue here and MBAM was fine on previous release 18317.  So something has changed causing this issue.  Have other applications installed for protection as well so will wait for fix.

Share this post


Link to post
Share on other sites
3 hours ago, LiquidTension said:

@Kabutocub  Did the issue occur prior to installing 18323 (19H1)?

@siliconman01 Thank you for the logs. Please carry out the Process Monitor instructions below and provide the generated file.

MgeHyNE.png Run Process Monitor

  • Please download run_procmon.bat using the link below.
    https://malwarebytes.box.com/s/he92cwwd71sa0w7waiub8wx69ymb5d4i
  • Open your Downloads folder.
  • Double-click CX41PDv.png run_procmon.bat. Click Yes if prompted by AVOiBNU.jpg User Account Control.
  • Note: If you are prompted by Windows SmartScreen, click More info followed by Run anyway.
  • A black Command Prompt window will appear.
  • When prompted to carry out the tasks, please do the following:
    • Try to launch Malwarebytes and wait for the DDA Driver error.
    • Don't click Yes to restart.
  • Once done, click inside the Command Prompt window and press Y on your keyboard followed by Enter.
  • Upon completion, a file named HSPwQfy.png procmon-log.zip will be saved to your Desktop. Please attach the file in your next reply.
  • Note: If the file is too large, you will be provided instructions to upload the file to a file hosting website (wetransfer.com).

The zipped Procmon file is 126 mbytes.  Please provide wetransfer.com upload instructions

Edited by siliconman01
request for wetransfer.com instructions added

Share this post


Link to post
Share on other sites

FYI:  Eight topics submitted to the Feedback Hub regarding the latest Windows Insider Build 18323 and  the missing MBAM Anti-Rootkit DDA Driver with only Exploit Protection working and all other options "locked" off.  As with everyone else reporting, Malwarebytes Premium was working perfectly until restart completing the Build installation.  (Encouraging Upvoting the issue in the FBH so the Microsoft Developers will see that something they likely did caused the issue.)

Edited by Corrine

Share this post


Link to post
Share on other sites

For what its worth, bug being researched by Microsoft: 

 

Share this post


Link to post
Share on other sites

Thanks Corrine.  I've been tracking this issue as well and have seen several threads and reports from several users with this issue with the Insider Preview build and it does indeed appear to be an issue with the new build preventing Malwarebytes from installing drivers based on the logs and reports I've analyzed so far.

Share this post


Link to post
Share on other sites

@Kabutocub, @siliconman01

Hi there, I'm having the exact same issue here and tried all the previously stated fixes:

Web protection:                        off
Exploit protection:                    on
Malware protection:                off
Ransomware protection:        off

Windows 10 Pro x64, Build 18323.19H1 release190119-1759

Malwarebytes version: 3.6.1.2711
Component package version: 1.0.527
Update package version: 1.0.8970

Here are the log files: mbst-grab-results.zip

Ran run_procmon.bat and procmon-log.zip is 314Mb so please advise how to upload it thanks.

 

Share this post


Link to post
Share on other sites

Please upload the file to WeTransfer.com, selecting the Send as link option (click the round ... button) and then provide the link it gives you once the upload is complete.

Thanks

Share this post


Link to post
Share on other sites
9 minutes ago, exile360 said:

Please upload the file to WeTransfer.com, selecting the Send as link option (click the round ... button) and then provide the link it gives you once the upload is complete.

Thanks

@exile360 Thanks for the info. Uploading, 57 minutes to go...will post link when it completes.

Share this post


Link to post
Share on other sites

Excellent, thanks to both of you for providing the logs.  I know such large uploads can be tedious (particularly since I'm on a DSL internet connection myself with a 100Kbps upload speed).

Hopefully they'll give the Developers a clue as to the root cause of this issue.

Share this post


Link to post
Share on other sites

I opened a ticket ( 2522848 ) yesterday about this problem, after running the support tool, which I understand collected some data and transmitted it to Malwarebytes. and offered to create a ticket. If someone is working on that it may be worthwhile consolidating the efforts.

Share this post


Link to post
Share on other sites
52 minutes ago, lmod said:

I opened a ticket ( 2522848 ) yesterday about this problem, after running the support tool, which I understand collected some data and transmitted it to Malwarebytes. and offered to create a ticket. If someone is working on that it may be worthwhile consolidating the efforts.

Yes, the Support team has been made aware of this issue as have the members of the Product team so they will definitely collect all of the reports and information that has been provided for analysis.  Thank you for your help with this, and that goes for all of those who have reported on this issue.  I hope that it may be resolved soon, but I suspect that action may be required on Microsoft's end to correct the issue completely so hopefully they will take action on this issue as it has been reported to them by several individuals already and I'm sure that Malwarebytes will reach out to them directly if necessary as well.

Share this post


Link to post
Share on other sites

You're very welcome, I'm just sorry that your protection has been compromised by this issue, but hopefully a resolution will be forthcoming.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • 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.