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

Steve C · 13 Nov 2019

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

EdTittel · 16 Nov 2019

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--

Brink · 16 Nov 2019

UPDATE 11/15:

Known and Resolved issues updated in first post.

Crizal · 16 Nov 2019

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.

krzemien · 17 Nov 2019

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)?

EdTittel · 17 Nov 2019

@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--

Ztruker · 17 Nov 2019

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?

Crizal · 19 Nov 2019

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.

krzemien · 19 Nov 2019

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...

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	Resolved KB4559004	July 21, 2020 02:00 PM PT
Outlook closes unexpectedly or you might receive an error when attempting to open An example of an error you might receive is, "Outlook couldn't start last time." See details >	OS Build 18363.959 July 14, 2020 KB4565483	Resolved	July 15, 2020 03:38 PM PT
Local Security Authority Subsystem Service (lsass.exe) might fail on some devices Affected devices might receive a critical system process error and the device might restart. See details >	OS Build 18363.836 May 12, 2020 KB4556799	Resolved KB4565483	July 14, 2020 10:00 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	Resolved External	July 14, 2020 10:19 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	Resolved	July 14, 2020 10:19 AM PT
Print spooler might error or close unexpectedly when attempting to print Certain printers might be unable to print after taking updates released June 9, 2020. See details >	OS Build 18363.900 June 09, 2020 KB4560960	Resolved KB4567512	June 16, 2020 10:00 AM 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, 2020 KB4524244	Mitigated	February 15, 2020 01:22 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, 2020 KB4524244	Mitigated	February 15, 2020 01:22 AM PT

Summary	Originating update	Status	Date resolved
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	Resolved KB4559004	July 21, 2020 02:00 PM PT
Outlook closes unexpectedly or you might receive an error when attempting to open An example of an error you might receive is, "Outlook couldn't start last time." See details >	OS Build 18363.959 July 14, 2020 KB4565483	Resolved	July 15, 2020 03:38 PM PT
Local Security Authority Subsystem Service (lsass.exe) might fail on some devices Affected devices might receive a critical system process error and the device might restart. See details >	OS Build 18363.836 May 12, 2020 KB4556799	Resolved KB4565483	July 14, 2020 10:00 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	Resolved External	July 14, 2020 10:19 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	Resolved	July 14, 2020 10:19 AM PT
Print spooler might error or close unexpectedly when attempting to print Certain printers might be unable to print after taking updates released June 9, 2020. See details >	OS Build 18363.900 June 09, 2020 KB4560960	Resolved KB4567512	June 16, 2020 10:00 AM PT
Error when attempting to open any Microsoft Office application You might receive the error: Windows cannot find "c:\program files\microsoft office\root\office16\winword.exe" See details >	OS Build 18363.900 June 09, 2020 KB4560960	Resolved External	June 12, 2020 05:06 PM PT
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