Windows 10: I am having trouble updating my win 10 version 1803 regarding it's life cycle ending?

I am having trouble updating my win 10 version 1803 regarding it's life cycle ending?

:)

 

What happens when 1803 reaches end of life date

Unless you've taken steps to block/defer feature and/or quality updates, then by now you should see an 'end of life' warning and a 'Download and install now' option for the Feature Update. I see this in 1803 on my test machine:





Some however are seeing a 'not quite ready...' message (usually due the 3rd-party drivers/software that needs an update).




Device not ready to update to 1903


As the end of life approaches an 'un-tweaked' install of 1803 should be automatically updated to 1903 through Windows Update. This has already started....


Microsoft now auto updating Windows 10 version 1803 and older to 1903

If you have 'tweaked' your system in any way to put off updates, then undo those tweaks now. After clicking 'Check for updates' it should either say 'download and install now' if it passes initial compatibility checks, or 'not quite ready...' if it doesn't.

 

Unable to update Windows 10 Pro version 1709 to 1803

Have made several attempts to update Windows 10 version 1709 to the latest version 1803 and have not been successful.

I've done the following per some suggestions found online:

• Updated drivers
• Ran the Trouble Shooter for Windows 10 (Errors found were shown to be "Fixed" per the tool)
• Unplugged the printer

Although not at every attempt, I have received the following errors:

• 0xc1900101
• 0x80070643

Can someone please advise me as to what the errors are and provide me with the steps to update Windows.

Thank you.

 

Internet disconnect Win 10 Version 1803

I am trying to find help with internet disconnect on Win 10 Version 1803 shortly after making a connection through the trouble shooter. I have looked for an update to my wireless adapter as instructed in the only information available wit no relief. I
am using Version 1803. Others have posted the same issue but no fix is listed