Malicious Software Removal Tool in Win10 Home won't run

Anonymous
2017-06-12T20:10:34+00:00

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

Windows for home | Windows 10 | Security and privacy

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

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2017-06-14T15:43:33+00:00

    RikDatta,

    Normally, people do not use the MRT command in the run box.  Most people do not even know that this is available.

    MRST scans automatically as part of the Patch Tuesday download and installation.  It just does so.....you do not have to scan it yourself.  If something is wrong, a message will be prompted.  

    Does your desktop look normal again?

    Update me,

    Wayne

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-06-14T15:35:02+00:00

    Hi Wayne.

    I rebooted, and logged in with the Administrator option.

    Tried to run the MRT command.

    Got the same result as previously stated.

    I have now reversed the command by typing in: net user administrator active:no

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-06-14T15:33:07+00:00

    RikDatta,

    Is your desktop back to its normal look?

    Wayne

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-06-14T15:25:07+00:00

    Hi Wayne.

    I ran the net user administrator /active:yes command, as you suggested.

    And I get to sign in as an Admin.

    I tried to run the tool manually, and got the same result. In other words, it just doesn't run.

    If I use the MRT command in the 'run' box', then I get exactly the same message: 'This app has bee blocked by your system administrator.'

    So, no difference.

    And you can see, below, that I am logged in as an Administrator:

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-06-14T15:00:09+00:00

    RikDatta,

    Modification:

    The article previously cited  uses this command:  net user administrator /active:nowith a colon after the word active and before the word no.

    Wayne

    Was this answer helpful?

    0 comments