Known and Resolved issues for Windows 10 Nov. 2019 Update version 1909

Page 1 of 6 123 ... LastLast
    Known and Resolved issues for Windows 10 Nov. 2019 Update version 1909

    Known and Resolved issues for Windows 10 Nov. 2019 Update version 1909

    Windows release health dashboard

    Last Updated: 1 Week Ago at 14:08

    Current status as of May 27, 2020:

    Windows 10, version 1909 is designated ready for broad deployment for all users via Windows Update.

    We recommend commercial customers running earlier versions of Windows 10 nearing end of support begin broad deployments of Windows 10, version 1909 in their organizations.

    For information on how users running Windows 10, version 1903 can update to Windows 10, version 1909 in a new, streamlined way, see this post.

    Note follow @windowsupdate on Twitter to find out when new content is published to the release information dashboard.



    Known issues

    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    Summary Originating update Status Last updated
    Unable to access internet when using certain WWAN LTE modems
    Internet might show as connected but be unreachable when using certain WWAN LTE modems.

    See details >
    OS Build 18363.693

    February 27, 2020
    KB4535996
    Investigating May 27, 2020
    09:28 AM PT
    Social media reports related to issues with KB4549951
    Reported issues include Bluetooth, stop error with blue screen and other related issues.

    See details >
    OS Build 18363.778

    April 14, 2020
    KB4549951
    Investigating April 24, 2020
    12:47 PM PT
    “Reset this PC” feature might fail
    “Reset this PC” feature is also called “Push Button Reset” or PBR.

    See details >
    N/A
    February 11, 2019
    KB4524244
    Mitigated February 15, 2020
    12:02 AM PT
    You might encounter issues with KB4524244
    You might encounter issues trying to install or after installing KB4524244

    See details >
    N/A
    February 11, 2019
    KB4524244
    Mitigated February 15, 2020
    12:02 AM PT
    Issues with some older versions of Avast and AVG anti-virus products
    Microsoft and Avast has identified compatibility issues with some versions of Avast and AVG Antivirus.

    See details >
    N/A Mitigated External November 25, 2019
    05:25 PM PT

    Resolved issues

    Summary Originating update Status Date resolved
    Devices using a proxy might show limited or no internet connection status
    Network Connectivity Status Indicator might show limited or no internet connection and apps may have issues connecting.

    See details >
    OS Build 18363.693

    February 27, 2020
    KB4535996
    Resolved
    KB4554364
    March 30, 2020
    02:00 PM PT
    Unable to create local users in Chinese, Japanese and Korean during device setup
    You might be unable to create users in Chinese, Japanese and Korean using Input Method Editor (IME) during OOBE.

    See details >
    OS Build 18363.476

    November 12, 2019
    KB4524570
    Resolved
    KB4530684
    December 10, 2019
    10:00 AM PT

    Source:


    See also:

    Brink's Avatar Posted By: Brink
    12 Nov 2019

  1. Steve C's Avatar
    Posts : 5,283
    Windows 10 Pro 64 bit
       #1

    Any issues with cldflt.sys I wonder which have been a recent problem with v1903?
      My Computers

  2. EdTittel's Avatar
    Posts : 3,761
    Windows 10
       #2

    I've got an issue with my production desktop where as soon as I plug my iPhone in via USB 3.0 on the front panel, the PC bluescreens. See this Windows Enterprise Desktop blog post for more details: USB iPhone Link-Up Causes BSOD. @Kari suggests I delete the current drivers in Safe Mode, then attempt another plug-in at the next normal reboot. I'm going to give it a try and see what happens. Owing to another bug in HD Tune (I provoked 9 APPCRASH events yesterday) my Reliability Monitor index is currently at rock bottom anyway. Sigh.
    --Ed--
      My Computers

  3. Brink's Avatar
    Posts : 48,917
    64-bit Windows 10 Pro for Workstations build 19640
    Thread Starter
       #3

    UPDATE 11/15:

    Known and Resolved issues updated in first post.
      My Computers

  4. Crizal's Avatar
    Posts : 270
    Windows 10 Home 64bit
       #4

    Updated 1903 to 1909 without incident via Windows Update four days ago. No problem until today. Discovered that as of this morning, every time I turn on my computer, restart it or run any browser, app or program, Reliability History is showing an error "Runtime Broker has stopped working". Fault module is "settingsenvironment.desktop.dll".

    Runtime Broker deals with apps, so I ran the app troubleshooter. No problem found but it suggested running Windows Update troubleshooter. All that did was change the services startup from manual to automatic trigger. It then suggested running BITS troubleshooter. No problem found there.

    I also followed Brink's tutorial to reinstall and re-register all apps. Didn't fix. And I ran sfc /scannow and every DISM command I could find. No issues found.

    I then uninstalled the Enablement Package KB4517245 and reverted back to 1903. All errors disappeared from Reliability History and computer is working just fine. Tried a second install of 1909 and the error problem immediately came back. Reverted back to 1903, problem gone. I suppose there's something in 1909 that doesn't like my machine, or vice versa.

    Guess I'm going to stay on 1903 for now. May try a clean install when I have time in a few days or perhaps bypass 1909 and go to 2003 when it comes out and see if that works. To be continued.....eventually.



    EDIT: I think I may have put this in the wrong thread. Mods please move if need be.
      My Computer

  5. krzemien's Avatar
    Posts : 575
    Windows 10 Home x64
       #5

    EdTittel said:
    Owing to another bug in HD Tune (I provoked 9 APPCRASH events yesterday)(...)
    Apologies for OT, but are you able to shed more light here - I'm the user? Is this bug present in the Pro version? And in the latest one (v5.75)?
      My Computers

  6. EdTittel's Avatar
    Posts : 3,761
    Windows 10
       #6

    @krzemien: AFAIK, it's only affecting one of my PCs. That PC is also subject to some other weirdnesses, including an instant bluescreen whenever I plug in an iPhone via USB/Lightning cable. In this case, I'm inclined to blame the PC itself, rather than HD Tune or Windows 10. HTH,
    --Ed--
      My Computers


  7. Ztruker's Avatar
    Posts : 10,256
    Windows 10 Pro X64 1909 18363.815
       #7

    Crizal said:
    Updated 1903 to 1909 without incident via Windows Update four days ago. No problem until today. Discovered that as of this morning, every time I turn on my computer, restart it or run any browser, app or program, Reliability History is showing an error "Runtime Broker has stopped working". Fault module is "settingsenvironment.desktop.dll".

    Runtime Broker deals with apps, so I ran the app troubleshooter. No problem found but it suggested running Windows Update troubleshooter. All that did was change the services startup from manual to automatic trigger. It then suggested running BITS troubleshooter. No problem found there.

    I also followed Brink's tutorial to reinstall and re-register all apps. Didn't fix. And I ran sfc /scannow and every DISM command I could find. No issues found.

    I then uninstalled the Enablement Package KB4517245 and reverted back to 1903. All errors disappeared from Reliability History and computer is working just fine. Tried a second install of 1909 and the error problem immediately came back. Reverted back to 1903, problem gone. I suppose there's something in 1909 that doesn't like my machine, or vice versa.

    Guess I'm going to stay on 1903 for now. May try a clean install when I have time in a few days or perhaps bypass 1909 and go to 2003 when it comes out and see if that works. To be continued.....eventually.



    EDIT: I think I may have put this in the wrong thread. Mods please move if need be.
    Did you report it via Feedback?
      My Computers

  8. Crizal's Avatar
    Posts : 270
    Windows 10 Home 64bit
       #8

    Ztruker said:
    Did you report it via Feedback?
    Sure did. Will try the clean install in a few days. Have a lot on the plate right now.

    - - - Updated - - -

    Here's the latest on my 1909 woes described in post #4 …..

    1. Tried one last time to update 1903 to 1909 via Enablement Package in Windows Update. Installation successful, computer works fine BUT "Runtime Broker has stopped working" error is generated in Reliability History with any and every thing I do. Reverted back to 1903 -- errors gone.

    2. Tried a clean install. Same problem. Used Macrium to get back to 1903.

    3. No response yet to my post in Feedback. Spoke to MS and was essentially advised to stay on 1903 and see what happens when 2003 is released. And, if that doesn't work, revert back to 1903 until it's no longer supported and then consider buying a new computer.

    This last tidbit is not something I wanted to hear. My rig is not even four years old and has been virtually flawless since the day I got it. I will continue to research and explore the issue as I have the time. Obviously staying put on 1903.
      My Computer

  9. krzemien's Avatar
    Posts : 575
    Windows 10 Home x64
       #9

    I'm pretty much sure I've seen this issue mentioned before on the occasion of earlier upgrades. Worth checking what Uncle Google says about this, methinks...
      My Computers


 

Related Threads
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:01.
Find Us




Windows 10 Forums