Today we are resuming the rollout of the latest Windows 10 feature update—Windows 10, version 1809—via the Software Download Center (via Update Assistant or the Media Creation Tool), Windows Server Update Services (WSUS), and Windows Update for Business. Windows 10, version 1809 is also now available on the Volume Licensing Service Center (VLSC); however, it may take a few hours to be visible for all editions in all languages. Windows 10, version 1809 will be available for Visual Studio Subscriptions (formerly MSDN Subscriptions) by the end of this week.

As noted in John Cable’s blog post, we have changed the “born on” date accordingly and today marks the start of the 30-month support lifecycle for the Enterprise and Education editions of Windows 10, version 1809; and the 18-month support lifecycle for Windows 10 Pro and Windows 10 Pro for Workstation. For more details on currently supported versions and support end dates, see the Windows 10 lifecycle fact sheet and the Windows 10 release information page.

In addition to the new capabilities for IT pros, new versions of the tools you use to manage and deploy updates and devices are also now available. These include:

  • Windows Assessment and Deployment Kit (Windows ADK) for Windows 10, version 1809 – Tools to help you customize Windows images for large-scale deployments and test the quality and performance of your systems, added components, and applications running on those systems.
  • Windows PE add-on for the Windows ADK – Starting with Windows 10, version 1809, Windows Preinstallation Environment (PE) is released separately from the ADK. To add Windows PE to your ADK installation, download the Windows PE add-on and run the included installer after installing the ADK. This change enables post-RTM updates to the tools in the ADK. After running the installer for the Windows PE add-on, the WinPE files will be in the same location as they were in previous installations of the ADK.
  • Security baseline for Windows 10, version 1809 and Windows Server 2019 – Importable Group Policy Objects (GPOs), a PowerShell script for applying the GPOs to local policy, custom ADMX files for Group Policy settings, and documentation in spreadsheet form and as a Policy Analyzer file (MSFT-Win10-v1809-RS5-WS2019-DRAFT.PolicyRules).
  • Windows 10 Enterprise Evaluation – Free 90-day evaluation designed to help you test Windows 10 Enterprise (or Windows 10 Enterprise LTSC 2019) in your environment. Available in 10 languages as 32-bit or 64-bit ISOs.
  • Remote Server Administration Tools (RSAT) – Starting with Windows 10, version 1809, RSAT is included as a set of "Features on Demand" in Windows 10 itself. Go to "Manage optional features" in Settings and click "Add a feature" to see the list of available RSAT tools.
  • Group Policy Settings Reference – Policy settings for computer and user configurations included in the Administrative template files delivered with Windows 10, version 1809.
  • Administrative Templates (.admx) for Windows 10, version 1809 – Administrative template files to help you manage registry-based policy settings by populating policy settings in the UI of your favorite Group Policy management tool.

What about LTSC?

If your organization is currently utilizing the Long-Term Servicing Channel (LTSC), Windows 10 Enterprise LTSC 2019 is also now available on the Volume Licensing Service Center (VLSC).

What about partner availability?

Windows 10 Enterprise, version 1809 will be available on the Microsoft Partner Network (MPN) on November 14th, with all other editions (including Windows 10 Enterprise LTSC 2019) following on November 20th. Windows 10 Pro, version 1809 will be available to those with Microsoft Action Pack Subscriptions (MAPS) today, with all other editions following on November 20th.

What about Windows Server 2019?

Today we are also resuming availability of Windows Server 2019 and Windows Server, version 1809, globally to all Volume License customers. Please see the Windows Server Blog for more details.

When will I see Windows 10, version 1809 in Upgrade Readiness?

Windows 10 is now available as a “Target version to be evaluated” drop-down in Windows Analytics Upgrade Readiness, enabling you to obtain guidance and insights into application and driver compatibility issues, with suggested fixes, that may affect your migration to Windows 10, version 1809 from Windows 7, Windows 8.1, or a previous version of Windows 10.


Where can I learn more?

To ensure that you have the ability to experience the latest features and capabilities for yourself and your organization, our webcast on “What’s new in Windows 10, version 1809 for IT pros” has been rescheduled for 10:00 a.m. Pacific Time, Wednesday, November 28th. During this one-hour webcast, my colleague Nic Fillingham and I will walk you through the changes in this feature update, the logic behind them, and, most importantly, how to use these improvements to speed up your deployments and more easily manage your devices. Register today to secure your spot.


We’ll then follow up with a Windows 10 IT Pro AMA on Tech Community from 9:00-10:00 a.m. Pacific Time on Thursday, December 13th. This event will be your opportunity to ask questions and get answers from members of the product and engineering teams for Windows, Windows Defender ATP, Microsoft Intune, and System Center Configuration Manager. Out of respect for our international IT pro community, we’ll open the Windows 10 AMA space in advance so that everyone has a chance to participate. All you have to do is be a member of the Microsoft Tech Community. I hope you will be able to join us.


Continue the conversation. Find best practices. Bookmark the Windows 10 Tech Community.

Looking for support? Visit the Windows 10 IT pro forums.

Frequent Contributor
Thank you for including the blurb on MPN availability! We partners appreciate the shout out :) Also like the nod to Upgrade Readiness, we use that heavily for each major update.
Super Contributor

Crossing fingers, hopefully second time is a charm :)

For those who want direct download links of the new 1809 ISO files, you can get them here: Nawzil.com/1809

Super Contributor

Or one can change browser agent to say Android and download the ISO from https://www.microsoft.com/en-gb/software-download/windows10ISO (maybe someday MS will remove this stupid block and allow one to choose to download ISO or media creation tool on Windows).

Not applicable

