New
#20
@jimbo45 my issue is that it really never is a good time for me to upgrade/update at the moment. My computers are on 24/7 and when I sit down, I expect everything to be where I left it.
Hi that's fine
@slicendice
only making a suggestion though. However this upgrade seems to work really quickly and unlike a lot of previous builds IMO this one is worth having.
The problem with Windows that because of the huge disparity in users ability and hardware Ms I suppose has to take the line of what it thinks is the best compromise option which in theory has the advantage of keeping most systems up to an appropriate level. This obviously doesn't please some people and unless you block all updates which itself is a risk stategy I'm afraid this is one of the drawbacks with Windows that most of us have to tolerate.
Ms though could look at ways to run these updates in the background so you can just carry on with what you are doing and also find ways where a re-boot or restart would only very seldomly be required.
If Windows could work like this for updates though !!!! :
My Arch Linux system has had 3 different kernel upgrades (4.9, 5.2 and currently 5.3.1), 2 VMWare release updates from 15.0 (15.1, 15.5) and a whole slew of library and other updates -- not a single re-boot been needed in several months running 24/7 and apart (obviously enough) when updating the VMware release I had to close down 2 VM's and restart running those VM's -- not unreasonable in that case.
Cheers
jimbo
Updated to this yesterday without issue. I'm using my RP test machine in a quasi-production role and it's been a solid as a rock. The RP release seems pretty stable and well-behaved -- at least on this new-ish laptop (i7 8650U, 8th Generation aka Kaby Lake) PC. Although we may not see 19H2 for a little while yet, it seems like it's getting close, at least.
Just MHO.
--Ed--
I switched from the Slow Ring to the Release Preview Ring yesterday from 18362.10022--then downloaded the RP 18363.329 ISO from the Flight Hub and then installed it in place over 18362.10022--and afterwards got a few .net updates and Defender updates. But my build number is now 18363.10022....;) Tried to install KB4524147 x64, but of course it will not install since my build # is .10022 instead of .387. I may have jumped the gun a bit...;) Any suggestions? The build is running fine but I am afraid I won't get any more updates on the release preview ring because of this build #.
Yep, thanks--I have a Macrum Reflect backup of my 18362.10022 boot partition, and I may wind up simply restoring that to go back to the slow ring--but first I think I'll wait awhile to see if Microsoft will release another update for KB4524147 x64 that'll work with a build besides 18363.388, or a new cumulative build update for 18363 that I can access that includes it! We shall see.... No trouble with this build as of yet!
Just received the update from WU on my 19H2 1909 18363.388 Release Preview system.