JamminR

Seems a Jason of MB support has re-opened the case and is having me run the log gathering again. Thanks.

Your instruction looks as though it might work. That being said, 1) MB is a 'security' product that wants me to create yet one more internet account user/pass that will be stored in a publicly accessable server, in which the account will some day be hacked? (when not if) 2) and more valuable to me than 1 because, sure, yet more registrations, I'm already 45 minutes into the work of the MB support tool to get to the point where the 'submit ticket' button existed. I'd spent 15 minutes typing up my issue. It would save me much more time and frustration if I didn't have to re-do all the typing and work I'd done to get to that point if the original ticket could be re-opened. As a moderator, do you not have contacts within the company to get it re-opened?

I'd spent 45-60 minutes gathering info and using the MB support tool to first diagnose, and then submit, a support incident. This is on top of the hours I've spent before determining what I believe to be an issue with MBAMService.exe Upon clicking the submit button, I immediately get a email back saying the ticket has been closed because the email address doesn't match a subscription. I DO NOT HAVE a subscription. I bought this, what seemed to be, great product when it was still sold in boxes and had never expiring licensing. Please re-open ticket 4534820 immediately.

Hi All. Since as of this moment, Google search is now placing this topic at the top of it's results page, I felt I must post. I too have 4 reports of this "optional" PUM regarding MRT. Registry Value: 4 PUM.Optional.DisableMRT, HKLM\SOFTWARE\POLICIES\MICROSOFT\MRT|DONTOFFERTHROUGHWUAU, No Action By User, [7122], [676880],1.0.10470 PUM.Optional.DisableMRT, HKLM\SOFTWARE\POLICIES\MICROSOFT\MRT|DONTREPORTINFECTIONINFORMATION, No Action By User, [7122], [676881],1.0.10470 PUM.Optional.DisableMRT, HKLM\SOFTWARE\WOW6432NODE\POLICIES\MICROSOFT\MRT|DONTOFFERTHROUGHWUAU, No Action By User, [7122], [676880],1.0.10470 PUM.Optional.DisableMRT, HKLM\SOFTWARE\WOW6432NODE\POLICIES\MICROSOFT\MRT|DONTREPORTINFECTIONINFORMATION, No Action By User, [7122], [676881],1.0.10470 Further research indicate that, at least in my 4 examples, those exact 4 changes do NOT prevent MRT from running/working during Windows updates/other scheduled or forced scans. They simply try to prevent the MRT results from being sent to Microsoft. If you've ever run DoNotSpy, Windows Anti-Beacon, or any other number of (legitimate non-infected versions) of Windows "privacy" applications, they often make settings changes like the ones being discussed. (I personally choose to opt out of data sharing whenever possible)