diff --git a/browsers/internet-explorer/TOC.md b/browsers/internet-explorer/TOC.md index 6bd312c3b2..28a0957588 100644 --- a/browsers/internet-explorer/TOC.md +++ b/browsers/internet-explorer/TOC.md @@ -186,6 +186,6 @@ ### [IExpress Wizard command-line options](ie11-ieak/iexpress-command-line-options.md) ### [Internet Explorer Setup command-line options and return codes](ie11-ieak/ie-setup-command-line-options-and-return-codes.md) -## Troubleshooting -### [Clear the Internet Explorer cache from a command line](/../troubleshooting/clear-ie-cache-from-command-line.md) -### [IE and Microsoft Edge FAQ for IT Pros](/../troubleshooting/ie-edge-faqs.md) +## KB Troubleshoot +### [Clear the Internet Explorer cache from a command line](kb-support/clear-ie-cache-from-command-line.md) +### [Internet Explorer and Microsoft Edge FAQ for IT Pros](kb-support/ie-edge-faqs.md) diff --git a/browsers/troubleshooting/clear-ie-cache-from-command-line.md b/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md similarity index 74% rename from browsers/troubleshooting/clear-ie-cache-from-command-line.md rename to browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md index 74054a95b3..27232c758a 100644 --- a/browsers/troubleshooting/clear-ie-cache-from-command-line.md +++ b/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md @@ -1,16 +1,19 @@ --- title: Clear the Internet Explorer cache from a command line description: Introduces command-line commands and a sample batch file for clearing the IE cache. -author: ramakoni -manager: dcscontentpm -ms.prod: internet-explorer -ms.topic: troubleshooting -ms.author: ramakoni -ms.custom: CI=111020 -ms.reviewer: ramakoni, DEV_Triage audience: ITPro +manager: msmets +author: ramakoni1 +ms.author: ramakoni +ms.reviewer: ramakoni, DEV_Triage +ms.prod: internet-explorer +ms.technology: +ms.topic: troubleshooting +ms.custom: CI=111020 ms.localizationpriority: Normal -ms.date: 01/20/2020 +# localization_priority: medium +# ms.translationtype: MT +ms.date: 01/22/2020 --- # How to clear Internet Explorer cache by using the command line @@ -21,46 +24,46 @@ This article outlines the procedure to clear the Internet Explorer cache by usin 1. Delete history from the Low folder `del /s /q C:\Users\\%username%\AppData\Local\Microsoft\Windows\History\low\* /ah` -2. Delete history +2. Delete history `RunDll32.exe InetCpl.cpl, ClearMyTracksByProcess 1` -3. Delete cookies +3. Delete cookies `RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 2` -4. Delete temporary internet files +4. Delete temporary internet files `RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8` -5. Delete form data +5. Delete form data `RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 16` -6. Delete stored passwords +6. Delete stored passwords `RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 32` 7. Delete all `RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 255` -8. Delete files and settings stored by add-ons +8. Delete files and settings stored by add-ons `InetCpl.cpl,ClearMyTracksByProcess 4351` If you upgraded from a previous version of Internet Explorer, you have to use the following commands to delete the files from older versions: -`RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 9` +`RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 9` Command to reset Internet Explorer settings: `Rundll32.exe inetcpl.cpl ResetIEtoDefaults` ## Sample batch file to clear Internet Explorer cache files -A sample batch file is available that you can use to clear Internet Explorer cache files and other items. You can download the file from https://msdnshared.blob.core.windows.net/media/2017/09/ClearIE_Cache.zip. +A sample batch file is available that you can use to clear Internet Explorer cache files and other items. You can download the file from [https://msdnshared.blob.core.windows.net/media/2017/09/ClearIE_Cache.zip](https://msdnshared.blob.core.windows.net/media/2017/09/ClearIE_Cache.zip). The batch file offers the following options: -- Delete Non-trusted web History (low-level hidden cleanup) -- Delete History -- Delete Cookies -- Delete Temporary Internet Files -- Delete Form Data -- Delete Stored Passwords -- Delete All +- Delete Non-trusted web History (low-level hidden cleanup) +- Delete History +- Delete Cookies +- Delete Temporary Internet Files +- Delete Form Data +- Delete Stored Passwords +- Delete All - Delete All "Also delete files and settings stored by add-ons" - Delete IE10 and IE9 Temporary Internet Files - Resets IE Settings @@ -78,32 +81,32 @@ cls COLOR 00 echo Delete IE History echo Please select the task you wish to run. -echo Pick one: +echo Pick one: echo. -echo 1. Delete Non-trusted web History(low level hidden clean up) -echo 2. Delete History -echo 3. Delete Cookies -echo 4. Delete Temporary Internet Files -echo 5. Delete Form Data -echo 6. Delete Stored Passwords -echo 7. Delete All +echo 1. Delete Non-trusted web History(low level hidden clean up) +echo 2. Delete History +echo 3. Delete Cookies +echo 4. Delete Temporary Internet Files +echo 5. Delete Form Data +echo 6. Delete Stored Passwords +echo 7. Delete All echo 8. Delete All "Also delete files and settings stored by add-ons" echo 9. Delete IE10 and 9 Temporary Internet Files echo 10. Reset IE Settings echo 77. EXIT :choice -Echo Hit a number [1-10] and press enter. +Echo Hit a number [1-10] and press enter. set /P CH=[1-10] -if "%CH%"=="1" set x=del /s /q C:\Users\%username%\AppData\Local\Microsoft\Windows\History\low\* /ah -if "%CH%"=="2" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 1 -if "%CH%"=="3" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 2 -if "%CH%"=="4" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8 -if "%CH%"=="5" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 16 -if "%CH%"=="6" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 32 -if "%CH%"=="7" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 255 -if "%CH%"=="8" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 4351 -if "%CH%"=="9" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 9 +if "%CH%"=="1" set x=del /s /q C:\Users\%username%\AppData\Local\Microsoft\Windows\History\low\* /ah +if "%CH%"=="2" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 1 +if "%CH%"=="3" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 2 +if "%CH%"=="4" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8 +if "%CH%"=="5" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 16 +if "%CH%"=="6" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 32 +if "%CH%"=="7" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 255 +if "%CH%"=="8" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 4351 +if "%CH%"=="9" set x=RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 9 if "%CH%"=="10" set x=rundll32.exe inetcpl.cpl ResetIEtoDefaults if "%CH%"=="77" goto quit @@ -111,23 +114,24 @@ if "%CH%"=="77" goto quit goto Home -::Temporary Internet Files > Delete files - To delete copies of web pages, images, and media +::Temporary Internet Files > Delete files - To delete copies of web pages, images, and media ::that are saved for faster viewing. -::Cookies > Delete cookies - To delete cookies, which are files that are stored on your computer by +::Cookies > Delete cookies - To delete cookies, which are files that are stored on your computer by ::websites to save preferences such as login information. ::History > Delete history - To delete the history of the websites you have visited. -::Form data > Delete forms - To delete all the saved information that you have typed into +::Form data > Delete forms - To delete all the saved information that you have typed into ::forms. -::Passwords > Delete passwords - To delete all the passwords that are automatically filled in +::Passwords > Delete passwords - To delete all the passwords that are automatically filled in ::when you log on to a website that you've previously visited. ::Delete all - To delete all of these listed items in one operation. ::enter below in search/run to see Low history dir if exists ::C:\Users\%username%\AppData\Local\Microsoft\Windows\History\low -::Delete all low(untrusted history) very hidden -::this will clean any unlocked files under the dir and not delete the dir structure +::Delete all low (untrusted history) very hidden +::this will clean any unlocked files under the dir and not delete the dir structure ::del /s /q low\* /ah ::del /s /q C:\Users\%username%\AppData\Local\Microsoft\Windows\History\low\* /ah goto Home +:quit ``` diff --git a/browsers/troubleshooting/ie-edge-faqs.md b/browsers/internet-explorer/kb-support/ie-edge-faqs.md similarity index 92% rename from browsers/troubleshooting/ie-edge-faqs.md rename to browsers/internet-explorer/kb-support/ie-edge-faqs.md index 578f76499f..18643175f9 100644 --- a/browsers/troubleshooting/ie-edge-faqs.md +++ b/browsers/internet-explorer/kb-support/ie-edge-faqs.md @@ -1,16 +1,19 @@ --- title: IE and Microsoft Edge FAQ for IT Pros description: Describes frequently asked questions about Internet Explorer and Microsoft Edge for IT professionals. -author: ramakoni -manager: dcscontentpm -ms.prod: internet-explorer -ms.topic: troubleshooting -ms.author: ramakoni -ms.custom: CI=111020 -ms.reviewer: ramakoni audience: ITPro +manager: msmets +author: ramakoni1 +ms.author: ramakoni +ms.reviewer: ramakoni, DEV_Triage +ms.prod: internet-explorer +ms.technology: +ms.topic: troubleshooting +ms.custom: CI=111020 ms.localizationpriority: Normal -ms.date: 01/20/2020 +# localization_priority: medium +# ms.translationtype: MT +ms.date: 01/22/2020 --- # Internet Explorer and Microsoft Edge frequently asked questions (FAQ) for IT Pros @@ -35,7 +38,7 @@ For more information about how Internet Explorer handles cookies, see the follow To see where Internet Explorer stores its cookies, follow these steps: 1. Start File Explorer. -2. Select **Views** > **Change folder and search options**. +2. Select **Views** \> **Change folder and search options**. 3. In the **Folder Options** dialog box, select **View**. 4. In **Advanced settings**, select **Do not show hidden files, folders, or drivers**. 5. Clear **Hide protected operation system files (Recommended)**. @@ -66,12 +69,10 @@ For more information, see [Internet Explorer Cookie Internals (FAQ)](https://blo #### Additional information about cookie limits -**What does the Cookie RFC allow?** - +**What does the Cookie RFC allow?** RFC 2109 defines how cookies should be implemented, and it defines minimum values that browsers support. According to the RFC, browsers would ideally have no limits on the size and number of cookies that a browser can handle. To meet the specifications, the user agent should support the following: - At least 300 cookies total - - At least 20 cookies per unique host or domain name For practicality, individual browser makers set a limit on the total number of cookies that any one domain or unique host can set. They also limit the total number of cookies that can be stored on a computer. @@ -98,14 +99,12 @@ function FindProxyForURL(url, host) For more information about how to write a PAC file and about the different functions in a PAC file, see [the FindProxyForURL website](https://findproxyforurl.com/). -**Third-party information disclaimer** - +**Third-party information disclaimer** The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. ### How to improve performance by using PAC scripts - [Browser is slow to respond when you use an automatic configuration script](https://support.microsoft.com/help/315810/browser-is-slow-to-respond-when-you-use-an-automatic-configuration-scr) - - [Optimizing performance with automatic Proxyconfiguration scripts (PAC)](https://blogs.msdn.microsoft.com/askie/2014/02/07/optimizing-performance-with-automatic-proxyconfiguration-scripts-pac/) ## Other questions @@ -135,13 +134,13 @@ For more information, see the following articles: ### Where to find Internet Explorer security zones registry entries -Most of the Internet Zone entries can be found in [Internet Explorer security zones registry entries for advanced users](https://support.microsoft.com/help/182569/internet-explorer-security-zones-registry-entries-for-advanced-users). +Most of the Internet Zone entries can be found in [Internet Explorer security zones registry entries for advanced users](https://support.microsoft.com/help/182569/internet-explorer-security-zones-registry-entries-for-advanced-users). + This article was written for Internet Explorer 6 but is still applicable to Internet Explorer 11. The default Zone Keys are stored in the following locations: - HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones - - HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones ### Why don't HTML5 videos play in Internet Explorer 11? @@ -151,7 +150,7 @@ To play HTML5 videos in the Internet Zone, use the default settings or make sure - 0 (the default value): Allow - 3: Disallow -This key is read by the **URLACTION_ALLOW_AUDIO_VIDEO 0x00002701** URL action flag that determines whether media elements (audio and video) are allowed in pages in a URL security zone. +This key is read by the **URLACTION\_ALLOW\_AUDIO\_VIDEO 0x00002701** URL action flag that determines whether media elements (audio and video) are allowed in pages in a URL security zone. For more information, see [Unable to play HTML5 Videos in IE](https://blogs.msdn.microsoft.com/askie/2014/12/31/unable-to-play-html5-videos-in-ie/). @@ -159,7 +158,7 @@ For Windows 10 N and Windows KN editions, you must also download the feature pac For more information about how to check Windows versions, see [Which version of Windows operating system am I running?](https://support.microsoft.com/help/13443/windows-which-version-am-i-running) -### What is the Enterprise Mode Site List Portal? +### What is the Enterprise Mode Site List Portal? This is a new feature to add sites to your enterprise mode site list XML. For more information, see [Enterprise Mode Site List Portal](https://github.com/MicrosoftEdge/enterprise-mode-site-list-portal). @@ -185,35 +184,31 @@ For more information about how to configure TLS/SSL for Internet Explorer, see [ Site to Zone usually refers to one of the following: -**Site to Zone Assignment List** - +**Site to Zone Assignment List** This is a Group Policy policy setting that can be used to add sites to the various security zones. The Site to Zone Assignment List policy setting associates sites to zones by using the following values for the Internet security zones: - Intranet zone - Trusted Sites zone -- Internet zone +- Internet zone - Restricted Sites zone If you set this policy setting to **Enabled**, you can enter a list of sites and their related zone numbers. By associating a site to a zone, you can make sure that the security settings for the specified zone are applied to the site. -**Site to Zone Mapping** - +**Site to Zone Mapping** Site to Zone Mapping is stored as the name of the key. The protocol is a registry value that has a number that assigns it to the corresponding zone. Internet Explorer will read from the following registry subkeys for the sites that are deployed through the Site to Zone assignment list: -- HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap -- HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMapKey - -**Site to Zone Assignment List policy** +- HKEY\_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap +- HKEY\_CURRENT_USER\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMapKey +**Site to Zone Assignment List policy** This policy setting is available for both Computer Configuration and User Configuration: - Computer Configuration > Administrative Templates > Windows Components > Internet Explorer > Internet Control Panel > Security Page - User Configuration > Administrative Templates > Windows Components > Internet Explorer > Internet Control Panel > Security Page -**References** - +**References** [How to configure Internet Explorer security zone sites using group polices](https://blogs.msdn.microsoft.com/askie/2012/06/05/how-to-configure-internet-explorer-security-zone-sites-using-group-polices/) ### What are the limits for MaxConnectionsPerServer, MaxConnectionsPer1_0Server for the current versions of Internet Explorer? @@ -222,8 +217,6 @@ For more information about these settings and limits, see [Connectivity Enhancem ### What is the MaxConnectionsPerProxy setting, and what are the maximum allowed values for this setting? -The **MaxConnectionsPerProxy** setting controls the number of connections that a single-user client can maintain to a given host by using a proxy server. - +The **MaxConnectionsPerProxy** setting controls the number of connections that a single-user client can maintain to a given host by using a proxy server. + For more information, see [Understanding Connection Limits and New Proxy Connection Limits in WinInet and Internet Explorer](https://blogs.msdn.microsoft.com/jpsanders/2009/06/29/understanding-connection-limits-and-new-proxy-connection-limits-in-wininet-and-internet-explorer/). - - diff --git a/windows/release-information/resolved-issues-windows-10-1607.yml b/windows/release-information/resolved-issues-windows-10-1607.yml index b586fa4b0e..829cea21b4 100644 --- a/windows/release-information/resolved-issues-windows-10-1607.yml +++ b/windows/release-information/resolved-issues-windows-10-1607.yml @@ -32,7 +32,7 @@ sections: - type: markdown text: "
Summary | Originating update | Status | Date resolved |
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. See details > | OS Build 14393.2608 November 13, 2018 KB4467691 | Resolved External | January 23, 2020 08:10 AM PT |
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. See details > | OS Build 14393.2608 November 13, 2018 KB4467691 | Resolved External | January 23, 2020 02:08 PM PT |
Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | OS Build 14393.3206 September 23, 2019 KB4522010 | Resolved KB4519998 | October 08, 2019 10:00 AM PT |
IME may become unresponsive or have High CPU usage Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage. See details > | OS Build 14393.3204 September 10, 2019 KB4516044 | Resolved | September 17, 2019 04:47 PM PT |
Apps and scripts using the NetQueryDisplayInformation API may fail with error Applications and scripts that call NetQueryDisplayInformation may fail to return results after the first page of data. See details > | OS Build 14393.3053 June 18, 2019 KB4503294 | Resolved KB4516044 | September 10, 2019 10:00 AM PT |
Details | Originating update | Status | History |
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. Affected platforms:
Workaround: Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart. If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled. Resolution: Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device. Back to top | OS Build 14393.2608 November 13, 2018 KB4467691 | Resolved External | Last updated: January 23, 2020 08:10 AM PT Opened: November 13, 2018 10:00 AM PT |
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. Affected platforms:
Workaround: Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart. If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled. Resolution: Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device. Back to top | OS Build 14393.2608 November 13, 2018 KB4467691 | Resolved External | Last updated: January 23, 2020 02:08 PM PT Opened: November 13, 2018 10:00 AM PT |
Summary | Originating update | Status | Date resolved |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from WU/WSUS. See details > | Resolved | January 23, 2020 08:10 AM PT | |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from WU/WSUS. See details > | Resolved | January 23, 2020 02:08 PM PT | |
Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | September 24, 2019 KB4516048 | Resolved KB4519976 | October 08, 2019 10:00 AM PT |
You may receive an error when opening or using the Toshiba Qosmio AV Center Toshiba Qosmio AV Center may error when opening and you may also receive an error in Event Log related to cryptnet.dll. See details > | August 13, 2019 KB4512506 | Resolved KB4516048 | September 24, 2019 10:00 AM PT |
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV Windows updates that are SHA-2 signed are not available with Symantec or Norton antivirus program installed See details > | August 13, 2019 KB4512506 | Resolved External | August 27, 2019 02:29 PM PT |
Details | Originating update | Status | History |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from Windows Update (WU), Windows Server Update Services (WSUS) or Configuration Manager and might be re-offered. If you use WU or WSUS, you might also receive the following error in the WindowsUpdate.log, “Misc WARNING: Digital Signatures on file C:\\Windows\\SoftwareDistribution\\Download\\XXXX are not trusted: Error 0x800b0109”. If you use Configuration Manager, you might also receive the following error in the WUAHandler.log, \"Failed to download updates to the WUAgent datastore. Error = 0x800b0109. WUAHandler 14/11/2019 16:33:23 980 (0x03D4)\". Note All Configuration Manager information also applies to System Center Configuration Manager (SCCM) and Microsoft Endpoint Configuration Manager. Affected platforms:
Resolution: This issue was resolved in the December 2019 release of Windows Malicious Software Removal Tool (MSRT). Back to top | Resolved | Resolved: January 23, 2020 08:10 AM PT Opened: November 15, 2019 05:59 PM PT | |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from Windows Update (WU), Windows Server Update Services (WSUS) or Configuration Manager and might be re-offered. If you use WU or WSUS, you might also receive the following error in the WindowsUpdate.log, “Misc WARNING: Digital Signatures on file C:\\Windows\\SoftwareDistribution\\Download\\XXXX are not trusted: Error 0x800b0109”. If you use Configuration Manager, you might also receive the following error in the WUAHandler.log, \"Failed to download updates to the WUAgent datastore. Error = 0x800b0109. WUAHandler 14/11/2019 16:33:23 980 (0x03D4)\". Note All Configuration Manager information also applies to System Center Configuration Manager (SCCM) and Microsoft Endpoint Configuration Manager. Affected platforms:
Resolution: This issue was resolved in the December 2019 release of Windows Malicious Software Removal Tool (MSRT). Back to top | Resolved | Resolved: January 23, 2020 02:08 PM PT Opened: November 15, 2019 05:59 PM PT |
Summary | Originating update | Status | Date resolved |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from WU/WSUS. See details > | Resolved | January 23, 2020 08:10 AM PT | |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from WU/WSUS. See details > | Resolved | January 23, 2020 02:08 PM PT | |
Issues manually installing updates by double-clicking the .msu file You may encounter issues manually installing updates by double-clicking the .msu file and may receive an error. See details > | September 10, 2019 KB4474419 | Resolved KB4474419 | September 23, 2019 10:00 AM PT |
Intermittent issues when printing The print spooler service may intermittently have issues completing a print job and results print job failure. See details > | September 24, 2019 KB4516030 | Resolved KB4520002 | October 08, 2019 10:00 AM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using PXE images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503273 | Resolved KB4512499 | August 17, 2019 02:00 PM PT |
Details | Originating update | Status | History |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from Windows Update (WU), Windows Server Update Services (WSUS) or Configuration Manager and might be re-offered. If you use WU or WSUS, you might also receive the following error in the WindowsUpdate.log, “Misc WARNING: Digital Signatures on file C:\\Windows\\SoftwareDistribution\\Download\\XXXX are not trusted: Error 0x800b0109”. If you use Configuration Manager, you might also receive the following error in the WUAHandler.log, \"Failed to download updates to the WUAgent datastore. Error = 0x800b0109. WUAHandler 14/11/2019 16:33:23 980 (0x03D4)\". Note All Configuration Manager information also applies to System Center Configuration Manager (SCCM) and Microsoft Endpoint Configuration Manager. Affected platforms:
Resolution: This issue was resolved in the December 2019 release of Windows Malicious Software Removal Tool (MSRT). Back to top | Resolved | Resolved: January 23, 2020 08:10 AM PT Opened: November 15, 2019 05:59 PM PT | |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from Windows Update (WU), Windows Server Update Services (WSUS) or Configuration Manager and might be re-offered. If you use WU or WSUS, you might also receive the following error in the WindowsUpdate.log, “Misc WARNING: Digital Signatures on file C:\\Windows\\SoftwareDistribution\\Download\\XXXX are not trusted: Error 0x800b0109”. If you use Configuration Manager, you might also receive the following error in the WUAHandler.log, \"Failed to download updates to the WUAgent datastore. Error = 0x800b0109. WUAHandler 14/11/2019 16:33:23 980 (0x03D4)\". Note All Configuration Manager information also applies to System Center Configuration Manager (SCCM) and Microsoft Endpoint Configuration Manager. Affected platforms:
Resolution: This issue was resolved in the December 2019 release of Windows Malicious Software Removal Tool (MSRT). Back to top | Resolved | Resolved: January 23, 2020 02:08 PM PT Opened: November 15, 2019 05:59 PM PT |
Summary | Originating update | Status | Last updated |
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. See details > | OS Build 14393.2608 November 13, 2018 KB4467691 | Resolved External | January 23, 2020 08:10 AM PT |
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. See details > | OS Build 14393.2608 November 13, 2018 KB4467691 | Resolved External | January 23, 2020 02:08 PM 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 14393.3274 October 08, 2019 KB4519998 | Mitigated External | November 05, 2019 03:36 PM PT |
Certain operations performed on a Cluster Shared Volume may fail Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5). See details > | OS Build 14393.2724 January 08, 2019 KB4480961 | Mitigated | April 25, 2019 02:00 PM PT |
Cluster service may fail if the minimum password length is set to greater than 14 The cluster service may fail to start if “Minimum Password Length” is configured with greater than 14 characters. See details > | OS Build 14393.2639 November 27, 2018 KB4467684 | Mitigated | April 25, 2019 02:00 PM PT |
Details | Originating update | Status | History |
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. Affected platforms:
Workaround: Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart. If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled. Resolution: Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device. Back to top | OS Build 14393.2608 November 13, 2018 KB4467691 | Resolved External | Last updated: January 23, 2020 08:10 AM PT Opened: November 13, 2018 10:00 AM PT |
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. Affected platforms:
Workaround: Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart. If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled. Resolution: Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device. Back to top | OS Build 14393.2608 November 13, 2018 KB4467691 | Resolved External | Last updated: January 23, 2020 02:08 PM PT Opened: November 13, 2018 10:00 AM PT |
Cluster service may fail if the minimum password length is set to greater than 14 After installing KB4467684, the cluster service may fail to start with the error \"2245 (NERR_PasswordTooShort)\" if the Group Policy \"Minimum Password Length\" is configured with greater than 14 characters. Affected platforms:
Workaround: Set the domain default \"Minimum Password Length\" policy to less than or equal to 14 characters. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 14393.2639 November 27, 2018 KB4467684 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: November 27, 2018 10:00 AM PT |
Summary | Originating update | Status | Last updated |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from WU/WSUS. See details > | Resolved | January 23, 2020 08:10 AM PT | |
Custom wallpaper displays as black Using a custom image set to \"Stretch\" might not display as expected. See details > | January 14, 2020 KB4534310 | Mitigated | January 24, 2020 09:15 AM PT |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from WU/WSUS. See details > | Resolved | January 23, 2020 02:08 PM PT | |
TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | October 08, 2019 KB4519976 | Mitigated External | November 05, 2019 03:36 PM PT |
IA64 and x64 devices may fail to start after installing updates After installing updates released on or after August 13, 2019, IA64 and x64 devices using EFI Boot may fail to start. See details > | August 13, 2019 KB4512506 | Mitigated | August 17, 2019 12:59 PM PT |
Details | Originating update | Status | History |
Custom wallpaper displays as black After installing KB4534310, your desktop wallpaper when set to \"Stretch\" might display as black. Affected platforms:
Workaround: To mitigate the issue, you can do one of the following:
Next steps: We are working on a resolution and estimate a solution will be available in mid-February for organizations who have purchased Windows 7 Extended Security Updates (ESU). Back to top | January 14, 2020 KB4534310 | Mitigated | Last updated: January 24, 2020 09:15 AM PT Opened: January 24, 2020 09:15 AM PT |
Details | Originating update | Status | History |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from Windows Update (WU), Windows Server Update Services (WSUS) or Configuration Manager and might be re-offered. If you use WU or WSUS, you might also receive the following error in the WindowsUpdate.log, “Misc WARNING: Digital Signatures on file C:\\Windows\\SoftwareDistribution\\Download\\XXXX are not trusted: Error 0x800b0109”. If you use Configuration Manager, you might also receive the following error in the WUAHandler.log, \"Failed to download updates to the WUAgent datastore. Error = 0x800b0109. WUAHandler 14/11/2019 16:33:23 980 (0x03D4)\". Note All Configuration Manager information also applies to System Center Configuration Manager (SCCM) and Microsoft Endpoint Configuration Manager. Affected platforms:
Resolution: This issue was resolved in the December 2019 release of Windows Malicious Software Removal Tool (MSRT). Back to top | Resolved | Resolved: January 23, 2020 08:10 AM PT Opened: November 15, 2019 05:59 PM PT | |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from Windows Update (WU), Windows Server Update Services (WSUS) or Configuration Manager and might be re-offered. If you use WU or WSUS, you might also receive the following error in the WindowsUpdate.log, “Misc WARNING: Digital Signatures on file C:\\Windows\\SoftwareDistribution\\Download\\XXXX are not trusted: Error 0x800b0109”. If you use Configuration Manager, you might also receive the following error in the WUAHandler.log, \"Failed to download updates to the WUAgent datastore. Error = 0x800b0109. WUAHandler 14/11/2019 16:33:23 980 (0x03D4)\". Note All Configuration Manager information also applies to System Center Configuration Manager (SCCM) and Microsoft Endpoint Configuration Manager. Affected platforms:
Resolution: This issue was resolved in the December 2019 release of Windows Malicious Software Removal Tool (MSRT). Back to top | Resolved | Resolved: January 23, 2020 02:08 PM PT Opened: November 15, 2019 05:59 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:
Affected platforms:
Next Steps: 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 | October 08, 2019 KB4519976 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |
Summary | Originating update | Status | Last updated |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from WU/WSUS. See details > | Resolved | January 23, 2020 08:10 AM PT | |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from WU/WSUS. See details > | Resolved | January 23, 2020 02:08 PM PT | |
TLS connections might fail or timeout Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption. See details > | October 08, 2019 KB4520002 | Mitigated External | November 05, 2019 03:36 PM PT |
Details | Originating update | Status | History |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from Windows Update (WU), Windows Server Update Services (WSUS) or Configuration Manager and might be re-offered. If you use WU or WSUS, you might also receive the following error in the WindowsUpdate.log, “Misc WARNING: Digital Signatures on file C:\\Windows\\SoftwareDistribution\\Download\\XXXX are not trusted: Error 0x800b0109”. If you use Configuration Manager, you might also receive the following error in the WUAHandler.log, \"Failed to download updates to the WUAgent datastore. Error = 0x800b0109. WUAHandler 14/11/2019 16:33:23 980 (0x03D4)\". Note All Configuration Manager information also applies to System Center Configuration Manager (SCCM) and Microsoft Endpoint Configuration Manager. Affected platforms:
Resolution: This issue was resolved in the December 2019 release of Windows Malicious Software Removal Tool (MSRT). Back to top | Resolved | Resolved: January 23, 2020 08:10 AM PT Opened: November 15, 2019 05:59 PM PT | |
MSRT might fail to install and be re-offered from Windows Update or WSUS The November 2019 update for Windows Malicious Software Removal Tool (MSRT) might fail to install from Windows Update (WU), Windows Server Update Services (WSUS) or Configuration Manager and might be re-offered. If you use WU or WSUS, you might also receive the following error in the WindowsUpdate.log, “Misc WARNING: Digital Signatures on file C:\\Windows\\SoftwareDistribution\\Download\\XXXX are not trusted: Error 0x800b0109”. If you use Configuration Manager, you might also receive the following error in the WUAHandler.log, \"Failed to download updates to the WUAgent datastore. Error = 0x800b0109. WUAHandler 14/11/2019 16:33:23 980 (0x03D4)\". Note All Configuration Manager information also applies to System Center Configuration Manager (SCCM) and Microsoft Endpoint Configuration Manager. Affected platforms:
Resolution: This issue was resolved in the December 2019 release of Windows Malicious Software Removal Tool (MSRT). Back to top | Resolved | Resolved: January 23, 2020 02:08 PM PT Opened: November 15, 2019 05:59 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:
Affected platforms:
Next Steps: 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 | October 08, 2019 KB4520002 | Mitigated External | Last updated: November 05, 2019 03:36 PM PT Opened: November 05, 2019 03:36 PM PT |