How to get the Windows 10 May 2019 Update version 1903

JMacleod26 said:

I suppose so? I honestly have no idea what it does beyond make it easier to share data between multiple partitions, I think.

Google is your friend!

I didn't know either but I do have some Dell PCs to update so have a look at these links:

https://www.dell.com/support/article...ftware?lang=en

https://www.dell.com/support/home/uk...driverid=02rn8

Windows 10 1903 Update Blocked by Old Intel Rapid Storage Drivers

jimbo45 said:

Hi there
If really old Intel computers e.g those with Pentium IV and that sort of thing install 1903 then why on earth does Windows try and install stuff for incompatible hardware -- Windows can run with a load of "Unknown devices" -- just do that and then let people or even Ms try and sort out remaining problems where applicable.

I can't understand how people are taught to code these days -- surely it would be simple at Windows Driver install time to have a piece of code saying - check device "X" -- if return code come back OK then install, if there's any error just don't install / update the device driver.

I know it's not always as simple as that but I can't believe some preliminary hardware checking can't be dome by the install process.

If I'm trying out a new release I'd much rather have a version missing a few devices which I can then do further analysis on than just have the whole process error out. Not sure what typical people think about this but I would rather have a partially working system than a totally broken one.

For those who don't want this --then at least you know what devices are a problem and can roll back easily enough via windows.old if they haven't taken a backup before updating / installing.

I think problem is people are too used to looking for instant answers rather than try and understand the process and logic behind the operation -- this might be OK for end users but developers should have a better understanding of the process.

Cheers
jimbo

Couldn't agree more

jimbo45 said:

Hi there
If really old Intel computers e.g those with Pentium IV and that sort of thing install 1903 then why on earth does Windows try and install stuff for incompatible hardware -- Windows can run with a load of "Unknown devices" -- just do that and then let people or even Ms try and sort out remaining problems where applicable.

I can't understand how people are taught to code these days -- surely it would be simple at Windows Driver install time to have a piece of code saying - check device "X" -- if return code come back OK then install, if there's any error just don't install / update the device driver.

I know it's not always as simple as that but I can't believe some preliminary hardware checking can't be dome by the install process.

If I'm trying out a new release I'd much rather have a version missing a few devices which I can then do further analysis on than just have the whole process error out. Not sure what typical people think about this but I would rather have a partially working system than a totally broken one.

For those who don't want this --then at least you know what devices are a problem and can roll back easily enough via windows.old if they haven't taken a backup before updating / installing.

I think problem is people are too used to looking for instant answers rather than try and understand the process and logic behind the operation -- this might be OK for end users but developers should have a better understanding of the process.

Cheers
jimbo

It may be looking at wrong drivers or their data base of drivers is not very good. All my drivers are newest and best for system and I still had to download ISO and force upgrade which went on without a hitch and is updating regularly.

The problem is that MS sometimes fix driver issues on the OS level. Then the driver developers keeps updating their repository with the OS fix enabled. When MS release a new build, it might happen that the OS-level fix has been removed, or forgotten, leading to issues with drivers, that may render the OS completely unusable. I think Microsoft should focus more on differentiating what should be fixed on the OS-level and what is actually a real driver bug. This way we get properly programmed drivers.