Windows 10 Cumulative Updates
June 13, 2017 at 7:57 pm #9080
November 15, 2017 at 10:40 pm #13517
November 14, 2017—KB4048955 (OS Build 16299.64) – various quality improvements.
Never trust an atom - they make up everything !December 1, 2017 at 9:21 pm #13943
November 30, 2017—KB4051963 (OS Build 16299.98)
This update includes quality improvements. No new operating system features.
Never trust an atom - they make up everything !December 2, 2017 at 10:50 am #13949
I updated 10 machines yesterday. two failed and needed me to download the executable version which worked in both cases. What I don’t understand is why the update was called:-
2017-11 Cumulative update for Win10 V1709 for AMD64-based Systems.
This was the title shown in Windows update even on systems that were Intel not AMD.
Funnily enough the reference to AMD64-based does not occur in the downloaded exe file.
Anyone know whyDecember 5, 2017 at 7:57 pm #14100
They have done that before. Seems to happen off and on anytime they talk about X64.December 5, 2017 at 8:05 pm #14101
The last update broke Office home and student 2016 on two of my mum’s friends computers.
The update disabled the Office click start service preventing Office from starting. Just setting the service back to automatic fixed it.December 6, 2017 at 7:41 am #14102ParticipantDave Rice@ricedgForumite Points: 9,073
It’s called AMD 64 as it was AMD that designed the “X86” 64 bit code we use today and Intel licence it (Intel went off down the Itanium route which ended up in failure).
Not had an issue with Office yet, but 2 PCs in one office both had the network port of their shared office printer set to LPT1. That obviously stopped them printing!December 6, 2017 at 9:48 am #14103
Thanks for the info David. That does explain the anomaly. I have learned something new today.December 9, 2017 at 12:34 am #14203
Yep Intel said at the time that it was not possible to extend X86 any further with a 64 bit version and that was why they were starting afresh with the Itanium.
Before the Itanium launch they also said it would do X86 emulation in hardware at about the same speed as a real X86. The Itaniun actually does emulation at about 25% the speed.
Intel was seriously wrong footed when AMD came up with AMD64 and microsoft wrote a version of windows for it.December 9, 2017 at 12:45 am #14204
Intel even had a problem with their naming conventions because they had retro named X86 as IA32 (Intel Architecture 32) and named the Itanium IA64.
What were they going to call their 64 bit version of X86. They settled on IA32e.December 12, 2017 at 8:34 pm #14323
December 12, 2017—KB4054517 (OS Build 16299.125)
update includes quality improvements, No new features.
Never trust an atom - they make up everything !December 13, 2017 at 7:22 am #14327ParticipantEd P@edpsForumite Points: 16,286
While normally I have no problem in using the automated update system, it is a disaster if Windows is used for 24/7 security purposes. One recent such roll-up on Windows Home totally stuffed a week’s cctv recordings. If you have the same problem in letting Windows update run rampant you can simply zap the Windows Update Service afaik this is an all or nothing nuclear option so do NOT use it unless you are willing to take full responsibility in turning updates on or off. (there is no fine-grained control). This does NOT turn off security updates so unfortunately my security system can still be zapped by ‘security’ updates.
I think if I still can an unacceptable number of problems I am going to have to somehow install Windows 7 or move to a Linux setup (not a trivial move unfortunately as I would have to re-roll my security system).December 16, 2017 at 12:16 pm #14410ParticipantJayCeeDee@jayceedeeForumite Points: 5,356
Just been told to “restart to update for new options” by a blue W10 style dialogue box, hit the restart now and it got stuck on the spinning dots for an hour and a half. I had to do a hard reset.
That’s either one hell of an update, or – as I suspect – it’s having problems updating because the Fall Creators Update failed through various files being missing. I’ve not bothered to deal with that yet, and I’ve managed so far as all the earlier security updates have gone through fine.December 16, 2017 at 12:39 pm #14411ParticipantJayCeeDee@jayceedeeForumite Points: 5,356
Apparently it’s ” Feature update to Windows 10, version 1709.”
EDIT – found the reason – 1709 is the Fall Creators Update – I’ll set that to run overnight – I’ve already had a nag screen!!December 16, 2017 at 12:51 pm #14413
Might be quicker to use the Media Creation Tool.December 16, 2017 at 1:13 pm #14414ParticipantRichard@sawbomanForumite Points: 6,517
Alan, I agree, I have done four machines that way a while back. Most of the family devices were stuck back on older Windows 10 versions then one, a 2008 Dell portable, made the leap straight to Fall. With another, software issues interrupted the game so I replaced the spinning rust with an SSD and doubled the memory before a re-install using the media creation route. The machine went from 32bit to 64bit at that time. The other three machines were done during daylight hours via the forced route with everything under control so no unexpected results. They took various amounts of time, two had SSDs and one, the slowest portable a spinner. The process took a noticeable amount of time, but when planned it was no great challenge and I knew all was well by the end.
I have one machine left to update and for the moment, that’s as in ‘left well alone (on 1603?)’ . The user is a ‘challenging person’ with a number of ‘issues’ both physical and ‘other’ – the effects of any disturbance to their bubble are rapidly very apparent!
It is interesting that John’s machine waited so long before stepping into the water, perhaps our remaining machine will take the automatic plunge. However, I was also told that a glitch with some earlier parts of the update 1609 process might require the forced route via media creation to be used.December 16, 2017 at 1:49 pm #14416
The MCT has got me out of jail on (a) a Windows tablet with only 32GB storage and (b) another PC that just didn’t like the Fall update and kept failing.
Took me a while to find out that you create the MCT USB, but don’t boot from it – instead plug it in and just run “setup.exe” – this seems to be the only way to use temporary external storage if you are low on space. Why the “normal” update won’t let you use an external HDD/Flash Drive/SD who knows?
Have a feeling that Windows 10 is starting to get messy. Everything update-wise used to just happen – still does on some machines, but getting to be a chore on others.December 16, 2017 at 2:51 pm #14417ParticipantPlaneMan@planemanForumite Points: 7,221
Another one for the MCT, I update my little Dell using that whenever there’s a big update. Nothing critical on it (tv box essentially) so it just has a wipe and reinstall of the latest Windows version.December 16, 2017 at 4:56 pm #14421
PM from memory you have the same mini dell as me (3050)…if you want to wipe and reinstall fine, but you can use MCT to update without reinstalling… just done the fall update on mine …plug the MCT usb in and launch setup.exe (while windows is live)…. you’ll probably need another blank temporary usb drive plugged in for temporary storage but it will tell you if you do…it then updates, keeps your apps and all relatively painless.December 16, 2017 at 5:02 pm #14422ParticipantPlaneMan@planemanForumite Points: 7,221
Yep, that’s the one.
The way you describe is how I keep my mum’s ‘disposable’ Win 10 laptop updated, one of the super cheap low spec jobs that she takes on holiday.
She can’t remember half her passwords so it’s easier that way, for me I just have to log in to Netflix and Amazon and it’s good to clear the crud out.December 16, 2017 at 5:24 pm #14427
Fair play – makes sense
- You must be logged in to reply to this topic.