My PC was ready for 2004 update, but now it isn't anymore.

You mentioned my post, but I think you missed my point.

Damun said:

Once the update comes back i think that i'll give it a couple of weeks or more, before instaling it - just to make sure that most issues have been solved.

I'm inclined to completely skip these updates because, as I said, they offer risk and no benefit. I'm running 1809. (My brand-new work laptop is at 1803.) I have no intention of "upgrading" because there is no upgrade. There's only risk.

- I don't need new metro apps.
- I don't need an even more three-dimensional paint program.
- I don't need to replace Skype with super-Skype.
- I don't need more funny variations on the start menu or the taskbar.

Do you?

I think it's hopeless:
- MS has exhausted its innovative spark.
- Bill Gates is retired.
- The cloud gets their attention because that's where the money is.

When this PC dies I'll get Windows 11 in its replacement.
Until then I'm freezing at 1809. No more broken updates for me.

One potential issue with remaining on the older revisions of Windows 10 is related to the new support cycle, this is either 18 or 30 Months, not the 5 years +5 years extended support of previous Microsoft OS's

The shorter life cycle at present only applies to Microsoft drivers and OS features, so those using mostly third party software should have less of an issue, unless the 3rd part manufactures /programmers decide to align with Microsoft's schedules

   Note

The The Long-Term Servicing Channel (LTSC) provides a ten year support cycle if you are on a Volume licence agreement, or can run the same base OS revision and have access to the LTSC updates

.

It is as always a personal choice as to what any individual does, It may be better to consider upgrading when your current version reaches, EOS, (end of support), even if you decide to ignore the intermediate releases on a Risk Vs Gain basis, which is a valid reason

Home version of Windows has much less control over updates to the OS, it is Microsoft's attempt to cater for the Smartphone Generation, where the device does everything for the user, whilst they play on Candy Crush, and take Selfies

There are ways to manually override the auto updates, there are many on this site in the Tutorials sections, so you can retain your chosen version after EOS although the potential issues are as stated.

The system for Microsoft updates has changed recently, after several embarrassing issues with updates,.

They now only offer upgrades to systems that meet a set level as to hardware and software, if the upgrade is offered but meets an issue ( known or not), during install the upgrade is aborted and will not be offered again until the issue found has be sorted out

The user can of course if they wish, override Microsoft's check system, download the installer and manually install the upgrade, but this is at their own risk as it could well lead to data loss in future use

Snip from Nigel's post:

They now only offer upgrades to systems that meet a set level as to hardware and software, if the upgrade is offered but meets an issue ( known or not), during install the upgrade is aborted and will not be offered again until the issue found has be sorted out.


All fine and good. But would it be too much to ask from MS if they gave us a hint what the issue or block is? They tell the user "There is nothing you need to do". Well, I will submit there are plenty of users, thousands on TF alone, that if given the chance could get the horse back up on it's feet!

If the issue is fixable by replacement of a file with another existing file, I agree that this would be a way to speed things up.

However, if there is a minor or major error in the actual coding, how many users would be able to do anything about it? they would need access to the non compiled code, the compiler software, plus all the documentation explaining what does what, then assuming that they have enough experience to see the issue, develop a fix and then code it.

We can all change out a file, or change a setting in the registry, but the actual coding of an OS is not something many could even grasp the complexities, even Microsoft themselves would use specialists in teams

Agreed. I was thinking more along the lines of fixing a bad driver, some DISM fixes....... non-code issues.

Drivers are an old problem for any OS, especially as in the case of Microsoft who do not write the Drivers. if there is an issue due to a 3rd party driver not being compatible with a new Windows upgrade version Microsoft has to get the hardware company to make the changes to make the driver comply and then take it through the compliance system to ensure it does not break anything else.

It is not up to Microsoft to fix the issue by changing their own code as this is likely to break those systems that were supplied with correctly coded drivers

These issues are often the ones that mean that a specific system cannot be upgraded until the following bug fix upgrade or even the next annual upgrade (assuming we are still on this "new" system)

Hence the similar message for several of the known issues....

To safeguard your update experience, we have applied a compatibility hold on Windows 10 devices with affected Realtek Bluetooth radio drivers installed from being offered Windows 10, version 2004 or Windows Server, version 2004 until the driver has been updated.

I personally think that that type of statement, that points the blame elsewhere, is overdue. how many times do we see bad third party drivers causing problems :

This sort of thing may embarrass the developers enough to get the issue sorted - which has to be a good thing for us as users