What Happens To Those Of Us Who Can't Update Beyond 1709?

Thanks for those suggestions. Food for thought. ;-)

ignatzatsonic said:

That's a 10 year old CPU. A powerhouse when it was introduced, but I wonder how old a CPU can be and still accept Windows 10?

I have v1803 working fine on 2 old 2006 PCs but they won't auto update to v1809. I plan to try updating using the Media Creation Tool soon. I'm not bothered if they don't update since I only keep them as museum exhibits.

Update: I just updated one of those 2006 PCs to v1809 using a USB update drive generated by the Media Creation Tools. There were no problems despite the update not being offered via Windows Update

Steve C said:

I have v1803 working fine on 2 old 2006 PCs but they won't auto update to v1809. I plan to try updating using the Media Creation Tool soon. I'm not bothered if they don't update since I only keep them as museum exhibits.

I wish I could say the same. but the only museum exhibit around this place is me....at the moment...!!

zbook said:

These are some options:

1) Perform a reset save files
Reset Windows 10
2) Perform a custom install
Custom Install Windows 10
3) Perform a clean install
Clean Install Windows 10
4) Troubleshoot

Microsoft has free support for failure to upgrade.
The highest level is tier 3.
They have a log collector.


In the prior thread steps had failed; consider clean install


See Windows lifecycle:
https://support.microsoft.com/en-us/...cle-fact-sheet

They still offer direct support, but only for upgrade failures? It used to be for any Windows Update issues.
Thanks I'll try it when I can.

Well, then either my logs (posted elsewhere) aren't giving the full picture or someone is not reading them right. I've got to the point now where I have given up.
I'll be forced to buy a new machine.
Again I think @Microsoft are negligent in not providing exact reasons for update failures.
I'm an ex-MVP and I gave up trying to help others at that time because I got so little backing from them since Bill Gates left the top position.
Everything has become hit-and-miss since the changes at the top.
I'll revisit this when the time comes that my Windows 7 is no longer supported.
Thanks to all who have helped.

Well, then either my logs (posted elsewhere) aren't giving the full picture

Peter,

That is perfectly possible. After my Ver 1803 failures on my problem computer the logs were still as they had been beforehand.
- The undoing of the update attempt must have undone the log changes [if they had been changed, that is] - yes, that does not make any sense to me either.
- In my case, clean install attempts failed as well.

I do still wonder, however, if that setupdiag result you referred to would match anything in the driver logs I suggested a batch file for.

Denis

sygnus21 said:

Feel how you want but many here have installed versions of 10 beyond 1709 without issue. And Windows 10 definitely works with hardware older than 2 years. I know this doesn't help you but those are the facts.

And for the record, I too have had issues getting newer updates installed on my old Asus laptop, but a clean install solved those issues. You might consider backing up your files and doing the same... clean install.

Oh, and looking at your specs, that motherboard and CPU is certainly far beyond 2 years so... That x58 board goes back to 2010. That's far beyond a 2 year old system.

Good luck.

Tried that.....and some 24 other attempts after disabling or disconnecting just about everything on the darn machine.
It's always the same safe_os boot - type error - ends in 017 so it's a driver. What driver only God seemingly knows.

Try3 said:

Peter,

That is perfectly possible. After my Ver 1803 failures on my problem computer the logs were still as they had been beforehand.
- The undoing of the update attempt must have undone the log changes [if they had been changed, that is] - yes, that does not make any sense to me either.
- In my case, clean install attempts failed as well.

I do still wonder, however, if that setupdiag result you referred to would match anything in the driver logs I suggested a batch file for.

Denis

I could try again. Tell me again what I have to do.