Solved Malicious Software Removal Tool Update KB890830

[feetand nches]

Is it really possible that there are no Dates to these Posts, or even the start of my Thread??? Now I will not know which Restore Point to use!

 

[feetand nches]

I let SURT Install, but it did not help even after a shutdown and startup. It did not say a Restart was needed, perhaps I should have done that.

I then used a Restore Point from 11-16-17 (it was the latest Restore Point available) but that did not work either, still can't Search For Updates.

The directions above seem to be for an older 890830. I Deleted Windows\system32\mrt anyhow, but Windows Update still would not work and won't even show me Installed Updates so that I could Hide as they suggested, so that was a dead end for this problem. If this is indeed the issue, glad I did not install this on another pc of mine.

 

[feetand nches]

Interesting that they have "Modified" this Tool/Update
Windows Malicious Software Removal Tool x64 - November 2017 (KB890830)
Last Modified: 12/7/2017
Size: 49.0 MB

Just did a sfc with no success, so the only thing I can think of is to Install this Update again with Avast Turned off, though the Update seems to be an issue, I don't see others with this issue in the US. I just don't know any other way to fix this guys, is there no one else having this issue here?

 

[feetand nches]

Can someone tell me why there are Two Downloads for this? I downloaded the first one, but it is just running a Scan, and don't seem to be installing anything? The Second one seems to be called "Delta" I did this after Disabling Avast as one of those links said it may interfere.

 

[feetand nches]

I seen this thread also, but it is a dead end unless I am missing something.
November 2017 update Malicious Software Removal Tool Solved - Windows 7 Help Forums

 

[Seffrid]

The manual MSRT only runs a scan, when you download it through Windows Updates it installs and runs silently only alerting you if there's a problem. I haven't installed the current one but stayed well clear.

Recent problems with Windows Update not running have been related to an expiry date on Microsoft's end. That is supposed to have been fixed now but some are still having problems. Unfortunately while there's a very good discussion of these issues on another site it appears to have been blacklisted here so I can't provide a link to it.

 

[feetand nches]

Thanks Seffrid! I have google'd the heck out of it but cannot find anyone else having the same issue.

 

[Ranger4]

Having problems now, and don't really know how to fix it. The weird thing is, KB890830 is not installed even after I installed it.

Now, I cannot Update, and File Explorer seems to crash from time to time, otherwise all else seems to be working.

I will run sfc and see what happens.

"Windows update cannot currently check for updates, because the service is not running, You my need to restart your computer".

This is exactly the message you get when the AuthCab has expired. Doing the following seems to fix it:

The date on the computer has to be reset & to do that follow this:

To reset the date on the computer Right Click on the Clock at bottom RH corner of the screen, select Change Date & Time Settings, when that opens click on the Internet Time tab, Then select Change Settings, then untick Synchronise with Internet Time Server, be sure to tick OK, then select the Date & Time tab, Then select Change Date & Time & set the date back to 3 Dec.

Then reboot the computer & then run Check for Updates in Windows Update, it should update to the 3 Dec. In some cases you may need to try an earlier date if the 2nd does't work.

Then reboot, reset Internet time Synch, change computer date to today's date, re run Check for Updates in Windows Update & it should check for Updates & came back with Windows is up to date, with the latest updates installed.

This method should retain all your Update History as well.

 

[feetand nches]

I will make note of this Ranger, unfortunately I have used one Image I had to Restore the pc. That did not work, so now going back even further, hope it works. If not I'll try your suggestion. Never heard of that fix before, so that is very interesting to me.

Thanks, pcpunk

 

[Ranger4]

The reason you need to follow the procedure I have shown in Post #28, is that Windows accesses an AuthCab during the start up procedure that Authorises access to the Windows Update download site. This authorisation expired on 3 Dec for a lot of users & access get blocked to the Windows Update site.

By running the repair I listed above, resetting the computer date & rebooting provides access to Update site at which MS have now reset the expiry of that AuthCab which gets installed on your computer, so it can now download & install Updates. Of course it is then necessary to reset the date on the computer & re run Check for Updates to bring it completely up to date.

Going back & restoring old images are unlikely to fix the problem as no doubt they are using the same AuthCab expiry date.

 

[feetand nches]

Ranger4, I am so thankful, as I could not get anything to work. I used your directions after employing two different images (and all the other stuff I did) and it is all fixed now, thank you so much. This is my main pc, and my work pc, I was pulling my hair out trying to fix this. I think bashing my head against my desktop must have helped a little also LOL.

Is there any ideas as to why this happens to only certain people?

Thanks, Nasty7

 

[feetand nches]

Yes, you should install it. It will run in the background afterwards. MSRT usually comes out once a month. I always check to see if Updates are ticked & if not ticked I tick them.

Running other AV software should not affect MSRT.

I actually hid that Update, I wonder if that is okay?

 

[Ranger4]

No doubt there will be a new one coming in the next major roll up, so you can probably leave it until then. Or you can unhide it.

It really is up to you. I always run the MSRT as it's good insurance against malware.

You are welcome & thank you. Very glad to hear the update problem has been fixed for you.

The only reason I can think of it that different Windows 7 users have different expiry dates on that AuthCab. This is probably a sensible approach from MS because having them all expiring at the one time would create massive havoc if what happened to ours happened to every user. The problem seemed to be caused by neglect of someone at MS to update these things.

 

[Seffrid]

The MSRT only finds certain specific infections already on your machine, it does not protect against anything in the future. It accompanies the usual Windows Updates every month. I would leave the current one uninstalled as it is unchecked and you should never check/install unchecked updates as there is always a reason for MS not checking them - in this case, it's a problematic update that has caused some issues. I would hide it.

 

[feetand nches]

The MSRT only finds certain specific infections already on your machine, it does not protect against anything in the future. It accompanies the usual Windows Updates every month. I would leave the current one uninstalled as it is unchecked and you should never check/install unchecked updates as there is always a reason for MS not checking them - in this case, it's a problematic update that has caused some issues. I would hide it.

No argument here! LOL

Got no problem hiding this one, and was hesitant when I installed it. My system is super clean and I'm quite careful with it as my Primary pc, so I can only guess that this caused my problem. Otherwise it has been smooth sailing for a while now. Only had one problem with this install when I (Stupidly) Connected a customer's Docked drive that was infected. Caused me some problems, but not do bad.

Thanks Seffrid!