Malicious Software Removal Tool in Win10 Home won't run

Anonymous

I am running Windows 10 Home 64bit. I used to run the Malicious Software Removal Tool, but, all of a sudden, it doesn't run any more.

I've downloaded the most up to date version available from the MS website.

I've tried running it as Admin as well.

But, the tool just doesn't run.

Any ideas, please?

Moved from Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

94 answers

Anonymous

2017-06-15T22:29:54+00:00

Thanks for the advice, Richard.

However, what I'm looking for is an answer to why the tool that I can download from the MS website won't run.

And,

Why MRT won't run from the run box.

If it happens that the downloaded version from the MS website is V5.48, and the tool in the System32 folder is 5.49 - I would have to say that this is not what I'm concerned with.

The problem I am seeking solution to, is why is it that I was able to run the tool manually, and it won't run any more.

But, I take your point and I've just been to the MS website and downloaded 5.49 onto my desktop.

Tried to run it.

And I have the same result. The tool does not run.

Yet... the MRT.exe file that I copied from the System32 folder onto the desktop, does run.

But, please allow me to say, that I used to be able to download the tool and run it manually. And it doesn't run any more.

As well as typing MRT in the run box, that doesn't work either.
Was this answer helpful?

0 comments No comments
Anonymous

2017-06-15T22:05:06+00:00

The log entries you show here are from yesterday and today and show that both the May v5.48 (4 times total and all initiated manually) and the June v5.49 (2 times total, both initiated by Windows update) have ben run.

The first instance of the May v5.48 was a full scan and took about 2 hours and 36 minutes to run and complete. The other 3 instances were quick scans.

The first instance of the June v5.49 was a quick scan and took about 49 minutes to run and complete. The second instance was a quick scan and took about 47 minutes to run and complete.

From what I see here your playing with two different versions (builds) of the tool and the May v5.48 has been able to be run manually (over and over again) and that the June v5.49 has not been run manually.

No wonder your having problems, do you even know for sure if a manual run attempt of the June v5.49 was made?

Quit running the May v5.48 tool, it looks like running it after the June v5.49 tool has been run by Windows update causes Windows update to run the June v5.49 tool again.

-Richard
Was this answer helpful?

0 comments No comments
Anonymous

2017-06-15T20:58:46+00:00

Yes.

I have checked the MRT.log file:

Microsoft Windows Malicious Software Removal Tool v5.48, May 2017 (build 5.48.13803.0)

Started On Wed Jun 14 17:11:13 2017

Engine: 1.1.13704.0

Signatures: 1.243.729.0

Run Mode: Interactive Graphical Mode

Results Summary:

No infection found.

Successfully Submitted MAPS Report

Successfully Submitted Heartbeat Report

Microsoft Windows Malicious Software Removal Tool Finished On Wed Jun 14 19:47:37 2017

Return code: 0 (0x0)

Microsoft Windows Malicious Software Removal Tool v5.48, May 2017 (build 5.48.13803.0)

Started On Wed Jun 14 19:48:04 2017

Engine: 1.1.13704.0

Signatures: 1.243.729.0

Run Mode: Interactive Graphical Mode

Successfully Submitted Heartbeat Report

Microsoft Windows Malicious Software Removal Tool Finished On Wed Jun 14 19:48:15 2017

Return code: 0 (0x0)

Microsoft Windows Malicious Software Removal Tool v5.49, June 2017 (build 5.49.13902.0)

Started On Wed Jun 14 20:01:17 2017

Engine: 1.1.13804.0

Signatures: 1.245.112.0

Run Mode: Scan Run From Windows Update

Results Summary:

No infection found.

Successfully Submitted Heartbeat Report

Microsoft Windows Malicious Software Removal Tool Finished On Wed Jun 14 20:50:44 2017

Return code: 0 (0x0)

Microsoft Windows Malicious Software Removal Tool v5.48, May 2017 (build 5.48.13803.0)

Started On Thu Jun 15 18:30:26 2017

Engine: 1.1.13704.0

Signatures: 1.243.729.0

Run Mode: Interactive Graphical Mode

Successfully Submitted Heartbeat Report

Microsoft Windows Malicious Software Removal Tool Finished On Thu Jun 15 18:30:38 2017

Return code: 0 (0x0)

Microsoft Windows Malicious Software Removal Tool v5.48, May 2017 (build 5.48.13803.0)

Started On Thu Jun 15 18:31:32 2017

Engine: 1.1.13704.0

Signatures: 1.243.729.0

Run Mode: Interactive Graphical Mode

Successfully Submitted Heartbeat Report

Microsoft Windows Malicious Software Removal Tool Finished On Thu Jun 15 18:31:40 2017

Return code: 0 (0x0)

Microsoft Windows Malicious Software Removal Tool v5.49, June 2017 (build 5.49.13902.0)

Started On Thu Jun 15 18:39:44 2017

Engine: 1.1.13804.0

Signatures: 1.245.112.0

Run Mode: Scan Run From Windows Update

Results Summary:

No infection found.

Successfully Submitted Heartbeat Report

Microsoft Windows Malicious Software Removal Tool Finished On Thu Jun 15 19:26:05 2017

Return code: 0 (0x0)
Was this answer helpful?

0 comments No comments
Anonymous

2017-06-15T20:11:42+00:00

Check the All app packages, All restricted app packages, and users ...... entries, they should all be shown with Read & execute and Read checked only.

What is shown as Owner in Advanced >Permissions tab (at the top left under Name)? In the field you will also see the assigned permissions for each account.

Have you checked the MRT.log file as of yet?
Was this answer helpful?

0 comments No comments
Rob Koch 26,160 Reputation points Volunteer Moderator

2017-06-15T19:56:53+00:00

Everyone,

I've seen lots of discussion about the specific file(s) and issues affecting them, but no attempt to verify the log entries on the system actually having the problems.

It's possible this may contain valuable error information that isn't otherwise being displayed on screen, so I'd suggest that RikDatta provide the most recent section of his log here, if possible correlating which version of the program he was manually attempting to execute for each entry listed. Even if the entries for some of these are entirely missing, that tells us that the program is never actually executing far enough to perform this simple process.

Any potential error messages displayed would be the most valuable, while any difference from normal entries might tell us something about the flaky operation in the OP case here.

Remember the MRT.log is found in the %WinDir%\debug folder

Here are my log entries with no infections detected for the newest version that downloaded this Tuesday, running first from Windows Update and then 2 times manually (quick then full scan) on Wednesday when I first responded to this thread.

Microsoft Windows Malicious Software Removal Tool v5.49, June 2017 (build 5.49.13902.0)

Started On Tue Jun 13 17:03:55 2017

Engine: 1.1.13804.0

Signatures: 1.245.112.0

Run Mode: Scan Run From Windows Update

Results Summary:

No infection found.

Successfully Submitted Heartbeat Report

Microsoft Windows Malicious Software Removal Tool Finished On Tue Jun 13 17:04:53 2017

Return code: 0 (0x0)

Microsoft Windows Malicious Software Removal Tool v5.49, June 2017 (build 5.49.13902.0)

Started On Wed Jun 14 15:28:07 2017

Engine: 1.1.13804.0

Signatures: 1.245.112.0

Run Mode: Interactive Graphical Mode

Results Summary:

No infection found.

Successfully Submitted Heartbeat Report

Microsoft Windows Malicious Software Removal Tool Finished On Wed Jun 14 15:29:37 2017

Return code: 0 (0x0)

Microsoft Windows Malicious Software Removal Tool v5.49, June 2017 (build 5.49.13902.0)

Started On Wed Jun 14 15:31:54 2017

Engine: 1.1.13804.0

Signatures: 1.245.112.0

Run Mode: Interactive Graphical Mode

Results Summary:

No infection found.

Successfully Submitted Heartbeat Report

Microsoft Windows Malicious Software Removal Tool Finished On Wed Jun 14 15:53:58 2017

Return code: 0 (0x0)
Was this answer helpful?

0 comments No comments