Yesterday, I downloaded the KB890830 update via Windows Update. The update process wasn't exactly straightforward as it hung on me while installing updates so I had to hit the reset button on my tower.

After restarting, I went back to Windows Update and verified the update was indeed installed in the update history. However, I noticed there's a maintenance process as indicated by the Action Centre tray icon. I opened up Windows Update and saw my PC is trying to install the update once again.

Is there a way to alleviate this?

Hi,

Please confirm If it appears in the Installed Updates list:

Control Panel\All Control Panel Items\Windows Update\View update history, click Installed Update link in the upper right-hand corner.

If yes, restart your PC to check the result.

If no, please download and install it manually. You could get it here:

http://www.microsoft.com/en-in/download/malicious-software-removal-tool-details.aspx

I'm having a similar problem: I've verified that this update has installed. However, it still shows up in Windows Update as an "Important Update."

Note that in the update history, this same update shows as having succeeded yesterday, then having failed today, and then having succeeded another time today. At some point today, the computer entered a loop of configuring the update, restarting, configuring update, restarting, and so on. After at least five repetitions of this, the computer finally started properly. That's when I saw the success, failure, success of this update, and I saw it's still showing up as an "Important Update" even though it's been installed.

For now, I'm simply going to hide the "available" update.

• Marked as answer by Andy AltmannMicrosoft contingent staff, Moderator Wednesday, March 05, 2014 2:29 AM

I've been having the same problem.  None of the suggested solutions work for me.  Windows 7 32 bit.

What is Windows checking to make it think the update hasn't installed and needs to be installed again.  The update history indicates 4 successful installs of the same patch.  Microsoft needs to provide a fix for this issue.