From 3a5fc30b0824cf0a58c736a74032eb63f7d217d3 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Mon, 10 Feb 2020 15:12:33 -0800 Subject: [PATCH 01/17] Added 20H1 Bluetooth policy --- .../policy-configuration-service-provider.md | 5 ++ .../mdm/policy-csp-bluetooth.md | 79 ++++++++++++++++++- 2 files changed, 82 insertions(+), 2 deletions(-) diff --git a/windows/client-management/mdm/policy-configuration-service-provider.md b/windows/client-management/mdm/policy-configuration-service-provider.md index 9d72af8a49..7ec3bd938b 100644 --- a/windows/client-management/mdm/policy-configuration-service-provider.md +++ b/windows/client-management/mdm/policy-configuration-service-provider.md @@ -15,6 +15,8 @@ ms.date: 07/18/2019 # Policy CSP +> [!WARNING] +> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here. The Policy configuration service provider enables the enterprise to configure policies on Windows 10. Use this configuration service provider to configure any company policies. @@ -612,6 +614,9 @@ The following diagram shows the Policy configuration service provider in tree fo
Bluetooth/ServicesAllowedList
+
+ Bluetooth/SetMinimumEncryptionKeySize +
### Browser policies diff --git a/windows/client-management/mdm/policy-csp-bluetooth.md b/windows/client-management/mdm/policy-csp-bluetooth.md index 225de9c9ca..1684e92639 100644 --- a/windows/client-management/mdm/policy-csp-bluetooth.md +++ b/windows/client-management/mdm/policy-csp-bluetooth.md @@ -7,14 +7,15 @@ ms.prod: w10 ms.technology: windows author: manikadhiman ms.localizationpriority: medium -ms.date: 09/27/2019 +ms.date: 02/10/2020 ms.reviewer: manager: dansimp --- # Policy CSP - Bluetooth - +> [!WARNING] +> Some information relates to prereleased products, which may be substantially modified before it's commercially released. Microsoft makes no warranties, expressed or implied, concerning the information provided here.
@@ -40,6 +41,9 @@ manager: dansimp
Bluetooth/ServicesAllowedList
+
+ Bluetooth/SetMinimumEncryptionKeySize +
@@ -390,6 +394,76 @@ The default value is an empty string. For more information, see [ServicesAllowed + +
+ + +**Bluetooth/SetMinimumEncryptionKeySize** + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Windows EditionSupported?
Homecross mark
Procheck mark7
Businesscheck mark7
Enterprisecheck mark7
Educationcheck mark7
Mobile
Mobile Enterprise
+ + +
+ + +[Scope](./policy-configuration-service-provider.md#policy-scope): + +> [!div class = "checklist"] +> * Device + +
+ + + +Added in the next major release of Windows 10. +There are multiple levels of encryption strength when pairing Bluetooth devices. This policy helps prevent weaker devices cryptographically being used in high security environments. + + +The following list shows the supported values: +- 0 (default) - All Bluetooth traffic is allowed. +- 1-N - A number representing the bytes that must be used in the encryption process. + + + + + + + +
Footnotes: @@ -400,6 +474,7 @@ Footnotes: - 4 - Added in Windows 10, version 1803. - 5 - Added in Windows 10, version 1809. - 6 - Added in Windows 10, version 1903. +- 7 - Added in the next major release of Windows 10. From 128324095188333892d3f37dccd1b1a6f52858c7 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Mon, 10 Feb 2020 15:39:32 -0800 Subject: [PATCH 02/17] Fixed http warnings --- windows/client-management/troubleshoot-stop-errors.md | 2 +- windows/client-management/troubleshoot-windows-freeze.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/client-management/troubleshoot-stop-errors.md b/windows/client-management/troubleshoot-stop-errors.md index 719976a254..3fe73d34ec 100644 --- a/windows/client-management/troubleshoot-stop-errors.md +++ b/windows/client-management/troubleshoot-stop-errors.md @@ -59,7 +59,7 @@ To troubleshoot Stop error messages, follow these general steps: 3. Run the [Machine Memory Dump Collector](https://home.diagnostics.support.microsoft.com/selfhelp?knowledgebasearticlefilter=2027760&wa=wsignin1.0) Windows diagnostic package. This diagnostic tool is used to collect machine memory dump files and check for known solutions. -4. Run [Microsoft Safety Scanner](http://www.microsoft.com/security/scanner/en-us/default.aspx) or any other virus detection program that includes checks of the Master Boot Record for infections. +4. Run [Microsoft Safety Scanner](https://www.microsoft.com/security/scanner/en-us/default.aspx) or any other virus detection program that includes checks of the Master Boot Record for infections. 5. Make sure that there is sufficient free space on the hard disk. The exact requirement varies, but we recommend 10–15 percent free disk space. diff --git a/windows/client-management/troubleshoot-windows-freeze.md b/windows/client-management/troubleshoot-windows-freeze.md index 664dc7700e..c9691539ef 100644 --- a/windows/client-management/troubleshoot-windows-freeze.md +++ b/windows/client-management/troubleshoot-windows-freeze.md @@ -251,7 +251,7 @@ If the physical computer is still running in a frozen state, follow these steps Pool Monitor shows you the number of allocations and outstanding bytes of allocation by type of pool and the tag that is passed into calls of ExAllocatePoolWithTag. -Learn [how to use Pool Monitor](https://support.microsoft.com/help/177415) and how to [use the data to troubleshoot pool leaks](http://blogs.technet.com/b/markrussinovich/archive/2009/03/26/3211216.aspx). +Learn [how to use Pool Monitor](https://support.microsoft.com/help/177415) and how to [use the data to troubleshoot pool leaks](https://blogs.technet.com/b/markrussinovich/archive/2009/03/26/3211216.aspx). ### Use memory dump to collect data for the virtual machine that's running in a frozen state @@ -284,4 +284,4 @@ On Windows Server 2008, you may not have enough free disk space to generate a co Additionally, on Windows Server 2008 Service Pack (SP2), there's a second option if the system drive doesn't have sufficient space. Namely, you can use the DedicatedDumpFile registry entry. To learn how to use the registry entry, see [New behavior in Windows Vista and Windows Server 2008](https://support.microsoft.com/help/969028). -For more information, see [How to use the DedicatedDumpFile registry value to overcome space limitations on the system drive](http://blogs.msdn.com/b/ntdebugging/archive/2010/04/02/how-to-use-the-dedicateddumpfile-registry-value-to-overcome-space-limitations-on-the-system-drive-when-capturing-a-system-memory-dump.aspx). +For more information, see [How to use the DedicatedDumpFile registry value to overcome space limitations on the system drive](https://blogs.msdn.com/b/ntdebugging/archive/2010/04/02/how-to-use-the-dedicateddumpfile-registry-value-to-overcome-space-limitations-on-the-system-drive-when-capturing-a-system-memory-dump.aspx). From 1b55043257fd4193c1e5d224ebf73d5627addc86 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Mon, 10 Feb 2020 16:15:11 -0800 Subject: [PATCH 03/17] minor update --- windows/client-management/mdm/policy-csp-bluetooth.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-bluetooth.md b/windows/client-management/mdm/policy-csp-bluetooth.md index 1684e92639..b8c197552d 100644 --- a/windows/client-management/mdm/policy-csp-bluetooth.md +++ b/windows/client-management/mdm/policy-csp-bluetooth.md @@ -426,14 +426,6 @@ The default value is an empty string. For more information, see [ServicesAllowed Education check mark7 - - Mobile - - - - Mobile Enterprise - - From 13ca80891567b7b460c2dd486031f8a82e8c6f2d Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 11 Feb 2020 08:45:56 -0800 Subject: [PATCH 04/17] minor update --- windows/client-management/mdm/policy-csp-bluetooth.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/policy-csp-bluetooth.md b/windows/client-management/mdm/policy-csp-bluetooth.md index b8c197552d..ccd311c9f6 100644 --- a/windows/client-management/mdm/policy-csp-bluetooth.md +++ b/windows/client-management/mdm/policy-csp-bluetooth.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.technology: windows author: manikadhiman ms.localizationpriority: medium -ms.date: 02/10/2020 +ms.date: 02/11/2020 ms.reviewer: manager: dansimp --- From 7e703a77537165f85188d33e3f2aa649c10a061a Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 11 Feb 2020 09:04:10 -0800 Subject: [PATCH 05/17] testing --- windows/client-management/mdm/policy-csp-bluetooth.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/client-management/mdm/policy-csp-bluetooth.md b/windows/client-management/mdm/policy-csp-bluetooth.md index ccd311c9f6..be4ffce043 100644 --- a/windows/client-management/mdm/policy-csp-bluetooth.md +++ b/windows/client-management/mdm/policy-csp-bluetooth.md @@ -7,7 +7,7 @@ ms.prod: w10 ms.technology: windows author: manikadhiman ms.localizationpriority: medium -ms.date: 02/11/2020 +ms.date: 02/12/2020 ms.reviewer: manager: dansimp --- From 8e4f85ca48e8f12dd34210799e60879868757ed3 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 11 Feb 2020 16:20:53 -0800 Subject: [PATCH 06/17] Added a note --- windows/client-management/mdm/policy-csp-bluetooth.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/windows/client-management/mdm/policy-csp-bluetooth.md b/windows/client-management/mdm/policy-csp-bluetooth.md index be4ffce043..8e384d21f3 100644 --- a/windows/client-management/mdm/policy-csp-bluetooth.md +++ b/windows/client-management/mdm/policy-csp-bluetooth.md @@ -443,11 +443,15 @@ The default value is an empty string. For more information, see [ServicesAllowed Added in the next major release of Windows 10. There are multiple levels of encryption strength when pairing Bluetooth devices. This policy helps prevent weaker devices cryptographically being used in high security environments. + The following list shows the supported values: - 0 (default) - All Bluetooth traffic is allowed. - 1-N - A number representing the bytes that must be used in the encryption process. + + >[!Note] + >If you wish to enforce Windows to use Bluetooth encryption at all times, but do not care about the precise encryption key strength, use a value of 1. From fe4edd0b33c44cd925b17cd6b6ac052c2c0ea4b1 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Tue, 11 Feb 2020 17:02:43 -0800 Subject: [PATCH 07/17] More updates --- windows/client-management/mdm/policy-csp-bluetooth.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/windows/client-management/mdm/policy-csp-bluetooth.md b/windows/client-management/mdm/policy-csp-bluetooth.md index 8e384d21f3..2160f0b07a 100644 --- a/windows/client-management/mdm/policy-csp-bluetooth.md +++ b/windows/client-management/mdm/policy-csp-bluetooth.md @@ -448,10 +448,8 @@ There are multiple levels of encryption strength when pairing Bluetooth devices. The following list shows the supported values: - 0 (default) - All Bluetooth traffic is allowed. -- 1-N - A number representing the bytes that must be used in the encryption process. +- N - A number from 1 through 16 representing the bytes that must be used in the encryption process. At this time, 16 is the largest allowed value for N and 16 bytes is the largest key size that Bluetooth supports so far. If you wish to enforce Windows to use Bluetooth encryption at all times, but do not care about the precise encryption key strength, use a value of 1. - >[!Note] - >If you wish to enforce Windows to use Bluetooth encryption at all times, but do not care about the precise encryption key strength, use a value of 1. From ac6c580fe88dfabd20ffe988454ef233ee2e9e67 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 20 Feb 2020 14:23:01 -0800 Subject: [PATCH 08/17] Update TOC.md --- windows/security/threat-protection/TOC.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/security/threat-protection/TOC.md b/windows/security/threat-protection/TOC.md index c969d4994f..418d1ceaa9 100644 --- a/windows/security/threat-protection/TOC.md +++ b/windows/security/threat-protection/TOC.md @@ -103,10 +103,10 @@ ###### [Investigate entities on machines](microsoft-defender-atp/live-response.md) ###### [Live response command examples](microsoft-defender-atp/live-response-command-examples.md) -### [Automated investigation and remediation]() -#### [Automated investigation and remediation overview](microsoft-defender-atp/automated-investigations.md) -#### [Use the automated investigation and remediation dashboard](microsoft-defender-atp/manage-auto-investigation.md) -#### [Manage actions related to automated investigation and remediation](microsoft-defender-atp/auto-investigation-action-center.md) +### [Automated investigation and remediation (AIR)]() +#### [Overview of AIR](microsoft-defender-atp/automated-investigations.md) +#### [View details and results of automated investigations](microsoft-defender-atp/auto-investigation-action-center.md) +#### [View and approve remediation actions](microsoft-defender-atp/manage-auto-investigation.md) ### [Secure score](microsoft-defender-atp/overview-secure-score.md) ### [Threat analytics](microsoft-defender-atp/threat-analytics.md) From 349ef5b90eebe4630bf20a026f03da3f8337c554 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 20 Feb 2020 14:52:42 -0800 Subject: [PATCH 09/17] AutoIR revisions --- .../auto-investigation-action-center.md | 42 ++++++++++++------ .../images/mdatp-investigations.jpg | Bin 0 -> 47514 bytes 2 files changed, 28 insertions(+), 14 deletions(-) create mode 100644 windows/security/threat-protection/microsoft-defender-atp/images/mdatp-investigations.jpg diff --git a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md index 67192e12e8..c2c022f1ad 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md +++ b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md @@ -1,14 +1,14 @@ --- -title: Manage actions related to automated investigation and remediation -description: Use the action center to manage actions related to automated investigation and response +title: View details and results of automated investigations +description: Use the action center to view details and results following an automated investigation keywords: action, center, autoir, automated, investigation, response, remediation search.product: eADQiWindows 10XVcnh ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: security -ms.author: macapara -author: mjcaparas +ms.author: deniseb +author: denisebmsft ms.localizationpriority: medium manager: dansimp audience: ITPro @@ -16,27 +16,41 @@ ms.collection: M365-security-compliance ms.topic: article --- -# Manage actions related to automated investigation and remediation +# View details and results of automated investigations -The Action center aggregates all investigations that require an action for an investigation to proceed or be completed. +When an automated investigation runs, a verdict is generated for each piece of evidence investigated. Verdicts can be *Malicious*, *Suspicious*, or *Clean*. Depending on the type of threat and resulting verdict, remediation actions occur automatically or upon approval by your organization’s security operations team. -![Image of Action center page](images/action-center.png) +Pending and completed actions are listed in the Action center ([https://securitycenter.windows.com/action-center](https://securitycenter.windows.com/action-center)) and the Investigations list ([https://securitycenter.windows.com/investigations](https://securitycenter.windows.com/investigations)). -The action center consists of two main tabs: -- Pending actions - Displays a list of ongoing investigations that require attention. A recommended action is presented to the analyst, which they can approve or reject. -- History - Acts as an audit log for: - - All actions taken by AutoIR or approved by an analyst with ability to undo actions that support this capability (for example, quarantine file). - - All commands ran and remediation actions applied in Live Response with ability to undo actions that support this capability. - - Remediation actions applied by Windows Defender AV with ability to undo actions that support this capability. +## The Action center + +![Action center page](images/action-center.png) + +The action center consists of two main tabs, as described in the following table. + + +|Tab |Description | +|---------|---------| +|Pending actions |Displays a list of ongoing investigations that require attention. Recommended actions are presented that your security operations team can approve or reject. | +|History |Acts as an audit log for all of the following:
- All actions taken by automated investigation and remediation in Microsoft Defender ATP
Actions that were approved by your security operations team (some actions, such as sending a file to quarantine, can be undone)
- All commands ran and remediation actions that were applied in Live Response (some actions can be undone)
- Remediation actions applied by Windows Defender Antivirus (some actions can be undone) | Use the Customize columns drop-down menu to select columns that you'd like to show or hide. From this view, you can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. - >[!NOTE] >The tab will only appear if there are pending actions for that category. +## Investigations page + +![Investigations page](images/mdatp-investigations.jpg) + +On the **Investigations** page, you'll find a list of all automated investigations. Select an item in the list to view additional information about that automated investigation. + +Use the Customize columns drop-down menu to select columns that you'd like to show or hide. + +From this view, you can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. + ### Approve or reject an action You'll need to manually approve or reject pending actions on each of these categories for the automated actions to proceed. diff --git a/windows/security/threat-protection/microsoft-defender-atp/images/mdatp-investigations.jpg b/windows/security/threat-protection/microsoft-defender-atp/images/mdatp-investigations.jpg new file mode 100644 index 0000000000000000000000000000000000000000..6fe755e85762552d398e0605eb6f387d40fdd4cf GIT binary patch literal 47514 zcmeFY2RvNg_BVX=5+wv7h#Dk%C(00s5)mT0C<%fnBcendB}A`5LX<>H(Zh^BBsx)p zFc_kjQAQo6yp!K8&%OV0|L=X@`~08h^Stkw4>RZNbM{_)t##I3>$}z_{3Of+=WlE4 zX#*t0k3I1N5byxcom-kWc}<)gTs*<ym0R!75`Hf znefzi)B-oE+gXiAb_Hc0c}LLDvR!27xO7EGSmf$8Ie7&|CFSc{H*aa{=<40RZ(?d@ zZeeNV;OO+&*~RtAGap|+|K|aLkuRd6U&h47rKP{h$jo~ECi{J1QE^G>hmW6XzSP!1 zVf77-U%z#9c6Imk_KlAH7@wH@IW@iTYjJ6LWp!s+w z`u`ry5&w^f{wvLYC7I9$Fj13OktUFl5UFP(A!8yTOapXeB*YUkCIAHN$8RED)MuDk z0?bN)3II5SQ9dUvaxz45CSy>-I4pRt;1RBM6(8770776V!=wHE&^}~pnT^Y z_~+|nXE&B0{jQ)L=YYZ7zP0w5CAnH0?>*e0C5FmXMteMx+0O4SW|%KZ|?j6;OBDi zfyA3bU<81b$o~W6{wVki1wZ)&fM6xWIi*989t5D%h&0jfkp{CtZ#UAD0PJ4V;G2BR z6_EZEkAUo%wEg|9B)Aqu>_HCx42-`<z)blKY_0Q*1;%he^hX5iH*(^ z04Q=%*P#{pjL2uF-+acp0B0dX*uyO1wD$_gP{*MC2|FSqi8}Ll`ltT?wMXO+5Ni4+ z6u&Y?1?PLvH6PTvp7nC?jWrb9*f6uoeEr_?igRo|vyQ0D(!mgK!qHZU>lWqE%aVZd zsiMc;f&yZCO4Dy0kKU1V+d;a2zz@d>z=5oe(OO{FM;9hfxX;CN9|%A{G_M{({}E4< z^u1xwp*LAMGDt4mX$ucIeRhg%<<|6UwL8^0#O%CV^y%`=JKr+4CE@I0YC4}ep{wCI zr`5Apu{4iLy%1FRG@_pTLSNu#k08+_b92a*4^Y>NY(#6aVP5w`-w)3p|6(sUeI-a; zEpk=PRraeSn{q{S@mz41%Vq5ceV>Keyf|5#z>i03)^gL__9s6hH7z@fS}#|Ao*)3D zYtSG4;muM%^)lr}>C_#foB5_*l&tn};Sbqwhi3GW z!VXJ2Co8|zHEydr?Y{4_RLDfPJAR+Kc2mZ~!Y(S)te)x3ozGl1gr?)`W!Vlq=lrl@ z@NbRjvjXS$*uA3N7V~AGB@~s^ebB|(@i||`06#Kb)JU*^@&s4 zbePHoliA{n>S(xKEh-d`f=lv?P0H95g0YlCV|M#u--8zVyC5jGxDB5RwcZ+OR$oV& z+d9v&7nr%ed!aBPwS|GoN*lR>zTmb^a<*|OV*=1-uAdEU$Zfs+crtBFXY(^!DF5DW zMUg`qO2Y;JoyOEH=Bq}k^)`C^US#mff>XZ$Gub=AFlC4`CaxRWpBrGVzTI==LN+U94*>XtC_DucZ;gEdas>% zG{K7t!Rh|{a%OtRHL$^BOu1^})HYWBd8@~w_P%(%2`o&XzSdpcOu7f!do`oYoN1uu zy~4t(lqcsb0?+wtRP>XT)zJu|xW`;i7_oQko3$8ZXJfYVOlzUkmHK&_QoD=B*~7G( z3S$(O-o<814>01qHdUy>3DFd*y2EXpc&T{faSOJLo7wsdj;p~O$Upj_di^Feb6Bvi z>-l`t_c1V~n=D7-mqz97d%`5q!|eRf4qfx~Qr6(2e z&#y-%G78-;DnNHGiLvcav<$2{$Jj&^m!zrHBsdI2=_Zb|i=tGsUmf@%Z|3`C8$*r` zb8PQ+C2LnSL7NnE^p2Ms4V%n`1A-MYf9XNzY%$MND=z&KOq&;LV!4^x@tF*kUR9|5 zEoDRIXR#ABTh#Ng5xy`msUHvv2^z9Xhppx36(85{zDj*@Eyts?EmpH3G2gdqNk*5c zpNXbJFhYyc9PsG(gXWf>^xN4*;g+)NfTfnCQ>wm38L@b9546len_$HUXCsAm8BL<6hj!u#f#fWJ5s3x`@aHe*4Iban zQj8JBfa_3~pC=j}3eIx*hEh`P33W(qXJ@C(#}L=J{EwhXEYEP1ac8J;M}#(yFfTCG zx79|DV(;zw=IAZL-j&qt#_B)Ag5r*CQ$8!?N>ezcTP+5h{uqiZsg{I)UIsOEZ*oI~ z)Wu9;MvyOn-QlP6TM+?aWQugpsvPxe1R^|NwgI5KkZem;xpLipSUM?1V&<|I{Y(UH zrt%WWFv(c;VF8Vm$|I@rB)!d_^Pl$Hx_P0D%4!sVc9nHrh0Yyx>r^*alJ1Zu?Cp{f z*{G=F8LCN%i_0N3eJp`4DMT^Ih>Ty?QX?g*SJ^$SZJT|uWVWHV8(s&1dg}x@`%tHj z%gO3*>3j}{)Iz*GwZx3bQ`jeN%91{!EB=c6 z6_(iM(=Nb!xhuN{`7n?>sm`O&+Nv2EGw0jSmw0ni_$OX>Nm>cG$iO}JRKlb{neO(r zz@V0#$e^Dq)y;9dvC2GLsNOCM7DxfV8 zqdlM>K`P?zIjvIaIBmB(bh^I30jkNj+dPHmr*;|%xZTQQw~YFFa|CcqX{7SIMIIpS z{KA#v<)A{%qTkk4<5Q4iy8lR^<;FS4rqk!KAqVD^K&tf{`#%}=@^us0?tEij-z0H- z%?_gjPf4Xnz8yT#s(bxeR_=M%xYny9r&>1j}eD{QmN; zEA?7!yvH>Q*c0YvV=DJ+t1C8d?j2L#fm8IVh285dEnUSyY&=%Peev*e_ZIo}@->vt z`JVyB*Phl!^TnX2Vp4;1tMlc=9Ng-s{a5oYVtJbMgXbz{FV)R%^GwXach%1_`D%9$ zG%YK*dvzF!Kz+B>yN&oU%Vtw&HGOaT!J?h=9{En6*0At$6&9FnlbwFRI>u9d0{LxZ z#(kgTRjkyQG&-DA?M;Wn&dQB*j-mj^bw@jYEXXi(wr4!hZpV!1Lh*p*wB)SVbBn{f z*ld}Osb7OGs z!SuAqfRi-k7N04}3osf|*kMujTvUKFS>EgRd4{EjQQuo|v*nWCy>T0-2SO^^XH#|) z+dE5TsL3B8<8$$(eS4jBqckK@0y;k*?z3!#oN2r&@Y+_lFZR-pjD%ITth*BZ<}@s} zLOm};eHlJT03=gw(P~_uzqtw8TKJe`WZsi9x|ybbe0M8aVVw==3rNy7Np}-Q`cAn* zEI~mvX4Z4P7>S&K)+`kFMgNcVoh7l$jo(yaV>}WDzF*1^uy@zsXzmn#`W53zo7hHr zzZHre+irn#`VT`g;pK4sO4*#eD^bwTMTHzQIn~JIHzup_JKoBh(NrJSovaP&bOFEl zE!C@zg1ycAVKjqYcTvrkTyDaajk{2uEIJvFe=?Y_0DSku(*_z;$>6H~k_C-#C!-;Y zQ}E4?1Yp=Wjl*`ay>a*x2bs}*IY@cu)K{Y1mLyrB<@s> z&hA9BSrc)$i2%U0!?+0mwQvk%jWdV!8zJ=J#h-U#HUuk~voKnsa zud-g^kPs zQC08oV6W0a{-HvX{(f7Se)I0n`hV`4NSigWkt>cl6BpZ?KEWGY^l)t%T@LIt&nz(9qq3d zjfn;(US5MOM1B7en#p6zT)oI!@1R!+rQvQ^;;Psvr%iu@#>45c1hc6~Cp9fQ+0TrJ z`9>jE3)J5a!#~_KRhbWtn(hWn&&^zT`|R$7 z-vQQia-L@wLgjptNeM5#h>jY#Z2$B!Qd+hpmgH$(Q3SB9$*p}=k{9vJG{#78O}T)2 z)F)+uUAoOvdHw*D47LI)pM7X|%Hvl zL8hl;VtRtt!amW64czzur0J3-hJDD+ElRv3IA9eVVDGu=EgPO&f4`c2A*KsZO`(D2 zPfTL#=$qjSD9oC9hzFv5@3|KU+VzJ+TmXJ85Jq)k{@M3)Ht=!}%-Ure zIB`)F*MCyn?^xB|*53V4gQcV;Vp@x(l3%9uO;1R%|Fzt57@d|(#3y~y{%$!)8`h7$ z_7LK?B)tJmQy7vT*}HmeVK|%tDeL9L>BV8FBv!=QvyzmxRf%qa%e$R(?w>fqN@7$} z>7NYr@a~ z9J!NL&$stoIm21PJTi-d;ihijlB@%BC|nw%KX|&17Hrs4$a2YZgc(J(d2&fl&)H5) zHzhIVTxO7dd4G5my|2GAo3&Wrfo?j>K+Y>;^@=;c%_1t!Ny-!~Kdtvg)rZ>qvjE5w zJ-P9opqO+QhyCjnrtG3JX+LHn2im7gjvj3)uScDt7o9}BL|i1H61#*%+fvB;Y!v< z>*0)Q)?qOL5XB8ueg0)2zRR}#bGw)QjWR9Sh2usF-t;kY;+;6ZhXjBgN7O9;d%CgL zlw6j(x~QUOWTXP0Atp<${GbtV(`rF)u}E*Ogw)ir$jIcbl-XB#^727b{7D&BjJ?cNOjE~^+k9pWeVT_^d`OPH()J+LXJO5e4+YIWhwt1A9052Ce7T()*DwsqC=a`O#o;l zUeVaqA)GV?1A5zNEzBc6rXc}-t`o4|036JiJIH$vOO3%d6xb1pLa zlHvwycnN?-Q%X|cb#&=FV84^obrqa{Fbv7S-|CS+=T;P8pCPFGCZkWvz6}1HyP=(1 z_kj06F5rNXzwdU^?RVrAG~G%=0{dJzsh~I@1YjZQ-k78uFV1r7ty=oz;HT8P6duKu z7f3cy`Y7Q{f6;HSiCeWw{ZUV!J{^jlvtEpnhC7^lP=u^G5@$sK8bK+a1k=LQLr=;H z0G|bXa|CqYen7I8eGwa34%wXJ!Likn49d4(ycvLoly@O(71Rm9EaIrl0Xmz92r_CU zQ`v+Ze#Y+>&`&K~WNN;n%Pe|T-~%0XPmh4=UP|aIde@Js4ACE^vMq%lNL}Uctb={j zYI1*~J8j6(ts19jpx#L8_wxguaZHe!TM&HJPiTGBU4rWxc9grH-JdDCN2A+QR%fG( z0Pu91SDeOs5JMq)wj3AwdDPW*vlkimtgredCX7B5NFk%i`n5R*1?{AQF@k|RI4}X| zy**oT7LAlV;aO^3dO%dsXNFUP+UJek1LE}0Bb;2rcwvUpZ(`P-MP~d;-Zxyyaock@ z!Y7|LdLMCO`qMAU2w-nxFRq&m;h6=GCm#?16}(Ha z$Gn;X&G(MD(VBXxtAgTST|Bt150*|+&Ebwp5QT-YP<7$ca~H|@vR4?CPY&2?(| zWVQP6SrZ3R0B&fo^>Y)!v7<}l5X(2%c`i+_txIp?u1YrWE~vfDi@|i^^S}Zcl$yueQDTj~h^%dGeE|I78&cbQ3 z3BW{Le;xc>sODr&1w3&F^TkZb?7KspRB(OzqwrpU;#?k%%1U9Fa+ZI#V^_(m=IZ?@ z^7%6XkC&ksxk)>1YZR=_*~Fio74|w zgO^tx*Nlvo-`Sga<-OaSCZw$q5W4S}INJkA*?OC#P`_&M+s9gi_Zta6#8z zq2+6=HJaRNx1_|3C{z8^h<7u_cjT+=f1g18@lrfV4W#Y=b>$5;}DSZz+u#;4up{JezuX6%31k0MBfu+|AzeV_GW~esK?|s|+iYhx12&i22>B*o z+;qWW?dXUhP55n>{Iud_*`7HQ3W}q&oa(;Aey5M?E%47*N;ZvUz_-&uQ;DX?bC>=c}$_EQfi#KA_ zP1^xLS7;hyZH@LjIN&)vLGDlfh;6=DeEs!+!E#EWbIw%_(~h`4A_UJs<_TN~e;WpX zDu;+LOxE04{3+4$hxEXnE_^;9*D+y1` za0Y%kn@Db?FUvBx*gG3CWIC0R-rjiUuAr_$245Jn?gg($?NBO2Y8pxRIdpPXoIk$R z74I6-1FCGV?1eW!-%ZLa6$PlCNci`Ts=DJP7pB$gSLGF;dHF9MKn^m8cS5iPfa6){ zla)?rK1FfOR0q61k@T9hI6A4LS`aTd?s?m6gsqJh;38=wOE6}yC5a6w#MNwbR`tAR z_++L9&;Nyx;p;X*a&CcNI~N;dU|Q$bAL)N5?KVm+X^7DsA(yRgBkGf+I3U#+gR|ir&?)}iI>(1mX-0IrZb&nt}aJHZ3vRf2>fDBIaK%lVpaEQx6Cp}jw|%hs9QoNBC$1$>qSePhdK?oTMrhR0FQ zUTgZD0o4?%pa@eFMHOtAq zF_@oPYs?c}9vv4RDR`K_Xm9y7_)14A6A8W4Cn ziU9C#+MON|akX3JfScnmITX2hAGe^v&Hb08$=|0?{`F_9LQ3GTVPd7TJenE||G>W| zTiuC6qFLkdEf)xY_K?Qqm+$sUt&WJl|3o}n;A}BAnw{$l-TW&j^X~hcQnd5_(}r4W zF7&kuDELI_+1Ie^*MBD`{`08eU)Ofc;22H|)a3hwPykP*Heo{JLVgd$+TUot?AM^m zN>P-RtsFutDXDFwA@H;C@13FVB>l5zxzaFKL1V_t@Yr6*xaYU~w%a}_;6AQ4Q-7mX zWH!no<1}IGo##NU< z=9XrqK_G{fZ$PWy%>zXj_P@=B{Y8`{`^TMN3~eV7jff=xh0XwbH%*&vHo zi;>Z>n%%ARl6>XzTSnEpyLFjY*(=1W>t3~DXuFsBQWX2b&*!J9ewG#s5LWcBJZvGt zevB#Vv!HnxxMkb-Px@pmP*}ha)M@o`&4MgV@R+Kf5u;bSYzV*@O30u`PhN%r)Szcm3 zH?ZzrrfE#o_mh0_>`e2@Gt0RNu&1ROs7c+fe?Rn=XSVgnTOoTZ_?C;WcTV(o9>J20 zGO2IXZC&Vh|18R3(ha`SN7FT2q{rp_Gy%Wfb04k}8HyT1X5|<(x}NNO!4%xyF=%KA zKK+d61fQhp|7x*fU-E<2;X2<2#y@gZ4v*Y^5xRqWE?sR28b5Es^!8WwvgeuhZON6{ z@^z1(1N4g>H_tJ*z6s<60hqKt4i(E5zags2tZbim&!brkljIj(a@hg%h=H1RM4&c| zdy1Upoha<`%mnH=5hG7WxCJJiUWG)}EsH|3Lm|GHSx{GCk(olgSLy@X*>2UdQPI-m zzUZ5GSYXlS%qmJG(6T3mf|-0);P)`yPPn?$dz%Y^$l@b3v}}6nS)XVhF+^LRY>BDBb*VmoS7{jUm+bV{2T6}rYc8TqF;di0Sl3Z;$v9i_%$Zi7VK+-N}X zR2W1LlCkZVy)}Bvw^Yo%r^Z&M-dMxw?8=yj{q@AY^2ja?HI0u}pff-4wr&;?QA3Pi zE&CBC-NtSf6-&^t_$Fn~g(PJz_$erJv&z59!MZlD zBxuK7@sf?=I(zA%X673yK8^Stq~P+&E#VE+NT&Us!4levM!Yk@T(`k3BiH}#cm4qC z;5w#yk+S!T{jQm}m`di`xUFo`^(Pb$#vW%jDpt9-68!~XFgC~MXl;O7u>%A2 z#P?8ty|Brl20m?8jnd@U?Z71j_0QSqV=el(T3!OZ!@YCk;Gd+Mu#dvAH0Tz{&7M3<2- zfP>>Tu16c7qy1nlIMF8sIbre4nm>fBm}H5<{3X9mLXvvIv2Fo!GPYLMoku}#qCx97 zYpT4{Fe|!+(^2{#Uc5@dCZ?uFrg*GBuT;?!%Fk%X7%s2bbUn4Duk4zZEvT9lZuqfW zohtxK)M97F4k`HB0-VMI$yTu=#+!CZkBpjO-=@t%R`rrpo7Rb_#70L zadbVK@-Noy?+O6^>5C>gJE1HjPU>r?w7@5y%}22uiGDYWjU1xxCxmZ#f%pu;-*)TZ zf;^MRAUt@7z0sydDb<0t{Y^W0(t~aHFfUDa=vc;#K1rH^cr6Av97Bza-qN_lI>qxq z1PG5B9M%vdOPEi6dqE@M;(xp_{RgWar04o1zU3VO7;)3MR7)ZcJN-cbo*Pl=Xt0)k ziC+Je=EyLyvvTupsLs#cdWJXCTa?cd(v(*c>ulY2W>n$jw2IU8N$+hc9-6z})I^At z1!p?PL>trAx^J2Oc*z+<#bpdzh2)lFTvuv&FxJaK_`uUtorUu2EJ-5sCKf`9OenG9 z$L`x+?U7Ds{|K-7l(q<0l=Jivrm1c{^aa8fX}(bl|ImY#EdDxr-MT=wEasbdtr&dM zlm+_p#TyK^DkoW3C@~`w5!@6Q;I0nagb%?h-#k5VQ)W$lZ(L&?Z_c$3%*G6Xe8AvP zL%BH^+}wYoF;>)SmNo00HJ+(l5ygMpW2a{0M4#D~YSblouE{>+rJIt?K(n+Gi#Yeh zDP9G4JUMjl0A_G;)-7bhOaM%~p2!~GLmMy9*L3-&2pUrMvuC3xIXPQSlw-S2p{{(y zGSKe;&43TYo}FUi0~Tx~jh^6}&$+3l1XQM#NS# zS`ACzRjL&!igWh8%cj~F5I*556k6D+o(kCNN=Caa9iM&cAHgA5Jr06Y?g7zPG#@8& zu@7yJe2u=BJ{$ zX}r)-V;Ze>{<%^iEUo5Xy1foNi>z3BsZlM{DSN8{m0>2<9A*Bnk2@+(_M@`7lLRB* z7ai+E0uT<)%yzkKHwhU?R8?^Rz(VZfvAM6LoHZr^8i=2@XRnmvd({0wKuphC!nCd& zJvW!lhqT6&?we0enmwD=315K9)S=t?`)Ls|?<~#a6CL+8XT?VQ>(xhdY}n36_8WN< zl~1LVSo<-DRDpe-^!&ORI%yYDi5>&r4^fpa>12=MHNAIzCP6lOfBXiG|2DGu18uke zU;|^ltmE`h9cnoQfA-RMt``eEi)z^I%JGTis*?Dbt!-00oUA;Mme|wRDd=rEoR;u3 zLy6rCn}!k3%0A@uz#U_b(PGe8$9}QLEHqDPt$PaWW03*@&K~co>-oR1Ci{&v^`C1Z^Lwg|1f4(zR02FOq1wg& zBFFb{O^5G4=#vK&Y(@Z5%Ipr;@=p~4ft`bB$5GT2<*K!AU*vGri}MW1?MhtF^dFXw z23>ZVN5)=Cj+OTtdkl?MA_k_`4(V4KJGxZw)N@)rzAwm|HG5t>HRJm&8-;_>%@t(R zM!Ek+l%y|W5b0ZY;6L_V79swJE1dG*>EJIAUE%87kEw$fmDUkIc0rd6Z#~TmVeHVi z7_K{bOd40Vz|AEpSIO~mMY^e%{RWzSq)>EUds{lQ(Yn!25z_lv1#wSJ;#3sZH?((m zqw~ed%Tns#-b{=96(N3s$F#-hZuh7gVK2TgllpiUaS_ovbE7~aqU*M|rB=B#eK?_S zh^4@D53aLckG9nUbcV+QU2ad_`w{)`mILzpcQV&(1_7*|Z~@@0rwS+whilM~uY2W; zmENFkH@^Ovtmom(B?Yo}_5U!AI{s5AVgVZ~_qdYwoL_hO?TU^m09AvW{v5imJuMzN zFb4f|o^Nf9EOw9LRbWM>gM;@dF1Nh0*fGiV9lapfvHAt*w+aY+__g|BM}y%q)hOew`rmp@1dWdNwc8~BsZRgZn#-!HNL`b2 zuO_ib%G&nRjT$|{V%DwlD^84}DkvG_lqVC?K!#fwgIgZU z(@~@!{2U_d9l03mKgq zsUEn`FLD4rtCAj|^6hhmn`79Rv2Qi(+q?m@#?RQb&4e_n(~z>~)g5vRl5Si}>}F{U z-ob@Ff;RfqMcL8bAdf@$^Y;L>s0?FDl5<~o1IS!90*@{q@56uPuY+&oHDauH-45X& ze+={f*QgL_-EviP%-6faKbL}}!0Y-wZZ}%r5IrB~n+`MVX*AOj@(ZTg=h?bx&vCsa zmX3yr%9tM;1H~BBQi9d!VjJN5g)edZS^E7D`AlVOTBNIqWhk` z0$>5K{1=?M2Ob_uG|F~SvG>0*@tQFAE`JcM;x2Rr`7lMWB)3u_c`qawbEtJi2rDx; z2B*Gj<5A3f?hNYqc~%-xn&$<828k#|{%a2y(cc7|u>x)Av4Mdi55XiBFUsqlT?_=E zrA6!P9xl}3=lGa=bdG0cd$uNf*Q#K3udra6A;hkPilxJ*h)S&W(zOVXTAML7SzskI z2c?N##FT&_Q*MF1gjrN^bNPw&DJCQ2fCzEKbnOm=JyK~XB!d9;OZy?9(Uei*CfTQXBtmiqpal%V>Gm^RgJa+cc5#dKS!026K1 z(|8YPd2vSiVPKv%5B>G~#;$_tExEJP2Ugs)77sM)E%iNmf#3%5ep1=m{W0N$$)q5m zGTNRvLFM4!Zm6N~<*9X49FX}Ry{M%BKB;QOceMn;${7QF5uPG*Q$IYtt#?s4{KsgJ z3zc%Q*0v=#0IWQUOCAYQV4NdTv>@ zG`Sz29@TDvoA1U$9l0la=kyCzE1TVA#lrB*Kb>?6qgE3_Z3mH|Vdazkc$)YH z4&ML?MLYR#0ymMa)-j{fti#d|?WZXpiVQ_W>kbYhzNKf64kBDVk0*}tE!0GONG-^^ z^zbH)zQHv-)X;d7Oup)`_a zc>|;UXlw=nxClwVmGj;Few-s({72_fwv zqM{(8H|Ul5(FY9IDV@LHw5L$$2FH;g-1Ye><`D7fq)&OM!1UdHIPI_WOcRr13s__D z_T;udG@O`Q#%3K(VPs}5brnnHDZorJm7Jd^O+hbO3R&Ng0fdy4QrdEq4ix*0wVVR%GIi}OHMEALLn%*jH z!u4_MHu6hHJ3;Gpopnejr%B(^^2+5EKbElnfdkR?bH)~D`@Eu0t!GN9D0JnDctAfu z-7EU)n*{sYF!5%hUo#J}`R0t)iNXF|2zj7(4zD=@KSVL&G}??fRuRLSyO)sw{F7gdm3JLFm(%P33}_ccevcVEpR3JD~(;wlcn>snrhbMR}f=%Y4F8? z7V-U3w=+0HYYSvPR87G&(pnQH;=iLz$H0z$*B?A*)C=5tNiM1K?1q`ye$Y{C)@D#J ztRV;9Jn00s24z&jZNI(RT$6s`F~uRI`i@giiBn4;`0JI0HpEJmvfOC^(Xk8+oSQ~D znwR<>+t}^GbAR@K=6*D-cC?Mkfyq7Nx=rUj0NTZFHtzhy`@KYkKJ()ww@~Vm&Cl6hrLS73X-ikJnyouT;;9C4 z6v#jGejKn+PqCS$JntB#u0KE5~koH{$836#dn3iEZ-&q9?*JN?SBJv2pW zUVdU@@Y%t>r+x1=M#a(=6y5hPI*=olchK!a{b92d@~cyL=-B~$ zunjip5qjo&GShDntl3iR-SD&UNo|lO=P^4=0wr$=-5LBj1H_L)9Sa^WPXrF+X;cYhsZmbF=58lF*`j@Gt;#n*d^EOkhpDg^NH8mP3za^F=9Ohq~%}wrxM;_&{KtA!(K}wo*#E~cN%Ozfj7f? zR-)^sH|zS&L%{mP+`+em7agQG^o39j#&M)zX&U9B)0tgz(J8x{!@JYSRYd6)egOeDrtILPy50z<{HdMFev5?g*dfBbB?9agzq90c1u+Evy(Hv?jW7 zW_=J8j5kBv*IsgCJCt{Ktzsj(|6n(_c0lWES(BVHAgFPr_{$B^i7#vdRI zd|MhB3|#x5c0u^Yqbp6-EpBhPgS*UTw8WN8Iv)Pyvw(dn%LDJI4rP^|j^u{BIqzc+ z4q%H@bL+qB0U{xG<9;&4%#F#zsn^N8l{?lPx5ymwrSiakG~T@3V9XL3!O8V3GAZOEi1+IH-h+W-&&rQIJI2LGIrTj{*Y5$CJv1%0{o&+k7FGOT9X0S3^dfC!D|)P<}Rn zS$qsmDf+|`Cs2Z$#ZEwBCAs;ZSelz$mrjwVE*o{!U^CzBo(L({jGtRwTWJ@rDLRlT z&pQKoB8XF>^Bo4-L=!hQNoSdG(}^jywc7@+@-;g8Y}2ceYYHFr2nwga;JMm{K`IEdZkYh2?yoyXH$0oJ4_vS^_@q}`w9xd)VcxB$I%-rLR`6?0FIbDbF?%;?B9C4?a zMz@8a40YJhHI1&Z<@_D8hEU(LHpRKN`Fqg($%AjFSb7zv=NzpQ4%ajgRZNjHzRFyS zsy@f1u)|GaGy#&_#M2b&K4vSVKzwiHUJ;LxN+VZh=-kz(V^-L&-KFkXGe0~5O`bl) zh1$JyFo@WuOh*~6fO#tz&;4LZnwsAWADSg+cCpH?{R`OVeVW_)PV5V(@1tU-hy3$h zWI*TZg88Ksb@x^9yN~{LnMr3DSEARj!_aDm7_xz|9$%V{pP@FfmJssOknJn=eh{H< zMAFOA+txlPl5ucv=LC`umaYVCnmoFa2~~gij9pAqq}|$ceBP7kLw^;i@u$xTwNJ_n zOnksO9tX&+&w;^)6SM51zKsWmNa6|}Ig^`ip~(0$p{<-9pt!LaC0WJ#s!}C#$9YC6 zLHpa&i}{eTLkLJF1XK=D32ttZYcE%E_?{%Mg4Uj(J@>Tk4)2nXg6AU=#uXYxp>e$a z&L+-pe;j_7xHGDjXqsKj&m>wd&!=lo2}U5E_LIR#xxy%KyoFx$Gksks?uQK}0BD@T zc&w=H4!qw0#IrF?mt#0yp_~!UE7kWv)jHe>H-%m_Dg<8n+R1C0IJ-*+tgn`Co}9Wa zf%@(G56{MaRQa@MD=%g$!^kBpRMR}JyuU@}vPfz4J%XJ-?1G!Lylrm&90E3zeU>)8 zBzW5T5&Oy*5@fgo_NH@7k>i}vy=-D`YNFympXJKacdyTr%sx5y^^(G#)hViyNYOlI ztNa~t@&urd0K9xNWlWYZ0$DsGzKfN_^4kNXlLq&LQCuEn7H4yJ3%njjs$nABBeRp0`4yx+B_OfJ8UUC-8$B9Y*hZS zJ)W6#6q-9ZH1y@mb=EzDv|hpc7pUXxgoErqD@jPd60cgOK?r@T{n$MqnkzSsoj!vp z1iG#hNw-Ed@b1ZnF$|(E-GV(+_2$LAaMGnK$msZ(N%kZ?T7YGuq8~0f1e+JF$R(yz zup{D`EpCB+d?IJi7Z0OBSA!Fn73LN0J{O?k;CQv&kU3F*T7Tq6Orvz^{4!9#VLnJ} z;zbQLn&pk9u(r&yVtJM`TLR^iYN&x-8`-e#8*W37>5Fp(17kP1AF z)FI-Eb`$S6!JGHn@qYuulc_P@ASP0LD{(=@eSz;M!USGg=v5kIvTAC(%)n*bJu0ge z&;>6sk$D%dXgCR4A^V1wh^Ujzuo|eM1zs^!4fnv;f#z69e#gVXpkD=5>X}wAFT-1i z2An~yXS2(N?9+FEqkv2fcpOGIOp*=AYEZfW|7$KWC~C8}j#mXDbxt51t^LWHT{>#d zvVn~fYWs&*J08n6AACh&l5_+T4hq~t=v1`7xH@!<^=SW!mwbI5n?Qp})#N*O+3-#_ z5te5PWNlW)g>!w;d4J9+JxKL4HCg5~M~WAnd!HgZ-0#7&{gqsVzPS^QSO^`ia4#eW z--^ctWrH0`o+MV4$=1~-bZXK$r1px}lYNu!<$HPWt)qz`%+~LWXx*5bN+%}mBDj6u zxgIMkp6_apTlK&5!PFKXZqCyg#_%NlOXD0dlgFAi-@U@+<*fCF7jt_X&;y5(v9?amP@Z(VbjWk~ zJU$DXHDmtrYqpQETnQhaj945Gr^7Y9dzZpKeJYLzH2b;I?uuA>te$MMZ7yZ?LcXOF zceBZtq?m85M_Q_`>vGxD|5rmQ)}K$$mZ$3!haFrv4VFl+=XUtKX{E=46t+Q zMO?~qr%QNC7M?m3n2EWczE*k6$~y4F3{`ymR`Nx&uVhR`RPp$m8n^gcKg4zOlshuZ zHX;XpUhIE;(fD3)&u*xt#b=UIQS;V4S9!dIn|B-MNyzRp^dq| zU0*2553WB;U6~P;K^JmrUZWO%I>&mHLXDwT>KQ2a%)0foMSdT4coMRFanClNJ@rk| zIqJucrFB_e@L9WFBRd@GyQ?ASB|=PWoJ=Dl4M*P9^^P8y6QqC0wUs zwNCUN@zzz-s+&%bugH}$OT!DUJK&>s$!*ndmvPDcBu(KkK~~JG@CfC@V#E-5^K{H6 z5>DK56tG@@>z6ghDqD4ft3H1iQ}tPgvsM#3ZM!vjYMRv5sZ;PW6#gNgawx5RR z?v*#BpV?pBb>vJBpwQrD;n`IFnn$x_oYmxq|GtAp?v4Gpju_j+SFYW_%T`&;rhg9* z&_JC}ge8=q*&WVRLCORd81Ea1)@GR#`3KQo-?-wuytxi(oj!eH-LR*Y8$XzJgINzH><5Q_TD9XMt4uHhWijEmm1WE8ygfNjOX$Sb`3f1SCBM*}T{JUy&R=B!W`yZsJelOS(Yx@-0 zuh>WF`g_3wwb+Ex;J!}TtW`{U)(@ zzB!g1nm-OZtAiJa+hpZ0d^CDq(_8d2XX^H6ffvEIE$YvmN4%kN6m9F;rZfOaS)oR3 z@rB4vGd)qwtXU?0Gm&=w_GFxc!}8E;(p_)U@OGBWqeHBCP{`Wl{FjS3%gl1Drt8yd z8hQ30}-H2349m`?iMr;`~BFu>+zm{ z&*3li=u?#TOe&wf0H||Ni9FUo-*XZN5f7on%^s|uh6V<%37ov|^xJxz{#?bBss9T@ z%xBn@pTX_VRlJZsk)|W9M6|%x#$ps>S-c(sXHMBGj=bTRJdiqKnk}a-rYIsTNZ;fj z?4FqWNt^LW9rypm+#qEkA3q%__AZYp_Bu z&ScTOJA9`?bin2=-%|)HE8u zlSi6+lufU`$@R8kj7f2?T%7Xa;sw$d*agkm9wT}2CD--M{9YpCId=8&cIkg~DGi7N zg16*M(tvlcsh@7M7nqRFBs1H$F`Oo zXH;c5I&KeDgr~s`9W|@FA+;PFdL$ zjvQkifOwj-CVd_;$X+k38YvKF{h*kn9whPkZOMC_q$L4E5c&S>J~kA`u(zNHj>~~j3hycsP%G-+Stv~kxX=`Dw)YIaqq}gd7OHqd@ zHXqRNK-dq7%ETkfU1&^p&J>n~ZMQY&U<%kX?DR%Pbx*po>%7U9Vsqh0Ip`-dM5(f; zw6lWNL!;#;`*CKs(PkGn0&eG+1@WQBe)w?3cS$~CbXk4VAH4{%$9HeD=+D2=ZZ-Ob zp%*U}T_J#OxD(Xzq!ftZKcCm`&V8?HeXaL;7@5^zhj~*>piRVvbj-4y>AQ) z_DJ||<)*EoS0gUJgu%Yk%JSmj(CkhSvu$y!k|LCGffu4+rfAMBWCUo{(zOJu40<$N3BQpJ}aD+dScH zei!5uFK~HgTbF$!z|lH!FB`%BSY#hxtZ)8IC;hY5-qlau_UMoh1&=Z(KasB$QwMXY z6$mNB02WPon$3{f?Ikw&P{C<{J!FG;&ynWAzMFZkZd1tX)y^9Om{}o5S1#9fE{xO` zZfUZmu?}}S3y|c6oj1;(EwL$Wzd12uyaB{o&>*f=Ou@9o9&CzCV!lth<2F#{!vjz)>b$-|wPJ09Cpw5(v zD=)3%+r^~+%=Q<%KC3$%;0L_xyp32vqK0_(a|uwMO`U?~*~?v=N*(GLE9|TDH%vcY zV)U2|h_C_q#y_#6=cACxf2%h<(iRRyzayqn0fkSV*A{4N1C$G~BO|VaP==7RhE7m! zD$(E4iLBj)+})h~^(2ZuE9^P7-GK@3M)ZTwD#={AaL7AJqfLP2$2rRlao0u72C%1c zX+MZry~gXgm7mm_F1@XOauM_ddUAoYbF3|u4Le+o;L+K8qknh3P~I;OjwlmMTTGi{ zc6GaJn9ll^y`Rc><*B%+dyjiNAO~N^gg5$J0b9W;XX!sc>XEC01DBr{(LXriuIcCT&2_&!SY)jg3K>)koe zRFW7x4?pI@w6v4iLubkFQMUtlSB~_FQkB}zAi6%hY-X%4K$-rw%gO3kmL5d29Ma+R z!J0Bec>oh0!pnuhMB&R|;@1KnF~cUC;($*~?&~~Lp7{{AkQmX|?J;l_>BW*v{LP*R ziWO*gKZHeh7Fm15xa&22gT?Op{_7>~F>XcpvvF_WB^&tbUw6ta^4}5J`bq9Ti`9gq zeK_OXK#Zp#FKRfdVi1Dsu3GV<^k8I3^ds}YENAs3XCIf1U+iO$M+K${$c~$A`iZfx z!;I+o^BD1@S=}GrHG3~p6I}InbeAiQU;3GB6r-CKX_5?2b}dkM55yhJS{I!PAxRZR zh>i#u&K!HYWtK;C1}}i+XF_szeD%ARzkJNSYGvZ2**?k&p)Fq^ySAN&BVR@@*g`5D zC+l(r#nkB@r_4l)0#<0jJwIG8H!i+jAX3oWEK^&Ckt&rTH(V;!S5ZF*l;@MkOtLlm zLzDcG0mMetnqHbB_hk1j7k=@iJ*dfgpb2?c)<-}KL6(qfzt^MPD7g!MNZa&b9N21y z^v>R|47&A$N=m@8yM8Y8d8Q3LN!xM}_1Ek$$Vk(zPa?kqgeEv) zh9J~};fNTs8#^>S$#0NXZEvHIq1H#7W^O4;EhLFU_cAxV6Q8{=b7)ZI4* z6=DJ(fh2a^K+x2;hBFF!U;Y636lv=)181e1c~QeOL~Xk+!+&?#wWx?ir+{VZ2Yze2 zYh}-B;TKH~hi;w6juKN@hPLBp6{c&h?A`%D@#+w5LYd`k>GjVHV8{2dM8o`X)2XJF(2+ajF{xv5L|gF~s^JA(Lq z$blOXJw7W1cniF%j*xHDVxaT-9^O)oaWB_k%r;5V1eg*{&Sdosq1Oha%eP_YxNqof zoZ^+#_fe>IGcUmLyS{5h4l1CdYI(DpaT4#q- zn>fVOPn$7+zvt*hAOjXPYlbM(ISXgYVgh-fI^!u!Ds1dN+8?Cp^c>}q6*=VM|9KFx z)kiE=hL5SyTNdcTA`o9h${0eH2CHZp@ zi0LC}h8NWK&y)S*l>ax65R7t9Q2oUVoXt@#0dR)@)zL-`g8$`si$8;;1#}#>zYi!= z9+m57tIa?<7M-0-4s2g8S^J;zjQEy79F~4yH~q^bXPkQm|yN1%QXB&e8E_7 zhK-SAIavi9XgB5+kartFym;Ap&t1!&)ftP{{?epN3_7IMe?OJjzs`}^yTxzYkR0#z zRqth)R>1Au4L=mJ8DA=Vk6>bH5*jzY^Ds5|i-oh7S93~2Gt(5?uw?Y7ZaM`i9 zQIqyOhl^cNiPMK^A&t*vlT%ZrEvRG1lYnDcd3CLZcfVYPZb?tu5NoZZ&Rm9&zj^zu zTD4KqRC_YEvcU5jeD&yC&@DJdti`YezIupjeWvvFBw^$F@G9p`%RR}Id-~osq$Gsw z9EX|797#&#=n(+-3Ed3(q~DY>`MP=&jj1s6=7y6$o(=YpA`@r6_oMzH?~I~*4Nx{Q z%#i}MN=cIIDE3@DffuFo-GO^Q&8o$oEWp@1pFAt6=^nEXxKE8tkm5^};Dc|07+PN# z>dt~<#OBZLTX^qd9C5A(dyk)BOar$)nj9{gNIVACvHb`7#R|Yi<`K$y~j{A zBwn-A)2%h~M>mx(9Qas3za2j@4FnR%&KHS)fULHDPKW;_wlIAhknoDbjxQ-?Fqm#{su%Yj;iD?m~%I82(=$2&08f?4My)UnN+e?K^E5@ zx-PrUdxKl+#$8jAubu>X*YL@5{uz`#@_V|GtoK#8{H$=Jfa<;riHx0sv*5a43`h6I z?4e%7cx=991hnv7U8|$WmxY57eVQp)4N$|NMfBj991Ii~TEyv}I21T?Yxdf*vA^hl z85KcBYNkub->YZAX+&ROS8!o*x_}rPd9m)Deib;YIK2JLBwn>OWKuT3FKIq6D~B%$ zVy8je^PK)W6Er!bEY4ftK0@;MJYi8=Z@Td=Q;dJee@LYFlZVE1 z+7Vs|bXZlmhqXEdlmz8C#MK&MjfbSB^r;+Myf)98aOB!U-c&*i2AWnjK8N@DYlF4O z@8EqTsVu%n5}{w(8Qk10z#gN3+APm@wFl~bMUTD=3A`A$XfehzH%V0H>;4Cosqzc* z88+YG?h}48jdl*u3WcviMDihCVU9gl-UC~N#9&~@1o>ugIDP`&x?F<5z|^ms3m(7Y zWBg&4W&t0C@+mYo>A?ui$XlGPUbi**bB^U}yryJ^b&^MGY^=99_V(vdYgxw_$JN4j z(NA_~e#E0k_AyK^cEdZXF_VWF+miC}%$FZjGrg`iL=J^^dyvtRxNi5iUj<3w(2EIu zMNehaZ=~2Nk&*YCyS59UNXZuI7H^V_-snQW)*w`ljTv@E+e8{T3OeC0pTI<-T1?Z! zYSb~7A-~__Hu7_p1I--mW-s%h%ij5EZ8ze|HY3@)A2|u9yFEkvfIw>#clMxWoS*JO?CNzQ6 z26wyN^Gr6LGv}{Mai;fv)KIvmAQR z6)UBa)SfTGmNvw?vd$V4KVg%cIs!=`!S}<>}$Aam2QPRZ*nN)Y_$U$&NC-AbQo9h;Us{B|+*YSAi}~AC2Cb znXADGDyI?6`K@`skpTYgaCZ`jx_`d6sx3XO_q#vt7mzm-+q7m#Z03_{bL|K}Uhq1m zvmgyAB(;BGb~II`IJJD`gkJW}x`~-xZ+`I@?L8u965+h~Or`iRp+WD>3~7Lmf-y#9 z`{H<}Hz?~55D5a7z3Tb%@_3HD#f>f%f(cuxv?e-ouU$N7(r7c}|Fk&eDiGv@L-%oV zmH~`#**W6LmbmM6^EpJtJHA)fLpfb~*6g@U(#5}un%9~VeeysODAkNDOu>#C18^L` zEQvvAmc0{XxqjQT$DOq47W+Dv57h{jdbSQd|CkKKmCG;~uXOwo%hD`Xru93^Yjqc-YRs)uS|Y0&&e zXYT+fQTS_iKie?rj+P|!z2wWh0RPWCh}%-7-eYG@le-lSre?iG1nAc;M6ZWLZ%|qv z5=DQskI9D#no5BoO@-z~{G^sh%?mDsl%02TDr)~|bo|49kzHBExqncA&IhM8W%dQ( z-D($Uy`)<_&(K>&YSC(&}Eip>4 z0DjUs=9K|a(qC1O?k?RJ0;nZ1&C_?)<0uRu$6i?Bx$@scoHMoBo4$Wy{@qmFHGnPK z>&GoMkJWZ>el42EXBu=p17{xJ=d^!BDHX6B= z`lDJORv%U`D89UJE(B#t={=|_Dosi#Mb;Goy1pGJ(c2~sV!rmbIB@h>1Ot5njPGW} z3n2$Qr$Ft=P3%WoW9w@mLU72kyBez?u$)p05~=}y1$X`e-Mdx+4pRh?72iLTA{OQq zCt zMi0msQ92c_0wT>buZ>VCs`yAvM!Yu56D|)zUk)C0nO{+%gW5KG#Nz~imZJ;*6Kc@b ze>Qo*TrQ!o;nqNP?H-_=tr>-Wa4>f~MW5{drX=N%L$#w%W=uEDjVmjChmp@Ykm%Ut~lzHhRRuW$}{wP1{^d z@bcD_=ralQpWkSF6!f|xM@K%*NIt^?g+(wirS9jpFKY!3W*g+$d~)_=o*#@kH(H3e zY%++6=(Y4_nmEMJ_!a|~Dx6j`<}YPd7H62Gt~+7qij; zZ}@UJm|NH2y6V~`g%OgiOEen8!Og}N)(_`i0HOojFiSsWgh_7ty>iOt2CWEJ!IWoW z;VkS~gFOzI%KX`t83ZR#m_se8_y8e+ON*I*5P|B_{BZxPV!Cu1+rTZ(sOkufiIQ|h z|4%thN0NM+bQC58(;|u@2Ui!{)hK&6fYm%lG(D2?*?<2`gqqX4*wd{+L_+0@pr{(L z8U5VL@nEF&e9No0rz&Y$6+q$tX|^~2>~RfX9#o18hA(Xh+uRV8;IHe_SMlTw|H2AB z^l|=Kh2kVVX*=4W7;a8JXy%coqw)wZ6NZFNR=jcRd<5v>Thv&KHym6o>Xnh>)E zRkpd&kBhU~>O0Pw`QuooFd_c1@d3nkPzzaIqVm5|3jg-hrv?*D6#n2zQ9Fz_b8*ik zU6z){#_|;AD%<0;Z4eY8^HNM-axro82fSeA+t~?fi!Y$b%NV1uFqJs| z^!c`pNE$m+lR+djCTpc!mZCU86BM%&+nlowcot7(y(*Zpc~wX`&7``=;QJUY=h8P@ z!x>Xf#BYX#ot%aDa{iL9^<%J`BLaIPHF?cJS~i8^o=6k>m;`_a0AB^J?3Z_zRP&3e z?8SJ5S}89Gq1HG-THw$mrS3;)mf?jd3_x+}bisfG0xO`$44FFjNsOtZ-SfsY^l~nO zV-BxC({QQRDaFST*pIGOFQD z_D&*c7#w)=hcSAg=;wI`?Npx~bcW2-1MTI)DTW`X=9w*1z%$@2C{~yG zp2LQ_8$vM8*87qol*`nknv`gOF<9>`BW@_@=^pxJnaj)>qylxk@8m6rj{2!N)DUNA zCsr&}rIOaOFtAEUX6(jn)!)+)!B-Y^8AOXqlm!ZIxat4Ro^_ zL}9*2px{ao)=^^-Fc;vsjS0#!I-RI|sVZko*(E4zC#GJC|Dy@ zUS@N1=-RB|s1U-ZHB!+IUNGBVM(WB?onn+IO!HuuGo~NU#(@WN45b;rd%~T`BP8{_ zFG!Pd^u2b*dYJQMT2laa=xyrEsRSn%6Qj*bTb8DjpAqT;wx<+V7LKHO7AQ z7h4aPq2mcn+*SkFiNF?B*O8Swp9Ks&86MHSuv00Rpx8Y#rXODZ{vvNwQDqmzW=RAM z@h2|;3H=_U_*4cSh9*>zq+m#Kx10OuVrVFkphNyIbPSPLgPYLG>IuZLOO6uL(|>?i zM67iYQ$9&iv~Snczn3)4S2fInTs(tQWq9y;q9wmV)7kFXB!M|?67Kp3$~Wplp8dG_ zBB5me;VwYKAg?ipAqfKsdA}QBuaP=wQM@$(Oe1(~=VDL$Od5Mo0BJHFB+}sWS@xbox@YRu zwO`!yJ@sOR_z1j-C}hOPwtT638Y&NHu?oYwe6NU)LZFxrE_{oJg=uGGI|- zdyxrJKoU!Wr~k#xLBy4*yPn)P63gnzej~ z1dz)tdhCn(PwtL%VX}1}XM(F)d^SsN^LQzKl}Zd@8>NyVWbCV%c1{t-^~cD2;=2n| zzgp1pEqZJRc>?Ly4PNemM`MBy;Y^TKBV~M&FkY2V{W>+^UikTF=i+9|LeHvCpseuK z7oBTq)$cmZdp|7Q^W+{iha1vCGWWPtU3zDNw!#@4T8mG8P{XGLh1r_^vyTE1Wg2S- zh|E~}daD)-pB)CAJ$ZfI&$O4$S(S1dU&?RL3*eyZ7Yi_XWk*y_dC5Yg_JGPzWH_$f zBaPh$A(T~DIqcJ&m|&Xz_G-Q>&g|TvWRG0SIgdV zkkFDQs?L)38z|8RX&EIWru}$xtyJh+Jf++d&tO~r--mzGH{CuI# z>8{Xo-`@NBt=L{VKdT5kNOm4b_!{T0N2QXDP5_mE(6_PERO2#x^&HX6_YX4FeTfA8 zefqiLg_KS%St&Kh8c7Lwq_^QG>43m_m&gGDK*GPDN|p1Mirdad_e?STm}R-_^ks!+UHorf`-qkK-IQ1tPuhgBSP}j~;JiPn_u@q^A9?;^2oAL#P z1Ni&z*AfaXXVYV>n7A>HqJQ*mAHsjEsr4L)RV`t7(k05A0;rTFbl(ql|B$>k(cy*|8 zRBEYCQqyJhQEThis}$P)dtCVhHv%Hz^~`|HzE}$)EI48^nOPOmrZ3~J^L=18hza|wIf`rF1s;E7DIjP4-ZtVsP79= zq?i#@f~TXsxEzVI(YIr0VDWEvFxoVPdYbvDnwjmrI$(AhZWoEF-?evnx1iH;vgP<( z>eif&Xl*o44Bw#%&79e4w_!d$iwv~rqEPYhD}l)NF93@_IRvT)IK^j zxfffL^5|2!-4U6BXKmQk8bwHsyb!wLPQ^T8tJA4yc|Gq+oqV@1XmnVv?vPrgcs1-u zmFmGWm7zD?FGmCk`|*_K@3qpxF=_LG2=a_WAuqIJ(1V58%Yyk>+91{=B?_K5ke8@b z`ncsL>GTjgB9YijI!flnwy&s)pEXx-j9)~~R0W1=^Ux{zk?U!v$tbO3b4!MMoi0sO zLS=`anF#cCw`xJt=$P=Mp(A(Hv0W};Crom=t!*C*nNqn6o+h4i3sbr($b3pHJ%f;WKd~2 z{p)C!?RE5;QME*Rk$9xZSukB-m?fDhG2^a_f-yrHecznY-M~d(#NU{iTymAKpu6yo za-nb{j_;ifxsqI{F(JX}r*!?|q$2xVtfV&JCo1(lAe*>}wkcp_{O-u1+FzCz*Hz@cfsuG{_5(wXWqnZpXPd6u}3SS_hBiT!g^;#=|{+oB2Mnn zxjIg8y0-Vx4sIKfhM5Z}4N_da3hbskc=?*0rM8BbEi*;-@Z&3bG92SBr&xcXTh&U{ z9n|s#BDJ;7NF`-e*tG*7@y5T(o64SRG*U~E`VE^(xzZ^|wYsl`&t9S%YF002{SZLo zidX<{M{qufEh`_W7&sVrl`58dO7FWK_pC8-@|x<0%D!$pF4Namujw^}joDPfi924% z&ca~*1LG%rrA-(vSM37tgVz%MYny%9rkw4{VZtSOmZW%W?LZnrl5 z0WvzSzK$mExVYRi$@!vn+Z|unHe?cz(!E4jeMzWOY)v@?cm}oI&no@s^@DDqinK}< zJ8;+g9?T*{L`tTBu(N;glN_&2LVudLUy??3?;seySohGEpF=Rl+EO)7J=~U+_=#`^ z?AOA|apR%UlpavLUp;ykxrgizj!;9n)yn5;O)hp+; z#cxydRo6^WS3+h8e{V$4QqNEMWL2^H#OA1bSwxPaC7_hh*e>s%WFV92JpT5mq5#~Mj$d4F9H&p^20E4=z9a8>H}G;d7P5a ztQ>4>CZ49(i9w2=$w7FH_q}8|V?47xRDfI$a5q?I4|w1=UOq205@KlLcsb`vCvbK~ z)2+TROa}hF9Q%-%T^v@TzmKuBc#8E9c_`CwXEKVd#3V?|fs}3oYt{D26<&8rc+qz& z6YxCBeMG0ZD_&m*XqKjZH_7k)AE2~F@p)EaP*2NP?8FaWx1#65^iuJO>A|d(P}x^2 z_V1w|1^!u#SpM8p@;fo1I|y5WB)WT0S5-$(y+ z-Ao2JKSWcn>Q4uY8cx8P;xe+o09Cg{pQ1|P8M)aEnLoRkg63@9-`<}Ba?rzoW)WQ> zM7-WUdcB=1RkRZ|P$T z(cS0^7aT~5+4X3{AgQ~T2pJQ6R^R^2iZTMqb6BYaEOs9Uv>C+f@O2><<5W+QVBUeV zdf1o*%Xxk_Na^L2y*d0GHPu(q0!;eHg=w~ZdU}`Rmr1b8=g)kw>?${db5m-lKkg01 z*T*(3EScq;p&?d{_KBvLf&EF|$sbZ_8zM!%Vm zA9K7M|AY`#m1);pCsrHJSjxRxISF4Af)cDGZL-?^Q#6EyLS(?8~fz7XgJ!IEu zMjdiJsT5bS&NgUsea%_PoHG51g6M)*#O*XgV0VE?Ii?k#ojSmw^#+z^MQ2(3Uv`l& z1>+NfLXY-9c-K5WNc0*%gXrOmu_9MIr91jlE@@b%R)j$L%Il?4$>8$JCF#{T?p`J3 z1U_R9#I*=050nYK%waS>RMB+tRY=(hW$+FIETf6DzKz3Mig#~k3@i)kf~3SWx=CEP z)fkLH*iHesGqO1i=#MMX9*JcEtYcp-oIe!0Vfi9WT%+oG3By^86lJaCug`v*AFq#z zuTW6K?vzbkU>CMOe^>P0M=e|-I$U!vM`%sIKRWeGwVY1Cqo7d$jE-gN%`43-b;(RC zbM8={0ryq7EC@hU9$hbWy*Sl5fsJ`r@WkvUYMQKgV@?Zgp4wdYoA<4*?^AwGe^Bha z{7%w%vuIuzmYq41T;qhoNL`psn7*`gPU5`ASSFaEp>J)@p4`=+5Ri^`WeG?X(kej*kEA zKlo1{cgIu`qy|A8h?6wa9)DsvlWcC3;PszoKe=RaNEx#o#200&?NcFD=A3OW>`IWy zip>w?-Es%e8j|e)p$F-C1{RlZRXrD8en67le%kApu7~j|07TYg-J8LP_o<%sm^FqX z=tJ<%<4Da~l;yAPl7WPx;KqtM{LJB=PQQQs&uBaqen{0eX( zewzk`hK3H4KLK^#g^xX*z0>UypYYS1>bG(^9U!c+wmIhrisrf(MeV>rJdzH5(F-nPHUE zZDQY6j70ia7Ofht8i|`Hs0!1Y*arl$2pKP)H{YK>eMW~d5q;w< zt#ZqvQmkWT=P)cw?dmPOa3TKZ1$wG3zwmf$2B9+6Q;>rRQj+iq8>1`DilD!`oW zlPr8!{d48VxIqT%C_=O7QeglOg{>FmsAR|e(7d`Lu0DTv!X?^cyFb__Y0h^zOA=xO zbflI9;Gm5DI%>e*b@mtBf75CA8+lpt!YZQYVgeFfNUN&UrSpE$8*Jxo!C zpB?m5D>H&MCU)kB(;lu>sSzWN`~~mOsJwdfsgRBD(V!XrzyP9zqu*5mT+{ME)RytF zKlhZ*p}*qORP=^WQs4|MHsfiQt80^9Pv_LH4#8aq6ZZZ4dZO0EN`@L@Ea};rgzCgq znK5e_M!4pM&GXvO>L(T!7=@AJ!zOMW3fOxEyW%yKTre-#N1=XyFMvIpx2rg6u)3Y?mHhW)j@6h3 z7WQghH7W`X*0`oKU_tVps=-{%YtJ+vEdrquiME7vl zTA7ot4Fb}3L%;y7)8T|-1wgblzTXC{g10NF%b zQ*eQm+nMgCYLV1Iv(K1dY4L^8fD9OD`WcvUh81P-U$8n4~j~W~59SH`5jEKIAswwx%t%QasPAl##hB#T> z`iqxGcBv=)b}@ReHxwn? zHfO6OI%`lv7abfU0T)W>7+9!NsljPo;LrkMyJxdNl=kx&D1EwY>Ftr*4k}BNtX<8w zk-e-g2+3BmN>T$Ub8ze)q8D(m3M~tPlOt50Mc_W})&=EA>6ZQxqj-Bbyrb98cP>}l zPB)!)jexwjjW(v2_??Bq{uB;szfs-;ltK=1?>0_b1_&<=qnAW~xxPv#DdACKSHt&S zl1_}~11yQC-W%UB3k13-J#Y-%PFwZ9peVl-GM?|x!1}d%-?Qm7cCTf3f(hBDutREt zqn@?%#}Zl6Xz%}k{4|s9ze!W!bcUtD8E;OtHUc8Tla96)pkJq*jQTzv8^MGo9;kkys?3ZffHs`wEbe?AJ1JYfN--&-J2T;8GLvJxT7 zM36ex0rdatpUKSQ>am21#Xzr|znV+@w_Z7a7h9p)fRePbbpVNws$xuIkYXZ0;Iku1 zqe0@lpx#`3zz8K~y?*n26mLZroTx;2A4E?LvekuHOMe>-Hjo98fTSqy;`t}YK8r;r z|Ly<&a*F@+w~%GPxv>l+{LfSWNcNp1m_6m0?yrRY4%WCZy-H^MzgLd_h7IDguXjej z%a;@#us`*V%C=9^FK5(R{p2pbdh6jy)WP?@-fkkO-GAAb@Bu|3o@Jd2Vqjo@$+hG9eGpy3hgGikDxUkUhpckG>Z;kULb0xY~*vRYUS`q1|e16cwTf%!>eI!G!rBoopo>GgbOveF+kR%2>=!1A-9wmAF&14=Cj)3HMs*qKSjPp&-UZn zcA4gpb@(ywV}A38(UThe&*kRUbTOLeS2pK9u=#Q0b|k z9O>5;X6vhRiY9C)NqwP@uoUU4XQm6C43pY*aODVU_5f0q`O!TBy5bVwei?bW;PWH4 z6&9(BL+cDiy>Q~0uk+RJi0F(u%qlsT`*qle`Wn2)`}>!Y*dF!b8O^L@H8-3d+Z6M& zr9!!NW=lKPq947RO7JUx#5=(bIUi81a5XQNrV%NaNljTUZuw*GHHUwj-u%_C8JyIg zz?P&!Lt&fT271Abq`%(jnMzq{LqGF<2Ql(<;sqg+8wgxvim_JtX0TX(vo~fR2AJn$ z?kBd1eK`ylQ@@Q|lg^q{XDrE#nF-6UpeaPly1JZh!yA)U^76cAR|6|%u0$G|T|St; z3~AF)TPzxvzVMcNar#lf>c>kzetM4Imp0S1v^M)hbMkPCR=#af+#B15c^r zBL_A3)(8VtNx#N+h%^r!bQI`XT67!qll?}mD5vEz&|r0Oc>&5?ukZ$>&fY723N2=m7)zZw#-Ru0S`kxo15&hNPk7R0 zKRKpY464Lb5$EwVi4jBfHSphARgU}N6??MtmlAMRg2cM1R}SXl-yHQWzmo?!!OU_8 zv~D3yY#W2$^tn%!fV9Ye0!Cloi53iMU+wxW>3g;(f`9sCUnQ>r5qtKVpq#a|wJ}We z>6M~lA6cNv4^f2gCncNDWM{HUf;2Zgt3V+t#d2{nK!@L#k$}}2qBmbo*;4JNNWa8z zPx}{IjP}A?xKX=#NPn;RV%eXF7u-L36Y=yBPV?f0uzInXM#+)^c*>Ww-ON$e!?3br z4Wq5Z*7`WKOYxi~ZULe66b9H`ycQi|++yZ7R{i=W0?NopnK+ry#|t=R`Thnf{-u7) z;|Fi39~ZR7NQ&kj)TKFdP|m8!B|V_JCXhlB+nHqSKunR8%a2shi^LgWEK_9t3?G8RM~ePXRhzPEW0}Sc}A?b2=rM2bWlwZ3sZ1(`HZuuuZ|`$#gndD zJh9Linrk5vM+Amo@bDmBhR*F%9J+iTCN&4NcD~rLNV`{^WhBF9bT6@h$g{Gk?)2Hi zT@TnArXAdB2?hZXQt0_UrgGLg9?SkjXCT9*PgjYDb1|ej$>Y0`oyGL`{F0x(e`<&U z<7^-`z&_(}lX4iPMSLys$NeCWGH%i^Pb6dPU@lzbXxZnskmNB2VdlNT00hia*c(rQ zN$|f+RtYt!`ay1Vctp@bbygfSaes&b#Hn@D8`KnK6DO|o_(c9nN8SOyE$A;!Qy_ot zF!!RF#F>Bew{1s-y4<=%BvaH%WqT8JHi*IbVw>t;iY0@66&s-ax4~Pd>*B?KfE;w8 z_y02}Oj7EwZw4BM!BPW9HpC$P zmadiCukxQ^?FqY&QQlw18myXx0Lc>GH;anx)pIYV^8J;xIc1)ZV~pKVrp8b@8Oe2Y zGrW_4Bpj5aHg}@|mC9YHuv#{@5DE`+{$0=DAGz2wM_hk$JKJMlQ?7&6jw7U#Dp$OE zXAzmt)bzcaE`oRx$o3}V$~F?P=rYC9i^Tgsg%kvIDhXUUykbM<)-+}~jzHu@-}OD_ z@HB7V34rAaiLB}BKxR1`ek|CVoPJUg_Q?_Pis_{AV235}K3qxZlL;uyv5=>Q!A32p zHoX=yw6`y|o+P(VimRON*v+#0*`Z=D-KkJRsPj&-h+#D_2;_)DY!9J_Pz!@MQ=L9k z1GCrlYvf@&O@5(}U-g0G_0=9l5rUeoC!vZ0Wjv*8z#gN$5vzU`bQ2pJsQ4&UOO>g9 zrmQw`?_*VH8{@8W^4!YT-|6V2t7}?mt}0jfe;w%mURUS^tqmMz^FoT4+|;fM9pkl> zC7Gs*?O}%fWZL>6C(T29&7GZTfo7)L$(*PDik*CGTBN8TEA3Jm*w^sfhXqw3pY^jC^aZ z$smIujV2UI+=XOP>XXZ~FOoBo4LrNeKk#!vQ*BN>KABC!{7v_@WzH2m&2ilLlF?J4cryHCXZMGuKNQ@!S*)^=5CE6@*N(yONpKDd^)>SAwv)<%mcIzupo0 zpBk(&Ff6+Yf@GW z?Fk#mYR9>e)F!`r9r+6RaFRx)B&965$>SFlnl*4HY`L*p1%PMI@LVw~Pp9^$UNpC) zi^l-FkgjRua$^S4`gVc_7c!U5Z3Nu#KeU&dEU;9%S1|Men{yR~V`%A}qW4uHMWhl? zOFBuy(_kx>4%1P$>xA8qnODAaG5A4JZzK+h;X%XgRxGPLIE;>LxbH4hFT~TYI?=Bx z9-pTss4FC4bsXVN0%pL>y; zw*KuE-upouVh+;fEV4UN@3|L8_c+9lw62Qb{ZYyd83h9ammnNm22v!Z8 z8#7C+8>L*kiIWe*oQgWFxj=`z#QdnYSxB}AKQ@!)*=6q?)7gqf9$i7W7SYM{KIn&@ zh+TJOXDF7D8MAa7Tg{7KQdiw6I3x76qW2xii0L2q<Kc`v`!a-L}t#y(jD?MTU z3lP@mcLew!`26oD|25yie%RX7(X-^GwNLxPpU^JWKH@<}X`h#f@X|lwAs8?GZZ<%_ z=t(-t+FR&^3T^(iKm%_^xsSci-{_o^g%mESjz_J~;CpMEG_OS&=I2HZ&4*IB%$gowM}S^XdIkbJ zA5uunmxqnX=B?@4BDqHF?0Hw`7eLfDlXQ+9S8{aZjdf#?Bg73l?U9 zsppxV)qNJ>&rY~SIL5Y59{{?}vrw;M?=Xmgh@+T21TTtvshOog#Dz(mI_ zirixlCBmEmWW)i9bDr)N%_?BxaO>hHn~{sQi?F^fnK#K*pN5ZhJ<_63GKB=>#}I5L zCd11Q<^+(8>NYv`Bgvf~3h?<$_{w1P*&OiETNbySt|E$Goo}G81k*n|KwcK)Pn3Ezs zB~RY_kiwINi_+_YM#o=jN6Q_T;d7|4+^L`1oOj>HDlV5?do0-P2!O9!#tF2=Jt)<> z9ot${6l!HUp|H@BMpgIxBGXct zGg8_1!mnn|Ewx*@*xnn*8xYs!N?8T5wo00ZOanCwO0L(1)KZVh+}S2yr9{bokW@DP z+F9=TY4fKQ;eLW5g0zo!bd#Oh#t<@Kszb99I>N=EkdlvAMb2-b+!i=va)$6rqmONR z-^OS@Zf0+;PP#oWMpZ2(#q)_JqgS5yA?){>%ePMquN~PQPq1!l7C8@J)y0)_miw(X zk8+@Vf2hEG5$gX;L4%sD!u!tDW^uif)-a?8dUEi{a=FGVNFS6gw{S=h=ooezEGPW> zE7J2qP9kes6Xp3IuKTyv`fV})@}Og^@CNqs;1cMWLb^AV4u2fYEi1HBYKOnmv5>l8 z5=){D%302(+c5Fj9o2nyYqBXuz2Og}x#C6M_yo7kdM6fi`FKiS7BQ?5JV?zlh~N^? zft9amr@!&m&EpMBA)Kw|q6yJG#k#+TiHbs>JQdH++ zgpvh0_55~{s%QMTvQwszB=$(>OjCaR-q!agsZjyGHefbu@8MIphNE@b#Ha-t%2Nu;nIQmts7C*(;O6 zRgCP{c)$@yEsM`i7#6g_P7>PY)W7RO-FTvz%1E*;9xA#PaRs7^K>&e~SRt(r%bjny z4)wvVv&GAg$g|$ykF#e>9cqB(W&JP7835(oO3wTdmwa>Ae(~TBd|@;ER)^}N7}BJ7 z!UuVp=bMl#UL7P_zYI_;5Icy-DjeO|dKLj20aUzf0m!Q zJ}^V`bYl|3s2l1qUR(FZ_^vXW`zQ{vOR*BFRYpKm!@(&=iNcFFlIe#l61In$cA-d_u5C&J7x zADL4hBIv7IAG(42P1K)?f?Nnm|FUD_{Kign^1_DuhQuEG8$sOeD$mR?dv`RapR<*? z#xIj^*2~u@EZrmJ7*8)eX(fc6qkjQ-)5e6eK$#W~&uErVpE8!hw5aj9nvOEQc1unL z9oQwOOGDLQL)z5t69BBHx&>Ba{Z?E00{};Mw$jqb=jNqH7oN_*rsMCjg?34CalABm ziSD#~UrS$C8nHJ&vOTXW-Z3}=!*z@7``7=tKF=W!^b_fxOq*Szi`#e+BxsjBTYo~} zti8m-qc`k{+FBPVB3$pE3BOZYaFX7aN~*_6L`gc4UZI%zE^7S*?wA1d)5dGR^hW)3 zvOnFuNrW@op${2JJRd18Cug^K>GP@86gG?BY}!z8#W>{|KDW?gsXomD(fTSO=+lf1 z&*ucZYE7Y(;un<29-OeRoEKTW8O4`$lvScXVty7|KC!=D57)oT@9j_sXi7PhtA;Z6 z>g}78I?HFBGz#xRgKCGDD?=Y)ijsz+HO9|of(4sJnZl86uTeN!wW})1N{v6YnaY%G8?KLX(C;2KS67UV7yL`i9N8g@OaO zi|}QkS2M5twpZ;;pfqjdR_6iy1)XPS8qTQI85xY9GTr^yEGAjSN!c|EDM%Z6`Yto7 zAfGsDRKXg@Z`#C><`bz2Lf$L0Xk>QIqR`mmSG1u%es} z=L0Y|-{R-%nX1J&hc2Ye*9?~$VJ6YAiOinm#TLRcH+GkUNwT(+4lDNdI=+5#Y1&NhqK_K>~pLi^o9MgxtgGx@_6w92E%c2#gO z!p7hdK*G=)?KPff@4UNbJG$Q@c#Jlf<%*Q7ucE>`0tX!{H8C*#EBI2MraD{yR3K37 z%vu(UZ9}aM(1?HQ$I?dIaF4-wAqulcYcSS(5$;P=5FWh@~>S#%zn6tOJPP z<`OT+)#cYjXMcYdN|xkJ=*=>SQH(!rLK9`RxMR=4Equb?wwrU`^TC}b8=e!99@|1E ziaZDv%+I44x#RC}vrIu+G~ezeq}FccAR>1qDYIWLwsUm*{FEyFbz4(T*L&33c5Z7r zK7CA=sF@?CC|Lt}*tGJW+&rhA_CVFEVOMuqLdKKzR`#Pe(1=@g@@8CBrvlXPB#U!w zlddrg2xIfOl*N~m12kH4p4#*`yA>w}4b>@i)&Mf39)^k2xno+M%jSwt<+Uh^V{VwG(OUi?|ly{Jl?Mykh&8KH56*!bv0tlOY# zOyBY6{n&!Nu!~m(-EPtA4s~f5CBwCb)U(|=0 zD^KRy>ANQ{N!Q8jk<*P=6|`ySRIkwUs`l#i;=JEKIB@#F^=VE=lPO)vqoui8l<3X`%_lZ$O;Trq6n+I6^tb5fjj-7dYfxsOWL9hKv5}G%AdP{)gwK zSzW3D(}@3L0~G%DQ+5>AafvCuhmLJI=BhJq%i$GwOX9pJ;$Vds0gQP;{%U^!Li6gwM*O|1NL#4}Tf3pguRnBjG=6 zLal%X<$6@Kprdi0QzPp^%Fr`mNMO)nwT4E_;Yn88?E2O}NY$(P*;NU}G3T zQBZ;nI8e9hO-_eYY_qKu?6c6>Hs+jnj{2qw1t(s(V5241ije(Y4T!XMHUNi3;%yn@NRvrs%2f%oT9(e<&7aByW8_U;U~L`iPe| zvDBq6Z6pQXfUn71`FM)3=Mh4YKlSE239I0I@hGY82pFn&|ForEZhiem^0nWP3ybTe zZi^i&d)JWnK`)q3=eqLHLotCtGC7RVto!8asnvpK`n=b!)%us&9#SeFgPrZ@6%Ill z4Z-i7MM|!GM5o1iOcvzWOGF3ZjSo&2uq$>jC*B;osN3B&jUYc-iW#i!gzZcMAzYl=mQF;!vLI1)B3@FsRHr#|RzfM?NR41~^fjS*P zV{-w8Ol8E2t(7cse{bIm;Y2F|)Y686_C>!SCLqEeUoa`UrpkXf{Y0LF50kH9M99;P zjOR|u<@bo4Dx=e@m-lSk+fqSmN*$1D2`7ucxZBcIi^utC^30l|*vZ3Z7(|o=!(K6U zo+_CpdLQ@g9Y$(?I%8dYqB$vS#FRT9;RS_uP#LC08Wx(W|6 ze%$t(Q*gH84)IWw8C3;k*cB-W+x`7N`1n6M_g{f91zY-A@N?fC&N#fr5h*^JyF3LY z-IEI{)=z0aEub|U6DQ=ET!qX&c5}NBdzBvM=hAAw^TcaL&}TvB0PcgjN*vjQ%E%$k zxp44^!C+^7Kzn>qq_woN!&h+C|J)v$V>$bPMiO7V<5@-odlW#6n1Oo8 z#gZ}sNKAcK9%tpCg^xR@SH^>Ja>(V;mvep$&DVk{YdvI|!s<{NPtEoSE^`vzjB6|- zmn$L_6b}QwtbgF+tQlry3C-${ROigkad9LvZiiOjegk0vp)r<9d{oLT6{2aZp$447 z&NWMNR=p+%B05+Mu2u!VVz$&dF!ENKN7np9>j8G~6CTy$9Xz+M^UAt}pnm(1IQ^7# zsjYd0h_0v^{*WS5NF?)tHoMwBybk2l0QC{emOD3OJ(0(lgy{YT@46=y&P1jqD!Iz$?5 z0|mA*5+K-sztn&c@sF^L{fz*F5(9`}iSTu-7SLEJO;`uqgsqEFE|XF~QN|s)LNX=^ z;OM7`DkSe2?Cb^}tcy zz(l{=q7xM#Y%!JaMZ-%{r*q5+D?8knw-65_v z5V+1vemfc9)kTrEW%|ZnOn+7B2y$&5ROY{$_e%u;NNViw{C0T${vu!$FCOtDjQV{0 zA`aX(2hGbG-a_#Ba%u>>f$#v-&6qm;1{FAkL5bvGxsf_xxxHUU;3P)X^CTLBjZyb X5&E`50Ribo21huyBH|Zeo8A8dtRvYf literal 0 HcmV?d00001 From 3871e806bb94da85443017025760e30f0d5603b2 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 20 Feb 2020 14:55:40 -0800 Subject: [PATCH 10/17] Update auto-investigation-action-center.md --- .../auto-investigation-action-center.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md index c2c022f1ad..dba3b17e10 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md +++ b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md @@ -34,7 +34,7 @@ The action center consists of two main tabs, as described in the following table |Pending actions |Displays a list of ongoing investigations that require attention. Recommended actions are presented that your security operations team can approve or reject. | |History |Acts as an audit log for all of the following:
- All actions taken by automated investigation and remediation in Microsoft Defender ATP
Actions that were approved by your security operations team (some actions, such as sending a file to quarantine, can be undone)
- All commands ran and remediation actions that were applied in Live Response (some actions can be undone)
- Remediation actions applied by Windows Defender Antivirus (some actions can be undone) | -Use the Customize columns drop-down menu to select columns that you'd like to show or hide. +Use the **Customize columns** menu to select columns that you'd like to show or hide. From this view, you can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. @@ -47,7 +47,7 @@ From this view, you can also download the entire list in CSV format using the ** On the **Investigations** page, you'll find a list of all automated investigations. Select an item in the list to view additional information about that automated investigation. -Use the Customize columns drop-down menu to select columns that you'd like to show or hide. +Use the **Customize columns** menu to select columns that you'd like to show or hide. From this view, you can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. @@ -60,6 +60,6 @@ From the panel, you can click on the Open investigation page link to see the inv You also have the option of selecting multiple investigations to approve or reject actions on multiple investigations. -## Related topics -- [Automated investigation and investigation](automated-investigations.md) -- [Learn about the automated investigations dashboard](manage-auto-investigation.md) +Next steps + +[View and approve remediation actions](manage-auto-investigation.md) From 56d49316389123275b6dab099d25df484af96a20 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 20 Feb 2020 15:27:24 -0800 Subject: [PATCH 11/17] Update auto-investigation-action-center.md --- .../auto-investigation-action-center.md | 19 ++++--------------- 1 file changed, 4 insertions(+), 15 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md index dba3b17e10..65b8232367 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md +++ b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md @@ -31,15 +31,13 @@ The action center consists of two main tabs, as described in the following table |Tab |Description | |---------|---------| -|Pending actions |Displays a list of ongoing investigations that require attention. Recommended actions are presented that your security operations team can approve or reject. | -|History |Acts as an audit log for all of the following:
- All actions taken by automated investigation and remediation in Microsoft Defender ATP
Actions that were approved by your security operations team (some actions, such as sending a file to quarantine, can be undone)
- All commands ran and remediation actions that were applied in Live Response (some actions can be undone)
- Remediation actions applied by Windows Defender Antivirus (some actions can be undone) | +|Pending actions |Displays a list of ongoing investigations that require attention. Recommended actions are presented that your security operations team can approve or reject.

**NOTE**: The Pending tab appears only if there are pending actions to be approved (or rejected). | +|History |Acts as an audit log for all of the following:
- All actions taken by automated investigation and remediation in Microsoft Defender ATP
Actions that were approved by your security operations team (some actions, such as sending a file to quarantine, can be undone)
- All commands ran and remediation actions that were applied in Live Response sessions (some actions can be undone)
- Remediation actions that were applied by Windows Defender Antivirus (some actions can be undone) | Use the **Customize columns** menu to select columns that you'd like to show or hide. -From this view, you can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. +You can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. ->[!NOTE] ->The tab will only appear if there are pending actions for that category. ## Investigations page @@ -51,15 +49,6 @@ Use the **Customize columns** menu to select columns that you'd like to show or From this view, you can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. -### Approve or reject an action -You'll need to manually approve or reject pending actions on each of these categories for the automated actions to proceed. - -Selecting an investigation from any of the categories opens a panel where you can approve or reject the remediation. Other details such as file or service details, investigation details, and alert details are displayed. - -From the panel, you can click on the Open investigation page link to see the investigation details. - -You also have the option of selecting multiple investigations to approve or reject actions on multiple investigations. - -Next steps +## Next steps [View and approve remediation actions](manage-auto-investigation.md) From 9746ba9a94cff09b6a835acc27d05e406d409b92 Mon Sep 17 00:00:00 2001 From: ManikaDhiman Date: Thu, 20 Feb 2020 15:45:23 -0800 Subject: [PATCH 12/17] Added final comments --- windows/client-management/mdm/policy-csp-bluetooth.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/windows/client-management/mdm/policy-csp-bluetooth.md b/windows/client-management/mdm/policy-csp-bluetooth.md index 2160f0b07a..40e770a691 100644 --- a/windows/client-management/mdm/policy-csp-bluetooth.md +++ b/windows/client-management/mdm/policy-csp-bluetooth.md @@ -448,7 +448,9 @@ There are multiple levels of encryption strength when pairing Bluetooth devices. The following list shows the supported values: - 0 (default) - All Bluetooth traffic is allowed. -- N - A number from 1 through 16 representing the bytes that must be used in the encryption process. At this time, 16 is the largest allowed value for N and 16 bytes is the largest key size that Bluetooth supports so far. If you wish to enforce Windows to use Bluetooth encryption at all times, but do not care about the precise encryption key strength, use a value of 1. +- N - A number from 1 through 16 representing the bytes that must be used in the encryption process. Currently, 16 is the largest allowed value for N and 16 bytes is the largest key size that Bluetooth supports. If you want to enforce Windows to always use Bluetooth encryption, ignoring the precise encryption key strength, use 1 as the value for N. + +For more information on allowed key sizes, refer to Bluetooth Core Specification v5.1. From b92b2c95869a2190a9417fff9d7f155ba1a4e37f Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 20 Feb 2020 15:46:11 -0800 Subject: [PATCH 13/17] Update auto-investigation-action-center.md --- .../auto-investigation-action-center.md | 39 +++++++++++++++++-- 1 file changed, 36 insertions(+), 3 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md index 65b8232367..3c337a125f 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md +++ b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md @@ -22,13 +22,15 @@ When an automated investigation runs, a verdict is generated for each piece of e Pending and completed actions are listed in the Action center ([https://securitycenter.windows.com/action-center](https://securitycenter.windows.com/action-center)) and the Investigations list ([https://securitycenter.windows.com/investigations](https://securitycenter.windows.com/investigations)). +>[!NOTE] +>If your organization has implemented role-based access to manage portal access, only authorized users or user groups who have permission to view the machine or machine group will be able to view the entire investigation. + ## The Action center ![Action center page](images/action-center.png) The action center consists of two main tabs, as described in the following table. - |Tab |Description | |---------|---------| |Pending actions |Displays a list of ongoing investigations that require attention. Recommended actions are presented that your security operations team can approve or reject.

**NOTE**: The Pending tab appears only if there are pending actions to be approved (or rejected). | @@ -38,17 +40,48 @@ Use the **Customize columns** menu to select columns that you'd like to show or You can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. - ## Investigations page -![Investigations page](images/mdatp-investigations.jpg) +![Image of Auto investigations page](images/atp-auto-investigations-list.png) On the **Investigations** page, you'll find a list of all automated investigations. Select an item in the list to view additional information about that automated investigation. +By default, the automated investigations list displays investigations initiated in the last week. You can also choose to select other time ranges from the drop-down menu or specify a custom range. + Use the **Customize columns** menu to select columns that you'd like to show or hide. From this view, you can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. +### Filters and details + +On the **Investigations** page, you can view details and use filters to focus on specific information. Filters include the following: +- **Status** (see the details below) +- **Triggering alert** (The alert that initiated the automated investigation) +- **Detection source** (The source of the alert that initiated the automated investigation.) +- **Entities** (these can include device or machines, and machine groups. You can filter the automated investigations list to zone in a specific machine to see other investigations related to the machine, or to see specific machine groups that you might have created.) +- **Threat** (The category of threat detected during the automated investigation.) +- **Tags** (Filter using manually added tags that capture the context of an automated investigation.) +- **Comments** (Select between filtering the list between automated investigations that have comments and those that don't.) + + +## Automated investigation status + +An automated investigation can be have one of the following status values: + +|Status |Description | +|---------|---------| +| No threats found | No malicious entities found during the investigation. | +| Failed | A problem has interrupted the investigation, preventing it from completing. | +| Partially remediated | A problem prevented the remediation of some malicious entities. | +| Pending action | Remediation actions require review and approval. | +| Waiting for machine | Investigation paused. The investigation will resume as soon as the machine is available. | +| Queued | Investigation has been queued and will resume as soon as other remediation activities are completed. | +| Running | Investigation ongoing. Malicious entities found will be remediated. | +| Remediated | Malicious entities found were successfully remediated. | +| Terminated by system | Investigation was stopped by the system. | +| Terminated by user | A user stopped the investigation before it could complete. | +| Partially investigated | Entities directly related to the alert have been investigated. However, a problem stopped the investigation of collateral entities. | + ## Next steps [View and approve remediation actions](manage-auto-investigation.md) From fa54328dd007ecbb3fee07f57ed32ed1811f6722 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 20 Feb 2020 16:06:35 -0800 Subject: [PATCH 14/17] AIR fixes --- .../auto-investigation-action-center.md | 93 ++++++++-- .../manage-auto-investigation.md | 166 ++---------------- 2 files changed, 101 insertions(+), 158 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md index 3c337a125f..50b88498b3 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md +++ b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md @@ -40,7 +40,7 @@ Use the **Customize columns** menu to select columns that you'd like to show or You can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. -## Investigations page +## The Investigations page ![Image of Auto investigations page](images/atp-auto-investigations-list.png) @@ -52,16 +52,19 @@ Use the **Customize columns** menu to select columns that you'd like to show or From this view, you can also download the entire list in CSV format using the **Export** feature, specify the number of items to show per page, and navigate between pages. -### Filters and details +### Filters for the list of investigations -On the **Investigations** page, you can view details and use filters to focus on specific information. Filters include the following: -- **Status** (see the details below) -- **Triggering alert** (The alert that initiated the automated investigation) -- **Detection source** (The source of the alert that initiated the automated investigation.) -- **Entities** (these can include device or machines, and machine groups. You can filter the automated investigations list to zone in a specific machine to see other investigations related to the machine, or to see specific machine groups that you might have created.) -- **Threat** (The category of threat detected during the automated investigation.) -- **Tags** (Filter using manually added tags that capture the context of an automated investigation.) -- **Comments** (Select between filtering the list between automated investigations that have comments and those that don't.) +On the **Investigations** page, you can view details and use filters to focus on specific information. The following table lists available filters: + +|Filter |Description | +|---------|---------| +|**Status** |(See [Automated investigation status](#automated-investigation-status)) | +|**Triggering alert** | The alert that initiated the automated investigation | +|**Detection source** |The source of the alert that initiated the automated investigation. | +|**Entities** | These can include device or machines, and machine groups. You can filter the automated investigations list to zone in a specific machine to see other investigations related to the machine, or to see specific machine groups that you might have created. | +|**Threat** |The category of threat detected during the automated investigation. | +|**Tags** |Filter using manually added tags that capture the context of an automated investigation.| +|**Comments** |Select between filtering the list between automated investigations that have comments and those that don't.| ## Automated investigation status @@ -82,6 +85,76 @@ An automated investigation can be have one of the following status values: | Terminated by user | A user stopped the investigation before it could complete. | | Partially investigated | Entities directly related to the alert have been investigated. However, a problem stopped the investigation of collateral entities. | +## View details about an automated investigation + +![Image of investigation details window](images/atp-analyze-auto-ir.png) + +You can view the details of an automated investigation to see information such as the investigation graph, alerts associated with the investigation, the machine that was investigated, and other information. + +In this view, you'll see the name of the investigation, when it started and ended. + +### Investigation graph + +The investigation graph provides a graphical representation of an automated investigation. All investigation related information is simplified and arranged in specific sections. Clicking on any of the icons brings you the relevant section where you can view more information. + +A progress ring shows two status indicators: +- Orange ring - shows the pending portion of the investigation +- Green ring - shows the running time portion of the investigation + +![Image of start, end, and pending time for an automated investigation](images/atp-auto-investigation-pending.png) + +In the example image, the automated investigation started on 10:26:59 AM and ended on 10:56:26 AM. Therefore, the entire investigation was running for 29 minutes and 27 seconds. + +The pending time of 16 minutes and 51 seconds reflects two possible pending states: pending for asset (for example, the device might have disconnected from the network) or pending for approval. + +From this view, you can also view and add comments and tags about the investigation. + +### Alerts + +The **Alerts** tab for an automated investigation shows details such as a short description of the alert that initiated the automated investigation, severity, category, the machine associated with the alert, user, time in queue, status, investigation state, and who the investigation is assigned to. + +Additional alerts seen on a machine can be added to an automated investigation as long as the investigation is ongoing. + +Selecting an alert using the check box brings up the alerts details pane where you have the option of opening the alert page, manage the alert by changing its status, see alert details, automated investigation details, related machine, logged-on users, and comments and history. + +Clicking on an alert title brings you the alert page. + +### Machines + +The **Machines** tab Shows details the machine name, IP address, group, users, operating system, remediation level, investigation count, and when it was last investigated. + +Machines that show the same threat can be added to an ongoing investigation and will be displayed in this tab. If 10 or more machines are found during this expansion process from the same entity, then that expansion action will require an approval and will be seen in the **Pending actions** view. + +Selecting a machine using the checkbox brings up the machine details pane where you can see more information such as machine details and logged-on users. + +Clicking on an machine name brings you the machine page. + +### Evidence + +The **Evidence** tab shows details related to threats associated with this investigation. + +### Entities + +The **Entities** tab shows details about entities such as files, process, services, drives, and IP addresses. The table details such as the number of entities that were analyzed. You'll gain insight into details such as how many are remediated, suspicious, or determined to be clean. + +### Log + +The **Log** tab gives a chronological detailed view of all the investigation actions taken on the alert. You'll see the action type, action, status, machine name, description of the action, comments entered by analysts who may have worked on the investigation, execution start time, duration, pending duration. + +As with other sections, you can customize columns, select the number of items to show per page, and filter the log. + +Available filters include action type, action, status, machine name, and description. + +You can also click on an action to bring up the details pane where you'll see information such as the summary of the action and input data. + +### Pending actions + +If there are pending actions on an automated investigation, you'll see a pop up similar to the following image. + +![Image of pending actions](images/pending-actions.png) + +When you click on the pending actions link, you'll be taken to the Action center. You can also navigate to the page from the navigation page by going to **automated investigation** > **Action center**. + ## Next steps [View and approve remediation actions](manage-auto-investigation.md) diff --git a/windows/security/threat-protection/microsoft-defender-atp/manage-auto-investigation.md b/windows/security/threat-protection/microsoft-defender-atp/manage-auto-investigation.md index 32343d94bd..3af42fe74d 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/manage-auto-investigation.md +++ b/windows/security/threat-protection/microsoft-defender-atp/manage-auto-investigation.md @@ -1,6 +1,6 @@ --- -title: Learn about the automated investigations dashboard in Microsoft Defender Security Center -description: View the automated investigations list. View the status, detection source and other details for automated investigations. +title: Review and approve actions following automated investigations in the Microsoft Defender Security Center +description: Review and approve (or reject) remediation actions following an automated investigation. keywords: autoir, automated, investigation, detection, dashboard, source, threat types, id, tags, machines, duration, filter export search.product: eADQiWindows 10XVcnh search.appverid: met150 @@ -8,8 +8,8 @@ ms.prod: w10 ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: security -ms.author: macapara -author: mjcaparas +ms.author: deniseb +author: denisebmsft ms.localizationpriority: medium manager: dansimp audience: ITPro @@ -17,154 +17,24 @@ ms.collection: M365-security-compliance ms.topic: conceptual --- -# Learn about the automated investigations dashboard -By default, the automated investigations list displays investigations initiated in the last week. You can also choose to select other time ranges from the drop-down menu or specify a custom range. +# Review and approve actions following an automated investigation ->[!NOTE] ->If your organization has implemented role-based access to manage portal access, only authorized users or user groups who have permission to view the machine or machine group will be able to view the entire investigation. +When an automated investigation runs, a verdict is generated for each piece of evidence investigated. Verdicts can be *Malicious*, *Suspicious*, or *Clean*. Depending on the type of threat and resulting verdict, remediation actions occur automatically or upon approval by your organization’s security operations team. For example, some actions, such as removing malware, are taken automatically. Other actions require review and approval to proceed. -Use the **Customize columns** drop-down menu to select columns that you'd like to show or hide. +As a best practice, make sure to approve (or reject) pending actions as soon as possible. This helps your automated investigations complete in a timely manner. -From this view, you can also download the entire list in CSV format using the **Export** button, specify the number of items to show per page, and navigate between pages. You also have the flexibility to filter the list based on your preferred criteria. +1. -![Image of Auto investigations page](images/atp-auto-investigations-list.png) + +You'll need to manually approve or reject pending actions on each of these categories for the automated actions to proceed. + +Selecting an investigation from any of the categories opens a panel where you can approve or reject the remediation. Other details such as file or service details, investigation details, and alert details are displayed. + +From the panel, you can click on the Open investigation page link to see the investigation details. + +You also have the option of selecting multiple investigations to approve or reject actions on multiple investigations. -**Filters**
-You can use the following operations to customize the list of automated investigations displayed: +## Related articles - -**Triggering alert**
-The alert that initiated the automated investigation. - -**Status**
-An automated investigation can be in one of the following status: - -Status | Description -:---|:--- -| No threats found | No malicious entities found during the investigation. -| Failed | A problem has interrupted the investigation, preventing it from completing. | -| Partially remediated | A problem prevented the remediation of some malicious entities. | -| Pending action | Remediation actions require review and approval. | -| Waiting for machine | Investigation paused. The investigation will resume as soon as the machine is available. | -| Queued | Investigation has been queued and will resume as soon as other remediation activities are completed. | -| Running | Investigation ongoing. Malicious entities found will be remediated. | -| Remediated | Malicious entities found were successfully remediated. | -| Terminated by system | Investigation was stopped by the system. | -| Terminated by user | A user stopped the investigation before it could complete. -| Partially investigated | Entities directly related to the alert have been investigated. However, a problem stopped the investigation of collateral entities. | - - - -**Detection source**
-Source of the alert that initiated the automated investigation. - -**Threat**
-The category of threat detected during the automated investigation. - - -**Tags**
-Filter using manually added tags that capture the context of an automated investigation. - -**Machines**
-You can filter the automated investigations list to zone in a specific machine to see other investigations related to the machine. - -**Machine groups**
-Apply this filter to see specific machine groups that you might have created. - -**Comments**
-Select between filtering the list between automated investigations that have comments and those that don't. - -## Analyze automated investigations -You can view the details of an automated investigation to see information such as the investigation graph, alerts associated with the investigation, the machine that was investigated, and other information. - -In this view, you'll see the name of the investigation, when it started and ended. - -![Image of investigation details window](images/atp-analyze-auto-ir.png) - -The progress ring shows two status indicators: -- Orange ring - shows the pending portion of the investigation -- Green ring - shows the running time portion of the investigation - -![Image of start, end, and pending time for an automated investigation](images/atp-auto-investigation-pending.png) - -In the example image, the automated investigation started on 10:26:59 AM and ended on 10:56:26 AM. Therefore, the entire investigation was running for 29 minutes and 27 seconds. - -The pending time of 16 minutes and 51 seconds reflects two possible pending states: pending for asset (for example, the device might have disconnected from the network) or pending for approval. - -From this view, you can also view and add comments and tags about the investigation. - -### Investigation page -The investigation page gives you a quick summary on the status, alert severity, category, and detection source. - -You'll also have access to the following sections that help you see details of the investigation with finer granularity: - -- Investigation graph -- Alerts -- Machines -- Evidence -- Entities -- Log -- Pending actions - - >[!NOTE] - >The Pending actions tab is only displayed if there are actual pending actions. - -- Pending actions history - - >[!NOTE] - >The Pending actions history tab is only displayed when an investigation is complete. - -In any of the sections, you can customize columns to further expand to limit the details you see in a section. - -### Investigation graph -The investigation graph provides a graphical representation of an automated investigation. All investigation related information is simplified and arranged in specific sections. Clicking on any of the icons brings you the relevant section where you can view more information. - -### Alerts -Shows details such as a short description of the alert that initiated the automated investigation, severity, category, the machine associated with the alert, user, time in queue, status, investigation state, and who the investigation is assigned to. - -Additional alerts seen on a machine can be added to an automated investigation as long as the investigation is ongoing. - -Selecting an alert using the check box brings up the alerts details pane where you have the option of opening the alert page, manage the alert by changing its status, see alert details, automated investigation details, related machine, logged-on users, and comments and history. - -Clicking on an alert title brings you the alert page. - -### Machines -Shows details the machine name, IP address, group, users, operating system, remediation level, investigation count, and when it was last investigated. - -Machines that show the same threat can be added to an ongoing investigation and will be displayed in this tab. If 10 or more machines are found during this expansion process from the same entity, then that expansion action will require an approval and will be seen in the **Pending actions** view. - -Selecting a machine using the checkbox brings up the machine details pane where you can see more information such as machine details and logged-on users. - -Clicking on an machine name brings you the machine page. - -### Evidence -Shows details related to threats associated with this investigation. - -### Entities -Shows details about entities such as files, process, services, drives, and IP addresses. The table details such as the number of entities that were analyzed. You'll gain insight into details such as how many are remediated, suspicious, or determined to be clean. - -### Log -Gives a chronological detailed view of all the investigation actions taken on the alert. You'll see the action type, action, status, machine name, description of the action, comments entered by analysts who may have worked on the investigation, execution start time, duration, pending duration. - -As with other sections, you can customize columns, select the number of items to show per page, and filter the log. - -Available filters include action type, action, status, machine name, and description. - -You can also click on an action to bring up the details pane where you'll see information such as the summary of the action and input data. - -### Pending actions history -This tab is only displayed when an investigation is complete and shows all pending actions taken during the investigation. - - -## Pending actions -If there are pending actions on an automated investigation, you'll see a pop up similar to the following image. - -![Image of pending actions](images/pending-actions.png) - -When you click on the pending actions link, you'll be taken to the Action center. You can also navigate to the page from the navigation page by going to **automated investigation** > **Action center**. For more information, see [Action center](auto-investigation-action-center.md). - - -## Related topic -- [Investigate Microsoft Defender ATP alerts](investigate-alerts.md) -- [Manage actions related to automated investigation and remediation](auto-investigation-action-center.md) +[Advanced Hunting](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-overview) \ No newline at end of file From fe0ac889f6cce95e176a2e8b7d71fa28353073c4 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 20 Feb 2020 16:13:58 -0800 Subject: [PATCH 15/17] AIR content updates --- .../auto-investigation-action-center.md | 1 - .../manage-auto-investigation.md | 22 ++++++++++++++----- 2 files changed, 17 insertions(+), 6 deletions(-) diff --git a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md index 50b88498b3..d297b71baf 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md +++ b/windows/security/threat-protection/microsoft-defender-atp/auto-investigation-action-center.md @@ -18,7 +18,6 @@ ms.topic: article # View details and results of automated investigations -When an automated investigation runs, a verdict is generated for each piece of evidence investigated. Verdicts can be *Malicious*, *Suspicious*, or *Clean*. Depending on the type of threat and resulting verdict, remediation actions occur automatically or upon approval by your organization’s security operations team. Pending and completed actions are listed in the Action center ([https://securitycenter.windows.com/action-center](https://securitycenter.windows.com/action-center)) and the Investigations list ([https://securitycenter.windows.com/investigations](https://securitycenter.windows.com/investigations)). diff --git a/windows/security/threat-protection/microsoft-defender-atp/manage-auto-investigation.md b/windows/security/threat-protection/microsoft-defender-atp/manage-auto-investigation.md index 3af42fe74d..04e76fc5f1 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/manage-auto-investigation.md +++ b/windows/security/threat-protection/microsoft-defender-atp/manage-auto-investigation.md @@ -23,18 +23,30 @@ When an automated investigation runs, a verdict is generated for each piece of e As a best practice, make sure to approve (or reject) pending actions as soon as possible. This helps your automated investigations complete in a timely manner. -1. +## Review pending actions +1. Go to the Microsoft Defender Security Center ([https://securitycenter.windows.com](https://securitycenter.windows.com)) and sign in. This takes you to your Security dashboard. -You'll need to manually approve or reject pending actions on each of these categories for the automated actions to proceed. +2. On the Security dashboard, in the navigation pane on the left, choose **Automated investigations** > **Action center**. -Selecting an investigation from any of the categories opens a panel where you can approve or reject the remediation. Other details such as file or service details, investigation details, and alert details are displayed. +3. Review any items on the **Pending** tab. -From the panel, you can click on the Open investigation page link to see the investigation details. + Selecting an investigation from any of the categories opens a panel where you can approve or reject the remediation. Other details such as file or service details, investigation details, and alert details are displayed. From the panel, you can click on the **Open investigation page** link to see the investigation details. -You also have the option of selecting multiple investigations to approve or reject actions on multiple investigations. + You can also select multiple investigations to approve or reject actions on multiple investigations. + +## Review completed actions + +1. Go to the Microsoft Defender Security Center ([https://securitycenter.windows.com](https://securitycenter.windows.com)) and sign in. This takes you to your Security dashboard. + +2. On the Security dashboard, in the navigation pane on the left, choose **Automated investigations** > **Action center**. + +3. Select the **History** tab. (If need be, expand the time period to display more data.) + +4. Select an item to view more details about that remediation action. + ## Related articles [Advanced Hunting](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/advanced-hunting-overview) \ No newline at end of file From db84fe31d54897122fb822b17137dc6a5d569e95 Mon Sep 17 00:00:00 2001 From: Denise Vangel-MSFT Date: Thu, 20 Feb 2020 16:26:43 -0800 Subject: [PATCH 16/17] Update index.md --- windows/security/threat-protection/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/security/threat-protection/index.md b/windows/security/threat-protection/index.md index 16ddcac988..fe2f573495 100644 --- a/windows/security/threat-protection/index.md +++ b/windows/security/threat-protection/index.md @@ -100,9 +100,9 @@ Endpoint detection and response capabilities are put in place to detect, investi In conjunction with being able to quickly respond to advanced attacks, Microsoft Defender ATP offers automatic investigation and remediation capabilities that help reduce the volume of alerts in minutes at scale. - [Automated investigation and remediation](microsoft-defender-atp/automated-investigations.md) -- [Threat remediation](microsoft-defender-atp/automated-investigations.md#how-threats-are-remediated) -- [Manage automated investigation](microsoft-defender-atp/manage-auto-investigation.md) -- [Analyze automated investigation](microsoft-defender-atp/manage-auto-investigation.md#analyze-automated-investigations) +- [Overview of automated investigation and remediation](microsoft-defender-atp/automated-investigations.md) +- [View details and results of automated investigations](microsoft-defender-atp/auto-investigation-action-center.md) +- [View and approve remediation actions](microsoft-defender-atp/manage-auto-investigation.md) From ded072442e1281303240e523ff7992249814076a Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Thu, 20 Feb 2020 17:06:08 -0800 Subject: [PATCH 17/17] CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20200220162439 (#2097) Co-authored-by: Direesh Kumar Kandakatla --- .../resolved-issues-windows-10-1803.yml | 20 ------------------- .../status-windows-10-1507.yml | 4 ++-- ...indows-10-1607-and-windows-server-2016.yml | 8 ++++---- .../status-windows-10-1709.yml | 8 ++++---- .../status-windows-10-1803.yml | 8 ++++---- ...indows-10-1809-and-windows-server-2019.yml | 8 ++++---- .../status-windows-10-1903.yml | 8 ++++---- .../status-windows-10-1909.yml | 8 ++++---- 8 files changed, 26 insertions(+), 46 deletions(-) diff --git a/windows/release-information/resolved-issues-windows-10-1803.yml b/windows/release-information/resolved-issues-windows-10-1803.yml index c5f045f610..63b5bd826c 100644 --- a/windows/release-information/resolved-issues-windows-10-1803.yml +++ b/windows/release-information/resolved-issues-windows-10-1803.yml @@ -38,8 +38,6 @@ sections:
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 17134.1009

September 23, 2019
KB4522014Resolved
KB4520008October 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 17134.1006

September 10, 2019
KB4516058Resolved
September 19, 2019
04:08 PM PT
Notification issue: \"Your device is missing important security and quality fixes.\"
Some users may have incorrectly received the notification \"Your device is missing important security and quality fixes.\"

See details >N/A

Resolved
September 03, 2019
12:32 PM 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 >OS Build 17134.829

June 11, 2019
KB4503286Resolved
KB4512509August 19, 2019
02:00 PM PT -
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications made using VB6, macros using VBA, and VBScript may stop responding and you may receive an error.

See details >OS Build 17134.950

August 13, 2019
KB4512501Resolved
KB4512509August 19, 2019
02:00 PM PT " @@ -71,24 +69,6 @@ sections: " -- title: August 2019 -- items: - - type: markdown - text: " - - -
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512501, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an \"invalid procedure call error.\"

Affected platforms:
  • Client: Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue was resolved in KB4512509. The ‘optional’ update will be available on Microsoft Update Catalog, Windows Update, Microsoft Update and Windows Server Update Services (WSUS). As with any 'optional' update, you will need to Check for updates to receive KB4512509 and install. For instructions, see Update Windows 10.

Note Windows Update for Business customers should apply the update via Microsoft Update Catalog or Windows Server Update Services (WSUS).

Back to top		OS Build 17134.950

August 13, 2019
KB4512501		Resolved
KB4512509		Resolved:
August 19, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
- " - -- title: July 2019 -- items: - - type: markdown - text: " - - -
DetailsOriginating updateStatusHistory
Devices starting using PXE from a WDS or SCCM servers may fail to start
Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503286 on a WDS server.

Affected platforms:
  • Server: Windows Server 2008 SP2; Windows Server 2008 R2 SP1; Windows Server 2012; Windows Server 2012 R2; Windows Server 2016; Windows Server, version 1803; Windows Server 2019; Windows Server, version 1809; Windows Server, version 1903
Resolution: This issue was resolved in KB4512509.

Back to top		OS Build 17134.829

June 11, 2019
KB4503286		Resolved
KB4512509		Resolved:
August 19, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
- " - - title: June 2019 - items: - type: markdown diff --git a/windows/release-information/status-windows-10-1507.yml b/windows/release-information/status-windows-10-1507.yml index 50e384face..9c9ab15b4e 100644 --- a/windows/release-information/status-windows-10-1507.yml +++ b/windows/release-information/status-windows-10-1507.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
You might encounter issues with KB4502496
You might encounter issues trying to install or after installing KB4502496

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

See details >		N/A
February 11, 2020
KB4502496		Mitigated
February 15, 2020
01:22 AM PT
TLS connections might fail or timeout
Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption.

See details >		OS Build 10240.18368

October 08, 2019
KB4520011		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 10240.18094

January 08, 2019
KB4480962		Mitigated
April 25, 2019
02:00 PM PT
@@ -78,7 +78,7 @@ sections: - type: markdown text: " - +
DetailsOriginating updateStatusHistory
You might encounter issues with KB4502496
You might encounter issues trying to install or after installing KB4502496.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4502496) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4502496 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4502496		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4502496
You might encounter issues trying to install or after installing KB4502496.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4502496) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4502496 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4502496		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM 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 ad5f5d081d..a70457e0ab 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,8 +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.

