New
#10
Hi there
I wonder what the issue is in releasing these fixes for 1809 when as I think we all know that 1903 is very near to be being released -- surely it would be better almost to treat 1809 as "EOL" and just release emergency fixes etc on it and concentrate on the 19H1 (1903) and 20H1 releases instead.
Of course who knows how the great corporate entity known as Ms works internally -- I suppose there could be a load of politics and ego clashings going on --often is at large corporations while the poor old developers are just like the foot soldiers - they just get on with what their bosses tell them to do.
Still it does seem to me a bonkersly idiotic way of treating a workforce to get out what looks rather a pointless release / update on a beautiful Sunday (coming up soon to longest day of the year) when people could be out with families etc (or even their dogs !!) rather than stuck in an office getting the release out.
Cheers
jimbo
Hi there
I don't need to pay anything to UK Govt - but if their site is down and you owe them money it's not your problem if they can't take it !!!!!!!!! Same as anywhere else I suppose would be party time !!!
--OK some services need to run 24/7 e.g power suppliers, Hotel and Bank sites, Police etc but a lot of these now are "On Call" so people don't actually have to be there unless something breaks.
Cheers
jimbo
I agree: it's odd that MS decided to let this one fly over the weekend (on a Sunday evening). Just installing on my various Current Branch systems now. So far, so good.
--Ed--
This was also released for Win 7 under KB4505050.
Wondering, this will also already be part of the next CU, right?
Its just an urgent hot fix.
I suspect it's an attempt to correct the 'egg on face' moment ASAP after they accidentally blocked access to some UK .gov.uk sites. I'm sure MS don't want to get on the wrong side of the UK government.
I note that, unlike the 'C/D' releases, this one is not optional. It has been installed automatically through windows update on my machines without manually checking for updates.
EVERY version has had this patch released, there's even one for the original 1507 (which is still in support as a LTSB).
Cumulative Update KB4505051 Windows 10 v1507 Build 10240.18218 May 19
Yep, indeed it sounds like a very plausible explanation.