Windows 10 Version 1809 Update Download
Lorri Dent
Find information on known issues and the servicing status for Windows 10, version 1809 and Windows Server 2019. For immediate help with Windows update issues, click here if you are using a Windows device to open the Get Help app or go to support.microsoft.com. Follow @WindowsUpdate on X (formerly Twitter) for Windows release health updates. If you are an IT administrator and want to programmatically get information from this page, use the Windows Updates API in Microsoft Graph.
Search, browse, or ask a question on the Microsoft Support Community. If you are an IT pro supporting an organization, visit Windows release health on the Microsoft 365 admin center for additional details.
This site is available in 11 languages: English, Chinese Traditional, Chinese Simplified, French (France), German, Italian, Japanese, Korean, Portuguese (Brazil), Russian, and Spanish (Spain). All text will appear in English if your browser default language is not one of the 11 supported languages. To manually change the display language, scroll down to the bottom of this page, click on the current language displayed on the bottom left of the page, and select one of the 11 supported languages from the list.
I have a Windows 10 Pro v1809, OS build 17763.1339. According to the MS docs, this is the latest update to version 1809.I'm not sure why feature updates are not being shown via Windows update. I have not disabled/ paused updates. I don't see the option to select "Choose when updates are installed" from Windows Update > Advanced Options. Instead I had to manual set those from the Group Policy editor.
Download the preferred version using the TechBench link and install while logged in. You should be able to perform the upgrade manually, without a clean install.Please note that your version is up-to-date before upgrading to next version.Eg: If you are trying to move from version 1809 to 1909, make sure your currently at version 1809 build 17763.1339, the latest as of today. I had trouble when my build was not up-to-date. Check version history here).
For a couple of days ago i decided to do a clean install of 1809 and was so sure that i downloaded the 1809 build from Microsoft. I failed to see that the version i actually downloaded was 1803. Confirmation bias...?
So in the end got two surprises: The first being that i installed the wrong version, 1803, of Windows and the second one was that OneNote is now removed from Office 365/Office 2019. I could download OneNote 2016 separatly but i dont understand why Microsoft drops it and promts the end user to use the OneNote app in Win 10 when it cannot open local OneNote books. The desktop version of OneNote EOL. I still wonder why...
I hope that this is not the future of software companys with subscriptions, that they just withdraw applications without much info about why the do it. I remember when several version of Premiere Pro/AME/Ae got withdrawn when CC 2018 were released.
because the file system changed to store documents in skydrive onedrive [what ever its called this week] and Microsoft wants people to use that service so they force it as part of the upgrade list i.e, docs are moved to onedrive which by default lives on the c drive under the users profile... yes what could possibly go wrong right
I look after the four computers and one shared printer at the Citizens Advice Bureau where I volunteer. We recently got four new HP ProDesk systems with Windows 10, and a discounted Office 2016 volume license. They'd been working fine for about two weeks when one went into a non recoverable startup loop with a error message that resolved to Windows Update.
So I fixed that, and was told another had done the same thing. While I was there fixing the second system, a third failed with the same thing! I have them all with a recover image in case they fail again, but I still don't know why they are failing, so all I have done so far is pause Windows updates for the MAX (sorry Dave ) allowed 35 days. I look forward to reading the PC World article to see if it helps.
Trevor, following your advice, I also tried to pause Windows updates this morning for the MAX allowed of 35 days, and while I was looking for pause, which I never found, Windows updated itself to 1808.
Jane I am only pausing updates on the CAB computers until I can work out what is going wrong with them. The four Windows systems at home are all still on auto update. Your Advanced options are different to mine.
The two desktop systems at home are still on Windows 10 1803, and I am now inclined to keep them that way. I have a Shadow Protect license for my main desktop, but I haven't got round to creating boot drive image, and it would be a royal PITA to have it do the same thing as the CAB computers. I strongly suspect that the CAB computer problem is to do with them being HP Prodesk. They came with Windows 7 and a bunch of DVDs including Windows 10, but I had to change the BIOS in order to install Windows 10. I can't put my hands on the paperwork for that right now, and I don't remember off the top of my head what I had to change in the BIOS, but I do know I didn't change it back, and it might be that it would best if had been changed back. It's a ten minute job to fix the CAB systems if they break again, now I have an OS image to reset to, but I still have to reinstall Office. I did worry about Office running out of Activations, but it obviously recognised the hardware, and didn't even ask for a serial number. Now wouldn't it be nice if the pre-CC Photoshop versions had done that. All moot now.. Blimey, I just wrote off those thousands (millions?) of people who still use earlier versions.
Taking John's thread off topic, I wonder how many unused earlier version licenses we have between us? I've just looked, and I have three versions of Photoshop, two Premiere Pro, and an InDesign all registered and currently unused. At the time, I bet we all thought we were using amazing software... The best in the world. It seems a shame that that software now goes unused. Old versions of Premiere Pro would have limited use because of their outdated CODECs, and some of my earlier Adobe software is 32 bit, but it did the job for us back in the day. [1]
[1] I just reminded myself with the 'back in the day' comment, which is something Jack Reacher would say. Two days, as I type this, till the next Reacher book 'Past Tense' is released. There are an awful lot of reviews for this book considering has not been released yet.
I know that Hollywood "takes liberties" when converting a book to a movie, but after reading one Jack Reacher novel it really irritated me that the LARGE man described in the book was played by the not large at all Tom Cruise
There was quite a backlash about this back at the time. It's sad to say, but my impression is that Lee Child has become too focused on the bottom line. I still look forward to each new Reacher book, but Past Tense was disappointing. [SPOILER] one of the most significant plot lines seemed to just fizzle out near the end of the book. It was like Lee Child had fulfilled is contractual obligation to his publisher, so he slipped in a paragraph about some serious bad guys getting bored so they went home.
But aside from that, I honestly can't recall ever having problems with any Windows update. Clean up what, exactly? Compared to almost any other software company, Microsoft has a stellar record. "No Windows 10 update has been without some major problem" - what problems are they talking about? I've certainly not seen them.
But... other people have had problems, and Microsoft does sometimes have to issue a patch after an update, so the general idea of the article contains a few grains of truth about not enough testing being done
That was a Photoshop bug, I remember it well, I was in the Photoshop forum daily at the time. It was fixed by a Photoshop update, the registry edit was a temporary workaround until the update was released. When that update came out, users were required to reverse the registry edit.
"I'm glad the fix helped. Michel is right that I don't have time to help everyone personally -- a video with the workaround for this issue had 54,000 views as of yesterday. Needless to say I wouldn't have been able to help over 50,000 people personally."
For the record, while the bug was corrected rapidly in Photoshop, it was only solved in last september in Elements. And you know what? by editing the registry when installing the last (paying) version, PSE 2019. Which leaves the users of the three older versions with the registry edit as the only working solution.
In the fifty or so posts I had to write to angry users in the Elements forum, I made it clear that I understand the need for Microcoft to move ahead. My critique was about the impossibility to roll back to the previous Win 10 build. And for Apple, just have a look at the Elements user to user forum or the feedback forum about the introduction of Mojave...
Microsoft Windows is designed as a general 'one size fits all' system... you can roll it back if you have set it up to allow that option and there are a few different senarios like virtual builds inside Hyper-v or 3rd party backup software
yes the current Windows build has major problems that effect a small % of the millions of worldwide users and not just with Adobe software and yes Apple Mac is no saint so the people that learn to understand their systems and adapt when bugs stop their work flows will survive and the ones that assume Adobe, Microsoft or Apple [& any other big company] have it under control will lose out
c80f0f1006