- - + + @@ -81,8 +81,8 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

See details >		N/A
February 11, 2019
KB4524244		Mitigated
February 15, 2020
01:22 AM PT
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

See details >		N/A
February 11, 2020
KB4524244		Mitigated
February 15, 2020
01:22 AM PT
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
- - + +
DetailsOriginating updateStatusHistory
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
" diff --git a/windows/release-information/status-windows-10-1709.yml b/windows/release-information/status-windows-10-1709.yml index b0ee5c7ec5..de65b88d9b 100644 --- a/windows/release-information/status-windows-10-1709.yml +++ b/windows/release-information/status-windows-10-1709.yml @@ -60,8 +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.

- - + + @@ -80,8 +80,8 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

See details >		N/A
February 11, 2019
KB4524244		Mitigated
February 15, 2020
01:22 AM PT
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

See details >		N/A
February 11, 2020
KB4524244		Mitigated
February 15, 2020
01:22 AM PT
Unable to create local users in Chinese, Japanese and Korean during device setup
You might be unable to create users in Chinese, Japanese and Korean using Input Method Editor (IME) during OOBE.

See details >		OS Build 16299.1387

September 10, 2019
KB4516066		Resolved
KB4534318		January 23, 2020
02:00 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 16299.1451

October 08, 2019
KB4520004		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 16299.904

