Windows Malicious Software Removal Tool x64 - November 2019 (KB890830) -Error 0x800711c7

Thanks. Like all who replied, I am waiting for Microsoft to fix problem.

Thanks. Like all who replied, I am waiting for Microsoft to fix problem.

Microsoft Fix this please?

Windows Malicious Software Removal Tool x64 - November 2019 (KB890830) - Error 0x800711c7

Thank you!

I'm just going to add a note for those with enough ability to understand what I'm about to say, since I also have a Surface Go device running Windows 10 S and first saw this error code myself when checking Windows Update for a different reason.  This thread told me everything I needed to know, which is that the problem is common and appears to occur only with Windows 10 S since the November MSRT update, which was all I truly cared to know.

I've returned here to explain something I realized myself only after reading the concerns in this thread, since it appears the error code issue continues with the December MSRT release and so will likely continue to receive much concern from those who care enough to use Windows 10 S for its improved security.

The point is that the Windows Malicious Software Removal Tool is described in its knowledge base article as follows.

"Microsoft generally releases the MSRT monthly as part of Windows Update or as the standalone tool. Use this tool to find and remove specific prevalent threats and reverse the changes they have made (see covered malware families)."

If you click the link to the covered malware families above, you'll find there are roughly 300 families detected, but what's more important is that most are either Win32, Win64, Worm or PowerShell types of detection.

To those with even a small amount of knowledge relating to Windows 10 S, you should recognize that since Windows 10 S doesn't allow executable files from other than the Windows 10 Store to operate, nor does it support PowerShell scripts, that means that none of these particular items should even be able to function within Windows 10 S.

The larger question this brings to mind for me is; Why is Microsoft even including the MSRT update in those it provides for Windows 10 S?

I'm afraid I don't have enough time to fully investigate each specific detection to try and discern a reason, but I suspect it might simply be in case a future item added to the MSRT may also affect something Windows 10 S doesn't inherently provide protection from.

For those not following, I'm saying that I don't truly think that the MSRT is (currently) needed with Windows 10 S, so I'm personally not concerned that it's not "installing" (e.g. running) properly.  If Windows Security is indicating that Windows Defender is operating properly, then there's really no reason that the MSRT is needed.

In fact, it's only normal purpose on any Windows desktop or other device is as a sanity check that the installed AV or other security application(s) are performing properly, detecting the most prevalent malware known to Microsoft that are contained within this relatively tiny and fast scanner.

In other words, though the error code display may be disconcerting, I'll simply ignore it myself and assume Microsoft will eventually get around to fixing it when convenient, even possibly by just removing it entirely if there's no reason to support it on Windows 10 S.

Rob

Nice detail Rob. 

Agreed. 

To be honest Win10S was new to me. Ive just bought 2 laptops for the kids. I wanted to updated everything before giving them to them for Christmas so i removed the S and updated. 

I wish MS would address the issue so its not an issue. 

However for me, there were other issues with the trackpads on Asus laptops so they’ve gone back and will have Lenova ones to setup this weekend.