Another W7 update tale of woe

Le_Kirk

Today was the monthly roll-up (whatever that is) for Windows 7. As usual, I just allowed it to happen and then went for a restart. Normal process, shut-down, configuring 30%, shut-down/restart, log-in, configuration then wait, wait, wait, finally a box "updating personalized (why can't they use English!!!) desktop settings"

Taking a long time so had cup of tea, still waiting so forced shut-down and restart, same dialogue box, so did a cold boot, same dialogue box, so just left it and eventually 20 minutes later, normal desktop appears. It doesn't appear to have been updated or changed. Any ideas anyone? [Apart from; Change to W10, ditch windows and install Linux]

wongataa

Le_Kirk wrote: »

"updating personalized (why can't they use English!!!) desktop settings"/QUOTE]
Personalized is a perfectly valid English spelling. Just because in the UK we tend to use s instead of the z doesn't mean it is wrong. The OED prefers the z spelling BTW.

Spelunthus

I'm guessing you may just have applied the fix for KB4056894 (check Windows Update History to see). This is a VERY LARGE patch, to address some of the issues around the Meltdown problem for Intel CPUs.

It updates very many modules of the Windows 7 OS - so a long time to install, and some unusual install behaviour may be expected.

Personally, I'm waiting a couple of weeks before applying it, because of its huge impact and because there will probably be issues that early patch adopters will find. As far as I understand it, there are no "exploits" - that is, malware, that uses Meltdown.......... Yet.

Le_Kirk

wongataa wrote: »

Le_Kirk wrote: »

"updating personalized (why can't they use English!!!) desktop settings"

Personalized is a perfectly valid English spelling. Just because in the UK we tend to use s instead of the z doesn't mean it is wrong. The OED prefers the z spelling BTW.

Noted. I am old zchool and prefer the uze of "s" Inzert Icon of tongue in cheek!

Le_Kirk

Spelunthus wrote: »

I'm guessing you may just have applied the fix for KB4056894 ........

Indeed it was. I did think it might have something to do with the recent revelation about Intel/AMD but the update was actually quite small and installed quite quickly. It was afterwards when the excrement hit the extractor. I would have thought something as important as this (at least it is reported as important) would not just have been contained within the Monthly Quality Roll-up but would have had an update all to itself. Further research (now that I have the KB ID shows BSOD's reported all over the place, so not just me then. TBF I didn't have a BSOD, it was black with a non-functioning dialogue box.