Resolved issues in Windows 10, version 1903 and Windows Server, version 1903

See a list of known issues that have been resolved for Windows 10, version 1903 and Windows Server, version 1903 over the last six months. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s) to search the page.


Resolved issues

SummaryOriginating updateStatusDate 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 18362.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 18362.959

July 14, 2020
KB4565483
Resolved
July 15, 2020
03:43 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 18362.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
TLS connections might fail or timeout
Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption.

See details >
OS Build 18362.418

October 08, 2019
KB4517389
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 18362.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 18362.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 18362.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 18362.693

February 27, 2020
KB4535996
Resolved
KB4554364
March 30, 2020
02:00 PM PT

Issue details

July 2020

DetailsOriginating updateStatusHistory
Outlook closes unexpectedly or you might receive an error when attempting to open
Microsoft Outlook might close unexpectedly or you might receive an error when attempting to open the app. An example of an error you might receive is, "Outlook couldn't start last time. Safe mode could help you troubleshoot the problem, but some features might not be available in this mode. Do you want to start in Safe Mode?" You might also see an event in the Event Viewer, as listed in the article linked below.

Affected platforms:
  • Client: Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise 2015 LTSB; Windows 8.1; Windows 7 SP1
Workaround: As an alternative, on your Windows 10 device you can use the Office365 on the web (OWA), also known as webmail. Outlook mobile is also unaffected. There is no workaround for this issue for the Outlook app on Windows 10 until the resolution is deployed to your device. We do not recommend using the command to revert to an earlier version.

Resolution: This Outlook issue has been resolved and will be deployed automatically to your device. This issue was not related to any update for Windows and no update for Windows is needed. We expect this issue to be completely resolved for all affected users by July 15, 2020 at 3:30 PM PST (10:30 PM UTC). You may also need to attempt to open Outlook a few times before it will be fully refreshed and open as expected. For more information, please see the support article, Active Investigation into Outlook Crashing on Launch and this twitter thread.

Back to top
OS Build 18362.959

July 14, 2020
KB4565483
Resolved
Resolved:
July 15, 2020
03:43 PM PT

Opened:
July 15, 2020
03:22 PM PT

June 2020

DetailsOriginating updateStatusHistory
Local Security Authority Subsystem Service (lsass.exe) might fail on some devices
The Local Security Authority Subsystem Service file (lsass.exe) might fail on some devices with the error message, “A critical system process, C:\WINDOWS\system32\lsass.exe, failed with status code c0000008. The machine must now be restarted."

Affected platforms:
  • Client: Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019
Resolution: This issue was resolved in KB4565483.

Back to top
OS Build 18362.836

May 12, 2020
KB4556799
Resolved
KB4565483
Resolved:
July 14, 2020
10:00 AM PT

Opened:
June 24, 2020
12:46 PM PT
Print spooler might error or close unexpectedly when attempting to print
After installing KB4560960, certain printers may be unable to print. Print spooler may error or close unexpectedly when attempting to print and no output will come from affected printer. You might also encounter issues with the apps you are attempting to print from. You might receive an error from the app or the app may close unexpectedly. Note This issue might also affect software-based printers, for example printing to PDF.

Affected platforms:
  • Client: Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
  • Server: Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue was resolved in the out-of-band update KB4567512. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4567512, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB4567512 is not available from Windows Update and will not install automatically.

Back to top
OS Build 18362.900

June 09, 2020
KB4560960
Resolved
KB4567512
Resolved:
June 16, 2020
10:00 AM PT

Opened:
June 12, 2020
04:06 PM PT
Error when attempting to open any Microsoft Office application
We have received reports that some users are unable to open apps after installing KB4560960, especially Microsoft Office apps. Affected users might also receive an error, such as, 'Windows cannot find "c:\program files\microsoft office\root\office16\winword.exe" Make sure you typed the name correctly, and then try again.'

Affected platforms:
  • Client: Windows 10, version 2004; Windows 10, version 1909; Windows 10, version 1903
  • Server: Windows Server, version 2004; Windows Server, version 1909; Windows Server, version 1903
Resolution: This issue has been resolved by Avast. This issue only affected devices with certain versions of Avast or AVG applications and was addressed with an update to their respective products. For more information on this, please see Avast's forum post here. Note No update is needed for Windows or Microsoft Office to address this issue.

Back to top
OS Build 18362.900

June 09, 2020
KB4560960
Resolved External
Last updated:
June 12, 2020
05:06 PM PT

Opened:
June 12, 2020
04:18 PM PT

May 2020

