New
#11
You know, that's odd. The same update was unchecked on mine, that's the 1st time I've seen that happen. I did install it and apparently, there are no problems (knock on wood).
Recent updates are unchecked in Windows Update. Why?
-
-
New #12
Yep. Same. That particular update always seems to be unchecked, hence my suspicion that Microsoft controls it. Technically, this proves nothing. There could be something about that update which triggers an un-checking event on everyone's computer. Quite what that is I do not know.
This morning I trawled through every last piece of package data, and could find no such setting. When I get time, I shall have a look through the wsusscn2.cab XML data.
After that, I don't really know. Without access to the source code, it will be very difficult to track down without insider help.
Richard
P.S. But I *still* suspect the answer to lie within package or wsusscn data.
-
New #13
This is what the site says. It was marked as important, so it should have been checked...curious.
MS12-006: Description of the security update for Webio, Winhttp, and schannel in Windows: January 10, 2012A security issue has been identified that could allow an unauthenticated remote attacker to compromise your system and gain access to information. You can help protect your system by installing this update from Microsoft. After you install this update, you may have to restart your system.
-
New #14
Well I mentioned earlier that in some cases that update fails. It's getting to be a rather old update now so my bet is that it tried to install along with a lot of other updates and failed. So it remains in the list unchecked.
You can actually check your failure list and see if it's in there... Open Windows Update, then click View Update History. In mine, those two updates tried to install and failed /repeatedly/. I think after some number of tries it just gives up but leaves it in the list so you know that there is an update that needs attention.
-
Posts : 5,605 Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019New #15
For Borg386:
So far, so good for me also!
niemiro
I would be interested in what you find in the wsusscn2.cab file.
fseal
I feel left out.
After checking mine, yesterday's instance is the only time its been offered, and thankfully passed.
-
New #16
Heh yeah
Well all my machines at home did NOT have the problem. But my work machine did. At work our admin filters the updates and it's possible that the update fails given a certain set of updates applied or not applied previously, maybe in a certain combination or order that causes the situation.
-
Posts : 5,605 Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019New #17
Okay, now I don't feel so bad :)
I didn't want to put all the weight on niemiro, so I tried looking for that wsusscn2.cab file.
Even though I un-hid? system, and protected files I still couldn't come up with it.
-
New #18
My system installed this update last night, and I had massive bsod the second I tried to use my machine this morning. Every 2-3 minutes after login, bsod.
I system restored to yesterday, and so far the system has gone back to it's normal happy self.
-
Posts : 5,605 Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019New #19
Consider yourself lucky, some patches are un-instaliable.
Your machine store bought or home brew? Couldn't tell you didn't fill in your system specs.
-
New #20
Quote
Related Discussions