Cant select drive on custom scan

[ferris]

Using the latest version of MBAM i have uninstalled & reinstalled. I have uninstalled using the removal tool. I have created another user account but no matter what I do I cannot select the C drive to do a custom scan...Any ideas?

[Aura]

Hi ferris

Are you using a touchscreen monitor, laptop, all-in-one PC with a touchscreen, etc?

[ferris]

Its a Dell All In One touch screen. I tried using touch just now when you mentioned it and it didnt make a difference. I should note that it will allow me to select the "Q" drive which is created after installing Office Starter 2010. Also I am on WIndows 10 home x64. 

Edited February 7, 2017 by ferris

[Aura]

Sadly this is a known issue with touchscreen devices. The solution is to click elsewhere in the program window (close to the "check" buttons), or disable the touchscreen component. It should be adressed in a future release.

[ferris]

I see. Thanks for that answer. I've installed MBAM Premium on many a touch screen even recently and haven't seen that issue. I had to disable the touch screen & set a custom schedule. If I reenable it after that will it affect MBAM? thanks

[Aura]

The touchscreen only seems to be an issue when selecting drives on a custom scan. It doesn't seems to affect any other part of the program. Though I don't think this has been thoroughly investigated yet.

[ferris]

alright well you got me going so thank you for that information and your time!!

[Aura]

No problem ferris, you're welcome

[dcollins]

4 hours ago, Aura said:

The touchscreen only seems to be an issue when selecting drives on a custom scan. It doesn't seems to affect any other part of the program. Though I don't think this has been thoroughly investigated yet.

Just to clarify, our testing has shown that this will impact any checkboxes in the application. We only use checkboxes in a few locations though

[Aura]

Thanks for the clarification Devin

[ferris]

This is still an issue. With how often we use MBAM here and the increase of touchscreens this issue is becoming very annoying. Hope it gets fixed ASAP

[dcollins]

This should actually be fixed in our 3.1 beta which is available from the thread below

 

[siliconman01]

3 hours ago, dcollins said:

This should actually be fixed in our 3.1 beta which is available from the thread below

 

It is fixed on my systems with Dell P2714T touch screen monitors and also on my Surface Pro tablets.  Thanks for the fix in 3.1.1.1722 beta

Edited May 9, 2017 by siliconman01

[ferris]

thanks. ill probably start installing the beta from now on