January 08, 2019
KB4480978		Mitigated
April 25, 2019
02:00 PM PT
- - + +
DetailsOriginating updateStatusHistory
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
" diff --git a/windows/release-information/status-windows-10-1803.yml b/windows/release-information/status-windows-10-1803.yml index f390bca9da..db738bc8ee 100644 --- a/windows/release-information/status-windows-10-1803.yml +++ b/windows/release-information/status-windows-10-1803.yml @@ -64,8 +64,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.

- - + + @@ -84,8 +84,8 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

See details >		N/A
February 11, 2019
KB4524244		Mitigated
February 15, 2020
01:22 AM PT
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

See details >		N/A
February 11, 2020
KB4524244		Mitigated
February 15, 2020
01:22 AM PT
Unable to create local users in Chinese, Japanese and Korean during device setup
You might be unable to create users in Chinese, Japanese and Korean using Input Method Editor (IME) during OOBE.

See details >		OS Build 17134.1006

September 10, 2019
KB4516058		Resolved
KB4534308		January 23, 2020
02:00 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 17134.1069

October 08, 2019
KB4520008		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 17134.523

January 08, 2019
KB4480966		Mitigated
April 25, 2019
02:00 PM PT
- - + +
DetailsOriginating updateStatusHistory
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
" diff --git a/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml index da6e037493..b1fc3e7ceb 100644 --- a/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml +++ b/windows/release-information/status-windows-10-1809-and-windows-server-2019.yml @@ -64,8 +64,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.

