no disk in the drive msg when icon clicked mbam.exe 3.3.1.2183

[Mhyrr]

11/11/2017
after new installation of mbam.exe, version on Windows 7 -- today, error message when icon on desktop clicked:
mbam.exe - No Disk
There is no disk in the drive.  Please insert a disk into drive \Drive\Harddisk2\DR2 ***** cancel, continue, try again, I hit try again ,Malware opens to new version updated today.  Is this really how I have to open it each time?

malware version 3.3.1.2183
comp. pkg ver 1.0.236
update pkg ver 1.0.3233

 

[pmcjr]

This is happening to me also. It's always a leap of faith for me to  install a new version when the previous version is working fine.  But I did it anyway this evening.  Installed 3.3. The "no disc drive" error doesn't appear every time...say 1 out of 3 times.  I open MBAM by clicking on the icon in the task bar.  Now, with 3.3, in addition to opening MBAM, it also opens another MBAM icon in the task bar.  When I close MBAM, this second icon goes away.  It didn't do this with 3.2.  I"ll ask you same question...is this the new normal with 3.3?

[pmcjr]

21 minutes ago, pmcjr said:

This is happening to me also. It's always a leap of faith for me to  install a new version when the previous version is working fine.  But I did it anyway this evening.  Installed 3.3. The "no disc drive" error doesn't appear every time...say 1 out of 3 times.  I open MBAM by clicking on the icon in the task bar.  Now, with 3.3, in addition to opening MBAM, it also opens another MBAM icon in the task bar.  When I close MBAM, this second icon goes away.  It didn't do this with 3.2.  I"ll ask you same question...is this the new normal with 3.3?

Update to above...after unpinning MBAM icon from task bar and repinning it, I no longer get the second icon when opening MBAM.  I still occasionally get the "no disc in drive" error popup. This goes away by clicking on Cancel or Try Again and you then have to click on the MBAM icon again.  If it matters, I installed 3.3 by clicking install on the "new update available" popup above the system tray.  So, I installed over 3.2 and did not do an uninstall of 3.2.  Everything else appears to be OK.  All of the Real Time Protections stayed on, my Exclusions are still there as is my scan schedule.

[dcollins]

Can you try gathering a Procmon log of this issue? The instructions below should help clarify what we need:

1. Download Procmon from https://live.sysinternals.com/procmon.exe
2. Launch Procmon and accept the EULA
   • If you've ran Procmon before, you'll get a message about filters. Click Reset and then Ok
3. You should see a lot of data filling up the screen, if not, click the magnifying glass at the top
4. Leave Procmon running and open up mbam.exe
5. If the error doesn't happen, close mbam.exe and repeat the process
6. Once the issue occurs, click the Save button in Procmon and upload the pml file that it creates (you may need to zip it up)

[pmcjr]

47 minutes ago, dcollins said:

Can you try gathering a Procmon log of this issue? The instructions below should help clarify what we need:

1. Download Procmon from https://live.sysinternals.com/procmon.exe
2. Launch Procmon and accept the EULA
   • If you've ran Procmon before, you'll get a message about filters. Click Reset and then Ok
3. You should see a lot of data filling up the screen, if not, click the magnifying glass at the top
4. Leave Procmon running and open up mbam.exe
5. If the error doesn't happen, close mbam.exe and repeat the process
6. Once the issue occurs, click the Save button in Procmon and upload the pml file that it creates (you may need to zip it up)

Devin Collins....I shouldn't have to do this.  Maybe Mhyrr will do it.  Surely, this problem is known to MBAM.  Is it?  The error message is hit and miss and doesn't seem to be affecting MBAM features.  I can live with it and wait for you to include a fix in the next component package.  This is what the error popup looks like....What does it mean?

These unexpected problems seem to occur when I download and install and update instead of waiting for the metered updates.  I've said this before, but next time I will.  I feel like the early adopters are really doing your Beta testing.

Win 7, MBAM 3.3.1.2183, Comp Package 1.0.236, Update 1.0.3238

 

[dcollins]

@pmcjr you're right, you shouldn't have to do it, but none of our testing is able to reproduce this, which is why need help from the people experiencing the issue to be able to resolve it.

Another thing that may help is to grab FRST and mb-check logs as outlined below

 

 

[pmcjr]

Devin Collins...OK the FRST sounded easier than your first request.  Here it is.  Is this what you wanted?  Thank you for spending a Sunday afternoon helping us.  Anxious to get your response re: a MBAM fix for this problem.  Regards.

mb-check-results.zip.

[dcollins]

