1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Windows 10 [19H2] Build 18362.10005

Discussion in 'Operating Systems' started by Extraordinary, Jul 16, 2019.

  1. Extraordinary

    Extraordinary Ancient Guru

    Messages:
    19,327
    Likes Received:
    1,383
    GPU:
    GTX980 SLI
    Today we are releasing 19H2 Build 18362.10005 to Windows Insiders in the Slow ring. As a reminder, Windows Insiders in the Slow ring who are on the Windows 10 May 2019 Update will be receiving 19H2 via servicing as a Cumulative Update and not a full build update.

    In addition to the fixes included in KB4507453 for the May 2019 Update, 19H2 Build 18362.10005 includes the following changes and improvements:

    • 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 in-tune/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.
    Please note that these changes and improvements are currently OFF by default in this build. As mentioned previously, we may ship features in these updates turned off by default and turn them on via controlled feature rollouts. Doing this helps us gain better feedback on overall build quality. With today’s 19H2 build, we are testing this experience. Our plan is to quickly follow-up with another 19H2 build that turns these features on for a subset of Insiders and proceed from there based on feedback and quality.

    https://blogs.windows.com/windowsex...ws-10-insider-preview-build-18362-10005-19h2/


    UPDATE 7/17: Today we have released 19H2 Build 18362.10006 for a subset of Windows Insiders that turns on the features delivered as part of Build 18362.10005 (noted in the below blog post) earlier this week. Please note that Build 18362.10006 is only going out to a subset of Insiders in the Slow ring. That means not everyone in the Slow ring will get this update.
     
    Last edited: Jul 18, 2019
    Jackalito likes this.
  2. Chastity

    Chastity Ancient Guru

    Messages:
    1,818
    Likes Received:
    433
    GPU:
    Nitro 390/GTX1070M
  3. Extraordinary

    Extraordinary Ancient Guru

    Messages:
    19,327
    Likes Received:
    1,383
    GPU:
    GTX980 SLI
    UPDATE 7/17: Today we have released 19H2 Build 18362.10006 for a subset of Windows Insiders that turns on the features delivered as part of Build 18362.10005 (noted in the below blog post) earlier this week. Please note that Build 18362.10006 is only going out to a subset of Insiders in the Slow ring. That means not everyone in the Slow ring will get this update.
     
    Jackalito and JonasBeckman like this.
  4. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    15,402
    Likes Received:
    1,433
    GPU:
    Sapphire Vega Pulse
    Hmm wonder if that's the changes from yesterdays cumulative update (Insider only as it seems for the release preview channel.) and now it's being (Fairly quickly.) moved into 19H2 here, wonder what changed though it's a gradual migration here to this build so if it was something incredibly critical or security related I would expect a full release but we'll see. :)

    Nice info though, will be curious to see what 19H2 actually is beyond these OEM focused updates unless that's literally it as a stepping stone for 20H1 at which point a yearly larger, focused and tested build instead sounds like it really is a better idea but eh I suppose they have some logic and reasoning behind the rapid release cycle much as I find it to have a few too many drawbacks and launch issues to be entirely functional. (At least it's not a mandatory or forced update.)
     

Share This Page