- - + + @@ -85,8 +85,8 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

See details >		N/A
February 11, 2019
KB4524244		Mitigated
February 15, 2020
01:22 AM PT
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

See details >		N/A
February 11, 2020
KB4524244		Mitigated
February 15, 2020
01:22 AM PT
Unable to create local users in Chinese, Japanese and Korean during device setup
You might be unable to create users in Chinese, Japanese and Korean using Input Method Editor (IME) during OOBE.

See details >		OS Build 17763.737

September 10, 2019
KB4512578		Resolved
KB4534321		January 23, 2020
02:00 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 17763.805

October 08, 2019
KB4519338		Mitigated External
November 05, 2019
03:36 PM PT
Devices with some Asian language packs installed may receive an error
Devices with Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.\"

See details >		OS Build 17763.437

April 09, 2019
KB4493509		Mitigated
May 03, 2019
10:59 AM PT
- - + +
DetailsOriginating updateStatusHistory
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
" diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index 4b98890fff..4fe4e28478 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -64,8 +64,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
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

See details >		N/A
February 11, 2019
KB4524244		Mitigated
February 15, 2020
01:22 AM PT
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

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

See details >		N/A

Mitigated External
November 25, 2019
05:25 PM PT
TLS connections might fail or timeout
Transport Layer Security (TLS) connections might fail or timeout when connecting or attempting a resumption.

