Jump to content
paulderdash

OfficeClickToRun.exe detected but already in Exclusion List - Quarantine empty on reboot

Recommended Posts

Hello paulderdash:

 

Has the above issue changed since your last post?

 

If not, the next step can be tried.

 

Thank you for beta testing MBARW and your report.

Share this post


Link to post
Share on other sites

Uninstalled Anti-Ransomware and Office Products worked after reboot.  Running Windows 10 and Office 2016.  Unsure if I want to reinstall Anti-Ransomware at this time?????

Share this post


Link to post
Share on other sites

Reinstalled, read how to report a false positive, and am now reading to contribute in a meaningful manner.

 

Thanks for the understanding.

Share this post


Link to post
Share on other sites

Hello paulderdash:

 

Has the above issue changed since your last post?

 

If not, the next step can be tried.

 

Thank you for beta testing MBARW and your report.

I haven't encountered the issue again since my post.

Share this post


Link to post
Share on other sites

Same problem.

Today Anti-Ransomware detected my OfficeClickToRun.exe as malware and quarantined it (Tray banner).

Office 2016 products stopped running.

It was not possible to restore the file while quarantine list was empty.

Uninstalling Anti-ransomware and restarting the PC solved the problem.

It should be useful to make a public list of fale positive solved, to be sure not to jump into this bug again.

 

ZZ

Share this post


Link to post
Share on other sites

Running this on a Production systems is not yet advised. PeAcE

Share this post


Link to post
Share on other sites

Hello @zappozeppo and :welcome:
 
Please carefully read the locked and pinned topic in this sub-forum, How to report a False Positive and for developer analysis, kindly attach the requested files to your next reply in this thread.
 
Thank you for beta testing MBARW and your feedback.

Share this post


Link to post
Share on other sites

Hello @zappozeppo and :welcome:

 

Please carefully read the locked and pinned topic in this sub-forum, How to report a False Positive and for developer analysis, kindly attach the requested files to your next reply in this thread.

 

Thank you for beta testing MBARW and your feedback.

 

I had the same thing as zappozeppo 2 days ago.  Anti-Ransomware detected the OfficeClickToRun executable and quarantined it, but it did not appear in the quarantine list.  When trying to start Office products, it said office was busy updating or something like that.  Disabling protection and rebooting did not help it show up in the quarantine list.

 

Uninstalling Anti-Ransomware entirely did let office start running, but now I don't have a MBAMService\logs folder to upload.  I can't find the specific executable it had detected as the path was so long it didn't show it fully to me, and without it being visible in quarantine list, I can't help with that.

 

I'm attaching my Anti-Ransomware folder from ProgramData

 

(P.S. I thought I wrote a similar reply without the attached logs 2 days ago, but it didn't appear when I came back to post an update. Moderated?)

Malwarebytes Anti-Ransomware.zip

Share this post


Link to post
Share on other sites

Running this on a Production systems is not yet advised. PeAcE

This is typical tip without sense.

If programmers and beta tester work on insulated machines only, they will never be able to release a product.

We are beta testing software on production machines, on our own risk, exactly while this kind of problem is only present on production machines.

And this is positive for programmers.

 

Dear 1PW, the reason I didn't send a "false positive report" for Office Clicktorun is very simple: Each PC sold in the last year has Office Clicktorun executable preinstalled.

And there are not particular situations to put in evidence: Anti-Ransomware is interfering with it.

You can reproduce the problem, simply creating a virtual machine, installing OEM Clicktorun or an Office 365 and ... "voila"

Best regards

ZZ

Share this post


Link to post
Share on other sites

Hello zappozeppo:
 

This is typical tip without sense.
If programmers and beta tester work on insulated machines only, they will never be able to release a product.
We are beta testing software on production machines, on our own risk, exactly while this kind of problem is only present on production machines.
And this is positive for programmers.

 
Testing early beta software on user production systems may be construed as ill-advised and terribly risky by many. Running even a Release Control version on a production system of lesser importance would involve some, but certainly less risk that Malwarebytes would still not suggest. Ignoring the advice of Malwarebytes' developers is at your own peril.
 

Dear 1PW, the reason I didn't send a "false positive report" for Office Clicktorun is very simple: Each PC sold in the last year has Office Clicktorun executable preinstalled.


For the casual observer, that conclusion may be easy to arrive at. In these individual cases, it is by far safer to verify that not one bit of the beta tester's binary/registry hive has been altered. This is one reason why an archive is requested for that exact installed file.
 
Thank you for your continued patience and understanding.

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.