Malicious software removal tool Feb 2017

Le_Kirk

Despite Microsoft saying they have cancelled Feb 2017 patch Tuesday, I received the malicious software removal tool this morning. System tried to install it and instead crashed with a "Windows has encountered a problem and....." but before it could tell me, a restart had occurred. When system was running some three minutes later, the "Windows has recovered from ....." error box pointed at two files (one of which was a mini-dump that I cannot open and the other is in a directory that doesn't exist) and after recording the files locations, I clicked on "Windows can search for a solution" but after three minutes of progress bar it just closed without offering a solution.

Anyone received the malicious tool today and successfully installed it?

outofworksch

Yes I updated this at few moments ago and appears to have installed ok. I installed it on its own.

GunJack

mine's gone through with no issues

chunter

as has mine, 32bit and 64bit Win 7 pcs fine.

Le_Kirk

Thanks for that guys, I will have another go later. Maybe I will try the lappy first just to try it. If it wasn't the malicious removal tool that caused my crash, what else could it be? It doesn't help that I am "not allowed" to read the .dmp file and the other one it pointed to doesn't exist!

Later
Added to laptop without problem, must have been a glitch. Will still leave it hidden until next month. Off on hols shortly and haven't time to sort out any issues that may arise.

donnac2558

After reading this thread checked and I had the same update. Went through in a few minutes no problems.

lovesgshp

Mine went through ok as well today.

alanclarke

Try downloading "Windows Malicious Software Removal Tool" from http://www.catalog.update.microsoft.com/Search.aspx?q=KB890830 and running the downloaded file outside Windows Update. I do this every month, it much better than using Windows Update

grumpycrab

This update coincided here with a Windows10 computer that refused to boot. Described at
https://forums.moneysavingexpert.com/discussion/5608045
If you cannot boot or repair I suggest you get to the command prompt in recovery mode then
1. go to main drive (not necessarily C but start there)

3. Type SrtTrail.txt and see if any driver errors are reported at the end of the file