[1809, ou] Windows 10 v1809 released

[Arthur]

I think patch Tuesday will be the release date.

You're right. [emoji846]

 

It is...

 

[ADMaster]

Will it be renamed to 1811?

 

[free780]

Or 11/18 for countries that put the date in the correct order.

 

:runs away from americans:

[psydii]

I’m looking forward to the 2003 release.

[mavhc]

Should always be Year then Month, then Day, Hour, Minute, Second etc.

 

1803 was released in April, so no problem there, except they did name it the October update, hubris.

[ADMaster]

I use ISO 8601 in file names and such, all the windows 10 releases have followed that standard.

 

I think 2003 might break older applications, but we shall see. It just might have to be delayed a month.

[Zoom7000]

Nothing on VLSC yet, I think we need to wait for Redmond to wake up

[Jaan]

I use ISO 8601 in file names and such, all the windows 10 releases have followed that standard.

 

I think 2003 might break older applications, but we shall see. It just might have to be delayed a month.

 

Shouldn't they just call it Windows X?

 

or

 

Super Windows X v1809.256.21452.2156 EX plus alpha arcade edition

[Arthur]

Nothing on VLSC yet, I think we need to wait for Redmond to wake up

I wouldn't be surprised if it was released after we've all gone home today.

[Arthur]

I think 2003 might break older applications, but we shall see.

