Windows 10, version 1809 designated for broad deployment

[John Wilcox]

Based on the data and the feedback we’ve received from consumers, OEMs, ISVs, partners, and commercial customers, Windows 10, version 1809 has transitioned to broad deployment. With this, the Windows 10 release information page will now reflect Semi-Annual Channel (SAC) for version 1809. We will continue to communicate for future releases the transition from targeted to broad deployment status.

According to our  lifecycle policy, Windows 10 Enterprise and Windows 10 Education, version 1809 will be serviced for 30 months from its November 13th release date. End of support information for Windows 10 releases can be found in the Windows lifecycle fact sheet.

In addition to publishing monthly media refreshes for Visual Studio Subscriptions, this month’s updated media will also be available in the Volume License Servicing Center on April 2, 2019. 

[wroot]

About time :) /s

[Susan Bradley]

May I ask where the fix is for the audio issue introduced with this month's security updates?  (The C/D week update is overdue)

[Torsten Grisel]

Keep SAC-T and SAC, release one new version a year and everyone is happy. We use WUfB and don't want new versions every six months. Too much support and problems at the end users. With WUfB you have no chance to be on 1809 for 30 months, right?

[John Wilcox]

@Susan Bradley You can find all the latest published information regarding Windows updates, by each release at the Update History pages.  For 1809, look here: 

---

[Susan Bradley]

@John Wilcox  Exactly.  There is a B week release of March 12th for 1809.  Where is the C/D week?  Note that in that update history page it states that there is an expected update for 1809 in late March.  It's late March.  I know (and love and appreciate) those pages.  I'm asking where is the C/D release for 1809?  We've only had the B week one.

https://support.microsoft.com/en-us/help/4489899

fter installing this update on machines that have multiple audio devices, applications that provide advanced options for internal or external audio output devices may stop working unexpectedly. This issue occurs for users that select an audio output device different from the “Default Audio Device”. Examples of applications that may stop working include: Windows Media Player Realtek HD Audio Manager Sound Blaster Control Panel

As a temporary solution, select the “Default Audio Device” in the options provided by the application; please refer to the application’s user manual for details. For example, to set the Default Audio Device in Windows Media Player: Open Windows Media Player > Tools > Options > Devices. Select the device and choose Properties. On the next dialog, from the drop-down menu under Select the Audio Device, choose Default Audio Device from the list. You can then send audio from the application to the audio device you want in the per-application audio settings found under Settings > System > Sound > App Volume and device preferences. Microsoft is working on a resolution and estimates a solution will be available in late March 2019.

[doriel]

Thank you, Susan Bradley. You are trully the lighthouse during this storm caused by Microsoft's vague attitude. Seems like they took to much. Result is, that they use Home users as guinea pigs for their half baked.Assumption is, that the newer version of windows, the fewer bugs there should be, right? Explain this....

[Mohamed_T]

@John Wilcox Thank you for this share. According to several Microsoft communication I thought that there was no SAC TD & BD versions ! Can you confirm please ? Thank you.

[skynic]

connect is not work properly.