[ding dong]

Yeah I read that but I didnt understand if the one that is already logged into my windows update sitting there before the crash is the bad one? The KB3000850 is said to be a problem?

[Advertisements]

"An emergency update was released yesterday.

The current solution for those affected is to uninstall KB3000850 this should revert the system back to normal
Run an update on Avast which will install the new driver
Then you can install the update again "

Edited by techmantrey1, 23 November 2014 - 09:22 PM.

[techmantrey1]

"An emergency update was released yesterday.

The current solution for those affected is to uninstall KB3000850 this should revert the system back to normal
Run an update on Avast which will install the new driver
Then you can install the update again "

Edited by techmantrey1, 23 November 2014 - 09:22 PM.

[ding dong]

ok, but sorry, i am still not being clear.

 

I do have the KB3000850 update sitting there in Windows update but dont know how to remove it from there and refresh updates so I get the latest one?

[hazard209]

I wouldn't remove it from the queue. It's the November rollup update. Kind of like a service pack but it doesn't change the version number or deprecate APIs. https://support.micr....com/kb/3000850

 

As Essexboy said, Avast! has patched the issues with this update. If you've updated Avast! to the latest version then you should be safe to reinstall this Windows update.

[ding dong]

But what if its been sitting there since before November....I'm scared...to touch it....

[hazard209]

It's your computer, buddy. You can do what you want to with it, no one is forcing you. I'm just letting you know that Microsoft is recommending that you install it and that you should be ok to do so now that all of the conflicts have been resolved.

Best of luck.