Why no guidance for those who downloaded and deployed the original Windows 10 version 1809?

Senior Member


Just an FYI ...


MSDATASHAPE Provider got broken with 1809, prior to the feature update it worked... also downloaded today the KB4467708 for the 1809 and it's still broken ...

Also I have been testing it in a machine with a build of windows insider and it is also broken (also affects windows server 2019)


I'm leaving here the feedback hub link: https://aka.ms/AA35fgd


Links to other complaining about the same:

MSDN: MSDataShape broken on upgrade to Windows 10 Feature Update 1809
StackOverflow: MSDataShape error, broken on upgrade to Windows 10 Feature Update 1809
MSDN: PLEASE READ: Problem with ADO & VACHAR in windows 10 Update 1809 and Server 2019


I installed 1809 upon release. Do I need to reinstall the re-release?



Super Contributor

New ISO installs version 1809, build 17763.107. It then should update to 17763.134 with a regular monthly CU update. So, those who have updated to 1809 previously should be covered after they are updated to that latest CU update. Do check for updates, install latest updates, reboot and check your version with 'winver' command. (November 13 information https://www.microsoft.com/en-us/itpro/windows-10/release-information)

Super Contributor

So, 1809 reappeared in WSUS again. But just like with a first release it only shows a combined version. No separate x86 and x64 versions. I don't get it. MS happily announces that admins can deploy smaller (by half) updates, but only provided separate installs for older builds (1709, 1803), but not for the current one. Why? Should we always deploy huge installs and not get benefit from this great feature if we are staying with current versions all the time. Is it designed only for those who update only after 6-12 months after a release? Where is the agility and Windows as a service with such approach?

The VLSC still says "Windows 10 Enterprise, version 1809 (updated Sept '18)", when you click on Description.


Yet at the top right of the Description it says "Release Date 11/13/2018"


Have the ISO's been updated ?


Can see when extracted that the file dates are 30th October, so presume they have.

New Contributor

I echo the issue where VLSC states the ISO is from Sept '18. Has anyone tested the ISO from VLSC to see if it is in fact the older build or if Microsoft has released an updated ISO? 

Super Contributor

You can try it yourself. Download that ISO, install in some VM without a network access and check build version with 'winver' command. It should be 17763.107 (if network is available it will automatically update to 134 during the setup).

Occasional Contributor

When will 1809 be available for Visual Studio subscriber? It has been the end of this week... but nothing appeared.

Frequent Visitor

why reinstall itself:

Annotation 2018-11-17 233437.jpg

Occasional Visitor

Will we see 1809 on Visual Studio Subscription this Sunday?

Established Member

Sunday but nothing on Visual Studio Subscription: what's happening?



Windows 10, version 1809 will be available for Visual Studio Subscriptions (formerly MSDN Subscriptions) by the end of this week.

Any update on this?


Established Member

Please, Microsoft, tell us something about this strange thing: why is it "next week monday" and nothing is visible inside Visual Studio Subscription?


Thank you.

Frequent Contributor
Win10 1809 was available for MPN download when promised, but Windows Server 2019 still isn't available for download there.
Established Member

@Paul Youngberg  thank you, but i'm talking about Visual Studio Subscription (ex MSDN): from the end of the previous week.

Frequent Contributor
Unrelated comment
Community Manager

@Kexy Biscuit@H F@Stefano Zambonin@Gabe Jones - Thanks for your patience. You should see Windows 10, version 1809 (and Windows Server 2019) in Visual Studio Subscriptions now!

Community Manager

@Shane Alexander and @Corey Richardson - Yes, the ISOs in the VLSC have been updated. We're working to get that description updated as well.

Established Member

@Heather Poulsenthank you so much. Yes, now i see it.

A little bit of more communication should be better.

I don't understand why i'm listed as null null even with profile updated...

I see that there are several problem even in mpn.

Thank you.




Frequent Contributor

@Heather Poulsenany update on Windows Server 2019 for MPN members? Thank you!


EDIT: We have liftoff! All the 2019 SKUs showed up this morning 11/20/18. Thanks Heather if you had a part to play in this!


Does Win 10 LTSC 2019 use the same group policy settings as Win 10 1809?

Community Manager

@sharonle214 - Yes. There are a few more policy settings that apply to Windows 10, version 1809 as LTSC does not contain all of the same features, but for the features LTSC does include, the same policy settings apply.


@Freddy Vendas , we now fully understand what caused the break in MSDataShape. We are in planning for how and when to best release a fix.


Senior Member
@ScotBren, thank you for the replay and the feedback. I eagerly await for the fix release.
Occasional Visitor

@ScotBren,Hello.  Wanted to see if there's any movement on the fix for MSDataShape in the last month?  Or if there's a beta fix we can try.  Thank you.


@Joseph_JS, Yes, there is "movement", albeit slower than anyone hopes. There have been a couple of dozen emails going back and forth just this week discussing the fix to both 19H1 and back-porting a fix to RS5. I have no commitments I can make yet about when it will be released. This issue is still very much on my radar, and I am not giving up the fight to get the fix released as soon as we can. Obviously, as with anything at this scope, there are always competing priorities to juggle.



Ha! 45 minutes after I post my "we don't know yet" message above, I get an email that says the fix is approved for RS5 update in 4C. If it doesn't happen on schedule as expected, please don't hunt me down or threaten my family.  But the current expectation is that in the third week of April ("4C"), there will be a Windows update for Windows 10 1809 (aka "RS5").

It will not likely be obvious that the issue has been fixed, as the module being updated is the old C RunTime DLL MSVCRT.dll. However, once the patches to MSVCRT.dll are done, the MSDataShape Provider should properly handle length values again.