From 0795bb06cd68742bbbe77d6ef23911c873b09826 Mon Sep 17 00:00:00 2001 From: MightyPen Date: Wed, 22 Jan 2020 21:42:52 -0800 Subject: [PATCH 1/7] Fixing PR 1849, about 'kb-support' renamed from 'troubleshooting'. And had docset-related flaw. --- browsers/internet-explorer/TOC.md | 4 +- .../clear-ie-cache-from-command-line.md | 86 +++++++++---------- .../kb-support}/ie-edge-faqs.md | 48 ++++------- 3 files changed, 64 insertions(+), 74 deletions(-) rename browsers/{troubleshooting => internet-explorer/kb-support}/clear-ie-cache-from-command-line.md (76%) rename browsers/{troubleshooting => internet-explorer/kb-support}/ie-edge-faqs.md (93%) diff --git a/browsers/internet-explorer/TOC.md b/browsers/internet-explorer/TOC.md index 6bd312c3b2..06bc5b95c7 100644 --- a/browsers/internet-explorer/TOC.md +++ b/browsers/internet-explorer/TOC.md @@ -187,5 +187,5 @@ ### [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) +### [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 76% 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..0171b57d2c 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,16 @@ --- 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 +author: ramakoni1 manager: dcscontentpm ms.prod: internet-explorer -ms.topic: troubleshooting +ms.topic: kb-support ms.author: ramakoni ms.custom: CI=111020 ms.reviewer: ramakoni, DEV_Triage audience: ITPro ms.localizationpriority: Normal -ms.date: 01/20/2020 +ms.date: 01/22/2020 --- # How to clear Internet Explorer cache by using the command line @@ -18,49 +18,49 @@ This article outlines the procedure to clear the Internet Explorer cache by usin ## Command line commands to clear browser cache -1. Delete history from the Low folder +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 +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 +78,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,21 +111,21 @@ 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 +::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 diff --git a/browsers/troubleshooting/ie-edge-faqs.md b/browsers/internet-explorer/kb-support/ie-edge-faqs.md similarity index 93% rename from browsers/troubleshooting/ie-edge-faqs.md rename to browsers/internet-explorer/kb-support/ie-edge-faqs.md index 578f76499f..b482acdd49 100644 --- a/browsers/troubleshooting/ie-edge-faqs.md +++ b/browsers/internet-explorer/kb-support/ie-edge-faqs.md @@ -1,16 +1,16 @@ --- 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 +author: ramakoni1 manager: dcscontentpm ms.prod: internet-explorer -ms.topic: troubleshooting +ms.topic: kb-support ms.author: ramakoni ms.custom: CI=111020 ms.reviewer: ramakoni audience: ITPro ms.localizationpriority: Normal -ms.date: 01/20/2020 +ms.date: 01/22/2020 --- # Internet Explorer and Microsoft Edge frequently asked questions (FAQ) for IT Pros @@ -35,7 +35,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 +66,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 +96,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 +131,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 +147,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 +155,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 +181,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 +214,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/). - - From e829f856293970a961fd9392d08604d1cebf3a05 Mon Sep 17 00:00:00 2001 From: MightyPen Date: Wed, 22 Jan 2020 21:51:13 -0800 Subject: [PATCH 2/7] TOC.md 'KB Troubleshoot' is revised node name. And removed leading '../' from paths. --- browsers/internet-explorer/TOC.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/browsers/internet-explorer/TOC.md b/browsers/internet-explorer/TOC.md index 06bc5b95c7..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](../kb-support/clear-ie-cache-from-command-line.md) -### [Internet Explorer and Microsoft Edge FAQ for IT Pros](../kb-support/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) From 96ac31a1730e4b48de202e9767469dc0c59904bc Mon Sep 17 00:00:00 2001 From: MightyPen Date: Wed, 22 Jan 2020 22:41:02 -0800 Subject: [PATCH 3/7] Fixing metadata 'manager', and fixing valid ms.prod by adding empty ms.technology (odd requirement). --- .../clear-ie-cache-from-command-line.md | 17 ++++++++++------- .../kb-support/ie-edge-faqs.md | 17 ++++++++++------- 2 files changed, 20 insertions(+), 14 deletions(-) diff --git a/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md b/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md index 0171b57d2c..ca00f5210f 100644 --- a/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md +++ b/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md @@ -1,15 +1,18 @@ --- 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: ramakoni1 -manager: dcscontentpm -ms.prod: internet-explorer -ms.topic: kb-support -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: kb-support +ms.custom: CI=111020 ms.localizationpriority: Normal +# localization_priority: medium +# ms.translationtype: MT ms.date: 01/22/2020 --- # How to clear Internet Explorer cache by using the command line diff --git a/browsers/internet-explorer/kb-support/ie-edge-faqs.md b/browsers/internet-explorer/kb-support/ie-edge-faqs.md index b482acdd49..de3c6e1b86 100644 --- a/browsers/internet-explorer/kb-support/ie-edge-faqs.md +++ b/browsers/internet-explorer/kb-support/ie-edge-faqs.md @@ -1,15 +1,18 @@ --- title: IE and Microsoft Edge FAQ for IT Pros description: Describes frequently asked questions about Internet Explorer and Microsoft Edge for IT professionals. -author: ramakoni1 -manager: dcscontentpm -ms.prod: internet-explorer -ms.topic: kb-support -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: kb-support +ms.custom: CI=111020 ms.localizationpriority: Normal +# localization_priority: medium +# ms.translationtype: MT ms.date: 01/22/2020 --- # Internet Explorer and Microsoft Edge frequently asked questions (FAQ) for IT Pros From 8fb90a1e4c6e14662607203a83ebf5051559d771 Mon Sep 17 00:00:00 2001 From: MightyPen Date: Thu, 23 Jan 2020 00:20:05 -0800 Subject: [PATCH 4/7] Using trailing 2-spaces (like HTML BR) on 'kb-support/clear-ie-cache-from-command-line.md' numbered list near top. --- .../clear-ie-cache-from-command-line.md | 21 ++++++++++--------- 1 file changed, 11 insertions(+), 10 deletions(-) diff --git a/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md b/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md index ca00f5210f..1b0af06095 100644 --- a/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md +++ b/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md @@ -21,28 +21,28 @@ This article outlines the procedure to clear the Internet Explorer cache by usin ## Command line commands to clear browser cache -1. Delete history from the Low folder +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 +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: @@ -128,9 +128,10 @@ goto Home ::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 ``` From 07cb80d7ed06d2a9bdc5b18d056b497562544f24 Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Thu, 23 Jan 2020 15:19:19 -0800 Subject: [PATCH 5/7] Restored a valid metadata for ms.topic For descriptions of valid metadata, please see [Required metadata for all topics](https://review.docs.microsoft.com/en-us/office-authoring-guide/metadata-for-max-content-on-dmc?branch=master#required-metadata-for-all-topics). --- .../kb-support/clear-ie-cache-from-command-line.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md b/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md index 1b0af06095..27232c758a 100644 --- a/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md +++ b/browsers/internet-explorer/kb-support/clear-ie-cache-from-command-line.md @@ -8,7 +8,7 @@ ms.author: ramakoni ms.reviewer: ramakoni, DEV_Triage ms.prod: internet-explorer ms.technology: -ms.topic: kb-support +ms.topic: troubleshooting ms.custom: CI=111020 ms.localizationpriority: Normal # localization_priority: medium From c5b46dcd85995a551cf1a1a2b9b3935e57f39f0f Mon Sep 17 00:00:00 2001 From: Gary Moore Date: Thu, 23 Jan 2020 15:20:18 -0800 Subject: [PATCH 6/7] Restored valid metadata for ms.topic For descriptions of valid metadata, please see [Required metadata for all topics](https://review.docs.microsoft.com/en-us/office-authoring-guide/metadata-for-max-content-on-dmc?branch=master#required-metadata-for-all-topics). --- browsers/internet-explorer/kb-support/ie-edge-faqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/browsers/internet-explorer/kb-support/ie-edge-faqs.md b/browsers/internet-explorer/kb-support/ie-edge-faqs.md index de3c6e1b86..18643175f9 100644 --- a/browsers/internet-explorer/kb-support/ie-edge-faqs.md +++ b/browsers/internet-explorer/kb-support/ie-edge-faqs.md @@ -8,7 +8,7 @@ ms.author: ramakoni ms.reviewer: ramakoni, DEV_Triage ms.prod: internet-explorer ms.technology: -ms.topic: kb-support +ms.topic: troubleshooting ms.custom: CI=111020 ms.localizationpriority: Normal # localization_priority: medium From 431e1dd4a9e5c919b8716f470e6a99edab2cf8d5 Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Fri, 24 Jan 2020 10:09:51 -0800 Subject: [PATCH 7/7] CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20200124091729 (#1932) Co-authored-by: Direesh Kumar Kandakatla --- .../resolved-issues-windows-10-1607.yml | 4 ++-- ...es-windows-7-and-windows-server-2008-r2-sp1.yml | 4 ++-- .../resolved-issues-windows-server-2008-sp2.yml | 4 ++-- ...tus-windows-10-1607-and-windows-server-2016.yml | 4 ++-- ...us-windows-7-and-windows-server-2008-r2-sp1.yml | 14 ++++++++++++-- .../status-windows-server-2008-sp2.yml | 4 ++-- 6 files changed, 22 insertions(+), 12 deletions(-) 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: " - + @@ -89,6 +89,6 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate 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
- +
DetailsOriginating updateStatusHistory
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:
  • Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
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:
  • Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
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
" diff --git a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml index caeed9779b..9856117a73 100644 --- a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml @@ -32,7 +32,7 @@ sections: - type: markdown text: " - + @@ -55,7 +55,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate 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
- +
DetailsOriginating updateStatusHistory
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:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
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:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
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
" diff --git a/windows/release-information/resolved-issues-windows-server-2008-sp2.yml b/windows/release-information/resolved-issues-windows-server-2008-sp2.yml index 47535347c0..8f891fdf1a 100644 --- a/windows/release-information/resolved-issues-windows-server-2008-sp2.yml +++ b/windows/release-information/resolved-issues-windows-server-2008-sp2.yml @@ -32,7 +32,7 @@ sections: - type: markdown text: " - + @@ -53,7 +53,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate 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
- +
DetailsOriginating updateStatusHistory
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:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
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:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
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
" diff --git a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml index 3dba1c748b..4a3d572494 100644 --- a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml +++ b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