See details >		OS Build 18362.418

October 08, 2019
KB4517389		Mitigated External
November 05, 2019
03:36 PM PT
@@ -83,8 +83,8 @@ sections: - type: markdown text: " - - + +
DetailsOriginating updateStatusHistory
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
" diff --git a/windows/release-information/status-windows-10-1909.yml b/windows/release-information/status-windows-10-1909.yml index 355ff2a8c2..6029fe13f7 100644 --- a/windows/release-information/status-windows-10-1909.yml +++ b/windows/release-information/status-windows-10-1909.yml @@ -64,8 +64,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
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

See details >		N/A
February 11, 2019
KB4524244		Mitigated
February 15, 2020
01:22 AM PT
“Reset this PC” feature might fail
“Reset this PC” feature is also called “Push Button Reset” or PBR.

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

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

See details >		N/A

Mitigated External
November 25, 2019
05:25 PM PT
" @@ -82,8 +82,8 @@ sections: - type: markdown text: " - - + +
DetailsOriginating updateStatusHistory
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2019
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
“Reset this PC” feature might fail
Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Workaround: The standalone security update, KB4524244 has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Update (LCU), Monthly Rollup or Security Only update.

If you have installed this update and are experiencing this issue, the following steps should allow you to reset your device:
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
  5. Upon restart use the “Reset this PC” feature and you should not encounter this issue.

Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
You might encounter issues with KB4524244
You might encounter issues trying to install or after installing KB4524244.

Affected platforms:
  • Client: Windows 10, version 1909; Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1
  • Server: Windows Server, version 1909; Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Workaround: To help a sub-set of affected devices, the standalone security update (KB4524244) has been removed and will not re-offered from Windows Update, Windows Server Update Services (WSUS) or Microsoft Update Catalog. Note This does not affect any other update, including Latest Cumulative Updates (LCUs), Monthly Rollups or Security Only updates.

If this update is installed and you are experiencing issues, you can uninstall this update.
  1. Select the start button or Windows Desktop Search and type update history and select View your Update history.
  2. On the Settings/View update history dialog window, Select Uninstall Updates.
  3. On the Installed Updates dialog window, find and select KB4524244 and select the Uninstall button.
  4. Restart your device.
 
Next steps: We are working on an improved version of this update in coordination with our partners and will release it in a future update.

Back to top		N/A
February 11, 2020
KB4524244		Mitigated
Last updated:
February 15, 2020
01:22 AM PT

Opened:
February 15, 2020
12:02 AM PT
"