MSE Update problem since Client Upgrade

Is anyone else having a problem with the updates for MSE since the Client Upgrade package?

Some of the updates I've gotten have not installed the 1st time and I've had to hit the "Try Again" button to get them to install. This morning I had to hit the button 2X to get it installed.

Installation Failure: Windows failed to install the following update with error 0x80070643: Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.85.1149.0).

I've done some searching on this, and haven't found a definite fix. But apparently other people are having the same issues. Anyone else find/know anything?

There may be a conflict or you could have malware ... have you run an anti-malware such as MBam ( Malwarebytes' Anti-Malware), just to make sure you're not infected?
|MG| Malwarebytes Anti-Malware 1.46 Download

I have Mbam and ran it just yesterday, full sys scan, also with McAfee (although that's not saying much). Everything was clear. Also ran a full scan with MSE this morning. All clear (knock on wood)

The 1st update failed, the second went in with no probs, the 3rd, 4th & 5th failed and I had to click "try again".

Thanks Jacee & Corrine, I think I found something relevant.

Ever since that problem with the MSE updates about 2 or 3 weeks ago (when you clicked on the update button, it wouldn't update), I've been using the Windows Updater to install the new defs.

This morning, I tried clicking on the MSE update button when Windows update showed a new def was available and it d/l ed and went right in.

So I'm thinking since they did an update for the Client, maybe there's some kind of conflict if you use the Windows Updater to install it? I tried installing 2 other updates that were not related to MSE and they went in fine.

I did look at those articles Corrine, I found the 1st one in my search, but didn't find the second one, thanx for the link.

I saved the link for future ref & I'll have to see if it continues to work good. Digging deep into the logs to check on the ones that didn't install the 1st time, I find that the hash file was read as incorrect.

Thank you

BTW....Adobe is up to it's old tricks. I updated the Reader yesterday and noticed some activity this morning, so I checked the MSConfig and sure enough, it had set the reader and acrobat manager to launch at startup. !@#$%^&* Adobe!

AND MBam was set to start up too for some odd reason, that could have also been a factor.

Have exactly the same problem,tried everything,uninstalled it,try to install it again after downloading it from Microssoft Download Center,but same result,near the end of instalation,it just acts as it does something,but nothing for more then 30 minutes,then had to cancel it.
Still,while system reverting the process,I've opened Program files,and discovered MSE installed near 9 megs of data.