Thanks @pmcjr. Nothing really jumps out in those logs directly, but we've seen some issues with AVAST and other AV programs not liking having us registered with Windows Action Center. Can you open Malwarebytes and go to Settings -> Applications, then scroll down to the Windows Action Center section and set Malwarebytes to "Never register with Windows Action Center". I don't think this will solve the issue, but at this point, it's the first place I'd start until we can reproduce this in house

[pmcjr]

32 minutes ago, dcollins said:

Thanks @pmcjr. Nothing really jumps out in those logs directly, but we've seen some issues with AVAST and other AV programs not liking having us registered with Windows Action Center. Can you open Malwarebytes and go to Settings -> Applications, then scroll down to the Windows Action Center section and set Malwarebytes to "Never register with Windows Action Center". I don't think this will solve the issue, but at this point, it's the first place I'd start until we can reproduce this in house

@Devin Collins.....OK, I did that, but it made the problem worse.  With "never register...." set, the error message happens every time I open MBAM when clicking on the MBAM icon in the task bar and not just occasionally.  It may be worth noting, that when I open MBAM by clicking on the MBAM icon in the system tray (bottom right side of task bar) and then clicking Open, I don't believe I get the error popup.  That method seems much better if not completely better.  I switched the Windows Action setting back to let MBAM decide.  As I said, this doesn't seem to be affecting the program's features, so I'll wait for a system fix.  Regards.

[dcollins]

Ok, I don't have a W7 machine in front of me to test at the moment, but I'll see if I can reproduce the issue when I get into the office tomorrow.

[Bigplayer]

I installed the update for Malwarebytes Premium 3.3.1.2183 on November 9,2017. When I launch the program I get a message box with the message 'mbam.exe-no disk' There is no disk in the drive. Please insert a disk into drive e. with options cancel,try again or continue.

I reply cancel and the Malwarebytes program window appears. Is this due to the install not not completing properly or some other reason?

I feel that something is wrong,however I have no idea what the problem may be. Does anyone have a answer to this situation? 

Edited November 13, 2017 by Bigplayer

[dcollins]

@Bigplayer we are researching the issue. If possible, can you please provide the information I asked for above?

10 hours ago, dcollins said:

Can you try gathering a Procmon log of this issue? The instructions below should help clarify what we need:

1. Download Procmon from https://live.sysinternals.com/procmon.exe
2. Launch Procmon and accept the EULA
   • If you've ran Procmon before, you'll get a message about filters. Click Reset and then Ok
3. You should see a lot of data filling up the screen, if not, click the magnifying glass at the top
4. Leave Procmon running and open up mbam.exe
5. If the error doesn't happen, close mbam.exe and repeat the process
6. Once the issue occurs, click the Save button in Procmon and upload the pml file that it creates (you may need to zip it up)

If not, if you could at least grab the logs mentioned in the following thread, that could help us as well

 

[pmcjr]

Devin Collins...any feedback yet on this?  Does it look like a system or 3.3 problem, Win 7 specific, or just individual bad luck for those of us experiencing this issue?  Regards.

[dcollins]

Not yet, so far we haven't been able to reproduce this. Would you mind right clicking your desktop icon, choosing Send to -> Compressed (Zipped) folder and uploading the zip file it creates?

[pmcjr]

1 hour ago, dcollins said:

Not yet, so far we haven't been able to reproduce this. Would you mind right clicking your desktop icon, choosing Send to -> Compressed (Zipped) folder and uploading the zip file it creates?

Devin Collins...I'm not sure what this gives you, but is this what you wanted?

Malwarebytes.zip

[dcollins]

I just wanted to make sure the shortcut properties didn't get messed up for some reason, but they look fine.

Does the same issue happen if you use the shortcut in your start menu to open Malwarebytes?

[pmcjr]

5 hours ago, dcollins said:

I just wanted to make sure the shortcut properties didn't get messed up for some reason, but they look fine.

Does the same issue happen if you use the shortcut in your start menu to open Malwarebytes?

Devin Collins...I didn't have it in the start menu, but I added it and, YES, it does still happen.  So, you get this disc error message if you click on the MBAM program in Start Menu>All Programs,  the MBAM icon you add to the Start menu, or the MBAM icon added to the Taskbar.  In all three places, it's intermittent.  The only place it doesn't appear to happen is if you open MBAM via the icon in the system tray.  As I've said, this doesn't appear to be affecting the MBAM program in ways that I can tell, but it is a weird program glitch.  It will be an annoyance removal if it can be resolved.  Regards.

[Boss281]

I have the paid version, doing this on all my machines (randomly).  Both Win10 and Win7...

[dcollins]

@Boss281 can you please provide the logs I asked for above?