





Today, we have released KB4517389 which applies to both 19H1 and 19H2. For Windows Insiders in Release Preview on 19H2, this will update them to Build 18363.418.

UPDATE 10/3: Today, we have released KB4524147 which applies to both 19H1 and 19H2. For Windows Insiders in Release Preview on 19H2, this will update them to Build 18363.388.

UPDATE 9/27: Today we have enabled 19H2 Build 18363.387 for Windows Insiders in Release Preview. This is just a small refresh update from Build 18363.385 with some fixes for uninstalling 19H2 updates.

UPDATE 9/25: Today we have released 19H1 Build 18362.387 for Windows Insiders in Release Preview who are still on 19H1 only. This is just a small refresh update from Build 18362.385. We plan to enable this update for 19H2 soon.

UPDATE 9/23: We have released 19H1 Build 18362.385 / 19H2 Build 18363.385 (KB4517211) to the Release Preview ring.

Windows Insiders in the Release Preview ring who are on 19H1 Build 18362.329 will get 19H1 Build 18362.385 today.

Windows Insiders in the Release Preview ring who are on 19H2 Build 18363.329 will get 19H2 Build 18363.385 today.

As a reminder, 19H1 and 19H2 share the same servicing content. That means they share the same Cumulative Update package.

For Insiders in the Release Preview ring who are not yet on 19H2, you will continue to see a Windows 10, version 1909 update available If you go to Settings > Update & Security > Windows Update. You can choose to install this update to receive 19H2 Build 18363.385 and future 19H2 builds.

This update contains all the same 19H2 features also available to Insiders in the Slow ring:

Windows containers require matched host and container version. This restricts customers and limits Windows containers from supporting mixed-version container pod scenarios This update includes 5 fixes to address this and allow the host to run down-level containers on up-level for process (Argon) isolation.

A fix to allow OEMs to reduce the inking latency based on the hardware capabilities of their devices rather than being stuck with latency selected on typical hardware configuration by the OS.

Key-rolling or Key-rotation feature enables secure rolling of Recovery passwords on MDM managed AAD devices upon on demand request from Microsoft Intune/MDM tools or upon every time recovery password is used to unlock the BitLocker protected drive. This feature will help prevent accidental recovery password disclosure as part of manual BitLocker drive unlock by users.

A change to enable third-party digital assistants to voice activate above the Lock screen.

You can now quickly create an event straight from the Calendar flyout on the Taskbar. Just click on the date and time at the lower right corner of the Taskbar to open the Calendar flyout and pick your desired date and start typing in the text box – you’ll now see inline options to set a time and location.



The navigation pane on the Start menu now expands when you hover over it with your mouse to better inform where clicking goes.

We have added friendly images to show what is meant by “banner” and “Action Center” when adjusting the notifications on apps in order to make these settings more approachable and understandable.



Notifications settings under Settings > System > Notifications will now default to sorting notification senders by most recently shown notification, rather than sender name. This makes it easier to find and configure frequent and recent senders. We have also added a setting to turn off playing sound when notifications appear.

We now show the options to configure and turn off notifications from an app/website right on the notification, both as a banner and in Action Center.

We have added a “Manage notifications” button to the top of Action Center that launches the main “Notifications & actions” Settings page.

We have added additional debugging capabilities for newer Intel processors. This is only relevant for hardware manufacturers.

We have made general battery life and power efficiency improvements for PCs with certain processors.

A CPU may have multiple “favored” cores (logical processors of the highest available scheduling class). To provide better performance and reliability, we have implemented a rotation policy that distributes work more fairly among these favored cores.

We have enabled Windows Defender Credential Guard for ARM64 devices for additional protection against credential theft for enterprises deploying ARM64 devices in their organizations.

We have enabled the ability for enterprises to supplement the Windows 10 in S Mode policy to allow traditional Win32 (desktop) apps from Microsoft Intune.

We’re updating the search box in File Explorer to now be powered by Windows Search. This change will help integrate your OneDrive content online with the traditional indexed results. More details here.

We have added the ability for Narrator and other assistive technologies to read and learn where the FN key is located on keyboards and what state it is in (locked versus unlocked).

Additionally, this update will now be offered if you use Windows Defender Application Guard (WDAG) or containers.

NOTE: We are continuing to push 19H2 out to 10% of Windows Insiders in the Release Preview ring automatically.

UPDATE 9/5: We have increased the “seeker” experience for 19H2 in the Release Preview ring to 100%. This means that everyone in the Release Preview ring should see a Windows 10, version 1909 update available If they go to Settings > Update & Security > Windows Update. Insiders who choose to install this update will be updated to 19H2 Build 18363.329. We are also beginning to push 19H2 out to 10% of Windows Insiders in the Release Preview ring as well. This means 10% of Insiders in the Release Preview should see 19H2 Build 18363.329 offered automatically.

NOTE: IF your PC uses Windows Defender Application Guard (WDAG) or containers, you will not be offered this build of 19H2.

UPDATE 8/29: We have released 19H1 Build 18362.329 and 19H2 Build 18363.329 to Windows Insiders in the Release Preview ring with the following fixes:

We fixed an issue where on devices with LTE capability, some SIM cards from certain carriers would not work correctly.

We fixed several issues resulting in bugchecks on some devices.

To offer a clarification on these releases – 19H1 and 19H2 share the same servicing content. That means they share the same Cumulative Update package. For the small subset of Windows Insiders (the 10%) in Release Preview who were given the option to install 19H2, an enablement package is downloaded from Windows Update that turns on the 19H2 features. This *changes* the build number for the OS from 19H1 Build 18362 to 19H2 Build 18363. Because they use the same servicing content, the build revision number (the number that comes after the dot) will always match between 19H1 and 19H2. As we continue to test our servicing packages in the Release Preview ring, Insiders on 19H1 and 19H2 will get a single Cumulative Update with the same fixes.

[ORIGINAL POST FROM 8/26 BELOW]

Hello Windows Insiders,

Today, we are beginning to test the throttled approach we intend to use to rollout 19H2 to customers with Windows Insiders using the Release Preview ring. This is not the final 19H2 build that we intend to make available via the Release Preview ring once we are closer to launch.

For a small subset of Insiders (around 10%) in the Release Preview ring, we have enabled the “seeker” experience for 19H2. For these Insiders, if they go to Settings > Update & Security > Windows Update, they will see that there is a Windows 10, version 1909 update available. They will be able to choose to download and install this update on their PC. After the update finishes, they will be on 19H2 Build 18363.327.

As John Cable mentioned in July, we will be delivering 19H2 to customers using our servicing technology (just like the monthly update process) for customers running the May 2019 Update (19H1). We have been testing 19H2 with Insiders in the Slow ring using the same baseline build number as the May 2019 Update but with an increased revision number like we normally use to show a build has been serviced with a Cumulative Update. However, to designate 19H2 as a feature update, we are revising the baseline build number by one full build.

Insiders in the Release Preview ring who get 19H2 Build 18363.327 today will not see all the 19H2 features the Slow ring currently has as not all the features have been incorporated into the build yet. Because of the differences between the way the 19H2 updates are packaged between the Slow and Release Preview rings, Insiders in the Slow ring will not be able to switch to the Release Preview ring and get updates yet. Insiders who are thinking of switching rings should stay put for now. We will communicate to Insiders when it is ok to make the switch.

Thanks,

Dona and Brandon