- + @@ -97,7 +97,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast 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
- +
DetailsOriginating updateStatusHistory
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:
  • Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
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:
  • Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
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:
  • Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
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
" diff --git a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml index 4a7f56ecb1..f88f58ac4c 100644 --- a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml @@ -60,7 +60,8 @@ sections: - type: markdown text: "
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

- + +
SummaryOriginating updateStatusLast 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
@@ -73,12 +74,21 @@ sections:
" +- title: January 2020 +- items: + - type: markdown + text: " + + +
DetailsOriginating updateStatusHistory
Custom wallpaper displays as black
After installing KB4534310, your desktop wallpaper when set to \"Stretch\" might display as black.

Affected platforms:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1
Workaround: To mitigate the issue, you can do one of the following:
  • Set your custom image to an option other than \"Stretch\", such as “Fill”, “Fit”, “Tile”, or “Center”, or
  • Choose a custom wallpaper that matches the resolution of your desktop.
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
+ " + - title: November 2019 - items: - type: markdown text: " - +
DetailsOriginating updateStatusHistory
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:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
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:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
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:
  • \"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

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
" diff --git a/windows/release-information/status-windows-server-2008-sp2.yml b/windows/release-information/status-windows-server-2008-sp2.yml index 28cf31facc..2ea115dab7 100644 --- a/windows/release-information/status-windows-server-2008-sp2.yml +++ b/windows/release-information/status-windows-server-2008-sp2.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

- +
SummaryOriginating updateStatusLast 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
" @@ -77,7 +77,7 @@ sections: - type: markdown text: " - +
DetailsOriginating updateStatusHistory
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:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
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:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1; Windows Server 2008 SP2
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:
  • \"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

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
"