DetailsOriginating updateStatusHistory
Unable to access internet when using certain WWAN LTE modems
After installing KB4535996 on a Windows 10 device with a wireless wide area network (WWAN) LTE modems, you might be unable to reach the internet even though the Network Connectivity Status Indicator (NCSI) in the notification area shows as connected to the internet.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903
  • Server: Windows Server, version 1909; Windows Server, version 1903
Resolution: This issue was resolved in KB4559004.

Back to top
OS Build 18362.693

February 27, 2020
KB4535996
Resolved
KB4559004
Resolved:
July 21, 2020
02:00 PM PT

Opened:
May 22, 2020
12:47 PM PT

April 2020

DetailsOriginating updateStatusHistory
Social media reports related to issues with KB4549951
We have seen social media reports related to KB4549951 that mention Bluetooth, stop error with blue screen and other related issues.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903
  • Server: None
Resolution: To date, we have not seen these issues reflected in telemetry, support data or customer feedback channels. We continuously investigate all customer feedback and are closely monitoring this situation. Note If you experience any issues we'd like to know. Please provide feedback using the keyboard shortcut Windows + F or go to the Start menu and select Feedback Hub so that we can investigate.

Back to top
OS Build 18362.778

April 14, 2020
KB4549951
Resolved
Resolved:
July 14, 2020
10:19 AM PT

Opened:
April 24, 2020
12:47 PM PT

March 2020

DetailsOriginating updateStatusHistory
Devices using a proxy might show limited or no internet connection status
Devices using a manual or auto-configured proxy, especially with a virtual private network (VPN), might show limited or no internet connection status in the Network Connectivity Status Indicator (NCSI) in the notification area.  This might happen when connected or disconnected to a VPN or after changing state between the two. Devices with this issue, might also have issues reaching the internet using applications that use WinHTTP or WinInet. Examples of apps that might be affected on devices in this state are as follows but not limited to Microsoft Teams, Microsoft Office, Office365, Outlook, Internet Explorer 11, and some version of Microsoft Edge.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709
Resolution: This issue was resolved in the out-of-band update KB4554364. It is a cumulative update, so you do not need to apply any previous update before installing it. To get the standalone package for KB4554364, search for it in the Microsoft Update Catalog. You can import this update into Windows Server Update Services (WSUS) manually. See the Microsoft Update Catalog for instructions. Note KB4554364 is not available from Windows Update and will not install automatically.

Back to top
OS Build 18362.693

February 27, 2020
KB4535996
Resolved
KB4554364
Resolved:
March 30, 2020
02:00 PM PT

Opened:
March 26, 2020
10:00 AM PT

November 2019

DetailsOriginating updateStatusHistory
Issues with some older versions of Avast and AVG anti-virus products
Microsoft and Avast has identified compatibility issues with some older versions of Avast Antivirus and AVG Antivirus that might still be installed by a small number of users. Any application from Avast or AVG that contains Antivirus version 19.5.4444.567 or earlier is affected.

To safeguard your upgrade experience, we have applied a hold on devices with affected Avast and AVG Antivirus from being offered or installing Windows 10, version 1903 or Windows 10, version 1909, until the application is updated.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903
  • Server: Windows Server, version 1909; Windows Server, version 1903
Workaround: Before updating to Windows 10, version 1903 or Windows 10, version 1909, you will need to download and install an updated version of your Avast or AVG application. Guidance for Avast and AVG customers can be found in the following support articles:
Resolution: This issue has been resolved and the safeguard hold has been removed. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 10, version 2004 is offered. Note The affected incompatible versions of Avast Antivirus and AVG Antivirus might not be installed after updating to a later version of Windows 10.

Back to top
N/A

Resolved External
Last updated:
July 14, 2020
10:19 AM PT

Opened:
November 22, 2019
04:10 PM PT
TLS connections might fail or timeout
Updates for Windows released October 8, 2019 or later provide protections, tracked by CVE-2019-1318, against an attack that could allow unauthorized access to information or data within TLS connections. This type of attack is known as a man-in-the-middle exploit. Windows might fail to connect to TLS clients and servers that do not support Extended Master Secret for resumption (RFC 7627). Lack of RFC support might cause one or more of the following errors or logged events:
  • "The request was aborted: Could not create SSL/TLS secure Channel"
  • SCHANNEL event 36887 is logged in the System event log with the description, "A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 20.​"
Affected platforms:
  • Client: Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2

Resolution: Connections between two devices running any supported version of Windows should not have this issue when fully updated. There is no update for Windows needed for this issue. These changes are required to address a security issue and security compliance. For information, see KB4528489.

Back to top
OS Build 18362.418

October 08, 2019
KB4517389
Resolved External
Last updated:
July 14, 2020
10:19 AM PT

Opened:
November 05, 2019
03:36 PM PT