Windows 10 [20H1] Build 19013

Discussion in 'Operating Systems' started by Extraordinary, Oct 30, 2019.

  1. Extraordinary

    Extraordinary Guest

    Messages:
    19,558
    Likes Received:
    1,636
    GPU:
    ROG Strix 1080 OC
    What’s new in Build 19013
    More kaomoji
    As some of you may know, with Windows 10 version 1903, we updated our WIN+(Period) / WIN+(Semicolon) keyboard shortcut to not only include emoji, but to also now contain kaomoji and special characters. What are kaomoji? Basically, they’re faces with expressions you can make by combining various characters–for example, you might be familiar with the shruggie:

    ¯\_(ツ)_/¯

    [​IMG]

    In any case, based on your feedback, in this build we’re updating our kaomoji list with a few more favorites, including:

    • ヾ(⌐■_■)ノ♪
    • ლ(╹◡╹ლ)
    • (⊙_◎)
    • ( ͡~ ͜ʖ ͡°)
    • ಠ_ರೃ
    • (∩^o^)⊃━☆
    • /ᐠ。ꞈ。ᐟ\
    And more! Enjoy (❁´◡`❁)

    Windows Subsystem for Linux (WSL) 2 will now release unused Linux memory back to your Windows machine
    Previously, your WSL 2 Virtual Machine’s (VM) memory would grow to meet the needs of your workflow, but would not shrink back down when the memory was no longer needed. With this change, as memory is no longer in use in the Linux VM, it will be freed back to Windows, which will shrink in memory size accordingly.

    Other updates for Insiders
    PowerToys v0.12 now available!
    We’ve just released our 0.12 release of PowerToys on GitHub. We’ve gotten tons of great feedback and suggestions from the community and want to directly say thank you to everyone.

    New features include a great new utility called PowerRename, which makes it easy to batch rename a bunch of files, improvements to FancyZones, and support for Dark Mode.

    [​IMG]

    Check out our latest article for all the details.

    Your Phone app–Elevating the Phone screen feature by removing its dependency on Bluetooth connection
    Windows Insiders, we heard your feedback about the Phone screen feature’s dependency on Bluetooth Low Energy connectivity. To address your feedback, we partnered closely with Samsung to bring you a more streamlined experience across all Windows 10 PCs by removing the peripheral role dependency for Phone screen, which will expand the overall reach of this feature.

    Samsung Galaxy Note 10 was the first device to introduce this feature in August. After a positive response, we’ve recently enabled this feature across Samsung Galaxy Fold, S10, S10+, and S10e smartphones. You’ll need to update your supported Samsung devices with the recent software update that enables the ‘Link to Windows’ feature. To continue offering this experience to other smartphones, we’re expanding this feature support to Samsung Galaxy A30s, A50s, and A90 smartphones, and we’ll continue to add additional devices in the coming months.

    With the new experience rolling out, we’ll be removing the Bluetooth connectivity option, effective immediately. If you were previously enjoying Phone screen over Bluetooth and you have a phone model that doesn’t yet support Link to Windows, the Phone screen node will disappear automatically within the Your Phone app. We recommend that you unpair your devices by going to the Bluetooth settings on both your PC and your Android phone, so that you don’t have a connection that is no longer in use.

    Thank you for helping us refine the Phone screen experience so far!

    Phone screen requirements:

    • Select Android phones running Android 9.0 or greater
    • PC running Windows 10 October 2018 Update or later
    • Android phone must be on and connected to the same network as the PC
    • You will need a supported device to use this feature:
      • Samsung Galaxy Fold
      • Samsung Galaxy Note 10/ Note 10+
      • Samsung Galaxy S10/S10+/S10e
      • Samsung Galaxy A30s/A50s/A90
    Refer to the Your Phone FAQs for additional information.

    Preview new DirectX 12 features
    In the latest 20H1 builds, you can preview new DirectX 12 features, including DirectX Raytracing tier 1.1, Mesh Shader, and Sampler Feedback. In this blog post, the DirectX Team explains what each of these features are and how they will improve the gaming experience in Windows 10!

    General changes, improvements, and fixes for PC
    • We fixed an issue resulting in frames being skipped, starting with Build 19002, when running games and videos fullscreen.
    • We fixed an issue where initiating “Reset this PC” with the cloud download option wasn’t working when started from Windows RE.
    • We fixed an issue resulting in preinstalled apps (like Calculator) and other UWP apps being missing from the Apps & Features page in Settings.
    • We appreciate your patience while we worked on our sync engine. As of this build, wallpaper and theme syncing is now up and running again.
    • We fixed an issue resulting in Wi-Fi unexpectedly resetting (turning off and back on) frequently in recent flights.
    • We fixed an issue where Wi-Fi Settings might get stuck saying Connecting, even though the network flyout (correctly) indicated that you were Connected.
    • We fixed an issue where an update being temporarily suspended would result in an 0xc19001e1 error being displayed in Windows Update history.
    • We fixed an issue resulting in the “Open location” search result option not working if the search result was a folder.
    • We fixed an issue where if you moved Cortana’s window to certain places on your screen, and then closed the window, the minimize animation wouldn’t go towards Cortana’s icon on the taskbar.
    • We fixed an issue resulting in File Explorer not rendering correctly sometimes when using multiple monitors with different DPIs on the previous flight.
    • We fixed an issue where you could get into a state where it wasn’t possible to set focus to File Explorer’s search box in order to type your query.
    • We fixed an issue that could result in the app thumbnail disappearing when you right clicked it in Task View.
    • We fixed an issue that could result in the Send Message button in certain notifications not being visible when using High Contrast White.
    • We fixed an issue where the notification following WIN+Shift+S might have a blank space for the screenshot (rather than actually displaying the screenshot).
    • We fixed an issue resulting in Resource Manager unexpectedly not showing any disk activity.
    • We fixed an issue where, if you called SUBST with a path ending with a \ it would give a Path not found error.
    • We fixed a memory leak with running apps that repeatedly sent calls to adjust gamma.
    • Some of you have reached out about when trying to shutdown, seeing a message saying that an app named “G” was preventing shutdown. We investigated and found an issue where windows related to GDI+were only referenced as “G.” We’ve fixed this, so going forward, these will now have the name “GDI+ Window (<exe name>)”, where <exe name> will show the .exe name of the app using GDI+.
    • We fixed an issue resulting in speechruntime.exe using an unexpectedly high amount of CPU on the previous flight.
    • We fixed an issue resulting in Bluetooth devices potentially not reconnecting as expected after closing then reopening the device lid for certain devices.
    • We fixed an issue resulting in the Surface Dial not scrolling in recent builds if you switched to something like zoom and then back to scrolling.
    • Thank you Insiders who shared feedback about the 2-in-1 convertible tablet experience improvements we discussed here. For the time being, we’re returning to the current experience in retail.
    • We fixed an issue where Narrator would sometime report focus as the page instead of reporting the actual focused control within Chrome.
    • We fixed an issue where Narrator would not automatically start reading the Narrator user guide webpage and the YouTube webpage.
    • We corrected Narrator’s “Next Table” command so that it would work in Excel.
    • We fixed an issue where the text cursor indicator was visible on top of the lock screen background picture.
    • We fixed an issue where the text cursor indicator preview wasn’t displaying correctly in Settings when using dark theme.
    • We fixed an issue where when using dark theme, the hardware keyboard text prediction candidate window was unreadable due to black text on a dark grey background.
    • We fixed an issue that could result in the touch keyboard flickering when inputting emoji.
    • We fixed an issue where English punctuations were outputted when using the Chinese Pinyin and Wubi IMEs, even if input mode was set to Chinese under the default IME settings. Thanks for your feedback.
    • We’ve fixed an issue where the character width of alphanumeric characters when using the Traditional Chinese Bopomofo IME would change from half width to full width unexpectedly in some input fields. Thanks for reporting it! If you feel this issue hasn’t been fully addressed in the new version of Bopomofo IME, please let us know your feedback.
    • We’ve fixed an issue where after successfully updating to a new build, the Windows Update Settings page may have shown the same build needed to be installed.
    • We’ve fixed an issue where Optional drivers were failing to install.
    Known issues
    • BattlEye and Microsoft have found incompatibility issues due to changes in the operating system between some Insider Preview builds and certain versions of BattlEye anti-cheat software. To safeguard Insiders who might have these versions installed on their PC, we have applied a compatibility hold on these devices from being offered affected builds of Windows Insider Preview. See this article for details.
    • We’ve heard that Settings still isn’t available outside of launching via the URI (ms-settings:) for some Insiders and are investigating.
    • If you use remote desktop connection and the target PC is on this build, within about an hour (if not sooner), DWM may start crashing, and the session window will either go totally black, experience black flashes, or you may get signed out of the remote desktop session altogether. We appreciate your patience.
    https://blogs.windows.com/windowsex...ncing-windows-10-insider-preview-build-19013/
     
    Jackalito and JonasBeckman like this.
  2. LocoDiceGR

    LocoDiceGR Ancient Guru

    Messages:
    2,858
    Likes Received:
    1,071
    GPU:
    Gigabyte 3060 Ti
    Yes Microsoft, all we wanted was kaomoji . /facepalm
     
    Jackalito likes this.
  3. Extraordinary

    Extraordinary Guest

    Messages:
    19,558
    Likes Received:
    1,636
    GPU:
    ROG Strix 1080 OC
    That Smart Rename Power Toy is the first update to 10 I consider even slightly useful
     
    Jackalito likes this.
  4. alexander1986

    alexander1986 Master Guru

    Messages:
    201
    Likes Received:
    21
    GPU:
    RTX 2060
    if I would like to test this build, what is an easy way to do so ?
     

  5. Extraordinary

    Extraordinary Guest

    Messages:
    19,558
    Likes Received:
    1,636
    GPU:
    ROG Strix 1080 OC
    alexander1986 likes this.
  6. Dan

    Dan Active Member

    Messages:
    75
    Likes Received:
    38
    GPU:
    6700 RX
    "We fixed an issue resulting in frames being skipped, starting with Build 19002, when running games and videos fullscreen."

    Is this implying that this particular issue began with build 19002 or that it was being fixed starting from build 19002? The reason for asking is that I've been seeing this or a simular issue since the retail 1809 build.
     
    Last edited: Oct 31, 2019
  7. Astyanax

    Astyanax Ancient Guru

    Messages:
    17,011
    Likes Received:
    7,352
    GPU:
    GTX 1080ti
    there has never been a 1901 build.
     
  8. Dan

    Dan Active Member

    Messages:
    75
    Likes Received:
    38
    GPU:
    6700 RX
    I meant 1809.
     
  9. alexander1986

    alexander1986 Master Guru

    Messages:
    201
    Likes Received:
    21
    GPU:
    RTX 2060

    hm, sorry but I tried doing that and not any of the 4 methods for a x64 version gave me a link to a ISO for example like expected, only some .CMD files I couldn't get to work and so on, can you perhaps say exactly how to get an ISO from there? would be very appreciated!
     
  10. Extraordinary

    Extraordinary Guest

    Messages:
    19,558
    Likes Received:
    1,636
    GPU:
    ROG Strix 1080 OC
    Run the CMD file and it will create an ISO for you, it might take some time as it has to download UUP files and then decrypt them and then create the ISO
     

  11. alexander1986

    alexander1986 Master Guru

    Messages:
    201
    Likes Received:
    21
    GPU:
    RTX 2060
    ah, anyway I searched some on my own and found an iso here a bit further down on this page


    https://thewincentral.com/windows-10-build-19013-iso-images-3rd-party-now-available/


    downloading it now with no speed limit, direct link to 3.5 gb iso file, 19013.1.vb_release.191025-1609 20H1 , seems good anyway cheers
     
  12. Extraordinary

    Extraordinary Guest

    Messages:
    19,558
    Likes Received:
    1,636
    GPU:
    ROG Strix 1080 OC
    Those ISOs are from WZor and are fine, but just be aware that there are no official Microsoft ISOs for most insider builds, so any you find have been made by someone else and could contain malware
     
    alexander1986 likes this.
  13. alexander1986

    alexander1986 Master Guru

    Messages:
    201
    Likes Received:
    21
    GPU:
    RTX 2060
    cool, and yes agreed on the malware part! do you perhaps have any clue about when this 20H1 version or a finalized build could be available from MS/windows update? in general terms of course as nobody knows exactly when :p

    does 20H1 stand for like, first half of 2020 ?


    because 1909 still not available from win update or from MS for regular users, if im not mistaken :S
     
  14. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    17,564
    Likes Received:
    2,961
    GPU:
    XFX 7900XTX M'310
    Build 18362 or 18363 .418 should have official install media at least in the way of a ESD though ISO might be available too, 19H1 and 19H2 are identical now with a cumulative update for version .459 or something like that and then the only difference is that 19H2 and the change from 18362 to 18363 is that features are disabled until a small enablement package gets downloaded and installed which prompts for a reboot and then it's all set.

    If there's no other pending updates like the usual for .NET or a November cumulative for the second Tuesday of the month then the release of 1909 as the "build" for 19H2 of Windows 10 should just be that small package. :)
    It's a bit weird due to Microsoft slowly transitioning away from the current twice a year build releases of Windows 10 into a once a year build cycle as earlier but still needing a update for 19H2 when it could just have been a cumulative with some additional features added or backported from 20H1 but it is what it is though due to the shared code most up to date 1903 users are already on the latest build and update just with the new features in a disabled state for now until the enablement package is installed either via Microsoft Update once this build gets released in full or manually and integrated via for example DISM.


    EDIT: ESD's for 19000 and 20H1 are also usually available but these are from the update servers and require some work and integration for turning them into full install media. UUPDump for example and various scripts joining the various components into a full ISO or ESD that can then be added to a disc or the newer method of a USB stick. :)

    Though with new builds almost weekly for the fast ring and several changes, additions and fixes per build it's probably not going to slow down until the bug hunt event starts and then pick up once that's over with and go until whatever final "RTM" (Sorta, not entirely used anymore.) version this ends up with for April or May of 2020 or when it was planned for release at least unless there's going to be any more delays or changes.
    (It can vary, sometimes it's just one or two additional cumulative updates, sometimes it's a cumulative but then a new build comes out anyway and that might be the new candidate for the final version.)
     
    alexander1986 likes this.
  15. Extraordinary

    Extraordinary Guest

    Messages:
    19,558
    Likes Received:
    1,636
    GPU:
    ROG Strix 1080 OC
    Yea first half of 2020, 1903 and 1909 and essentially the exact same OS, no difference other than an enablement package
    https://forums.mydigitallife.net/th...pc-19h1-2-release.79259/page-282#post-1551877
     
    Last edited: Nov 1, 2019
    alexander1986 likes this.

  16. alexander1986

    alexander1986 Master Guru

    Messages:
    201
    Likes Received:
    21
    GPU:
    RTX 2060

    cool, ty for the detailed info !

    what was interesting to me with the upcoming builds of win10 was those performance improvements I heard about, something about the OS automatically recognizing what core/cores of a multicore processor is the most efficient in an individual case (it was supposed to vary from cpu to cpu of the same model) and like leveraging workloads somehow dynamically to make better use of that/those core(s), something like this at least? :D


    always interested in higher performance/lower input lag wherever its possible for my gaming, IDK if there will be a noticeable difference but still interesting imo !


    also btw , this line in the first post in this thread about changes/improvements in this 19013 / 20H1 build: "We fixed an issue resulting in frames being skipped, starting with Build 19002, when running games and videos fullscreen."

    do you know if this means that the bug/issue was introduced in build 19002, and so me for example who is now running 18362.449 should not be affected by it? or that it was fixed and resolved from build 19002 and onwards? if that makes any sense?

    cheers!
     
  17. JonasBeckman

    JonasBeckman Ancient Guru

    Messages:
    17,564
    Likes Received:
    2,961
    GPU:
    XFX 7900XTX M'310
    Pretty sure the fix is only from 19002 since the code base is separate from the older builds even though a few features from 20H1 landed in 19H2 but they've been implemented for many months now across a separate slow ring (18362.1000 and on.) and thoroughly tested by this point.

    Core improvements and scheduling should affect Ryzen CPU's in particular though bios and chipset drivers help but many games still put weird priorities or load on the CPU cores although the overall performance increase might not change too much but it might improve CPU utilization or allow for better efficiency instead of using a few cores from each cluster or over-relying on CPU0 though the software meaning application or game also could do with some improving so I don't expect the OS changes to make a significant difference on it's own, general improvements overall are required.

    That and the chipset drivers at least on Ryzen 3000 CPU's already lower the value it checks and refreshes at to a much lower one (Forgot the exact figures however.) though this also introduced a few side effects like it boosting to higher clock states when measuring software like CPU-Z queried sensors and such for reporting data for monitoring.
    (New chipset software and the currently gradually rolling out 1004 AGESA and 1004b in motherboard bioses should have improved on this too.)


    I'm going to wait with jumping onto 19000 or 20H1 and whatever the build will end up at when it hits general release at least until the feature implementation is done and Microsoft moves into bug fixing and readying for a release candidate so maybe January or February next year although the fixes in 19013 here already look really promising with only a few current listed issues but there's still almost half a year at least so with almost two new builds weekly there's still plenty to come until 20H1 is released and final or as final as this service model of Windows 10 can be until the next build is ready. (20H2 as it's called is already getting ready for skip-ahead deployment and insider ring release.)

    Although I am following the blog posts and discussions for these builds, looking good so far and the longer period of testing before launch should also reduce launch issues or so I hope although a cumulative update will probably happen between the final build being deployed and said build hitting public channels and general release readiness.
     
    alexander1986 likes this.
  18. Passus

    Passus Ancient Guru

    Messages:
    2,553
    Likes Received:
    1,028
    GPU:
    MSI 4070 Gaming X
    Anyone know how to enable passwordless startup cause its gone from netplwiz :(

    I dont need a password as its a family computer
     
  19. Extraordinary

    Extraordinary Guest

    Messages:
    19,558
    Likes Received:
    1,636
    GPU:
    ROG Strix 1080 OC
    Did you log in with a MS account? Needs to be local to disable password afaik
     
  20. Passus

    Passus Ancient Guru

    Messages:
    2,553
    Likes Received:
    1,028
    GPU:
    MSI 4070 Gaming X
    no always local never use microsoft account
     

Share This Page