Microsoft switched to a different naming convention for the next releases (19H1, 19H2 etc.) for exactly that reason (which was the same reason Windows 10 wasn't called Windows 9).

Edited November 13, 2018 by Arthur

[mavhc]

In WSUS it's called Windows (v10), guess at some point they might drop the version number

[Arthur]

Resuming the rollout of the Windows 10 October 2018 Update

 

In early October, we paused the rollout of the Windows 10 October 2018 Update as we investigated isolated reports of users missing files after updating. We take any case of data loss seriously, and as I noted on 9 October, we have thoroughly investigated and resolved all related issues.

 

In addition to extensive internal validation, we have taken time to closely monitor feedback and diagnostic data from our Windows Insiders and from the millions of devices on the Windows 10 October Update, and we have no further evidence of data loss. Based on this data, today we are beginning the re-release of the October Update by making it available via media and to advanced users who seek to manually check for updates.

 

As with all Windows releases, we will continue to carefully study the results, feedback and diagnostic data before we begin offering the update in phases to more devices in the coming weeks and months.

 

While the April Update had the fastest Windows 10 update rollout velocity, we are taking a more measured approach with the October Update, slowing our rollout to more carefully study device health data. We will offer the October Update to users via Windows Update when data shows your device is ready and you will have a great experience. If we detect that your device may have an issue, such as an application incompatibility, we will not install the update until that issue is resolved, even if you “Check for updates,” so you avoid encountering any known problems. For those advanced users seeking to install the update early by manually using “Check for updates” in settings, know that we are slowly throttling up this availability, while we carefully monitor data and feedback.

 

For our commercial customers, the re-release date of the Windows 10 version 1809 will also be today, November 13, 2018 (this includes Windows Server 2019 and Windows Server, version 1809). This date marks the revised start of the servicing timeline for the Semi-Annual Channel (“Targeted”) release. As previously announced and beginning with this release, feature updates that release around September will have a 30-month servicing timeline. Just as we phase our consumer rollout, we recommend IT administrators begin to validate that apps, devices and infrastructure used by their organization work well with the new release before broadly deploying. Windows 10, version 1809 is now available through Windows Server Update Services, Windows Update for Business and System Center Configuration Manager’s phased deployment. For additional information please see the latest IT Pro Blog.

 

Windows 10 Quality approach for a complex ecosystem

 

Today we are re-releasing the October 2018 Update after pausing to investigate a small but serious issue. This is the first time in Windows 10’s “Windows as a Service” history that we have taken such an action, and as such it has naturally led to questions about the work we do to test and validate Windows quality before we begin rolling it out broadly.

 

While our measurements of quality show improving trends on aggregate for each successive Windows 10 release, if a single customer experiences an issue with any of our updates, we take it seriously. Today, I will share an overview of how we work to continuously improve the quality of Windows and our Windows as a Service approach. As part of our commitment to being more transparent about our approach to quality, this blog will be the first in a series of more in-depth explanations of the work we do to deliver quality in our Windows releases.

 

[...]

 

Just the beginning…

We are working on many fronts to ensure our customers have the best, most secure experience on Windows. While we do see positive trends, we also hear clearly the voices of our users who are facing frustrating issues, and we pledge to do more. We will up our effort to improve our ability to prevent issues and our ability to respond quickly and openly when issues do arise. We intend to leverage all the tools we have today and focus on new quality-focused innovation across product design, development, validation and delivery. We look forward to sharing more about our approach to quality and emerging quality-focused innovation in future posts.

 

https://support.microsoft.com/en-gb/help/4464455

 

This update includes quality improvements. No new operating system features are being introduced in this update. Key changes include:

 

• Addresses an issue that incorrectly implies that user policies have not been applied after configuring a user rights Group Policy setting. Reporting tools, such as RSOP.MSC or Gpresult.exe /h, do not show the user rights policies or display a red “X” instead.
  
• Addresses an issue that degrades Internet Explorer performance when you use roaming profiles or you don't use the Microsoft Compatibility List.
  
• Addresses additional issues with updated time zone information.
  
• Addresses an issue that causes a black screen to appear after turning on the display on some servers.
  
• Addresses an issue that causes a long delay in taking a photo using the Camera app in certain lighting conditions.
  
• Addresses a performance issue with vSwitch on network interface cards (NIC) that do not support Large Send Offload (LSO) and Checksum Offload (CSO).
  
• Addresses an issue that may cause applications to lose IPv4 connectivity when IPv6 is unbound.
  
• Addresses an issue that may break connectivity on guest VMs on the server when applications inject the low-resource flag on packets.
  

If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device.

Edited November 13, 2018 by Arthur

[Arthur]

It's on VLSC too!

 

[CHiLL]

I've got it downloading now. Looks like everyone else is too, 1MB download speeds!

[ADMaster]

My VLSC says the ISO was updated Sept '18 does that mean this iso doesn't have the data loss bugs fixed?

Do I just need to patch the wim before deployment?

 

[Arthur]

My VLSC says the ISO was updated Sept '18 does that mean this iso doesn't have the data loss bugs fixed?

The Sept. 18 ISO on VLSC that was released today (13th November) is build 17763.107 a.k.a. October 2018 Update 2.

 

https://twitter.com/WZorNET/status/1062445751517749248

 

Microsoft always makes it as confusing as possible!

 

https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-10-version-1809-rollout-resumes-now-available-on-VLSC/ba-p/284217

 

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.

 

[...]

 

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. The Administrative Templates package usually ships within a few weeks after release. In the meantime, you can install Windows 10, version 1809 and copy out the windir\PolicyDefinitions directory to another system.

Edited November 13, 2018 by Arthur

[mavhc]

Win10_1809Oct_EnglishInternational_x64.iso the Oct seems to indicate it's the fixed version.

 

My sha256 is 3bd9223e44bc64d2a19c4522257524b5d2021ba4ba663be6d9e8df80dbe46c6d

Edited November 13, 2018 by mavhc

[Arthur]

Win10_1809Oct_EnglishInternational_x64.iso the Oct seems to indicate it's the fixed version.

 

My sha256 is 3bd9223e44bc64d2a19c4522257524b5d2021ba4ba663be6d9e8df80dbe46c6d

 

en-GB ISO from VLSC...

 

[b]SW_DVD9_Win_Pro_Ent_Edu_N_10_1809_64-bit_English_International_MLF_X21-96503.iso[/b]

 SHA-1: ac4506a86fa8013d59d5250949a8fc10490c0db6
SHA-256: 9be96f2c87624c71f29c6660777359f3666957c82b41702afb255418b65038b9
SHA-512: ac80b28508b8a05436e9a0f5d93500155a53250f4f60e8c0ae718aea759209b7ae94849a4ffd7f28a6c14b6dac77c8618c00ed1b0180b878f16aca07beee8602

[ADMaster]

@mavhc

That doesn't look like a vlsc file name. Mine is very similar to Arthur's

SW_DVD9_Win_Pro_Ent_Edu_N_10_1809_64-bit_English_MLF_X21-96501

@ArthurWhere did you get those checksums, are they posted somewhere official or are those just your own results.

 

I should verify my 2019 iso tomorrow with the way the download was going.

 

1809 was speeding along and was almost done before home time, the sever 2019 iso was very slow and had hours left.

[mullet_man]

Another bug

 

https://support.microsoft.com/en-us/help/4471218/mapped-network-drives-don-t-work-in-windows-10-version-1809

 

Am holding off on this release for at least the next few cumulative updates.

[free780]

Or a gentle push away from mapped drives onto share point.

[mullet_man]

Possibly. That's something to look at in the future for us but we're not ready yet.

[Arthur]

Where did you get those checksums, are they posted somewhere official or are those just your own results.

They are my own, although I am confident they are correct since I used a download manager. It was too slow otherwise and I usually ended up with a corrupt ISO.

 

The checksums I have for the en-US ISO are:

 

[b]SW_DVD9_Win_Pro_Ent_Edu_N_10_1809_64-bit_English_MLF_X21-96501.iso[/b]

 SHA-1: 6208b319de3aaf0d8ec5b8d0f710e2744f89d0b4
SHA-256: 54b42dbd42c7839b8cf28e256763458aeb1c30cb858acaa2029a08f8f54e5c28
SHA-512: cc52be789e536324deaa32c5fa964333c8ebd5c9466af3019331dbbdd5e251509e967e08a111e83a08b4661ec6db58d7d06fb9488ad05ea3dc47b207055a9741

 

I should verify my 2019 iso tomorrow with the way the download was going.

I posted the checksums for the Server 2019 ISO here should you need it...

 

www.edugeek.net/forums/windows-server-2019/201261-windows-server-2019-available-again.html#post1717852

Edited November 14, 2018 by Arthur

[psydii]

Another bug

 

https://support.microsoft.com/en-us/help/4471218/mapped-network-drives-don-t-work-in-windows-10-version-1809

 

Am holding off on this release for at least the next few cumulative updates.

 

The fix/workaround includes the line “PowerShell -Command "Set-ExecutionPolicy -Scope CurrentUser Unrestricted"””

 

Umm what. You can do that as a standard user? Doesn’t that undermine the entire purpose of execution policy? If the user can do that to run an arbitrary script so can malware.

[caffrey]

ADMX Templates are out too

 

https://www.microsoft.com/en-us/download/details.aspx?id=57576&WT.mc_id=rss_alldownloads_all