In message , Stan Brown
writes:
On Sat, 26 Dec 2015 18:20:39 -0600, Paul in Houston TX wrote:
[]
The advice from the Win10 newsgroup is to let it run.
24 hours is not unreasonable.

I beg to differ. It is ridiculously unreasonable.

If you said "not unexpected", I would have been forced to agree.

Agreed on both points (-:

[I still don't understand what the railed CPU core - or whatever - is
actually _doing_ during these locks. To me, update is something like
your machine saying to MS "this is what I've got so far", with the MS
end then figuring out what subsequent updates you need - presumably
taking into account updates that supersede/fix earlier ones, and, OK,
taking account of users whose last update left them with a buggy one.
OK, I could understand if they've been lazy and are just doggedly
leading users through all updates, including buggy ones, rather than
doing a rollup (service packs in all but name, which I gather W7 SP1 -
and possibly W8.1 - are going to be the last ever
issued/released/whatever), but from what I read here and elsewhere, it
sounds as if this delay is occurring _before any actual update
downloading (let alone installing) takes place_. Hence my puzzlement as
to what is actually happening - being done - during the delay.]
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

_IMPORTANT INSTRUCTIONS_ BEFORE ALL TECHNICAL INTERVENTION ON THE [CASE CUT THE
ELECTRICAL FEEDING REGULAR MAINTENANCE PROVIDES THE GOOD WORKING OF A CASE (SEE
INSTRUCTIONS BOOK) [seen on bacon cabinet in Tesco (a large grocery chain)]