• Malicious Software Removal Tool update, KB 890830, throwing weird WinXP (!) EULA prompts

    Home » Forums » Newsletter and Homepage topics » Malicious Software Removal Tool update, KB 890830, throwing weird WinXP (!) EULA prompts

    Author
    Topic
    #233321

    If I’d seen it once, I’d just disregard it as another bizarre Microsoft bug. But we have three reports now, like this one from @Morat: I’m running Win
    [See the full post at: Malicious Software Removal Tool update, KB 890830, throwing weird WinXP (!) EULA prompts]

    4 users thanked author for this post.
    Viewing 16 reply threads
    Author
    Replies
    • #233322

      It’s just a prank from their A.I. Or one of their fired testing engineers hacking Microsoft for some humor.

      From all the pain we have seen from Microsoft for all these last months, at least we can laugh a bit from this one.

      6 users thanked author for this post.
    • #233325

      Microsoft gives all of us a fair share of frustration. Like this guy => https://lichess.org/forum/general-chess-discussion/my-computer-suddenly-restarted-and-updated-windows-when-i-was-playing-a-chess-game

      Is there anything left Windows, or any other Microsoft product, is good for but frustation?

    • #233336
      Windows - commercial by definition and now function...
      1 user thanked author for this post.
    • #233347
      2 users thanked author for this post.
    • #233375

      This tip is still working to block the useless tool from installing via WU/MU/WSUS/……

      https://winaero.com/blog/disable-malicious-software-removal-tool/

      1 user thanked author for this post.
    • #233389

      I get this EULA prompt when i hit approve in WSUS for KB890830… Windows 7/Server 2008 non x64 flavor only…. weird!

      Capture

      • #233405

        Same EULA in WSUS 2019…. Well, the only thing that this MS tool has ever achieved was wiping our business-critical custom application on workstations across the company — after that, it got never approved again.

    • #233399

      MSRT was originally created for XP. Maybe the EULA is in there more than once for some reason, and this second copy was never replaced – appearing in certain circumstances? Or it could be that part of the build process is to grab a copy of the current EULA text, and if there’s an error use the default?

    • #233409

      Win-XP-MSRT-15-11-18-Win-7-Pro-x32
      Well what do you know? Win7 Pro x32(bit) is it April 1st in Redmond or more of that legendary AI sending out the updates now ? 😉
      PS as per @microfix ‘s link: https://www.askwoody.com/forums/topic/malicious-software-removal-tool-update-kb-890830-throwing-weird-winxp-eula-prompts/#post-233336
      Maybe a time for a prudent wait and see approach for this months little crop of updates.

      4 users thanked author for this post.
    • #233419

      Maybe this is the first step towards Microsoft recommending we all roll back to XP.

      3 users thanked author for this post.
    • #233428

      Where do we stand on the other Windows 7 updates for November 2018?

      Have KB4467107 monthly rollup in WU besides Malicious Softwarw Removal Tool.

    • #233492

      I’ve wonder, since Windows 10 has degraded over the past year, how much ancient code remains in W10. I suspect that there is more old zombie code than I first thought, reading about the XP pre-release message. Coders that have left MS have written elsewhere that it has always been MS’s corporate culture to add new features and UI changes to Windows, while leaving old code behind. This was done to save time and money. It would be great if MS someday releases a clean, fresh OS, not unlike Chrome OS, that runs light and fast, and does not contain any old code from Windows. Features yes, old code that breaks or acts like an anchor, no. It’s possible. I doubt they’ll do it since they don’t even have a full QA department anymore.

      GreatAndPowerfulTech

    • #233549

      I always have installed the MSRT for as far as I can remember, but reading the previous comments now, I wonder what might be the serious problems, if any, with doing this. Any opinions or advice on that? Thanks.

      Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

      MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
      Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
      macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

      • #233560

        As a point of information, I can say that I have observed from log details recognizable version numbering patterns among MSE, Defender (of either type), and MSRT.

        As an opinion, I have held that a given months MSRT for Win7 is as effective as a Quick Scan performed by MSE on the last day of the previous month. That is to say on Tuesday “B” it is already eight or more days out of date. When you delay updating for weeks as a rule, it becomes even more dated. I have not even looked at November’s documentation for accurate current information.

        My personal conclusion is that MSRT is a valuable tool for inattentive users. It gives a reassurance that some minimal level of antivirus is executed once a month. It also reports that status back to Redmond. And there are varying opinions on the utility of that feature.

        Extending on that thought, there are no inattentive users among regular readers here at AskWoody. New readers are already taking steps to change their behavior. If you already use a ‘live’ protection from Microsoft, then MSRT is redundant at best. If you already have a dim view of Microsoft antimalware, then this discussion is moot from the beginning. Opinions, as always, will vary. And I love that freedom.

    • #233585

      Maybe this is the first step towards Microsoft recommending we all roll back to XP.

      May be MS wants people to go back to XP or may be it is the patch for business and governments that pay MS to keep patching XP. I am more leaning to the last one but may it is the first one like you mentioned.

    • #233611

      Nothing odd happened on my 64 bit Win 7 when I installed it…unreal.  Maybe it’s just the 32 bit version??

      I always assumed installing just the monthly “tool” was OK, and exempt from DEFCON rating…urg.

      “Assume”…oy.

      Win7 Pro SP1 64-bit, Dell Latitude E6330 ("The Tank"), Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Newbie
      --
      "The more kinks you put in the plumbing, the easier it is to stop up the pipes." -Scotty

      1 user thanked author for this post.
      • #233615

        I used to think that, too, until about a year and a half ago when it borked my “Turn Windows Features On or Off” window, turning it into a blank white pane. Now I never touch MSRT. The less MS junkware on my computer, the better. (Win 7 Pro, sp1, x64)

    • #233634

      I have never failed to receive the monthly MSRT update except for this month.
      It had me wondering if there was a glitch.
      Almost thought too there might be a lifecycle thing, but that might be
      an XP false alarm as well, and i am on Win 7 Pro Sp1 (albeit x86).
      Anyone experiencing similar?

      • #236493

        Hi, sorry just in passing, commenting that i finally got my November’s
        MSRT 2 weeks later on my Windows Update.
        Had a look on Microsoft Update Catalog for KB890830 and it’s updated
        11/26/2018 for Windows 7 & Windows Server 2008

        2 users thanked author for this post.
    • #233678

      May be MS wants people to go back to XP or may be it is the patch for business and governments that pay MS to keep patching XP. I am more leaning to the last one but may it is the first one like you mentioned.

      Yes, it is XP patch for users that pay MS for support. Many business and governments have programs and equipment that do not work with newer OS and are paying MS to keep getting updates. Paying a few millions is nothing for them. It is like 1 million dollars = 1 cent to them when they are saving trillions on nothing replacing equipment.

    • #233693

      I have not installed MSRT yet. I know about the current problem, but when it would be resolved, I have a question.
      If I have Kaspersky Internet Security and Malwarebytes 3 Premium does MSRT add any meaningful protection layer and/or wouldn’t be then a software conflict?

      • #233695

        As I understand it, this tool is a quick scan of your system to ensure there is no malware. Under normal operations, it would interfere with nothing. Some people see it as useful; others not. Right now, it is an impediment creating confusion and concern.

        On permanent hiatus {with backup and coffee}
        offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
        offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
        online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender
        2 users thanked author for this post.
      • #234204

        You may also wish to read (re-read) post #233375 toward the top of this thread.

        Also Disable Malicious Software Removal Tool Telemetry – gHacks Tech News

        1 user thanked author for this post.
    Viewing 16 reply threads
    Reply To: Malicious Software Removal Tool update, KB 890830, throwing weird WinXP (!) EULA prompts

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: