Win 10

[palombian]

Win 10 Build 18936.rs_prerelease.190705-1333 installed 11 July. Download and install to a usable PC took roughly 14.5 hours.

Most of that time, 10 hours, was install time.

As soon as the program asked for a restart, I was there to restart it. That took almost 4 hours. During this time the PC was totally unusable.

Fortunately I could do much of what I needed from my tablet.

My internet averages 75 Mbps per and runs up to 150Mbps per.

The PC is a 14 year old Dell 545 with Intel® Core™2 Q9400 Quad processors @ 2.66 ghz and 8 GB of RAM. Windows 10 has been running fine, with minor tweaking early on. It is not the fastest kid on the block but is should not take that much time to update.

BTW, the prior 2 updates have run smoothly and were fairly fast.

I like this update.The PC feels faster thanks to some of the production tips and so far all software and devices work.

I am a fan of the fast track but 14 hours is a bit much.

TGWOH

I had the same PC for years, but upgraded a year ago since it was really worn out.
Run now also WIN10 on a 2008 Latitude laptop with 4 GB.
This OS really runs fine on old hardware.

Never experienced such slow updated, IMO the problems are at the Microsoft servers.
You can enable downloads from other PC's within or out of your own network.

Apart from some minor settings losses no problems with 1903.

Like the audio setting MONO. Since I only hear from one side, finished with soldered wires for my headphone.

 

[stratman]

The PC is a 14 year old Dell 545 with Intel® Core™2 Q9400 Quad

This is at least part of why this major update took so long.

https://www.cpubenchmark.net/cpu.php?cpu=Intel+Core2+Quad+Q9400+@+2.66GHz&id=1045

Still, 14 hours is a horribly slow install time. There may be other issues, such as internet data transfer speed, minimal free hard drive space available, hard drive speed and/or failing components.

The PC feels faster

Many people comment the same. Windows 10 is the best MS OS, outliers exempted.

 

[palombian]

I had an SSD in the Inspiron.

 

[mikling]

Win 10 1903 has issues...or the supporting ecosystem has not caught up yet. I am also experiencing stuttering on Netflix both on the App and using MS Edge with subtitles on. I checked on the internet and sure enough, I am not alone. Gamers are also seeing stuttering on some games as well. The source of that can either be related or separate. I am also hearing the occasional dropout on streaming music as well this could be related but the rollback could take of this. This weekend I am rolling back my HTPCs with saved images. Macrium works like a champ here. Over the last 2-3 years I've had to do this over 20 times on various machines. Sure hope this is resolved by the end of the summer.

Palombian, don't feel bad. The time it takes to update will depend on the specific hardware and apps loaded on the machine. There is a huge difference between updating a Ryzen7 1800X with a Samsung M.2 960 EVO as compared to updating a FX8320 @4Ghz with a Samsung 860 EVO Sata. The latter took 2 hours whereas the Ryzen took less than 15 mins.... TO confirm the differences, it also took less time to update a Phenom X4 965 (older than FX8320) using only an older 120GB Sandisk SSD but with few apps loaded than the FX8320 system. My connection is rated at 250GB/s but I can peak at around 500! Get this though my old AMD AM2 system over a decade old now running a Phenom X3 720 updated in less than an hour using a cheap USB wireless adapter. It was a TPlink and cost less than $10 about 5 years ago! Definitely not an AC rated one.

 

[palombian]

...My connection is rated at 250GB/s...

I suppose you mean 250 Mbps (megabits per second).
I have here 100 Mbps from the phone company over copper wire.
This is already very fast, I did not have to wait long for the last Windows update.
Install time maybe 5-10 minutes.

But I had cleaned my OS SSD before.
Not sure if lack of disk space on SSD's had the same slowing down effect as on a hard disk.
On the latter it is easy explainable by excessive head movements and the fact that the data rate on the inner tracks is less.

IMO the hard disk is @TGWOH 's problem, not the CPU.
Never had 14 hrs on my Q9400 with an SSD.

PS: I have an i5-8600 now.

 

[stratman]

I have an i5-8600 now.

Friend has an i5 8400 with 8 GB RAM and an Samsung EVO SSD. It's impressive.

 

[palombian]

Friend has an i5 8400 with 8 GB RAM and an Samsung EVO SSD. It's impressive.

Indeed, and it was downplayed as a "cheap" processor.
6 cores helps a lot.
And Lightroom uses them all. I don't care about previews anymore, I evaluate my photo's directly in the editor.
Very glad I built this machine last september.
Only RAM was expensive then. Installed 16 GB, with 8 GB it is difficult to open a second editor within LR.
Memory price almost halved since.

 

[palombian]

I struggled 2 days with an issue caused by the 1909 update.

Every print instruction went fault needing the restart of the spooler service.
It was not my new printer messing up with the others, but it was an occasion to clean up all the old drivers.
No avail.
After uninstall of the 1909 update (KB4517145) everything was fine again.
First time this happens to me.
I blocked the updates for 14 days.

 

[Artur5]

I’m still running Win10-1803. Even if the system keeps telling me that the support for this version will end soon, I’m very reluctant to update ( I wouldn’t say upgrade... )
It’s not only about possible issues like yours but it’s the time consumed and hassle of replacing all the OS. There’s always something lost or changed : profiles, menus, screen appearance.. you need to recheck everything, In top of that, those bast..ds of Microsoft leave the old Win version lying there in a folder, usually 20-30 Gbytes of wasted space in the HD, that you can’t delete without considerable effort, because all the files and subfolders are protected.
One would think that after all this years they'd have learned to do things properly but they’re becoming worse and worse.

 

[palombian]

The nice thing of following the updates close is that you can easily step back just in case.
After some googling it was obvious the latest update caused the spool problem.

OTH, when you jump from 1803 to 1909 (won't find 1903 anymore soon) you risk to be faced with several issues you can't track down.

I still have 1/3 free space on my 250 GB SSD for the OS, the extra space to keep the previous version never has been an issue.

Strange enough many on this forum are very risk averse to software changes, while refilling is a very risky business in se.