Windows 10: Cumulative Update KB3201845 Windows 10 Build 14393.479

yes, don't like how the updates can catch you off guard! Done both my machines, seems fine but didn't notice any difference. Took ages on getting windows ready on our celeron mini PC!

 

After a week, finally got mine on the lappy. Just as I was checking my desktop, got a notification of restart. So far nothing noticeable.

 

Downloading now on my 2 in 1. I always do that before installing on primary laptop.

 

That's not new, mine has been doing that for a long time

 

It only includes bug fixes and optimisations so you probably won't notice any changes unless it breaks something Scottyboy *Smile

 

Well that was interesting. Download didn't seem to be doing anything after 30 minutes so I rebooted. Download restarted and took another 30 minutes.Then rebooted to apply update. Failed.
Restarted the update. download took 10 minutes this time and update took 5 minutes.
Rebooted, update completed and succeeded.
Just a little painful.
Well, the adventure continues.
I rebooted my PC again and I got the "Preparing Windows - Do Not Turn Off Your Computer" message...for 27 minutes. Believe me, I was tempted to press Reset but I didn't. It shut down and then booted up normally.
Strangest update since AU.

 

Two machines, one Toshiba laptop on Home x64, the other Samsung with Pro x86. Both updated successfully....

but....

....boy was it slow for the x64. download and install was at the pace I usually get, but the blue 'preparing to apply updates...' screen lasted for more than 25 minutes before the 'applying updates...' percentage count started. Thereafter progress was normal again.

 

All ok on all my systems I have to update

 

Ditto - see above.

 

Another difference between the two - for the x86 Pro Disk Clean Up finds 1.67GB, of which 1.66GB is 'Windows Update Clean-up'. The x64 Home has found the increasingly familiar 3.99TB of 'Windows Update Clean-up'.

 

Just a short note of explanation about what looks like freezing downloads and long times.

Today, if you looked at Taskmanager, you would see the process TIworker doing a lot of cpu and I/O. In the case of a cumulative update like this one, the system needs to first install "permanently" any previous updates. A similar process takes place when you run Disk Cleanup. When that process finishes, it speeds up.

A possible explanation for the Cumulative coming out today: Next Tuesday's Patches will most likely be all security patches. Today may have been to get the code up to date for the security patches. The Release Preview Ring (not to be confused with Slow or Fast) was already updated either last week or the week before, so RTM and Release Preview (both 14393.479 now) are ready for security patches.

TC

 

Glad to hear it's not just me. *Smile
Was yours the x64 version like mine? Home or Pro?

 

While that makes sense, it doesn't quite seem to explain my 25+ minutes of 'preparing...'. I routinely run Disk Cleanup to clean up all 'system files' (including the Updates) after each cumulative update. Doesn't that mean that they were already installed "permanently"?

 

I believe in the case of Disk Cleanup, they are compressed. Hence "similar". Both seem to take quite a while, though for different reasons. Lots of processes that appear to be taking a long time and "freezing" are doing lots of work in the background. That's why I mentioned checking Taskmanager, you'll usually see what's churning.

 

Unfortunately the only part of the update process that was extraordinarily slow was the blue 'Preparing to install updates' screen - which makes it a little difficult to check Taskmanager (or anything else).