From 88f69339a1a2ed2653c68c9b1fd743b907727f59 Mon Sep 17 00:00:00 2001 From: DocsPreview <49669258+DocsPreview@users.noreply.github.com> Date: Mon, 19 Aug 2019 14:45:06 -0700 Subject: [PATCH 1/9] Merge changes from master to live (#950) * v 1.6 * removed a known issue * removed references to CB, CBB * Latest changes for publish today (#949) --- .../manage-windows-updates-for-surface-hub.md | 3 +- devices/surface/ltsb-for-surface.md | 13 +- windows/deployment/deploy-whats-new.md | 369 +++++++++--------- windows/deployment/upgrade/setupdiag.md | 95 +++-- .../resolved-issues-windows-10-1607.yml | 8 +- .../resolved-issues-windows-10-1703.yml | 6 - .../resolved-issues-windows-10-1709.yml | 8 +- .../resolved-issues-windows-10-1803.yml | 18 +- ...indows-10-1809-and-windows-server-2019.yml | 2 + ...ndows-7-and-windows-server-2008-r2-sp1.yml | 19 +- ...windows-8.1-and-windows-server-2012-r2.yml | 16 +- ...esolved-issues-windows-server-2008-sp2.yml | 14 +- .../resolved-issues-windows-server-2012.yml | 16 +- ...indows-10-1607-and-windows-server-2016.yml | 4 +- .../status-windows-10-1709.yml | 4 +- .../status-windows-10-1803.yml | 8 +- ...indows-10-1809-and-windows-server-2019.yml | 4 +- .../status-windows-10-1903.yml | 4 +- ...ndows-7-and-windows-server-2008-r2-sp1.yml | 4 +- ...windows-8.1-and-windows-server-2012-r2.yml | 4 +- .../status-windows-server-2008-sp2.yml | 4 +- .../status-windows-server-2012.yml | 4 +- 22 files changed, 317 insertions(+), 310 deletions(-) diff --git a/devices/surface-hub/manage-windows-updates-for-surface-hub.md b/devices/surface-hub/manage-windows-updates-for-surface-hub.md index 01c378c14a..4535bd1f1b 100644 --- a/devices/surface-hub/manage-windows-updates-for-surface-hub.md +++ b/devices/surface-hub/manage-windows-updates-for-surface-hub.md @@ -10,7 +10,6 @@ ms.sitesec: library author: dansimp ms.author: dansimp ms.topic: article -ms.date: 06/20/2019 ms.localizationpriority: medium --- @@ -69,7 +68,7 @@ This table gives examples of deployment rings. | Deployment ring | Ring size | Servicing branch | Deferral for feature updates | Deferral for quality updates (security fixes, drivers, and other updates) | Validation step | | --------- | --------- | --------- | --------- | --------- | --------- | -| Preview (e.g. non-critical or test devices) | Small | Semi-annual channel (Targeted) | None. | None. | Manually test and evaluate new functionality. Pause updates if there are issues. | +| Preview (e.g. non-critical or test devices) | Small | Windows Insider Preview | None. | None. | Manually test and evaluate new functionality. Pause updates if there are issues. | | Release (e.g. devices used by select teams) | Medium | Semi-annual channel | None. | None. | Monitor device usage and user feedback. Pause updates if there are issues. | | Broad deployment (e.g. most of the devices in your organization) | Large | Semi-annual channel | 120 days after release. | 7-14 days after release. | Monitor device usage and user feedback. Pause updates if there are issues. | | Mission critical (e.g. devices in executive boardrooms) | Small | Semi-annual channel | 180 days after release (maximum deferral for feature updates). | 30 days after release (maximum deferral for quality updates). | Monitor device usage and user feedback. | diff --git a/devices/surface/ltsb-for-surface.md b/devices/surface/ltsb-for-surface.md index d7e5bdc7d7..225135d993 100644 --- a/devices/surface/ltsb-for-surface.md +++ b/devices/surface/ltsb-for-surface.md @@ -1,5 +1,5 @@ --- -title: Long-Term Servicing Branch for Surface devices (Surface) +title: Long-Term Servicing Channel for Surface devices (Surface) description: LTSB is not supported for general-purpose Surface devices and should be used for specialized devices only. ms.prod: w10 ms.mktglfcycl: manage @@ -8,26 +8,25 @@ ms.sitesec: library author: dansimp ms.author: dansimp ms.topic: article -ms.date: 04/25/2017 ms.reviewer: manager: dansimp --- -# Long-Term Servicing Branch (LTSB) for Surface devices +# Long-Term Servicing Channel (LTSC) for Surface devices >[!WARNING] >For updated information on this topic, see [Surface device compatibility with Windows 10 Long-Term Servicing Channel](surface-device-compatibility-with-windows-10-ltsc.md). For additional information on this update, see the [Documentation Updates for Surface and Windows 10 LTSB Compatibility](https://blogs.technet.microsoft.com/surface/2017/04/11/documentation-updates-for-surface-and-windows-10-ltsb-compatibility) post on the Surface Blog for IT Pros. -General-purpose Surface devices running Long-Term Servicing Branch (LTSB) are not supported. As a general guideline, if a Surface device runs productivity software, such as Microsoft Office, it is a general-purpose device that does not qualify for LTSB and should instead run Current Branch (CB) or Current Branch for Business (CBB). +General-purpose Surface devices in the Long-Term Servicing Channel (LTSC) are not supported. As a general guideline, if a Surface device runs productivity software, such as Microsoft Office, it is a general-purpose device that does not qualify for LTSC and should instead be on the Semi-Annual Channel. >[!NOTE] >For more information about the servicing branches, see [Overview of Windows as a service](https://technet.microsoft.com/itpro/windows/manage/waas-overview). -LTSB prevents Surface devices from receiving critical Windows 10 feature updates and certain non-security servicing updates. Customers with poor experiences using Surface devices in the LTSB configuration will be instructed to upgrade to CB or CBB. Furthermore, the Windows 10 Enterprise LTSB edition removes core features of Surface devices, including seamless inking and touch-friendly applications. It does not contain key in-box applications including Microsoft Edge, OneNote, Calendar or Camera. Therefore, productivity is impacted and functionality is limited. LTSB is not supported as a suitable servicing solution for general-purpose Surface devices. +LTSC prevents Surface devices from receiving critical Windows 10 feature updates and certain non-security servicing updates. Customers with poor experiences using Surface devices in the LTSC configuration will be instructed to switch to the Semi-Annual Channel. Furthermore, the Windows 10 Enterprise LTSB edition removes core features of Surface devices, including seamless inking and touch-friendly applications. It does not contain key in-box applications including Microsoft Edge, OneNote, Calendar or Camera. Therefore, productivity is impacted and functionality is limited. LTSC is not supported as a suitable servicing solution for general-purpose Surface devices. -General-purpose Surface devices are intended to run CB or CBB to receive full servicing and firmware updates and forward compatibility with the introduction of new Surface features. With CB, feature updates are available as soon as Microsoft releases them. Customers in the CBB servicing model receive the same build of Windows 10 as those in CB, at a later date. +General-purpose Surface devices are intended to run on the Semi-Annual Channel to receive full servicing and firmware updates and forward compatibility with the introduction of new Surface features. In the Semi-Annual Channel, feature updates are available as soon as Microsoft releases them. -Surface devices in specialized scenarios–such as PCs that control medical equipment, point-of-sale systems, and ATMs–may consider the use of LTSB. These special-purpose systems typically perform a single task and do not require feature updates as frequently as other devices in the organization. +Surface devices in specialized scenarios–such as PCs that control medical equipment, point-of-sale systems, and ATMs–might consider the use of LTSC. These special-purpose systems typically perform a single task and do not require feature updates as frequently as other devices in the organization. diff --git a/windows/deployment/deploy-whats-new.md b/windows/deployment/deploy-whats-new.md index 85ffed51b0..e32aae1631 100644 --- a/windows/deployment/deploy-whats-new.md +++ b/windows/deployment/deploy-whats-new.md @@ -1,184 +1,185 @@ ---- -title: What's new in Windows 10 deployment -ms.reviewer: -manager: laurawi -ms.author: greglin -description: Changes and new features related to Windows 10 deployment -keywords: deployment, automate, tools, configure, news -ms.mktglfcycl: deploy -ms.localizationpriority: medium -ms.prod: w10 -ms.sitesec: library -ms.pagetype: deploy -audience: itpro author: greg-lindsay -ms.topic: article ---- - -# What's new in Windows 10 deployment - -**Applies to** -- Windows 10 - -## In this topic - -This topic provides an overview of new solutions and online content related to deploying Windows 10 in your organization. - -- For an all-up overview of new features in Windows 10, see [What's new in Windows 10](https://docs.microsoft.com/windows/whats-new/index). -- For a detailed list of changes to Windows 10 ITPro TechNet library content, see [Online content change history](#online-content-change-history). - -## Recent additions to this page - -[SetupDiag](#setupdiag) 1.4.1 is released.
-The [Windows ADK for Windows 10, version 1903](https://docs.microsoft.com/windows-hardware/get-started/adk-install) is available.
-New [Windows Autopilot](#windows-autopilot) content is available.
-[Windows 10 Subscription Activation](#windows-10-subscription-activation) now supports Windows 10 Education. - -## The Modern Desktop Deployment Center - -The [Modern Desktop Deployment Center](https://docs.microsoft.com/microsoft-365/enterprise/desktop-deployment-center-home) has launched with tons of content to help you with large-scale deployment of Windows 10 and Office 365 ProPlus. - -## Microsoft 365 - -Microsoft 365 is a new offering from Microsoft that combines -- Windows 10 -- Office 365 -- Enterprise Mobility and Security (EMS). - -See [Deploy Windows 10 with Microsoft 365](deploy-m365.md) for an overview, which now includes a link to download a nifty [M365 Enterprise poster](deploy-m365.md#m365-enterprise-poster). - -## Windows 10 servicing and support - -- [**Delivery Optimization**](https://docs.microsoft.com/windows/deployment/update/waas-delivery-optimization): Improved Peer Efficiency for enterprises and educational institutions with complex networks is enabled with of [new policies](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-deliveryoptimization). This now supports Office 365 ProPlus updates, and Intune content, with System Center Configuration Manager content coming soon! -- [**Automatic Restart Sign-on (ARSO)**](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#automatic-restart-and-sign-on-arso-for-enterprises-build-18305): Windows will automatically logon as the user and lock their device in order to complete the update, ensuring that when the user returns and unlocks the device, the update will be completed. -- [**Windows Update for Business**](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-and-the-retirement-of-SAC-T/ba-p/339523): There will now be a single, common start date for phased deployments (no more SAC-T designation). In addition, there will a new notification and reboot scheduling experience for end users, the ability to enforce update installation and reboot deadlines, and the ability to provide end user control over reboots for a specific time period. -- **Update rollback improvements**: You can now automatically recover from startup failures by removing updates if the startup failure was introduced after the installation of recent driver or quality updates. When a device is unable to start up properly after the recent installation of Quality of driver updates, Windows will now automatically uninstall the updates to get the device back up and running normally. -- **Pause updates**: We have extended the ability to pause updates for both feature and monthly updates. This extension ability is for all editions of Windows 10, including Home. You can pause both feature and monthly updates for up to 35 days (seven days at a time, up to five times). Once the 35-day pause period is reached, you will need to update your device before pausing again. -- **Improved update notifications**: When there’s an update requiring you to restart your device, you’ll see a colored dot on the Power button in the Start menu and on the Windows icon in your taskbar. -- **Intelligent active hours**: To further enhance active hours, users will now have the option to let Windows Update intelligently adjust active hours based on their device-specific usage patterns. You must enable the intelligent active hours feature for the system to predict device-specific usage patterns. -- **Improved update orchestration to improve system responsiveness**: This feature will improve system performance by intelligently coordinating Windows updates and Microsoft Store updates, so they occur when users are away from their devices to minimize disruptions. - -Microsoft previously announced that we are [extending support](https://www.microsoft.com/microsoft-365/blog/2018/09/06/helping-customers-shift-to-a-modern-desktop) for Windows 10 Enterprise and Windows 10 Education editions to 30 months from the version release date. This includes all past versions and future versions that are targeted for release in September (versions ending in 09, ex: 1809). Future releases that are targeted for release in March (versions ending in 03, ex: 1903) will continue to be supported for 18 months from their release date. All releases of Windows 10 Home, Windows 10 Pro, and Office 365 ProPlus will continue to be supported for 18 months (there is no change for these editions). These support policies are summarized in the table below. - -![Support lifecycle](images/support-cycle.png) - -## Windows 10 Enterprise upgrade - -Windows 10 version 1703 includes a Windows 10 Enterprise E3 and E5 benefit to Microsoft customers with Enterprise Agreements (EA) or Microsoft Products & Services Agreements (MPSA). These customers can now subscribe users to Windows 10 Enterprise E3 or E5 and activate their subscriptions on up to five devices. Virtual machines can also be activated. For more information, see [Windows 10 Enterprise Subscription Activation](windows-10-subscription-activation.md). - -Windows 10 Enterprise E3 launched in the Cloud Solution Provider (CSP) channel on September 1, 2016. Previously, only organizations with a Microsoft Volume Licensing Agreement could deploy Windows 10 Enterprise to their users. With Windows 10 Enterprise E3 in CSP, small and medium-sized organizations can more easily take advantage of Windows 10 Enterprise features. - -For more information, see [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md) - - -## Deployment solutions and tools - -### Windows Autopilot - -[Windows Autopilot](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot) streamlines and automates the process of setting up and configuring new devices, with minimal interaction required from the end user. You can also use Windows Autopilot to reset, repurpose and recover devices. - -The following Windows Autopilot features are available in Windows 10, version 1903 and later: - -- [Windows Autopilot for white glove deployment](https://docs.microsoft.com/windows/deployment/windows-autopilot/white-glove) is new in Windows 10, version 1903. "White glove" deployment enables partners or IT staff to pre-provision devices so they are fully configured and business ready for your users. -- The Intune [enrollment status page](https://docs.microsoft.com/intune/windows-enrollment-status) (ESP) now tracks Intune Management Extensions​. -- [Cortana voiceover](https://docs.microsoft.com/windows-hardware/customize/desktop/cortana-voice-support) and speech recognition during OOBE is disabled by default for all Windows 10 Pro Education, and Enterprise SKUs. -- Windows Autopilot is self-updating during OOBE. Starting with the Windows 10, version 1903 Autopilot functional and critical updates will begin downloading automatically during OOBE. -- Windows Autopilot will set the [diagnostics data](https://docs.microsoft.com/windows/privacy/windows-diagnostic-data) level to Full on Windows 10 version 1903 and later during OOBE. - -### Windows 10 Subscription Activation - -Windows 10 Education support has been added to Windows 10 Subscription Activation. - -With Windows 10, version 1903, you can step-up from Windows 10 Pro Education to the enterprise-grade edition for educational institutions – Windows 10 Education. For more information, see [Windows 10 Subscription Activation](https://docs.microsoft.com/windows/deployment/windows-10-subscription-activation). - -### SetupDiag - -[SetupDiag](upgrade/setupdiag.md) is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful. - -SetupDiag version 1.4.1 was released on 5/17/2019. - -### Upgrade Readiness - -The Upgrade Readiness tool moved from public preview to general availability on March 2, 2017. - -Upgrade Readiness helps you ensure that applications and drivers are ready for a Windows 10 upgrade. The solution provides up-to-date application and driver inventory, information about known issues, troubleshooting guidance, and per-device readiness and tracking details. - -The development of Upgrade Readiness has been heavily influenced by input from the community the development of new features is ongoing. To begin using Upgrade Readiness, add it to an existing Operation Management Suite (OMS) workspace or sign up for a new OMS workspace with the Upgrade Readiness solution enabled. - -For more information about Upgrade Readiness, see the following topics: - -- [Windows Analytics blog](https://aka.ms/blog/WindowsAnalytics/) -- [Manage Windows upgrades with Upgrade Readiness](upgrade/manage-windows-upgrades-with-upgrade-readiness.md) - - -### Update Compliance - -Update Compliance helps you to keep Windows 10 devices in your organization secure and up-to-date. - -Update Compliance is a solution built using OMS Logs and Analytics that provides information about installation status of monthly quality and feature updates. Details are provided about the deployment progress of existing updates and the status of future updates. Information is also provided about devices that might need attention to resolve issues. - -For more information about Update Compliance, see [Monitor Windows Updates with Update Compliance](update/update-compliance-monitor.md). - -### Device Health - -Device Health is the newest Windows Analytics solution that complements the existing Upgrade Readiness and Update Compliance solutions by helping to identify devices crashes and the cause. Device drivers that are causing crashes are identified along with alternative drivers that might reduce the number of crashes. Windows Information Protection misconfigurations are also identified. For more information, see [Monitor the health of devices with Device Health](update/device-health-monitor.md) - -### MBR2GPT - -MBR2GPT.EXE converts a disk from Master Boot Record (MBR) to GUID Partition Table (GPT) partition style without modifying or deleting data on the disk. Previously, it was necessary to image, then wipe and reload a disk to change from MBR format to GPT. - -There are many benefits to converting the partition style of a disk to GPT, including the use of larger disk partitions, added data reliability, and faster boot and shutdown speeds. The GPT format also enables you to use the Unified Extensible Firmware Interface (UEFI) which replaces the Basic Input/Output System (BIOS) firmware interface. Security features of Windows 10 that require UEFI mode include: Secure Boot, Early Launch Anti-malware (ELAM) driver, Windows Trusted Boot, Measured Boot, Device Guard, Credential Guard, and BitLocker Network Unlock. - -For more information, see [MBR2GPT.EXE](mbr-to-gpt.md). - - -### Microsoft Deployment Toolkit (MDT) - -MDT build 8456 (12/19/2018) is available, including support for Windows 10, version 1809, and Windows Server 2019. - -For more information about MDT, see the [MDT resource page](https://docs.microsoft.com/sccm/mdt/). - - -### Windows Assessment and Deployment Kit (ADK) - -The Windows Assessment and Deployment Kit (Windows ADK) contains tools that can be used by IT Pros to deploy Windows. See the following topics: - -- [What's new in ADK kits and tools](https://docs.microsoft.com/windows-hardware/get-started/what-s-new-in-kits-and-tools) -- [Windows ADK for Windows 10 scenarios for IT Pros](windows-adk-scenarios-for-it-pros.md) - - -## Testing and validation guidance - -### Windows 10 deployment proof of concept (PoC) - -The Windows 10 PoC guide enables you to test Windows 10 deployment in a virtual environment and become familiar with deployment tools such as MDT and Configuration Manager. The PoC guide provides step-by-step instructions for installing and using Hyper-V to create a virtual lab environment. The guide makes extensive use of Windows PowerShell to streamline each phase of the installation and setup. - -For more information, see the following guides: - -- [Step by step guide: Configure a test lab to deploy Windows 10](windows-10-poc.md) -- [Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit](windows-10-poc-mdt.md) -- [Deploy Windows 10 in a test lab using System Center Configuration Manager](windows-10-poc-sc-config-mgr.md) - - -## Troubleshooting guidance - -[Resolve Windows 10 upgrade errors](upgrade/resolve-windows-10-upgrade-errors.md) was published in October of 2016 and will continue to be updated with new fixes. The topic provides a detailed explanation of the Windows 10 upgrade process and instructions on how to locate, interpret, and resolve specific errors that can be encountered during the upgrade process. - - -## Online content change history - -The following topics provide a change history for Windows 10 ITPro TechNet library content related to deploying and using Windows 10. - -[Change history for Deploy Windows 10](change-history-for-deploy-windows-10.md) -
[Change history for Access Protection](/windows/access-protection/change-history-for-access-protection) -
[Change history for Device Security](/windows/device-security/change-history-for-device-security) -
[Change history for Threat Protection](/windows/threat-protection/change-history-for-threat-protection) - - -## Related topics - -[Overview of Windows as a service](update/waas-overview.md) -
[Windows 10 deployment considerations](planning/windows-10-deployment-considerations.md) -
[Windows 10 release information](https://docs.microsoft.com/windows/windows-10/release-information) -
[Windows 10 Specifications & Systems Requirements](https://www.microsoft.com/en-us/windows/windows-10-specifications) -
[Windows 10 upgrade paths](upgrade/windows-10-upgrade-paths.md) -
[Windows 10 deployment tools](windows-deployment-scenarios-and-tools.md) +--- +title: What's new in Windows 10 deployment +ms.reviewer: +manager: laurawi +ms.author: greglin +description: Changes and new features related to Windows 10 deployment +keywords: deployment, automate, tools, configure, news +ms.mktglfcycl: deploy +ms.localizationpriority: medium +ms.prod: w10 +ms.sitesec: library +ms.pagetype: deploy +audience: itpro +author: greg-lindsay +ms.topic: article +--- + +# What's new in Windows 10 deployment + +**Applies to** +- Windows 10 + +## In this topic + +This topic provides an overview of new solutions and online content related to deploying Windows 10 in your organization. + +- For an all-up overview of new features in Windows 10, see [What's new in Windows 10](https://docs.microsoft.com/windows/whats-new/index). +- For a detailed list of changes to Windows 10 ITPro TechNet library content, see [Online content change history](#online-content-change-history). + +## Recent additions to this page + +[SetupDiag](#setupdiag) 1.6.0 is released.
+The [Windows ADK for Windows 10, version 1903](https://docs.microsoft.com/windows-hardware/get-started/adk-install) is available.
+New [Windows Autopilot](#windows-autopilot) content is available.
+[Windows 10 Subscription Activation](#windows-10-subscription-activation) now supports Windows 10 Education. + +## The Modern Desktop Deployment Center + +The [Modern Desktop Deployment Center](https://docs.microsoft.com/microsoft-365/enterprise/desktop-deployment-center-home) has launched with tons of content to help you with large-scale deployment of Windows 10 and Office 365 ProPlus. + +## Microsoft 365 + +Microsoft 365 is a new offering from Microsoft that combines +- Windows 10 +- Office 365 +- Enterprise Mobility and Security (EMS). + +See [Deploy Windows 10 with Microsoft 365](deploy-m365.md) for an overview, which now includes a link to download a nifty [M365 Enterprise poster](deploy-m365.md#m365-enterprise-poster). + +## Windows 10 servicing and support + +- [**Delivery Optimization**](https://docs.microsoft.com/windows/deployment/update/waas-delivery-optimization): Improved Peer Efficiency for enterprises and educational institutions with complex networks is enabled with of [new policies](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-deliveryoptimization). This now supports Office 365 ProPlus updates, and Intune content, with System Center Configuration Manager content coming soon! +- [**Automatic Restart Sign-on (ARSO)**](https://docs.microsoft.com/windows-insider/at-work-pro/wip-4-biz-whats-new#automatic-restart-and-sign-on-arso-for-enterprises-build-18305): Windows will automatically logon as the user and lock their device in order to complete the update, ensuring that when the user returns and unlocks the device, the update will be completed. +- [**Windows Update for Business**](https://techcommunity.microsoft.com/t5/Windows-IT-Pro-Blog/Windows-Update-for-Business-and-the-retirement-of-SAC-T/ba-p/339523): There will now be a single, common start date for phased deployments (no more SAC-T designation). In addition, there will a new notification and reboot scheduling experience for end users, the ability to enforce update installation and reboot deadlines, and the ability to provide end user control over reboots for a specific time period. +- **Update rollback improvements**: You can now automatically recover from startup failures by removing updates if the startup failure was introduced after the installation of recent driver or quality updates. When a device is unable to start up properly after the recent installation of Quality of driver updates, Windows will now automatically uninstall the updates to get the device back up and running normally. +- **Pause updates**: We have extended the ability to pause updates for both feature and monthly updates. This extension ability is for all editions of Windows 10, including Home. You can pause both feature and monthly updates for up to 35 days (seven days at a time, up to five times). Once the 35-day pause period is reached, you will need to update your device before pausing again. +- **Improved update notifications**: When there’s an update requiring you to restart your device, you’ll see a colored dot on the Power button in the Start menu and on the Windows icon in your taskbar. +- **Intelligent active hours**: To further enhance active hours, users will now have the option to let Windows Update intelligently adjust active hours based on their device-specific usage patterns. You must enable the intelligent active hours feature for the system to predict device-specific usage patterns. +- **Improved update orchestration to improve system responsiveness**: This feature will improve system performance by intelligently coordinating Windows updates and Microsoft Store updates, so they occur when users are away from their devices to minimize disruptions. + +Microsoft previously announced that we are [extending support](https://www.microsoft.com/microsoft-365/blog/2018/09/06/helping-customers-shift-to-a-modern-desktop) for Windows 10 Enterprise and Windows 10 Education editions to 30 months from the version release date. This includes all past versions and future versions that are targeted for release in September (versions ending in 09, ex: 1809). Future releases that are targeted for release in March (versions ending in 03, ex: 1903) will continue to be supported for 18 months from their release date. All releases of Windows 10 Home, Windows 10 Pro, and Office 365 ProPlus will continue to be supported for 18 months (there is no change for these editions). These support policies are summarized in the table below. + +![Support lifecycle](images/support-cycle.png) + +## Windows 10 Enterprise upgrade + +Windows 10 version 1703 includes a Windows 10 Enterprise E3 and E5 benefit to Microsoft customers with Enterprise Agreements (EA) or Microsoft Products & Services Agreements (MPSA). These customers can now subscribe users to Windows 10 Enterprise E3 or E5 and activate their subscriptions on up to five devices. Virtual machines can also be activated. For more information, see [Windows 10 Enterprise Subscription Activation](windows-10-subscription-activation.md). + +Windows 10 Enterprise E3 launched in the Cloud Solution Provider (CSP) channel on September 1, 2016. Previously, only organizations with a Microsoft Volume Licensing Agreement could deploy Windows 10 Enterprise to their users. With Windows 10 Enterprise E3 in CSP, small and medium-sized organizations can more easily take advantage of Windows 10 Enterprise features. + +For more information, see [Windows 10 Enterprise E3 in CSP](windows-10-enterprise-e3-overview.md) + + +## Deployment solutions and tools + +### Windows Autopilot + +[Windows Autopilot](https://docs.microsoft.com/windows/deployment/windows-autopilot/windows-autopilot) streamlines and automates the process of setting up and configuring new devices, with minimal interaction required from the end user. You can also use Windows Autopilot to reset, repurpose and recover devices. + +The following Windows Autopilot features are available in Windows 10, version 1903 and later: + +- [Windows Autopilot for white glove deployment](https://docs.microsoft.com/windows/deployment/windows-autopilot/white-glove) is new in Windows 10, version 1903. "White glove" deployment enables partners or IT staff to pre-provision devices so they are fully configured and business ready for your users. +- The Intune [enrollment status page](https://docs.microsoft.com/intune/windows-enrollment-status) (ESP) now tracks Intune Management Extensions​. +- [Cortana voiceover](https://docs.microsoft.com/windows-hardware/customize/desktop/cortana-voice-support) and speech recognition during OOBE is disabled by default for all Windows 10 Pro Education, and Enterprise SKUs. +- Windows Autopilot is self-updating during OOBE. Starting with the Windows 10, version 1903 Autopilot functional and critical updates will begin downloading automatically during OOBE. +- Windows Autopilot will set the [diagnostics data](https://docs.microsoft.com/windows/privacy/windows-diagnostic-data) level to Full on Windows 10 version 1903 and later during OOBE. + +### Windows 10 Subscription Activation + +Windows 10 Education support has been added to Windows 10 Subscription Activation. + +With Windows 10, version 1903, you can step-up from Windows 10 Pro Education to the enterprise-grade edition for educational institutions – Windows 10 Education. For more information, see [Windows 10 Subscription Activation](https://docs.microsoft.com/windows/deployment/windows-10-subscription-activation). + +### SetupDiag + +[SetupDiag](upgrade/setupdiag.md) is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful. + +SetupDiag version 1.4.1 was released on 5/17/2019. + +### Upgrade Readiness + +The Upgrade Readiness tool moved from public preview to general availability on March 2, 2017. + +Upgrade Readiness helps you ensure that applications and drivers are ready for a Windows 10 upgrade. The solution provides up-to-date application and driver inventory, information about known issues, troubleshooting guidance, and per-device readiness and tracking details. + +The development of Upgrade Readiness has been heavily influenced by input from the community the development of new features is ongoing. To begin using Upgrade Readiness, add it to an existing Operation Management Suite (OMS) workspace or sign up for a new OMS workspace with the Upgrade Readiness solution enabled. + +For more information about Upgrade Readiness, see the following topics: + +- [Windows Analytics blog](https://aka.ms/blog/WindowsAnalytics/) +- [Manage Windows upgrades with Upgrade Readiness](upgrade/manage-windows-upgrades-with-upgrade-readiness.md) + + +### Update Compliance + +Update Compliance helps you to keep Windows 10 devices in your organization secure and up-to-date. + +Update Compliance is a solution built using OMS Logs and Analytics that provides information about installation status of monthly quality and feature updates. Details are provided about the deployment progress of existing updates and the status of future updates. Information is also provided about devices that might need attention to resolve issues. + +For more information about Update Compliance, see [Monitor Windows Updates with Update Compliance](update/update-compliance-monitor.md). + +### Device Health + +Device Health is the newest Windows Analytics solution that complements the existing Upgrade Readiness and Update Compliance solutions by helping to identify devices crashes and the cause. Device drivers that are causing crashes are identified along with alternative drivers that might reduce the number of crashes. Windows Information Protection misconfigurations are also identified. For more information, see [Monitor the health of devices with Device Health](update/device-health-monitor.md) + +### MBR2GPT + +MBR2GPT.EXE converts a disk from Master Boot Record (MBR) to GUID Partition Table (GPT) partition style without modifying or deleting data on the disk. Previously, it was necessary to image, then wipe and reload a disk to change from MBR format to GPT. + +There are many benefits to converting the partition style of a disk to GPT, including the use of larger disk partitions, added data reliability, and faster boot and shutdown speeds. The GPT format also enables you to use the Unified Extensible Firmware Interface (UEFI) which replaces the Basic Input/Output System (BIOS) firmware interface. Security features of Windows 10 that require UEFI mode include: Secure Boot, Early Launch Anti-malware (ELAM) driver, Windows Trusted Boot, Measured Boot, Device Guard, Credential Guard, and BitLocker Network Unlock. + +For more information, see [MBR2GPT.EXE](mbr-to-gpt.md). + + +### Microsoft Deployment Toolkit (MDT) + +MDT build 8456 (12/19/2018) is available, including support for Windows 10, version 1809, and Windows Server 2019. + +For more information about MDT, see the [MDT resource page](https://docs.microsoft.com/sccm/mdt/). + + +### Windows Assessment and Deployment Kit (ADK) + +The Windows Assessment and Deployment Kit (Windows ADK) contains tools that can be used by IT Pros to deploy Windows. See the following topics: + +- [What's new in ADK kits and tools](https://docs.microsoft.com/windows-hardware/get-started/what-s-new-in-kits-and-tools) +- [Windows ADK for Windows 10 scenarios for IT Pros](windows-adk-scenarios-for-it-pros.md) + + +## Testing and validation guidance + +### Windows 10 deployment proof of concept (PoC) + +The Windows 10 PoC guide enables you to test Windows 10 deployment in a virtual environment and become familiar with deployment tools such as MDT and Configuration Manager. The PoC guide provides step-by-step instructions for installing and using Hyper-V to create a virtual lab environment. The guide makes extensive use of Windows PowerShell to streamline each phase of the installation and setup. + +For more information, see the following guides: + +- [Step by step guide: Configure a test lab to deploy Windows 10](windows-10-poc.md) +- [Deploy Windows 10 in a test lab using Microsoft Deployment Toolkit](windows-10-poc-mdt.md) +- [Deploy Windows 10 in a test lab using System Center Configuration Manager](windows-10-poc-sc-config-mgr.md) + + +## Troubleshooting guidance + +[Resolve Windows 10 upgrade errors](upgrade/resolve-windows-10-upgrade-errors.md) was published in October of 2016 and will continue to be updated with new fixes. The topic provides a detailed explanation of the Windows 10 upgrade process and instructions on how to locate, interpret, and resolve specific errors that can be encountered during the upgrade process. + + +## Online content change history + +The following topics provide a change history for Windows 10 ITPro TechNet library content related to deploying and using Windows 10. + +[Change history for Deploy Windows 10](change-history-for-deploy-windows-10.md) +
[Change history for Access Protection](/windows/access-protection/change-history-for-access-protection) +
[Change history for Device Security](/windows/device-security/change-history-for-device-security) +
[Change history for Threat Protection](/windows/threat-protection/change-history-for-threat-protection) + + +## Related topics + +[Overview of Windows as a service](update/waas-overview.md) +
[Windows 10 deployment considerations](planning/windows-10-deployment-considerations.md) +
[Windows 10 release information](https://docs.microsoft.com/windows/windows-10/release-information) +
[Windows 10 Specifications & Systems Requirements](https://www.microsoft.com/en-us/windows/windows-10-specifications) +
[Windows 10 upgrade paths](upgrade/windows-10-upgrade-paths.md) +
[Windows 10 deployment tools](windows-deployment-scenarios-and-tools.md) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 355c0da246..b413218f3d 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -28,7 +28,8 @@ ms.topic: article ## About SetupDiag -Current version of SetupDiag: 1.5.0.0 +Current version of SetupDiag: 1.6.0.0 +>Always be sure to run the most recent version of SetupDiag, so that can access new functionality and fixes to known issues. SetupDiag is a standalone diagnostic tool that can be used to obtain details about why a Windows 10 upgrade was unsuccessful. @@ -147,7 +148,6 @@ SetupDiag.exe /Output:C:\SetupDiag\Dumpdebug.log /LogsPath:D:\Dump ## Known issues 1. Some rules can take a long time to process if the log files involved are large. -2. If the failing computer is opted into the Insider program and getting regular pre-release updates, or an update is already pending on the computer when SetupDiag is run, it can encounter problems trying to open these log files. This will likely cause a failure to determine a root cause. In this case, try gathering the log files and running SetupDiag in offline mode. ## Sample output @@ -157,7 +157,7 @@ The following is an example where SetupDiag is run in offline mode. ``` D:\SetupDiag>SetupDiag.exe /output:c:\setupdiag\result.xml /logspath:D:\Tests\Logs\f55be736-beed-4b9b-aedf-c133536c946e /format:xml -SetupDiag v1.5.0.0 +SetupDiag v1.6.0.0 Copyright (c) Microsoft Corporation. All rights reserved. Searching for setup logs... @@ -318,55 +318,68 @@ Each rule name and its associated unique rule identifier are listed with a descr ## Release notes +08/08/2019 - SetupDiag v1.6.0.0 is released with 60 rules, as a standalone tool available from the Download Center. + - Log detection performance is improved. What used to take up to a minute should take around 10 seconds or less. + - Added Setup Operation and Setup Phase information to both the results log and the registry information. + - This is the last Operation and Phase that Setup was in when the failure occurred. + - Added detailed Setup Operation and Setup Phase information (and timing) to output log when /verbose is specified. + - Note, if the issue found is a compat block, no Setup Operation or Phase info exists yet and therefore won’t be available. + - Added more info to the Registry output. + - Detailed ‘FailureData’ info where available. Example: “AppName = MyBlockedApplication” or “DiskSpace = 6603” (in MB) + - “Key = Value” data specific to the failure found. + - Added ‘UpgradeStartTime’, ‘UpgradeEndTime’ and ‘UpgradeElapsedTime’ + - Added ‘SetupDiagVersion’, ‘DateTime’ (to indicate when SetupDiag was executed on the system), ‘TargetOSVersion’, ‘HostOSVersion’ and more… + + 06/19/2019 - SetupDiag v1.5.0.0 is released with 60 rules, as a standalone tool available from the Download Center. -- All date and time outputs are updated to localized format per user request. -- Added setup Operation and Phase information to /verbose log. -- Added last Setup Operation and last Setup Phase information to most rules where it make sense (see new output below). -- Performance improvement in searching setupact.logs to determine correct log to parse. -- Added SetupDiag version number to text report (xml and json always had it). -- Added "no match" reports for xml and json per user request. -- Formatted Json output for easy readability. -- Performance improvements when searching for setup logs; this should be much faster now. -- Added 7 new rules: PlugInComplianceBlock, PreReleaseWimMountDriverFound, WinSetupBootFilterFailure, WimMountDriverIssue, DISMImageSessionFailure, FindEarlyDownlevelError, and FindSPFatalError. See the [Rules](#rules) section above for more information. -- Diagnostic information is now output to the registry at **HKLM\SYSTEM\Setup\MoSetup\Volatile\SetupDiag** - - The **/AddReg** command was added to toggle registry output. This setting is off by default for offline mode, and on by default for online mode. The command has no effect for online mode and enables registry output for offline mode. - - This registry key is deleted as soon as SetupDiag is run a second time, and replaced with current data, so it’s always up to date. - - This registry key also gets deleted when a new update instance is invoked. - - For an example, see [Sample registry key](#sample-registry-key). + - All date and time outputs are updated to localized format per user request. + - Added setup Operation and Phase information to /verbose log. + - Added last Setup Operation and last Setup Phase information to most rules where it make sense (see new output below). + - Performance improvement in searching setupact.logs to determine correct log to parse. + - Added SetupDiag version number to text report (xml and json always had it). + - Added "no match" reports for xml and json per user request. + - Formatted Json output for easy readability. + - Performance improvements when searching for setup logs; this should be much faster now. + - Added 7 new rules: PlugInComplianceBlock, PreReleaseWimMountDriverFound, WinSetupBootFilterFailure, WimMountDriverIssue, DISMImageSessionFailure, FindEarlyDownlevelError, and FindSPFatalError. See the [Rules](#rules) section above for more information. + - Diagnostic information is now output to the registry at **HKLM\SYSTEM\Setup\MoSetup\Volatile\SetupDiag** + - The **/AddReg** command was added to toggle registry output. This setting is off by default for offline mode, and on by default for online mode. The command has no effect for online mode and enables registry output for offline mode. + - This registry key is deleted as soon as SetupDiag is run a second time, and replaced with current data, so it’s always up to date. + - This registry key also gets deleted when a new update instance is invoked. + - For an example, see [Sample registry key](#sample-registry-key). 05/17/2019 - SetupDiag v1.4.1.0 is released with 53 rules, as a standalone tool available from the Download Center. -- This release adds the ability to find and diagnose reset and recovery failures (Push Button Reset). + - This release dds the ability to find and diagnose reset and recovery failures (Push Button Reset). 12/18/2018 - SetupDiag v1.4.0.0 is released with 53 rules, as a standalone tool available from the Download Center. -- This release includes major improvements in rule processing performance: ~3x faster rule processing performance! - - The FindDownlevelFailure rule is up to 10x faster. -- New rules have been added to analyze failures upgrading to Windows 10 version 1809. -- A new help link is available for resolving servicing stack failures on the down-level OS when the rule match indicates this type of failure. -- Removed the need to specify /Mode parameter. Now if you specify /LogsPath, it automatically assumes offline mode. -- Some functional and output improvements were made for several rules. + - This release includes major improvements in rule processing performance: ~3x faster rule processing performance! + - The FindDownlevelFailure rule is up to 10x faster. + - New rules have been added to analyze failures upgrading to Windows 10 version 1809. + - A new help link is available for resolving servicing stack failures on the down-level OS when the rule match indicates this type of failure. + - Removed the need to specify /Mode parameter. Now if you specify /LogsPath, it automatically assumes offline mode. + - Some functional and output improvements were made for several rules. 07/16/2018 - SetupDiag v1.3.1 is released with 44 rules, as a standalone tool available from the Download Center. -- This release fixes a problem that can occur when running SetupDiag in online mode on a computer that produces a setupmem.dmp file, but does not have debugger binaries installed. + - This release fixes a problem that can occur when running SetupDiag in online mode on a computer that produces a setupmem.dmp file, but does not have debugger binaries installed. 07/10/2018 - SetupDiag v1.30 is released with 44 rules, as a standalone tool available from the Download Center. -- Bug fix for an over-matched plug-in rule. The rule will now correctly match only critical (setup failure) plug-in issues. -- New feature: Ability to output logs in JSON and XML format. - - Use "/Format:xml" or "/Format:json" command line parameters to specify the new output format. See [sample logs](#sample-logs) at the bottom of this topic. - - If the “/Format:xml” or “/Format:json” parameter is omitted, the log output format will default to text. -- New Feature: Where possible, specific instructions are now provided in rule output to repair the identified error. For example, instructions are provided to remediate known blocking issues such as uninstalling an incompatible app or freeing up space on the system drive. -- 3 new rules added: AdvancedInstallerFailed, MigrationAbortedDueToPluginFailure, DISMAddPackageFailed. + - Bug fix for an over-matched plug-in rule. The rule will now correctly match only critical (setup failure) plug-in issues. + - New feature: Ability to output logs in JSON and XML format. + - Use "/Format:xml" or "/Format:json" command line parameters to specify the new output format. See [sample logs](#sample-logs) at the bottom of this topic. + - If the “/Format:xml” or “/Format:json” parameter is omitted, the log output format will default to text. + - New Feature: Where possible, specific instructions are now provided in rule output to repair the identified error. For example, instructions are provided to remediate known blocking issues such as uninstalling an incompatible app or freeing up space on the system drive. + - 3 new rules added: AdvancedInstallerFailed, MigrationAbortedDueToPluginFailure, DISMAddPackageFailed. 05/30/2018 - SetupDiag v1.20 is released with 41 rules, as a standalone tool available from the Download Center. -- Fixed a bug in device install failure detection in online mode. -- Changed SetupDiag to work without an instance of setupact.log. Previously, SetupDiag required at least one setupact.log to operate. This change enables the tool to analyze update failures that occur prior to calling SetupHost. -- Telemetry is refactored to only send the rule name and GUID (or “NoRuleMatched” if no rule is matched) and the Setup360 ReportId. This change assures data privacy during rule processing. + - Fixed a bug in device install failure detection in online mode. + - Changed SetupDiag to work without an instance of setupact.log. Previously, SetupDiag required at least one setupact.log to operate. This change enables the tool to analyze update failures that occur prior to calling SetupHost. + - Telemetry is refactored to only send the rule name and GUID (or “NoRuleMatched” if no rule is matched) and the Setup360 ReportId. This change assures data privacy during rule processing. 05/02/2018 - SetupDiag v1.10 is released with 34 rules, as a standalone tool available from the Download Center. -- A performance enhancment has been added to result in faster rule processing. -- Rules output now includes links to support articles, if applicable. -- SetupDiag now provides the path and name of files that it is processing. -- You can now run SetupDiag by simply clicking on it and then examining the output log file. -- An output log file is now always created, whether or not a rule was matched. + - A performance enhancment has been added to result in faster rule processing. + - Rules output now includes links to support articles, if applicable. + - SetupDiag now provides the path and name of files that it is processing. + - You can now run SetupDiag by simply clicking on it and then examining the output log file. + - An output log file is now always created, whether or not a rule was matched. 03/30/2018 - SetupDiag v1.00 is released with 26 rules, as a standalone tool available from the Download Center. @@ -408,7 +421,7 @@ Refer to https://docs.microsoft.com/windows/deployment/upgrade/upgrade-error-cod ```xml - 1.5.0.0 + 1.6.0.0 FindSPFatalError A4028172-1B09-48F8-AD3B-86CDD7D55852 @@ -459,7 +472,7 @@ Refer to "https://docs.microsoft.com/windows/desktop/Debug/system-error-codes" f ``` { - "Version":"1.5.0.0", + "Version":"1.6.0.0", "ProfileName":"FindSPFatalError", "ProfileGuid":"A4028172-1B09-48F8-AD3B-86CDD7D55852", "SystemInfo":{ diff --git a/windows/release-information/resolved-issues-windows-10-1607.yml b/windows/release-information/resolved-issues-windows-10-1607.yml index bf1e899bff..08b49123c4 100644 --- a/windows/release-information/resolved-issues-windows-10-1607.yml +++ b/windows/release-information/resolved-issues-windows-10-1607.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: " + @@ -52,10 +53,7 @@ sections: - - -
SummaryOriginating updateStatusDate resolved
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 14393.3144

August 13, 2019
KB4512517		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		August 13, 2019
10:00 AM PT
Internet Explorer 11 and apps using the WebBrowser control may fail to render
JavaScript may fail to render as expected in Internet Explorer 11 and in apps using JavaScript or the WebBrowser control.

See details >		OS Build 14393.3085

July 09, 2019
KB4507460		Resolved
KB4512517		August 13, 2019
10:00 AM PT
End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system will stop working and a blue screen may appear at startup.

See details >		OS Build 14393.2879

March 19, 2019
KB4489889		Resolved
KB4493470		April 09, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >		OS Build 14393.2724

January 08, 2019
KB4480961		Resolved
KB4493470		April 09, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

See details >		OS Build 14393.2791

February 12, 2019
KB4487026		Resolved
KB4489882		March 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

See details >		OS Build 14393.2791

February 12, 2019
KB4487026		Resolved
KB4487006		February 19, 2019
02:00 PM PT
First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >		OS Build 14393.2759

January 17, 2019
KB4480977		Resolved
KB4487006		February 19, 2019
02:00 PM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		OS Build 14393.2848

March 12, 2019
KB4489882		Resolved
KB4493473		April 25, 2019
02:00 PM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

See details >		OS Build 14393.2791

February 12, 2019
KB4487026		Resolved
KB4487006		February 19, 2019
02:00 PM PT
Issue hosting multiple terminal server sessions and a user logs off on Windows Server
In some cases, Windows Server will stop working and restart when hosting multiple terminal server sessions and a user logs off.

See details >		OS Build 14393.2828

February 19, 2019
KB4487006		Resolved
KB4489882		March 12, 2019
10:00 AM PT
" @@ -82,6 +80,7 @@ sections: - type: markdown text: " + @@ -139,8 +138,6 @@ sections:
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 KB4503267 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 KB4512495.

Back to top		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved
KB4512495		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507459. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512517. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Internet Explorer 11 and apps using the WebBrowser control may fail to render
Internet Explorer 11 may fail to render some JavaScript after installing KB4507460. You may also have issues with apps using JavaScript or the WebBrowser control, such as the present PowerPoint feature of Skype Meeting Broadcast.

Affected platforms:
  • Client: Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server 2016
Resolution: This issue was resolved in KB4512517.

Back to top		OS Build 14393.3085

July 09, 2019
KB4507460		Resolved
KB4512517		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 26, 2019
04:58 PM PT
- -
DetailsOriginating updateStatusHistory
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. 
 
For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. 
 
Affected platforms:  
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: 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 is resolved in KB4493470. 

Back to top		OS Build 14393.2791

February 12, 2019
KB4487026		Resolved
KB4493470		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487026, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue is resolved in KB4489882.

Back to top		OS Build 14393.2791

February 12, 2019
KB4487026		Resolved
KB4489882		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
After installing KB4487026, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487006.

Back to top		OS Build 14393.2791

February 12, 2019
KB4487026		Resolved
KB4487006		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4487006.

Back to top		OS Build 14393.2791

February 12, 2019
KB4487026		Resolved
KB4487006		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
Issue hosting multiple terminal server sessions and a user logs off on Windows Server
In some cases, Windows Server will stop working and restart when hosting multiple terminal server sessions and a user logs off. The faulting driver is win32kbase.sys.

Affected platforms:
  • Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
Resolution: This issue is resolved in KB4489882.

Back to top		OS Build 14393.2828

February 19, 2019
KB4487006		Resolved
KB4489882		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 19, 2019
02:00 PM PT
" @@ -152,7 +149,6 @@ sections: -
DetailsOriginating updateStatusHistory
Internet Explorer 11 authentication issue with multiple concurrent logons
After installing KB4480961, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
  • Cache size and location show zero or empty.
  • Keyboard shortcuts may not work properly.
  • Webpages may intermittently fail to load or render correctly.
  • Issues with credential prompts.
  • Issues when downloading files.
Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1
Resolution: This issue was resolved in KB4493470.

Back to top		OS Build 14393.2724

January 08, 2019
KB4480961		Resolved
KB4493470		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding
After installing KB4480961, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue was resolved in KB4493470.

Back to top		OS Build 14393.2724

January 08, 2019
KB4480961		Resolved
KB4493470		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480977, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: 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 is resolved in KB4487006.

Back to top		OS Build 14393.2759

January 17, 2019
KB4480977		Resolved
KB4487006		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 17, 2019
02:00 PM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1703.yml b/windows/release-information/resolved-issues-windows-10-1703.yml index 89d2b4a9f4..22ddb295df 100644 --- a/windows/release-information/resolved-issues-windows-10-1703.yml +++ b/windows/release-information/resolved-issues-windows-10-1703.yml @@ -45,10 +45,7 @@ sections:
End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.

See details >OS Build 15063.1716

March 19, 2019
KB4489888Resolved
KB4493474April 09, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >OS Build 15063.1563

January 08, 2019
KB4480973Resolved
KB4493474April 09, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

See details >OS Build 15063.1659

February 19, 2019
KB4487011Resolved
KB4489871March 12, 2019
10:00 AM PT -
Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

See details >OS Build 15063.1631

February 12, 2019
KB4487020Resolved
KB4487011February 19, 2019
02:00 PM PT -
First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >OS Build 15063.1596

January 15, 2019
KB4480959Resolved
KB4487011February 19, 2019
02:00 PM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >OS Build 15063.1689

March 12, 2019
KB4489871Resolved
KB4493436April 25, 2019
02:00 PM PT -
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

See details >OS Build 15063.1631

February 12, 2019
KB4487020Resolved
KB4487011February 19, 2019
02:00 PM PT " @@ -118,8 +115,6 @@ sections: - -
DetailsOriginating updateStatusHistory
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. 
 
For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. 
 
Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: 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 is resolved in KB4493474. 

Back to top		OS Build 15063.1631

February 12, 2019
KB4487020		Resolved
KB4493474		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487011, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue is resolved in KB4489871.

Back to top		OS Build 15063.1659

February 19, 2019
KB4487011		Resolved
KB4489871		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 19, 2019
02:00 PM PT
Internet Explorer may fail to load images
After installing KB4487020, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487011.

Back to top		OS Build 15063.1631

February 12, 2019
KB4487020		Resolved
KB4487011		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4487011.

Back to top		OS Build 15063.1631

February 12, 2019
KB4487020		Resolved
KB4487011		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
" @@ -129,6 +124,5 @@ sections: text: " -
DetailsOriginating updateStatusHistory
MSXML6 may cause applications to stop responding
After installing KB4480973, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue was resolved in KB4493474.

Back to top		OS Build 15063.1563

January 08, 2019
KB4480973		Resolved
KB4493474		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480959, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: 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 is resolved in KB4487011.

Back to top		OS Build 15063.1596

January 15, 2019
KB4480959		Resolved
KB4487011		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 15, 2019
10:00 AM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1709.yml b/windows/release-information/resolved-issues-windows-10-1709.yml index 876d623cf2..9bf77f7d45 100644 --- a/windows/release-information/resolved-issues-windows-10-1709.yml +++ b/windows/release-information/resolved-issues-windows-10-1709.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: " + @@ -46,9 +47,6 @@ sections: - - -
SummaryOriginating updateStatusDate resolved
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved
KB4512494		August 16, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 16299.1331

August 13, 2019
KB4512516		Resolved
KB4512494		August 16, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved External
August 09, 2019
07:03 PM PT
End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.

See details >		OS Build 16299.1059

March 19, 2019
KB4489890		Resolved
KB4493441		April 09, 2019
10:00 AM PT
MSXML6 causes applications to stop responding if an exception was thrown
MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >		OS Build 16299.904

January 08, 2019
KB4480978		Resolved
KB4493441		April 09, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

See details >		OS Build 16299.967

February 12, 2019
KB4486996		Resolved
KB4489886		March 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

See details >		OS Build 16299.967

February 12, 2019
KB4486996		Resolved
KB4487021		February 19, 2019
02:00 PM PT
First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >		OS Build 16299.936

January 15, 2019
KB4480967		Resolved
KB4487021		February 19, 2019
02:00 PM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

See details >		OS Build 16299.967

February 12, 2019
KB4486996		Resolved
KB4487021		February 19, 2019
02:00 PM PT
Stop error when attempting to start SSH from WSL
A stop error occurs when attempting to start Secure Shell from Windows Subsystem for Linux with agent forwarding using a command line switch (ssh –A) or a configuration setting.

See details >		OS Build 16299.1029

March 12, 2019
KB4489886		Resolved
KB4493441		April 09, 2019
10:00 AM PT
" @@ -75,6 +73,7 @@ sections: - 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 KB4503284 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 KB4512494.

Back to top		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved
KB4512494		Resolved:
August 16, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507465. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512516. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
@@ -128,8 +127,6 @@ sections: - -
DetailsOriginating updateStatusHistory
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. 
 
For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. 
 
Affected platforms:  
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: 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 is resolved in KB4493441. 

Back to top		OS Build 16299.967

February 12, 2019
KB4486996		Resolved
KB4493441		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4486996, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue is resolved in KB4489886.

Back to top		OS Build 16299.967

February 12, 2019
KB4486996		Resolved
KB4489886		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
After installing KB4486996, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487021.

Back to top		OS Build 16299.967

February 12, 2019
KB4486996		Resolved
KB4487021		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4487021.

Back to top		OS Build 16299.967

February 12, 2019
KB4486996		Resolved
KB4487021		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
" @@ -139,6 +136,5 @@ sections: text: " -
DetailsOriginating updateStatusHistory
MSXML6 causes applications to stop responding if an exception was thrown
After installing KB4480978, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue is resolved in KB4493441.

Back to top		OS Build 16299.904

January 08, 2019
KB4480978		Resolved
KB4493441		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480967, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: 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 is resolved in KB4487021.

Back to top		OS Build 16299.936

January 15, 2019
KB4480967		Resolved
KB4487021		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 15, 2019
10:00 AM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1803.yml b/windows/release-information/resolved-issues-windows-10-1803.yml index c94998225d..b3059b9fe8 100644 --- a/windows/release-information/resolved-issues-windows-10-1803.yml +++ b/windows/release-information/resolved-issues-windows-10-1803.yml @@ -32,6 +32,8 @@ sections: - type: markdown text: " + + @@ -44,10 +46,7 @@ sections: - - -
SummaryOriginating updateStatusDate resolved
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17134.950

August 13, 2019
KB4512501		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved External
August 09, 2019
07:03 PM PT
Difficulty connecting to some iSCSI-based SANs
Devices may have difficulty connecting to some Storage Area Network (SAN) devices that leverage iSCSI.

See details >		OS Build 17134.799

May 21, 2019
KB4499183		Resolved
KB4509478		June 26, 2019
04:00 PM PT
End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.

See details >		OS Build 17134.677

March 19, 2019
KB4489894		Resolved
KB4493464		April 09, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >		OS Build 17134.523

January 08, 2019
KB4480966		Resolved
KB4493464		April 09, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.

See details >		OS Build 17134.590

February 12, 2019
KB4487017		Resolved
KB4489868		March 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

See details >		OS Build 17134.590

February 12, 2019
KB4487017		Resolved
KB4487029		February 19, 2019
02:00 PM PT
First character of the Japanese era name not recognized
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >		OS Build 17134.556

January 15, 2019
KB4480976		Resolved
KB4487029		February 19, 2019
02:00 PM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		OS Build 17134.648

March 12, 2019
KB4489868		Resolved
KB4493437		April 25, 2019
02:00 PM PT
Cannot pin a web link on the Start menu or the taskbar
Some users cannot pin a web link on the Start menu or the taskbar.

See details >		OS Build 17134.471

December 11, 2018
KB4471324		Resolved
KB4487029		February 19, 2019
02:00 PM PT
Stop error when attempting to start SSH from WSL
A stop error occurs when attempting to start Secure Shell from Windows Subsystem for Linux with agent forwarding using a command line switch (ssh –A) or a configuration setting.

See details >		OS Build 17134.648

March 12, 2019
KB4489868		Resolved
KB4493464		April 09, 2019
10:00 AM PT
" @@ -64,6 +63,7 @@ sections: - 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
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503286) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 17134.829

June 11, 2019
KB4503286		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" @@ -73,6 +73,7 @@ sections: - 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
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507466. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512501. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
@@ -126,7 +127,6 @@ sections: -
DetailsOriginating updateStatusHistory
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. 
 
For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. 
 
Affected platforms:  
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: 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 is resolved in KB4493464. 

Back to top		OS Build 17134.590

February 12, 2019
KB4487017		Resolved
KB4493464		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487017, users may received \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files. 

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue is resolved in KB4489868.

Back to top		OS Build 17134.590

February 12, 2019
KB4487017		Resolved
KB4489868		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
After installing KB4487017, Internet Explorer may fail to load images with a backslash (\\) in their relative source path. 

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4487029. 

Back to top		OS Build 17134.590

February 12, 2019
KB4487017		Resolved
KB4487029		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
" @@ -136,15 +136,5 @@ sections: text: " - -
DetailsOriginating updateStatusHistory
MSXML6 may cause applications to stop responding
After installing KB4480966, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue was resolved in KB4493464. 

Back to top		OS Build 17134.523

January 08, 2019
KB4480966		Resolved
KB4493464		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
First character of the Japanese era name not recognized
After installing KB4480976, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: 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 is resolved in KB4487029. 

Back to top		OS Build 17134.556

January 15, 2019
KB4480976		Resolved
KB4487029		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 08, 2019
10:00 AM PT
- " - -- title: December 2018 -- items: - - type: markdown - text: " - -
DetailsOriginating updateStatusHistory
Cannot pin a web link on the Start menu or the taskbar
After installing KB4471324, some users cannot pin a web link on the Start menu or the taskbar. 

Affected platforms:
  • Client: Windows 10, version 1803
  • Server: Windows Server, version 1803
Resolution: This issue is resolved in KB4487029. 

Back to top		OS Build 17134.471

December 11, 2018
KB4471324		Resolved
KB4487029		Resolved:
February 19, 2019
02:00 PM PT

Opened:
December 11, 2018
10:00 AM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml index dc24852730..c70c55ae78 100644 --- a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml +++ b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: " + @@ -87,6 +88,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate resolved
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Resolved
KB4512534		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17763.678

August 13, 2019
KB4511553		Resolved
KB4512534		August 17, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Resolved External
August 09, 2019
07:03 PM PT
+
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 KB4503327 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 KB4512534.

Back to top		OS Build 17763.557

June 11, 2019
KB4503327		Resolved
KB4512534		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4505658. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4511553. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
diff --git a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml index 7135d3adff..b30db83a7d 100644 --- a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: " + @@ -40,17 +41,14 @@ sections: + - - - -
SummaryOriginating updateStatusDate resolved
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503292		Resolved
KB4512514		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512506		Resolved
KB4517297		August 16, 2019
02:00 PM PT
System may be unresponsive after restart with certain McAfee antivirus products
Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.

See details >		April 09, 2019
KB4493472		Resolved External
August 13, 2019
06:59 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503292		Resolved External
August 09, 2019
07:03 PM PT
Unable to access some gov.uk websites
gov.uk websites that don’t support “HSTS” may not be accessible

See details >		May 14, 2019
KB4499164		Resolved
KB4505050		May 18, 2019
02:00 PM PT
System may be unresponsive after restart if ArcaBit antivirus software installed
Devices with ArcaBit antivirus software installed may become unresponsive upon restart.

See details >		April 09, 2019
KB4493472		Resolved
May 14, 2019
01:23 PM PT
System unresponsive after restart if Sophos Endpoint Protection installed
Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

See details >		April 09, 2019
KB4493472		Resolved
May 14, 2019
01:22 PM PT
System may be unresponsive after restart if Avira antivirus software installed
Devices with Avira antivirus software installed may become unresponsive upon restart.

See details >		April 09, 2019
KB4493472		Resolved
May 14, 2019
01:21 PM PT
Authentication may fail for services after the Kerberos ticket expires
Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires.

See details >		March 12, 2019
KB4489878		Resolved
KB4499164		May 14, 2019
10:00 AM PT
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

See details >		February 12, 2019
KB4486563		Resolved
KB4493472		April 09, 2019
10:00 AM PT
Devices may not respond at login or Welcome screen if running certain Avast software
Devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software may become unresponsive after restart.

See details >		April 09, 2019
KB4493472		Resolved
April 25, 2019
02:00 PM PT
NETDOM.EXE fails to run
NETDOM.EXE fails to run and the error, “The command failed to complete successfully.” appears on screen.

See details >		March 12, 2019
KB4489878		Resolved
KB4493472		April 09, 2019
10:00 AM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		March 12, 2019
KB4489878		Resolved
KB4493472		April 09, 2019
10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

See details >		February 12, 2019
KB4486563		Resolved
KB4486565		February 19, 2019
02:00 PM PT
Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

See details >		February 12, 2019
KB4486563		Resolved
KB4486565		February 19, 2019
02:00 PM PT
First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >		January 17, 2019
KB4480955		Resolved
KB4486565		February 19, 2019
02:00 PM PT
Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.

See details >		January 08, 2019
KB4480970		Resolved
KB4493472		April 09, 2019
10:00 AM PT
Event Viewer may not show some event descriptions for network interface cards
The Event Viewer may not show some event descriptions for network interface cards (NIC).

See details >		October 18, 2018
KB4462927		Resolved
KB4489878		March 12, 2019
10:00 AM PT
Virtual machines fail to restore
Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before.

See details >		January 08, 2019
KB4480970		Resolved
KB4490511		February 19, 2019
02:00 PM PT
" @@ -71,6 +69,15 @@ sections: " +- 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 KB4503292 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 KB4512514.

Back to top		June 11, 2019
KB4503292		Resolved
KB4512514		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
+ " + - title: June 2019 - items: - type: markdown @@ -120,8 +127,6 @@ sections: text: " - -
DetailsOriginating updateStatusHistory
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. 
 
For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. 
 
Affected platforms:  
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: 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 is resolved in KB4493472. 

Back to top		February 12, 2019
KB4486563		Resolved
KB4493472		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 7 SP1 
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2 
Resolution: This issue is resolved in KB4486565.

Back to top		February 12, 2019
KB4486563		Resolved
KB4486565		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
After installing KB4486563, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1 
Resolution: This issue is resolved in KB4486565.

Back to top		February 12, 2019
KB4486563		Resolved
KB4486565		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
" @@ -130,9 +135,7 @@ sections: - type: markdown text: " - -
DetailsOriginating updateStatusHistory
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480955, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: 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 is resolved in KB4486565.

Back to top		January 17, 2019
KB4480955		Resolved
KB4486565		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 17, 2019
10:00 AM PT
Internet Explorer 11 authentication issue with multiple concurrent logons
After installing KB4480970, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
  • Cache size and location show zero or empty.
  • Keyboard shortcuts may not work properly.
  • Webpages may intermittently fail to load or render correctly.
  • Issues with credential prompts.
  • Issues when downloading files.
Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493472.

Back to top		January 08, 2019
KB4480970		Resolved
KB4493472		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
Virtual machines fail to restore
After installing KB4480970, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).”

This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.

Affected platforms: 
  • Client: Windows 8.1; Windows 7 SP1 
  • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4490511.

Back to top		January 08, 2019
KB4480970		Resolved
KB4490511		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 08, 2019
10:00 AM PT
" diff --git a/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml b/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml index 3c832e536c..cee285c22f 100644 --- a/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml +++ b/windows/release-information/resolved-issues-windows-8.1-and-windows-server-2012-r2.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: " + @@ -43,8 +44,6 @@ sections: - - @@ -52,7 +51,6 @@ sections: -
SummaryOriginating updateStatusDate resolved
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503276		Resolved
KB4512478		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512488		Resolved
KB4517298		August 16, 2019
02:00 PM PT
System may be unresponsive after restart with certain McAfee antivirus products
Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.

See details >		April 09, 2019
KB4493446		Resolved External
August 13, 2019
06:59 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503276		Resolved External
August 09, 2019
07:03 PM PT
System may be unresponsive after restart if ArcaBit antivirus software installed
Devices with ArcaBit antivirus software installed may become unresponsive upon restart.

See details >		April 09, 2019
KB4493446		Resolved
May 14, 2019
01:22 PM PT
System unresponsive after restart if Sophos Endpoint Protection installed
Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

See details >		April 09, 2019
KB4493446		Resolved
May 14, 2019
01:22 PM PT
System may be unresponsive after restart if Avira antivirus software installed
Devices with Avira antivirus software installed may become unresponsive upon restart.

See details >		April 09, 2019
KB4493446		Resolved
May 14, 2019
01:21 PM PT
Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

See details >		February 12, 2019
KB4487000		Resolved
KB4487016		February 19, 2019
02:00 PM PT
First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >		January 15, 2019
KB4480969		Resolved
KB4487016		February 19, 2019
02:00 PM PT
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

See details >		February 12, 2019
KB4487000		Resolved
KB4493446		April 09, 2019
10:00 AM PT
Devices may not respond at login or Welcome screen if running certain Avast software
Devices running Avast for Business, Avast CloudCare, and AVG Business Edition antivirus software may become unresponsive after restart.

See details >		April 09, 2019
KB4493446		Resolved
April 25, 2019
02:00 PM PT
Devices with winsock kernel client may receive error
Devices with a winsock kernel client may receive D1, FC, and other errors.

See details >		March 12, 2019
KB4489881		Resolved
KB4489893		March 19, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

See details >		February 19, 2019
KB4487016		Resolved
KB4489881		March 12, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding.
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >		January 08, 2019
KB4480963		Resolved
KB4493446		April 09, 2019
10:00 AM PT
Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.

See details >		January 08, 2019
KB4480963		Resolved
KB4493446		April 09, 2019
10:00 AM PT
Virtual machines fail to restore
Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before.

See details >		January 08, 2019
KB4480963		Resolved
KB4490512		February 19, 2019
02:00 PM PT
" @@ -73,6 +71,15 @@ sections: " +- 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 KB4503276 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 KB4512478.

Back to top		June 11, 2019
KB4503276		Resolved
KB4512478		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
+ " + - title: June 2019 - items: - type: markdown @@ -122,7 +129,6 @@ sections: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Internet Explorer may fail to load images
After installing KB4487000, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1 
Resolution: This issue is resolved in KB4487016.

Back to top		February 12, 2019
KB4487000		Resolved
KB4487016		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color.

Affected platforms 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: 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 is resolved in KB4493446.

Back to top		February 12, 2019
KB4487000		Resolved
KB4493446		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487016, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1 
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 
Resolution: This issue is resolved in KB4489881.

Back to top		February 19, 2019
KB4487016		Resolved
KB4489881		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 19, 2019
02:00 PM PT
@@ -133,9 +139,7 @@ sections: - type: markdown text: " - -
DetailsOriginating updateStatusHistory
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480969, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: 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 is resolved in KB4487016.

Back to top		January 15, 2019
KB4480969		Resolved
KB4487016		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 15, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding.
After installing KB4480963, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue is resolved in KB4493446.

Back to top		January 08, 2019
KB4480963		Resolved
KB4493446		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
Internet Explorer 11 authentication issue with multiple concurrent logons
After installing KB4480963, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
  • Cache size and location show zero or empty.
  • Keyboard shortcuts may not work properly.
  • Webpages may intermittently fail to load or render correctly.
  • Issues with credential prompts.
  • Issues when downloading files.
Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493446.

Back to top		January 08, 2019
KB4480963		Resolved
KB4493446		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
Virtual machines fail to restore
After installing KB4480963, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).”

This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.

Affected platforms: 
  • Client: Windows 8.1; Windows 7 SP1 
  • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4490512.

Back to top		January 08, 2019
KB4480963		Resolved
KB4490512		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 08, 2019
10:00 AM PT
" diff --git a/windows/release-information/resolved-issues-windows-server-2008-sp2.yml b/windows/release-information/resolved-issues-windows-server-2008-sp2.yml index 8ca80054e9..df7f82cfb2 100644 --- a/windows/release-information/resolved-issues-windows-server-2008-sp2.yml +++ b/windows/release-information/resolved-issues-windows-server-2008-sp2.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: " + @@ -39,10 +40,8 @@ sections: - -
SummaryOriginating updateStatusDate resolved
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503273		Resolved
KB4512499		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512476		Resolved
KB4517301		August 16, 2019
02:00 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503273		Resolved External
August 09, 2019
07:03 PM PT
Event Viewer may close or you may receive an error when using Custom Views
When trying to expand, view or create Custom Views in Event Viewer, you may receive an error and the app may stop responding or close.

See details >		June 11, 2019
KB4503273		Resolved
KB4503271		June 20, 2019
02:00 PM PT
System may be unresponsive after restart if Avira antivirus software installed
Devices with Avira antivirus software installed may become unresponsive upon restart.

See details >		April 09, 2019
KB4493471		Resolved
May 14, 2019
01:19 PM PT
Authentication may fail for services after the Kerberos ticket expires
Authentication may fail for services that require unconstrained delegation after the Kerberos ticket expires.

See details >		March 12, 2019
KB4489880		Resolved
KB4499149		May 14, 2019
10:00 AM PT
NETDOM.EXE fails to run
NETDOM.EXE fails to run and the error, “The command failed to complete successfully.” appears on screen.

See details >		March 12, 2019
KB4489880		Resolved
KB4493471		April 09, 2019
10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

See details >		February 12, 2019
KB4487023		Resolved
KB4487022		February 19, 2019
02:00 PM PT
First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >		January 17, 2019
KB4480974		Resolved
KB4489880		March 12, 2019
10:00 AM PT
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

See details >		February 12, 2019
KB4487023		Resolved
KB4493471		April 09, 2019
10:00 AM PT
Virtual machines fail to restore
Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before.

See details >		January 08, 2019
KB4480968		Resolved
KB4490514		February 19, 2019
02:00 PM PT
" @@ -63,6 +62,15 @@ sections: " +- 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 KB4503273 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 KB4512499.

Back to top		June 11, 2019
KB4503273		Resolved
KB4512499		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
+ " + - title: June 2019 - items: - type: markdown @@ -97,7 +105,6 @@ sections: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4487022.

Back to top		February 12, 2019
KB4487023		Resolved
KB4487022		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color.

Affected platforms 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: 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 is resolved in KB4493471.

Back to top		February 12, 2019
KB4487023		Resolved
KB4493471		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
" @@ -108,6 +115,5 @@ sections: text: " -
DetailsOriginating updateStatusHistory
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480974, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: 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 is resolved in KB4489880.

Back to top		January 17, 2019
KB4480974		Resolved
KB4489880		Resolved:
March 12, 2019
10:00 AM PT

Opened:
January 17, 2019
10:00 AM PT
Virtual machines fail to restore
After installing KB4480968, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, “Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).”

This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.

Affected platforms: 
  • Client: Windows 8.1; Windows 7 SP1 
  • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4490514.

Back to top		January 08, 2019
KB4480968		Resolved
KB4490514		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 08, 2019
10:00 AM PT
" diff --git a/windows/release-information/resolved-issues-windows-server-2012.yml b/windows/release-information/resolved-issues-windows-server-2012.yml index 7725b0bf92..4bd64240b8 100644 --- a/windows/release-information/resolved-issues-windows-server-2012.yml +++ b/windows/release-information/resolved-issues-windows-server-2012.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: " + @@ -42,13 +43,10 @@ sections: - - -
SummaryOriginating updateStatusDate resolved
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503285		Resolved
KB4512512		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512518		Resolved
KB4517302		August 16, 2019
02:00 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503285		Resolved External
August 09, 2019
07:03 PM PT
Some devices and generation 2 Hyper-V VMs may have issues installing updates
Some devices and generation 2 Hyper-V virtual machines (VMs) may have issues installing some updates when Secure Boot is enabled.

See details >		June 11, 2019
KB4503285		Resolved
KB4503295		June 21, 2019
02:00 PM PT
Layout and cell size of Excel sheets may change when using MS UI Gothic
When using the MS UI Gothic or MS PGothic fonts, the text, layout, or cell size may become narrower or wider than expected in Microsoft Excel.

See details >		April 25, 2019
KB4493462		Resolved
KB4499171		May 14, 2019
10:00 AM PT
System unresponsive after restart if Sophos Endpoint Protection installed
Devices with Sophos Endpoint Protection installed and managed by Sophos Central or Sophos Enterprise Console (SEC) may become unresponsive upon restart.

See details >		April 09, 2019
KB4493451		Resolved
May 14, 2019
01:21 PM PT
System may be unresponsive after restart if Avira antivirus software installed
Devices with Avira antivirus software installed may become unresponsive upon restart.

See details >		April 09, 2019
KB4493451		Resolved
May 14, 2019
01:19 PM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

See details >		February 12, 2019
KB4487025		Resolved
KB4487024		February 19, 2019
02:00 PM PT
First character of the Japanese era name not recognized as an abbreviation
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >		January 15, 2019
KB4480971		Resolved
KB4487024		February 19, 2019
02:00 PM PT
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

See details >		February 12, 2019
KB4487025		Resolved
KB4493451		April 09, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

See details >		February 12, 2019
KB4487025		Resolved
KB4489891		March 12, 2019
10:00 AM PT
Internet Explorer 11 authentication issue with multiple concurrent logons
Internet Explorer 11 users may encounter issues if two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine.

See details >		January 08, 2019
KB4480975		Resolved
KB4493451		April 09, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >		January 08, 2019
KB4480975		Resolved
KB4493451		April 09, 2019
10:00 AM PT
Virtual machines fail to restore
Virtual machines (VMs) may fail to restore successfully if the VM has been saved and restored once before.

See details >		January 08, 2019
KB4480975		Resolved
KB4490516		February 19, 2019
02:00 PM PT
Event Viewer may not show some event descriptions for network interface cards
The Event Viewer may not show some event descriptions for network interface cards (NIC).

See details >		September 11, 2018
KB4457135		Resolved
KB4489891		March 12, 2019
10:00 AM PT
" @@ -70,6 +68,15 @@ sections: " +- 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 KB4503285 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 KB4512512.

Back to top		June 11, 2019
KB4503285		Resolved
KB4512512		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
+ " + - title: June 2019 - items: - type: markdown @@ -115,7 +122,6 @@ sections: - type: markdown text: " -
DetailsOriginating updateStatusHistory
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4487024.

Back to top		February 12, 2019
KB4487025		Resolved
KB4487024		Resolved:
February 19, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color.

Affected platforms 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1 
  • Server: 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 is resolved in KB4493451.

Back to top		February 12, 2019
KB4487025		Resolved
KB4493451		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487025, users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue is resolved in KB4489891.

Back to top		February 12, 2019
KB4487025		Resolved
KB4489891		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
@@ -126,10 +132,8 @@ sections: - type: markdown text: " - -
DetailsOriginating updateStatusHistory
First character of the Japanese era name not recognized as an abbreviation
After installing KB4480971, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: 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 is resolved in KB4487024.

Back to top		January 15, 2019
KB4480971		Resolved
KB4487024		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 15, 2019
10:00 AM PT
Internet Explorer 11 authentication issue with multiple concurrent logons
After installing KB4480975, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to:
  • Cache size and location show zero or empty.
  • Keyboard shortcuts may not work properly.
  • Webpages may intermittently fail to load or render correctly.
  • Issues with credential prompts.
  • Issues when downloading files.
Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4493451.

Back to top		January 08, 2019
KB4480975		Resolved
KB4493451		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding
After installing KB4480975, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue is resolved in KB4493451.

Back to top		January 08, 2019
KB4480975		Resolved
KB4493451		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
Virtual machines fail to restore
After installing KB4480975, virtual machines (VM) may fail to restore successfully if the VM has been saved and restored once before. The error message is, \"Failed to restore the virtual machine state: Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. (0xC0370027).\"

This affects AMD Bulldozer Family 15h, AMD Jaguar Family 16h, and AMD Puma Family 16h (second generation) microarchitectures.

Affected platforms: 
  • Client: Windows 8.1; Windows 7 SP1 
  • Server: Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4490516.

Back to top		January 08, 2019
KB4480975		Resolved
KB4490516		Resolved:
February 19, 2019
02:00 PM PT

Opened:
January 08, 2019
10:00 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 4a6c046585..cca3c91d12 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,13 +60,13 @@ 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.

+ - @@ -96,10 +96,10 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 14393.3144

August 13, 2019
KB4512517		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		August 13, 2019
10:00 AM PT
Internet Explorer 11 and apps using the WebBrowser control may fail to render
JavaScript may fail to render as expected in Internet Explorer 11 and in apps using JavaScript or the WebBrowser control.

See details >		OS Build 14393.3085

July 09, 2019
KB4507460		Resolved
KB4512517		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved External
August 09, 2019
07:03 PM PT
Apps and scripts using the NetQueryDisplayInformation API may fail with error
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data.

See details >		OS Build 14393.3053

June 18, 2019
KB4503294		Investigating
August 01, 2019
05:00 PM PT
SCVMM cannot enumerate and manage logical switches deployed on the host
For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host.

See details >		OS Build 14393.2639

November 27, 2018
KB4467684		Resolved
KB4507459		July 16, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Mitigated
July 10, 2019
07:09 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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
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		Mitigated
February 19, 2019
10:00 AM PT
Cluster service may fail if the minimum password length is set to greater than 14
The cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters.

See details >		OS Build 14393.2639

November 27, 2018
KB4467684		Mitigated
April 25, 2019
02:00 PM PT
+ -
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 KB4503267 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 KB4512495.

Back to top		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved
KB4512495		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507459. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512517. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Internet Explorer 11 and apps using the WebBrowser control may fail to render
Internet Explorer 11 may fail to render some JavaScript after installing KB4507460. You may also have issues with apps using JavaScript or the WebBrowser control, such as the present PowerPoint feature of Skype Meeting Broadcast.

Affected platforms:
  • Client: Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server 2016
Resolution: This issue was resolved in KB4512517.

Back to top		OS Build 14393.3085

July 09, 2019
KB4507460		Resolved
KB4512517		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 26, 2019
04:58 PM PT
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 KB4503267 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
Workaround:
To mitigate this issue on an SCCM server:
  1. Verify Variable Window Extension is enabled.
  2. Set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In WDS TFTP settings, verify Variable Window Extension is enabled.
  2. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  3. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 14393.3025

June 11, 2019
KB4503267		Mitigated
Last updated:
July 10, 2019
07:09 PM PT

Opened:
July 10, 2019
02:51 PM PT
" diff --git a/windows/release-information/status-windows-10-1709.yml b/windows/release-information/status-windows-10-1709.yml index 22dc09d48a..9fa8392574 100644 --- a/windows/release-information/status-windows-10-1709.yml +++ b/windows/release-information/status-windows-10-1709.yml @@ -60,10 +60,10 @@ 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
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved
KB4512494		August 16, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 16299.1331

August 13, 2019
KB4512516		Resolved
KB4512494		August 16, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved External
August 09, 2019
07:03 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 16299.1217

June 11, 2019
KB4503284		Mitigated
July 10, 2019
07:09 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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
" @@ -90,9 +90,9 @@ sections: - 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 KB4503284 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 KB4512494.

Back to top		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved
KB4512494		Resolved:
August 16, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507465. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512516. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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 KB4503284 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
Workaround:
To mitigate this issue on an SCCM server:
  1. Verify Variable Window Extension is enabled.
  2. Set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In WDS TFTP settings, verify Variable Window Extension is enabled.
  2. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  3. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 16299.1217

June 11, 2019
KB4503284		Mitigated
Last updated:
July 10, 2019
07:09 PM PT

Opened:
July 10, 2019
02:51 PM PT
" diff --git a/windows/release-information/status-windows-10-1803.yml b/windows/release-information/status-windows-10-1803.yml index a0e9fb7109..c9f0739b5a 100644 --- a/windows/release-information/status-windows-10-1803.yml +++ b/windows/release-information/status-windows-10-1803.yml @@ -65,10 +65,10 @@ 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
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17134.950

August 13, 2019
KB4512501		Investigating
August 17, 2019
01:37 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17134.950

August 13, 2019
KB4512501		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved External
August 09, 2019
07:03 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Mitigated
July 10, 2019
07:09 PM PT
Startup to a black screen after installing updates
Your device may startup to a black screen during the first logon after installing updates.

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Mitigated
June 14, 2019
04:41 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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
@@ -86,7 +86,7 @@ sections: - 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
Next steps: Microsoft is working on a resolution and estimates a solution will be available over the coming days.

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 this update once it is released and install it.

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		Investigating
Last updated:
August 17, 2019
01:37 PM PT

Opened:
August 14, 2019
03:34 PM PT
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
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503286) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 17134.829

June 11, 2019
KB4503286		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" @@ -96,9 +96,9 @@ sections: - 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
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507466. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512501. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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
Workaround:
To mitigate this issue on an SCCM server:
  1. Verify Variable Window Extension is enabled.
  2. Set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In WDS TFTP settings, verify Variable Window Extension is enabled.
  2. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  3. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 17134.829

June 11, 2019
KB4503286		Mitigated
Last updated:
July 10, 2019
07:09 PM PT

Opened:
July 10, 2019
02:51 PM 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 9be5808d94..4c3dfc4364 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,11 +64,11 @@ 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.

+ - @@ -98,9 +98,9 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Resolved
KB4512534		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17763.678

August 13, 2019
KB4511553		Resolved
KB4512534		August 17, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Resolved External
August 09, 2019
07:03 PM PT
Apps and scripts using the NetQueryDisplayInformation API may fail with error
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data.

See details >		OS Build 17763.55

October 09, 2018
KB4464330		Investigating
August 01, 2019
05:00 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Mitigated
July 10, 2019
07:09 PM PT
Startup to a black screen after installing updates
Your device may startup to a black screen during the first logon after installing updates.

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Mitigated
June 14, 2019
04:41 PM PT
Devices with some Asian language packs installed may receive an error
After installing the KB4493509 devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_F

See details >		OS Build 17763.437

April 09, 2019
KB4493509		Mitigated
May 03, 2019
10:59 AM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

See details >		OS Build 17763.253

January 08, 2019
KB4480116		Mitigated
April 09, 2019
10:00 AM PT
+ -
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 KB4503327 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 KB4512534.

Back to top		OS Build 17763.557

June 11, 2019
KB4503327		Resolved
KB4512534		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4505658. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4511553. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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 KB4503327 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
Workaround:
To mitigate this issue on an SCCM server:
  1. Verify Variable Window Extension is enabled.
  2. Set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In WDS TFTP settings, verify Variable Window Extension is enabled.
  2. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  3. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 17763.557

June 11, 2019
KB4503327		Mitigated
Last updated:
July 10, 2019
07:09 PM PT

Opened:
July 10, 2019
02:51 PM PT
" diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index 1039a0f7f1..1d23df7da7 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -65,7 +65,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.

- + @@ -96,7 +96,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Investigating
August 17, 2019
01:38 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Investigating
August 17, 2019
01:49 PM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive an error, \"Updates Failed, There were problems installing some updates, but we'll try again later\" and \"Error 0x80073701.\"

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 16, 2019
04:28 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 13, 2019
06:59 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
August 09, 2019
07:03 PM PT
- +
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512508, 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
Next steps: Microsoft is working on a resolution and estimates a solution will be available late August. 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 the update once it is released.

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 18362.295

August 13, 2019
KB4512508		Investigating
Last updated:
August 17, 2019
01:38 PM PT

Opened:
August 14, 2019
03:34 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512508, 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
Next steps: Microsoft is working on a resolution and estimates a solution will be available late August. 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 the update once it is released.

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 18362.295

August 13, 2019
KB4512508		Investigating
Last updated:
August 17, 2019
01:49 PM PT

Opened:
August 14, 2019
03:34 PM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive the error message, \"Updates Failed, There were problems installing some updates, but we'll try again later\" or \"Error 0x80073701\" on the Windows Update dialog or within Update history.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
Last updated:
August 16, 2019
04:28 PM PT

Opened:
August 16, 2019
01:41 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503293) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
diff --git a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml index 32a79ba231..15f5bd4ccc 100644 --- a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml @@ -60,12 +60,12 @@ 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
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503292		Resolved
KB4512514		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512506		Resolved
KB4517297		August 16, 2019
02:00 PM PT
IA64 and x64 devices may fail to start after installing updates
After installing updates released on or after August 13, 2019, IA64 and x64 devices using EFI Boot may fail to start.

See details >		August 13, 2019
KB4512506		Mitigated
August 17, 2019
12:59 PM PT
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV
Windows udates that are SHA-2 signed are not available with Symantec or Norton antivirus program installed

See details >		August 13, 2019
KB4512506		Investigating
August 16, 2019
04:28 PM PT
System may be unresponsive after restart with certain McAfee antivirus products
Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.

See details >		April 09, 2019
KB4493472		Resolved External
August 13, 2019
06:59 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503292		Resolved External
August 09, 2019
07:03 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503292		Mitigated
July 10, 2019
02:59 PM PT
" @@ -93,7 +93,7 @@ sections: - 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 KB4503292 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
Workaround:
To mitigate this issue on an SCCM server, set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.

Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  2. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		June 11, 2019
KB4503292		Mitigated
Last updated:
July 10, 2019
02:59 PM PT

Opened:
July 10, 2019
02:51 PM PT
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 KB4503292 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 KB4512514.

Back to top		June 11, 2019
KB4503292		Resolved
KB4512514		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
" diff --git a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml index 9d7b7f6c5a..3efbd362b4 100644 --- a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml +++ b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml @@ -60,10 +60,10 @@ 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
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503276		Resolved
KB4512478		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512488		Resolved
KB4517298		August 16, 2019
02:00 PM PT
System may be unresponsive after restart with certain McAfee antivirus products
Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.

See details >		April 09, 2019
KB4493446		Resolved External
August 13, 2019
06:59 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503276		Resolved External
August 09, 2019
07:03 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503276		Mitigated
July 10, 2019
07:09 PM PT
Japanese IME doesn't show the new Japanese Era name as a text input option
If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option.

See details >		April 25, 2019
KB4493443		Mitigated
May 15, 2019
05:53 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.

See details >		January 08, 2019
KB4480963		Mitigated
April 25, 2019
02:00 PM PT
@@ -91,7 +91,7 @@ sections: - 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 KB4503276 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
Workaround:
To mitigate this issue on an SCCM server:
  1. Verify Variable Window Extension is enabled.
  2. Set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In WDS TFTP settings, verify Variable Window Extension is enabled.
  2. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  3. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		June 11, 2019
KB4503276		Mitigated
Last updated:
July 10, 2019
07:09 PM PT

Opened:
July 10, 2019
02:51 PM PT
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 KB4503276 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 KB4512478.

Back to top		June 11, 2019
KB4503276		Resolved
KB4512478		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
" diff --git a/windows/release-information/status-windows-server-2008-sp2.yml b/windows/release-information/status-windows-server-2008-sp2.yml index b8b9bb20a0..d1010bdae7 100644 --- a/windows/release-information/status-windows-server-2008-sp2.yml +++ b/windows/release-information/status-windows-server-2008-sp2.yml @@ -60,9 +60,9 @@ 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
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503273		Resolved
KB4512499		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512476		Resolved
KB4517301		August 16, 2019
02:00 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503273		Resolved External
August 09, 2019
07:03 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503273		Mitigated
July 10, 2019
02:59 PM PT
" @@ -88,6 +88,6 @@ sections: - 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 KB4503273 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
Workaround:
To mitigate this issue on an SCCM server, set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.

Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  2. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		June 11, 2019
KB4503273		Mitigated
Last updated:
July 10, 2019
02:59 PM PT

Opened:
July 10, 2019
02:51 PM PT
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 KB4503273 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 KB4512499.

Back to top		June 11, 2019
KB4503273		Resolved
KB4512499		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
" diff --git a/windows/release-information/status-windows-server-2012.yml b/windows/release-information/status-windows-server-2012.yml index df2dfdfbe6..055acb57ff 100644 --- a/windows/release-information/status-windows-server-2012.yml +++ b/windows/release-information/status-windows-server-2012.yml @@ -60,9 +60,9 @@ 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
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503285		Resolved
KB4512512		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512518		Resolved
KB4517302		August 16, 2019
02:00 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503285		Resolved External
August 09, 2019
07:03 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503285		Mitigated
July 10, 2019
07:09 PM PT
Japanese IME doesn't show the new Japanese Era name as a text input option
If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option.

See details >		April 25, 2019
KB4493462		Mitigated
May 15, 2019
05:53 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.

See details >		January 08, 2019
KB4480975		Mitigated
April 25, 2019
02:00 PM PT
@@ -90,7 +90,7 @@ sections: - 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 KB4503285 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
Workaround:
To mitigate this issue on an SCCM server:
  1. Verify Variable Window Extension is enabled.
  2. Set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In WDS TFTP settings, verify Variable Window Extension is enabled.
  2. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  3. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		June 11, 2019
KB4503285		Mitigated
Last updated:
July 10, 2019
07:09 PM PT

Opened:
July 10, 2019
02:51 PM PT
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 KB4503285 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 KB4512512.

Back to top		June 11, 2019
KB4503285		Resolved
KB4512512		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
" From d1c05ca3a01c8bd0fac61c69f679f55cb33dce24 Mon Sep 17 00:00:00 2001 From: DocsPreview <49669258+DocsPreview@users.noreply.github.com> Date: Tue, 20 Aug 2019 12:32:51 -0700 Subject: [PATCH 2/9] Merge from master to live (#956) * safety checkin * added location for group policy object * replaced reboot w/ restart * safety commit for some initial noodlings * restructured to emphasize new policy; connected to TOC * adjusting heading levels * fixing tables * Latest change for August 20 (#955) --- windows/deployment/TOC.md | 1 + .../wufb-pastdeadline-restart-warning.png | Bin 0 -> 52613 bytes .../images/wufb-pastdeadline-restartnow.png | Bin 0 -> 23060 bytes .../images/wufb-restart-imminent-warning.png | Bin 0 -> 41159 bytes .../images/wufb-update-deadline-warning.png | Bin 0 -> 31090 bytes .../update/wufb-compliancedeadlines.md | 273 +++++++++++------- .../status-windows-10-1903.yml | 4 +- 7 files changed, 176 insertions(+), 102 deletions(-) create mode 100644 windows/deployment/update/images/wufb-pastdeadline-restart-warning.png create mode 100644 windows/deployment/update/images/wufb-pastdeadline-restartnow.png create mode 100644 windows/deployment/update/images/wufb-restart-imminent-warning.png create mode 100644 windows/deployment/update/images/wufb-update-deadline-warning.png diff --git a/windows/deployment/TOC.md b/windows/deployment/TOC.md index cc903e11ec..2ac2f8253f 100644 --- a/windows/deployment/TOC.md +++ b/windows/deployment/TOC.md @@ -249,6 +249,7 @@ ### Use Windows Update for Business #### [Deploy updates using Windows Update for Business](update/waas-manage-updates-wufb.md) #### [Configure Windows Update for Business](update/waas-configure-wufb.md) +#### [Enforcing compliance deadlines for updates](update/wufb-compliancedeadlines.md) #### [Integrate Windows Update for Business with management solutions](update/waas-integrate-wufb.md) #### [Walkthrough: use Group Policy to configure Windows Update for Business](update/waas-wufb-group-policy.md) #### [Walkthrough: use Intune to configure Windows Update for Business](https://docs.microsoft.com/intune/windows-update-for-business-configure) diff --git a/windows/deployment/update/images/wufb-pastdeadline-restart-warning.png b/windows/deployment/update/images/wufb-pastdeadline-restart-warning.png new file mode 100644 index 0000000000000000000000000000000000000000..984afea6ed65d637c32d8e1e02698bf706241616 GIT binary patch literal 52613 zcmV)@K!LxBP)Px#1ZP1_K>z@;j|==^1poj532;bRa{vGi!vFvd!vV){sAK>D%^FEWK~#8N?EMFL zR@aq14y)6_y~QndoH&kq+#6NBqC)SzH}&3o7eW;w2?-&(5Fh~(UG(0&G1vxoJ8|0l zzL{CyTIWR$ahOT|6K2MqpyxS{-uJ%up0dy0Yp;FoDOR}t_wWDy@7F)w{=5Bm`|tMO z?Y|%T-@pIczg_F6Q_Dz8t zh^pEQt6vAhs&DM=bUWQnx6|$PLrkxS;`P}J1l$I<_4gM*p1gQFtorcA{^_^V?Q}cc zPPfw!F*zlmU*sYIx4~`w-3Id8>2|uEZl@npx((#F)9rLS-A+I9bQ{QTr`zdvx}ARH z={AtxPPfzTbUXdX(`_LCF{HGcT)Ular`zdvx}I(cko#mXWx~prsedM{ebQkq@Zo=b zx9Xq8#Cy#B`mby4-`nrG@%xWIS^K2@IT;{U`!X!D;kBDRb7Rtdmd|>Q^7GZR7MWW2 zPc_%ADfjmL{#;Ib`pf)&Ea|(psIA|-cH@0N{$$a2>+fCv^Y_1P50<|F&wu-V{(qe; zdU<1c-#vTNy#Mlki_YEbzW1NL>{eQ{h2bgXRBhP`2S3a!# z<}&5N);k3@z6ln=^yhW|Lf#`VXQ%t-@E(5We;c0^-otBt1^g}hdS3q*QW|X8HhZ5$ z*n20koyojrQ5dz^j^FLcdOtWFzKaPN&16!|b*n6e24Cd*b z#4?lkOcI}AdA>g~g}m;R?7WlNPPHZFyWjNLj&1vk`+w9)x*+nBPJK{6S#&}DZTYTy zEWiI}$=)js4(xyPjQZPG`XaqaHP;=yWq&t+_Rp!kE*3DepDTk1ZC&q=A62>) zKyFPo?%L&}Bn!dZqy*EqNeoQ7( z%b?@WB(Tf&6cO{9t`lf)_S|12Mbb*94$8}-d+q5ju73w`?fsHwh>D2GU*-GXkSuyG zlEg%!V{CxJ{Z>W%9_lo=4(Mp7{}^TLI)Y6ly0=3u_Ylv=M+1 zylp5nu|)~^&xUAW9RfK6XiS#h+Lh%0LZWgQCT#(3i;-HC-;&y|-|X4;MB}7fI(Wq! z`8m*F?D^l?H=nXjpsXn~e=-Vx=I5{SEXF8cxAD$0Y+e6vp7#$h8Kxv=WC0B$C$`lj zBeU<_|07Sv;ToM+zp0^iSfwR8b6~P#5-^$Tet%E@TY%aE<~K{s zgVCSz6zB>3?3gV7(@e54{q^6UgfI4tN;@cdCD0}Wydp5|Hukq{O5`f}hCC7}v+H@7 zHvD~g{2ztl_Jul(d3uIq05@Ph$!OaC}{Y4|JIuwvshzN`O# zZ?X_T%7)}nAa2MFlc~StXogH~{%m{tejXkEA`d=q`s3!${-D!84&)Z_5D;seR^w_$ z82&}Po(l&u3pcJpVyOMWzHpFE>*w!R6l_hh8wM|lP0^I9&iF<&}KD`)nN2Y(mCGa;^JJkt!d z{0}juTairvyT?;TF?3XnLfGzhaM5r7mxfj}M4<6p(`LON@*rqaKkW27ZNiqiqxT^< zd-lfU;Khj7gTUmQ#%B_lPYmr$?@?%TboL#*HH>icXWP?v0 zhTU6|hHOOEM8*s`(^$Cy`y`PAY+6giHcxcM6uz$Ya}SoKB#`-)x*iVbwQ?ibv(}oohPe z&rCr7zn|}qGf62djLPEV?A>GV(-CR-`M4|^AEOg*8h|mLn?G-o8JeNOkqyZKYPd?u zE3mWiEi`QV4l;?SM`z={K{RAfMnihZDW_>(cB=dz5BS-T<=r(X13w?1i>}_WjN~+= zB#==^t#DXvyZN&}wj?KSPawAuIC^K}o*^0d#pq;oWuIA_{w7GVKmS$~BIjo3OCa}% zLpK8XljHJm|6uAH9lVW~#;*T%l-vGN(_(+rIg&5~lBxrrxACMyagXM8-lL&B5idWH z5jrBh{PZXA{T)pBA5CV=--C7VVtE0jER*;_n-H6}FzV~|zsa-h$>iawJXl|ohbCd@ zy@G|^n<3%9k;e}<{o_C`_Q?(n5Qr0a+*0vw(sBgVZbla`DgX`C%8%^aB@XXQO+j!? z3pxzcuuG9qAa#NzocWOo@FvMb9qlYZ%HbT1?41`-ed=S_x@*RX?vv8|^|S5CGUJEO zOLj7DKGTIP=&^y(WM5Q7_jEioGzU!|e~STy8`+W31b7*)%4IU3uFp5m{|A>Gqv2Dq z3C&;q3mzOsgCjGyjJ;Z34qN2;y=Q);NkFb>N-wLe+|n_kqy?KUe};SgX=h$!i3CPt z7k|sy`%_MS)DzcOJP?qM)=z$q@fB^b?iB`GKiVaKzv*)~q`v}kCIjSNDQ4KAyI&k0 z8WM|+0&cNyf6Xw{%R<$kePU*>{P)|g>UiJ46m*gE@FC8~E?BMz({~_jhIwxOy!1$s z$Gyy>8y%6gH%X*M4Jhk&X8*VI_yMPX6v!nUGaYUKzstip$K&PcnYjA@{uTX`t7)K7 zysrqhj^S8;;ykK%9D%i)6sH7s?vd!^8f;j}cV1n_>#5GVL5cO*ODtApP}pAluJJkj zX9#(7h39>`N53oS`5S-NZ#T>1#%ENXDObN;Hwt}k|6TXCUpM((zt@8xs(kxX=@~j( zdnDqyX>;+?ta)TwWH@>u#jyChe3aVjrwE3hZQWwX9(b=`39nPG1nQTk<)h{JMRb+Z z^vE!V_UowScwk}~%WfZ2WxirA?#z#2x8>UPWZKJXs$+Y(rVTgTb7L}Xx}J2eo|F9l z>iO$3Xix1jYA>t3Z8v^yPuH(mQ(pHD%fl;?OVF9dY2zswG6L}-PXtEcjJBE&-eS+^toML%Jas1+vTJ@J=nM2Y+JuX zj4NJ?L!W+)pZJBFezg%RR^Q7GOda@)>egP*>-iZ+uf%&g5R6`ns>g#P^QmK+F(yE! zO|`ef(X9F>8d_|7a3=nh_Qnr%3gCYv3eWI_MAmW7uHR7>o?EbYwZzlX@mMk z!!O_0fg6*N`StQ{?6Y<`eZa$XKWh3PbN57=t_gsa$SS@M7l8$iq1Zw$71k zUk17k%)q??Q7kta5A~16{az8clg`jKfQsal$U4R2LH|%Z;1gzPhj%7AyUvDxXco?W z@-?0u5|8^lqR_=VmURq*9m8;Ig}pvBGM0IlZz6uuKNj89W)~)J&F{}g2ZrC>*j_8Q zc-%E00r&Thg0&(9D!jF3IItYCF|i+O%HP2^6Am6>4Ap~ipMNwuljRu);l^kE5^%5P zth=&L+yxx$L-m78GCHze53+roHI>UHiL&7{1ScCt79DxbM*Y~IM#M5~{Ma`BZYSea z-ei{=W)YxtBn!87i9!$m1a$MKuE`kLp04bR`~9PEm#5^TG1BWZCtT9doo#%8fY^gf z(nKU;Uy2&NvtZ9UcK79V4_?z$M*|v~kDY){1K4(r%R8yw@p#xj0(Vm{tlR{qmKj)G zykgN=G8YSG-K{+fU`K#;2w=U)&@{m={l4wAj1R_7FS z_m0MW1Cr5!k;m}72JHIy3q0x{#{OVl?yQ$b9PS;Ih`ZR2RxXj|dS`z|dWHm~!p2*( z!zfSc+kHONOUc!&DJg>59D z*;5vF0%kw03!$8yf>5-6KQ^8D5Ks6;P%qh^{i$QFxs*`~9_t^32Ye+XwVCyyEYuGg z!Z2g%Y`5&WqwKzw%+4;yz5OOo@AO`Y{jV`{6Y&YeHQZ~#wjWjc$AO$lvm>ND>^ysYcFw?K z;|p=|kAK9#xJt9>`SL>-5x;B;tlka8!^87Y+IAMLm#$&knGdk?{AX~As)5xzA^63F zLaaFVDP9YyfwdzQ*g2d`vE_g z2!;yvXb4Y_&O-Ix^H_KBGpspx4UOkMhI0h#(uaay}qWObsNL{rDchGoi z+K!`NFpaZM41qcuF{_UAzN^@H`Z8KR_!QI1TByu49LEIs7pz6o{xe8v*oUR(uMs>x zLq_vqbfw(Her(A`Z0Q6Y1gd@0;g`Asi*_ADUfU7u`0#V|iL60avc23*C$RZE%Xt4Y z6t`U@aK^!gPE*mCPs%d1Ui=hIXFtSZwlA-79|~KK(Rs(iIc+`a4__pJQJ)Aj*8QU4 z7*UGS9mm)^~Z^Q9MZJU2*sd2D6W?`m#UhtfrQ4#-_^_S+!mH1m5|rw6R3IHm!`dbDnzq z5n3;Qi8%|mp@Ul>x{w@nl%oisJ<*}gtlf%Fzy2LQ|Mm~q#rlpaScjmcKUS1M2Q%zK{RyDVJYwdQ`4g0X|%4e8dy%9OorLX?< z|HJ;PUt-Ov5Aa6FBI;}$9ZkH22>h6bc>nP+aw@f6G{{5xX&!49lYk=}nHzRv#i2_W z7*>P>1fRPHWudD}EY=@8kF_T*QUV*IhJJXQXxC^`Kbnfmm1&=fT7w44Yg%Md8mDzx6{|dOJR?$g? zVcOiam{71BkBlnBYcq0i=%Y{JoxBVkJ+d$|a~;lI`wVYI6ykv~1!PD`I84CkpHK^{ zH)bMv$tIlp_$vH^vhduvx$uuI$C=MQ$Bg18SiLn3=!NGvS&zduL!AUA|~anF!#qSZo|t{O7KuX3aVR=W9`9ncxh@Ho|~MGwI|P` zpm`sx-V8z?I^#>f{}Y1d)!>&SQ{WL>g|B}9M;xM4vU+Pa#ulx?l`p=+PX$>03kZa> zF)=0|n=V|1ZNHg#eoPW}ef?WJH7pTbdrzj(euN`m{0qDz3h>LJvFH_4j?iSh&yLN+W5beh`isxu7gKCt%jX9XN31 zbKIrKL^DGAOh?X=X6(826&(5n<0t;J@W~&(#SRjacjuJiiAkkor*jPx)^LfHYdYQy zEX1X+zQ(N5HF$nx5`2TwsYhSnz}4TNyH_;s@{Yo`OP^qV>n=PuCK-L^RN>SozlDE# zHF|~>swZ z7x2#H95U*7^a&}(l`p@r3;mL_5cw!jA{=j9Fw$M?$ zHJQ)ngJxxj&KuJT@z}_0JU^5&y7VDtRcyk~#}%RbAd(3$%R4QzrbQ9G@a(2I_XAJ2 z3dpspP~&)Z3}HKH%#23z*!XnpzxFjg{o*$Wo!>~HN+I)Zz=dm9aqmDr+l!%)V<;M3un8+;Lv9VHlFwx>1z+Op0kj!au-?;UxI@h^KqxF7-`r$hF~kN zC9I^3`^Auv)5*L$lSUeW7pBdJV^B8Q&YVZqx}Cf}1FuaXu#;_TD8i}_ft;*s@A)g} z7rF@d49vvQYhR&%R52ZgK#I=volwjuS&i+dKjiaM$sU_<{FC3Kn}%U}vYl_wKt0)9 z&E89ld?KjS>_7IQt@^ch5+=`GjT09?#GTH%HyE!@FU5z9G@j}oLFY9RRxb~MS70ug z>nG^o9EtL6r;)c#{W1wQj=}sNhQPA5*md#>??xs>(i)vuTzF(o>pEY0|5dhP3M!$qu@$lIK?s^9zose6^n$0Yf-o7EbBKD z4UEoG8SPoUMV-{N&Ue_?Gb?fNtKZ?LgW@rzbUpSk3b=v!saud!H#*~ zGcXzlzx)brQ487jKv=tK*e?SP{k7O z@+Cs%Kyd4<;nH_zAZg`3G#ornkf$B>3dAZpw)C}h+;3CHjF_!@N7890Y59nSM(n9nS9erGiHpSy%nsnzgF zti>TliuZa_$KKE^H_Dn(f`dmgb~4I*d-ejOOJ)wc6WjF0G`u`28GR{>yw!WL_Au*8 zU43&_5#ImoOGf6bQ&0A#D{YvzyY=`vI=7Xy2S&Jf zJXR`!ErGnFX9~=iE0w!&^>%#l#kaWApUTuX0YOWSV9TlZVXGkt?_4vl+Ny6jMr1EU z{ecsBc2p8h5wu-G*zwNH+dUsI1y#_8dmKaNt0-8A9-DYe%eHC4Nsj!|@BCQT z{}HZAk$H4PRR^xHKSIqA znT?;uec5-t5-`4WBNiRKND!cb)A5YRZzRM1J?i$IMAiONsNQoF`%YgX2z`Usr)FaN z`KuUTw2sfx(4-grQs5O+fi)*7*Pc;i~h~nNM1PM7U=WKW;RATdqi*$gYczOhl z{FBcJvYCwBg0YQG%rR`f>60D=h7D&v!uF59MA4oTSh4RoR_r=}ON`#an@+=q@{F!+ z!x`#Y;g(}~VjLqOmuOh~$H3k@4i27l9-bLyHQ&|?*DyG54Ow|2wp{rdKAA1(LML{T z?0%#GM^0P&1~CeHd~gbmU;P5!NlP$d?mBFK|5M!IFR;=OVjO~NH(}%1Yv|?@h(`y6 zqvgYEcxrqBY+NJJ-80yt-;yVR=uWcjWAA^AaTV-O0hB-M=$ML$g{!cWjNFdSaBAU7 zeDKw8Fn7mMR35y5#k&vT;0NzBqWuQ;ZYcFy)AKoD*@@B!>K z1|FcHwG?!8C!qC?LQ3Nv)E~VJJ36I1JVS8c!>f2ZhNR4eV6By<9!cmCkcO?-ev9$B z1W4MXW`me{|FpfQ#uuaQ!!Pjg$U;6to%Bq?_LG;;cJ?C5cb~w*eW$Tv&jEb$FMmMn zif!oZ5`oILv(%~IAb!byJmAlI_X|YlK?T_K{uhi&7BOGik4Gwg&PchwZ6EfW`2d>_ zoX5ovKgSy8CkNPjRw4G$A$HeD0d2+FD+{)?ueKBCF*toK^C&VS2xfAD-k12MP-kg_ z`hHWK`+=uh0ptoD&1OygQ_YIPPGko*0&;rH*ad4*zwH=}Ti$yPf);PXwzCYiT`6F{ zLMjgpf}TF4ssR;y&fxK(so4MFm+*|B=j}(qx@C}&&&QeH{1I;iRvLy;yJa6DDhU|< zSbhNSqe9vCCy;xQsb5=JZB=tPp&9l>%Mht*rtk=?inv0~@E zZsnYa)U}6DcjN<0nNmW}1pK6b41w5o3gw3=-+WI8IcmH1Vgk-vj& zdn*i?jeD`_*eS9mg0jMRD%z@}pQC6U%Xo7dk{fnm%gJl7@gRWFakwXztgrIcSX;f|{V|_ag@6M{giAz^;UjTn&+d6xtVE4Ie z=o7jS&rU7F?hik~!-J{#1T9-BDS_N2b}9CK@G0(en}bmV@?9T(OGeH*Xtsi5G>Tge zp>`h`IT^5d(dnB*AZMQtXeN}jVCfOc%Y)8|5yOa_b-3{L?+Aho=%3Mufm!P@EPXkF zqZp43PQt$TuVG^Gdge=c>!n`r82H64zbgn+}71(@| zK;AdR0Qn99`S1*MVtuv{$ep4z^C=l!`)6V!fxLRt9(csn(eW?FgzTm8NT|V6)91rl zYZv+^;++}uux9@;9RB1hJU5jF?-|2(5y0u(%%TrE`Vi{$qHX)(JSPk5KlqZ4tq^w( znup_zXvSyOvaMR|l1F3D#7~E3wKW;~&5$uA2R~6hrb>A|SOM zuTQUFWXpE>F)H(qLkBuBtKMlyUEPKyM;Xz%C8Dc)81{VdFyd z5OoiuF1xTC+O<}vTDis$$V;&2qc8F3Sm}8J?CB7;pZO3eEB3)Nc?AaNG_cMq;1<7t z^`*`_6GvRK&_8iGc3-@P&4bv ze&FdJ1#-RYG+~ZBpMad(;K0R?F|l$FY+Mr1#!!9s0)^BJ|6ZMpsRWL%{|yY6iW!PdMBVlSh^|~i zMPuk`R+gorqfaC{_z)1O2=9c<$HlLIi#I0ow>KGDz8Q!fo>AEG!8J2ZZ1rj|a+-D_ zYts+mVel9l46RYY61;1|fd+0c<~hnRSlD-To2S zbLA2yB{ITzek!lA-fuEWxoaeuHPH(Quxh z469$$ancEEuN|x238-v6h`P2D7N`Ag1gyyvm+Ux+{c_wr!|>>sES&rFE4()F2YF;-HG}~r;xdNH&$=n0jn1$un+jW z%6E^4t!E;-`)87|G8})EzcB(jc1UHoEnF7@pSj-Ee_ z@TH8Hdb6%hQK%$aT}m>c5ZvlLw)xd*7?imhr#|@_J>0_ZF2VHNH~+$@ksz<3ojwz> z`ruh?x%dqutpwaVECpLX{tPcpCTMw3#$@J}H7 zXgVrd4&cP6-=YJf9?#_E<^^XDtpt9NzrRBL=oJcEIYv(cq+2u^+V*0@uEQiNmvPT9 z*;z6k_Kn3Zl7J}%b?D|i13T%|W6EhGug|vh2cu(q$0&@-TYCB&Pc#(4K zOFPs%3m@iBQf8-NN|B%5Sx8-X0PBu3itQyGor&`8#|V~Z(V^!=%h1f*!SIW(#8EoC zhX;@ZIWzSq8PL#*TO@ulb{@`OxrS#(kbF3@9ggu>$v#hQq}*TBuqNyAY9Oo`-E?t_ zMHjJr7lP}{!Fbp&5?}wzpWqz31ReT?;p~O?;S|Kad~Q5`F(w@shzX8*(f=&-VH?+y zl{XzFkiVCLH-i@7AfxHK{T2POAH0%D?7|4{moYe*tp3F@=%^WABA|+xWD`GDHm>xK z1G%Oj5;VxbwIIcYKyK@$mmR$37>>jhJFxfw!}DGdX6dzqb1>4DZNlNtenTVLilB-$ z42KS3^P%&&M|r*%gqVdio#)Q!+{gnu>S<^(YX0rb5OSB0OqgTLS{V$ zHttF2PQ_bGhO^`1M+jN49tq1fqxHy1T>j!4JjYP^;r-%gRD6LF)I!kwi~gy z6;o@sptS8U##Gap^@_vWb4qaGi?30$X)nfCv?8tLATD3MhFu3w!lBP>bR_#(edHn| zvMZRgpb;5t$FWbp!FC#)eb4cDVN5a({O_3a3nzcx%Z^9`?Azm|RoSJ?~AXl_uP3Gu8 zhHgWkE@?e(UUt7eDVHQ;4uL!d&rB-8{*S)GqP9cq<7T8R*@(l`q0t2-6$I06p0Q{m zsBJra86m|>*yr1D_4mKSmiIqnIniW>sW|xcZ}9RIIywTAncnE9X_nM$tt9j)#B&pi zagKemlw@RP*%}l#@4&@xzQwN3|HMcsgJ2tqMSD&Wa6U#z^FZxa0S^WBf$RYt8o6)uaVQZll`+Ui5)r10kNHX%w$aLBU zBRjVQMiqrP`T1`dT^+@Y1=|p}stsAYuHXUxRD@Nm$AT>fF{Ne;^>+t$Q#T$M%IJqq zaLK{a{y>pj?CdY5rCocqD2TLl zh0p^!#Z)mQUug-YHHVc<#lbxsgYz3H{6m;aK%KR0AMPB?j`z$oFKxQf;3v-Cg!!BI zBWv|GxI|T8YRzUmGJze+(0E|(O7w}Wq<0Us%s=)oqw?gk9*}digTlVcxSe%Xbf~qmLkgSfO zxwS7r#5)xZZYh|Uy9#BSb|JfEA3|!{@aS;Osb-!GSKkaOr-R&zxtn(*pkg~lrY*r% zGPsUfwBcTkdxz#Dan)uNZ#{@vwOjFeXeA~Ttwv|p2;4I$8xt38!CiycAFfFlS-yeb zS_o?`j?yrMTROqK92u*(qO^4vGFlIyPhx`sho6njLCVUVZ1(}`)j{-)Wn`lH%>kCV z@n$zj8mbxpX9P5bPOb6C8FVAFwAJvNhEiP9@#wfxMo)WCy0Hxf8~3A6!YWg)+3n9Y z8c&SLL)_|JDA{_P0J0fANmUp*e>M9i77tP9f~(fy{!w%qjL14jA1OGlH2`vmGvRi!i048Qpy~%$Ikwi_a+JtvQ=aNX!UR`qVUc^EI_&&-+(dQ;SK9NMoIUn~8 znTt3Qp~6kOkxYj+x}Xs~`jeG=Y0U)X<)v)`w9#E6x_P8ycHt_NFw$~NTTAj3i-*US zBYM?7l(n=WpEBx~w4CKd@>ybm52H~tm!=F%{3LxksV>?nQItC zKuh5{QYkewqIum4?Y#Ib!y7HsFe?)K@b_LpObjojz#2}F!w^uD?Z|k=AWfNOL6E}O z_V28N7LPb8BxjgRHf7a^|1}=3MMq*vn#tls_Ar13JRlu5TGYYNRs*~Q>>jfb5ch<}V*2{%#gY{A!Y>ZcDSro3BEg(lB&#&1qdP&xo z^)YSd|M%E_Mj>YQj-GL4UaD&!{_boEiN%z(V8Lus)Q|b}(zQsopZ97Qz(eD$e3lMW z3vx_*do$lYtRtfhv!{(%hh8u%Z=<+!xXe$(7L=35P|bFrbc{xh>IaQGtDhuKy*$-_ zt*}&IXx59$=*`arF?&6y14A_S{@z4bYiQ!_ICv-4VcW?|uosZ~(x?RZeKaJ))R)g{ z!4u2Sz8;#=XWFOLcm!V~FSB@u*RS`nS)kMVx?c2VJ54Ch`#mHVe%DZ$>ZR)@T;{Vz zNBLjNuN~9S*?Bhhkg?CmBMYT0t$hh_{qqgrS_uRtBh4D=%{n^Eu&Gc_-z8T@ zn3}t<1w>X(;nV>wEMnXBn~|ZGm0S8uj!`;cp4W?RfrpVDlV*d^(d*^67WtUT1Cp_s zCBpJ$AAO|z0$H|Q?a`cltxRNH&ElVS+v_97%ZNkwXoaF=E18(SV)A79+AxaXY|54l z^^EM(kg*I)^q{Gg1WDdD?$Q%YFfeuE{nuq^#`bmZk1gE_Apg&kgrua;0$QaTuebm9 z{iN$shIT>!NB1eU=XtZ#{w$M}VSxT?c8vg+#wn1cVLVILJ^#REj7V>QPiPHhXVv2D zSHDGQ^+tMl&FElWs*CP#SJE5vHtEJP+dtnd-SCX^F>O@3$?qn$U;F-VH-6XW8)d8f zZg#!>T6_Bb_wT2h{jO`*>ulvMZM+Ux)Q)PDaB_xx2k-~Zm8ZoKw=U1)F1jpesr`+h#( zOW&1$<8^-jE4}@X(v8pFtX?l7n9Elnrj*fIjRm!WCm%EMTH^gPz@Ka5Ss&SLt!rRd^D5Z7J} zWVPDK(axJJ{x6i{b}~z%&GLSNqMzm<$CxRoT20w2q6)cdc2d@2RyTR}e=3o^-8nE5 z3wIntGyC}E*$UZNr@>_70r|$U+iRMd_CLAV^S9IO^g~YnR6tG-to>WWygD-U68kbI z>gY|qXA-O##yYspq(M)CjoSC|8E_FaSM`|kPkyxh4WSl0w}^^C%ww;sOP z^S9IO^aD=+OhB$<#OyuO(SdAH`&*kaOU-vTi7Z#-z2kXmR1Lv85<0J9W+BmFQsqx?EiF<)6qD!ZxQ=4pAlCw zdU!+=%=I2e?;39R?d|j`VX67+bda&Fspjy^g(#U`rtH;He|* z$lRICOCY^~)61Uk=lRc`p8R-SbG83sy!Ljwoqi z#!VvZ`jc7qk2ZU_Smu}JFv-|&hu=3Qb9%pqRs`h6IbLVz8cxx^Fb3rR_hqIjp>obP z-kO1uz`hNIjb9XXfgm2RfNdx;^Qdq3?Co?r{h-tT7?5ka5P{N63;gb-*UiG%|H$Cm z@BMoKLHFo>r9a;jHB!Gc)8OpwculUN?E& zN_Kg(_WwueZ{2&Nd~Q|!{=TF+x|V}}3D{!0?<*7Uvq2_XNE+Wlv_iG}Nc zaGm{VhRb}kb+4w>sowL<;xZjE_m|J#n5RDfJ^k>v?zx?Ar(2xCZDacY8p9y-u4O&J7Yz3A-Zk&L_C zSs%}Y>oYB~c;EG56~A0FBw(-M6>l24msWcfvL2bR*Ge}&Z=?CJnp&sni{=GhCV$sl zVdcg4GCbFYVcOrqGSr~0ed#>R7%{K&IUSB`3G>x{KF4k*>OQrZPRBCuR(T3& z$QqfSIq#D|q{A`H{uvsd)|jvPT?-m43sKBQ`Er<&i^)@qUX&lpqwMvf*TzH`>HJK9 z^U&D8`odCIZJZ>zSq{vWBhx&69nPS0CDr%JON+oL8_L_XU57^2j6NwyXwjM3SgCww?J3*=5@-?9PDjgL^5CYubmg~RezZ8 zY&&JBDUWtOnpaJ^NG~KC(?8S$>ZP5To6fxDnElvi8e-9*A9Uba?4z=68HHJZobqLI z@S-ezBiKgjj&#zCZD*um%jnINp(uoH)r(v^y>n5$bxIcVHuJ~LAsT9%oSn|ORKK&% zl7W$*>U2BZPPZW48X%{EdWo&fB><4+Qi%o90&82hSd1xJjd?rHA!^Y&WN$r+;N^R8 zUjV_DplK`MWhic@uE`lV%|QnZW%%>E*+7RttVKWp^Wfl_jILf$u;X_N023q$WIEx+ z7^DAO*!w4=Bk!^DEoD9Cp|eLcLukutMQ!XQK)%a65_fpSprZhp<=WACICyLLg!vJi z1l-mHavLuJxQsK8Hhy`q z_ef(|e4b$0Q43rI`~(y2G-%^ZaP|?{upNpJ3=q+o5U9<`C2Xg)@-c@#&u^g^8YSJnE+SXN|YO9x#1j>$zR0NQW zM#Nn0JuNeQ>Xly-I=Mx{!A<=lV5a_=e#}Cr{&D7IslCxNIaRig z4x>Z=1lB9b$kR9&{x0XN-8e0W1^=Zj-A=dDe>vTfp%p5vVTJ@)h1oJ-E3Z5_IK?7l z@h)Vx9>t3jXz*^~cyf3GlIqr?e)BG}b1^G{5%VXQJUBWNy=D+tv~ta>2#<{`!1FT- zV5^Oh2x@j@P4*sSL>}q<9LKW6o&?rnkpx*WEgGqo*$NDG61Y|zYFeBanKdH>8*QLO zV6i8Avlj#PnMb42Fo29)LoKX74O;-OBjh@m(?b*;khN;;mjLdbvI0phCu#g-qy%iS zG<$&n!L2hLgf?-q5vUSCtewN4m8-AJo=-U(Mi(t8q64#|;ddtB+8O5{rby#weQg4i zkAO>Ieylm-&K$v|@>xHfz|=|48KBD~Xvd(NXApr`vLF-mXSo7@$%7!*fzHSPmS-xj z6I2F}DHGIfwC9Z81@Iot$gv_g+iF~!z-mB{GP3p~=qs8aV95a(CoS3Vb4Nx&4lGmm zY0TL{rwpD27l2E+Q9pO#4L9MVo^ zil=14dTZtj8NB*S{ih}D12dOmMp+|loo4eH)>+`mI(ODgBdv^;lk_5^_RKf?? z^yEON)KL+I_5-3!%_>7Wk2^fV(ak-?w9AH$qMMgijIuqfr;Vppqp}_>cj&zJm{Pr- zWki_Oz&fke)&RdiS`ir?o*(;L`+E@JwSw4QGo%RMV&if`(oyxVSzvZETe_WYr~gX2 z6+o^jW->;FlUgui!b!JWIE602g0?fT*TM^@D7+q5k4}Tg9N(UWjK(%hn7fpDlQ9#d zZ9F0f+;g$x!>{q?v?^$O&!Quj;Fz$0_fNwej?-vNF*MR*8WIgi;3c-CeK5o%ougpm zI13%z_#2H#tWitHZ3v{catuy1OizZrZoKZOrS$x+kl%@b)Q`XSX5KV(h3wXvXY5LY z)M+OINXIZ((+OES1;fTE6u%gmV)lgSbeWtUH8lxuw_9IZ~IVYCmmS_M@Lk>FgP#gH0gCA5c zc9@-(kvmbQVz8bO=-h86>&4#));b)*s&6o?wTE~=o#Dvu1TJgW7}jkz+r_#DFi+=M zuyf}#TAuC5vNb%#d+hsB2HMKkE1I&3MTfr3Lrb6K=rklEQ13U}0IrFGw6vUHWlOpA zaAA8`R~tqiwr+gJB?TSLE|{#3C+nmAu6u^EzGSd&bXamCT3XM3vetppY@^O%?dZyT z`-Z{Jg@D;t8+@^D0&7Qpe{(A4RIWwQM(xoa%62hA(z&D5vF@H(m{#3p$bxM@_88QN<*(rkgv##!pU|i;)W3MU9gY9uo#vML^m|fM32kAVXAC!aW zB_tiJ)6d3d;>DTNA6Lm=d*4uYF8oZ=VmTl?7M)yYvd)uOXO`(s=j6(0MLQ2FN+Qt9 zfe6UWkm2|2=ytlD{>$kf2XX=t*^l;n?nEZq(Xccz*Gxn#--Q|F4KygSM(+@es%XIj zQ?)r%9)2~w0`r>pFeD{F5PTFmYoCqr#m#0j`+%rIWV9S*NF0agWvxhI8b?NC=N5zh zIm_|V^eWup8Hb6r+ws7dxtLbggq(Hz;F8`zkS0KTWa93T=?JWELHN>5m|V4mAQg%M zY0J!JNTZ9E;epZf5W09XGV7a=zjimCo{){lr(}F*@EW{4s|-i~1xQ`f z2B%r+n3!8{Kzv}v5=1X=LCC5${A64ielltvk{Wj+q4Mt{f zgjK;ay&h-2`3>T0sCTTxmw)&cV+)qSDP;kAN0j01$pFYeH^2EPXgWr@@5G#%_2}*! zi=Pb5KsaqBf=(v6ZUbJPU5cltmLYuE7R0XHiC@fKY#gfCyM|_NGxFQ%mZn<)_? z(@L@J>@_4*Z@?W4bv4#0mY&sg068l+;~}!m#HND?&sl(?^}DgG?Jyqp3`0TdQOsG? zieC&3$MH`-gJ05eJUuuaUI}%`Ub6!kYYxCGdI?T`@moAIVJ>FW?m%pHBc|0KK;DWb z+}Ud;emW!%YfoRnsCkX(zBx)(#^7vSs{U*hG783} zXKKM>Y&-S=-VR=fhGQS$rLp-KUa%Ic4xhp6BVw`U^i}xAm7|PNR7KMsRP8=X5L|~} zk4?u@!wEhf`MA?R8S4(6#;@m8qF-Dcigp}F)Phw=psXJEi9|`uUQDmui%G>BkwoXB z(^_;e!GO3jq^;V8MMo~;fuW2p1~Cd@6f``w4moWX8FhssZ^LoSn%{!ag=?_&2tFAGIN&T z+)ex89=8GmV-_HE;RdtUa}j}lWMUbX5p1pANWhyx^;o`jC&9KA@npDG&rU&1C7Il+ zodk(c_{S6@vvwWg2o$a7uHvO3A*ej|F`gKkhqnSNv2@pQBsJ_IkPuW}4}(qLAT;hf zfyC-&EZb^1G}e_)WaYt&=&G@O?|gLdPDa(i3wU)xCZ3;Eh?=d3U_%E|ux2NMOV+?Y zx(Eqmg~|16F#q8D7!f@WHTy2W>fJz0Ppd^k%MrXeeF0Kd?ndmwCT!hz5>W)$gf+Wh z_1rl8d}<+zHyniX%sez+{uILq_A^RX!f8$+em%ViMLSO;u&No4vkz=M*{{7q$gtNV zYUK{(uiS(_!KGNf_Y7QOYbcM&7{oGDTTddaycvl)9OUI`n7891WmAsKx;6w+URJ%w zz-kEl$uSl~;%kw;{)jm!B8|~ZP;mps7B(Px%|Yfj3olb&TJ|1B)7CbONMaek7>TiY zYmmRX1%A__kxJRevM*Mix{N3M!%?>V5bpL5#Nez(9Dn}`hGbMR&wBI^&WD4GwpLEW zuf`-JpUxqMedQTFA6qVdjOlZ$F(#)56Y`hg1>c#dX+4M@gLClQ^g^sW`625Xgk(C> zq{?;hO|L}e_QSAxX)ID#??DWidnG~p#fg;9n_&o9eE>7ED)7?8d{l2fgv_etxNivU z#DAU{QZWZH_ovO=)Shmq+v&fMZp9e6Wwj)M+&>rg1af4(bFdHe$w_wV`9q1ichRdJ+4lj={MkAS~Q)C6hf4xXzgy0g5JTkz9+EzS778Jea z5Q1_SAZOzNOssB&-P^OVc=K+IDs929CKTb&M_&+xmZ6@&J1D-IkwgQk_ngPblsYWi zdy+t%f?n|((X?|X;+CvO#L^vjeO3+jkS#wyr3iQUWsq@SKxFww^b4*;+n2w^vqQpB zcl;{)##X|SLT)+n0eVH2pnM-0`LJAg$1cG94LdO`c_G>3C4xl)d~!BmHD%M?i!%32 zLRZg7H0sdV8T0VctO_jJdk!7w?8>(tMKB|fRz@O&QYtYycOmM}eFop;3e=Nxf}_TW+fbfm05 zhN3pInH>-YgU^Re!O}%oCSxT8-#8X3Jv7V95 z%(Ar@n^TVs?|+7$4$8rt6$cPn-hlkNjVRrI4vz(-p`J3xVPw^?`v|7yH^L)kA+~(@ z1s?SZN9C?l@Jw3(Pdb(zC$8WLvgW5JW#Z>!vtY}JLVK&cGN%O3jfzA4t|Lfi6tINO zabR=_?jMwj=Vq4Rf&P(guBL(aF2~D(3oxpx6%7X}7z8#(1qtGwB5;04f;22YhX#`UpWIP~m72;R4 zAbCYA!~1;vbbJ{m6O^qPmcKH)9FykL(TK5mB%0}#Qwfw$j4Q&!V@olpcr))y$6z|g z*CUtGX%sP^O~`57fsth!@#`6L3C=CBc8NmI&|(ZJSc9L>sY2+|jmTZGh3s_`9QsAU zIjRbYOEw^{aVP5b9z#c`Nf?^32q{hbc<&axG%W)o>F{EgZN{Y1wYXDLG~KBOjGlBZ zg@<-1oHS)ozO#q z;hF@Oq&lQDZbMXU6Yd{1A5V`fL}J5s)^!tn*f)CNIcmXHL@eIPXfO*?3hObsXchWV z=FSOKczad}Mi)23zUM3q$X|+DS(>fn*U|E!CqS85)%4xiBG_jFRWnq|^A1a@xWu<>O6rjF4}Y#Zxkc1h%C z%^)$eGn{z8hD=yjdp=|3q!|@#k2l-t7)|F#dFnn#=3_!{)>my)ei~o(;Wd{e)`kBy zJx&J{usl1J+gFEEM6n#r(1~O}q`=yZbE|KWy zOs1_i3Zx_}*2h+7PxfVgo{8oj&G=A1Tl$*q(3C~hO?A{E8E;KNY~3c5Z9Wd`cgDlE z58LIPYoZg$)Xs%@>6%WQ(y@AcRUQX+_(?FUSBCEc<(yxTy2JKgg1 z&jjQqT?ZwzzqmlnBi=087Pwh!zY+r3O`rP_rgk8=fQFX(i*09`1ydTHGHg+d*MA;? zQfyqy{4)sTi3ZFq3{pcXd|r%F4v^QhqSM}!fF(fEP?%O+{-YpkR&wT;_as^xZz2fQ zi4NC%)`F!U1dt27OA(K@YUrS)_?`)LZrX-G+a_q+1_8FfTRNpAr+6F4Z>Rr; z^iRdeO}Y*S8b{}UZI&e#Xf}fSKQ=8)K>p{`j08Mt8v(^IXgVRw}(|EpNTsMFI$Cl)@zH?kR0=Y^0te1}0fyl6M?NgIrR+L(Hm=us- zXXFO_DI4>dzZr069=gZmZ7K7=n&eECbcly`b+lpBV6W{4wDFZ!l1Y|b7yq}@Ujn%$ z>bWitBO{Rk$)sJ*H>TS_emng)rGG9)E;f1n;AMrrOctQCfVcLF`QePi-s+?_T9Re# z+tOw^GJ&@Na00m*in%Tm1Dpo1H5{OO#qitZB~Z#VAb%?WRvS*41CTYu;IqSW%=BmZj$%ybUXc5(yayZ|4s$H zS-$^YL07=TkX>8RdK0M3j0mwO%kY3e!vbQuxBb72@5Vg--uB(BZvWA<-@ksVp4D%E z{#|VoP+P{$1=w<2Y#)Ki0+RYn<|vl!qwQWT0I%zcU^MKaXr_H=Mxbu?;r@YGH?AxCt^0Hy0I^A%(wkod(yR=UB5Bi`1^l$ zZ~Jd5@5XjA88BDWA{K68+>(=`KFP$AD0jow^$hcp?AoK7zbfNDN;lS_{rlf~rv2Xb zbmRTs|Ltb!X8Hd;&;6}*V;=ha{XE;hxA*nmD)YvA{zspc{-b_2{Z&C+EP|?YLodp1t8@XOQynG#&z4n zQQpsMwtAT)VYY*aghm6h)4kVcHV9<&yyo|cZQE#URrO%`+Nn>6KN#Tl(e|^fw~w|- zWf{s-0H$_m&li8S$1)ACgLkwU|1{&BtgGdq1WWxL$Px|Es7#F;Uti>5+GoZ|nTMWL zn|NJqumGm=SG|;veplNh2PVnOkI#M=zO!5cft^5ALqMkes*9f0R;fBff_YMwrY*jD zIVh!L(kv6osgsws0gh)L+9zB?C3Iwxy~@{Ev}TNW7w|u2Em;ywZT)zEe=Y7(K9nEp zW~26cYpY-amgc_my6WB0JI=D0%U^xWzGpj)yv+;Cd|tD#YB>fo)@|CLz03bR#%#^9 z%)tz*cL2*{ADDg4DQB~@rVb)8?H4erof<>eym0B8rGK>TthO`OcDpuAmeY#F?zM{~ zpOuqfozy1HDABxfD}PN%)oNtD_+{HD1Ire-%CB9Y`CTuzE`UXu(}Ccm4p ze3nbyw9L4XjZwCKnrg9B?~rlZAe3QA8M9zVL3Nb^3OJbT*@5<6mN9J0X)~5R#x*;_-iOAfQ|Scg0#qrDl~X*rxJB_^Dj1cy81+z?XcCt5d(k%Mk)#0*Ud8wo!Dk;DWnJG?jl2;2M7OH z(>}A3RtG*1$UFB}IaDhDB6RRfLU;E#I0O(FeWKZBEsb%0cv<}ePw zB2%_Qf95H$F@Rc39mz%yPn`f2#d}zH%1-;ZckzsYjSHXm%3*(|qZ8|+Jgoq5O4$mgjCW}kY>UG49}z86W7PT3mgph!vj zl4x{E_GHdYb*2uokF~%`+hN!Q5aj)JHYu;OUR^!n_?*C+vJ!Cdz8;i|y+6T=^|x}A zgQEV^4m)XP65FOV7q$dDGvsAXKgvaC_XKp*tS31?Hvw0^u|a{ZfZCjN*&fh52&JDNhWgW#nff~PF&EUGi#P>hzRA?#VZgU*go}hCv8LRNL=ugW2f#L zyUNb#%|`((J_CgFg{1U@nnCoE!Kn7He!s2 zwrQqJrN6x25K2Q1<+z9k?!vhObm>oBpx$cAuGSJ5C+1f|SqWdLbLunNoWV2JPYzLi zudNwuXuIZ67UQVf@$(j?TfxZ9I4QlIjaFxh2~knH4a&glQ&MQWY_x9~?i`Sg*QOCb z#as#2cK&RPUnvD8Pe#x+Y?YlO&qV?25Qz>1P#awrv!x*HY9!cTH z5OnyQjMI0nQ3MAwvxUmzP6y*wj0cBSqM&&n9v{c=T6O53Zy11a1|F;%0l}6app%T$ z9?e@9fOQgBQ#r&;4ErRI7!U8SLnXxC#T*G7Wc`+*3<9Qpql* zO_^DHgyG>~DTrHt7WWOVgpEfw^NK}R0TDr2`)S*=okpfqMgeR`_OAfPifwT4NT3|3 z3zVAy7e)dd*bX^oW84O8i_pa{6;VsJ;um8wF?-bxydJffh9Nl;DAWeZpc7@FJ$np` zm9r$Em{WeG+5_I_~kFhTQMuy zb{ggYI&m-UQC`kEQD0;gAT8|R=#@Bp%YYWd5<02Y)^S= zlQ?6TUOMH8AVg4ckE=jnHT%bdIz!#C@tMc_1Ri9-#yJsCjO`HM+!8Uaq7{R3SDRI% z)&nF%-s?f9NgXl(WZKI*4q!W7sW0qrfu~+d>qIE!XCIJ{!1|qdVMGwiZbHxLY@b#X z`zjif^P!_Asj&}`eMaKx*~JK4yc6AAqmBJ_q+_46n0+#dI?b{jXnWQJ)n}z_Tb}6; z>jCN?_641T>Uxh$Af6vbeb&)|h8a`e2x>Zb<7cC@ap&k75{*K<7djt(6RU9VNIvhD zfbRWgp@&N_?&STyo?Qi($i?VAB_Fnq(YRw+DW00BH6FyA07i=a=i;s*S$KX*Av(#n z>8uUd6MVY{Wa2G?*W01hcsHaHybG9P(}8vCAB7jD<`H|Sv$QYk z0NE+~!q_1l(*QbsZIH%#SoEJHhlTDC2q(t!^;q`&}8-w-mD zS@f)8HdJ7p{z3+!!w9UYyx)ahmU&t`PUSN+Y_{F%J(k%!5Z3)@{AA8n0fht?IRxgV{CdqM3uPJFYCv@( zyEoejh`scSK$pG~Vbyc8ITXV|hb%ae-6-sqBk2=@S7zqpjo@n?LG&Z|7#2W)V|m))@2N3qcyneMn$CTSJ2YRrC)@27j0ebYy`pN+ z-N<7aY_(N^lbm0fQBE`Tq=P5=g~GniY(ArCfc@?mitg-J`(7-Q%5UYYEe_azX9A+5 z*eBa2Bkz@fdz|KA+xd_1Mo=l8JhkhZp$L^=F2SFj8kyDJ%MpNX(_n#uds zW;qhds9y?#%9dmG?&BG10AWhi0Bu{@2sPbHt|Zw>jc#|rcpN9vY{Vk zPW=@_H9({2%ZYXA%gB@9sZGV68zG&LY{S{NVbnE7J41@lc;Pd+P7BA1Bj+(NhHdYq zdsx2e=SmO~ttKXo1d>!r|kc{-jjR>t> zjnxOv;K^ZhJRa0r*6GzL1=xJ~W6aDd$NKFDFfx8A+~Zf_{cnDU$40X4Zj=%2F{!Qz zC%^dbpF=ue`I>av9hzTW4d?pufhcCdp z1P*%&YgoZLJTCeB#=3Tqdb6N@p zWK@#rCF7+zb%?KPMf{QtcxF~P0W%fTYqwx(MKi*eZXx5Kfs*~2!*>}zyCv2ka`_H; zXRX1b;}&3M>1rfZufj7^7gDhb;GeSwDa$q>ZRJ+g;=^3zn)f(N5;&9Q+fk>keQE}zY;M^THut?Ku~1=(xE*$ zz6QYyHY2ubEs~e4!_Vm06eT#PuSRt38jPK{9$g3IV9?wKj4xepV3IeiNn3) z3J|)e6-i`%+pm0y=cbopU}7zPHZlcnNwr9<--gU(t?)}BL+=%iU(YH*+S0X%s#${x zg)7lX3|3>*WJ>`#OYyS_#RS}3es08zvx@lKB1A9TfT*RLFmx^fx8E#0IywUpi#H*( zxE`zb9*19Y30|I(gP^+2h+No;pA1jO=-hgI^QV8o^z!BCN+9q{Uxhi9tKm(#+mTTV zaJw*4tJ!-7dp`aGZw8m)jzO7-TDTr*%Uj`|xtvagz^iuzl>6wc71(|0Q_L)D9FgR-w9XSD0wnAs_6I+RQ86CY&=N!3q7iKNlj$uWOj1ZIYv&kih zt!>8m`Rma;tOi#<`xKRHnsM)_xfoX1h=j#W@XK1xC?^f2M?c1EGcu94|9$j|nos7N ziE%|6FneJ$-ixiK9Y>-kbt<;L3FWPOG5^TNbR+~W&s03%F$YTyUBa~DT7*`v#lXTQ zJUz7lV=K1s_e?xCHU(3ut9OyXir~Bzxe$THb*MRdiJ+T+sr6gXV<4G%?-(rDb_yT< z;a}jFxP%Orj-%Ifbasuyf%9ME&FR`Kk09ori&y59qwLrPSiLqFW74WIzvVcb$*%wO zr{5ra!8!tExY-AO|CtLo`QhhyatLvVbukC3tIgK4RDH#l-53xNoS2Ras|Yr3mj|Vd+1RZp9e6UY?nu0EMRd zOwcm3Ldc}D*X+c>)8{cbrWm8hCeoVs;uj2UD%#FsN^T`W%NAi${Xu%sNUWwJI>ppr z!R8~V-FFrb4x4Mn95s$RiU6^A&sqGOp;H(QFt&<-UcM2#uUx}ZBMK2z*@}5vPvThu z+SW54(fBvxVLFZ>sr59DY8^x%fGq#Ud;}a1l=7MR=3! zvb^mC97E^f@YmlWAf*<=@>XNPuH)$HO{0~Q>p2SxcOOM&>q-1%ND8X??3AMAh*;Q& z;)544JfjA=Z2L1~3bFLq$4Fj#7z0z6V(EcPWE2UAZ+Rb63#t*lXe}MxE)2?Cg2P|^ zp2{`PoSszPb_(9nHCTH5GG^r0VL9dC8d;6!W>lH5PGgVvGaRkjeHw0g8}Ulea_qbM z4c=w_Ll!onV%r6H#8sKP%qdxi4M(ov)yet1uZ)b0jH7onT%wla@;85kPk03ZX*r7a zoPVPZjGbphV`>%e9y9ZO>$RIm1np;M> zIwlbC$rx+)U&N@?TGZ`2hpHXt@vG6fSaO&;7nzLW<}CNwDaQNCcBnp)4;vJ}L+KwUFi%>!U@Qhl3 zwhuppQ$#J>qUb3G)zsVBWm_@3bTf8c`wCA_$Yh_Nh0E+b6l^|(Sc1@FQ%mv4)JkkV zauNecbUFqsfJ=H4{Hfo|PP`AV;9LUCDZDc=o_%rwy}}9+wQ@H?>Y6byXCXFT{tWJn zj+eI`!>gm`A#TwQtUCE29JE;(qvAV#;<53>XJ)t1UyjVfvg6kU)I`uIg8j*tGl}&hfa5VGXfbmHsC~w&dzqmT;%xt)3 ztVF@~bBGc^>X<^YQMUp*>iMWSdl}D6$v{Tic@l@s1fxo`Rdo4=y|C#Wh5UKKKE8&LSBJDaEn_=kU^$dDwXJ zGF}R*BcW)(7MAxDlD;>h7bAcKuIca@%r2-yEp_y{u}SC~Q;!tm?}63pGmyXQA|u~Age+K& zR`%&Hi5VRzV-x9Le>r}0JpC`Ge;mkJF)|h_hVmMl)Yy+*e+_HUb35l_MCMYQx%?@9 z;ys&2{wewdlA*pZ1=F-&^_q1EE33trifvSk*;KMq4C^aULhzqju#Dw0wDC%X14HKW zgID1bM^^DtEFK-2kESCRkg{|qGM8+G)vsq^-N{ekK^9{5^e_Z2YN1!%f)^)cBVkbk zQtMV=`9T6sNH&`G97P9)Ja-StK+Dd97*nP{02K?sN~u&*{CJ zPhP^~V<-zU3G2SWDBidWKAFwvL@+w_!AD4{T!Co>bN}RpXl^@%S?O%!&!%7!8ByY@ z0~naR42!lMVf_LT)o>USvgRYWVikhwH(_+<0_1Nz1FKhqvEtyzsM&T9Loyd4k;>y1 zUXBrSm!r0IH@rd^DVR_$kD+uNDq8m79RlVvlgiL^>@qrggyOlWDX2X30Rm#_kak_b z>tpj#v|(=i8Ct;8Va zQNQC9`b=k7`|330Z9ahb`if#LR20$i^Mg6z9dH2U2b8()sREob1H z&S>P>Sthz$x_&EG?mC7?$5+7W<>`!sS}~Xm)iq{5;@P*0R&T&U*7KE7@mPNJ0=hU( zM|$&dtYoM@GOrHdHBESFyg-Lw*Cz~9=5IhKBNywQLD+QQC>|e5{d{3MiW;^eW63Vo zC4vkv8k36GqH-hq?1fqQ`S^L*O5Izqbq^Z$9y5Thw!JY;+v*bdU7}G$#x|v}1wlny zkiUwy@X8oEier>x5qbvA!@|vbFqZv#mrpEK>^_F)$LHaWfIP~2BPPzP!`cJKF*B_k z^LCxY+Y=K}!mxjMVlJBZ9Y#iDD_Q4q1g6hNA;GR_*=AV%d@P;|szB}Wi@47f3jMCFzPSi0*3s+Kb%d@~3Sj4VU-j$?RbQXWP!VxCsC1gm$Q zqMd9Y5n7A9`HPU+uoL~`D|!D6+N@sS7aCG3hx;s_JMs1J@ch_Bly5zbG1)5_1q8z_ zvK&ijd((1OAb&|S@n{^h{ltk{AFe4^2C z{C!NUYC+uA^9UudxXy^h26|$*@O*4MeiofPGw{<9#n`?72qsmwAcsux@ga$5Id>Iq zQH#*YF&&u%$O;0Fuq5>Ie1}I9DYRx@Usa8n2}eH{g*z&Jpp1u4DB2f43JOGtHK+ztFZI*C%B8u z@Qu)NGP}zdlT?iQ!yn`MY590)P#9uYZeetAjeSYrb`B+zoQH#SK#va3q~jxdp<|jr zgR3FH-0eCGPmj;Uvm=ujhJFa=z(Ph6Ay~Bk41&s5V)L;}cqOzRZ_b*Fv)}v)uT3gK z9s8s8XIT0>zItJ#yyB! zu@jFCOhDU5pI~4@4Jx-DMbx5AxW_#al_UiN!}3tQ=`cp*HR1lj1U9nL;qzOt=fbD( zoSlitd5ckX_yT@8ff3gGpWw;#HfG%R4>OetQByVx(UkB-Bb zxlL#~{sA8LPs6Oboz%@w7bSMuOd7(G7YU~uA+9s zVRZ2zi2Kud>F{pabMMf6tiA9Ro(xEWSK2~6Nqu{Mas>fD53QH3A&5llS92EOk@1yu z6me)iaTaffRS_U5Cjw*dX}MT^;v;mYGqdWcvE(2OFKI$Lqs?bWXW}sXHKvaC;FpH= zXFoN^L%tqVj{C^Gt$YfIF(eAT!jagpi;?~jMq=4$ICP!_su0gkt3utrGZ>b%04;lu z;^9FV7+A0w8_s-y;Ur5-uYQGx`iEiV?(@We?f3;rSL>b=C~RWHG{i68i0I|pF?ZVuyf8i&BMMjHy#$R5r@&e-(kQIE zeZmk^-;9veI}o|L4fpwmGqkS7kkYlrxV!XEL10}Aq8F}V2>l^L)wL|U8ktS|5L>&E z2D$^kA_EMr-HHx$JogXEL}1lg^h#Jq1z(DhX_Yj7hOt%4FrmDe3bz1}OEw{9MH}XA zJB$a1W#EF`Dh+9SN_5dL*sckJQy$@J{>^+{<>y5@fp#%)`${Wh0iI zeAh5C869}xmWuJ^O?Zz6sqxA_i7Svo#YtPe8E?j~C0kA~2Q0^tp=>>K8ObYl!@(&A zAxpL*oiaNLN%GhE`*bn zJ4WdxCmpkM3f_)dfwprWn|BH6tGD9UK{QO~7|dSKj8w`iq~Q=ApR@o|Yc~;uX>d*% zn7wej8HenbQir7V2asOB8Ck6d@%X3=Oeb(YKPeaEik9KMh$=IMHJs(%J226lB$c&x zE7BUaVavf2xIcgfrD?2WNDq(6MatSeNLt*A{FY;QVOAMRH}1!hE&C8vzaCQ;w7|wC z9AuTqvMN_#5^-vPGVHeHrO)Sn7D8&f@{{}(Gl|y(XbcU%bPKK z*-msHS_ErNd-F)e{Uh?t$wd8TQ@&zsHQz>g0WEj|c+)GI&MS69^Vz)Z7MGJ4ItC>+^Qt zT!!&05wUs~0;`+R%{K@A;>lRo?m#d8meQ~rA&WO4dF=tb6;#V8v=u)ek%kHE|EH$T z#nTfjk-hF9;;1`5WV{_IzZuK-BX{Li6t3Qhpe5U2<4Nb}nLwLJ!|eK9h-ZCM$=b)4 zHp1RN9h!35LdQ3*g!ZTx*_!&P>Ba65cy4Se<}BV!Qj~y@D4<+Y(vjP z*7?0Tn2@&&d5oH(7PS&soAI+TX$Yc?#nv^WoKd!89HY2*gV1>D8X{^LVZR-NIV1#w zGpiXvhMM6O>A-zMvJkR#2Ob|+!ulm(TE$wFtZqg$9oGG07o+n4>JB5%blOZI`~N-K zl4o)y1{5`!si9^K3-i*t3Cmpd@8Re_l5Po*_gAPxFDuZcx3{JTwb9&Ejg{-51J_ux zbRD(Ddt4*XjiJ00-pad}o|VSw5(x(?hR$#_3w1nL9>XlXwENI6?E7v60@!4)}yvI{hndY;8A?Wb- zc+8?RDcpLRvS+>6Nq4vf!@gf24L^xSz>u8J*+@=003m=t>y-yPw!N!IFh5@(%3)nQ zdc-hK)>TvR{A7fR4&q>~Sv;B{kDMu9u~gL1n=^O7}VL{r}UHESq| zKvIM4C$Hc!ALYw?uP+R-b_!**6p2nwtea*JX>WJ7*=hityJi=8u)TC99odeq<^T%T zQ*+97j;2CRG9MfFG<4Ri3LQW(AP@JA%SWeP)5*3MVDrfj(1TH*t?Hr|;5ul+IT;-_ z3#cz;;2wvihc00PnUa}JquEWGB}4t|<~R|ZHFc0qQTJIn1ySaDo=G!?G*wM~NFB3L z-Kl3?y{KoJ-`qdn%+%T5U6j?jJnY$t)zj&@+9*+qRL(VcCz zWfUXbH49)ES$5Rnwpa=5|7767h(DSv-rtK$$T#5QDT7D);FFu%jfi7KrGXhi8`+ZFy@3X z_OXLxPAAdBWfpCoWlPrPBr$=x$PMeMgG@9LK*O@CgI4geT&>Tr>c_TeN}m_y{az6I zCe>r4>{@Fm$jBX7RyQx|xD)k>5rUZ+MSZaM)C?cl2Jo(4_ z(bYW&He|}O+eb!Zp@vb=&&Jc1T-jDe3HC1GW*vZ;UM-TUKBLaJ4^wKW@h;by%uDs; zcP%(#A9kg4*0$Kzl8>>~L?bgZdLdgO=9!U(zrxXfAl(Wex2#@b#ROsmUdxI)Rg{&M zLYbGLnPzc`Whh4TTGd(nE~8XF0(4Dn)7(sd%^Ri?3MhSfUDFx`HZi6NIg@z227-{*~S*M2u*X{t+fEp zY=fZw=RMTJM;R5xt!l%N{B>~X7sS3}e(ZMvuBIGo@r*^s1@L^1;JOb4QMC6@ZgaU|fb!I?;0vl|0R0z@WF{g{{f!OZqD za@YUs@;3IR{8VqXO`mm7`+d58{daTU|3JDGKyH=@D@l+h2|Q>J1SbKAr2{Ec0-m+z zH=CX9(#TFIG%|NhCsL!EoR9y&!{-yk$Nw&v2i}CTZ zQ5;`_mY5)wOsQjk$%Vg*O_Oy<4sr@+$*(a|DU1|M*BMpWk(mmL4cS zO`{7)M+fF%M}ya5nGRZKpcS0{^C-t;mahe3WV=SsbzNjafMEeE^|`=O%f_{|+p>K8 zx{j%BCY07^$wPXe#QGa{mTlx=qE6|AfSzQ z{dqqFHeBq+gV%J@3qe9a-+=~b9l-mg0DM-3*})P{Jix+B5vLqmtPXd~7@kD!!#uRxLczXDX=}fa)USrc&86%yMv#v?!E1 zOGcnFjbg}Pr5F}~H;EuGE6FPYNd9ViFO-VFpoqtr48%j&dFG)U!R z0S!erIh2d!s%S)DlS;6s9LZ#?S#L4VE(}LIF%0g=q&jv`#3a`0TgbW+DCtnFy);z8 zGR4dWX;_SomHBq%GZrAHJP7b&t~MSa%%5#yIBw%b(3f7g3Mjq zk=31UQM^v#L?@>u>t?YU@3B<`r0)aDcz-ePRdf=<|4{(uKpDRlIna?PPqjrLYzW77 za5aFZ2v23Pjv^7Nn{j%kzWiOuI6mRPb-A&g7GlG;Gk?RZ(>AMR^ikF5jU9Ry8OPmBatwy`h>;Oo%$BMw(*)KYi@T2d4$l?|2F z0^-_6K*~lIz;ZiMAq9%sPel8a81_L~Xd@tdvETj#QtkI~9c&Fa(y%&Gsk(SZ8}QM- z9##X$+O;=_SWy3X+#Nussj?_LGw#O!b{g{}Xqg2mR6wzM%K-;8a;=0Uz;t7~?;avn zqjqTD6@j>-q`8!tm^}M1fJQe^V3mMQ9#Le->;unSwwVT@-wCE&0@9clL6S1PCxC6x zcq9#3@{*A#V(3VNdc;2jotckiD9Cc{!GQ!;=ArUcKg&i&+OmKKEN3QTqYRBPGXG8* zN@0{^tG!^@2R3Bg+T+6vQ?a}*1Y_05O4}`vE!z{=&BkKPS7ZJiC`Sv^k1|WlwNTBD zWpp7BX_(E9GB&^yK#)@8*jLjBHI^Ge8Bjh3KzW_|plC|KA(m)Ia5L@Da(C*Iz^o$) zguRLScwGP@urlnEV8On#caLLzv=@<>tHzN@21sZWF?RIPaFZCbKuAZ#sa|5Fv=z!q zTP>K=l0-tx{yiGTWB*eR1mbe|+MLexxAdB_Hk+fdeCdgzGqYiwe;Mn}@--B}cFDm@ zRw7FsDJKD%+9@#YL1)s1PD-p-d)3%!weFw={9R+@>BdQFQ!MGMWqS@wAE|uHiBpt= z0aodjg=m;)Kz5^hHGHEwu?-d==QaK=a$svfQ_esbq5Jun_F*=ilQULdQ@0FRqRe^> zq)rH1cwG)a&PEZKA&owT78_%~cP2TwXP};u?oo~`*MUw<^_G*;y9qlvSJp+cKr zrsRw)KrVUS6a)Xa(=7pVy|593Adre7C_L8w24bgH3Rj&%F|E24BMa7%LD4Yv;zKX@ z#0Uf)G$Jzrp9-YYVf2#EIim$ut^{m%hRp5?=cL%`e08pvE!h$k#V{orm6oWRy-WxS zhPBez?x2xrk*so`jh4Ixeo5(=;jdy z2eMJaC&8ms_|^0>%-?q&J%-Zh>Lrk;q7>HE?580XMmeeNG$?CNMG%bGBx{|%ulmvO&4Ck= z4g1^5ISn2ORmfU@)N*>i_U4d0eTt|b+DweVLD08lerC9YPTTBuNitwh9qm8^wR0yp z=!L9XG#(m}iistSn6qFlJmM?NYzV{lBuhpMod_JAHPoek;WhJqL5_;D(hGfi)8}lD zVTS4h)=?3MhIYKQ7Z06`hTizuuxrVMk)riLer7+LHnDyVjBo@*wq67k0;`fD76T%h zwkJm|9W~%aU{qAX=*jH0qq*pqWISRjoYFIgju`i;~gMDvSIU0G+r;bp+#PV5|Hls2iF5uHU1L-`Sl{N;G zgU|~@eYYbh8}=(_Vpuv zRXOY*;fDHHb&)f)oa3uRN2zOapsIH}_We-OEdg>f?oHtvAZI7>nqfxl{7z&Wcl$;m zVMQB)D_UXoUNE|Q2IDRTcfLBLF~PrG!ul1;9rE!RKPpPu&g!9gv`>Gd8#vQXb{~zBJk9hEZpZ6j3uY9pjU7) z@>>sJMAlOCCR_WhOetG~;+?0_mB!qaj=;SAW=D1)C_OTSA*_2efk(q21U+`79RZ`G zTPW@wz-zA2^z!kzcd%xkkV&~~MnD7}A#?2D6a&AEwMcK+&3aJjsCah`V0#8-@cBR* zHk}s1_b!hhyb)N2jMgJ~G9U!D%tP$<{sCn2TC5>MWxIQjLB2dL32XNr!eb*fBtZjo z%Qq{`%A2>NyPPS(zMFR>enRG}6X+!)J2G(@*u9JZ^t{=z&^Z|Q`;&2r6$>=!6njv< zkN9VxbMIJ$mbV~zVH4~%tA~d9(BM3>Yv%d(L?o}>kBEiqFgtA_7STz{(52)Knp(PS zD?B6X@ZPjCtUqxDPmIks8=G0V1)-Z?Jl+}`W`;w$d4=OAgW`;H)}};ax|$tic7~*k zJA1`YAN10RVY_P>?hBw^FnTdg)2oPpz`mu?jmWG+S=%La={FJg`3B-4ZSv$o{qTxF z>9*tO6SIhYCq0T|8&WKLf)HqJ{L3jnIzn$cE`rueGqO=mCo?8z3HnS)LJ^(NgxVc^ zmMqm(hg36~4A9UM>nzr*AvEf@y+ZvJRIZly-${M2a}I~SOBn9*j=)_*3Sm!O zh*-P@LA9Ic-02WV03Klb9kc~6KX-SXX`Hc!mPX_>Aam^j5*0Fb0-T1(v=gD7b0F@c z?sV~{K5E#5U}WPSiwB0~m}tYsg;57tvUZ}hca5bJBngod)CO(?$f61C_xZ+P)y7u1 zhn27&1lZZQhcda|Kqnx5(ojZ6Iub=|HvNKew_lu*pS5F% z(E$fV3<6RDYd1zzn#I<|We)D8zTUxdYz^BlqgGVK5CTZGhYMA?pGcqe=zS!Ez5SFAU4U*{~@jIQi#Gv$j0Ic7mC z>W{sTQ3Xr!%=BCY(m^FPY{%dtmhT;isQOLFZ`cCwtmVjP+J|#rd;|BWGQ1X8g5;H3 zk+|+K2FDiRof*Yw*n1pd3!0GHuotI4{~U8lR+=G+iDkUQg~xou5x;l`rq?!Me8wVFY(79a(uh3@@N#%P_Fw%B^V^PNVAe8hK6MF^YYw7_ z{oxz60KXiagUp3%@WPA*h+DNC32Sy>NLd>Jguv*O2>19Z1o3z4zCjo=w*jL|Hkfq) zs}G(=hUPspqWal{blgXlm)3L`!F8=zee4p_n~vhq(TNCNxeGD18!?>E_MV-E_rLiq z3bvoXoqkVQL;4qCl84G#~ZzOaw` zM3rK0%VDH8@5KwV2>K)zW=Kf-KrqW$y&H@7pF`iI<#>fM45F^ZuR93GSvh!TS_X0( zHenX~)-h=jb{sy1Jr_U5+rgz6o!@|jI_lT5Ry;(KGrMplHXOTv(G?r9c+V-E{rDPO z(v}$~WZf?ejwy{OZrz8#Ma@{S>y%kBe3wroQrGN8s1~C%?!xOc%aOeP5T5XlfMeWp zWHq*-OP?7CTD%ocPOpJg?*#lhuoBn4{u+hbkK>LZ1@KL(N5O{u$lZ7lW9F`)gQU~- zE`URyDAesdivbCxn6Pj=`*AOxm_%K#-E6iC2(I0RJH4VQpIU_0Z$@&{4*X(l4kMWw ztfAaODVNL*yYcg3bUGvonl3wq&rB?BhBoAiT)d6;vK2ltRhYYe7t%K#!pOoVJTWR0 zq08C``WbkBS_x9u9>ybMt5CD`5Rw{q;sxrkl?VIJF%~|tCCJ`<2;uB^ExLPlU@+c| zT#T7j>k(1E0b|mZAb}3??Wjex+h}6S9!8RjFntm2qF<0%_>|MU3v(Lw;ql=q7+SCr z!F09}#GZ!+(IJsgnV}{zbwwJA9h(_(MvlyIGkNHPFfLmxG>i3={ zu+GPwWc>XD=VIfzEAY=>iHMbLW}k>|WOUjc%|CxFiZ|^+|2c{H;{O2wsdb1UFilLY z#ER1&px1;*EZTe07*W>xeHfm;m~A3kamvQ@q7~S9@&fMcI|ULM1ahBK8SE*0z(#*{~BG-yV&cT_=#yxC8zfRapPQH3XG4V#CEx@b-i_ zbasirkZjfKC~W$KXef;SyJkCFeguZ0$NMJA4j5pHPaQ56{G&W2cxG9i>88mn^oW230ifPL6@7BtssT zSqX>tLXg{f6rt6ux90h}q`^778qLQ)#PgGiaro1(@Y3K=Os4V9-9(^Tx&ftI5984x zkz|F5WRH80zjVFXsq)o13otak6srzhz?k$}ge=&MX#~YFxroVSH8qAh9_ge{xf)KW)YcMA+~))N0(5Ada}&9Yv?@Q3nh@#Fb9$hxF%!C_G7H) za>|KhBw#KaNDdb7Ka1IOtFiymRrHRiBpAiesP%q9de1g{XE2w}_W?54u6#CgDV;b0%ycbwbnO0*Rb=WOoIdWDUKo$GJ z{@o~yD{MgR=H1W=Tr+&qI|!qzc461~57E8fBxKY#A)a8Aw0t`Pt2e-o&L@2S8bq&T zKQ7;epsY$nHJ!wcYk$DN*ix)JbQX66WD)@LVeeOjRdf_@5D=eb)U@r?Sv=N10?&*s z!PXBx#p9zBcpn)&opbHheRFglE7M7;ymY>!_;5jJ1>0>P#AXg+%d!x))W zwjD+Es(qM7GPC~38FcCwO3>ec`5X6=Q4@IkrNBL9wE^UZJtGa-8aa0jmK?u~XNJb& zXCqRv>cW>8M8{D~o9_^igZF~xWA%}b@$A%E9Q*haJU^Zw>ZYhOhjx&KO|7G^F`afJnonFd+w{&^xZbQZE!lP&vx}CaboWvCMHON>@4b&Y za3`av@Zx%GXIot2DzW!>G4Z=byAuE@^|MHlPMg)Sc0F~D%U9svr1Q!b?t-IvttOTnOJb- zLoC^J0xLFdN8dT=aE&X)%M-|q6sEewBD;A%#?fH4=;ZiEpJQhJBJ>F*|`WUU5;f3E)aZDaj$OzHtyPs$A;2@kvUm8=VDm)GR)t0gkX|j zR=qv$8wjhH74@`XLEBkI9Rza6IP?iF!IFa?;kAi*SkL=95P1F48&E|C-KF;g%q(4l zrTfm{#i^Busosvb8Zx6k2`C^No|9RDa^=y8vL?+sQT?Xp zlp$-=MOeKUfmtPuh+4jljBz1~n-BBa96U=vZrF4X1?#qBM8#TIJvRlusf<*b&SQM? z3S>8K!sLv3*m~|G{BmRpDh^)3b7L~mYjz=yp1+Jf(UtIvDZ#JDQ64l>GxqLZZH5P` zw;e{}!c}x4L99y-o*0sWMSCt_Ktu^P>_3HvCi6ZzI9obr?I*5x8a7^8*g%kU3@X8+ zV~cR`({C|4E)Omd^Y9jd`u;)bj9SPh*{{!09x=-ZvejEC_aqdo*@?+%g{a$g7@qO< z$X(Qm@P(TR^3fPaeO$1KI`d8>tTmsXpg6I7GZt>#1FN^DVZz*HSh#K<8uncv+aw`* zX%2j2N|C+g97fX_ZQHROVT??YwqC)?Lnld8*e>r96P0O((fWNS3~=|3tVSL6!0MGL z=;jhl5WIw6O=r}>=*q?^1k1J@z_)+=gV`z6>Wvw+#Sc(gzXqB z0P4L*L@AybkwW6I4vDK-&lhK+Uw9r??K_Pwbi!7i3(%3yelgpXSiS_|D|Vsh>>N~* zuvxu5jWQ3x5`LbYUVyo~&k$2G@ye6}tlN7UuTCt$+C!&s*ANYH(CO1|T_b9->F6cO zV+?E=MU=3wheT#$$Jq}tBXd3mglFTuDH(Wz?X2E*3`Hx}!LM+W*~h7L`ynJV;+;lD zZuJ&*;Md_uB{A8*Ya99nC82NpGCVUO-!e3%m#aS4-% zS@h_y1Xp6ir+>oCxeGC;vI#|-51P%0yi=CI-Zc(>DK$9zZ~u7Sqt!9 z;&QU+^(feU8t&nhSW0H_^q5pEp&w&hj@K@Lr{FiQ71QQ##L3UT!~=t?@mSPhlik}aT zN8&2Vd;MO#GkZQt_nw1WbU9_ix;w_RlgqH|!q<3Z;#_RH_!+t|f*M?~9?K6Lhd-mE zci2ab`%Yqf_DW1CXvF+oAG1x3XuI$+`b~<*d>YtDvd`e9ZHQXD9+T(Qqi{bBk?c*& z)3rx=F%30p`2mKw_1JLkV|4RPg>%9()Ev8tcLV2R-QkOHBj~;rT!{RJX5_TdLFrT) z=Xkt2D;srWNsjD?O{Xs*s&Ow3uM9`t{|r5+=OMl20LJ7j#ZWq~^`|~W?^%Udck~?Q zwVX!b`lE=e--tnEhkL*HBYsN8mc_is%v*(5r{q#TAEHmxLi7zQ#jCRyAd+GJyD`g* zBe!;nN3XyNY#=)vncs+C&#Xq#-t!ohzZy@Dnui?>+aH}+iu;FWU=pLpF5Yxn9@*xl zw)W<6Ph5d+1o=gW&SPqREncM4e=~GG`e!!5ZB7os^elXntI1YZn~0-t>PECuradQz z5xma9pFp11u!oFxKY=CEZ2GnG*abW_mid5f`~QRM5hN>H@rAO^6nteteY1!d-%hcS68aq#M=crSV> z?jT4mQXPWcw*bnTyeDW+wG+6{DJDA=_m8`|2>P_&8U&3%H9rrQ>A6d8tcMeWOhXE<@ zPg;%p{UY$l@GypOt1y|NV~-)(cx*@kLg%l-41)Wsvx?BsX%@P_=-TfqA>sYHqB8B>cF0?W+71KnMxVq#G}W>&2+OV=MF z1DssG3^R+C;%B3?(9wAoM&;GRi6Pt5lQS{Bya8j2n&F;MgP%_-gj4(?^D@iMB@C{~ zH5f2&9lCo*!HvK=y=onN3z|)6`q=19%&cs{q@ra6!X@Z9u!v!wWl>LOk0=aJUI6dp zg}7@#GKLn>=;p6LAF?EKAce+s-IDR-=yW)zt;7S2UVM{kpyS$}nNp0N;bm|nI}5B@ z1^@I#hP6F1FosNy1`$$*esOh}Qqct8tW|hobT(d|Q$of$7tb@w>77sq8_M2RQ}NuB z@z(5l7{&g6Bccu-iM3>5EO%TU+!7YykwIx@*TLt)>M*IY731@lnu7vt$&9sYrj~}k z7haCgibl*RTZ3OtFT#N2TI@P-gaEOSvLLghW9aM|gPG}dh-L^qG`S2f)6w2JA|B)B zuEn&{%@|0q=)!UzpHPCa70q~fNHX4=nT^Sn8!)tFJ?j4_Oc-k4d4jxKR}+HgOxbU@aVD@(F(7xN~SJeA5=Ai+eccRJ9;Y(Lry`p3-8pMEE6^;b)WQGa5<6 zV`QXL7OcaBigkEq&LX@SvjQQNt1&FC61MIMxX(8dQ`mp6hc86`q*_d6IRoglA0C;7 zz9I7|(<%a$wgL#pP)2PobP%>4d3-hnFH@IY!gW$lI(|tu{5Ew^`%6LM&K8*ty?6g)K{50k5!F{X4S zo*Ei!*&@K3AV%GArM)~ty?b&h`?PqenWj68pdU#+9GYE8f)I#jf~pZ(xenut8qi}z z4(1fpW5>ahMhE;-R+eI$oj7gDHopr5Yb6*!PXZ zbE7gbr*ti5&07QigbLit=+iTKIePS;M{rGsw))VE-iL;#8(EJjSc9P%OVNY!eROO- z##e1Hdw)MSXCd`J6R*uFgMTXJ<&utHOfE*>lvS|l7X(l0efWYV_{`l%OiChl)FO<} z4bEL*_L|pJRx@)&7hO$%moc5m3=^W~G?Ny?;?0rKGcw4zJPqFKOd9cxmJlcn)m+HgvbvlqAy|7mO zX?kMcSwsXxa6M?qnzOEHl$v+kkBX{&UsMl`N$W%x_ar(tmgC6ZUG-L< z^)OQ&`C0pyXyyU)*3>M`#a8{S`f64O^U^)N=fI|KFy%#g=yW8V_R>cu$HdVv*={W#Cscx*h*?)%jJBPtuAu}C?j^xu(b~t*%fJp``K1Vjggu7XNZ=w0CoC0Cj zXDVzQCtHkH3!?f3Qw~w+AHyhcb_pH0)wLf-m_sdkmYFF zDEr#1kaiA+eIM3AWq21-KZ}?rf7jLlnljgKHpz_k22sSUDX#1z&1O>nyHjo?I#zus z7pK`QFPzRmTNP+{ly;+iQKSp*(pUDqxyHJxe;rAlG}Y6C@{wNX#He18NLjQN6^+D; zSJ}Qke3t!cj>4m?H2W;8p%sDEE&PpnYI>&j@B%achx?wzRQ&WgNevX3m&NX?My z0QL<@mQ_#6jwH$~6x2Q}8gg?AVp%N5Og+3V$A6mXhg1@U9cC`F8myO|Y_R5(Yc8m! zAL-aNEvvWj(E=0+DwPTo&Hu`S;T( zNoSz>x&CCdG&r3oZdnOOA=6QqvQ-ZzEoe{&XaR;DuiI$h2ib{be+ZVPxxxzlv?Sdu zPS9Lsv65^mHi3%Ds9owzXZuqDO`EhlT&pcLPgV<52;i)TI@lblt2yFkZaK>`4j_ez zve9)N1Emv`1Qb*hft^m>HU_H~#bVGj5-kQXMs4b*{VgntBsr)~I$7OPH`ZGVT6m9{ zcdTmyMZaRpGwdHNJh73JG4rh3Wy1dgA(dyAg%bqyS<^;UH`QOVptGYjj~hed5`YXs#FIV73-~QTG(P%ADX(Uf0&2*Tyw4IXtbzA3r4gricXob*GpXg z3W7i$UY%XYuzQUKFwAxV>;v|ftzMu7ka6j3#6jA!K;=?)l+FLYz3%|ivO3fLrZIpf zn>Cwc^DCmUCPrg4*+df+DN=?hOaUWpWU=rT!|F5eKwKxO2TczJg9Ai=p$}C!xagbGO%Y^w@NqbfCLi} zm%;zkW>nr~v>U^Ep*z)y$Xx@3@~LE!LEPL-{wCYrK zeIVL?r?UpCTeWMEl_YpeKkJRss&}Mb?j#(sOf5WyWqak>r3Wg-VE9Te0dD3K`pe^@+c z3?gy$0iCFof-*5M#YTxx8OF5px< z6aO47sY8{{hGAsxrAtqbY?vM+l2NR99k7rp0iB{#1EpIX&|&)2P`%^#Oiy$Pz7~~< ztJ&xxv}acN(H)(X*1c1yvLpG#{>E-!7(R!?vTxmM1j~ zkNnS-qoqZ}!15G9SR>cTv_eYYI_;^>t)qexT(irlOGuBL>l0WwS-Ui;V|(P`T8XiDkXj)eQk zO$2MIAlRmq$1t6eReduaoig;4s;M3{_-H9af`ks3D9!BP91L_xbf`YklT5wat!N)h zQql~_gbszp_!2o#YA}~RbPXmN^fl<(K`NDp>Wg*7{G0S^Z7+|5O9tcBpr-neS;zC~ zM|Gh-qc)(EsUjie!-Nc#i6nE?E0LuA^lCTiQ>q)bDN5YhXKflbH4|ohl6=GTKL--q zSI+h+{V^(kwQ;+@R)e#(0}U1;S=A%sl)a^2X;9rTPiiA1KIKvESZP#wXgSY>0+Fzm zYnYD4Q8~Cu{Xtp-b?B)J{dV!UH#4D3cWp?t?CTLK5A_ifj!HS3qkqnBn{;HF zM7G*xBjF`>G9oyL>&U(I>6m&4)wKpWwpj^u=LIw6NvCXe8dd|1+O6{L4P+)vn2;i} zFC>?!Z&6rd|CD-d)7q-?loCAUJt+MB=yJp*6S*qgPOGs&N@^m>iKtDB9Z641CyiB5 zR;VQ;Qt4$-qhiIgV~fDU*%-W=)-${%11WuCgH+>_P7;$^N%)abBt#LRrm5Dr)EGH6 zCs9fYIWLW$CvZKzccoSFct__&zIJ+3o!!Vv9VOTPyDEwuiR5i32~7f3<*IS0!}C9p zl^Te`^b@P65Q`mwq$+7cCqFF?4OEOn`PShGuQQTt8HP9D1R9Atj|fxc#Ppi9BI!+p z?1iC0KtyR$f+SP=zba+~%SMfw`LY8clr-tbW(zD!k8~A}KU_6Nk*g7~h)t(drB`Gm z(gy$$>%X@suqo zZK_w5sZQn6jwEh3opbOFjiHoHGHpuo@CJ7OY=CyQM8WnM5jV{0S<=0ch|+Ec-@N>5 z!1D4Ls5{mR-FZ4yRM%b}Rqxi$=~g7@-4r7~g2EHQuzWcSi6BYa$xM?_Sw0#(RHm`g z;^-e_r9Z^lvV;=FL88}XF7b?$AxAKQ;X2iNtzHBy~#91=SO^UU=Jc;b3{7oteRPQ?8KaOSQ z^($S5ZmO=?@0v!l?^9?}{h0*JG=;M)BBG0JKr$5&Y)6_AXwa1^2!$z~JDSaSd5~ZA zL$ygifm@rDomWocCg~9h(*VH1D}n>))luRE^=*|C!!kc=?;Zl?K%eoA(i8DPN+F zga_>9UKJ#wmS#UG6{4grMM0F#OnrcngGh*tfq7`89SbC9>0CF7!aAIYD=?i?m>!XM zYi#Nq(vP8!!Ct&}be@ghTRKtP0@J}kK@y#a-i{8lY_%2{XrLmB5Pf)M9F1bMPRh>2 z&gOMUrG;f`?iD}N9LT#QD-wkW<(!0KjZtATos>dUPwHScMW-LrET?5BmZv(G1`$b# zip%pSA|v^kJ;PI4^&kC&a>^~z^#(eUhB|{0p9UhuE&UtpkjlRe=;~CgW9DBHvGS#I zRT^|bx73yDq_F88@rUIRjz~oHA+ySmg8@6a256I9Ng$S1KM{EY3CoI7z2%iNKS`Kj zB2nd;<>t-K=st<*O&o56iWg=cJ3MEQHeiUrv=rnGo_gAB#>j-yzl0LinZnWZUUB=& z%w{iEMDF^E zL4xUE*?Y@zN{8AY$&CZE1Rrn7$D1j8gP62HDr}{PZC-<}%3A%7^csS8 zl8+iyfKU~VpvEEcl7Eq-)*=~>HO%w>%dDxlq;%75VT7g*pfs_}L=t*8_xevyrP1H1 z;wK(he`{{+NRzlbni)f z3sdP=8vSMxlx8cE>=jm|Eyd|S#qCMx%E$Q*uXz0Ad9EB)wjvXir_739gs*qTXXM3p z$2g3P8UDHUV{YhP{lEqZfBES@Eze29w)8444VZdr@Ku{pJTfaS%A3kjb>hz-)8dtp zmv#}d)vfvQ$js8nFwdojevDu>0Q=*#{9BlMdIO}$(gYt1oB!G1NN^xh9HubK%1G`M z56j4Apk6vHeuib63v3qQm6`HxZAQc|$)53sOLc>m+blh52P!kK+`M+FciAgGg+sH1 zFbhXz$g(xH%Swmx;kEbrIOo@&HV^gfF9TdMkz0e;M#^S2$qZK;&BI%FY|Y4_4BNl}ng&Bph4sU$V1VD_JdKsqk= z8!!h;r~dm};`%gPN?8Ah#{OmJ_hKjy|H$_6W#r}WSsucrl*t$M_gU@(`MlKn`Foew zKM0pfr7_T#S9 z60}R7iSe8EqGv%Brf)t>|I&b$k0~`eCAR_#>fXYS9EbQ;LDwAoWWWUEu0M>lMcZ&| z-1C@Odk6_*W@GS_MaWsc6TUXtsNQh`zvxwhq!$)o@~)Fe$eoWZZ+wh9x{pHd@)el0 z^$6NLGZyQPe}FstPs2+GPhs?&RakZCByLU^gx#kcZs|G#g$q`ruzDjB^OxYN&V?90ZwvAkZ$gi8)d*>ugN~V1h{@-B z)Mz|DaTR{}XaRowbOkz%TZ6>xc_is~@T^q5uH=BwcQmd`c>(>aHsiX~v3PFAYW$@8 z2n?ON0>c(Iq+FEbY)oSA#7sus= zG}6TbvH8%25}qz*eJHB;VZ_0~!J#4GlGn&7$=U_Bv0ADqv3;KUnjF%30{_co1Va#_ zFVh{;5vm<2x)okWvD=RzfznS0l4$!J)63zDqI9plsk&hIzF*^+{3)n@^*BQLza7)> zn1)atac-^kc%8I+4xx68oPM>xxE<}H`IP^TrTC||46CKSPSZ}u;5!UQm>rGJ^7gjI zEPhtaM|KgiQIOr=xA#qNxI8uK6S7}w~rT+bPEukGy%S( ziMFk-k@nnbi%){CzS2E{@>fK+qwQdaZ3D6c1tegSeeBRl$XL9YZWvGW1T>1uN8@N6 zpV$6jZKu-5R!P#@-lf9=`3TXL#?ECXX@9*#DVpjqf%eX7`;xYL*%mF%8WOc1TOT>K zTV;$LE7z&Wz!p6R2M31+gD-{1bxMmwsJ)}1x_DU!M@XzXL~)f)OljRYp~&`(N`a1a zCrFc?PZlJ0Pk3PBiehXGU-lxO6%`fu|3VqPq2JCI5;?5 zuDE0(_v8HLc`bYR?R2702OZ?*96^de^&T*LoA5oee_6x)lVr8Y- z0{@=mD!QnE;mqp}%J3fs(MZf_Pc5rZTaQIYw z^+fLA;NakJNpM8&;NalUz~PA8!NI|yfx{8GgM))Z1BWAW2L}g-1`bE$4h{|uUj@Fz z?aq$K9UK}ebS<22w$Uv+H0x{yVJDS!`;T2tqRSq>TG)jay2U3^2l#Yga5S34==wVy z2+T)#d^Yo(UT`-{wDT=)Cbq$|Rc{c>ug($l4oKL$@ zLzmqYL${^r^7p_6A3@6^7#xv1I5b4ClP69edXb7-Q-@8UjKSUSOVC795x&5~Qv~$_Di=RUrj-{a~9@Q96A%i{Sq)NswPP9%kAe8qO!v*@9_o{~U?udH5ue$4|72uyvw_unpW#0hs@DRIa!S~Q$zCXjXGY>7(JUpaw z?b(%vpu!CspJ7{fkNFy3lznB0i6_m}e~|b;_HMp;eoZKBER1 zFK$E@!^={hXT5}xvsU@b;POZ2%(cj5on_8gL-QJpn6(kZsy5>J*_$zJ<`(oRoR7v@ zlHy<&v^*|`BXS3a1_rH%Ka!432TtPH`)4tC>j5mPJ&d{APhifD)0nyabyRIXiP_su zU>?nLwx7bBZKp81_9We$CiqTs70vojcHaN5@%h?$v)?Y@C*Vf!7y6;uAJ1(1pX2uv zFwbK=^J|Y`%Fa`mR`(hfY&nKM{_aocJ8m9)?S_)XbI>G4>*N>Zvp%B7ph<@jIPk_h zc=ff@sM=VE`LFE5g4+F9@XCJ7edQqLy>b8xw$iQvVBuD#oAsvW!kT@UPrF4myD@9i z9&A2z3h$o%7}q3`$eHh;<#90_kvljvFo?+8W?;>}6G*A7K`8s@_xqHgS+5FQn_7wQ zrcB0-y(i-Ol<~wwH0xQ88+%ov8Q-th({FCBce-zuJQ2QjzJNfWSc_v;ui zaWM&KsHvF_kNq6=(J^`WT8A|3Ir#=Urj^5YUmy6|4<*tVhVCRF;XRT=3~v}{MNVy< zOJwq$>2FOtEwTJ;5PsZ$0uH|U9=_Ryd2&SV;BbXP%M5KtV)gE$=s9gS?tXd(9)5N_ z?&>p^Brp+o448^L`&HnF{VQ?TfJ*#G&wdkeXa5Q_-z__u@2Y3Mi|zw%eq{gC+}H1i z{{K3RNwf?2;r}wz&z*hCEp9Jf?|=Efv(FU#xX*MvIAARP^@&NSKKLg3j$cXglDg>< zgvCjdX^^}c^5Bcry#Zsf?c_U%&zVc|OSg}m;o6-OljYy#K{v5^4FWz>$*mj7N?D(! zrgpnYOuCW#FP@u@qi5d1w>mqC+`-|>g%SA(Y}s`X{ip80?R_W}cPmEYZZ9IV+Z_0k zNs!6a@b#p`E9gDh{|uPxKLbcvLOUYxpCMrO|98$TKYllQUf|~xD((d+6)k-4CozY6T;G7tHmV-C2__oKdDq2GM|zw>@CbblfKI*tIsbOBC$0YW(V zgv6C0G+_)PV#%{@i}CZJb8*;+oD#buatDVi6h`FfczMrZq|P{m+xpEy^WGH*?=}+= zJ?Fufx*VaY)d){rf{^4z2;sXB)@unuQx+4|9%v5hxybB%$xGquJe%Y)4Zeh#@O58^ zMkyrBq!;1qwh$pb_?}Q{Pq`1VFz7#ZF~Vdfu`5m?Oi#sA&)g(s9vYF%@9i@gH}tB& zy8W-?xv?B{wChIq*LrLAXX$r-*2VED}*uL}lB5$XR%94buI6`#MOhTEtwaaEY6(BT`ekd*5 zT?lcsBSLi3nCx^BjkZ=M(7lBz|8!>;)X=OrZI3t+uXst?c9~5+XA{~osta)PNakLc zVR1Q3e+hnej>w%v?%;6c!q&*sv2M>%^qpRZ+ezZrr;^l2$|0%CNU|Q$hNS3yDM3QN z0G^#B@Q4)p={6sYk{9C1>cc4AegbK0PvYACi*ZfYNf@wbFK*3TW9#mP%Xi@3k?Y{= zx}1Z>Du%Hb;mPwz+9Y~^co)WV-cEx`XwQYXcR&T2Cs$z2{BXML%i zA|*ZR|G08u9Q~23wQQnGa5~aYGzp&nHHyhWSbNSGq8TqGdtWrusta)xM=Z%cLF7-u z?^NbpiqkF|zZ^Unhu(Y_|Kirj9UQJ;_=$WyiM-#`THOA4Ihv=4$g4@PEBq3(NR)(2 zGWU_VKMkQh79qU*0+erg9Xnq;jUlsM#!GvTW8=~Hap%BU*nIX67%+V;rfu4f)kogN zb-gLACvSkS_eO*!FEAqaanJ}B_IXHhXL=adJp(JzETs~w54??Ek6lD=5rG$zG(YcS z=L?94&c>@J&mcaRakj~}Q>{jd@g!+&Uu>I$vQ1}j^8I(wZ|r0oJ9`!*CUCI$`Lnpb zM?VOLByXg*Jl0K#EZ*&=l z>mDn>ZQau_r|uvMme-+aM;%5gL?or{e@V!}w<$Sa-#s5!$Bu-r14*8P!c9H%aZTa` z4i=+u?W1Yn$R3~RFlj}l)=KS2c^Z9a*`M0?k6kItk-0$qC|e_ zL_YdLB7YV#^yuEkiUEr zo-MD&|NY}%FtPRo?jJcBGdI;>!=A%PUsi{2_b9^7GiNbw-99`waW+2s?I(EqgAZ}< zGqd1pJsLN38HTO<4`JKU)7X9bEtFJm!PjFlP`-XIj+{7-n$z!~#qbv~>E&JMK5;$T z=gj2*b{uy+QHIKW@1n)va)h<}HNrb-U??V$GcWCO{1W+lj>sJxu4vRJ^6A_013!`5 zN5?NjC3To*Ae4^k*kk0UXpey3B30j zO5%$Vkv!kx^QEo~5_Ww^BCqC*VIh9pzZ}>1n)Ia*dFaJN-gYELuh@h4-g_S(eDnz> ztlEjMQ{p}J;U_3sycRF-+Kc&{j$n1oer&9(#r=beaZA@M?4k7glcy?ibz%vgD4T&9 zt6rwvZ_xVJWwuZM&S$0}^p^usd*BqtuiTD^4q5QE&%sS3^4CB49WrLGN3Z-Umf?p; zE?$W3C*Q#xoimVCU5l*;52L(l5%OPt6%${o#h+Q0!zVAs(!;0m-Gt!??Kl{rvDwUr zcCZv#xDO7h#1SWvJ2+h7xR}Tv*B1xb7X8uy&TxK=RE)j`5O52eM3JY^B?>976m z6_iZBY$7M&waY{P#&JE{i|6wvqxRrYT+?Gb!!E&!qh~Rs zdLMibkAN>K1J`xQMD6?kjTV{n@j%)fY&i2Vo}0V^YxbRj@18;EUa%C$-+CL}^QL3{ z=?}1>b{Ce`)S>R=>nK>V1K}Mq5E@Ss*N0M-tF|Jx&&ET8%5n4ziM+ETatDVi7xmZ3 zr)|UcN#x$g&c$Dl$VsxvOA+3+3Pa}C;lSDd!kpSuIP}3M7`5ss{x!7~DXIpJ$M?yDddz@?13SF^h3g8vh(353G@g^jL^{w6vm+onOitd3_?Mn>J~f zyzw~J>^%YB{R2?>%2BM}e*#;!?ZNu3uVT#7T6CIRgCWc6uz1x5oOtU4+&`ooOHRLs z>D!KA!txz>X<05kAqg^IiI3jm&_+Nl}5_!Mr9+5Y)<%W#nQ@$7BiB|)Z;kxRSz5W6$U|Z>aNkqKX#Y$xBHLu(hF+C;WaJdw)_V-P zb9T|SaH;8cc_e)*QcD)${{Drys?}4t``HR~EM9@zx)&inYbH94sm24tDsWS;QFw6h zWHjwUl8w#BO+7QvXY^Ful2S&AJP%D03-CbtJY1VR4&UujjE6GkBBIl1-1$T)o*26n z?Q-WZ?PUmwDnP3t6YztlCgB^2CFqzj1K;gN0*|Ex-lc>Rc`;`frT&kdnRsAOgwPM$4;%0U#~Ut9y+8$3A`r>(hlj6V0)5G4J7uU&lQO5xq#9<{rze^d`YxV zn2WIPbL@bT@6lDZ-7vD-EJ}_frpHL4skG}wx5>-sZochCIUi2|f$#(GOdBQgyZTPx zpc5c++I?XnfAbuX%g;F?x2=dI#|{jy%`il2i=p1zk-Iw5jgIiQ)UFafNqV-=yhARU zYDwmiESl*yI+yRy(|-;@yC|C5Yrx1xL_DSEDETAkE?nCT6<=FEV;Fu%`OP39Gp!_f z)AVS|KZR(lw6#fRSj=N=Im5_Ac>638IMbLg##H(?R{mlb28sL^&rQVvJEBj2j>sJx zu29&4pfqgQeHeYJj^dWy({Nw%NZguQhMOLrL`iZ2ZhU+yZcd$mTOOZ+8&hf5dkSvg z^JdzAFLg5A(3~Q-lj*Jk%^#nMX1%L$bMHyGrO!0FnS@(=SK_)}GiWyjcO;kK_TCfm zJxZU=pO}qik5`%BTT{w$Gl^N@eUD~6Ek4F`qvD}o#dm88?URep?)g$Q>oXh6_PmFI zW9O29au50)Bnh)gRFHhu zM_dsiWAm~9=y603BBA~)4Zc>CoLiIZq>H`9bCiOI5}5?0>2uG(dwu(0?-wK3f1l;P zK7zRk`1PYDrR|oqm$EF)6dsf!E#~8wnfP(vLL7YkZAat|4p%fpwt}1J5sh6@!WN*?aIGAN>yokDJeY3`0cxC^Vsj8#J#0P^ylIDa7$N{~ar~ z)FExkOURzJ9yzl%5bOEA1{qcBky*8g*j(=!c&~3C?EPW{`|q>d*GDin0Xr{@>{%O$ zwaA#gn&x%Low){Cvo~N6?WeBUhPOZb2;c1Nh}^;9%7v}NX5*>Jt1+YQ1g6#<$CB*_ z@zS>4SY5jlE4S^%!X1Y&zwRiOY&(o)JBaOvv1G>)&&+pWsmyv_U_OGSemAoB{2V%G zHaGRdpnES2zngPmcxL^#lId8xbq}hUzWKWjqPp%Nme%Y;>t~DM>o6Rlok|fFM@cU5@{sCm38~EY}-C8XP#Hp9l|Q+b@8hwu<+I6Sn=xq27y&O_TeSwW6`Tj zd)*Ps!?N0asM>iLi*_DG>7vcJN*7DSFz-Rj5Wm8&~Nk_;-1DVg~7>43uo?9|ZD>{pHqzb@tF8mJRJxKGIdL0b7c`f|bX`U^zP?cW`Kc&~5ow#SBLyDR7F{ zhdAxtAi98A2qfN*iG!!;IHQP3>SIsVm>Qfj*99aap4nAyQ+jT`x(@w=_6L z7b4O=ppIafk;G$JKKl3>tQ>;D5xIjyLj;K|VFF2DEIWQ42|(ASrK4#~8X{ve5f+UOOzlT4>ishzL7T7bujP(y6aUWguM31|sJK9Z@F{2hC>y+DW1
}zkr1Uq z*3`)IU0M*OI#%jp8v>*fR~JhpNm-Wklb5o-iVzv6`Xk@QGG8_z2P=ypa76Cl&@d53 zk`B=}Ig)ylm<*D3u5Eh@rCHnNwEx*iPrAOpLWCr6P>CmT$7P@~)2aJ8ui~I%`olSk z2#L>TnzMrDF@TUxW6&ga1P6tYo?X%;`YBn7ODFZCekcPU6P(8 zKa#;$4O`|ZGs!$6j)dKX1lCz;mBd*{A|p|2JveAS10eb7G6+3Q`Yy%SqDOE*$fVyw zmIWnslVC-Bmp?R!NeypAC*~n~7zbq%d%OmxQD_{ShLBh-6FG_8!QqOB5w)$Os?*C( z?;=hiKmsDZuNq#uJhEn*ZH-*;{`VwQy`Rrpa44KWnEFOA%4QyRJYQk|e}!>*Ky{~C zMu;6i^75ekg|K|249qisf&4fkcW}6p5Rm$U{dc+G%SvCvA?{Dd`GM(tx%>_JazyUn z;NZ}};fUP9!NH+{!x6cIgM&i@ha++a2M31+j?W|Vv==wRcdw4aW;!@HI5=F6_}NhW z{F!MYZsTqJ&J#JY?a&(-HKzvoi?^e|!NI}7;j+W1d0R1W^FjRiPk%J}*6$pV|M}0l zUG6-?yPx~HpZmGr<@@{7AOGNg3lKSfe=#!uGydY>;NalU01yzof&T}pSNsAvzd5G> O00002<{LTmcP-JB!)ZV>=bA3DaLHzW#R~%?Me>=drs!5Bz ztD7M{dTYR2i7JY|d)Juo1!ns3t^L_aM)$1;>fnDH+^Ay(;N3gjN?8d}4KJg!T!d6j z$=e$uc+ue;s)N%=-g0(233v@`74!&dL>bg%&I*%v5|T8K9L{gNkenv!563(^firD^ zke&@8UqX9y`0V4BTc5UzT77rMGuJAIrAq3B9VmFxejxO7dQJ|pQ>y8Fi7c1@qgytw ztEGs@?;Utf%c%zIg|f9W#q0tnc~C+Osi2R}0~B0qvs48qO;Dv#X@)}ht$|iCOK)#P z@%{Vv@m}9N7OS;qX_fO}`WzPv)yxZu;v&LjeEB$%|QJzug+ut7pMB@JqivAB9 z)zAgb!j0`M?A|j5x`@ajo#zY%m(yzl4mz!eaK{k<+3G>|u@Wj}}N*rtyB1ZMM z@$LshPv{%f{@BJvK~HcX@)@ycs#-|k_e5}gAoe(|E8l5w)C+P#pr?oiu(Y3DU44rt6 zkU$!K-5(HbLer&3=GK&*k&_j;#O&1mFiolTY~$$`b9qLr;RVDiZBdEbo<(y0V1Z-4 z&Wz$I^vSX(bah;e^~m8Joni_mvk4Y=Vgdrm$Ms?sx{Y6@{LDh%|(y3+pBt&dpN|noL2*>$4W5 z>pjeas#mU1R&$zE()4UH-NIUWZ*LakZm$v4%^#M1J>|BUY~rH?6F@IxP_$h@SJ4wFa&h$?cBa?uC8mRO5GI621!fmL>?^Y-49PddxbG3;3WG zd4AJ-%2<~hWgs$hm)kD3A{8>io$Cn-D*hC8CPWE^XH{a$6n5Dm@qm1xVRp?_?d#1U z?Vg`xbkqMK-xlCFD&Bcqlc7yyLFD-g@Z`<}$bOV`qwK{3#N{%|-{SLCG4pO)$OP0x z(!0JNe-Nz0IbcoNyKdCl7kAG8xm1(%GlU__%a4H^ zWjIr_#4W2vjM;j?M-Rhjp^Fl0Um%_*QQg{-ZF4kjp&V;@UA8kqfQ}KCy3}>rg4%RS zJ?x4M{U-!p>e+-&HdJCoCvOC}hU^Eo%NjddsJAbq8kK=U&m485=#uF$y6=31`Bklb zjbsrHbuIg^iXo|-N8Y?c`Q@L0yhpS_uL)7cR|1?zvfIRRY`FO#H5h{hQCivrNA~gG zmyr}^@1;7O?!}k^wdF=&EX45DN;^*&zj0!OWyiW)X8ANUAwyDb%WJ)n3lrVxTI5U! zOh_7u-j_kjK_=kUAo#jSN*ChYxgKG@vZ}3P1T>@Q zJ)qKBZ~oq8KR=PnWt4k=v<$TTatq{~Kx^v%(z+&2SmbMkXKJ9~UV>uSJnc}!xePI} zy)`z=TxxU;f= zqm!n76MV?;8RPz|eMSgFmR}Y3*nDM~&^+Y8@dl!kDJhh1FUxk*4BWz7=iYhU;5vI4 zmtuP!VZ1RqeRz6-ysmOEG`{#i>`L`}H{MsTTQ$;vPfTb1dA9hJwoSf2v9v@nd8~t` zcl6V?VHVYwO6r33e@YP;GmCOg`lhdZ9d?BAq+z*K7X3r@AK?Uk=--G{oVxG+AUjn=eg ztk1fw89$lDXIMy%b0`&8XP(^Z?C|QJc1I7Im$0tY2YS|^=(lgt%I9Ikv~5_WEI)ml zWOpuwsy*p)i9VFgK|&%`QX$`#)`*gM83NIK%cj3&7qp6c&3Bg{ z4gG@3qzaOgi|@V7qZzD*r}=lA4%|YTL&}B?vGumPV>h@;X#H_^!^Suoz-hW9%9!Lw`5ci& z=c_j?!MI|*pQydxXm!D+#>y`c=PEJcD#>?)z|v;Rl+b`zBB15pv?7gQ730URy!9iu z+`fURDmFElz*L(FRSG3d;(8@ogA?!EmMl)!oJ=-}MsQ^bDS&ShT+8W{39jOsFtX!b zXpQOeEBSy2Ak2j0j(lLV7^8=ZaKc-aYjwY`wPr0L1AnK7I=njkDLZBN&$(=$I~ zOtSGzdM#Izl4Wyi+aQX+YwkSS&ZS)Q)o6`r^>b`_8vV@A&N{qh3e(dD2-!p@=!COu zS~|MtUQFDxEYSq!({GZfRkaoFmk6kI4|xWsoe;dRaSXCne%*x1dDn0DuDC1_SXnXjpkghrd0{-W*f3dDqHLD8Hab8Ov}BO} z5~c~N>&4K#@`9Ie@7O!vVxAWdB4E45+tv5Fm%kS9-0HLYPDr70FjvQ>K|izF^Ry*> zP*R4nrrI|C^0i(iB4XA5keLZN`S4eFfB6?&hnJZ=9A_y&K&H$Wrq}+16tlZXWBB)( zj(7wd()p?NT>%kYVFBi6jg+$v>DPYTUF}dAeP;Ow#)Dd_YE}pD+g}~y+hiRREXoPm zF5ie+2Sz54hRkZVt)gzSI@ZS7D}x61&nc_@<63gbCj~vVF;#5d zlMTJY@T2;0toM&B>t(G?TRMs9OEY}+?g+AL=l+6?aIpZv=|{ld;K=<4xpdelFfkW^ zHHin76F?dq+p}aC9#P}d84B$w-i6nv;^$d-c{oz$S-sEO`$)d+L$Ej>qeLj3NC=G^+05)f$&RuD-`X zO!02-7`TH=-5xl0`W}N5@X{PfPI)CSc_6<)epN&QSw+^}rAx)=r?2gjFwtp6ce>Ek zubHixUN#PGmKDF(x2P=djwxc`A1WtB8YA?8?)KK)F!tbW&?kKYw&J(WYsLKTRNVOC zZ{^r%#L2aWG(IQoEVevdTA&vLZw_A}rrlkfao+GAD3trvT{vkf#yyAW=jQQ|mk*_6 zS!9;TL9%Hl)TLU6RZ>aNQBaOro)De>juQLK(MsOCB@J`G82bA`-(O-t<|nYHxZf+g z*+n~6CMm8nvFMOndV&FkL)sKZn%TGDn#9y$PHCpKl?%Q7s$YPyl5(Ngc)(cg^C5j0 z8zEZi!Mo%Ekk1Nr{5WwXe`a}~iU#JFp`tC*%#*f;oLQo1eiFx(CHQJl+)l7d&9-AL zSmp=?UKH|~xP||8C%^)uA&xct_dC=Z2O3)$6^NPlI0ea%NDz7p=QxNrt~UI>d5t0D zVq2vi*!_S%Xu&6>PD^6B#^Vl60c6tEZ(DQ-tIIi*Z za}s2oeO2v7cKm}zFK+2Qn*n8ln=USPYeZM`-PLZ&jNFS6XA1W1rFa=1IIK{KIUHFq zNtx%pjR0Wh&$EHww(5Mf)BEOazni7?2+K*F!QV4wLUs@`@o+NHve-@*%KcLF@~&74 zlbCIweDZSVT1gEMB5$K(>kFp1gwaR<*0_PSg&OZyx-EUA6SE{AOWlcCSvc0{K)3Lz z@|tb?(ZX-zZS#y9?uC);C>$$I>6CkSiC7%*J13>>@*Y{QL>#k2E-Ih}nb6A8QvJY& z?31`FKQ3yrZeumm)Ddw-+F>cm+`o7@KR(<#({%@t z1wIIObzO$~r*xciZhe&&zoV1rl~wj|N&d%xohl`paf~flJYfhBM)z~6(W{EPB1_9 z$T=TaH|&G;MFJ|7Q#8G`m4LIAMx=F9kAt~HCzHxlXc}JK`o)amZ$~B{JuQMS;;vmq6 zzb~>-CSq-SJa_6S@;K3=leJ-qKcM;XIYaNL9-^C3Nn{V2$n|IqKTBLCGM;I%-+A7! znUJenH!rLQ+~2)E3HuggGP~AjC3Ll=9SiJ0c9dC}9?0#I7PF%r&t}MKvw-cOn zh$tH~4A`V+`QvWn#+Ce#h!(W82VN$(h34gw54`9&w`MoYKvt77()bwwtUq7OppUEH zqQ@@T84BZ~>xciP-KIn50_OQPZuZz3t?`GSi5@gj>7#T{JoE`lhi_Uh0&bx^b&Dch z($KHaf2D<~UGqPkqziM@W_fL|UF~b<@;rqKdQ0zh*j{&DvsONmiRdEC$mIrKwd#Ci z=-_)!Z`U;XwIo<0rnYsd>RTYiQF<-3K)c9J*2^ioY~Vh!PWZfIuQ$xz*@nDFDN zCNUHAn8;+B;Ik#(qk@~I%h^hLN;b*?y4V3Ti~u3)o>_(_g+{RiNe{`mIrdWYglrUE zbd6iJ5c5k8KRnqc_=dru8zlu4$@h4i-y%-cC+XC>N?+jVHfEDo^e@>CbWoB~^()4h zc$Iy9E0(bOzm~!s;ibAj-47{K?SMYA`80vAfD#G|7w;R@+spRv%WC@*=PFV-vw_S5 zn3q@C(`j1hXK74a+(2~B1*=Du57vB3C#L} z_FrN?vdj17jBEhER1B4pU)T_DLibD2d)IL#-tF>hIr-qmgIwM#X$`4VDr*&^;l3=q zS1EM$>#5nm%5H&Dj={G{_25Sw*K)f6S)~G*+DrGT3|q^80TlDNi(w@qWh(Qo^h$Es z4W5rm+!7Iq2?IU;--`jkUn{!PMcju}Ge9ket{a6I30U}#ankqto3 z&IezGn%eHKqeew}w&Oq)O6OOkmxUrS`Bq~Cp6>$2@$Nn&$WjTHOf(Gv$x-t}>pEv7 z{Mc?|$0==pF?=rbvx&kNJUi?`OqHf4I+6qrae|_Sn%}drm4?8qQ^P{;iurc4?)EGU z8X;oFe1{LFjMRG8|TN^1tL%i4SDrxR4w75#77Y zY`c5V*~?|^)peYQcy1$mHG8cmDh>7QGvz*QrF^aSH|i1+D{>HsobQp?GWmzB8qeujTW`M-&bmAu;)LZ5FT^Lc!}P{t zUMS%?l!bp)TVxF;9k1<*L^DfA3Sbnu$esKLlPJW@^1u8q-1)~X`Tt=KRnpYMkCARB zCW`oyqmcgq4;8L7W+vyXUP-+L6Z@Z;>aUwK^!(p$RWB}J>}Mhe34=LT{e!!Vqbh-L zfxMU-o4eGmgs-;G%z+!3w`==1y)4hgjn%c6e{cfEh8(rxCFHkt`r$4gY_J3)?mLuX z@0kGfM(U8(!~wzTY93FJ|CNyG=V*^ab@1M+vy{j2jG1-MY8_fK+`S znSBv>V=;Xz{s#xY$e9!usxw7UWAjysTXTRt9< zNqGi|S&H_B%j>G0?W^7e$UVt+=E<#^1R6?SjQWw+CBX`K%_%Kz%11+@cBeLjAIJ2$ z^_MSC9#fsd(6E+Eo-0Y;Mc?Kg!5x9@p+D+!dr!ZYFxD0RzF0Utb6=hm8GkiQrJDOk zW-i71c9rNaqed?Vz;=Zp>FywxNDxT(8=3xgCQ`p=-;KE z5B@f|qr8?Qaw4_C*&9acJUaOF+MS|PHZ-X8M+P_VgpXEQVET|dPm7uCQFE=mJ{@sP z5npC@@F>Gcb#qLb=Vj%&X@}6J7&p*7!|5=5g1MB~{TXmldH%vv+FcRRZpUymY;gsJ zV|ZBpe#Ar?KX$c{?>3zj$h|~*qO?HzLx8>2I=U0uz85)4kV2C_S^-m=kD5nATxF|J zEHxlw<O;V~TBS`ov)^yKmWgrLt8Hqf}l(3y~L zxA_}n$CM3XfUenfEwS9fogW@2%Td+jq<+}F%s3;FB{`mIi_r5=I`Rb;RadK9s!9*C zc|3hSscEmV-5#{!D*v+k=LA|sbvDAcS96qz6YxqIhwLJ2R2Jq0Sn`>&;g0$gN$3ivO-pZjBFsIiYwm(1Pwf7MeeRLpfnsaQEN#FKjWxy;+cr)63Cq1M6ji zhD9Y7?nTm9lj!f7tGHBJx+vqZL|YO1ijCnu@zq;QH0D}qikb{+s5`$YR`-1JG>63f zziZ>?IOo>5jBbg_gTt_*fg;;g`Q24yp366CY`zDBM@D!n8f5nNQuRv{`LgK7Mj0G_0zz>kOwL zltsV2T&%SwyiH=8S&IB4P%(n}uG6aR^hmBxDxb!P_MB&GL3v5~ZAwI!M$E)}wW;d~ zdD0y-i0e3O|9*S;1ne|E+bdZO0QvA6=5i0as6vFK04p9a!t8dJj4evDup!3ECZht# zmX&=go^Y1KMbtl|-)1YmUOe5kxA;VTZV{U29b-x(e95H}2!k0s5YId|D2P0YTQbP& z+bN%WNN$}I$&&1(pWqH_5^~O;s}dRVav91tnMY2BPcvA<#k)n*I~x{`F&ay{lWv)8 zMY^WnmsDNp$yO%B_9b4V^%Yvx4QA3uttnHu7$&Kmce;oH#_}G9gyb|;`tb_Ymq35ZDkQWiv@)gcU{oa_ z5Gpj}Q7&IGp|oXdMvOU!fPSw$ax!jURZzjnla5+)+YY%H4VwnMpIeIl(AMGAu)n#q z8`Ihqp}0xBY2=tA$SnDrLBdY~Vz(y1lKkvscU%)W)*dDEAi>ZuGoj7GFlVEdGhXen z=B%>_gz`!`<{`dP=&s?(B&8?949gvwA*uDcM7>R$7s@R@YP9W4WpUS9M)~ti{F2v1vW^xwVRU#-vWR9D89s*r2%GEYQHJv9hEPe;2fT+h8J?2p zIuI8HErn|;e*r_FS%}!h(HAM|o4OQl;zx1o;?gm1y)`s9~H~`Wi0NN7GrACZ!t}=Qwb3 zb-Z^;h=0F;afYpoG5*tK556#%xLvg&qpKGD?{r17>OPHE5ebZhLEsD%NBR+Yd<~E? zyR3{-s0x{>YOA)5yTmHX8Xf+OA78U3 z4&NM!Ny92f@bM>zQn+L|6R30gteMfFK^9WV%udZ?0;Wo1-%&Qw<|8h-+(%gGj#bw5 zL0Lk@|F}Iiu94J_iQZt$gE^Mdp`3(~P9AY{5QL0xBL+nod8&L+Fum^?x=O)Sf(SS3aO^IWm%B#feqT}VysLb*W~D2yPa4EFwPePUwE8;S{Gzk4146Z_A7S< z!~YxJ`f(^%P0umQq?Xt0Qf_Ey5gPs=ZlBEj`zM)l8|E9uY6tV5iY0xQF5aT2^pZbv zQW-uN0z@&&#QF)szZe}8!>VGDUPp!nIa^b^33xlr^6@5xrbIP zw@kIaB~4n-Gs(&iSKJ)<3b&I2KJ#AcziEhnE zTc|G`9GEnAYq>P3cr*GS`w%91o~npSC%#m8yw3|Ja*U_1z>-W9l=ONiJw!|ZJw(*} z>!m#CW>iLWfmY=PB#6uXB6T*q;)SjjuD@bp^wJND=42f6mNWGf`rcLMUMEs|)jR+^ z`<@D<@Yt9(1>%b2Y(n>4A&j0E?>ML7pSd9CWpVP!BpZjKtB&Y>2&Y3XYO;2)6le8dCi2yUtFM>>c?^`fW zN*Sg~KKiT+nbOxzbAL&VyrXqD6E0WVb#(mNU+zhof^#1k8G@BUE_2{zd=CgG6Y7Tv zxo#-1i)uZ%^(BJ>4bmI(x%EmC^e4MV1z^rVm5b%XTyZj)J$96L4bW;RUSZhCJ*dd2w7F6~*~>tJWoM$DViH^0}%jfXwAyGjEJvu9EoS_om2^5nJ+fS?j>v`vFR-l34bBde%pD zS?{913{Ae-G@}PyU2IOp!3_O1j2rqImSmBMNoSTA!n?fR;7^|3_q?X3+Gv%!`{yj1Z zW9YbEv|Du$h1nRGi&@r!>?<8c^Qn{>P6415pqcO?2Hr7An$t2GruY2K3 z!?sU1lV6Q5jp}E7EGzqgHPVlMhr)oK$Nn#&!yM_GdAP5fR#V?ET*(NcGOi!uAe^^# z=a)h*|N0{EyfS>9t2YA2^G8c`d&uZ$;Pi zv-GT>_CD{1LS`R3g2N5o1Ty&(rUxF?jB zwp3dl9x<4a&seu*t)3Q8hob8~-fA&O@*q)MuH@-6pVK14;kQH;z14s$$O5+D;B>UYW^HS`mgx9@DviI9!=mJ_T1|^jP1U+@AmAxCi+P#w50zKnl73wbiXKcTq$h`*zF4N5dU2^#xUAlI8!yPFXDXaKhS7l% z7@2AzPo3pR9X)dro}HmzmUYY(s0`dlE*i8KiO()d+AnAn^sGw|Y)Ue(9kSVNPYcsi zYAyR{&i6v?Pn7o*PVcb)_5w1eE5)LnBuRCoQ#>~tn&ops)K(h2I^hn zoLJ#$k$@3I+f%-6B9@@u`MOXGQ8_LuUkg8AL;b!@8{498rR$P>CS$&r>JKqa6N=f=mYR?0F^fw^g5dq3 z_%oym*$ZT3Wn>niD(ZJZ<0wdSA+bL@@W!UQfKCd6-VZ4TW9Cg91cr@%WRs)K<^%Ta z-F+qs%DPIV-iv;`2GM=JC!A!@ts-Szu7$+Sr{+5|7XqVyu^C9r9@1Ypl_>x z3)@HP2d5yn%N=ri+SZ_YYu~-q<2Uj~g_Rbiin@I}My`qk{!Ut+LUYeQ@wx8T1vP}q ze-{3o8);}H?p<;^{#4zwRjvS?F!V5EAW-X`^j(zHQ0ks+St-u*&W?+VVtat*%$c-*L{tcN8NY3-}2bd@x`&a8W6b^1kG%H6B>Fr8*~9z($n-qk+x{ zMt#lG{fe)#m5yA}FXwA_y0C{p8?iS=~IK zhkv&1^qUNhRyydp)-B^9pg^2+_nIT*4A)xG&qh1Fh^G(aRQ<<3nBQ+;VmJv;I(CVq zeG1L=uSjT0nvhaogU=;tq(_gE9xk2kYX$dAE?ZA|cxW*-YFNcqVAOX~;6R?WprSW{ zMfNSs&aliOl0@U(T-BQdU~Fg?)2*m!oAkiwOJl>_JTdn{T7^_3+dpm|4KWlXI{o|b z4q0z6NnDe{S*wlV331P)QE^Hj8n1xpT{ql`e~#B&P}Nb-mu&*mdbeNT_?(v|>s~Uh zV1z!dWr) zeb|77$9CS-AM$WjWACe^qg2z0rGB#EqI%Gm`UK!0Xfe{ErU%gzG1ixlLA|ByKa3jS zl!gMuRow7f6234cs64Z{hU{XbaXMHrgw%ik*-0L-ed>Jt&mZE@nB$1nGODlOu`+U3 z0b_{i!X_OoZg~?3bm^WC;H`|aRojCw=Eg%%>$;7Z=%- z(c&CZKncukJx|jtdRV2%lP{6emZ+0XYg&9yaZ5eJ9ubBl`Nyvs5i!(M)`+WL#EsG& zp88Mf;`aSiynT$$u-Sg`poxEOin&u{7;Q==OC^gRb1L+UJ0?a;BbE}&{_ULGCOVu@ zRQ_y*5u9Ird&_pyc%|7l6ccltkcJzPrt<1VP%5xP*0N3lE(Gu@z+1@hkMwT=z*g(W zTibNeZaL<7RW+BR2}D-=q6fc9#*9&>N?6`>wkeQ26_FFU2La zh&6%B7i@mT8-BMp=tOOlmqQe!kA#f4KDt#!RUaXd2NNg$3_#Ubz0b&FuzxBdJh8PQ zzULM;p8YqbE&Va(;zX(n(V$h$JLlV?T5fk6b1>(k*RP)ioPQfpcjh5STgjBExPw}} zjZ>o4wvn2$aYV29cw?P=+cgaLl%&y^m9g!t#S6f8=2mmcGX zWIdK2!iS~%Hwk@I-79XN9B~3EAu*Aij^kOLLp2_qpA=V_f%gyEn3p<93#5j{BL@34 z@j?IDB=Q6&@U5_zx~w(1U;{)kZlC6F%}9{h#a`MnXWRi&(xILgsNZE%0W~4~xXDA0 z*c5vmzzpagc_?R`dnNP0dj<9Vi(MlQ;Zzz#ie-|9spm~`G2)Tki73BH)~X8E`SkoB zg&5f9_NAfZm7O0lo@C`R)07w(=Ia;p2;$nmS9&&82&mY(ovUm1il;_&lPR^?e&Z-| zP+1-OC42L)=KKm~w}fF27xGa&1Y^*mb4C97L+O&T{qwdImi<2HOiK;m(|G(!n6?CB z+3AY;;kTfUP^XeAG_&tS;#V^f>qJi-ncV5CX8&Y_u~YD{0Ru3nUP!88OKRTTgQds+ zb~FVcBSc=&E};cLcft^H$n5_qJ%+ENK~OiVn#sBMiK@Dt{vnk+vZgWn_SB2Y8{&X#OGd0 z7sfQj5gro^CdAvx>h3)bD+vKm94p%2q9NGIaLzLp$2<6ZMx#!6eN_n91S6>Kd9pyz zN9+&4^WUW&MFXboshYmS3v>cOwvJ`(|MI*8I!uKObwmY%x=sjy>&gQ>761{#qk$x` z1DjtO_wTJY79_-sD|ep~Psf#RO}eQHNUAH@zv3+TTr<{(c2c&r0dhN5y1fK+j!c>;c0FWxsP`G9PDx_+mPZB?0kE9&ym{J2v$aUrNrq8|4s@Ewu4 zZbg#*jDQ1tWEm!zrvab7B#eU_p?pD48qd(BvyN*U`(P*RBpMfrREKqO{cS=>uDFH} zsU#jxY(^kV<9Y1+cOzzoNQ}vz^ljUETSDeR9YBYA9NFvYtN4LfBO9b5cxb<5vlrV4 z>vI~eH@nz)`KO16688Wz)Cj@9oFti~lw^z_HaFunLb|%Ffrzd#T|Xsh5l12Lnj=Qb z$JeRWs-;_MeP}=S_an^zywkh|YqU;F)c{fDgfpZJh@Cby_s0rR#3h;`oKxZ5CB!a2 z0N+#qen}HCA+#!}IzP=b&Kf)|*8VmThk3Z4v2Tm2$hBk93NLcw@>4aJ_-#G^MTLRT z@KmvrC~0>RBAqs~meA7|f+}p4vI%KE!ezRed@jd$!2UVFo_fJx(Z4vnB^MIH9#1zr zTm7;~tMV<87s12i*=1G2p=DI)jR#^0f{<}-$Na0L{MyL_RN<$B@rQHh z&B{%^eTxKSq;JM#Fb4PC(um-XE)UMmLvO0arphI$znsVN28H^VQfn&RjG8j&RLRb| z-Oia)>o+C-i@w-ESM_LT{2Qi~A*O}a)0BU4*1cB-&f-gNCTtF1nnCZcLH+*Qm! z%7x;fW@s555$lo4;+5NV8ooufM&&+c*U_e5U6Nu62)?G3R`4>!w2l;#w8`TlW7e3K z<;ZlULlyMRN(TLe=qw+w$$tl_Y>3W<5T$B;zhOe=M#SJf@|5%fc}c8X?kH3A1qFKzRup-G@x!X-}1zY|ad2W6)qr=E>bX zJ?3C(PH=({vm7<4)y-JNOu%<6G*~J`B9yO$=dMRB^;CoL;-HeOBKezBERswTjp- zjBf;N+@-5$5wSdVG6VTj>1u?9ZvRlYTDQYuBf*?W40QJ*T4Pg*vBiIY^GOYUOJ6D8 z)wqOv>&WEHiw}~v*_Ch6eQ^tl++)|B&tcL7o!sYisOZJjZXmlmeBV#*lwvR_@N!IJ z#v2C}VhPd_(AI8SO4w@Pm_y9hKe5c-v3m1*e@ zuLg()0~gR=hy$r|XzU#~W+`oPSW)(93IFXmDOPI0lV%e-aR`SoXisSZYbvH^OE-0D zIu7GB>iG~&txAuwXi2KE`VlC{R`GSJR{J={)jTPR;$mO3YtzhM;f8oRf^%N<0ZM@Z zHFX;xC}>+D-m~(;)s`+Xkcn^=K{#Byi9R7@kcfXjM9 zO6OSp>SRC?;jzhx2>`tPRtjr#pBhW@)rbJwE82tf=S_=uhhz!IB-or(#Z1?%4iOjH z9l}&0k;U-5((VldhD@b8%Haq=j=1;MhI$T>E4);l6M}eEJGIcHO&$i`R6yYP5aNwn z*q|N+n_kMXtzy>M=;TM~(F>Tu6@#c;+xdD2YVYemkqG;zE#p4A$vM#+RL6@`MUJE_ z5eND^^#PT_Tgg5#=|E3+t1Z$bvvs^)b+c9uEe0lcV<>gW|CWcXY%L{>uxyz^s^SDn zT3?zUiAtUlkrhx`#t)WV73NIte}7hHic90aU0b+?8c)JSs>%-D{p4TJaOt@n7g4AsqhFKoPH$~DcjCK4yV_N zLQIX$z%lhf^O;m@ig=YSiINEcY6pu(+87u;R+bcPc9TX=rZ5Q%;qH z>qNlc^_ZD|^D@Mlx{*VDvyxYM9qd(c(Ph4*;VsA$tMxalnWybGsm132CCck5nUcKy zr1);WG4BUX1YNPrMg~@x&Gaq()2u_^oM2(4H+B;XUyqGvO*Yui?&yCH3Ei$R4#1caQ*(F)v=sl11oA$0Ujuqk%iZ$a~r0(8LN5K<1YMdfbc zrS*!vuQ-E$ayosK&myc7zffn?6RPOC0+p%2`DtYIw>8J`Q&j4&y^JHm5;twql3M#2 z53eydFZOa7*53i`QCN|SNK3&zZY<%;jNGs4i$GN3L7M3UD7?1u@E5&*?eGiX~WK8 zB26PguyjJav#8>iDq2Kakg4%AJ^qP9yAr8Ff2S}+q`jQboOLP}Ek4tTD;vXrgIq$( zC@v+nUz^CR(#t)Uq2k7j`7#tc1v{^1YpuqJ0tH9HjN3jD<+Cj|9n;#cc@sH^ z>G;H2yACkcr0I_ox$C}KhY;Jz%JVUkVVPD1nJ`QOimU0@L5(Fb(@(K!ZbZtI|FWp( zT}eYT?ny5dt-4`X>2n*Rsi7VFf^Yrj?m?(Ob>@-=VWZ22%?XLM!P#O;)~F`-lB)(d zI$w@rZt>Jc-SSb2+V9C!qW>^gNaRUK+CNC#I6i};K-uJ-AuEA3WRaaN^TCb8TZtQF zvCoqOKs|(?TA53%5U8V|uSu&ATYA&AX#Fst@+qU}rzah_RJvxpoR=kcF@&U+P9~X` zpBN<&5SiyjvQ322C|si+(TzZy6Y~OO^Y1&PALqI#dm>}iw|6tVyk?$YWbQuDK~5-U z*oXZH&!~ixL&LhH7|+iME#sU6P-JxOyY_f!u)ro&E!lhpB>7TwFXBfy0p9D8 zk(#G_p=VRgm3*K^i#qy;EO99Tg_4@KMFg_`JDEcxLE)q)^jrJO}P^@`~Lmlo&|h2)$nh`Y}IUG zJBp?45rw5Zv~G9l;Jd&T0defj#s9F0YI${KZ@`DyWvr>nw1?5 zx!+{sad8hGs3+|a3C`c5pO6oQ zI1YgNBXus3r#J*PNy|vp?5NS_&_rh&nc@|)2A4`~D_$&|+};vH)qAfd)*_#KV18c zOhQ>6=GEP2LQ0@ZkXCjBGZAy2nqMZiu|+8D{Sbf<1@>(p&zT|BO>&Em^ed8@bSz4z zV}6ys@cniFv~6;8a)}sa8pR!*0#WtDxF<`F94JZuf*$Cm=od&m**j21^X1M9RjrR~ z_~e3iGX|jWx!4$k*m&b28V zzD|NZkU1Nm$V()vL$PONn>>2BRUv@cFPJB3k;E5w7#Iw7y+a9A9M7&RcA?BU7j5rN zqGl(}lXj7?hN~-v#=RsAlyAno9vgb_1Kpt4K=JNPA%doLPxetzTwh9OoJzc^E^V1; zNA!@c=)fH%nzBHU6}kI!@Q@R!v4DZudgTt)DN|4FS$j*b%Y?9o3t1-SB-LMXio#Pg zrp#*4Z0%PA+%ftK0p>MRCERj8x~deX>EyncH}GaFDTSQ?iFFaT=%H7) zF<=%no91(F3W>YfnYuIGy{|k(%2%9?;#Ng%burd0iM1nA&1U?=MY3yL%Si!1>PRW0~>tf6>|Y3r4*| z<*&MNi5G)My)$F76*PGWd0|a-j88$1ne7l3QB}b|W_G~z z_w314&foKF9`Kf$okKCPvF~#VFt=#}Ylv=DqX1NKtDj$!#b29DBQ4D6nCcZj)&DDP zpgR&wpEcCBZO+AIa|M}dBIv)YwcH&Iwe)`Bl!`79*C!}xmwJSX&xT==bTxn8=`Kc{_>}u)678mSn&S_Qa%3u20-Lnl@g;t{TyS0~G0vq#(I*f4 zT%xo;SsXM`2em+8KIu;YXPz5Yaf~T-sR@ip<-1z^e48FsCKET`6>V1IeF#gYjAiTR*yF z#G`k~WQAQ%Z9y^8h#h?A^_5iw|3CEAW?JkGr2Y zhVkB2({iT>+ANy>6w{p^;38&%IIHIu;k}V0B%%co&R(^*;&}KdTlQvCK<^om&NFIRC316+>K^l%^=&V zX}YfhAO*=bO_jDL_!iAkH9HArr!kO#43>XLLe+=m|4%9B{m)kWH}G2rYE!f*iq;;j z+FNak)`;0?Nw}?AEkcaiTT#@C-b(Ggi^LXU+_s24YZEm>$Tz+}J+J4-=lKK9bAEE8xQ4nT{dzNKf~n(6S#QW%=6nI&zwg4? z8eJl12Yna8mW9){i}+BtN2laf)kSf_)(ux9i|6Hv$AQqo;@SJo|3r$;eW*9(Xxnu0 z=2RlQR)S}?c32iy9P)HscuUnj&wID0upV_^a+dFoE(~os{9!zDV&AL;uEdUzYS6U# z@o4srYeY^@>O{kgjVk-Nn39Q2yBG>>lxbryzeMwM-#OEz+(a5ZL258cpu-ZYne*S7 z{o)ZleIoIt)desh(A9tME#y6cEbHw6RB}W*SCXT3FtaFNrQi@mFYY|aMr*z?@Q1Pf z9|x0!HA?A6F5)HpXeHAC73^9DwGqFwTkMV4+6Gn z6~eNT!$TP}4+u=0_x{yaVUVqaGYMs7P4Jlsx%!4Y@Rc-bx7^O$X52Lhu+FLf@fD@9 z{ff?#M1V%_<8yj1vx4zAVfRL#DR%I3Hk<>$4|k`nNPiW*)=j23IpKP-e+xM3zm_UM zCuLN{a{FblN{wxRDpm5%De3*P79?)@jJIWkT*~Kr8Itl^rD`PwxVyDQw|Uru+0zlw zM#i$ce=Nc`$$Zb|_qu`$hDYTl*nvD&nS*nZB-L$qFNFAQyV9v!ICM6n0me{_67D?; zDw=9+CUDQ&vc^~{C8{8fkqx*?Q3tcXpLXz(Papmh0O{%*nx0Uz?zcU9sp&!p!d?|~ zPm92BrJREK-k(W6V2j{)v%rpif%z1dvgJbqk7>RL z*OB1y&x|sDc_*ftv7M_7G}K}f^RA85{ovceDFX$+kS#7|Nd=6gaNQVf+2qDsMuYrT z*~ZnWx$G!9?yQe_*q#oCK#!S_MHO{3;JWJ7+7Axc!G@k4x-QHUQZ@+^%S}j`vY@Yb z)=u&xOGmM4R_6#fr!{zT8r!ewjks@j56^jlSbmhDA<@{b5t@Wzazf0Cok>`vmJ~_# z_!Kow>VqtdeK}#u$C%mpinmk*Asp)PYnD>pT#-Fh?AraA$}`*FW;WWxW|Px1_u`+2 z3x(x5`TWT#G$HVt;_0iU<^%o|DK6)o@ut2vO?A{@q&s1r)N5C5CsGifZ`?5x>E&Pc)LqdGJ(7+aJ4`}HmjzEG~P#Q?0N zU?|N=QsvA@V3#gkU7BLCv`>m_rk>-Q_xkf|zw#W0TjL_r|Pu#rP~^R2-9N5JM%qk)&*M`3Fqle^Wb ze*1=6U>bDQBx@td2r9FscG%p<&*az6t;Hj4i{;$ztBTiJ-CBxUtfh=Q7-^_Z(lUV2 zHq?3s?N2ifGCyWLb%-&1@R+iK`Ss&h>4RVEbs&qx<)r;ZHYGcMZP={^# z5s<4B`7% zw_zv01>ZD6zIWK9uXE%M2R*tZyCyZ~9CUAG{Qb!==ln8(1zZ&@joGPT-5$7z6cz)h zbtd*@)u>-=vn)(!-}HqWtnd(!#54))j@Yc7VyzJW+B?MW74q@hr7Ah@2cvm*+st7VCyYbs!5iF}dfmr1M<* zuEm#E9WD#UDe3Y#*QQrv&)?8MGHaM{q+Df(JN|h^Z1;0Yi%RDNTiWB45I6Ml8^0ep3r7ikHsR`J3k7;;1S1#45 zpfK+9Tv^&m1c6QLduh$kLRC^|-(}XsW{b?&+ndnmh&N~1^LWSd5K{3|m=vS*z-w(GE3>kz!t*8KO1VTez1Ic4K z**0MF2nC1=*VY-=q)4FJVL(D96*&t54Xs<{;rP`5JIsOK7H{*I7VH^6_S8_O0b7&L zk?I5Za>xPR?($1wLp>`lwKF;M{e@TOiFieiD}E%`HEq93nv?06LJA?qKyxs2=x7K%8l!MC7wHR?}ysS9Zkt;86-)vu!ARZS$ z_Iro(EJ-nI`))4pIXzZ^yK*32!6;Igs_88_fS2=1z-&MTw|-mnNlAzG>cQ%%Ed}R#c9!_+YjtBOe(!jmrIEU(E|ncAY_{=HAIh7MRt_~ytM1!c7+WRqir z>-MLIiF_~rd;s+vqWoJ86vge+M$cn)2$t^xTtB1#}uS zBU!_FhPyr2iDcIj`wBPB+7sv#D_ah2N;-ol8J;=ZS}(KnIoq_X6=G*&#@fXcway^G zdk5m0N8PI%Z|PE#P?gW#;PHvAt(zlv_Qxy!I#S;Y!)t9F3J<6;ra5%$D=5US>6a?- z5O?D8p!5-EUkml}O=fj1me)|Laf@fpYtdMp*`(ckwjO=h{qfjsG2KM}?tb~C*11@$ zif_8jbbg=zn*hzD-z;g$@J&roZ=#HJLPAGbk{}rz`F!cqZHb=7`!|6PlS0?aGgS&#t>o3 zPa&^_=9VMYY{R-t@)MEVp~R)+jW7lgcvTiSG(ZNIIC^(WkE^DHhVL;gsKfG}I)^*| z(txfj73I11Q_tY+QRGwBqyi?Ao-Hp8Ry(_f%re+#6KW*^)0vt`7F;*B}1SA7`{ z_;J9H)fkvKgsJM=An4Qe%Q^3TP#)Nq2C@gy_FS}-z8xl8B1b@OAz0|wT=y^BuKw0L zGv5OLS3zdClBzW2f6B{N^;-)y?j5?m)3oLG`2l?9@4J6mwk`>^o0f*rvJ84cLB((C za^Jpo%y-4@I|wa8;G9*-2S2u07$BK^n5Ke7bAN-Sm;^y8VhQXQRW63z=U$C1j4SUIM8aSV^5q}WPYZ|2n%C!GhcbMS*_+XDRGILP2 ziB$RU96%Uy`l9yNO5#{YqCBUtj&ga`C6NXuA0 z#&$5b%r$|$MBDw}H`)`7X zEYe`r`khV2i}sP8^+C*HtN-I0lbbsuR~tx_Te)=DbEo#uKdXL=FRS^84|R6Jo7;GL z_E&!V`mo|gJubjM2|U_1mEt{Hw61JkiCaXUh?rR!6`#wmGg}y;W%3A+bmuZ$9f%|{ zW)RGk`!?{~ka-K{XW0VSOA6{dc`15ytP{{fm5&rdadEj_i_Kt$gB+R^uR11X6j#>Z z15;hNjN%KMGtaLaE)eBR4$9lrLZUR~3w4`({>P<|v_CI>{8x7%QobDx=N;H12_z>) z&q!LTusJp`@!7@I5VlL^&jJ^bJH1V6UVBl$dy>h?zx>}2-WgNd;2z$+V6Qs&-%&b~ zZ+Xdl$`lWnWsyurv(%@fF;@+i&2X!|3Cjz@JQ%Q48V{(uv=>^itIer+mP+PY+lIhT zTN=)RKWRek8lhFa9|GL!nRXg1DBk~2yu^|EZ`4u)evUA=n2rGV>qcX?u2!p--p~}U zlSF}l9t%1d#%=CvAg@cDR@Qg^PGLkz37dUvZ12M zhLe`uz2%L5Z@qxHnCRWLO>(}C_18&|%hNrPvsGI3YEOw%({ucEI??_|!$}NX&4Abgh#30XP2O;- z*=nvPKe6)H1gR))A%a{j9siEqVZT~yw!AU-`j{x(y5O*?J8>v|img!iyTx_xm{SPt z6{`=t{4vRP5+9%dZgeFq6VO-OC!<1vRpAsEwU`k1T!VR6HuzOyYHG5(kfKNi4Od34 z+54vQ3;W6&?x|PwsuxIrCd_k%z*?OO10IjT+ODli`D=jHS7gr5p#@AhXv3lnVu!D# z68!`<{o$u1OG9TGkwn7oT>S8GcHN{!%-p8tGryZesAxk(Rc%@^6QgEV{DR`QqC;%J zGyD3sDUXVH^VWIKNp^=9(|gq;eC3T9&S(5X;Ztt=fc_VlZCXqFmLPnOXY?+MqV*ux zO!2X25waE7=9hMm(YJS(O9I453Fkk9s>#cW8GPV+J-k35dW|a(q zZaU2^Gx{;ky{y=IX{iS`O^NH5z7hIXEtrZg3Mq_dzYFAdcO2R9^A+RL7Gric7(I%v z2|Xgpj;YeXT+q^lhH+=nda3@FU1y6O zpEktoJ&suTXf zW*XF#FJ8M8tQtR!kF0P<;Y$VBgo{;ZTa2f07dgtat|z@c4d_z54bf8sIGA%r>r&M@ zU|xBxgf+zm%9^F&8okw0lcsca^HCGj-q967*CPbUGDqJBV3AhWiVLIGLMR4T`O@?sF`nk%cX=Mu2-iQez|hmuth;PEbv> z^Qk3FOloH6pt4$(!pkYX002JpE>*^|T}C1im#uDBtM=iaF=cbXt^ltY>C^qgy)+Zg z&xXz4sfLT&2K}@xvW3OnxH>DJn~dO|Wu__IjMgH#W*$w{nTW|kD+7L6WJI(%WnC_K zkFV@xr&lfA3TF7zis;UB2`=*x-a(Zl5FhFIXBWUyK78lN%AOdiO??vwFl7!5RYhgH z8xo7xNk@q8}q0nX|?Awg2C63^eSE4wk;5DeAh{ zZ#CenJ2+kfOG3kx(fDD$7v}q$!@tH?()8W87yk_lP@GIyzpQG;pcp=3@Mk^z0)gk2 z*O`_r!9tV33>_RoAft0(4-j+0`c;@eeN(!rjOJ1f|D&_KO~;kjNzLtJ-FD%FWxVtd z`v9+Cuswy^w8K|++rD&$<*kKcaKucsb#0A0K@Dy`T_z=4{O27?7?lO_SmKobynn=% zvYFr2Hh60bM=;+ZDkG<%|9)*PY?D+M{~h!;h325eRBY*$&`_%I((5E#`{&zsr4~+M zlfuN@O-0PzpUEY__iR6k9Rk{%DUu;vQ{2C5AjNQ zBM{J5b$~RNhlBO*Gu?0S<@SEOE+DunL7sa(E+XA;w$Bc5GX;?md@Oz->-9sDtrn9I zAk;8-c<`4J5>~V*n?(pv0l`De$y`uk!#7YOe#qT$HQL(<{SQLfCp$`-%p71*-YE63 z@{A9|Bl1F&gNegMs$aB3TwH1|834%-myU=U#6%BfS*F~i_MrP!7a@tk<_+iP=km9> z`8XZd#Y7H|zUa$4_N0!gwAE192MzH3-vzffwO9Yckn7ivpDZaCE2N}hi5d&X{Dd* z-s)NAUe;hKpxCzF3E@2HG+Dh(qD5VFK&qc&Dl^YH8L6ZIM1seM2Ll5`l9m!z0RsaEec55K-@fiStDz3hb!~4pIjem2O|9O6`y2&%(^Zotv^|SW< ziBhd{J^sWs+}4DgU}aeHlR~{pAO!UBv7_iu+WetUKmBp}394H8(3UmyE?Rys#u$^>2!hr*E0WqRvTA=y!}q*|LU=FWbGm^OppQd8sNeMMZvjw*qgUa zU+*$uiOogehG7^;pZvgj)&x}Y7WlFN5NJpuI+)3+yc}7> zdZGL4pM$CI$yHqRQoERWGKF5i_b02e-VssCuw9CCNr=C5*AGkIB-Wgq;C=i!D}bvE zlj&o`;vC2Hd_Pda!RXNa&K!o-pijXxfI3@PTv%m@l!rd2$e$08#AnoSS4|d}(Jd1| zKHcCl(c-4$CIjiW1Z%RT7`o3pk&x_9mji(@>~6x?x z=(FX(BF0gefAT;=XjsQ~z+mFzX$4_6M|7acLG0lN@t4e35k; zu$74BL?`eDsxeJQ=i*zCQ22D*Ab#YS!)1$&OwuM#AVOKO$ETJi_zp>w>yXNEXtLBsS#?IDo`vW!j*cF`)a<;vZ+Ql@Ab%w{kZLa;D%2Wdwoe z`M+ucG}6iflBP@xUzEW!UTg?&=oJOi**MZV$_eQG83$U5LhbCIY_aoYT4+0)?6CCb z6!i~BB)ML+XPZEc-;{!3X-E%hJy>iGVR@iVi!%5CRRV4l?cHP`vooIDqU|G~^&*)4 z9I)8FscF$F3ORDi9YgC~^VO6EWA87^JENRIH0{WRk81@G= z{_aTJ6r;$%K2TW7;mUCN`@{;>9@W%H>i{5T2a0OTxXB*}Zaj$7oVHemLI|HTA${A2 z+#R4#%NN9QurI6)>d_GY{)z);JJ%TR+B$Xj2Au>Yp0=fz#+jN>KD5pDft_sOn{5e3 ztCE)exJVmZGvxjYf-~(;{*&t4?BElxjjBq2tSXZvntt$`jY&~HyzU&KEk=36GtOSI zBc%fZGdWM)TmyL%)pl#vjvwCYBaQG-1l#(ux<+}}3dAb*td(T_ehilQcXz`>*ZcU; z0d~mXXiZZ04c6rFP_dJ=-4A-H+q(K$-HyHKRY1}kN07EsBo-7zDH;Wx<*{VnLUdZr z)3vmO_&e9QRyzu|KFDkd!Y#`SHtpx^n<@Dd6c+k4r#oS^#^#Pim2zl)K*o2s0lqg) zaK^~kzTa0;_2R`2PwR=_&xFS|X1D|2q>q(mR5VmNv+&vAGlZ>UnQPzZIw7}sb%}&B zuC=**!M>WKKcD{FX*tzM7FF0W&qq6HVL@20wHN)SL56G~7}K9Vr>q@Z#aWk5SKHf0 zHhk`QkFN1lPZkH@fP4~0692(>Y+;A#AEn(Hy+_YWH+FBf#EMCMGV93{-h#>K^ofdKL)bBzrE~_ zOQU)OTV`&lweS*6_-m-XVx=0+1Au zCd97el3Qz-`#i+wME9?Lbnh!VkQa=A8ef?x=W|N`@pGi=T=qvZSR7QiynCEicomwS zW5@P1t+9AsnCXSH%YpYLJxxxgci?ZTPeJHhQ||s{#tPbXcA4`ZG!ti7erbAIOvQ#+ z9ekSbY)*{zt9G#!&NdEMWUzLU6~6d6q2<0!aRyKrEP|YMJW>3NOb7wBcHjg8VGfO^ zo@G7CfHVwx5)M}~-9#T4)1%yjE;8P1g$uBYhJONrzV8r+68Q8vB>PjG@vq>mj6fg3 zxt`WNESrK__a}4=#ubk7;&tA74Gu+E9?T9OzmmjL7@b!-V4}`p6*bLtk;^br3ILcGjC_@ zdrB(Ght!qxKtJL#n-n< zOh-#wlQLa@hnXz7wY3Ogd?;Q1nKU?xV<8*tKI}V`I&IH1;H;KBhD#yS^G|2Hrf)CzXDjDh$V?U5ws<5k`e^%aC=Kf6R zw1C035ejREAX94pB=q~-`V0JvGsD)Gzc^P0mke^18zD`X`n_$p`MuPZOd{b1GnB}RC}TtGkm+^%{V-Z? zC&ngKynzoJye`GXKGyO4`_;SwvHRA2D=0Ixp0w*ft*%EdKO@HSKap?abwx{UM*9Wg zwtLvzrNxy-ZG2wZw|07Q{JWEiaIUS^jqb*DgO0RM4LyC~+YT9oM`v@Tv^p@_74*dq zs-0WA?9s@~Z3jv)aB6SPhCG@DJ$l+^EK3}!`&j{0UpEI79dNu_Xr9B<@ocpq5>Kk~bbPeT=1I*hOwF69QsRLu+)XU4Q#-yjwn&Sq{O3#v3R8I`ol zp{xV{=ws*js3z9Gp~5en4ZJ1eB($8s)bv{KX>qe6D%ge)R9|?K9^!$_#sjNjI43WY-#Zpda1}(FT+q zu}u%MBTJ9Dk=s1T40Z)9ujsH8*w9bj$bv} zETYxQ;5YAHcmDZiLX5AA1VrX;%Ia1y=-zp(@|9&Zyzt`}Dj`I9luZE6V2kGF{{mQ-B3^?o zF?{@kqEu(Wn@6A=vIP8R@Lc_#@#mf9Y?Ck^7c`3SnA1H6$v(sCgHKGPuh>1+Gp-I` z^}qGwXKlpfexwilYfo4udO8}pCR(rj$AXP zGrXIF29X{?O4MpDwc|xJbD~NM{M4PSBqsRtcDVj-^S0XhrT}p^T+X$t&b9a!#2xdG zsEvG|K>f#5=!P%;fGp-xdvdQqx@zf=Vz6eN}4j*DtR}()D}Uf1;xxF^EW=x#T?Uv%AEV_Z9^^ zDRth{m|gNhdxMTSy(f)l;vk>oKW$uMvLela`+FA`#~IGs5GN0LeYYL<5*6>M5neGg zx{)w1SUUrerpqrqmscklKX^J>GvF`D&p!A3$-e(ajCXEy_J5QcUvq_zM$YYA|l5a2{da%ZxW=Y!M(>IWm`6LT&_QOd-pSQ5(+ajSD`pG7#-KvIAxV6+c6m z3Mp$lh~l{Xq!II_StbU}K*{P*pm6TN?whO~5|j4DW@iAgpXM%5d`aPRcRwK5~9 zA-SP(B=6dPR$4AQe8pU3L zz(lP+1wZ=m7vHEwqw`~wooQ2a5uv#2y{ig6IG&rC(pCTsp)%C4D{$(kK=^LGBx7eW z)U64H1~YJHR=2T)H>ZU2NI0}0^_v?Zwho`k_eLus8I7xVf|LbsOR1bD@YGY}o*NmC zl6jlnB;V2}e)Kf%y`AJ%SdzEH&jH`RJe7Xrh%K*S#;4Em*TPd2h)kfch49Vrjdo*$ zB~o-`A~DNr{}9sD#<&gD3AM0_e^!8@-HAv_o|orzk6P+mAIcONBZ9OGz7Zdf%Sjgd z(B1P|Jf5euuH7C#ZNkAJox@p9q#dmAi9^5epAwBB`gkLEY^lvZP^HWm^ zPKv6#>|>q=R7KtM5Xw&Zg_OHOy)O;b+l`O|h5yi_6j{OSxl0ucqxrb7Ki8#jJ!_Hqa0dA?C79`BIdLP6THWiP_)__G0_P9spSfI^>3}zKTG?PVWO3o$f zci-mL2i_x6L8#(Y$6sqge1+Vh4XDi?H7Fd5Vy0DZ*b0>V{;1$mhwDdwaq$hRLGxz_ zgmE1IiN9{hHQh7JA3^$$*=7O1cc<+Wn|%PDG3LGr+@p;Grky$8Kj=hOc8MVyX8VK) zs{ZcP9?j!qs7Mr08dz<*69qbK%{(f*Uore6{u|H)qiC>n=s(aP#(pIgZ$URbw*0Vj zh^x_=m1f2^h97xM5NEI|3A(s|8fB6`O5rD=SM-hW1SlFTzUa2Tg?|>fc7}E+4yY`) zEScP#aEk7K%JiNtSU|Fmmo&MjtK@&@&GA`T z+1R^w_{6Lfa)x_+EKxtqivhfv8NaWLwN41(7v8V2s=m4YaxKR~(Zg#rF|K>u4fk*( ztoq}w0tdEp6-#sA@PYA*k&32^3mLCLqsU+cxpN7IEr_8<^*np=ou6irPat!am z7UX@|Pu}TAUQz`>9E;vd&}u*|K80(vgDPc;yoxCw6oJ?ee&>~QlkJ`$wbXJyAq$^n z&CqK4HugZ=xA)GANTM2+KB&1j@=@LzYdEe_UqDu&KI-He^?QJ{(v8UZ}SlgR$ zPUEsrLe|sr7V6f^MGCyx|G}J}Hz=(I#$Woi&)yDz@BVT z{|WZ-UaCL2sAT6&{{vD44gW?l43hD@9O^`%lzCULYsAA4it&dK#9ae9n!X^)8ne%& z;WbqMqzi{C07a7p7avym!4>=V5IH{-B)6&sz(d#$Arc zzjr-<1mB31h$U6QA&kulzDkZ%Blo+vj`=g@5C&siKOgLK*y_j2+mwg%9S4tF7Q_q7drsMlwleFrVgXj^$z8QiSwl z?sk2=cA=^^Ov;5;n)p5gl`nGpwtuQqtSvyvGN6mc==-Mr7_EZ?N(Al=1dq zMh<$A$o>!149o8L2*~=Pea}KW6W0e0WCmtcyrEU4OvalR?8`pK2p*+M(j6FKIHmIj z%&CJ>ML0Wo_5ENa&53;0vNq{79sHi(-29%mv=r%IbEo;_$~Gf*n;Mz)b3)4R0m@Bb zVqV%agg5O2^F~{jA3;OkhS}r?h&C+X^4?JuV}AvCdZSZ~Zw9{S`$R%}D-`ZLL93np z8D^0-%gpM?<;_qQCk1(i{d9XJJ^T9x7p753wk+R`3Ceo?a*ha(9q|i5+y$1`nGJTApWwlOGT6 z8EnSvgj*RgUqRRuPaM9Me-+2$Nm|GfRl4D$c^B|Jam>SvBNYcLVuiNE)CT;S5Zcll zBzr#j75`_>G=Wz&ul#18hA=Gki0IoH3jbX+O?ErggA`cj;qJtmhm@^W(E&)b=)N;gKCjZXF<+V8Uzbmn|0r1Q}rTeEe$uX}s4@aH%w~ z#}*Xu{tFLJ?=H9Hy#w5Zx#(8)$A+r~`yv~JNJsx?Y0 zf|`>5Y07XYOgOs*XeG?0p?{1(=jTaqdMF7>JUC7cqL#$zNuIJtE@7ZaU!qQB`*d30 z6he7K93IepbG?%uvL7~X*NZXc(#7mUXN%pTT|&$BpmxHyJL##`5ULR2XB4awmIoNDC`mNj!em*@RBY{}S+{v^0@o^^3p6g5)Br@&2 zx=xpuT{XcR1*~7HptN&F8+8C)-d#oL+sogi>YF7P!hbc5P^0kHZeE;%+@73aOEnkw z>t|}#J`YWgyQ!DzX2s=fbh@^ZEK7*gN%hwT#Jdf&NY~W0?Y;KoD7ypc*IjA(spCd| ze^pyc?&LwSK0d&8`kmp!RC#bo)T!6&W)Bk5%EjE;c)a&<>j>A)6Qb^ ziOWwsE4{dXOPX`;f2|ed-&*bz=I^SDZ{AQ}G*g~Qiv203D*F6%c(cdK{>XKn>tb*! z))Zf9CU5HIc7E|sinCwoI4|1| zhOK#HCqtvVkp1TCsZO0psXMJ1saaNEtb3CWtDPK*IJ^0r!k>>;g@Sz!vV0$$epXfe z<`Z2%!39h(D68PY+*p{q^&Q-1BFD}rQC5A9*HypHCs7ZwPYsZd6BzvZM8H`KMciAoHBLfN#h<$n{Jq1|yzzKR7CToY=ThWEou*oZsO?i$sJ( zPSW5s$+U8MbmzizoB6jHy@7aK5@mEC&wz{sSwksNUu#tKm}_+7gjvf|8JX-)B;sr$ z*Rg{k0gDsjWQdp&UCuiN^@zg#^ihMblj^Tpzn<*Hu1G!gakt!I^-KvOvTm|=`uLo_PM`YY z;{5=GhAn*E62KD;fnnFV3C6QbwT%JCv$^p#qLT0gI7DBav`r*MPb} zzTaqJwb!pE=mr?9mWyUzpjOP)>NgX60mzyVZL^JEaYo9)O-sGrj8B(rp}BPU$USEX zy0F7}P=j_pIBFppf{qqMQU)e4m<51(XM!vBq51L#(qoGQk^u$fK@Pl4?l7X?bz-Oq zIxzivW?wXeDX_sfyoK6<7p9*LDU5V@%rPd{pR|WI+H^PwA-_FKLCRs~Swm2o!T6`+ zzg^J;mLY!_%@xybH)3qtE;&6~rs053;+?fg*6XiXwn6o>AFnbQ65=@zBw}6w0y;!!oGn z@j!msSPe;18Da>9l5<&M3S8+pK3&bXk&WVp6e81~?zra2MQPT=R zl=DjP1e{Z}M(|S?#NzBJA*)EKoUvi%!2PcBDZ*6%TrD#N%NPI;c0`F?D3VjM1^P0? z=$|)dXqN3C5Wbe1z(rmaMr8hMHJO-Uo8rmRzD=Ka)tmCW?>(zrrA|DIS8)L&!R6^* zeVxZE@!bT)vRAEY1!UcI^JOkv{xEuD`oO7bP$`vMU&CIdg3{TtCn1!e;F$@OOsTM& z97GEHt;4J(LgUrGmgg&#Potw3>3g66oe9KjVm35NTC>J z+X2Jiawb6;OIbihT7xE(NH_dCHbmo!p3JFM!O^Hs&f9KPcXur^gMIRi)1o5_9sR-T zCO4*n98eGhjTu+}3)Y0L6hWF=(Bd(plC>Q*NKuLKH1r^q!Nms=D?`~zFlLBjA9W~4 zpk%`;w)BlJn|*|$fghql5-djc4=zbFpJAYkqJqm0*qeGcXor6sP;`9W`k(G9aZ_E{H55t@p2D1r5mw zn#7l&8f{YWC9QZ$6p9Azug66$$DyTknn}`H$Ywf$e0ov({VwPe*c*6j@!Jom5cmYu z$qEgW2@HY{aBXPggaRtcj&J1roM8s%f_UyQA@#}D8IsoV2Iu%JsRl)cgtw+c7Uu+k z*+J-*oL0*+S64Btg0}V-RDu@QFWBsU*dXXRvhyAmLEhG2{^skSp$zu=P;t$TKUblT zm$7rl2Fy2SS`#0u1<@QRTmSOVp`hH$4ly=PuBw(dUdNHu4&Lw~aW@b;J-Ta7xlmLI z1yH}3?ndURUXP;&*_a0*i0pJ0&^law=XplohSjQqRpWLu^&=jSU(Bxi1@*N5ZWdG& zY>wGO33qOa^kTJ23d#K(zB?%lGKTWw9csRf=#C9^RD&AN7cMWnuiCIEb~VL4mrJhn zDcR;`gJdk z1apcpTp(V(o-ZxAJ{>^~&AOzLj>8fECQ>%I_an!8aa)p(JYB^#=h_aQDx7%>%P0r3 zyGtoVT09)msaPdBI6}`8a*z=LXr+3SwROf9(GE`IB{OA2t$%zi;P9JSudN9!8{851 zlf-VFvUY1b30ABoKjW!KQ&Oc+YECY>GZq$mKQBPAAcEdh^p zx{b>`+qX#nD~i$l4|#_SH>o~jsPawb-8ULC5XG*spOtZPzo6cj`djQ|~k9 zh*`50dpL+=Jbi~W{G$;c!JSAVew??}Ss0CKVsq4|dAq56!2@8%1mD~lFWq#SQ18TT zcbOSx$lkJ@yCaPYsz;QL<|?#%62tNWLDDux+I)WhMk$S1efh!T%d2tlA7+Nkc0 z*5CnX_P^ogXZOVBkLEUZT3`#)2_BME5bGP5V)Y&)<>%!`$)n|rsMZg!h1PMjwvR*P zh!vASPvV4Gk>xftxHnrzRS95aUm~yf;|x=;9$2fpU;bRdk;-X+Jig`L4Ho)9+oZk6 z9eu2cWBMhxSY&m|OTm36-V(E7aex>1^bGh)&%dc#KlBK>a&1QB#V%9o(6;M(7^orj z@XW~_TUeDB`+c2uzQJF*l!=`3E?0#ai9UJX%B$foChh$w69h9xkbHfSfvI-hHC~9# z7>_(6mDz>YS?6=8E>*A?&KhKL$b!kB6D@EkI4B$J%;Nv4%@1H8a(|Q_m@PV-Cg(#c z2MFyt@WULRnG}s`W=*pA9w76${FIRBw#Ui{Yty|fQUq}l0tSm*Hblg677Qj%;UAqS^T6%UY$gCR6bk0#r#jgDP$?hi5(P2paUY6f`06Hv3Ej; zO$%?-;Kw=5ud3zP+WOFCk28q%(*2#-E4;ETXY_N+Tx%)suj9m~;|VSgKO-#Z9+=4L z4yi|w8?EiFP*gSK(INO}I$*E^p-aNSg|zt#LJom!V&yEds`Rrs&;}XWw2B zSqQ@QybcA{z}3Uo208CCJ)~VUiM7*BAgYD1kK9+=o)4^E7O^*tSorzGHbbiuf|SNO)rUm9!^?(^ta z%i~R~Rel_J(-G@oD#OPYvb2k8`aVjd7cW1cno<-T?^^v7xj7@1`8UXL$>?8o@^J22 z08UuRZjzM8$~CHf4W~)#`b3BfF1aWs*-*& z5F!)Tnnw^v+Tc!B=Y?ihlnQ9F5d3Gi60IMfr!bI*viByC(9tr_{3WNVIQ~ip8Bk^k zQw2*hn3orw%X2o2QO68Tcat_66-9sfPjAXDFV;SMt?AGS?ou$HDi!Ujqob$!*5Y}IGJ^>I%bpvZ(sxp2wq&Z?# z-MYLHrFO;iodh4HbwSXcqU^;QW@fm)k*_asW5wSoh#xHW;r6ot6#Qefkddh8Ze;Zu zu_AA|zT2N0A{Jp~)Z4)HaKP={B7ZOPL#yW^5gi)lU3U4$-oH@O13hBZSQxY#YN&~>`xay#Cdz16^PY7==svc!(#5=idr-%P5_&9>`FwtTqCee@g z1PXRnkshm2IkuLXe?i1u5jsICEM-m@-%@Lgho*|4{gBCJ(~8Uvm4hw`E8m|K9Ta~T z-upy?CCm7w7rNX#irexBl2XdnI-Ig%GHk>#DRa^+`-F(SscX3(BXqFw2fEh5I7YjX zvDm}C8I=_25AfZMXNI?tr(g9K$nmsVZ*rv{WCtVof1q@5{(!}q2xHAe}+v+8Gl|8*)-3A zhqX?G?|uFS{+n#0cRZWKy5gR864wt6xN7qOwhU|2vsf8TdpuR^&&xN@`PYNXMu=*; z^_!cBRljyUNd%nJ3v^cC`K5S49ZoZy=Bx(`0oSIt%1y6?qAKYHR_At46cdstX?3o` z=uz%@Jt3I{*XUU9yJFPWlPRM6mjVd+Au=ZR0OXpdV-GV6uHSCCz4Uug$_=MHZRSgc z1J}0^<)Em^OawGc-LSA=>R1##qRd|yp%Y0xU~6}Qv3_8>2-8+bRSnDppa7q6D_#}0 zCjK5V{b}ADBHcD933}d?D*f2T1>p6+eJ79tEtF(cygcdjV7K%f61b^Hts)aKi5}Fm zP193xH)HcRT_dxf^00x+HKFOB7OSiR=;p~qjE0*ZdzStkp^gzRmCNr3yI5t4~n^R()NQLD3>xw|a z8|2|WNU^&a2FOQbx^6K@Rfo%3^dLRb4l&ssH07X{-IBeO)e_=hn^fNR*WWZi}jB-@tx41<2swUI##8_9$8+4t(G0GsTI5<6hkNtqk&|>rvS0UxSTe|x zUcS*?d5{QRDoSh^dfDj?w|=lUP>%(PZCGMD&&PO5bnN)9c~xzK+$kB+KvgE zgKF}2pgrt<@Dc_gTiWrO{cCaNrept4;d+@H4oqnA&(>Oqr-33~#*6@Rl1|2qH z5|s!*dxJt-$@Y@*Z@Fh;gLhZr%&0b3Z`KkctTj=%H`SBtRhBgUY7()iW=AGSIciAme%e{o6aR;-Y%X$TT0+ z3PP%LNp07EO;1Xm_tnz>n3{V)~$d!;U!l%iNgun}IT-#GO4+*T20XxX21S$| ze-IdU#$rDFzA7Q-_Fq)-(hr@Pq+%SH335N&{?Q?FI!axKkMcmt@&}=E-ZHD#Uk4Ps zqnpT7)*~U8V2Jh{EVM~jj4IiU3k*F<;7>1t0M&>zU)85L_Ca*1df32$Z4R`>naIftXtFqxFm+zFt%CZ zz(GObb$XU7e?oglxYKr0HaSPBg|o@w$LocF+NpffWEt2-N~Bu|7TGEN@e(OLSlej~ zbFjbnl@Hthg!c82<5z#IcKqCMPN^u7h`E`0G5=yAjz|jh*{1zCIYp*n>+_^bY#Ux8 z%&85YGwloKHIxAIV;SDa14s@@u+6L4%=(C{ZC3Y%1vfe^Z+sRq183*v&jcbMFtV%K z7o=$o-4Wp3J^v@^EHW!ZrX&^<6uWIvGZZ$4&F#)`nE6(!Pb22#mL!y7UozLG#geAe zo`%yYP*3}A5E#0W@m;(8Z-fnYRqThzi-b<&8LXK~g%)@NoXh>3jT;gIiiY?Hc(-LU+)nu}SLe0te;uJ^ULNtM2Wri z-KqAoZyJRv8MHcNmnZ)LuEd^NP;ZXEjRlLqfe8$tspVWG6j`)_Zs7>`YU1xK;vbw- z=Q=ysrlbfK&W>BWN&Sv`Xdz0VQR!Gy-IX?L?d5+D*l5B0XfM8>!|aRkU!@9+fMgRBDaN8N_&3!vtrJott+dBq<3q#5=OB0Ayy=`q~2g%vHDn?H3hIytj+GCR4-ihoFowe)25Zk1vFF5J%| zLg_<=6L%9<%zyh_8F6{1Jj|DB;9&+c+om^{h^csBL_A2J62L2-I<9c2i14SpayRn& zeB7s0Fiz{eJBtU=n9CW8HSPxnoBTu~-#3b@+?-tpo{6_gG2a18D@3}Qd%X`m)B6$b z-}e^wANbljrqslQJ_D*u(t2YiO&ElDzyPx}wvlvO2V&1*>as-O-bCf_enmOdA8U>d z{FbOjKD@1Y%0BD#d@hL$es#r;meDM>c~M_b(L+k2V=hg%T_wiz(gMCJI|?xaD$Z04 zMvn2n0o`}>?ce9CN%l&#b87Dm7vrdUrc>W>twAEka1rWm#iW0%)W{BnVsA@Rs&3p) zteO_pHC5OiC6vEG84bVy zVw7yuz5h8X$_E!2NxEkeEH+Ss*&ljh=6Xw#1E_!g^r3q>c%8Gj_7^Px% zTGah{67F<;%)sopD}A0Kv!q8Nz2HZo`p@#EVg&fEa4uuI^mjE><9F@la8F{nqBQ|4 zPfu-5Nez8uf zHQvU3Ct+ytC+#clP0ig*MUrMhy-(fDjMa;k`p{YMfcC1kvMF)IPJkH^_p@DD@jcj5 z)4yNwoVTEb0srMQ2XAmUGYQX=;wr_K6Qrf^JfTj09c@%JY~qCCmAZp z)g{D~D9u>KeQ!iG_O`HSV2#KT2A=40=Jo?@O*fPt4L?>v*7w#wA~bABs$hGovz!cH zn~LtwkMw)J7)sVx+!jV?0Zp0ByR5C>Zko-ecx>Cy3s#zmmjC_2ZE{vFg2C~$MPMlL z(MIV}$*|e$f&RwQ)G(X+mgS=TiM;995pO0inCUe`g<4Ucrl<$;?No<}Z7suf&9M?8 zjgcnp*{mnkw|_(k`=O_f0Rc#TBej@2E_Z7I}O-d8MYl!gGGY7o|N&E4$9O~jOf&KMu@+{Y+Ga7>i=Abxp9(@u=Q*NDJj zF^b@U93m?Q3%tS7yC)@4nPpc*rY7MgnmVj@1Fa&2+|5b<_c3Q^I=Z2s6TCfQEY($~ z#*3yLQ5ott7WHzdpXNZ!UGCr&R;^cC#6u}noRXp|UTL-?=w17j7YKmk->|3k`A}OWr^pE0XjG{Fa8>4^293L89Rj+kE zWEXOif>)63&l#@y0lu0DL;!U9WaED<@Iw1+p7h(8fEVu<#rPa)%9Lhwpsx={GstS= zmoS{ksc6-+9K@^-2N0v`$#eeG$sJO&rBLNgaX5&kO5vKDuoPp5bg#xDO^#*`E zf?jiCr>0^4pk+%qD>pSlg+`Xux=6hAN2d(8eraQ^8 zU&Tv%E6S7(4pW2gJ)s`vyK-}qgb+MGNlB^&oUWIbeLB!Vk;*q8oMwDqs_5RfID<6< z{=Ei`Ma*Z|-@BX#GJ4Q{gR|sXE3Z;`N@kVJs@Sw#;JNu=@wUt%m!gg9avF$ZKnbgL zvKzg{R=%I*I@$#(*%fsmri{{s^+c>W-J>)tk0v2YRejz&`vb}68>L`-X6GT{IUC;7 zd}e@zU?=c61SA-0?X;8qjbX^ZzRBR{T7NBAChU8hpxt0GcvJy@0b-KW@LDYInXGM_ zCaw{bJqyMs@;+y@E~gep+j62*>_>{2{5m*Nyju^(gApElICRv5_@|2=(+F)}RNHpt zYiT@-+gM4y`ltnLlhk^-G=omfKOUFeZgYd-=P|B(-7Hz=INNv?df2r$rT`@!cNM{U z>)+!Rd(48x^ZPKEfG2eqmOpl(yE=---zq#((BuncvU5(Uf#Z z=*)}heGFcSgo?nK<@0(zhF_A{kg5$j&|5tudh()HpKKS|L}{6~coxwPgeB~NrZaJ_ zR&ZqbDGjW0%bPg@R5~K7ck&SIuX*>sFm4`d3alYO>P+-KwBN(J3&KPP`T7ejj`cz& z)+Gaea&8ZeUX@_=g{=&R=dL9aGN{CKyuK z|0-AhD)-bS0Dsd;Y;3cG&k(1#rP~^zW@ZF}$Ta*bq+1zjQVy&TWhr;Y2UqzrI!-a+ zKs)tq`)_L!ermxZ+2%QxCfJX#ji!)umMCUG%)L>djSgKfhg;-Q|W-$0wltE{?o2s=p!=4?SkpbHx+l6Evb~dbjbNT1}xrQCPj=>C; zdH@;e`i9Y67su>~l{I9ev&N>{4&qo-m?`7q&W73!!niBm*Tg>_0ESBikyisZuom%k z?lRctFSbN;QZ&Vu2kJ4xY8>Dd*HKFdPWXP*nm4%@8%%}+5x+Vwplf+w%a~d9KWx2K zR9sEhwH*kq!Civ8gy8N3ClEq6?(WvO1-Ibt7NmhdUk-QC^4zMpseXaCtg+*P~A zuBx@>yk>WzU&|+;kS<*heGRE09;#)y)vF7qT@m-L*aerQl^c-2ZHvU4?z7{alS^i2 z%!Km3RJm+OfPkgo<73h~P=C%krPQKF`Dh16h65{iTE0-o-hm{xPy4>W3n;ux)yY0^ zO&xjZAUZs5%mnlb-ga|!m~*y{wSb(H2D_br*s}T!b!M?|6u|+K=0MA@xOP8;n+7&7 zHG`i}puzl4h2($r zNP)yfOSRGKYpy8QNakK<`uB!ps>SZA;i2>P-GbYtxvTU&KYTMxg{=_tFlP#3ThhE6 zs}+-#u?TgwLc4-T7WDxXUp!4NhrguMq^ND+jNB0-gt8en244a_xI|U<2C#x;Vt5_? zsn#EUSi#=aU_x_$oXN$;cZukmoDL?`<{)6p0*I1&)Ey^>kO)bZx|E_xETka!kCW0u z&d0G(!Jv`lgpHi9n8r*bTIUtc^_T>8j9fpuoD}F-4cA5G=Mf<3yhf7O^n8!zwcKT;C;=)>l-d9j?`;Lw;!02Fc^ph)Td~w646bp#yk`WeiHWj zNPbKfd&zz5;B~LDvcv_yy>B}(l28`cVaDFCS=GrJ^v952CuxsN#F*P?zoM(SHpj^5 zmTqOOg_QcZ{&Sr#vgbbQz~Cd|g=ep#rYBlAzFlAAR`7*9Abk1RjM92mz=REmcn&E7 znSH0NJ7(%-T?$AU(9{wXs5|oMv9PQVj_Q>r;ViWiUh?Rt^m%hD90i7Kakos-Cy{+G z;i&E^Q^P3BA2kDa4IceCvA~kk_xeC&jX?!AM9t3pg4u9CDm@&3y5j|(Owkc`_H8z5 zqJN$d_3RRr^SV=ddqW_grlZJ<1qDO5Q(K*j)A9^|WwqpYr&iF^tTlfWiu6w4ZK{Ah z^RRoitO5S+bPE#lh+D3~rog{b{_vJ(v+dbbTBM?2{5lKFY+^2Sl^7KWF?LC_Tu9Jm?{d1|c<{&v;2=W@TD;!~6f)Hdb(lyoa|LNqopPRRRzVUXDO)F52GIW4wr{?7z8v-XPbEfp1Ys z9XGxl8u0lTp$fUAJoZ7?qaX~$>Kpm3+7fl!iiLSQE)BOV{x1-GkluuyRPMID5F81j zx8d;~=26E`;Pkx{Sm|^Vth4)AqelIn`uTnzc5vX^pspoR(szt0E2%uS#uN`v67R; zN2V>SY!o5aX?Y%C+x@;hhzlHeDlt4q)HiqA6@KBeo@qRM+!%6`0UkZC^XHCTJA>Hl^mI~T{?xA_ygPSEH2M|d9 z>tHXhdAH{!<^MhmN}n`ez+{tTe?0%k-y5_mm)U~eLEfbXZl3||Y_&ZsCcZoMvMhw{ zFIMh;^qipY=u=SNJ>sIUEizaz8*8nNs!6UsrznDM@MFSLHUv-BXHzE+mvXX8TdaiI zwE=UsLUzYl(M9HdkyCi(YSp(i-{(oYd)jb5Wqu)H#>kYhm=%z!5JHJn1(2Prz=ceo z?tfBmK-k1xt0^jwQD!v9sx{u#6@coTG-%_NTsX z3m&O{Ph8uFOb}mTa0p5v`&vM6*{qETB34fbx95^KFu4?zEO{N0K)~_Gg?|`{lBj$w zbXRz98$TEhc&mQIoBLzH!i04>Xz+?w%j1CMsaSI(+|V+$_Sk2IR1sbIc%+XDmaM15 zSWN9>vi=KfmQ0@!mxo(MYA_5DH{5bi*dLQOmK^5+xqme{HzNiGxzd&%ykuBhbH=PB zS}pF>ib0VXP2CU92SSX(Yjk=jw+yNFZNmON(XLNRk>JqwNQR6&W~7H`Kh zmHcA|nj>?d%@Ei+FO^)CHwj!j!AK(OhJ3SYJy0=AA1mp1dx6)_dgMKEh+sYQ7`{D< zcO>0z`M(<%rZ-CE{Vg~OsvXa`C#96EFw&6U7LR`u)1s|wXDzk+jPWOFphPEeLT%JqBF4>F$F0idGIOGYR-3* z9#1+@ja3Ne%zVCWiq@#GClSmy4Gvw4$L78Qqjl*UrAjgG<)g$j=F8qNCze$oax!Y> zzX6XOeCa*fG4Bx5=4^ItFox;6g}G`*uJmPmQeX4;Wa|GMjNX`lQr;#b1JTK$t*#Jt zL$+5O?W-Ko-SClloEBTaKe;PiopK{N|P(K_crg8 z+Ob(vdBZpChV&t2HIUz3$#zZ6tbUEqq!0~VepVR}mNd(^yOoI=q88D4APapAKls@m zJZy*Ov|ri15iw>V9qBoHRsf=Q5;>#L8&~UPVae}X=eA|*|G|=*bDH3guJkbd z=CG%JG9L@t20+^;eebC9v27R|Ru4 zc=rdHdwi7SzNq+r&0cdS407`EE5x02k9;Vt#6G%c%YzPkn|VIhX^b5A69+k2ek@Vx zALD_?S%bhIB{V|(h6q=@WHKG85-fWc3${We?{DgjC9_s=hbGv+yO_>3osx(O);t9e`?V;7W_V!Em3JZ#5_9xt_P)#^irwaCh@ zOyLUIu_2GXttLlWE#D1NAhhLgw5T?^20^WgV(#`*N3o16*%D@|tg)rvz*mnJb9-4y zLv<7tblI)vI-vOR3yi2jO+!UtTF$#&hZKXcmK7E#e7;S~F! zwsx%%pJcJ%ftKw4WwOnN#EO8eV0sy|Aq=|c2<3O(;9!VQ0m|sc#;TBQ+`vB!&dDbs zvP&*PlUyGo)5gJF;Rgczn6nvoUDV#h-}ld@&ml}J1f)Sn=q;c47_mm&$h$TIrCZk{ zV~m}vA1>e_=CXAUDIBLJCU!m)cF4|`pmP_SgxFPgI^(U@1j1BNvO`o&Ly1k6l~d02 zg8JJ*J+DudPi~vpVI{IjhFx6>ATJ4geA1_|*UvcN3ikzmcS0{^=CFI;^ICaJ;ZTt! zpu@Pls3y{Cdj61Xw`JjkEt{eeO6_@xMXYYkVgKqj-1-TFjJ~Grw96i0zlYbDvj%^f zN`6*NQrs}gmMl8##$2h9BhP>Iqm(ztn8$l0@HJq(Y&d=~Fj=iQOv5UISzvY9!<`v>gliDhSSN%6`ntJ`ms$2Pq zl7GWmAm_Jb1nU%mL(f>FAL(sVgC*V+Yd4WnH0GNLV2 zqY0&*bEb66TFq$#2W=SK12ueq0@lXi5eKoRv`g`T#YRXr|H){zwp@RL=N z|(szSTrhq_GE00|-^ zxkn$AlG~#Kt|D$yh+_76jpqu6x`nd6CX;z$!GzA~mhdSuW=F54_{RE=&JLE;J>Om6 z?)gLx@1vvRLM9#nX=DM`Y`k)`NI&UECC=S%BVgAei5%KPXZU zQtVgzAROEA>qP>h>=v&r7wu$DUW7qj!-_0|AcT+3#86NS5nS<{@iBoP-5_4UFR?q# zEhku8KKXj`T~#k?yF_c{2BaG{y~rlS@qElKqprWP4A*I?weLdfyHq9uN!R(egnCW* zw=K$fDpss_Z<|#Ii8ZOaCT)$Fb-KLE>1)Ts{w(YvS(gpW7YL^M^0Ep6gftL~I6WyHA+gZYnEBuvZ zo+#HBbZ5({c0vIhH+$vJ7iVHRtH9nGuqn4quL*FleEbDpe5h8rhOFWTkEy^~9I z`l}mxnLAluk54%D*Xa}C{5U>8YHWV&Z+l4UCC)DU2PPxC>oa9l;-@jSNZ;6GIw}Bz zCDR804opEdzktf{nZ>*DJg+^{3PD$_S3t*VO|n7%S^~&Pk)Mf|T!I5n_dOm#h_^lJ zl@`IaWzPs7PpRVspuv>#CyZw+&CxW~c}KGT@OunL-3~jvz^fL;9Z*ltCu4)w`tcMb_0L9}hm}x)0EjMf2{PUK zdZUmQ5{md~NBD}5RHf)v^Bd})^g!l*VF;BTVH~QtkBOQw>hy136qVRf)1d6|`|dJ_ zb2092hE^qJ20n1Iq|n}OT8|U%c4;0^I4(p`=EoMfmHQZ@D@sOxh-!==B3{1kJ=E+_ z(j(|5u!KDNdRz2UGM}(@)S+#L$)az1$(-8H>E$Z~{hNgKyPVKSUW4`TWYeO~Aud>Z z?A&H-3;k@>h>XC5%ZEl3$ma?7`>|e0Ny~2_ldT`XOPEVMkhK)g*-?hVZvTrwud(8y z{OGa|Ecui)$chFp-W)eOQ^Rhn;ZzNY9b>=;nJE@+TX6WqaClc319Jr5o(}0eWVel> zm6Hy&3kRqA_=L9gYx8gXPoZOswHp~4sPlSwd!X~*3)qdJDcif3yL*xeLG~4o7B{3b zEw$Qo(gAQRak>$Usro&-oJ>q3bQgc zv3q-h7(LbAs+8ICj7)>}Rqxl%AP<0_y!Xmn*OuV6x=eQTQ?K3aKD9o$PqSWp*~HpX z0F`})KZLwDtWsiEF0c<@AsF(3#;O=l^<%%i4DQy@<|9&g2`pyDkeUkiar)-7#?;bK z-!>`o_%N05yMmff*T-B=!&yfP@t^D)Kqu?qCVy#6}fn-kPrS!Z)}pNPJp$ zqp!b2^fb@=d51k}m~j`)+Ov!U5MjS#e5Z1W$dobuv+ys-n;ez*CEjW>E#htOZDvC( z@}FQmO6;9V536Dcsw^S-Uv7&TCFU@TqWD;^FfN#HTvN1V__33zf3G9V)~mRElzmpc z(M{`bVZK49opf(p_2%PU>D{S#mqnDSJk#R z_ts#0P>eRN9odA>nQ{a7s3?;X99UyfzEgke%OI6WwiSSa@EizpO@TFk_(|i>H6rOr z5;VmRtp98|$=SXnrz1POl?Cvi!{03L-2c1CWsmZ%G(5!XC{|SHxY94%6QBmi-fp4{xp3V9=xCd5M_hxr)fl=eh3Wz+)NB@ z|C8=bR5HZQI#T57mmI@M8e%K4l>SQk6l)^Xo*-0OO?uO}5c<+|`BOw!P-^ortcj4* zT5yH0mu=Z2y{C=TB~O|xUNaVp_WF0D0ghc_{^U;&COjM!^jP%W2z_9WaXMoOV>#f* z)L`wf`Cd0bbLhuJ`iSmr-a|9NI~}XYj9}jsqQWcuJ>E4!g*`rx9+FEqi%yyZo`$ixD-tb7$ zR>hxTjfP@IAGEH4U&JiZ8w=8Gle61uY8w3)gZJ~xj2A^e`ZVG#+JYCC?e6ZlxqWDX z%G(#<_18aZw03gjOf4W)a;hT6#c%aW6H!q_;}?UiE>(BdTU;vCg2j36DAeS=4JHLO zL-&xi<2QY!#2Hah*<+Psj@)0PScD&4b>%M#_K>2!;#ru_HP^(~nSnE04coa`@t!|m zqy<53fcx=t=bWskdw(lwXO{$&qz?cwFgRJeRq%TPfjf_CqZ5(Ix%P1DYN|iC)PIMt z!_sW0t@2?vd(6dOJd7gMJ+>5^{|tU!^4YH4+jLnqg69@~Pj+8#e6O!oy1C^52K_+(ve?&-f;@R;r4U?(TKl0>+)_pK~mL$-|*;K%klJD zDZqJN={aY#V0Hs`vdqWNE}v;2e0!d@%HK0g4{dvD_GnD*M)K#|LSf3KmF=OUq&W4$ z-B^s9Ll>W0wH@2?krWv#WvrsJVpPOAY+EXtQ?{N7PnNk7`SVK%cjN3WnAG;bhUe;{ z4pOPya@f9DYyZ#w`dH?Bs{OB)7#CJCYgzR*<=k%y-y>H}N5_dZNkd_l>dUf>$9)|U zXu#ni5SdiD_edbE;oz2zl9yz#Pc&rBL}VLBJ82crCN|eRo9Hz41mHFS;M$P_ z9De0Ban@?-XjUm}Qy!p1)gdent}%eiuOL(GQUB~s7)sBrj8T?jc-mdUYhc%1;i-yN z;UJ_$BN9mp6C0Law+3V9?&}H9&E@7{A?X4RxwFRe+!&QW7ZvqYm%B6E_!#9&r5&GU zfKDa&x0$k*(2Z}8d?~Mq4li5lFyK*pqk&<1+Xo!kkCrKrB`KLuo7`Ar_p&D4Zk(-6KB^4udIf$%#P%Z@;;PoStO;O>Zo5jW8fm%jQ zeMa*3tF@dhOYEbCx&pTBpCz*4yRvi605~1is;6}6SFU2~8VgfSs|mL-HxB7-gmsXG zN)ra1x2F~sIpH8i#p`STm)$xqnrx!HSV4G;?G%5uA?8o1ZP10Be_Q^TZV>p_9VMGE z9{wF#s~Xe^Sbo|oz=Il}E%5B(V?T~LKbmcf>%oJJk6a)a(>w|=U@`HHc$=(xj=7Ut zI|fmnZ+|T!r2OR-{xJwMH(E_JRz@2~$>hF9q@RJWb0e%{tl~&#FCLF^#XilAx7qJl z7U-jt##(rOGd~81KK&5}$cn@2mOIncMJ8|S3nE+0+VcleQ6SiSbCNGSJ;;X+9_=uF z&%%`7mEQkua_xZzavR0@+_lPuZ?qoT(X$XiR^7@O(p`Y35PA1=b=%=^q{G0Zj|Wmx zBv|N;j6HnJX@3rYoR$@oZ5teNz%)hj=9~5Cp~*2ycFk>riv3XDZuH-yIn!pVTY2Mz zq^Ydm@H5}G{kDofLEC~F>@+G+4d*A#PBmI=KH%0ffmA;#f#5Hw)(u#2MCt_D%snK= zDK0J0L9eG8q96H}6=FB{$N}Ic9xt6*_PBTo71VyA!a@fPe zxWmTd+jXb0zeVN2Zp6R^y3-Z(gz1b5y#%;E2D3A_Y-`Z4iu!j}xK_6cp>c%Es z@wptLj;{J3;Kyn~&a-2b%td;Vo&9>j;yV*iprubOI7zCL)4AQuTy~`O{kxoY4p_Dd zm*;FE*$-wGRs0$;MPKu8X6GPt5^;k-N--r|Giz|e6nhYoLw{UsCUI%o9|~SrTe(t8 z?RgxFr26`19;j@Mwo0vZjWH_Qhih#j9x77X)f?|)F=sR=vhWDYPQel@fRdjuS?6z| zphg!Veg=vm=X&GshO9Mv6=FM4v(?TD!RBjbqf3sY+t+4Y;v+1uMDxOUrIBv=M!UXI z<$6KAuIJlLU8M}m-q`TgF&n{u`z{pHf@+dl)S9lT&XE6BVtqB&ftRBmiDmXcnG`BI z$nbtQ3d1wkw7mFv4eUQJuF&A>D7#k@E8m}s4VoLHo%1TE{amg|R%wYM9^KAanRaYD zIwI2{W(C*qff2Z7-JWwg1c4!DoA){rJ5^f$Sh#}Dz893aWK$5&dpcot`gZc4k14NQ z6QP>QrQ7PaNTr-$QhL>VU-_M3HyW^VBD#|dW-7Jr*e8lPJ5q_B&EUDK;NjLF~7#U^86jPqc5@YSLpLotG?U298jy>mWHDP%m>HB=* zy&2`IT&sX8dsj}@FK7S#FEIe>rkNSwsQoIn*CzB%4+yBAQg5q=7g=EcSQRzam0&z< z0ai9|BzhRTpn7SBnnq4CK6c!|Bgtondp*&_$H6r^{Mp(`3YJC0+v>uC*o|@U5!g2G zrm=>*wI6~^97N7e^*`{(``Q^HLyguE^G0S}+`kO#dWs$O2GHWFwyOvJ?=3i>(4T3e zug)HG+eSO$di$(I=O<@NPbI8&QRhmZ(B(r(b+v_zHjX&cKFAxKWTGjAslDkLmD(OMu_6-W>-J%prvv$svM-K9`6VD+b!GWTJG z8c|+QH@7Gz_Tk3G0t@{xatZu-ruC6Sv5yhebc~5X39B)kG4gug?-F^ zh!8oVdA*GaFeHi|Q}k)Fs1%t?7%La-1*>y8O=^%Kcb>ks{6C;j?0@?-f)okNEKB*9 zH-zcj+7(x+zpmz*cGQ$suV&j^Stle{LXV(vI6KE^XfdY&U0SfnHheuzliqF0LxP7!Al0hv`Ps?k%O7h1P zyXCZ2!`u3C$~)r9pNelEA0x;AQ?Q3s?%>D3HjixW#S}b5WJgg$LW%g zRA}2fS9rt`Y-iG`hKgJ1R(e+gF@M=O0gWH5U1W@Dg9+G~3dT97ft%jegtdC}p3N1= z1>D_xK4pv@T<}K+DJI>326|@w(@gcWokZ<{U+N-e?mGA$hWsy##?&N33}c{H_q*Ds z0}YWFn9C6N+HXCBa)noi9Bp3{>VNdp*xndusoND<*3)s3z1wUP>I|TyjZx|*wb#q? zRtnRd1Fg(&Wy=MAuK<*{|HzWaRcIH0Z?l!B$2)A)HDzZD=6Dhi1^0{xJk`mTx!RY4 zO$@-Iac(!0Q-Q=hqPCq=%U)7 znrnW9q8@&Za59=uvG`%-ss}hY*P0C-zQ0^8*hr-CU(n2}Fz_|{Z)zv!c!x=8ECgzE zK2Vb>`@+Gx(%HV7zS+Lu$iX)0G*;Ix!Q&(bMsDOgk4BvbI~AvylLiUmn7BY{7PDk7 zoXpnd#;a<_21|Ip!F>blbTTpov~spl28zI&%C39e&b$r60~hdL8V&o{d%(sH)7{3 zMXo4UfWgEYrnOT)RLHCgaD{b%ko0{{U{IY>2T4|cc=kk)d zm7p^E_+d+B&m?RMo00$fpcw*_oP==b9~ha(|(SJ|G(*hCN;%WA}TrChYRp&;Gw;P%}NDn~X13vP!F(!=kH6&X%l zN_35;+|m~96{@=q#d67#YSLP)zM3bZClxIHCYyIM+#xhJp2~G^Em$rzzP&5sQXt5 zH8S~e>f%gJ4?AD|49yKD{$v-@i(h2~EmISEXk!$ZPk)V?$cZT%lf67{KZ(jRUPNB_ zW?{O3IFkRZm|G(Ehxz@KL-Jv@v$jw?k{jI52?sZaeriyY)!;!=4E>X|LHB5q1&$nQ zWbXVpJuwEvlLeB?A_C_X8*Z^`DipFmCMhR@e(suXjm^pqYeEom8$pewm|A?J1PwP+e+d6+U-T{aE}Zv+;W>Gb-r?`vxy%|D?;~qF8>~Gn zuEzl`Fy;sS`ye0O=Ly0<3b0o!ALKq=N+Dh|4L8!9$|Lp{wMPx_<1Zrk>Fl{|>4Ey^ z!7ub-GgJ-LnHU;Wl`nPI)6cjoC;Z5^Lezw@mRP?}gtsR{B1YGOc99JETN5^>`O`gm z)h%&<^9Fiy;Kk0H2pw=^pvL(AqL;yL6j0og3yg>z9-HMtyR%a#jF~__;`NN_7R-Zh z1k=OJvXa{hV^1c_%S7}`q%|W9nHDX z4%#g|fsaZa=hPsdnxoziLW-A9@qi@f-^hg&c;W7mxBEBHC2h`PS%Sp8e^<@L$I%~u z??5}>;=%))K$8S|{K4cG67xL2et|*4CaGl zFBUG0;LKRWR|4zg05v#Om|#P~VH!#VdzG<)8#026-UA{z{dTfg%;7+b_)R|p#*t7|A^7p0jLA_Tb$M2(SJY4YTCmC^BGeekKh z)cGew!?GTp`Dp$3Y>UFtt4h%&EIS~T-`X`LiHPmRLM}cwCr>Ea4}W^Cgee#9G*Z%+DH@ z|3oa zHa~^5Z=p;HLTCw?LTPSM!M}TbV+T3gV9?=B$WE^)rAmp7XtfgXdYR-Kta6%+S&1!< z&p41IM1AyoB0>03DY=wSMi{55TwM&mr}k@Mu?5QR#;=MR9awqYcQC&Pft1I40#8#W z_0$m|0_(&%(OL9t#&dT#AZJC+6>6(Vhdmq@CA~0yxTC_dqSTIOI0TxB&P*TkxK3ZW+hadacBjIP!$de3P3K(HX<{*W?jGBWR`@Jy-fXAy7J0BvAWC2iEILGMRAf z+U3lo!vk(}@q{$|wMt2MTGKIK_9;IRKS^w^y%YR!!*3O)=Eatnjh}7#j8^uY7ox^} zY9_2pG2;mej$5_tmx}Ku8mAx%J@pzWR{~a|oY*1M9!>K*f{1srWYKBXSBmQx-!S@6 zlg+-krh}9=B$5fA5c0StXp+&FwQxWfOfd8B+BZI-Zsxy<8z*IqRDl)6-xamF<|J&BhzT4(fl{11_jgan7d{UesD$I=L6&sn9XgP|O3{>FTLsmGUfhaT z@SRv|4V9kKagb1sxu@y_FEl1-_01UMs`a(mjN9OP%K4)3#{phisBEa&#_2cs)OIt} zb!bm5q&U~&)edqQE74shNtmD=`84LmS!VIs$h=ZaYY0{=JLlH|?K4NA1rf`+Q{yRF zY^Z0S5hqLw8LPAs$7-#oH27qX zaQC;<)eZiVD>gK9;GV?z*$X8te@GIdp$9jbdsA$0zk1GAWfvDAU7Dr`-P=owsPXaP zdiRwlU;h;GGU(y!8d+8l6teV5T_YAu&(4KmX~7T=@NBkA{EBa9}}R@taS zo&oT~X$P8vPI)xgbbej#l-kR~?}3-PT&NA8DIY%&RSI$g#Sm84MTEY!( zgM3(y2NMbqhL75Rt5yhrh}=K0M5sF&I%hM{0d;e zOVYDLq&|y059uz_1`-OA5j29O=jskF(M}}BlzA?HCJYVKpSY3yW?dUfp?(qWLp6J zmItFGwJ3A0mTJ^sIT)=9KG8~2V1a$3YURdY=Ak@Z-pM)u1cI~^Tkq%*17O^U^XH|9 zuJ!qEAX+vVhhZZP8v%(Cc9NlTOe%;QYi6^QvCb<#hA#I&a#)6hQ}tD^EXb!DZDrP6 zpzJO?*xZG&d2h7mdXxKNq^#$6#o^%6^Jj9R^w<#NlV7Djv>fgvU830s%4&0rjlO*} zI^wISSd+Slls?E@O>Ihgyra@`4Iij_Dl|9@&Do{{PPBc&&$roDgDaenUCo|Bk_Y&2 zfzP)W1JW+SDhKxcUR8u_<(h_n&{GE{nU9I4GK zyL$m7$ll1+$MF&K#hONYd9`6#4ahS*r=j{<Tn;2}dtrrDM`0RyB zPN@07cxQePMS7lZ?8|Jb#|D+%u|lNcb*f$y$XWxw{bgDIQ)&yGtbOso1j zYkvIEZ6iBZVi4yA#@q7$ns=0hc5x-KMg$u{7%NaA7oRQ0-l-_+`@gh3E{M>@@<9bntWz`pL0+YG_r6A?<=>qK+)H0INQ)aMFu2h~Z zG+kC#DMp$0g93K7d>QiJ$?ITg&jJ}@R*J@`s^6u)kc<2&n-Sz>@|iUSaFD@Ic7I=F zy37xw5>wUt@#FQy@#c)`-}8?vyICK+&T07IOSX5v?KXnlu>wA$$2u&mh_+zpIdVCw z$C5r2j?1h=tX7soa}Sl6nVb*=e*JW2NDC4J@}HHWI_P(J3w>#Y#Y8KT-qDVFek#t_ z|IXj3?I1gWCPW65 z-893Zu^P=heEnF%$x%hD8-K)DrL(fy@!|DL8B|*lD){G@)m>)apDiF9-K?t2(*lmM zZg=n1+HRj3EbDwr=#IJw{HQxILWzp3swaBp?e01??zxOcuDK@}lm{2ZBfNEalgP9( z&4q&zWnV(Q@fz>owT^o;S}Ja!C9;+#)da@@7U3sMR7YJOg%%$|zg)`qXBZ|m^3$M? zx5t5!=Yhx<4)-)@6KT;HSdb-vy?uzX2&j~Pe7G02bfxESp%E%H*Yn{;K0mux~Q8)H9vmPK16+q~^Cs+qUj z>XKX*wW{~uR(sdu&O~!rZ-sO{GzZoft(hnC&dMtDIzITg&#+n>4TfjQJDgV`?WQgV z|76VP%JE(-uuMgL+gymOTFz`V-wWrbegR32>t5Aa9na6rIw~9ch z`4W#9oR?%5GPR{pgO{^4KltlhQD?23G(P;{wAW#eQgN1`=g-NotRt?B)1BekmXh-} zO36bO2;4mF^~$7jc~E*gl*lj3m#nO=>X&> zRti}++k5-%>dsu7oumB?%5WcUdAz2x!iQ$7miX-YTtAl|Sn0K6b?_hRZa+hB`nWn` zp9Uq%{oz`_w!`tdQ|DSp<<^y^hZydza8oa0HLv8t+k3ep%;?qjo=G3>?^3)A%}<^*cQq{!X(C4u?! z8EeL|y$PVFJv3-n&gIqrE~D`DF9t-bPJK8ntIxB!`@LMs^i!fr^{j*sz!)<9f`kEV z`lMmOqUNle&JJ!=-gLN})qw3u+g=6lm+?R0fI8yNCc-sjV8IMwyH_Rv#*c{3Hdq0g z8EQ8E(C#Dbt6+d;C)0()*5sQ1;QMtUYbhKaFwrc!#BG+yT2rt+ek`-0e%GqJDuG9l zkOHwrZdaSKPspBsH3!jB&K?&5?0)?>4n+#Tomza}CdKx1476ffTj)nWNj%-Et1$7d zPjije8g9~L*;o<#)zaZIHk99J^<*|>)Z$bZxg1=$--N*y@>q*}%5EK2@cB4x@X-$-+r?BEj z&rQV7+V+e%hyW3#D}{ysI`_Gjg%1FlD>8A)NS#4~pvfA{j?)EHI3E6)Mb>|2dY_>N ztZLG;MWYm9@pas-C=$paESWCghTQk3upi1xzH^4P$}OrPTi_b*j+Nmm5{*H|c}HIH zIMEAeI*7vw^;@D%lDbq<)9bi;$^q^b&4#Z-^HrsSLx)FBywt^ptR;0Z-~!G*wN<7z zv&Yw7xmQ(@O0Y=!t)l5u_LVQmqW@iq80(MhY#;riw}hlOdn!f@rGV7BR;RWnv5#ZzSex<+k$Yl+n7&I7LsTr!( zm0#3I15?qFXiB#|nCFG^je>vC1He;c$hxnR2nTs{+5{-J1AZ=HuhkK{i7!o)j_sSa z5-jipOwRUt((`G{>X$8hQ_BuXvMGV}W`TqE^b$)u)BU^%l~=U3!!v&@9+k(*jg09ik+{eN7BajQo4!8&UWa4==A5G>ufj z=@3sc^#PU!3^+}Mz$JbSu_dzjF<*lO|0f+GA^*GQ9+4?!u<@#@v+J5D*%#%Du?RvU z6q;)t+b4<-fd85#F0X$|aV!riK2x*8zY&jgeu#EGuADuh?i>zio|~H9`a2&d*pD5L zcWE4#{5hT;xZa;XH7%G0nX-s((AhKVjWI=&r!ubEpEm{>p#Y@9pHE+4j)lb0_ycWKqYPfDs6=dw{H7Y8aoa9bI^rXQvx zU%fGYg5e1prco^{6$-E`F#56TTQIsV4(4jnd&Hj|FIE9gvvX$)rcRT#Zp5;-U?AsYC>u ze(7~_N&Gaz63QzoJstYfnI}UT<&Z9$7H2Lcv(f*~i|3@jM6i&?^i^i^&_X$@Yc}4WDQk3!%Dh#{zZ4{ufYkETbf* zz!8VHotu|WBysc=qYMiwX^41u% z52fhpuE3u9huGsYQVlQ(S~V`(G#kD-IFJln)d+*I3|1KtABQ=2y8m1@1-O7cPAH64m;C2s=A-`&A=THIj5_=slE|$)ILYugmoX`Dwm@zz zVA>$(M?X_bIv8Ca$HF@x)eC2%xv!>(73yKy!28@@Hl&ZYmZ9a}(lVf}LWYs=y7WCQ zBQDDio18p7#@*OFSJH-iCBJ+!*z_8WJ!nEBS+F9?6#V!to}^UaK@p^!70wn{SCL`` z`Zd;>(UY+GFWR&q={Pr5d>sYinT=U;mIU&u5IR$m3{91Gh)hR!AO6Q&v7oviW;H!p zwfj0lH7ERdYohCloD-vrb$dX_O_2qN;T=f97ApM>U(Y(6OSJgE0Yd6hHKTFFHBI)~ z0u>%vNXB*PjAz50`Q8^Ps-I8H7bKQIXQ(!O&-_(>k*BTezI$9YyXOs4Jd!!}4`(e0 zq5W!af`b!gS9P~H0}re3k199v42C(mt~eDzp8?s)!?t0XDxt`!9Uk;-uWy(OzFRDA zIZaZ{QElcToo_P~1{8kxgw5V~bvGx>OW=ERZO_VedxdN5KSeGNik7F;WF|nt3C^~e zeTSEz35UlSb_Zvb=-1qSs|YWzgF0?UWf%IJ1sylP z_`VN_Zt+T9TdYpk*s39n{qN`HYoaS!mIS}I9mk@>8jdn3!yL<~<$8zROgG*|_BI6a z-cf{}@{_;f#9~w#e$0*;2-Uo5Mv09|?b`pb*L}B( zLW=llEx&v~`iIn9=IeBD3O@QD$Dk3 z*J$I-_jo$M3zYqfk}L=FM*}8k@&4?ze{E8GZ(4R(f_SSK7MWQRTJgeM{i30VT%$se zcG>@J>bMF4D)^x&r(xg1MNF}+7{@#R9vdp5&r1Um<9^Q4dF)E`B9sDMaR_qEBIdEY zOd-P;IiJ@?@H*&EJ`AQzeV&Lj#8u(iO7^jhS(XCA!k~p+U=tlB@!HbT_h1F z2|ZnivI*V*#V|wd22$m$qHDu~N8>(;-B*A5MEUbq7R3?`ALj23DX8=c-tc|}jm`|) zl7KeUibxtmjrRhA4h%1zTG*IvI*jfhcg6`ehIwb$P)ZB_uN39rChO1QfO`fbSq3nV z6;IB-DzCq#@1a~*9#*;?@L*h-ZRz?Yndln}tqAN1pon&3BQKPf4BjUa5+&y^N|jHH zf~`H{K$||UdXKk1R-`sRr~PzhH=j3bbhX3cd*rn7gy{5WZ`h;pNDs%_YsvLT?4~1_?eBOok7?+ zbJegambBYr$!)g-qalt>wL)_Z_*Mwy?(b(uus7R(P!hV{dcBjQoUP_m#FgAe2=sX> z9emAZltc`)uOb#y3c9b7c}(`Br23!b8z8ZEdr!g))VK9>yEaaHw|zgmJt)27mpVS~ zFJoYjs#piS-+Bk;k3viau;v5^g$7xc%7W@O$7;?VKR?OqJ0G-{-M^4DOB3E1R9HSS zA*Dcu#6S)xuIb3&_7gGz!eNG1yal!9$w}| z!Zg|_dlsRg$@Jhl$%N49UXkz?3i-(u0CXyHXHeX$G;NcXg}ST~K3m^1s=F6u8&oTp z_r=%lJ^i@28!*|hnvTXOy)~H>orX|;qf_>B4c(|oW$!?~u zhVbBPEpR~LIl>=w!Ib;qKYaP*?18DZ7M#C5cp2P z-0M(0kIUdA5s>}5>7Tjs-m3!hPn&d6#RhBBkDOPCm=VDpk7ubKcTic}Z4MJyeGVq$ zI3KqDdNPx2&A}dWKq4456p8~Ms*CQcDN{e4^?|O6gn?HKjs1l~^);TDT~6H>Oz$Wk z<0!59ie+ApYO7nB|D>1$@Q-6hZh7lpB;aIY(!=(^%Rkh7f4apI%oCW@&GCZt=sM!P zZ^j6PI(t=)QMtXy`P`RT$^yxECX1qS6_Did#A+l_-X$d)&VmMnrnKeRkhq@C%5~## zN6P4~ntL68kw$&DPKQ$#PRS8ulEZarT$k08GZNtwI*O^J6PhV6`fe@D< zxaMbE)OeR9ieKfmvH%5|E$noujra#N4ANnf%($ci6*2bVoI$5L{GFdyVjCs+LTm=i z@1#^!`yicgex%5^h}qsvjg*F0BqUMt^J#zWx?f@Iy*uT|PjOjkc>4&IYX(g06(^~A zKq$4?_?t~iSaW2`kQYM@HBIduRqcl3I*D{PFa`qUB>dJYW;7e@=V+OL*0 zF=n`*%WrbXCJku68K*Ok4;{Q_k#&**o(ZaNmP%~rv}ZGk2yJxkjmNI+Ypv9?H%)~) z5ABGo1RP0#6%M)Th{q-h&3(2dqdramQ655d)aP=_QMT7_3Qk5vx3)%R{Ykw85+6Ao zTg%G_GRb|EU3Tx^9TCm?Fs`R`sH0ABU%BPHLi@qtVRF(Sqa3FDP8jHUbiE1q)V4)f zk2v$~?B#2E@BsHEdL#@RV;OXZCO%E-4K0Ng$EFCF{r%jXvA?*Mr=s3==feE-ol?q9 zF=-(vZ$cnsh?`nOr}Fi6Lj-6xh>rKGM?vh6`$1&aL#U*DKC@2YeARAfWA0Y&lSZd#T1@?vFpA?w3jH$=H*3^qdp$REaS^pM8B)wFVNU#Y?eF!?U9 zdLzgyJ~z((>1cS}f5NDgNNVe2?BO?{+4+&utUB{rq`Lul2ah&wuBN$f_==R0yM&W5 zJjnEQ@FMfK9qz^6-jPpXUQcfG1F1nVZPwFG2@l^lx+|3$>Yt($dh5PV`$pm#ic0>V z6cWAFMCr!KF;yhvK3`tHUD66XYHYV2|7*N2=S_zX30~cY+^O2;2gXrurNvlMRlJU# zm1=6g^`OF@x%}c$MY?o)&hKBj_|*fT7{t6RV}sS#UFHV znlEL79~@3R7`Wfs`!~M5cR3m~OA4<|H02BNti_{*mCQl(pms&?YD4Ah7epe|17Yhc z8^qEkU$sZzp`N#X-~*)vvqk{iE|UqL=!{3;j8o{@s`6l8e61zb1%?WkLwpQm;SgY%o{Td!+tifoxb!;eIQ>9TD*=#lx`N}v_lSAkMGI%D`*_e&hy!`$PFyT<6 zv+B&Ef5mbD! zC)k3W;YTXKdPXXQ{G7rzTv!pEE?w~Plul3y%y#X` z{QY$0E*wi0(HcUTQx1lccdlh?6zE7OUsn8ALT!*|1P6`;F0VN)*z!oCJK+z>KKB+D z8wfmvv-djz8<({@J;ho)cn$a4yT4m7M*C~8Cbto>f8u=Yb-)yewY+7PQ#x00W!KUE zb;&VHV*ZjW42rVGu(NnVe1B7^8_FypM0{U{C>LKwS{sSOD- zI>*lTCbo?WWXWk6tD3IZyC|eyQ2)E}4A9p(WNC#w{bSs;#p8Hp@d|ello4`H)FST4 zW(QOH{4Mjns7QQIYlH(;2#(o{HSKdZPEIu757Y2$HD`8GThft%oT%G^_3*6soj>~a z-*fFHPlK*_0sIy*-epRE!E)qe0@T(YES{`w391{PcvL9(GO?d>_8oDmS8s2ZZ5F*n z=2SC+=qm|bP z4}Eon6$eWd-vEpJh)1i$s$|dg2_5 zUqhJPDZdQw!%rE;jd!uoH&%z=Y2H?^GC(XY6kOQ=)q8crjxg%1B*SZ`)p@ri8KlgN z&Kcoq{ie+T)#X9=;3~(pp`CkWYkDmAdgJgVuyJC zF~{wSKA{k93p3{|W+>aPcl!EB3&E|bRgLcISvBGWLOi6J&25F)7gbR)ihxvjm( z#FA8xwtPL9L-pMMkS;}l86grtm6wQT9CZn}Z(phZFm2^ZmY6974+VQ=7=Na@#mIad z1x5^oT!{cO+wM2(=Jau1$F59Du|_N1vVX95j*Muy@QLZp$kH(m!D=sRR?EGj&6BjD zXvlB*{Hc_I8*Y~{2f&U_?L5Dox$SC^%GPW55)!^*#!SBA2fHxRjB=0lpr$z#zci%{ z_P$Vex@55{;>sT8uv3KHk&T-mNQDz`^zc^`Ct6@PZH#Z>j`A`UcSa+aJ6tjE2oE@( zQ|1sgKN|9FPdP(9Y9SKRlla%}F=nk0eFMqUo@fVg`s8nlUi^*LSPY!2kY+LXL^~lc zTIhoIA6E2up!%~RyZqiz0Tq}{lwLSu^T?kQSr!>!aPgGJvkJ54e#=K_vCJY^swM}} zC&|?}PLzBOy0q2akmf0%LOcfAa8r=Z=jvOlkK?T-MwAKRZajIMrm?X)>NsJlTtw-2 zpJVIrAv(c1PnI}obf~Ez(c}!rYs4sb#`}7Zk9#$Y9-BMa~!24ZbkPxOYXx{cj<70)vuG6b_p5aB)j!Mcs3 zy1Z6#?D*H6*^pIw`SCb+<1L@CNYDYor{D=Nj}@$)k+jn+(y=5*sPN87uYR4ScLt_T z#Q1(xUNQUWfx;yJ*R~HNt~+CT z5k}AH?A>|?ZJ6D)m(6Bdy`Bg3byyrSJ6sRkM)YvA$@uE_3K8g4&%A+EJ_A)HP%7?XOg6dS zIECkb+}&rlhh)y-^uOT5{s>zW*YHIpMGNGc$bXm^j9$Gai-9X25VH{9ohbkivLjNN z)$>30Zj8?;5aM%MLApbe10n;06sgTxSjUbj0gACCKAyLMFAGY%w|M)Mv#1^6xmG-CNRZnozpua{ZxS zUvj=&p3)v0&)cpU$V9`82F(VjeK!bITvV%GwEk9dN1n@P7?Bu@|7T5e)0?2dl%D5$ z!}@X~YZbKxCH!;n6KWZU1@DoF2uR!)c-^pE%7z=Eo{;*G-IXy)?VjtdiDM}>zO@DY zueB}4nUF|3Lz`uBTxpE`qfB2ZjFQS{eKrZBN>HmMoqkQ_>Cz8|3rpU{nflKZm{+mE zcTC-WaF%=Lzks6@LcEt_+htC(!%Y1dJL{JPi6D@+2{{dR0_^7pM z^18lOn84rLZb*$vG`w{c7%0q*jclf|@#=hO!OH^n!A`t23#NlV^~@sBCkQjQdWJqG zd+bpSGdJ?+wYkexrw`b1@H3*7tFKBl(zG`t{E=KH=rm}u_o|*Fc4bH730@sYB4kY$ zN)Lh|?<6!IpD*S;+|}3{Ub3XPDUp<%>9;2s0I7;PjrsnTwpvdPWscsu&!<>VD72nQ z16+gl9HqACV`s++Ii^Od!{99SUP7R(Rn!X<4fHP6 zqRm?X_F7S5yG zN3{XbZ|C&ANt+Ra40~O6WtZzF&exV6=8fkskj{PuBHIA*ER)kWdm*Q&rByPXS z4(hso6330l4>erUgb?)HgV?`6_~m6i*bskHJ+PAbO0ua05_<@x{~?E8 zu=sGOinDH=JcDOF-`@x9O_}Cqd7XtzjEtQU&%XEv00NJ0LtRO-u%OfD=t-Lp({319f*&zD28( zAq`n^W=!AxMg!bhxo<7vtLp1Y&3JSnDy9)V*_Bjc@r_Z3f{kV_Y>kjWSJWcEFw(nd zKOTx;iLy2Owf0_~TNm4Z)e;M{exZ)#M85N@Pn=05@9Bq}SnsN!eU~4Natzd6???Og zHtcr1R+7$K6^bq~9J@FgcJmhHcIxR-pv)Ey4(-421}9ZU+fS1F^1$le9Xa}zN_Rv| zJ+Wo{&69e*w{*VXg-&kauo$3N&1}h-(Owy`HNphN1K6E%L`@C`VkbiToO{zHz6`beq+b2huf zpo3S8HN&|tC#uoU2REzwvJuE}TP@+1r&|c23esGJ=Y*}J*kUPUy%m$WEm@x;NrjG@ zDIf}wi%eT>tA7G(;ObzoZ_Tk%w+fVxo1 z5pm-7Tk#z^FTg$P2NU{@?E~xSV*Yomh;#{O#^b8hs-uctxm9GQo0P--xcJg$}*W8#xk`rIm3_aw?O<<2T3!1ZTNv_ zZc%RRUs-`_^dzrw$fkIMM4RudTJV|J0a5XvgpH{xP}!r%`&C;kHynQQW0)-s`-GfR z%*CB5MmHM7fgYRD53$NGW1q-vwsUX>{yN3>a=N+pzMF1?jtNEnvw`zkYqnhLnoO6Y z7QKb$ePDen`F(hcwmz#}%+foYW}8D3%u;cav-D~#I5g-ly5kbihw&L0r{1iOJSnM# zIyg5OWGl&ZnnY}~$> zZR4O>`=ENePVv^lvk0MzfO@D)nFzbZ6MDbHd7poj54OjShTgfBUyTg>Z(v_63-pxy zjioerHLmkYV3~CG?&jpJq|IW*;i z6y(05Fmb(`Ivjjs2v{~T^jepQoam!omyDdsvd&sFS#JDxXfzdNz2NmkNyQJmlSO58 zv@j?WMIK?x-M`Cs?q<29Mm}0Po!(X3jS$Pwin=pBXf)I%J^)=LEbT~B9XI?tfkF3K z9+lu!(n=C68RjoEUw;8@F-M&S>sQRQB{!+eP*&9%ucsQdgAjFt#zD_}Ap?FBzz2H0g|+M+rQb2kgH!x|jEF@fQi~ zm85;N`skV#mUFq?YRKI5F7b_EG|>W-l2~X58N@!F7Ed~YcD(pulG&d2zp1*KU0t}M zW5(UxyW?p?rV6I78%WlaC$fiJE3W z)i!7dHgn_Ly>+7^77rXM4g9i`6tuEiV(ky|jaYeTJi$dDy8?*T*794jAN?NGRFr%< z-uEz-x~gQD_~KhtJ>a*UZ>v5q%IlBDQ|kO@mR!>jzE*5@zkuWjFvA+6C6FNxO<7Pq z8kpH|#AEfG_^IAK@?~R`+t+V`Dv~kh_rKXH8t!zH30*Xve{r*Lvi)2hfaP6!LO-Cs z@jhrH)oaYhdiUj+8h>`)u~D>oEDcxbDgvYESB=bpNt^bsNjvBnmcqn1gSsVb@s|hp zp?-0G%Z+6N+|OY_s6$AKlDgGkS4Z7Gw2$- zJ@=X+NN37V8|KHN%k)ck!1N}|AqLAvk=OIr(=(RI^CtSH5)PTQS497tw;Yw1tK#J! zN_77XKmXHDS4#Z&7L8sDrMX89}$BA-89@H#9d}Avf%|Y8P(*Plr4q zg}l9XqpLX~ACLVwJ%8gI(x9}Ee}J|;<_%?RxIr)9Cf;&QPrH8^`0{(~4*tF@GQzhT zyr;H;G+fOD)!|zO$xcd53J$J51@p-g`K^xbrfBF12Zz)D-vvMHT5bae=Z~r+EA`RO z?9>!Bop`XR^A@Kt%TqeSN;;jzPzwt7oFE78=k|km5tKC}6ekQlCWP$p;PHuOubyvT z?*j|Y+Gah=P*H49{H{$MYtL%@ejd%$=*$OK236|SrkX^nsGNDs12tNYZUsgu3fTpu zTu7TKTZhR<2jE;b=df*Yy}L=Z9yklrDK*V;c1n%8aaJQ1kHDFd&#-T0Ho8z#2!^IE zEFI2|W00-yN<41LZYbf23R#hhEXHA&$gjmhxlF=?TI@P<6^{u^o|Vebf>z1Ha?HX{+{V`F5NJ2= z8O&DTPs5Y>FP`Y~8>T0H9`Qy{nyYYZWCYvZSH(21L6%3hP@=T5_M5iGkZhWI1L=zi zo#{cn@vL4#CX9t@7l{2|P)!xY7xN7fMo@B-2_d{Ms?_H5agtJ_S_tO>FP;2Ry z>p4xDtlk&cd?A4aceGp|@%GR!y~xDMSc2R?fSkW};g_pkx4+NbG~H03s7E&cAuj31 zcfb)M=lAg=aKo-&KU{KHtEXD@skl(%yjl$r8O zo)(0V7FIk?v~Brx9ONhB&W*pbZNeL#0L^!zXrW32@d#~y;TZ9TVrm6zy&8JG8@juCFqI~DBMKea)46CEx)WU;%QYS*eD8j*%TEtjki3s3Gian2kEqOcWYJLeLXz@SsNk*ZRn7 zG})nFZtfV5`szmuP!$$o-->|`+Uqov+0Yp7g-1l#&`9t)%rA|;(?N9D$Ph+=2PEE} z3lN6B6K4qej3v*Nk@*rCBc#YLpxE?IF=I!UeDovo#ymRXFTAK2^l(~BE6kc541}9h z!D1*web4HdTAPJpp z0l$j~4O8~b_e4cD^Z`#vnpBofES3>0*mprXM950Sa-yrKy>_5-IS5dX`M~a8A-X?r zhXQ@-18PvTBBX^GJqa!!yZ)U&eUb+D#R-DMQykpL2L!*En`*cUd3Z(s z3w-nzhABEUg6h_`-djtNOGL}M#_irwrrwy|?@eeVNJo<8IkZ5Psepfo@OaK}vJ@yD zy59%qU*XY`Wzj2_3gD4q+3@ATy3)w3s7l0V(dE{3{$>iA9u+V%NK6V7(u}LqvphZ<|pp5Lw-j`n>!ax3G zLA~|R{M18>B>!wL70R|=O`oM<=62Y`jI=SIM!NX#g%>M8UsdxX#!{w z4!;G`)-rC8Qh$l${?gh{OZ{b?YJn#Xn==9Kg&qae%Dq-3a^xyT2;WJsN;mMnZksn3 z`Jvb(Iv_$&s;xyH?hM%-89^2vWQR9`yHLp`A<5PRVBePBB%qDTg^R=eo~#dwO5lS@ zC3gVYOaMXv5N63&!VEe*`5+90v1zR!ArUqNA$*jJ{e!BDUCBQhVHzBF`0KCnNh#>4 z_nYEG;VDXS00~O*2wAd5$y5})jT;#NC4A+_aJMj88*+eR{?hUn2}dLZL!*9eG$s)J{#vx?|IsRDOy}x(?fevCT{>T>zGrUPg>+|Fp_O6WvXX4BI>0iy)@&I*Z5 z&D?f?H!eK`yDZeUgcj)t{X&<*G4fWC3vFjpR&Jmoj?V?o92xZ>#t{kcFY<)o3(O5O zVzSuzVrf;Rmpe`+y`dJP@kgI}1Jx)6x)*QVDuOLTzrIf{VmYnJbIVVOzF{^Avn~BB zfaUI{8Hz)?v>78Eq1I>{iW~ODk(*2|#$vVLK?_YLxU9)c%1g`NVk?cey7qHpj)aq^`_iJNYta2%lARcLn$omcIs+zXI-@HoScM{^2?gYlbd9 z!DTGT@3ghz=X!sJyA4R@-pki#&V8Bg*_RD&!M|>(&7g&S{1Y-n%k9qL+vturlyo^Y zN$qfVRE&cq-aRY%aLfIKouORV3sJnFhnk+RE<&P;q9)Q{UVh;zMg0gnL=WJbU-i zXOy6Vy&h8nUmF*f;^_d9gal>tgq8~Ahi!9$0Co=M1ycjznVcxn(V!RIG^MKo5yl-Y z(m)}43Ss_U^-mk`bg24R6KIj{HSpj2tx~xRkosEOukE&Nb4P+r_i0qu1lPEy7W1vw z`nfNQC;E88ZT_M{yNIG~C>20XA3*FJMV~Gm3%^wpj}kdP(2?|l@YgU4~Gn{FR4#|+ruDv$cS|OMUMr3~&yNbXH+X&|fo z`)aSapaHHvN_86FVA3(^Rm*RQ%29Pk7s%d1Iol!CZ)vynbxlA;KD)8J1TL4-Xxh~v zLA+A^9F~_doJurWs&)~&L;5}llD%ijUKMMB5@x!kvDR!bX_)k>mHtmth`z7{w$(LA zd-Gsq#KBQN(^A`l${)!+PJ#>y;G^>Hf#SkLTTeh_V%+=D9hd)K0AvCGEdm#w!T*Ls z`F|@zR-d-%{pU0%gS{GlsGd7JX%@DXD7aIu1xlpvmd4Dv`8JCGx(*k)A0$3=Sz24! zl9KYe!GFJ<0$BR@<{IyThIPE;4@23j9RCmEA_6N<5iSPxOKS)ey7e#qf6atpRplIc4(R`W0o)fv9KPqEH#m3sUwP7!-Zc#Bd!DK7yq3Kw z$3+ryr7Ly+b2~p6h=IS3bds)%-@R<&`%1a>Kl5!x{{9G8AS~q5?pDYcS~X_G89q>D zn~&YI`9QG=J^d2^ttsWM61$#~FljUb8FN2B{zatfovA*- zH#c9TBG>@FrhI5MGWh50XQdgB);q`V)~(=8>@YzG{MR*{N*9I@K3hBUN+oKK%l2Y4 zXH-hv)Z5bo2`K`bAOVSzY>eRWmLJz@-9JS!gA))bW@;0Kt;}3Dt&xVXk=JAt`Beli z|K{4mjV+aI#z?SRsXo@X@^lYLda;MEAMu396nry$pI){)%)f01(9te`>{@7Xx+geYafP}!3V08RRf$NC z);zq|(Du4B%Xe);n&kUT_2NrKcM9jC&{saDR@nA8DECDG!RzwJCzT(IeZ@SU!^qhU#|jlfmYH%b&C3drZ!@c-*T`A~ zn@p3`Gk`cOCva(bXYNK&AObZxs9K^w7=F}-+u?ECPvHrd)xoF69C)1D$FzOLUHoyK zMZHytB%p^^i=;r7R+??}`2p@()z)L@d$cOdstrij9D}BobA~k>2o{%;i21OYov*ZF zkh)y%V;~^3B+10Ny>!nkYe=}zOq^K!Bi_|wCmGC7QM$wDaK9FE*nF3D_eE{Ktq>yq zg-@4eueT1!K4kr(F1N?~EVJu@cx7jpjnkhk%)?V3G;tB+^HAS)F!9eSgejMma_0NG z=#pD%RK?cP*?1c4D&LY^B8ziXRhT`KH8x|`hnXzJGHA0(_E*l~gL5}=zQ5pc>aCY`z}|X^OzVccl|PwYC^r{F zd&7y#;WsZVGTa;3^ClbE?&8zs*L;%A;eR~tGAj${3&_ug;(OFpyaSl?6;u2Xs+UE7 z*>GQhPz(0E(TTdg><6p$4&jxE%PgkncjM`|B30?TWQ}}Omav(py)lLZOx*gKyK!NQ zPHnSMN%FkY&tZ+n>g$z}h7%Xw+Fl2rmTvoNwc%sT(?zYY_6RZBRv?#Oq&VSJ_(5&` z*oqmBkY;I!mx6T{rsvD`WT?^XD#2eRl|^ujo5W`3)3@LHH zfZ%o3FccFu3uYVl4v4ZGIuIB~g)GuO$_r^rGM!$7=*VXjfk{Nm0IFTy# z_{PNXMqG0FzR0 zV|H$*g1M%h1TR)bNQD36isuuWEfW34EJ8N}{oq#ok-S~Sqga&P925o88=YYL;LIVh zHZ}dnr=q<^D|pL7-~JCtb?hpl0P@YY`@wYVRQE82^!WiwM`S>m)3u$@-(!gK%&h^N z?ev)jeFsirY0yu~E5^TgmC3UV>nCdx%AQ!s%0weMyBw~~)klC;o zR58!#rthLtkqYm*iNkBSpL5G2k*FF|QM^HIBaP-R;f)6R@|-24xE^06J9PA4KvG#+ zyQke+D~eYNlnv(GFDev^(I%kKqngTH-NrRL7IV%6f&Rha4eOn0@^>?{O_F!Hi2U}H zyVBGW2&Sy@Zp%}xvBAby*MA-kNQAIwUg!=54RUdL*4GLBe! z3Y;%YAMp8gG%C+Uc2$zQE;!jun{=%ji67T*~11`xoK{uvPJF&7O7 zt5Iq)E9WLEpPV6toQ`wBcH3s_{J2Iwt1_p_+|$T+1e4aNXyL{2)4wY|iduu5UVm^t z;Iofw(0>KXJ#s-+4MwvSyX2vNHp;JSu2M$+HFS^YA5V^8f#$yz>sQ_6XwR1Hwd8r6 zEt~WBPNp2a@)0$yL=;1A#y^l_8g{L`MCQhZYP3v$AIFU_K~LCFQPm(}(AYx9b3#ZD z?T;_89fMY~{3RdpkiwB+opGZk$&g8rQ?TU}Hboejr@l>V%FQfd(-_rD-#(&!%~+H& z%Pusi)I6)FoEYioB(=RSD%f#gv2tfQfH!zT)x>4cD*z9mjq%je7{)9XKC#at43IbM zHC9Qy@E%>Y+-c#a^iVAOJdhfOMtJ092!S?xqW@N@hbKG!B8Ov4MAbHnggA$*UZs+t zKRRRKRHpv(T?qk^uW;EfyY?n6490FA+lnlotW@vs=BVvAKE;MSsS$+TDUBFUbzPQ! z{5jCzt*jS1LqlyL^uhWeJ+yaSr4CRtCW_U9U3T)dgiKa&K0lsYr|GHi&|XaM8!Pob zO@?hb>7Ib?G46t-4I0LSuJ@DrlH1cy(SfGec3NALxZaB1^k5j!#<1fR!Y<-xC|{g! zuvqMtl)??1W5^8Amyx_d4d8bhRLV}~c~lN519}}kbT?vmFL~*K4=pVB6JTN{u3Zx| zdbI8I=2EWqq9(F;ZG>9u+Ov!tJAdQ&v)WEO#^qb>b;VPfo)L6bQ*-ygadfEAAc><3 z>bc8IkTXznj0^n%;U?Vs<^!ytEEM(LB zQ`b}dyh4$XIWCNUBw=#_u3_1eAU zr{|M@uj>)kv6LzDTZEqNg#TO1eMd(!e6c|3j(*5%^O60rVJr~q&?ncI>@-Me#R7N7 z{=*gC)?^rdlQ!oQEVEP$`MCse9ZE1d_E3OfS{d=;it^zre%oLdA2H9vmr&-f@9lHt z3aC+Ahl-q>7G17z+02o)$utEj*gCj)O;I>S!n;CbZ$z|P$RZu0BhF%Ms@=k?#H1k9 zme7S3nK9%eoWe_Oi^iqkfBMy7wUQrCY>+JtPlQ5E!5+X}G;Nm{tX&Ew3Rb#z(Ro#P zi|6S!cEz4&VDI5t`+!_|6L_U*_m4oe*CcQN3m()l8jiEv@IL+OLxaw zR7=H$TJp!~6K6>p!H+2S)hI&3J;YK(X}7--mwDC^w7MAjKXG0XfBQ}n#z`7>U>HLK zvKzT&{&4DA7*_m8E1PR37+&ubXGGhAtTaY*=ow&V#NFkgcdwKcNxmq=7{Pwxx1w&A z)(aqwnVmqE23%^Pn1@4WNO`V}5rp1Nq<Kvz&CP|I&lZ^!Le zi3`S#d_}+uPP$|fImU;i7zGtS z3X#N|yPAoVsGvc5#2<@)+LOlRFRJNNTnAO7UWd&(%?}3={-9@9$6>FU?Fan26*ACb zDv=QjMRKSfw8+biB=n{YNR7IklRA*$2Z&3ulB9Ufq+RSyK@?Q_H$E@H$ZCh?HxU7$>AI%Or$#I$1R7rFodhpHIYDBmvLW;M zj3$Xa0hq{ZdBAqbKFGg}I=;MB#U^}V=TKBAPq;C_5Mf~i&udHK^|?Fa1G4lz0t2~% z(Yv%5Ddvq8PyVBJfI@N|G8NDmA2^1iYBe@x`>Sf8oIHhiaN=YfliK!fREH-*c{sVq z!FY^>s<$BAN*}d1I0>ifMU#m@RYIL~ybZr*ZI7x6E!na#EVoZJY$h}T#}6mTFmnLj zkY94*JDK;_6U_;EK;aJ)g^2Hs3KR_%(2596^(f2MZWMgSVJQWRWybD5rHFXdNJdl6 zc9Bj~tioHuWW`mr2*SAOH6rYeqxal4B_3UCBze&{)?=a;OYXr-^2mR&w#FsMBJq^4 zY@IMwB1o#i@#KT}oZ>y+wYWl*k`%c#GyT6h-c3Ng>-#h0g7PnNIGVoY9#y+w0mbC%1L-SP*qHd()aD67TtqV zD&cjGiy+2J-V)C`Z*Op;!dpoi?T99f$D>UkJrWH?4M+aj(3NFH4`et2U)S_U94jHb zdUjPtxLrBs!5TGiMG6AkRjM2C;-+a<;n1w^H%fle3dR~z zeO6+3+vhX(Ftdv2Y#r=$2Z|~;obR|rv!S@p9O521M^I^lWg{*Cs!>*Fk#DWl#SbUw ziqJ9{kB39pIiGNNm1Bg#AMv2p4iXz$i##2im}nOpOb z@RymXKj?@D-kdVzDp|k;(TaBO?r`0Si;)}~QL5k{D6kTjYstX8zCzeL8>==!%_bv4p9SZBhmSf4woDE8XRH<6wRXY=W`xQ^BsLGG;O2dznziV+jTSe~1{&G~* z6X6za0JF>IolkFkHf{STF46>MQt&Co-ran_R{BTG;`)K549xyK4L8dzc7hc>Juz@$ zUp@h7aWg;*F_3?rvLx+&$BN=V(`a0zLaD}0{DYke%bwVwbxKpslH4ueEm1X%zm)1D zQ<1;B%nRFX%+N!d=t+;K&df^$u0TQTyI!D^?Sq~i$?vspNt1XuGw1aeahx1( zr%5~J107I>Jk1P;^k|HIfT0n-$~3egHqwTUw_4Ju^rYnk#E`l^qFeT3uDlvds)qu7 zb_cT)6Wd6EO@nus{jr==NqI5VU2mMZSCBn42E3LHAoxHL)3P2$MF`;EKy@axD4`qb zYu{XSFfg9h5cvRLsUaVhF-x*+J&m4+IxsCh(*F`U5?~Mp#xvm``5=G7I1H>xRiNaY z6EqB{ZN84X1nBUpW>)gKsuY%0TSTIWjK^YqwZ$+2u@hr2=y zQqQ0B7P5*PexLxB>?qj5)|s!MX_jF(EHZXN)a21^p~&ot$aQWq#2^XDv2Vx6Ud&Jr zkYe=GUmDP1Lhd0sEHcrg!RAp_x>LS!lC>gS7)S6J+56KW`gIS}5eq+k_>ZPVDtu8vn;YKY-kXUBff$Ohn?>s1D6qQEU&Q}|u zxS~*?w4os2);vH}T<(#mXJZ&5k?aOs@*b`k?H7f`Mj}6uNZd0(nG#D2M3gej(Nu>3 zr4PvviOYNXJlm2YZ|6}t0QCgQLvacR{BX(6qR2`6M58NtItP)LFZd)#3#_)H8&tdS z1zW`@qwBgzt^@;J&J~$wt1Y`0L7s-6o*ndN>y9!WCHl5<%(DW=0fP2iJ`0^pE=j}^UCkf zdPYXohdg|9d<`DH&pJ{Au#M;uCEMV4<~Z9vUT9mf3c zMxoVy%}+Qr)48w>)eYuNBJ)+j(H%fT z=Wb2#uGn%2f|or@oVKl8TTsq~w>&4Q8^&*6G}m8J%$#AYjTH(ZA+h{^&D-zhy=$^> zha?@ZW5y^5V6)#_J!t)U0`awXZ{8jw?erBI=kXHA(MMAyJc2NC-c z#D+diqQLc1!^OQVgTndPIm9ZuT>Gy?j4W#^R)vmp=C1KP;9%DECo|CS;c!uq9~$z< zF|R6oxAr-U+jjQpJD7d(SQlsK5f~TRNeQJlOLIW=x>vmkx3yS{UHHopenWy0+xSn^>DHTh1AeWkvj}hNmr4o zxD&|^vodbm!NWVrY`ZJty#=z?{1^|d@O$m=qQV}CEMg+vM!A5NPbP>fmI7!LVXj{H z1TmN!w(q?UVy0hU=b^`5Vqq~GAN}c3;$U_BvHbyee_tOZ5^Rd%0;O8oy1wv0>X#$4 zybTda+%)iZ=m&y{c1^J{^JaNMc%+ZR{BTG%cYg0z{Zif;v&DP~sGkitSTZzZ)|Gr0 zG(EISY$VK%Sltsj(mpu%to>;~@7FuQyg&lmeacmt@^&6gFI_<4zVrwJ4>sdcY?zwn znF)}hN$soQjNg$sW1vqtM)@1oymW^Qhf*a4N>ve_2k4mIT_KYz{kwd?1kx?%A@vwa z3(XN{a=l!ITBWkvd@}uL%PjXe^Lcvm6ALYDm(p^A@5nm92*=~r)I-%H%Dm?^0j{9%e4D(;fp>MM1sx(%pTsf@AdD`?%yAX*CnFM)?`O0gI}4-C5Bwl>6x`) zr+#vCq&I9Li%IyITr90kqkkW%{FHV;_aaz$PcLbC-FpJK{sIdjupB!GF%$UOECM`xJMC{*>-Keau*4SH(aSU$rs}LUC+Y!oA@iWdT@U{zs8z7kV54I(ulsVDV+Wv} zxsavNgDl^5?%ohX0(k~^ej5F5DJmWvj9zIcRRJeT9d4K}TuR#1%JrJ0T5E!!VohR(0}mIe{j$ROva_5t?o6A7A&%4WJW0R_8%82e|s(1XL+g^OG^hS zvQU=lh!-a$Pg-i}*-w7_c(b2mxVel;u1<^8w-XTR+!p#^z|9IQCXO^5OX2!UJEL#> zXNQx4?6G8XRFv-D!=O$^7Oy=GL-n2vs9(Edsek*HrzpLLd);iDXcHf?lvR;?xoM&sv4#H9uGGtcwEmadJwOdv`r?w

3WI0KD!Jt#qz9+Uy5lLqulf#l^TAtRH`BaM=d7B)MLkzB zB$JUog+z5GtvL4(fAoD4PJVdlZGBv^ecEZ)FSA}gs<>i)afDGG1(Cd7aERu8rzpTc z)CHS!TZ@uy-=9fcYqhkMp3Z51al|KF_0LfpRyBIyt`SCVu2=)BA3Pc;tSA8=yIQu0 z^vVt!wO9N6FYp}EcEuGWHk^h)C$SsT*PS$yU`9opTpl+g>(c$AV`G|C%Tj+AorxAW zZ%`!NU!p*gs@Qe}=5unv=N2bPFf|gv9_nDTXKb zC)IKX4){N>-~?V6oI+tXr~ZH?DZr9AUnm&&zamq^zRxhZ6AUkA0DR>^}BG>#~TesX$mc8 zJpShmuf#tt1qmRqQ&l1Xjy&5aR0&mwayf~ghMf%?Id0KBbBVrgjhL3*EiTtC6ny=- zrgxm-yh_X__8Ory6OBCH{RMXJwps#o$RXx&nrF?1+;lV+c%t#p(K3cIr2MCl0b=Ra z$(}orMVrTXF2jCJurn6;*UP2%SOz;9SfuG(=(Y0N#P6eW@}KWH>gKPDp;fQ3nctWO z-{7DSl@z6Lshko_#dJz#(T~>oFSJ2BpC7rvbq4-6gL`TEj6#YT#_8^qJ<8^1Q?HN1 z#Z)xVfQyaI8bJCZR-(k+43lB^<2NTX=;s|W5PP+XK|N5JQN`tI$QenhV>Pjr)3<)> zx?uMCOT*55smcz6LCtFXVUpfhbUVzgV2rsXP?X(lt=wigL}|{Zo~rYyy`xu6yaiLF znFnih^FLE@$0mKz`Sar4n`!bkjVL^SGEOX*p?jTb;9ZIE&*Ssf@>Sg;ee^#9Z(7@i z%W9w*d7Mjqi^oGFS3a-h!=@&8yXK#Nf&KKU9+XlFH`SkVG)!lCGoBR7PRAqL1_8d% zfbe!)e{)v9{|43D8<=YG)N0amZWAl30ZDBZw%H*AJN<5Ldl^lWzWG7AX3+|pi~MGO zo;r+Qume3^qe0eUf@5_R@>f%Kqn#tr@x~2*1D6$l)%qIeT+P6C6CfD8jKP_@0jqaE zi}kNxuhzv8-%O-M#O=ZiNcNVx@@NGZ9(aVSK|(-Pzc5J|hQn+Qain)+#u9K%AnZ#J z-koRl%4=DTGw8RH-xxw3hq(SzpaQL2{&tDJL%S?Vc~qdHa0sT)G4|)=4B# zoz*nLP5;mExEf=_7oS-v{oibIgRW*{C^YKwjn&{s{*Z9~Oa3gQ>W%+n3^X*zocv(; zJ%g?6#d^_b7|&BFOu=%Bei!Ap=tMSGn;+HhLGxEeIr%@srC}diwXS+;YgMwGk-O(z zqN@Z)ievFZ&gIsEvP8NbKl^7?{pU+4|6`ADRF^D6&bS3IGSn#5S`l(x%dbEay9-Sd zQb}1aDlqR%s0gv5S;UqI`KIf4r?Hgk?ee5R_L>8BBE(yF23LjO_rv!}5V)xb6EJM&TH|pIYy9|Vyyfa`~`1=`E86YNbies8~qqy*2XmSaoyeyD|EPQh^NoDWm+Yn}} zb$R)pFk`+c|754=lZEk?-Vv#XsuZ-E-~|GWos%20gBAaS1}6m!fGLH9om2LyF5_z< zXO_pf7(UE?J6F-#FO_*P;4L%UQpjp(WKhrVcBKv`6Z_brXlNy;j3DgO8z(#eDtki= znimqYlN}?z;&Ab~?_)NHe~eSch3#fBDpOgfk1mAMVSa(9Y8{HyRqKm~fK> z{wgEB0QHY{j!(NYrR)ptzI9V)@IcgA%4U-+{eI-IcBA5A9Lc=tA87bOZW)F&bESA8 z(rE%`tG*We3(MS_;I`o=kqb=R9sT1koY&9vJbfwuX@|lNOE=2ymnyz&hz7xTUiB4s zsb)dd1*eLRrL#cY2e>V96v!t9KcW&<%(PGo#Z`~&j)CqSVd1S~XFY?*#M71c#8GBO}s#l6zGeY$NZ;X{#_A z!v~6`jRYLWL+Z@*KF6@?Q+=|gv^o8Sw-;xNspA>aL_{}_Xu2$qU7%vnf39>6L6P9Zz@6UVGV90R^ zkHh>~9r`?xRRJ90rH9@*p#~mU%fK~Kn)zpY&zm(1Z_$!r9rsvvF-}DM+L=FjU>uT} zy|l#=d|`w9u4CKlpE@(tkSft2IWw8qccM-S*HMFFXakdK1H-O@Y>0TitIM<6WYish zMx3>Mw`id2j@6A1F5OOI!D=42D}d-&my8KsoRJ>lx<29R^j``!BP}1wehk$8p7HF} zQo`6GkLGKe5M(j066dJh^hfJcmn4tn5}`{f{qABALLhQv$3OZW%|m0^!|YqXYu_@j zHu4P-?#(jA%^yRC%EOF2O0}sb(-GEgJK&<2-NYJ<0nUU zbOyxjj@{UK0qilBL=eUq0&Bf_$QJxjON>3PeX3vYG%+&7SeL_d%5Y_#5D@u42j9qx zU6Bt#9y4SDs5SqEB%~-mOt9I`LMwT&V5L29vqWcN zpJ>xV>~ol<(y3JQd%xOZDXay}gcjS#QQl+)Dn8J?Do+(P{iOz-+J&U@$TW|@A|;>$ zN&6)m8^33Qd-0)23>Isb1^6#@iN?N0X2{ceQWfCyjq$ZUW=U+kL0SBU2g%s$* zVdT`e7h!Mf23lEY6eDE@9ls*Ujuza`Jbsjtc5vyY)qTLMp+7qHAN@~leDbIqfNF|5^%_R%bA0H48-V#=(_&?`b-BfC;W8CM}< z$5Kf2_*(GvQ4|2@Y+>H%0sh|S*gq<}0;rvphrDTb@}va?GK>^X3j}&C)~y20$VEcZ z6Aw&k!>i=O56B7>cJ46LGqzY}r@k`pS{ewht~6Z=wA=okW&Ze<=p@`MPDw74@ff5qzwZhrBLQsywR53>hXCWg zB0*f{k+QThYedl|!ID7WRz!dEXs#*guP()9(V5ucD?TK;(C$|-juWBQ8L4F_qeH8S z62Aa!)otr%5RTB^_tg(li8`r1@>pkG-#$+2IbDqSy>Huy&gZ|o2u zkd8uuY$szh;~4)qri$P6dIA{LL%a|2w&RKgPcFgrwur_@5o3-rzWk<2h6irJ0^aLdXr%jqbY&w%{Wx5Yda=ddV3)ab zadZ(tvNy&f>Y!0P+*1uV+Uj=B_!dOc2^Jnz)G|gKIWk85u;|4|Eq!`=acm|Vmi~OA zQe5wA%-^}?RE$66N50YVnDeP7l=$@SnVXES$Ek!Dwmqi0))9LeS4RjC7|Vvg8HG>2 zrQ&1tq{H&)e=kEf9sH#!4z({oUaAou#jKJ;uW~+{CV&TRCzHmuJQ{vSq~wak>nIqn znG?H^nqa}a5GYE-i&)bzA^%J?jJ3@%o&~nlgRy#@sm!(3Uh~a=wJJvivmfvCf}TH8 zza`X|e=vSxq?)6N$nTErD3eYpk7YIH$~@m#M{0nZ=PjbOcdqp$ls6VNqhyo5KY4XknKV&5RfZ+sy681ONp>|k)6&wN;B3l9~ zk4u#8Fe_8ppmXW;^0O4AcgyMz@Sw#+T71`2ov@q1$CND z4!n-J&xWNN8!`-6VLg5tssO0vth=-KXYTcsFwkAH*mQ?`@K`hSPab0iG&5g{qS#yr zR*eeR;UpxlzH=??dH@8$8#wf9p1I9oqGnS8U?HFcg`39y>vrL|8cZ9DWM@tFxl4I7cfg7uE8+0!t z7ej-<88Zhs$FhZiPS`th5Sg|YLS8PHBF(}fTfUTdZDFy4Ul&V-xV||AC^NjJLKFhK z!eb{t`%t-g%14&$el3SpwF0-Z`|>OI=#mk7Rj0llIVkS|Ol3rJ2TFazB8+Lgm;ku&|sJW8D&q!I`W}Pt9Pxo&I4mo^!e0)2M$n+yIT_%Ji$f zi4QcpA-@eO8g7jAU|7ejlg#EHbDdAs{p7g|?KCkjjUFbo){rdC#B1h5A%F7+9;{84 z_K?a%o`w)J2ixu_tF`$EDl`SiYYP{OR1|?_lc~T{@H`1eyTZK^Vi5!J0*!uj(ffTtV9k} z1n;g4{EigqK~1$Nt02zVAZ%WW1>*kqPgicmCqYsVvfFa_HzNu zPrxy+&jN10$Ic`%Vi^B~PovMJOrBhLZF?RFldq|XUX8l}uxp?<5yUbo4Lnt!yVa=l zzNwDkIL>T!!au7SY?ofb4O#n@6~w!)jyIr>UHg6Do}?JUvD*^5@?J>2S{gz4?ttc4 z`}~GHR_sb=E6w$CQw*mv&Gzz22vs5{%<@de_8 zd;21LX-sB9py-gx!cYRY3Vi|Ylhdv`OG8%FZe&J34T0u5+49^Xi}ouKAzt+_qOO`)6)*ODkupK{hR#ta9ZVux<-_r)W(0KAn zZ#M!R3vOUMzAbI!({1=RZ!kNRQmd!_3h@H1(08TS0&92F45|Pk5ge^d8muxE}_%%wFQf{o|}P^`$Kz z>pPb+_@OaBJQKk0puDh#AEuUHYhZ-k=Wtwo zmw4@w9JCgE(9iwxibc=rApB7^=KbYCse@stpC1}^;;S3ROS|egF9{-x`=V}fp%SRmXtIxvN&jy@(YOUG0eRJ83`d@IgjgBS+T-cY1!7M^`OjI zOa=CK{M%m0Pi@BEJN@Sq_#S)3+}3J^C)ip_TknA~TP-hJa6Iy?)J)BoAbolc^_dLk z=7I{P#_(;QZg;=Nc2&Q-2+8q!H$GR5B~rMm_uv!4Bvv-g6#SLi<+@m;_U&)wBepX` z{?#&zKy7)Q|F5UF4vXpyx4-F@Qt57FXz3h5Iz+lbMv(3pxt5?~TO_9q#qWF(_70t@VCQDN_(-MOFf!F6gNG6< zb`xaP=zlskVZ*whnse+FDimsle!UdbEyuOerXl&8q58UXpzfnX*p)f|TP3HN4n+=! zIt^sw5(BT`E9$3u_|tJZb&dHGh8j;~rXM9;txm(kMt#(O2Au{V#mD|b$Ox0?tIYs& z1J%d;%%a|(&dm~P?q*`S&BY;PA1(CG8zd)%qEe&nT&QoTUS!UK(0h5Xsi(h09%|HJ zA=*tsl++TJnN`2@CQU+iSPQQ{#e^lp5; z&qTWbxkta?|HW#U1$iGkT!G_Bg7|4&bG?|iwbtJJ5GVAcpGxmMEV-UHc=IrYvB>Os zBl$Tou<5zMZI#a;A=R{zs{_3P#h4Iu@(zc9IadR(%AY`PUqdIQ?B86AH-B`bO0F>Z z(BKWCF|%1EXam6F-7xcskch_5_FkW%LtW@{z4)wVYw9uWc>fXRq)k-%5Wt5^e(Ve( z1#ijUHqPNZX^l3&ioDx4$Y#8nX9^fIpL1r)jXHFCJ}a>p8NzA1fcUv>I(W0SKXvZ0 z@%EhWGW=fP)ZucVr!Dr~F{_i@Kgxj6T9x|b8;gpUZ(zAdPbiXztxr>vfaot9F5d%( ze#hTej)_RXsFk4m6yzM$htTTOG9n%t3bK~N!ms`A{!VgClI^N}p0~#^8+!Tf4igm- zkRa7W;|o!% zp!d1hb9_(9Cg`xG${itjAbk?+f~8B!miZi9A?|0a29({_eReevWY^Td@B8Qw*33CE z+v_Pp^a6or%QdtRc!&NA?P*P=W)s4zvcb9ZG-nh^H|W4pWe-WZuS>XjO!;aSOwQKw zc9yP*#aQPb&8P94i$pbXfYLGHNXKcV>_ak$-Tp@oL-c!(l1fzCbsH1to(ZR*(&NSy zQ`m7a0srAB=P}8pN0mtO-_7%R5ZM6U1B|^JX5AfdOcCJ%G+>FZ(}{^4=Vubr?`B9+ zOSs?@*`JD=pLP~40CAQAw;~HoWf_B*guv*3WuJwvWB9Jj-Sot;J}l7fHX0s1GFBGQ z&+XwzAfjP%lUAng6apCD-&wC69dp* z6WZR7C>Xzz*K)DgOge1)`ah4{d65Z>%B$uoO@1Naw=yh9-r?<^y`P;~=N>iC-f9&! zh0l$1PUc?Fgk3;8ouzt@YQX03GrJVX$g~T&q~cqMpqT%5il~U>q}3xXLonj1^lBOj zTkrhHO^mTtsm<7Pw<;QisQ5Cq{)ng`pvV{^$!N~6`SXfd(7mO1y85ozz_9o74?zAI7_U0bB7$z>YowCPuTH^*Ak4?|tG2W`)F)8M(p3-%f z#9YChUrGpgN11)p+1}=I)g^VXfzbNS??>0$%XsH{p(Twj1nEFM6sT)A#HW*T9z!oN zel9*Rbr|3cv>6VEHOl2S8XoMaPM5ie#QwVX(pZcM|GB_|*kO_*e8ydz4P*m9k}T6oerAIvZ?GPP3R2K+YPxbS9MwqSj8=6Y%4}$Z*&79CIOm z16Qt+VAaeuxt; z#3^1%1Gc-FMe!`A&&1=e?JZ4q7MrLiWn!vv^shaarAY|rZJ8i-aV#RNL%Mhqk;N)j zuBsK%0<(a;WH(*6>@mZP0@%apu;u%MOqu4o zm9DssJr^sst3(~yG-0v9Gy_8#EgPK>vykGgaY@zD=FS&c_fzMWQDU@!lv=KcV~ePS zTa6m_=HOvxGW(e`@hl7`{bTfdilN*BDeaiXSMvgRNp5oed4jmkI)wI~tQo;vuKFou znB~g}XxFRsHOIAjxYisB7OH|W4Cw1WF`(yER~ka)lCW!xpk7|bv`OJ z^C>~!Sol-GOv{QWDTk6u<$HLng=?)5)FzKTX+JIg58(_oDOqCkt(jzbUIo2ibegWBj0cC9IGAKaKl*j=Q=Ct5rbj38;9U(gWYQ&ZxRIzF9 z&@^@cY0s#%pbxBW8MjQQt5)*F$ihz@SQVi%@OwWvZ1bs+-$kMJ%8?4-^{4jgrzjDI zOXltX+L(aIJ8ig5rP!Z;uK5-otS6|1%?HsM<1MYQun+*?B8|$bG=4sxHoQUpR-*A% zO{-?C8adJY2Pw>xv8m7A zsu)6SNQ?m4I}Fft>x@xc{L{fC3%3Azg2xxhke#fmoeVm*;iAcwN2WNl!HZ!*ymf=7tx2#^3ty1U#D1zdpwZ!6acUZVutf@ zHkov{GMj*nI=X*7Nl>GTznrgf<#$9)&Yiq0s;sK%G^#}TxF@~!D#gxkve6{jacL`$ z+=Ci5h>l;~-I#B=;k zo_JQmcmIR={vGFj#=wJ{{}{?3;IpHb=?G0pmkM{Mjtc1Tuv}n3TfEXGDlC%MGEr7? zwQABtcxaiNM{xsmE3;vTW8Ro5^1yxUY-D{59i!P|6R& zv0h@*A5X{t{nz_PTdLQLU8|R`_A^?3pOsgoe2VaAI*j~OM)Bzy)n`x#PLnKV1dRJA z%zGK~1%M+Rhf~EDe~A-D+z9a+YVVR9Kn_-d1k2V!Z@4BmI;W{30(>VDFk$JQbInS4gf+F&1<>zV zoL&D+Lw7yn6i)uZZ+<2)pP*ZTn`WZ521DSzdV`fkeT(YAX5S@VwBU8|2o4S9n&zFC zjoHv)tB~gNn6)f#>+_A}UtUw9zk$B2l(`u>pAS;fT~elQGNi*{i`N`qhn(abmm6UK zC9R=VFFT{+9y?u};!zaz-WJV~l(LtX9u(ZaH$D4s66=Q-mXGS9V^oaK_E zx&K=nr}TG!ve_JC)(m2do4cU#ywEo4yuv`KvVx{Pd3SuS6V_^zTa0yMBm0FUlp!iM z=v_me%|oH)cyJ5t9m;9M%Z%#nhlGM641>F8%)2l946jg}il!NBFMKI$tXT9c3KS`= zyI0hR!)CAXHXzn?y85bXbR6XyAVB#B#3MHe+|n=`1lWyDU^*)G_IU6QcOE6G|I_|I zHdP!5L4}su2-m|v8%dz&`f(2MJI9NgjOF#J|ED`Bc|G8U>sQu3S}>$lWcI4hEssK- z>DY{O|5tV(4d1;BRfhiU#*l7DuE}{3>@L80#4+G9p{eSWVDgD!10HqPz z;#&-RdD!RD=H&8mNV(mAmY=Q&%;Se05-6ZYT;<=)JLu@i|7jj1zK^W%R}(bqqO>Za z&Ih|HK6(Fpw^ah)$GA5r1wTv9oabb=o8SHk9p8(wbSBgRq^x9qig9d`X>7AN|YpyohvOIv}C^tO9V8{VPU zhiPM#R~%1L_}jw|O%dOcW)2%SIi|89n73?>HDFuZ?*3 z4r7wR)W2by1$R}zZuMa;QOP(H&BciH(0B?b4IlKx#|%<(DBN(VXCs*6iHpx0qL05|mO1xZpD81Q|hPaJR(kCk7 z@u~|m-n*Its$1$9p$xCR0U@$hJIPjZBAYp7HjGZ;@uB^$Wb{My*!$&nczix}?w+vB zc8sKI|1+4vmVi+8n4Yavh-~H!hct3nD?Q0kOEoyBp>GP$s3bNQ?c7cHqH9=7=m(Bcyt+aJm zX5$50+`k%PlQWIL?Qy^8)6ZP?Hr3c(C+4+Fjq!HuPmodn@bK+EaSqqQf#i^6_j|=D zhDiJ8y!@R3vq9C5PEDFfmZSX*U--MU)DmX_qJwn9@HH;esElUI!@<;&%{p84axc9O zr>1ZGJ;Ijt=ofjk8$v`&8GIY4m9QQ9xGB1I>XzOqiif@A4Aqyxp6I86|4?|r(4_Ah zuN_M~x?%SUmFat#ODh>Ny(sx0KqjgBdCinvczg}^5@48nkC2O zdRGwQ@P6xVws^t(&ze425@n*0eZ<&zQZ=||n-H_bo52yx!$xMIp4OSi0Pe7z&B5dy z1>U~_Iu?#ideDeQ^)94H=Aa)7W(8^V5~_V#Or}&61C>kE>WS|nBw7ZXFw+e`C)wf^ z@JnuH$09p(QzRx&3~EG*HQAVFJjDT-sOwtB+0J2mtTfjOfLkCi?yGr# zNzU7Bs3NV_Qb`G*H%3D`FDbJ!1drMwxJLO7AXB+__O(>mNXw|}OrD7m*v_KRU=+cw z`eW9tPI8V8X}qt!zzP@m!yZvLa1L4zOH)Z+)C&IMHR)YLtO06fROoNT6n*vEfu5y; zyhrqa+6keUU1DFGEPD5*q6Ok1vsoj1oB7Mv`!@w|g+j*P zE@fr0-SVxcDJ}lO{t9bF4;r2ciP*>Tj+i}O9HB%qbMHq7?8)L7{|rfquzxShV0v7J z9TXbu9ygZ92X0iiLdJw2|G|8YbGJV}sT%kT2=fhWLL2I9`(Sr+r$eCd+x~aaQLS1c z-R(o>l90ody^M;W%!`KOxt1%hDee4sb^Rx^*}JA=;(2U?Ht$qot#>b_?+=2w03@1) zB1y4o16p_(Tio~svstsA`F^%kB;tonyFX20q>bx)2c7+uUL;al%bM@d&)V4i{q-de z^K}kPyT3|~l^a+q{j7oTA?^*lA*-F^B~uBxcAxQk?Avl#kGBq1olM;A38zQ4^pj(A z>n+IdeA-4_@ef1s^UUfb7PAQ#?32NWdBJybs4D7eM8RKAjhyrea-zNW3%{18DGBUZ zIM8$N=W$E{aoYMVRZ*1wC9SA-V}zfIXjY*;+y7C|bedZGv&t9$UozGWIoz{;`@wL6 zbDC$c@~`63W6{bXi9qwd9<&(>Z++i$1~B;^u|l>jr@d!&L?9U0EN#vN%-EZx6^>DY z*a2`xeXX1?nxuwI(68V~Kd>8ng*C&%4c;(rw;u{;`po0BH!_SztMg4XcJ#k>I3;a@ z;h**|yOX;%GB>eu-hQT49g`S*}gk>ZeJ!vQQ zH?k%4uOG!i4UqV_1TpL;uY)yP|)M z=I0`pr$L2%9%p{pzT)cP78f9EhOXXu?1Nuq3+0SMsGzh_+EDBwmM}0UPd&~b(e zzr?I-)(p9DqeMBMeO5%-%F@c2joWX&U_-a^gN1z`@|0bOBF|+p%dBK1DHApK2>Z6( zx%T8=Nf$?Ow)xC@p2;&#CJ78VFqlPk*jj1$iwb`*&LML&!)P>ApzkDj9?60)il4 z(t2FvX3spP@e}W@2SQrASY+(JM&MRS#&OB&;}#q|-7%(6&pO#_&FLsj(|=A-T(Dac z%)lK^n60`C<7$`BWQ*1x!4zo8H>b(d1iwGF8I17m-|)O+m0=iaB#oSTwmFI(=1sl& zg4X`@FJ%QL=}X+-fm|CK)o9>;>hYwqaLLtkvT@CgCP(QCgM&m&dK}xFhGON#Jo=b? z20y49IOVA9%I@mM4P{Na1ern?UrY;XmyRY%-lNRNT=?&C3G$H~A5OO=tebsCh0-$7 z&81%5lGaP%#B?JfrNtKf`n<_#a}k}!`^a^a>+`E9?b@av_bG|$qMh)RcfO#9 zm$MVJgRXmBxtD+UzA)XQNIkvNzVXCdpI1w!Y#~&<&N)(jwf)ZGoaw>$rb68da}mT7 z_Q~~Te8M`GX0%&tVcZK-{=YYW#x>K8HNTB{B)AoO@abqp3s=KBaK|9oi}+|kA9*IS zFHDC?!@FRoV@S9833={Ru3t@MubFK0JR(wvSvxh}o8Xqf%Ic0_b4+sUqCh1VWK0U` z?*XiYvj4+SslXX@pa;m9I51j$sp9{`WW!0sBAqRYyYEH4&#D3w+5RPxMxAB@CK9M6 zl8~>(`7BFvo1sPJ6^|=%{#7WggsyznE@`gJY?4{^2Sa19jN=?O7~>egiCb=H)i?E? zNSXFR&xk>BkoAvlJ<=jkBP1inVL@^HpJc!lzj^(xzz&42?NaLU<1dD{W58Q>B3WG> zExydtpB_-=^j5#{BO{2Uc56@*{KJeP!}o8=cd9(Jii63nUSurYVDqGBsnI7 zHm~h1%sOw%+hS(LSnXK4JXyK1jFi*!)xt(0ViU$FYK(?X#fgxVJx@4}4-#Kn4Y%?)fFj zJIYX~|DI`DWZ|UsPN&*M zy?k48L&v6|9;K_nNB!shh9n;^cICx6X(xKMsCxJN^#v{xjm;FXm!Nfz9>USISVsEo z3;4a4guG>;en!#lboiDgPa*obN@5oirT_>Vq;%_XDlcbLerQzd;YY>HYhQWo?ypK{ zD#ZfgOC(N-;Ln%$ID9bc2*%Im@}8SJ-l zix{l_(i#}^6%I&uGZShfwkFXmPu(g0V0(|*UrEvBG4&{U%^o6W4_=GRb!z&n@ox!v z-=W8TOKTY-{NRtpHY_}EA-|OL;^xDSCy`{7fYn))u|I@^7Zs?%q84Tjww#tbNFC@n zuuhw1)$nXe7{;Ww$4&>DIBAb@PgYYeM0YxNhwrQ zdJCZ0>rZXvfL~b>RPK0o)*gI6!TgtVKVy;^MKnVef(Ob=9mizMRgjdnkfYn}cxVj# zS{sn()I8>jqeS9P)C1N!jl+lo1?`q0v_(-Qw@yk+-z<;>dp$34TZy-Vd_Fl7efxyy zcwkcjeauiek6h0rrRFYzgjIH~-^5x{`wf0^Uv;Y(_$=c%OUTmp2{gRzByi{@*0=J(szL8WO>Zv5|Ib=|!ulaqH^^tfjGc;g#CtRM^ z6KvZ|_u7ek{ry`38Pon4Qmw7LfOo`*jUj#vhI|d5CTqtJstbp9_{R@^DW8u9C1(V%CW{c(DLur)<40aJni3i`SRXf2!JlLn z?B6kL=bxQ9-QTY<0&-P*DtTt(`mL#7%XY73NEY%F*b6QQRr9j0V_w=Y6jy2lu`oVU z7fVGql+E;C7p{EJi>s-ydL-(3O%*+!LKz$gq)4Jb_|y z|4-jL{BAP^-eZojDDc9o;mT6gCk$FHr%xyb6$vRr1%O2Uh%;Y*Ph)iwI3f+{pw(K@)EHA`BiM#aE-{$aU_KX@Mjiit-pQH^+1DZW z^BH2f6J5!*ksk>O1qf|v7OW%O56hnCyXc$~x%&>05^dm7_KlCqY?fa8NN!8)9*0h8 zRxyJe8zHX|>w7^e!7gjBWxA7;KT&y}FwLk0|FO?W88J?~stbz{SD4yrn;PBQS>p?J zrXgrf27$-h2m$J%BSB58#7T#8SS9h2=bmi7CVC7mwCJH}-+ew+X`M*^WpI#xH?Hs? zjTnwic#?;0s*ku4!If$_0$d^GZ!WIfl-FkV+OVr+julYSP&CMTB+nevSW=Ctj(OhN z*G=<(WTVG2l)Qq%CIIF?sn(BKWrEg#;r|yXaYFsq?Dz63{B&n{vHh_YEEwvf32}1v z6F~o8VWkTtCn-bwX3o5UOq#-|zzP#Q;r|&{@WdW#V)aqEP+O5SC-6=js^t+@yk2(j zzhY2hPyEvx)mZ@LsgyCadlY3i2v34!!y>Rr3vXJA|r1Iw3iD7@OfuR|Q)W{R)!!7`$d6 zD|X80_HdnQDoG;QNZC{Ipm5spHslT2!?iuvHJMj~O4|KbF1YOxm$m&U98ZkZ_@r+x zBFyB14gJM`EH5FK9^)miyWqaYD?9HhD`Y_Z{)y&0=Y+y(nXlSIkyj-jTX8FJkJZu; zbn%-8u3GXaM4{zRsj8+rIFjHPD)wQE8=P)8>0Xoj>2_QdhS(R7RG+<%Jm|t!+Al#h zLY~VZ`I7UD5Ezhvm1WmFgsxa_asg#X`oKQ$Y?RMf>`j#Mdv64B(?9+sm*Fb4#MHUM z9ZVwLr)$G4%4y}bE<~CzP7THgRwMm3wjxc-@mH_xkdS?CHh^>~?SSPia>YOJ`4yZ0 zV?^aVrauG(7U~Wen8S8Cm*#RSOI*ZK`8OXO2iiC*JD1ePq=(%MGBU-rt(SFJ2Ik6jTHPKTrm`ysr~gophY1?{qr=;$L7$zZ zF5;x;yv~qia#|^vdD@=WW+|^MjXCuc_X6t4_NyG5ZV&jr8YSyP<1g188#Q4OD8#Po zssUpIKIBlCX+yf(CBD*kRr-_gHd6!$@j5tg!BQ zg%+{p8cce17V{#XJ%Es{W#f?l9H+sx)$(cppPcK`{w!?x{k$v=m)gp`9h=m&+F_0* zpIh<{Fw8Uv!Qr9=^R5tRhKqLvGz-&-^}9uH(JWWA3oti6l@{-;Q|k6oz(u9F+LcZV z3BEE1uCmC!Lk-x=TZi#AoiMk3F^h+u=>^>~gCJu!3#{D7GO_tH( zmd^@i3n1yKkac;EdZN4_cA0=QCz)Bbv3A@S6%`xp5iVn1 zZ*uW{T1!1Isc4GRLmhwRyDOY5O)`Io0G(wO-V5G>{@TMO)@!BbAKkDfnj@dJg>k7MC%BE-)v`~`bV=5Zj>;fa7xFRNgf+az#V~tT zIN*0c*yHqQ@3qHkwgXQ1?3v2H<(U6l$=y#^97jpQhEFLU@A(h%zeqd5R?av4nF=bc z&!|#8ghBgh7wcY*z~+ubPv4 zlD^Cn49(%GG6KKj=m$O)waaq$_2=}p9rcU13S}$Z_a!=Zs#X_|_$m8z z41JxQEdQQ|X?lBM8QB=}E9Yc@SZqE!AvFGBeHcIq0o^l&E5oj35&IjWWSCHA5oGAd z-?In?(I)h@(%?4J#KYjm<-lKRs%YZ}D1g*yvR1!AV-a@v|fXo10B z)Mbepj?W`5lLLO^B?A%A20!LLA?0dU_)?R1uFpcJ$y97;x=)P)a|UMZ&IB{?k(<_e z5=orePTSm*(q5@0dKW1lgZnA>3csNEa+o_FVU~$liP4~-Iv~t@tt%E4oa*^+yHzAo zsh?;F_{f|1BG*UWfZCzJCw+iWSMPg zn{jq5Iby)3=Prmyad4wvYFz3Ez2oTb+@i^wY>%_K5Y?+HpCOXDN2q}?@el|Cz)z?5 z7^@_NQF~}D`7mUoc}Vg?j95@Dqn+T}hAiy!uM(_p`?Hgms%2xUI!fm(s#!=PMoNQx zfqck+jKAUzCL=mjdz#WgYilb-w-4$b>pLOpQ((%E%Z~?4W4WN$a8d)8BYVnC(shn~ zbajfzjG#^X+pCkO)CJuTNKg7>T04(?DQy*;l+-m>Uv8MZu;Jln6dLd3-F+d6N*!{2 z_}n&kW0CabG`V>p^a3P@r-_wor$6c1Z!&Z6vK!eG|8@|WFY=Fzny~5j zpQJUl@C^ZW^+w&Lwg$K4HgEk23x$p|qKO+n1u$?lpFDU|W6SKd95x0L{@5aW6!sgr z4~>UyO^eve9OR9x1n6jMKXyDlw?93SH4Z-I1f!pqr8{iFNFf3o0!19N& zu`^?s+}Z5l0N4n1g-cQ)6hJLB33wP#oJ!;=|_3kJ)wD`8oyC3 zs$Z;&+GmNFntI(9NiZ}{3y!lO8zq2`t60u>Tr$6cKTBi#|58ic7|N( z2%Dq1EM5>dr8=AX8#5TAfs8G{X(doWba+CYDpcT;7&ck)UcHiROoFp4SQGY!lEYPo zzX^q(zRWi0B0%c!&eu^znvO|x+05nYoAZb}#W_iWUs3=Ts4*q9X)O{3z*b!p-Fb30 zJBiI$GavS4PZwX%_tHi*Qiq6orLncrNX}CF@0E;Vu zzw1AH5bi;+!p7>=?0<9gPal$&r|6Vv+Yh{oO(<3)RQKB4pMo)*Icg$!)gi$%RlfFi z{zZG_^F+fDQxcEKvAQkAOmipJZ>RQef1dcqGpddm!9aH5TvDCy1BqN(_#fD1)vXE7sQ zmiSbuj$TrUOsq3QgN_Q`eLX~1<=79@OAE&n4v%$=;8OljY8iBgJ@0m>%|12Wjxpip zJZq6mPqdyxasZw#F7qHwbB~~=EF7CAgpt^%-fg!+IePTon&ftx*h-!mw~MpPJ3RN{ zW)_m!AIy@G+eaJz6{G;Mn&!ook!Sw^363LGP;X+^RP@@H&J`VW54tTZIk8@kdpGarBIl6A2Xf8z=|}a{y1=^ zs3$!*`MS9hD))$Fb?{^9@s3B${w zb;f-5*3P?xII9ylgzUnJRLY3C#Y%`rL4!I9i@voqR(82HBZZ3lDh{6RMxJ!Ba0__F zflg{Hazrc{nU;1??~!l?vEj_!EVGaRY~4PR=Bm_~eSQd$%upKn|$1^@M?1dbWCFi)?ug+F+;YMzFw7e<> zmLtkhkP2e0fS*hKSCX|oYq)FFM0^F^QZNpw6%jV;{JN=6yCxbR8>G}}<-9%HuYCoV6o<%GZqjf?zTZnf?iB(%Ie} znW@)c@!?NaJHE=Qv&02QaM7vyewoFTy^H1DuwdxNm>uCNFJVhO0lq0QXKmjd;R~x4 zUAZj(-dZZk-qKr|r4NB(GWm?_s96=7eh38|8jQ!0qrUXg-!~TAw9nxFxo%6G{~Z`2 zBS5+r>=-X0ihdpFSP$ss*^A8cF9+md(GZn4B(G30`8-*dL{PHztozD-;`3?x-Kif) zL1yD)^U#1yP*60;G9e9Q4fkgYVC?*_7-2&FrTS`G1Wu$biVld5nfP~2OP=Q$f~D?* z;*~cj!VoQ1SMZL_d?nniwX~S6H3Jd>qsQ$S&=FkD)%hg6SlvrTgdH#+V`bc2H;#;s z$ zR^*$mv+womt*iYar@B$x6gYo9yiV?k^+4-^??C%;4gKae@kxcRGO-^5%5`oulIvRV z-ljATxO|+>eOFB<_jKmUEgCqisgl;&<_yP?hoQ62tDqW5^Ic4{?Ty{Ak8G%SG0M_7 zaKwsMxH?=advM|yh}Sx0UDS@{&SUq&%Hc+_pbwfqK+|i!)2B#8hUG9`qe`JvcArajvp&o^e~;;Mg%VC;{wk=f zpvYX3wV)j}qhcR&zZLH$w1njqhZEMunHZGl@_~do2>>GXh~}UQJ9i>a&aw1L>c4 zHU1)`fY&Xku{o%DLH~E93v%o@F-fJ~*^9sZ`jZ`>Z)S?MYhbQiYt7>=@XRr5dIeS$OQkcNR)+Ty?UAG*a-LR=+a>b<{;M<-$0?5 zm=l05M9jv>W~)jpEBM{Y&WgiuW3p2x5GJk0e6GBdk7dmnJh#d*j*PvXwe4UU|Hk5A z{@)T9bY;j`o&CTbrVlc*Lk8yXJZd;w!9_9PX$iqiomKqpRQCB%3pgsh_?pwio?@ga zQP?8a*R(7{8y(n+r7;0yR5LQtp+9{&fA2Cx=+^gjl7}Ae4s_XFY8%1OO<+}uFi=Gm z;ltf}8NZ}p&cTRM(J1WQK>PRm0PMP^iQ}UWIO{Fw!M-$gE<|!+ZVfnTPg-a~2s~z( zEa^{h6}mt5^XclfZ9A)O1h1a2Y=Ki?0>)ySiG~1@u~Vzy)v*m)$PBgUh|C>xm5Ks- z6Q&>W@St|%jW_TGw625i=L{ni+8cU278<p*6a^VhU(N%AovqRhq*S*6M>gFv78VxPOw5I;9Zge+@hc%&rvFD~4N%;Gprdi{1j8R zk@|GravWVs1B(tkgCjAqU-|NRs6aT{?`bUX-%}~lpVnQLnC?zDvHMuvD>x6a2XkeF zrF}&0r8?Gwe{s9L6}Y(XUnxi3>Ei$mFi_(dE#H#TtyY1|U9m#2Nlozrw|H+{F)Sq@ z-!LCxZai@Tw879#)Bw(B-8K0xtu$DwFA6DJl_JQQL~#SPUf||Ol5-)lPATIEEGPJY zH|C`94izr>_byyc1(4_2W>zhfY;KmFXyZ7yK!3EVuKRH}?1$X27Z+;|kU4w^4_+!B z>+fw0k8T;t^>rF7m6<1dWm0=w(h|))Hgz*h#xMXdFA4IpFe4t#-4*l^MLyi92WnD1Zd3$s^*MKSDVTOZ_wvUkt6>C@M1-9eJ>f z^?(@}hMKC7uc-A#q*J)U2|LHR>|$H~h6(ZDjK%vdlC@L{{dy57f?Fz?YaKO79*-fF zHC6G2P(xfyPE5}y%)JT=mO%UxI2d^$E7|$w*$=v$m#vBDL(zFe=;s`21EfXrBRKiv z?9b%;y8=owG5dhi6ZupX?;}5BHA}sl#(qo6U(BTu`Yi&jsU;s0AFjnD4bU;{e0A0J z>S{|_yzQJiRKGM-geGik9Wx9Ey=*!i*WClNHRhuO`gju_Vh2mM56RgW9Db9FfjT22 z8(9JRM&(R~mZF>spZR&LDvcLS2H(_@S=#=n!>nLgvFjCKtz@iyVTnV#EgM9b2L^TC zU3M)@^OS2_nz&ie(6+|B+*g0*D?3HL6?B?mc%QLI1yyWflW&c&d+dojs6IjG4!b7X zX?jn-Ow!uFawy@+X8av+ey0p(2fx^?shnRr!+FSxT@N9Q{q76Gy1)Z^9s6Q*)ylQL zMSRE-b5gv1NK6{V23|}1G8muGEf0n}euXTC{n?R<9BD$caDDmJHwFTycm3;jLCC_| z{dcwPVjh3P?x6r-*C}IF2@JG?=t7_Gc^cg?#Wc5t-K(fjx@(Tze>$^gWAj}usXL9v zgii(kzzfpKiFWySmCNFd1zmJo=2T5HY0ti+SDD?p4`IyumSBr_rjMGFjHdclOR@5e HRrvo0@@F;a literal 0 HcmV?d00001 diff --git a/windows/deployment/update/wufb-compliancedeadlines.md b/windows/deployment/update/wufb-compliancedeadlines.md index bb088093c1..6524be0563 100644 --- a/windows/deployment/update/wufb-compliancedeadlines.md +++ b/windows/deployment/update/wufb-compliancedeadlines.md @@ -1,100 +1,173 @@ ---- -title: Enforce compliance deadlines with policies in Windows Update for Business (Windows 10) -description: Learn how to enforce compliance deadlines using Windows Update for Business. -ms.prod: w10 -ms.mktglfcycl: manage -ms.sitesec: library -audience: itpro author: greg-lindsay -ms.localizationpriority: medium -ms.audience: itpro author: greg-lindsay -ms.date: 06/20/2018 -ms.reviewer: -manager: laurawi -ms.topic: article ---- -# Enforcing compliance deadlines for updates - ->Applies to: Windows 10 - -Deploying feature or quality updates for many organizations is only part of the equation for managing their device ecosystem. The ability to enforce patch compliance is the next important part. Windows Update for Business provides controls to manage deadlines for when devices should migrate to newer revisions. We offer two compliance flows that you can choose from: - -- [Deadline only](#deadline-only) -- [Deadline with user engagement](#deadline-with-user-engagement) - -## Deadline Only - -This flow only enforces the deadline where the device will attempt to silently restart outside of active hours before the deadline is reached. Once the deadline is reached the user is prompted with either a confirmation button or a restart now option. - -### End User Experience - -Once the device is in the pending restart state, it will attempt to restart the device during non-active hours. This is known as the auto-restart period, and by default it does not require user interaction to reboot the device. - ->[!NOTE] ->Deadlines are enforced from pending restart state (for example, when the device has completed the installation and download from Windows Update). - -### Policy overview - -|Policy|Description | -|-|-| -|Specify deadline before auto-restart for update installation|Governs the update experience once the device has entered pending reboot state. It specifies a deadline, in days, to enforce compliance (such as imminent install).| -|Configure Auto-restart warning notification schedule for updates|Configures the reminder notification and the warning notification for a scheduled install. The user can dismiss a reminder, but not the warning.| - -### Suggested Configuration - -|Policy|Location|3 Day Compliance|5 Day Compliance|7 Day Compliance | -|-|-|-|-|-| -|Specify deadline before auto-restart for update installation| GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadline before auto-restart for update installation |State: Enabled
**Specify the number of days before pending restart will automatically be executed outside of active hours**: 2|State: Enabled
**Specify the number of days before pending restart will automatically be executed outside of active hours**: 3|State: Enabled
**Specify the number of days before pending restart will automatically be executed outside of active hours**: 4 - -### Controlling notification experience for deadline - -|Policy| Location|Suggested Configuration | -|-|-|-| -|Configure Auto-restart warning notification schedule for updates|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure auto-restart warning notifications schedule for updates |State: Enabled
**Reminder** (hours): 2
**Warning** (minutes): 60 | - -### Notification experience for deadline - -Notification users get for a quality update deadline: -![The notification users get for an impending quality update deadline](images/wufb-quality-notification.png) - -Notification users get for a feature update deadline: -![The notification users get for an impending feature update deadline](images/wufb-feature-notification.png) - -## Deadline with user engagement - -This flow provides the end user with prompts to select a time to restart the device before the deadline is reached. If the device is unable to restart at the time specified by the user or the time selected is outside the deadline, the device will restart the next time it is active. - -### End user experience - -Before the deadline the device will be in two states: auto-restart period and engaged-restart period. During the auto-restart period the device will silently try to restart outside of active hours. If the device can't find an idle moment to restart, then the device will go into engaged-restart. The end user, at this point, can select a time that they would like the device to try to restart. Both phases happen before the deadline; once that deadline has passed then the device will restart at the next available time. - -### Policy overview - -|Policy| Description | -|-|-| -|Specify engaged restart transition and notification schedule for updates|Governs how the user will be impacted by the pending reboot. Transition days, first starts out in Auto-Restart where the device will find an idle moment to reboot the device. After 2 days engaged restart will commence and the user will be able to choose a time| -|Configure Auto-restart required notification for updates|Governs the notifications during the Auto-Restart period. During Active hours, the user will be notified that the device is trying to reboot. They will have the option to confirm or dismiss the notification| - -### Suggested configuration - -|Policy| Location| 3 Day Compliance| 5 Day Compliance| 7 Day Compliance | -|-|-|-|-|-| -|Specify engaged restart transition and notification schedule for updates|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify Engaged restart transition and notification schedule for updates|State: Enabled
**Transition** (Days): 2
**Snooze** (Days): 2
**Deadline** (Days): 3|State: Enabled
**Transition** (Days): 2
**Snooze** (Days): 2
**Deadline** (Days): 4|State: Enabled
**Transition** (Days): 2
**Snooze** (Days): 2
**Deadline** (Days): 5| - -### Controlling notification experience for engaged deadline - -|Policy| Location |Suggested Configuration -|-|-|-| -|Configure Auto-restart required notification for updates |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Auto-restart required notification for updates|State: Enabled
**Method**: 2- User| - -### Notification experience for engaged deadlines -Notification users get for quality update engaged deadline: -![The notification users get for an impending engaged quality update deadline](images/wufb-quality-engaged-notification.png) - -Notification users get for a quality update deadline: -![The notification users get for an impending quality update deadline](images/wufb-quality-notification.png) - -Notification users get for a feature update engaged deadline: -![The notification users get for an impending feature update engaged deadline](images/wufb-feature-update-engaged-notification.png) - -Notification users get for a feature update deadline: -![The notification users get for an impending feature update deadline](images/wufb-feature-update-deadline-notification.png) +--- +title: Enforce compliance deadlines with policies in Windows Update for Business (Windows 10) +description: Learn how to enforce compliance deadlines using Windows Update for Business. +ms.prod: w10 +ms.mktglfcycl: manage +ms.sitesec: library +author: jaimeo +ms.localizationpriority: medium +ms.author: jaimeo +ms.reviewer: +manager: laurawi +ms.topic: article +--- +# Enforcing compliance deadlines for updates + +>Applies to: Windows 10 + +Deploying feature or quality updates for many organizations is only part of the equation for managing their device ecosystem. The ability to enforce update compliance is the next important part. Windows Update for Business provides controls to manage deadlines for when devices should migrate to newer versions. + +The compliance options have changed with the release of Windows 10, version 1903: + +- [Starting with Windows 10, version 1903](#starting-with-windows-10-version-1903) +- [Prior to Windows 10, version 1903](#prior-to-windows-10-version-1903) + + +## Starting with Windows 10, version 1903 + +With a current version of Windows 10, it's best to use the new policy introduced in Windows 10, version 1903: **Specify deadlines for automatic updates and restarts**. In MDM, this policy is available as four separate settings: + +- Update/ConfigureDeadlineForFeatureUpdates +- Update/ConfigureDeadlineForQualityUpdates +- Update/ConfigureDeadlineGracePeriod +- Update/ConfigureDeadlineNoAutoReboot + +This policy starts the countdown for the update installation deadline from when the update is published, instead of starting with the "restart pending" state as the older policies did. + +The policy also includes a configurable grace period to allow, for example, users who have been away to have extra time before being forced to restart their devices. + +Further, the policy includes the option to opt out of automatic restarts until the deadline is reached by presenting the "engaged restart experience" until the deadline has actually expired. At this point the device will automatically schedule a restart regardless of active hours. + + + +### Policy setting overview + +|Policy|Description | +|-|-| +| (starting in Windows 10, version 1903) Specify deadlines for automatic updates and restarts | Similar to the older "Specify deadline before auto-restart for update installation," but starts the deadline countdown from when the update was published. Also introduces a configurable grace period and the option to opt out of automatic restarts until the deadline is reached. | + + + +### Suggested configurations + +|Policy|Location|Quality update deadline in days|Feature update deadline in days|Grace period in days| +|-|-|-|-|-| +|(starting in Windows 10, version 1903) Specify deadlines for automatic updates and restarts | GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadlines for automatic updates and restarts | 7 | 7 | 2 | + +When **Specify deadlines for automatic updates and restarts** is set (starting in Windows 10, version 1903): + +**While restart is pending, before the deadline occurs:** +- For the first few days, the user receives a toast notification +- After this period, the user receives this dialog: + +![The notification users get for an impending restart prior to deadline](images/wufb-update-deadline-warning.png) +- If the user scheduled a restart, or if an auto restart is scheduled, 15 minutes before the scheduled time the user is receives this notification that the restart is about to occur: + +![The notification users get for an impending restart 15 minutes prior to restart](images/wufb-restart-imminent-warning.png) + +**If the restart is still pending after the deadline passes:** +- Within 12 hours before the deadline passes, the user receives this notification that the deadline is approaching: + +![The notification users get for an approaching restart deadline](images/wufb-pastdeadline-restart-warning.png) +- Once the deadline has passed, the user is forced to restart to keep their devices in compliance and receives this notification: + +![The notification users get for an imminent restart after the deadline](images/wufb-pastdeadline-restartnow.png) + + + + +## Prior to Windows 10, version 1903 + + +Two compliance flows are available: + +- [Deadline only](#deadline-only) +- [Deadline with user engagement](#deadline-with-user-engagement) + +### Deadline only + +This flow only enforces the deadline where the device will attempt to silently restart outside of active hours before the deadline is reached. Once the deadline is reached the user is prompted with either a confirmation button or a restart now option. + +#### End-user experience + +Once the device is in the pending restart state, it will attempt to restart the device during non-active hours. This is known as the auto-restart period, and by default it does not require user interaction to restart the device. + +>[!NOTE] +>Deadlines are enforced from pending restart state (for example, when the device has completed the installation and download from Windows Update). + +#### Policy overview + +|Policy|Description | +|-|-| +|Specify deadline before auto-restart for update installation|Governs the update experience once the device has entered pending restart state. It specifies a deadline, in days, to enforce compliance (such as imminent installation).| +|Configure Auto-restart warning notification schedule for updates|Configures the reminder notification and the warning notification for a scheduled installation. The user can dismiss a reminder, but not the warning.| + + + + +#### Suggested configuration {OK} + +|Policy|Location|3-day compliance|5-day compliance|7-day compliance| +|-|-|-|-|-| +|Specify deadline before auto-restart for update installation| GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify deadline before auto-restart for update installation |State: Enabled
**Specify the number of days before pending restart will automatically be executed outside of active hours:** 2| State: Enabled
**Specify the number of days before pending restart will automatically be executed outside of active hours:** 3 | State: Enabled
**Specify the number of days before pending restart will automatically be executed outside of active hours:** 4| + +#### Controlling notification experience for deadline {OK} + +|Policy| Location|Suggested Configuration | +|-|-|-| +|Configure Auto-restart warning notification schedule for updates|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure auto-restart warning notifications schedule for updates |State: Enabled
**Reminder** (hours): 2
**Warning** (minutes): 60 | + +#### Notification experience for deadline + +Notification users get for a quality update deadline: +![The notification users get for an impending quality update deadline](images/wufb-quality-notification.png) + +Notification users get for a feature update deadline: +![The notification users get for an impending feature update deadline](images/wufb-feature-notification.png) + +### Deadline with user engagement + +This flow provides the end user with prompts to select a time to restart the device before the deadline is reached. If the device is unable to restart at the time specified by the user or the time selected is outside the deadline, the device will restart the next time it is active. + +#### End-user experience + +Before the deadline the device will be in two states: auto-restart period and engaged-restart period. During the auto-restart period the device will silently try to restart outside of active hours. If the device can't find an idle moment to restart, then the device will go into engaged-restart. The end user, at this point, can select a time that they would like the device to try to restart. Both phases happen before the deadline; once that deadline has passed then the device will restart at the next available time. + +#### Policy overview + +|Policy| Description | +|-|-| +|Specify engaged restart transition and notification schedule for updates|Governs how the user will be impacted by the pending restart. Transition days, first starts out in Auto-Restart where the device will find an idle moment to restart the device. After 2 days engaged restart will commence and the user will be able to choose a time| +|Configure Auto-restart required notification for updates|Governs the notifications during the Auto-Restart period. During Active hours, the user will be notified that the device is trying to restart. They will have the option to confirm or dismiss the notification| + +#### Suggested configuration + +|Policy| Location| 3-day compliance| 5-day compliance| 7-day compliance | +|-|-|-|-|-| +|Specify engaged restart transition and notification schedule for updates|GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Specify Engaged restart transition and notification schedule for updates|State: Enabled
**Transition** (Days): 2
**Snooze** (Days): 2
**Deadline** (Days): 3|State: Enabled
**Transition** (Days): 2
**Snooze** (Days): 2
**Deadline** (Days): 4|State: Enabled
**Transition** (Days): 2
**Snooze** (Days): 2
**Deadline** (Days): 5| + +#### Controlling notification experience for engaged deadline + +|Policy| Location |Suggested Configuration +|-|-|-| +|Configure Auto-restart required notification for updates |GPO: Computer Configuration > Administrative Templates > Windows Components > Windows Update > Configure Auto-restart required notification for updates|State: Enabled
**Method**: 2- User| + +#### Notification experience for engaged deadlines + +Notification users get for quality update engaged deadline: + +![The notification users get for an impending engaged quality update deadline](images/wufb-quality-engaged-notification.png) + +Notification users get for a quality update deadline: + +![The notification users get for an impending quality update deadline](images/wufb-quality-notification.png) + +Notification users get for a feature update engaged deadline: + +![The notification users get for an impending feature update engaged deadline](images/wufb-feature-update-engaged-notification.png) + +Notification users get for a feature update deadline: + +![The notification users get for an impending feature update deadline](images/wufb-feature-update-deadline-notification.png) + + diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index 1d23df7da7..9b7700d02e 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -65,6 +65,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.

+ @@ -77,7 +78,6 @@ sections: - @@ -130,10 +130,10 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
August 20, 2019
10:50 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Investigating
August 17, 2019
01:49 PM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive an error, \"Updates Failed, There were problems installing some updates, but we'll try again later\" and \"Error 0x80073701.\"

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 16, 2019
04:28 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 13, 2019
06:59 PM PT
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU
Some apps or games that needs to perform graphics intensive operations may close or fail to open on Surface Book 2 devices with Nvidia dGPU.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
July 16, 2019
09:04 AM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
July 12, 2019
04:42 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Mitigated
July 10, 2019
07:09 PM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
June 10, 2019
06:06 PM PT
Unable to discover or connect to Bluetooth devices
Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:48 PM PT
Intel Audio displays an intcdaud.sys notification
Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:47 PM PT
Cannot launch Camera app
Microsoft and Intel have identified an issue affecting Intel RealSense SR300 or Intel RealSense S200 camera apps.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:47 PM PT
+ - From 320d5ce5223585edebe669ab0bba0dd596a8d38a Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Fri, 23 Aug 2019 17:39:05 -0700 Subject: [PATCH 3/9] CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20190823163336 (#980) (#981) --- .../resolved-issues-windows-10-1507.yml | 2 -- .../status-windows-10-1607-and-windows-server-2016.yml | 2 -- windows/release-information/status-windows-10-1703.yml | 6 ++++++ .../status-windows-10-1809-and-windows-server-2019.yml | 2 +- windows/release-information/status-windows-10-1903.yml | 4 ++-- ...status-windows-7-and-windows-server-2008-r2-sp1.yml | 4 ++-- windows/release-information/windows-message-center.yml | 10 ++++++---- 7 files changed, 17 insertions(+), 13 deletions(-) diff --git a/windows/release-information/resolved-issues-windows-10-1507.yml b/windows/release-information/resolved-issues-windows-10-1507.yml index efd586d8b9..6eb7bd7645 100644 --- a/windows/release-information/resolved-issues-windows-10-1507.yml +++ b/windows/release-information/resolved-issues-windows-10-1507.yml @@ -39,7 +39,6 @@ sections: - @@ -97,7 +96,6 @@ sections:
DetailsOriginating updateStatusHistory
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution and estimates a solution will be available in late August.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
Last updated:
August 20, 2019
10:50 AM PT

Opened:
May 24, 2019
04:20 PM PT
Intermittent loss of Wi-Fi connectivity
Some older computers may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM).

To safeguard your upgrade experience, we have applied a hold on devices with this Qualcomm driver from being offered Windows 10, version 1903, until the updated driver is installed.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: Before updating to Windows 10, version 1903, you will need to download and install an updated Wi-Fi driver from your device manufacturer (OEM).
 
Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated External
Last updated:
August 01, 2019
08:44 PM PT

Opened:
May 21, 2019
07:13 AM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

Microsoft has identified some scenarios in which these features may have issues or stop working, for example:
  • Connecting to (or disconnecting from) an external monitor, dock, or projector
  • Rotating the screen
  • Updating display drivers or making other display mode changes
  • Closing full screen applications
  • Applying custom color profiles
  • Running applications that rely on custom gamma ramps
Affected platforms:
  • Client: Windows 10, version 1903
Workaround: If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer. For other color setting issues, restart your computer to correct the issue.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
August 01, 2019
06:27 PM PT

Opened:
May 21, 2019
07:28 AM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Windows 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change.

To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4505903 and the safeguard hold has been removed. Please ensure you have applied the resolving update before attempting to update to the Windows 10 May 2019 Update (version 1903). Please note, it can take up to 48 hours for the safeguard to be removed.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4505903		Resolved:
July 26, 2019
02:00 PM PT

Opened:
May 21, 2019
07:56 AM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
Last updated:
June 10, 2019
06:06 PM PT

Opened:
May 24, 2019
04:20 PM PT
Unable to discover or connect to Bluetooth devices
Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Realtek and Qualcomm. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Realtek or Qualcomm Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Workaround: Check with your device manufacturer (OEM) to see if an updated driver is available and install it.

  • For Qualcomm drivers, you will need to install a driver version greater than 10.0.1.11.
  • For Realtek drivers, you will need to install a driver version greater than 1.5.1011.0.
Note Until an updated driver has been installed, we recommend you do not attempt to manually update using the Update now button or the Media Creation Tool. 

Next steps: Microsoft is working with Realtek and Qualcomm to release new drivers for all affected system via Windows Update.  


Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 21, 2019
04:48 PM PT

Opened:
May 21, 2019
07:29 AM PT
Intel Audio displays an intcdaud.sys notification
Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in higher than normal battery drain. If you see an intcdaud.sys notification or “What needs your attention” notification when trying to update to Windows 10, version 1903, you have an affected Intel Audio Display device driver installed on your machine (intcdaud.sys, versions 10.25.0.3 through 10.25.0.8).
  
To safeguard your update experience, we have applied a compatibility hold on devices with drivers from being offered Windows 10, version 1903 until updated device drivers have been installed.

Affected platforms:
  • Client: Windows 10, version 1903; Windows 10, version 1809
Workaround:
On the “What needs your attention\" notification, click the Back button to remain on your current version of Windows 10. (Do not click Confirm as this will proceed with the update and you may experience compatibility issues.) Affected devices will automatically revert to the previous working configuration.

For more information, see Intel's customer support guidance and the Microsoft knowledge base article KB4465877.

Note We recommend you do not attempt to update your devices until newer device drivers are installed.

Next steps: You can opt to wait for newer drivers to be installed automatically through Windows Update or check with the computer manufacturer for the latest device driver software availability and installation procedures.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 21, 2019
04:47 PM PT

Opened:
May 21, 2019
07:22 AM PT
Cannot launch Camera app
Microsoft and Intel have identified an issue affecting Intel RealSense SR300 and Intel RealSense S200 cameras when using the Camera app. After updating to the Windows 10 May 2019 Update and launching the Camera app, you may get an error message stating:

\"Close other apps, error code: 0XA00F4243.”


To safeguard your update experience, we have applied a protective hold on machines with Intel RealSense SR300 or Intel RealSense S200 cameras installed from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: To temporarily resolve this issue, perform one of the following:

  • Unplug your camera and plug it back in.

or

  • Disable and re-enable the driver in Device Manager. In the Search box, type \"Device Manager\" and press Enter. In the Device Manager dialog box, expand Cameras, then right-click on any RealSense driver listed and select Disable device. Right click on the driver again and select Enable device.

or

  • Restart the RealSense service. In the Search box, type \"Task Manager\" and hit Enter. In the Task Manager dialog box, click on the Services tab, right-click on RealSense, and select Restart. 
Note This workaround will only resolve the issue until your next system restart.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
May 21, 2019
04:47 PM PT

Opened:
May 21, 2019
07:20 AM PT
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly.

See details >		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4493475		April 09, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >		OS Build 10240.18094

January 08, 2019
KB4480962		Resolved
KB4493475		April 09, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.

See details >		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4489872		March 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

See details >		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4491101		February 21, 2019
02:00 PM PT
First character of Japanese era name not recognized
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4489872		March 12, 2019
10:00 AM PT
Custom URI schemes may not start corresponding application
Custom URI schemes for application protocol handlers may not start the corresponding application for local intranet and trusted sites in Internet Explorer.

See details >		OS Build 10240.18158

March 12, 2019
KB4489872		Resolved
KB4493475		April 09, 2019
10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

See details >		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4489872		March 12, 2019
10:00 AM PT
-
DetailsOriginating updateStatusHistory
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. 
 
For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. 
 
Affected platforms:  
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: 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 is resolved in KB4493475. 

Back to top		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4493475		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487018, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue is resolved in KB4489872.

Back to top		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4489872		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
After installing KB4487018, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4491101.

Back to top		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4491101		Resolved:
February 21, 2019
02:00 PM PT

Opened:
February 12, 2019
10:00 AM PT
First character of Japanese era name not recognized
After installing KB4487018, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: 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 is resolved in KB4489872.

Back to top		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4489872		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4489872.

Back to top		OS Build 10240.18132

February 12, 2019
KB4487018		Resolved
KB4489872		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 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 cca3c91d12..fb76299a24 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 @@ -66,7 +66,6 @@ sections:
Internet Explorer 11 and apps using the WebBrowser control may fail to render
JavaScript may fail to render as expected in Internet Explorer 11 and in apps using JavaScript or the WebBrowser control.

See details >OS Build 14393.3085

July 09, 2019
KB4507460Resolved
KB4512517August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >OS Build 14393.3025

June 11, 2019
KB4503267Resolved External
August 09, 2019
07:03 PM PT
Apps and scripts using the NetQueryDisplayInformation API may fail with error
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data.

See details >OS Build 14393.3053

June 18, 2019
KB4503294Investigating
August 01, 2019
05:00 PM PT -
SCVMM cannot enumerate and manage logical switches deployed on the host
For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host.

See details >OS Build 14393.2639

November 27, 2018
KB4467684Resolved
KB4507459July 16, 2019
10:00 AM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

See details >OS Build 14393.2724

January 08, 2019
KB4480961Mitigated
April 25, 2019
02:00 PM 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
KB4467691Mitigated
February 19, 2019
10:00 AM PT
Cluster service may fail if the minimum password length is set to greater than 14
The cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters.

See details >OS Build 14393.2639

November 27, 2018
KB4467684Mitigated
April 25, 2019
02:00 PM PT @@ -117,7 +116,6 @@ sections: - type: markdown text: " -
DetailsOriginating updateStatusHistory
SCVMM cannot enumerate and manage logical switches deployed on the host
For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host after installing KB4467684.

Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts.

Affected platforms:
  • Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
Resolution: This issue was resolved in KB4507459.

Back to top		OS Build 14393.2639

November 27, 2018
KB4467684		Resolved
KB4507459		Resolved:
July 16, 2019
10:00 AM PT

Opened:
November 27, 2018
10:00 AM PT
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM
After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM.

Affected platforms:
  • Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
Workaround: Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart.

If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled.

Next steps: Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device.

Back to top		OS Build 14393.2608

November 13, 2018
KB4467691		Mitigated
Last updated:
February 19, 2019
10:00 AM PT

Opened:
November 13, 2018
10:00 AM PT
Cluster service may fail if the minimum password length is set to greater than 14
After installing KB4467684, the cluster service may fail to start with the error \"2245 (NERR_PasswordTooShort)\" if the Group Policy \"Minimum Password Length\" is configured with greater than 14 characters.

Affected platforms:
  • Client: Windows 10, version 1607; Windows 10 Enterprise LTSC 2016
  • Server: Windows Server 2016
Workaround: Set the domain default \"Minimum Password Length\" policy to less than or equal to 14 characters.

Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 14393.2639

November 27, 2018
KB4467684		Mitigated
Last updated:
April 25, 2019
02:00 PM PT

Opened:
November 27, 2018
10:00 AM PT
diff --git a/windows/release-information/status-windows-10-1703.yml b/windows/release-information/status-windows-10-1703.yml index 0e11306afb..dbe7b4e91e 100644 --- a/windows/release-information/status-windows-10-1703.yml +++ b/windows/release-information/status-windows-10-1703.yml @@ -20,6 +20,12 @@ sections: text: " Find information on known issues for Windows 10, version 1703. Looking for a specific issue? Press CTRL + F (or Command + F if you are using a Mac) and enter your search term(s). + +
Current status as of August 23, 2019:
+
The Enterprise and Education editions of Windows 10, version 1703 (the Windows 10 Creators Update) will reach end of life on October 9, 2019. The Home, Pro, Pro for Workstations, and IoT Core editions reached end of service on October 8, 2018.

There is no extended support available for any edition of Windows 10, version 1703. Therefore, it will no longer be supported after October 9, 2019 and will not receive monthly security and quality updates containing protections from the latest security threats.

To continue receiving security and quality updates, Microsoft recommends that you update your devices to the latest version of Windows 10. For more information on end of service dates and currently supported versions of Windows 10, see the Windows lifecycle fact sheet. +
+
+ " - items: 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 4c3dfc4364..5a2c3b8df0 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 @@ -118,7 +118,7 @@ sections: - type: markdown text: " - +
DetailsOriginating updateStatusHistory
Devices with some Asian language packs installed may receive an error
After installing the April 2019 Cumulative Update (KB4493509), devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.\"

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019
Workaround:
  1. Uninstall and reinstall any recently added language packs. For instructions, see \"Manage the input and display language settings in Windows 10\".
  2. Click Check for Updates and install the April 2019 Cumulative Update. For instructions, see \"Update Windows 10\".
Note: If reinstalling the language pack does not mitigate the issue, reset your PC as follows:
  1. Go to Settings app -> Recovery.
  2. Click on Get Started under \"Reset this PC\" recovery option.
  3. Select \"Keep my Files\".
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 17763.437

April 09, 2019
KB4493509		Mitigated
Last updated:
May 03, 2019
10:59 AM PT

Opened:
May 02, 2019
04:36 PM PT
Devices with some Asian language packs installed may receive an error
After installing the April 2019 Cumulative Update (KB4493509), devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.\"

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019
Workaround:
  1. Uninstall and reinstall any recently added language packs. For instructions, see \"Manage the input and display language settings in Windows 10\".
  2. Click Check for Updates and install the April 2019 Cumulative Update. For instructions, see \"Update Windows 10\".
Note: If reinstalling the language pack does not mitigate the issue, reset your PC as follows:
    1. Go to Settings app -> Recovery.
    2. Click on Get Started under \"Reset this PC\" recovery option.
    3. Select \"Keep my Files\".
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 17763.437

April 09, 2019
KB4493509		Mitigated
Last updated:
May 03, 2019
10:59 AM PT

Opened:
May 02, 2019
04:36 PM PT
" diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index 9b7700d02e..1c6c129a90 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -65,7 +65,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.

- + @@ -130,7 +130,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
August 20, 2019
10:50 AM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
August 20, 2019
11:06 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Investigating
August 17, 2019
01:49 PM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive an error, \"Updates Failed, There were problems installing some updates, but we'll try again later\" and \"Error 0x80073701.\"

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 16, 2019
04:28 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 13, 2019
06:59 PM PT
- + diff --git a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml index 15f5bd4ccc..a57a74739b 100644 --- a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml @@ -60,10 +60,10 @@ 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.

DetailsOriginating updateStatusHistory
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution and estimates a solution will be available in late August.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
Last updated:
August 20, 2019
10:50 AM PT

Opened:
May 24, 2019
04:20 PM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution and estimates a solution will be available in late August.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
Last updated:
August 20, 2019
11:06 AM PT

Opened:
May 24, 2019
04:20 PM PT
Intermittent loss of Wi-Fi connectivity
Some older computers may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM).

To safeguard your upgrade experience, we have applied a hold on devices with this Qualcomm driver from being offered Windows 10, version 1903, until the updated driver is installed.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: Before updating to Windows 10, version 1903, you will need to download and install an updated Wi-Fi driver from your device manufacturer (OEM).
 
Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated External
Last updated:
August 01, 2019
08:44 PM PT

Opened:
May 21, 2019
07:13 AM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

Microsoft has identified some scenarios in which these features may have issues or stop working, for example:
  • Connecting to (or disconnecting from) an external monitor, dock, or projector
  • Rotating the screen
  • Updating display drivers or making other display mode changes
  • Closing full screen applications
  • Applying custom color profiles
  • Running applications that rely on custom gamma ramps
Affected platforms:
  • Client: Windows 10, version 1903
Workaround: If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer. For other color setting issues, restart your computer to correct the issue.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
August 01, 2019
06:27 PM PT

Opened:
May 21, 2019
07:28 AM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Windows 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change.

To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4505903 and the safeguard hold has been removed. Please ensure you have applied the resolving update before attempting to update to the Windows 10 May 2019 Update (version 1903). Please note, it can take up to 48 hours for the safeguard to be removed.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4505903		Resolved:
July 26, 2019
02:00 PM PT

Opened:
May 21, 2019
07:56 AM PT
+ -
SummaryOriginating updateStatusLast updated
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV
Windows updates that are SHA-2 signed are not available with Symantec or Norton antivirus program installed

See details >		August 13, 2019
KB4512506		Mitigated External
August 23, 2019
04:25 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503292		Resolved
KB4512514		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512506		Resolved
KB4517297		August 16, 2019
02:00 PM PT
IA64 and x64 devices may fail to start after installing updates
After installing updates released on or after August 13, 2019, IA64 and x64 devices using EFI Boot may fail to start.

See details >		August 13, 2019
KB4512506		Mitigated
August 17, 2019
12:59 PM PT
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV
Windows udates that are SHA-2 signed are not available with Symantec or Norton antivirus program installed

See details >		August 13, 2019
KB4512506		Investigating
August 16, 2019
04:28 PM PT
System may be unresponsive after restart with certain McAfee antivirus products
Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.

See details >		April 09, 2019
KB4493472		Resolved External
August 13, 2019
06:59 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503292		Resolved External
August 09, 2019
07:03 PM PT
@@ -81,9 +81,9 @@ sections: - type: markdown text: " + -
DetailsOriginating updateStatusHistory
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV
Symantec identified the potential for a negative interaction that may occur after Windows Updates code signed with SHA-2 only certificates are installed on devices with Symantec or Norton antivirus programs installed. The software may not correctly identify files included in the update as code signed by Microsoft, putting the device at risk for a delayed or incomplete update.

Affected platforms:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1
Mitigation: To mitigate this issue, Symantec and Norton released updates to their anti-virus software. Symantec Endpoint Protection protected devices can safely apply this update and future updates. See the Symantec support article for additional detail. Norton Security and Norton 360 products will automatically install a product update or users may manually run LiveUpdate and reboot until there are no further updates available.

Next Steps: The safeguard hold on affected devices will be removed in the coming week to allow customers time to apply the resolving anti-virus updates.

Back to top		August 13, 2019
KB4512506		Mitigated External
Last updated:
August 23, 2019
04:25 PM PT

Opened:
August 13, 2019
10:05 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512506, 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 KB4517297. The ‘optional’ update is now available on Microsoft Update Catalog and Windows Server Update Services (WSUS).

Back to top		August 13, 2019
KB4512506		Resolved
KB4517297		Resolved:
August 16, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
IA64 and x64 devices may fail to start after installing updates
IA64 devices (in any configuration) and x64 devices using EFI boot that were provisioned after the July 9th updates and/or skipped the recommended update (KB3133977), may fail to start with the following error:
\"File: \\Windows\\system32\\winload.efi
Status: 0xc0000428
Info: Windows cannot verify the digital signature for this file.\"

Affected platforms:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1
Take Action: To resolve this issue please follow the steps outlined in the SHA-2 support FAQ article for error code 0xc0000428.

Back to top		August 13, 2019
KB4512506		Mitigated
Last updated:
August 17, 2019
12:59 PM PT

Opened:
August 13, 2019
08:34 AM PT
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV
Symantec has identified an issue that occurs when a device is running any Symantec or Norton antivirus program and installs updates for Windows that are signed with SHA-2 certificates only. The Windows updates are blocked or deleted by the antivirus program during installation, which may then cause Windows to stop working or fail to start.

Affected platforms:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1
Workaround: Guidance for Symantec customers can be found in the Symantec support article and the Norton support article.

Next steps: To safeguard your update experience, Microsoft and Symantec have partnered to place a safeguard hold on devices with an affected version of Symantec Antivirus or Norton Antivirus installed to prevent them from receiving this type of Windows update until a solution is available. We recommend that you do not manually install affected updates until a solution is available. Please reach out to Symantec or Norton support for further guidance.

Back to top		August 13, 2019
KB4512506		Investigating
Last updated:
August 16, 2019
04:28 PM PT

Opened:
August 13, 2019
10:05 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503292) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		June 11, 2019
KB4503292		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" diff --git a/windows/release-information/windows-message-center.yml b/windows/release-information/windows-message-center.yml index 6cacd95c0a..0ff0106922 100644 --- a/windows/release-information/windows-message-center.yml +++ b/windows/release-information/windows-message-center.yml @@ -49,11 +49,13 @@ sections: - type: markdown text: " - + + + + - @@ -78,8 +80,8 @@ Given the potential impact to customers and their businesses, we have also relea From 5cfda3f8607ddddea59d3a14531b38b17c341f50 Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Thu, 29 Aug 2019 11:35:07 -0700 Subject: [PATCH 4/9] CAT Auto Pulish for Windows Release Messages - 20190829112356 (#1007) * Update deploy-the-latest-firmware-and-drivers-for-surface-devices.md * add table * CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20190829102107 (#1006) --- ...irmware-and-drivers-for-surface-devices.md | 2 +- .../status-windows-10-1903.yml | 20 +++++++++---------- .../windows-message-center.yml | 1 + .../respond-file-alerts.md | 12 +++++++++++ 4 files changed, 24 insertions(+), 11 deletions(-) diff --git a/devices/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices.md b/devices/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices.md index 4bad708b64..94094f2b60 100644 --- a/devices/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices.md +++ b/devices/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices.md @@ -11,7 +11,7 @@ ms.mktglfcycl: deploy ms.pagetype: surface, devices ms.sitesec: library author: dansimp -ms.date: 08/13/2018 +ms.date: 08/13/2019 ms.author: dansimp ms.topic: article --- diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index f2377ee4cf..ceed17f7b4 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -65,18 +65,18 @@ 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.

MessageDate
Resolved: Delays starting Internet Explorer 11
On August 16, 2019 at 7:16 AM a server required for downloading the Internet Explorer 11 (IE11) startup page, went down. As a result of the server outage, IE 11 became unresponsive for some customers who had not yet installed the August 2019 security updates. Customers who had the August 2019 security update installed were not affected. In order to ensure your devices remain in a serviced and secure state, we recommend you install the latest monthly update.

This issue was resolved on the server side at 1:00 pm PST. 
August 16, 2019
04:00 PM PT
Take action: SHA-2 code signing support guidance for Windows 7 SP1 and Windows Server 2008 RS2 SP1
Windows 7 SP1 and Windows Server 2008 R2 SP1 update signatures are now SHA-2 based signatures and requires that SHA-2 support to be installed. For important customer guidance on installation and troubleshooting tips, please read the knowledge base article 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
August 23, 2019
03:35 PM PT
Take action: Windows 10, version 1703 (the Windows 10 Creators Update) reaches end of life on October 9, 2019
The Enterprise and Education editions of Windows 10, version 1703 (the Windows 10 Creators Update) will reach end of life on October 9, 2019. The Home, Pro, Pro for Workstations, and IoT Core editions reached end of service on October 8, 2018.

There is no extended support available for any edition of Windows 10, version 1703. Therefore, it will no longer be supported after October 9, 2019 and will not receive monthly security and quality updates containing protections from the latest security threats.

To continue receiving security and quality updates, Microsoft recommends that you update your devices to the latest version of Windows 10. For more information on end of service dates and currently supported versions of Windows 10, see the Windows lifecycle fact sheet.
August 23, 2019
02:17 PM PT
Resolved: Delays starting Internet Explorer 11
On August 16, 2019 at 7:16 AM a server required for downloading the Internet Explorer 11 (IE11) startup page, went down. As a result of the server outage, IE 11 became unresponsive for some customers who had not yet installed the August 2019 security updates. Customers who had the August 2019 security update installed were not affected. In order to ensure your devices remain in a serviced and secure state, we recommend you install the latest monthly update.

This issue was resolved on the server side at 1:00 pm PST. 
August 16, 2019
04:00 PM PT
August 2019 security update now available for Windows 10, version 1903 and all supported versions of Windows
The August 2019 security update release, referred to as our “B” release, is now available for Windows 10, version 1903 and all supported versions of Windows. A “B” release is the primary, regular update event for each month and is the only regular release that contains security fixes. As a result, we recommend that you install these updates promptly. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. To be informed about the latest updates and releases, follow us on Twitter @WindowsUpdate.
August 13, 2019
10:00 AM PT
Advisory: Bluetooth encryption key size vulnerability disclosed (CVE-2019-9506)
On August 13, 2019, Microsoft released security updates to address a Bluetooth key length encryption vulnerability. To exploit this vulnerability, an attacker would need specialized hardware and would be limited by the signal range of the Bluetooth devices in use. For more information about this industry-wide issue, see CVE-2019-9506 | Bluetooth Encryption Key Size Vulnerability in the Microsoft Security Update Guide and important guidance for IT pros in KB4514157. (Note: we are documenting this vulnerability together with guidance for IT admins as part of a coordinated industry disclosure effort.)
August 13, 2019
10:00 AM PT
Advisory: Windows Advanced Local Procedure Call Elevation of Privilege vulnerability disclosed (CVE-2019-1162)
On August 13, 2019, Google Project Zero (GPZ) disclosed an Elevation of Privilege (EoP) vulnerability in how Windows handles calls to Advanced Local Procedure Call (ALPC) that affects Windows operating systems, versions 8.1 and higher. An attacker must already have code execution on the target system to leverage these vulnerabilities. Microsoft released security updates on August 13, 2019 that partially address this issue. Other items disclosed by GPZ require more time to address and we are working to release a resolution in mid-September. For more information, see CVE-2019-1162 | Windows ALPC Elevation of Privilege Vulnerability
August 13, 2019
10:00 AM PT
Take action: Install required updates for Windows 7 SP1 and Windows Server 2008 RS2 SP1 for SHA-2 code sign support
As of August 13, 2019, Windows 7 SP1 and Windows Server 2008 R2 SP1 updates signatures only support SHA-2 code signing. As outlined in 2019 SHA-2 Code Signing Support requirement for Windows and WSUS, we are requiring that SHA-2 code signing support be installed. If you have Windows Update enabled and have applied the security updates released in March 2019 (KB4490628) and August 2019 (KB4474419), you are protected automatically; no further configuration is necessary. If you have not installed the March 2019 updates, you will need to do so in order to continue to receive updates on devices running Windows 7 SP1 and Windows Server 2008 R2 SP1.
August 13, 2019
10:00 AM PT
Take action: Windows 10, version 1803 (the April 2018 Update) reaches end of service on November 12, 2019
Windows 10, version 1803 (the April 2018 Update) will reach end of service on November 12, 2019 for Home and Pro editions. We will begin updating devices running Windows 10, version 1803 to Windows 10, version 1903 (the May 2019 Update) starting July 16, 2019 to help ensure that these devices remain in a serviced and secure state. For more information, see the Windows 10, version 1903 section of the Windows release health dashboard.
August 13, 2019
10:00 AM PT
Advisory: Windows Kernel Information Disclosure Vulnerability (CVE-2019-1125)
On July 9, 2019, Microsoft released a security update for a Windows kernel information disclosure vulnerability (CVE-2019-1125). Customers who have Windows Update enabled and have applied the security updates released on July 9, 2019 are protected automatically; no further configuration is necessary. For more information, see CVE-2019-1125 | Windows Kernel Information Disclosure Vulnerability in the Microsoft Security Update Guide. (Note: we are documenting this mitigation publicly today, instead of back in July, as part of a coordinated industry disclosure effort.)
August 06, 2019
10:00 AM PT
Resolved August 1, 2019 16:00 PT: Microsoft Store users may encounter blank screens when clicking on certain buttons
Some customers running the version of the Microsoft Store app released on July 29, 2019 encountered a blank screen when selecting “Switch out of S mode,” “Get Genuine,” or some “Upgrade to [version]” OS upgrade options. This issue has now been resolved and a new version of the Microsoft Store app has been released. Users who encountered this issue will need to update the Microsoft Store app on their device. If you are still encountering an issue, please see Fix problems with apps from Microsoft Store.
August 01, 2019
02:00 PM PT
Reminder: Windows 10 update servicing cadence
This month we received questions about the cadence of updates we released in April and May 2019. Here's a quick recap of our releases and servicing cadence:
  • April 9, 2019 was the regular Update Tuesday release for all versions of Windows.
    • -
  • May 1, 2019 was an \"optional,\" out of band non-security update (OOB) for Windows 10, version 1809. It was released to Microsoft Catalog and WSUS, providing a critical fix for our OEM partners.
    • -
  • May 3, 2019 was the \"optional\" Windows 10, version 1809 \"C\" release for April. This update contained important Japanese era packages for commercial customers to preview. It was released later than expected and mistakenly targeted as \"required\" (instead of \"optional\") for consumers, which pushed the update out to customers and required a reboot. Within 24 hours of receiving customer reports, we corrected the targeting logic and mitigated the issue.
    • +
  • May 1, 2019 was an \\\"optional,\\\" out of band non-security update (OOB) for Windows 10, version 1809. It was released to Microsoft Catalog and WSUS, providing a critical fix for our OEM partners.
    • +
  • May 3, 2019 was the \\\"optional\\\" Windows 10, version 1809 \\\"C\\\" release for April. This update contained important Japanese era packages for commercial customers to preview. It was released later than expected and mistakenly targeted as \\\"required\\\" (instead of \\\"optional\\\") for consumers, which pushed the update out to customers and required a reboot. Within 24 hours of receiving customer reports, we corrected the targeting logic and mitigated the issue.
For more information about the Windows 10 update servicing cadence, please see the Window IT Pro blog.
May 10, 2019
10:00 AM PT
- - + + - + - - + + @@ -95,7 +95,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
August 20, 2019
11:06 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Investigating
August 17, 2019
01:49 PM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
KB4512941		August 20, 2019
11:06 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Investigating
KB4512941		August 17, 2019
01:49 PM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive an error, \"Updates Failed, There were problems installing some updates, but we'll try again later\" and \"Error 0x80073701.\"

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 16, 2019
04:28 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 13, 2019
06:59 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
KB4512941		August 13, 2019
06:59 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
August 09, 2019
07:03 PM PT
Issues updating when certain versions of Intel storage drivers are installed
Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Mitigated External
August 09, 2019
07:03 PM PT
Intermittent loss of Wi-Fi connectivity
Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated External
August 01, 2019
08:44 PM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
August 01, 2019
06:27 PM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4505903		July 26, 2019
02:00 PM PT
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU
Some apps or games that needs to perform graphics intensive operations may close or fail to open on Surface Book 2 devices with Nvidia dGPU.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
July 16, 2019
09:04 AM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
July 12, 2019
04:42 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Mitigated
July 10, 2019
07:09 PM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
KB4512941		July 12, 2019
04:42 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Mitigated
KB4512941		July 10, 2019
07:09 PM PT
Unable to discover or connect to Bluetooth devices
Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:48 PM PT
Intel Audio displays an intcdaud.sys notification
Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:47 PM PT
Cannot launch Camera app
Microsoft and Intel have identified an issue affecting Intel RealSense SR300 or Intel RealSense S200 camera apps.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:47 PM PT
- +
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512508, 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
Next steps: Microsoft is working on a resolution and estimates a solution will be available late August. 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 the update once it is released.

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 18362.295

August 13, 2019
KB4512508		Investigating
Last updated:
August 17, 2019
01:49 PM PT

Opened:
August 14, 2019
03:34 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512508, 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
Next steps: Microsoft is working on a resolution and estimates a solution will be available late August. 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 the update once it is released.

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 18362.295

August 13, 2019
KB4512508		Investigating
KB4512941		Last updated:
August 17, 2019
01:49 PM PT

Opened:
August 14, 2019
03:34 PM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive the error message, \"Updates Failed, There were problems installing some updates, but we'll try again later\" or \"Error 0x80073701\" on the Windows Update dialog or within Update history.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
Last updated:
August 16, 2019
04:28 PM PT

Opened:
August 16, 2019
01:41 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503293) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
@@ -107,11 +107,11 @@ sections: text: " +

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Next steps: At this time, we suggest that devices in an affected environment do not install KB4497935. We are working on a resolution and estimate a solution will be available in late August.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top - - + +
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Next steps: At this time, we suggest that devices in an affected environment do not install KB4497935. We are working on a resolution and estimate a solution will be available in late August.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
Last updated:
August 13, 2019
06:59 PM PT

Opened:
July 25, 2019
06:10 PM PT
OS Build 18362.145

May 29, 2019
KB4497935		Investigating
KB4512941		Last updated:
August 13, 2019
06:59 PM PT

Opened:
July 25, 2019
06:10 PM PT
Issues updating when certain versions of Intel storage drivers are installed
Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903).  

To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated.

Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Workaround: To mitigate this issue before the resolution is released, you will need to update the Intel RST drivers for your device to version 15.5.2.1054 or a later.  Check with your device manufacturer (OEM) to see if an updated driver is available and install it. You can also download the latest Intel RST drivers directly from Intel at Intel® Rapid Storage Technology (Intel® RST) User Interface and Driver. Once your drivers are updated, you can restart the installation process for Windows 10, version 1903. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903.

Note Until an updated driver has been installed, we recommend you do not attempt to manually update using the Update now button or the Media Creation Tool. 

Next Steps: We are working on a resolution and estimate a solution will be available in late August.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Mitigated External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
July 25, 2019
06:10 PM PT
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU
Microsoft has identified a compatibility issue on some Surface Book 2 devices configured with Nvidia discrete graphics processing unit (dGPU). After updating to Windows 10, version 1903 (May 2019 Feature Update), some apps or games that needs to perform graphics intensive operations may close or fail to open.

To safeguard your update experience, we have applied a compatibility hold on Surface Book 2 devices with Nvidia dGPUs from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: To mitigate the issue if you are already on Windows 10, version 1903, you can restart the device or select the Scan for hardware changes button in the Action menu or on the toolbar in Device Manager.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
Last updated:
July 16, 2019
09:04 AM PT

Opened:
July 12, 2019
04:20 PM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU).

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Next steps: We are working on a resolution that will be made available in upcoming release.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
Last updated:
July 12, 2019
04:42 PM PT

Opened:
July 12, 2019
04:42 PM PT
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 KB4503293 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
Workaround:
To mitigate this issue on an SCCM server:
  1. Verify Variable Window Extension is enabled.
  2. Set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In WDS TFTP settings, verify Variable Window Extension is enabled.
  2. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  3. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Mitigated
Last updated:
July 10, 2019
07:09 PM PT

Opened:
July 10, 2019
02:51 PM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU).

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Next steps: We are working on a resolution that will be made available in upcoming release.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
KB4512941		Last updated:
July 12, 2019
04:42 PM PT

Opened:
July 12, 2019
04:42 PM PT
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 KB4503293 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
Workaround:
To mitigate this issue on an SCCM server:
  1. Verify Variable Window Extension is enabled.
  2. Set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In WDS TFTP settings, verify Variable Window Extension is enabled.
  2. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  3. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Mitigated
KB4512941		Last updated:
July 10, 2019
07:09 PM PT

Opened:
July 10, 2019
02:51 PM PT
" @@ -120,7 +120,7 @@ sections: - type: markdown text: " - + diff --git a/windows/release-information/windows-message-center.yml b/windows/release-information/windows-message-center.yml index 0ff0106922..a69de08f66 100644 --- a/windows/release-information/windows-message-center.yml +++ b/windows/release-information/windows-message-center.yml @@ -50,6 +50,7 @@ sections: text: "
DetailsOriginating updateStatusHistory
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution and estimates a solution will be available in late August.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
Last updated:
August 20, 2019
11:06 AM PT

Opened:
May 24, 2019
04:20 PM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution and estimates a solution will be available in late August.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
KB4512941		Last updated:
August 20, 2019
11:06 AM PT

Opened:
May 24, 2019
04:20 PM PT
Intermittent loss of Wi-Fi connectivity
Some older computers may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM).

To safeguard your upgrade experience, we have applied a hold on devices with this Qualcomm driver from being offered Windows 10, version 1903, until the updated driver is installed.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: Before updating to Windows 10, version 1903, you will need to download and install an updated Wi-Fi driver from your device manufacturer (OEM).
 
Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated External
Last updated:
August 01, 2019
08:44 PM PT

Opened:
May 21, 2019
07:13 AM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

Microsoft has identified some scenarios in which these features may have issues or stop working, for example:
  • Connecting to (or disconnecting from) an external monitor, dock, or projector
  • Rotating the screen
  • Updating display drivers or making other display mode changes
  • Closing full screen applications
  • Applying custom color profiles
  • Running applications that rely on custom gamma ramps
Affected platforms:
  • Client: Windows 10, version 1903
Workaround: If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer. For other color setting issues, restart your computer to correct the issue.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
August 01, 2019
06:27 PM PT

Opened:
May 21, 2019
07:28 AM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Windows 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change.

To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4505903 and the safeguard hold has been removed. Please ensure you have applied the resolving update before attempting to update to the Windows 10 May 2019 Update (version 1903). Please note, it can take up to 48 hours for the safeguard to be removed.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4505903		Resolved:
July 26, 2019
02:00 PM PT

Opened:
May 21, 2019
07:56 AM PT
+ diff --git a/windows/security/threat-protection/microsoft-defender-atp/respond-file-alerts.md b/windows/security/threat-protection/microsoft-defender-atp/respond-file-alerts.md index 3910cda2ff..ee0bb0ff9b 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/respond-file-alerts.md +++ b/windows/security/threat-protection/microsoft-defender-atp/respond-file-alerts.md @@ -40,6 +40,18 @@ Response actions run along the top of the file page, and include: You can also submit files for deep analysis, to run the file in a secure cloud sandbox. When the analysis is complete, you'll get a detailed report that provides information about the behavior of the file. You can submit files for deep analysis and read past reports by selecting the **Deep analysis** tab. It's located below the file information cards. +Some actions require certain permissions. The following table describes what action certain permissions can take on portable executable (PE) and non-PE files: + +Permission | PE files | Non-PE files +:---|:---|:--- +View data | X | X +Alerts investigation | ☑ | X +Live response basic | X | X +Live response advanced | ☑ |☑ + +For more information on roles, see [Create and manage roles for role-based access control](user-roles.md). + + ## Stop and quarantine files in your network You can contain an attack in your organization by stopping the malicious process and quarantining the file where it was observed. From 17d4fb7dd81d08feee42855e0b5ee368c36658f3 Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Thu, 29 Aug 2019 19:00:31 -0700 Subject: [PATCH 5/9] CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20190829175859 (#1012) (#1013) --- windows/release-information/windows-message-center.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/windows/release-information/windows-message-center.yml b/windows/release-information/windows-message-center.yml index a69de08f66..eee75f9b25 100644 --- a/windows/release-information/windows-message-center.yml +++ b/windows/release-information/windows-message-center.yml @@ -50,6 +50,7 @@ sections: text: "
MessageDate
Take Action: Internet Explorer 11 now available on Windows Update/WSUS for Windows Server 2012 and Windows Embedded 8 Standard
Internet Explorer 11 (KB 4492872) is now available via Windows Update (WU) and Windows Server Update Services (WSUS) for commercial customers running Windows Server 2012 and Windows Embedded 8 Standard. For details about these changes and end of support for IE10, please refer to the IT Pro blog. 
August 29, 2019
08:00 AM PT
Take action: SHA-2 code signing support guidance for Windows 7 SP1 and Windows Server 2008 RS2 SP1
Windows 7 SP1 and Windows Server 2008 R2 SP1 update signatures are now SHA-2 based signatures and requires that SHA-2 support to be installed. For important customer guidance on installation and troubleshooting tips, please read the knowledge base article 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
August 23, 2019
03:35 PM PT
Take action: Windows 10, version 1703 (the Windows 10 Creators Update) reaches end of life on October 9, 2019
The Enterprise and Education editions of Windows 10, version 1703 (the Windows 10 Creators Update) will reach end of life on October 9, 2019. The Home, Pro, Pro for Workstations, and IoT Core editions reached end of service on October 8, 2018.

There is no extended support available for any edition of Windows 10, version 1703. Therefore, it will no longer be supported after October 9, 2019 and will not receive monthly security and quality updates containing protections from the latest security threats.

To continue receiving security and quality updates, Microsoft recommends that you update your devices to the latest version of Windows 10. For more information on end of service dates and currently supported versions of Windows 10, see the Windows lifecycle fact sheet.
August 23, 2019
02:17 PM PT
Resolved: Delays starting Internet Explorer 11
On August 16, 2019 at 7:16 AM a server required for downloading the Internet Explorer 11 (IE11) startup page, went down. As a result of the server outage, IE 11 became unresponsive for some customers who had not yet installed the August 2019 security updates. Customers who had the August 2019 security update installed were not affected. In order to ensure your devices remain in a serviced and secure state, we recommend you install the latest monthly update.

This issue was resolved on the server side at 1:00 pm PST. 
August 16, 2019
04:00 PM PT
+ From c084d21ab6ad7c1165155315bd50591504fb4e66 Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Fri, 30 Aug 2019 11:11:11 -0700 Subject: [PATCH 6/9] CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20190830100739 (#1018) (#1019) --- .../resolved-issues-windows-10-1903.yml | 21 +++++++++++++++ .../status-windows-10-1903.yml | 26 +++++++++---------- .../windows-message-center.yml | 1 + 3 files changed, 35 insertions(+), 13 deletions(-) diff --git a/windows/release-information/resolved-issues-windows-10-1903.yml b/windows/release-information/resolved-issues-windows-10-1903.yml index 46128ad713..e3349d1356 100644 --- a/windows/release-information/resolved-issues-windows-10-1903.yml +++ b/windows/release-information/resolved-issues-windows-10-1903.yml @@ -32,6 +32,12 @@ sections: - type: markdown text: "
MessageDate
Feature update install notification on Windows 10, version 1809 (the October 2018 Update)
We've had reports on August 29th that some customers running Windows 10, version 1809 (the October 2018 Update) have received notification to install the latest feature update (version 1903) early. Updating remains in your control. To install the update, you must select one of the following options: \"Pick a Time\", \"Restart Tonight,\" or \"Restart Now\". If you are not ready to update at this time, simply dismiss the notification by clicking the arrow in the top right corner. If you have updated to Windows 10, version 1903 and would like to go back to your previous version, see the instructions here.
August 29, 2019
04:39 PM PT
Take Action: Internet Explorer 11 now available on Windows Update/WSUS for Windows Server 2012 and Windows Embedded 8 Standard
Internet Explorer 11 (KB 4492872) is now available via Windows Update (WU) and Windows Server Update Services (WSUS) for commercial customers running Windows Server 2012 and Windows Embedded 8 Standard. For details about these changes and end of support for IE10, please refer to the IT Pro blog. 
August 29, 2019
08:00 AM PT
Take action: SHA-2 code signing support guidance for Windows 7 SP1 and Windows Server 2008 RS2 SP1
Windows 7 SP1 and Windows Server 2008 R2 SP1 update signatures are now SHA-2 based signatures and requires that SHA-2 support to be installed. For important customer guidance on installation and troubleshooting tips, please read the knowledge base article 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
August 23, 2019
03:35 PM PT
Take action: Windows 10, version 1703 (the Windows 10 Creators Update) reaches end of life on October 9, 2019
The Enterprise and Education editions of Windows 10, version 1703 (the Windows 10 Creators Update) will reach end of life on October 9, 2019. The Home, Pro, Pro for Workstations, and IoT Core editions reached end of service on October 8, 2018.

There is no extended support available for any edition of Windows 10, version 1703. Therefore, it will no longer be supported after October 9, 2019 and will not receive monthly security and quality updates containing protections from the latest security threats.

To continue receiving security and quality updates, Microsoft recommends that you update your devices to the latest version of Windows 10. For more information on end of service dates and currently supported versions of Windows 10, see the Windows lifecycle fact sheet.
August 23, 2019
02:17 PM PT
+ + + + + + @@ -58,10 +64,24 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate resolved
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Issues updating when certain versions of Intel storage drivers are installed
Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Resolved
KB4512941		August 30, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
August 09, 2019
07:03 PM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4505903		July 26, 2019
02:00 PM PT
RASMAN service may stop working and result in the error “0xc0000005”
The Remote Access Connection Manager (RASMAN) service may stop working and result in the error “0xc0000005” with VPN profiles configured as an Always On VPN connection.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4505903		July 26, 2019
02:00 PM PT
+
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512508, 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 KB4512941. The ‘optional’ update is 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 KB4512941 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 18362.295

August 13, 2019
KB4512508		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
August 14, 2019
03:34 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503293) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" +- title: July 2019 +- items: + - type: markdown + text: " + + + + + +
DetailsOriginating updateStatusHistory
Issues updating when certain versions of Intel storage drivers are installed
Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903).  

To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated.

Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Workaround: To mitigate this issue before the safeguard hold is removed, you will need to update the Intel RST drivers for your device to version 15.5.2.1054 or a later.  Check with your device manufacturer (OEM) to see if an updated driver is available and install it. You can also download the latest Intel RST drivers directly from Intel at Intel® Rapid Storage Technology (Intel® RST) User Interface and Driver. Once your drivers are updated, you can restart the installation process for Windows 10, version 1903. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903.

Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU).

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

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 12, 2019
04:42 PM PT
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 KB4503293 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 KB4512941.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
+ " + - title: June 2019 - items: - type: markdown @@ -77,6 +97,7 @@ sections: - type: markdown text: " + diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index ceed17f7b4..5dd768299d 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -65,18 +65,18 @@ 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.

DetailsOriginating updateStatusHistory
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4512941.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
May 24, 2019
04:20 PM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Windows 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change.

To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4505903 and the safeguard hold has been removed. Please ensure you have applied the resolving update before attempting to update to the Windows 10 May 2019 Update (version 1903). Please note, it can take up to 48 hours for the safeguard to be removed.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4505903		Resolved:
July 26, 2019
02:00 PM PT

Opened:
May 21, 2019
07:56 AM PT
Loss of functionality in Dynabook Smartphone Link app
Some users may experience a loss of functionality after updating to Windows 10, version 1903 when using the Dynabook Smartphone Link application on Windows devices. Loss of functionality may affect the display of phone numbers in the Call menu and the ability to answer phone calls on the Windows PC.

To safeguard your update experience, we have applied a compatibility hold on devices with Dynabook Smartphone Link from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Resolved
Resolved:
July 11, 2019
01:54 PM PT

Opened:
May 24, 2019
03:10 PM PT
Error attempting to update with external USB device or memory card attached
If you have an external USB device or SD memory card attached when installing Windows 10, version 1903, you may get an error message stating \"This PC can't be upgraded to Windows 10.\" This is caused by inappropriate drive reassignment during installation.

Sample scenario: An update to Windows 10, version 1903 is attempted on a computer that has a thumb drive inserted into its USB port. Before the update, the thumb drive is mounted in the system as drive G based on the existing drive configuration. After the feature update is installed; however, the device is reassigned a different drive letter (e.g., drive H).

Note The drive reassignment is not limited to removable drives. Internal hard drives may also be affected.

To safeguard your update experience, we have applied a hold on devices with an external USB device or SD memory card attached from being offered Windows 10, version 1903 until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
Resolved:
July 11, 2019
01:53 PM PT

Opened:
May 21, 2019
07:38 AM PT
- - + + + + + + - - - - @@ -95,7 +95,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
KB4512941		August 20, 2019
11:06 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Investigating
KB4512941		August 17, 2019
01:49 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Issues updating when certain versions of Intel storage drivers are installed
Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Resolved
KB4512941		August 30, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive an error, \"Updates Failed, There were problems installing some updates, but we'll try again later\" and \"Error 0x80073701.\"

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 16, 2019
04:28 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
KB4512941		August 13, 2019
06:59 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
August 09, 2019
07:03 PM PT
Issues updating when certain versions of Intel storage drivers are installed
Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Mitigated External
August 09, 2019
07:03 PM PT
Intermittent loss of Wi-Fi connectivity
Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated External
August 01, 2019
08:44 PM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
August 01, 2019
06:27 PM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4505903		July 26, 2019
02:00 PM PT
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU
Some apps or games that needs to perform graphics intensive operations may close or fail to open on Surface Book 2 devices with Nvidia dGPU.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
July 16, 2019
09:04 AM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
KB4512941		July 12, 2019
04:42 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Mitigated
KB4512941		July 10, 2019
07:09 PM PT
Unable to discover or connect to Bluetooth devices
Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:48 PM PT
Intel Audio displays an intcdaud.sys notification
Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:47 PM PT
Cannot launch Camera app
Microsoft and Intel have identified an issue affecting Intel RealSense SR300 or Intel RealSense S200 camera apps.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
May 21, 2019
04:47 PM PT
- +
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512508, 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
Next steps: Microsoft is working on a resolution and estimates a solution will be available late August. 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 the update once it is released.

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 18362.295

August 13, 2019
KB4512508		Investigating
KB4512941		Last updated:
August 17, 2019
01:49 PM PT

Opened:
August 14, 2019
03:34 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512508, 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 KB4512941. The ‘optional’ update is 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 KB4512941 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 18362.295

August 13, 2019
KB4512508		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
August 14, 2019
03:34 PM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive the error message, \"Updates Failed, There were problems installing some updates, but we'll try again later\" or \"Error 0x80073701\" on the Windows Update dialog or within Update history.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
Last updated:
August 16, 2019
04:28 PM PT

Opened:
August 16, 2019
01:41 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503293) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
@@ -106,12 +106,12 @@ sections: - type: markdown text: " - - + + + + - -
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Next steps: At this time, we suggest that devices in an affected environment do not install KB4497935. We are working on a resolution and estimate a solution will be available in late August.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
KB4512941		Last updated:
August 13, 2019
06:59 PM PT

Opened:
July 25, 2019
06:10 PM PT
Issues updating when certain versions of Intel storage drivers are installed
Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903).  

To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated.

Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Workaround: To mitigate this issue before the resolution is released, you will need to update the Intel RST drivers for your device to version 15.5.2.1054 or a later.  Check with your device manufacturer (OEM) to see if an updated driver is available and install it. You can also download the latest Intel RST drivers directly from Intel at Intel® Rapid Storage Technology (Intel® RST) User Interface and Driver. Once your drivers are updated, you can restart the installation process for Windows 10, version 1903. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903.

Note Until an updated driver has been installed, we recommend you do not attempt to manually update using the Update now button or the Media Creation Tool. 

Next Steps: We are working on a resolution and estimate a solution will be available in late August.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Mitigated External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
July 25, 2019
06:10 PM PT
Issues updating when certain versions of Intel storage drivers are installed
Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903).  

To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated.

Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Workaround: To mitigate this issue before the safeguard hold is removed, you will need to update the Intel RST drivers for your device to version 15.5.2.1054 or a later.  Check with your device manufacturer (OEM) to see if an updated driver is available and install it. You can also download the latest Intel RST drivers directly from Intel at Intel® Rapid Storage Technology (Intel® RST) User Interface and Driver. Once your drivers are updated, you can restart the installation process for Windows 10, version 1903. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903.

Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU).

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

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 12, 2019
04:42 PM PT
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 KB4503293 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 KB4512941.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU
Microsoft has identified a compatibility issue on some Surface Book 2 devices configured with Nvidia discrete graphics processing unit (dGPU). After updating to Windows 10, version 1903 (May 2019 Feature Update), some apps or games that needs to perform graphics intensive operations may close or fail to open.

To safeguard your update experience, we have applied a compatibility hold on Surface Book 2 devices with Nvidia dGPUs from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: To mitigate the issue if you are already on Windows 10, version 1903, you can restart the device or select the Scan for hardware changes button in the Action menu or on the toolbar in Device Manager.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
Last updated:
July 16, 2019
09:04 AM PT

Opened:
July 12, 2019
04:20 PM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU).

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Next steps: We are working on a resolution that will be made available in upcoming release.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
KB4512941		Last updated:
July 12, 2019
04:42 PM PT

Opened:
July 12, 2019
04:42 PM PT
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 KB4503293 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
Workaround:
To mitigate this issue on an SCCM server:
  1. Verify Variable Window Extension is enabled.
  2. Set the values of TFTP block size to 4096 and TFTP window size to 1. For guidance on how to configure them, see Customize the RamDisk TFTP block and window sizes on PXE-enabled distribution points.
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager.

To mitigate this issue on a WDS server without SCCM:
  1. In WDS TFTP settings, verify Variable Window Extension is enabled.
  2. In the Boot Configuration Data (BCD) of the imported image, set RamDiskTFTPBlockSize to 1456.
  3. In the BCD of the imported image, set RamDiskTFTPWindowSize to 4.
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Mitigated
KB4512941		Last updated:
July 10, 2019
07:09 PM PT

Opened:
July 10, 2019
02:51 PM PT
" @@ -120,7 +120,7 @@ sections: - type: markdown text: " - + diff --git a/windows/release-information/windows-message-center.yml b/windows/release-information/windows-message-center.yml index eee75f9b25..2785208d7d 100644 --- a/windows/release-information/windows-message-center.yml +++ b/windows/release-information/windows-message-center.yml @@ -50,6 +50,7 @@ sections: text: "
DetailsOriginating updateStatusHistory
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution and estimates a solution will be available in late August.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Investigating
KB4512941		Last updated:
August 20, 2019
11:06 AM PT

Opened:
May 24, 2019
04:20 PM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4512941.

Back to top		OS Build 18362.116

May 20, 2019
KB4505057		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
May 24, 2019
04:20 PM PT
Intermittent loss of Wi-Fi connectivity
Some older computers may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM).

To safeguard your upgrade experience, we have applied a hold on devices with this Qualcomm driver from being offered Windows 10, version 1903, until the updated driver is installed.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: Before updating to Windows 10, version 1903, you will need to download and install an updated Wi-Fi driver from your device manufacturer (OEM).
 
Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated External
Last updated:
August 01, 2019
08:44 PM PT

Opened:
May 21, 2019
07:13 AM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

Microsoft has identified some scenarios in which these features may have issues or stop working, for example:
  • Connecting to (or disconnecting from) an external monitor, dock, or projector
  • Rotating the screen
  • Updating display drivers or making other display mode changes
  • Closing full screen applications
  • Applying custom color profiles
  • Running applications that rely on custom gamma ramps
Affected platforms:
  • Client: Windows 10, version 1903
Workaround: If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer. For other color setting issues, restart your computer to correct the issue.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
Last updated:
August 01, 2019
06:27 PM PT

Opened:
May 21, 2019
07:28 AM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Windows 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change.

To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4505903 and the safeguard hold has been removed. Please ensure you have applied the resolving update before attempting to update to the Windows 10 May 2019 Update (version 1903). Please note, it can take up to 48 hours for the safeguard to be removed.

Back to top		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4505903		Resolved:
July 26, 2019
02:00 PM PT

Opened:
May 21, 2019
07:56 AM PT
+ From 8b3979b9a55d226b6a8e52936d057f8812dcdacc Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Tue, 3 Sep 2019 14:02:07 -0700 Subject: [PATCH 7/9] CAT Auto Pulish for Windows Release Messages - 20190903135254 (#1033) * SIEM connector: change alert notion to Detection * update casing and redirects * remove space json file * fix json * CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20190903123340 (#1031) --- .openpublishing.redirection.json | 19 ++- .../resolved-issues-windows-10-1803.yml | 10 ++ ...indows-10-1809-and-windows-server-2019.yml | 12 -- .../status-windows-10-1803.yml | 10 ++ .../status-windows-10-1903.yml | 2 - windows/security/threat-protection/TOC.md | 15 +-- .../api-portal-mapping.md | 71 +++++----- .../configure-arcsight.md | 21 +-- .../microsoft-defender-atp/configure-siem.md | 35 ++--- .../configure-splunk.md | 24 ++-- .../enable-siem-integration.md | 23 ++-- .../get-ip-related-machines.md | 122 ------------------ .../is-domain-seen-in-org.md | 82 ------------ .../microsoft-defender-atp/is-ip-seen-org.md | 82 ------------ .../microsoft-defender-atp/management-apis.md | 1 - .../microsoft-defender-atp/oldTOC.txt | 15 +-- .../pull-alerts-using-rest-api.md | 48 +++---- .../troubleshoot-siem.md | 10 +- 18 files changed, 176 insertions(+), 426 deletions(-) delete mode 100644 windows/security/threat-protection/microsoft-defender-atp/get-ip-related-machines.md delete mode 100644 windows/security/threat-protection/microsoft-defender-atp/is-domain-seen-in-org.md delete mode 100644 windows/security/threat-protection/microsoft-defender-atp/is-ip-seen-org.md diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 16a10bcb81..95b887e08a 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -14778,7 +14778,7 @@ { "source_path": "windows/security/threat-protection/windows-defender-atp/get-ip-related-alerts-windows-defender-advanced-threat-protection-new.md", "redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/get-ip-related-alerts", -"redirect_document_id": true +"redirect_document_id": false }, { "source_path": "windows/security/threat-protection/windows-defender-atp/get-ip-related-machines-windows-defender-advanced-threat-protection.md", @@ -14788,7 +14788,7 @@ { "source_path": "windows/security/threat-protection/windows-defender-atp/get-ip-related-machines-windows-defender-advanced-threat-protection-new.md", "redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/get-ip-related-machines", -"redirect_document_id": true +"redirect_document_id": false }, { "source_path": "windows/security/threat-protection/windows-defender-atp/get-ip-statistics-windows-defender-advanced-threat-protection.md", @@ -15131,6 +15131,21 @@ "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/microsoft-defender-atp/is-domain-seen-in-org.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/get-domain-related-alerts", +"redirect_document_id": false +}, +{ +"source_path": "windows/security/threat-protection/microsoft-defender-atp/get-ip-related-machines.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/get-ip-related-alerts", +"redirect_document_id": true +}, +{ +"source_path": "windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp/is-ip-seen-org.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp/exposed-apis-list", +"redirect_document_id": false +}, +{ "source_path": "windows/security/threat-protection/windows-defender-atp/machineaction-windows-defender-advanced-threat-protection-new.md", "redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/machineaction", "redirect_document_id": true diff --git a/windows/release-information/resolved-issues-windows-10-1803.yml b/windows/release-information/resolved-issues-windows-10-1803.yml index b3059b9fe8..f6b4c85fb6 100644 --- a/windows/release-information/resolved-issues-windows-10-1803.yml +++ b/windows/release-information/resolved-issues-windows-10-1803.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: "
MessageDate
Status update: Windows 10, version 1903 \"D\" optional release available August 30th
The August optional monthly “D” release for Windows 10, version 1903 is now available. Follow @WindowsUpdate for the latest on the availability of this release.
August 30, 2019
08:00 AM PT
Feature update install notification on Windows 10, version 1809 (the October 2018 Update)
We've had reports on August 29th that some customers running Windows 10, version 1809 (the October 2018 Update) have received notification to install the latest feature update (version 1903) early. Updating remains in your control. To install the update, you must select one of the following options: \"Pick a Time\", \"Restart Tonight,\" or \"Restart Now\". If you are not ready to update at this time, simply dismiss the notification by clicking the arrow in the top right corner. If you have updated to Windows 10, version 1903 and would like to go back to your previous version, see the instructions here.
August 29, 2019
04:39 PM PT
Take Action: Internet Explorer 11 now available on Windows Update/WSUS for Windows Server 2012 and Windows Embedded 8 Standard
Internet Explorer 11 (KB 4492872) is now available via Windows Update (WU) and Windows Server Update Services (WSUS) for commercial customers running Windows Server 2012 and Windows Embedded 8 Standard. For details about these changes and end of support for IE10, please refer to the IT Pro blog. 
August 29, 2019
08:00 AM PT
Take action: SHA-2 code signing support guidance for Windows 7 SP1 and Windows Server 2008 RS2 SP1
Windows 7 SP1 and Windows Server 2008 R2 SP1 update signatures are now SHA-2 based signatures and requires that SHA-2 support to be installed. For important customer guidance on installation and troubleshooting tips, please read the knowledge base article 2019 SHA-2 Code Signing Support requirement for Windows and WSUS.
August 23, 2019
03:35 PM PT
+ @@ -58,6 +59,15 @@ sections:
" +- title: September 2019 +- items: + - type: markdown + text: " +
SummaryOriginating updateStatusDate resolved
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 Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17134.950

August 13, 2019
KB4512501		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		August 13, 2019
10:00 AM PT
+ +
DetailsOriginating updateStatusHistory
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\" in the Windows Update dialog and a red \"!\" in the task tray on the Windows Update tray icon. This notification is intended for devices that are 90 days or more out of date, but some users with installed updates released in June or July also saw this notification.

Affected platforms:
  • Client: Windows 10, version 1803
  • Server: Windows Server, version 1803
Resolution: This issue was resolved on the server side on August 30, 2019. Only devices that are out of date by 90 days or more should now see the notification. No action is required by the user to resolve this issue. If you are still seeing the \"Your device is missing important security and quality fixes\" notification, we recommend selecting Check for Updates in the Windows Update dialog. For instructions, see Update Windows 10. Microsoft always recommends trying to keep your devices up to date, as the monthly updates contain important security fixes. 

Back to top		N/A

Resolved
Resolved:
September 03, 2019
12:32 PM PT

Opened:
September 03, 2019
12:32 PM PT
+ " + - title: August 2019 - items: - type: markdown diff --git a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml index c70c55ae78..99b8f5966a 100644 --- a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml +++ b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml @@ -55,12 +55,6 @@ sections:
End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.

See details >OS Build 17763.404

April 02, 2019
KB4490481Resolved
KB4493509April 09, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >OS Build 17763.253

January 08, 2019
KB4480116Resolved
KB4493509April 09, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.

See details >OS Build 17763.316

February 12, 2019
KB4487044Resolved
KB4489899March 12, 2019
10:00 AM PT -
Internet Explorer may fail to load images
Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

See details >OS Build 17763.316

February 12, 2019
KB4487044Resolved
KB4482887March 01, 2019
10:00 AM PT -
First character of the Japanese era name not recognized
The first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues.

See details >OS Build 17763.316

February 12, 2019
KB4487044Resolved
KB4482887March 01, 2019
10:00 AM PT -
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 9 file format may randomly stop working.

See details >OS Build 17763.316

February 12, 2019
KB4487044Resolved
KB4482887March 01, 2019
10:00 AM PT -
Shared albums may not sync with iCloud for Windows
Upgrade block: Apple has identified an incompatibility with iCloud for Windows (version 7.7.0.27) where users may experience issues updating or synching Shared Albums.

See details >OS Build 17763.134

November 13, 2018
KB4467708Resolved
KB4482887March 01, 2019
10:00 AM PT -
Intel Audio Display (intcdaud.sys) notification during Windows 10 Setup
Upgrade block: Users may see an Intel Audio Display (intcdaud.sys) notification during setup for devices with certain Intel Display Audio Drivers.

See details >OS Build 17763.134

November 13, 2018
KB4467708Resolved
KB4482887March 01, 2019
10:00 AM PT -
F5 VPN clients losing network connectivity
Upgrade block: After updating to Windows 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.

See details >OS Build 17763.134

November 13, 2018
KB4467708Resolved
KB4482887March 01, 2019
10:00 AM PT
Global DNS outage affects Windows Update customers
Windows Update customers were recently affected by a network infrastructure event caused by an external DNS service provider's global outage.

See details >N/A

Resolved
March 08, 2019
11:15 AM PT
Apps may stop working after selecting an audio output device other than the default
Users with multiple audio devices that select an audio output device different from the \"Default Audio Device\" may find certain applications stop working unexpectedly.

See details >OS Build 17763.348

March 01, 2019
KB4482887Resolved
KB4490481April 02, 2019
10:00 AM PT @@ -148,9 +142,6 @@ sections: - - -
DetailsOriginating updateStatusHistory
Embedded objects may display incorrectly
Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. 
 
For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. 
 
Affected platforms:  
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1  
  • Server: 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 is resolved in KB4493509.  

Back to top		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4493509		Resolved:
April 09, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
After installing KB4487044, users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files. 

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue is resolved in KB4489899. 

Back to top		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4489899		Resolved:
March 12, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Internet Explorer may fail to load images
After installing KB4487044, Internet Explorer may fail to load images with a backslash (\\) in their relative source path.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2008 R2 SP1
Resolution: This issue is resolved in KB4482887.

Back to top		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4482887		Resolved:
March 01, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
First character of the Japanese era name not recognized
After installing KB4487044, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. 

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1; Windows 7 SP1
  • Server: 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 is resolved in KB4482887. 

Back to top		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4482887		Resolved:
March 01, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
Applications using Microsoft Jet database and Access 95 file format stop working
Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
Resolution: This issue is resolved in KB4482887.

Back to top		OS Build 17763.316

February 12, 2019
KB4487044		Resolved
KB4482887		Resolved:
March 01, 2019
10:00 AM PT

Opened:
February 12, 2019
10:00 AM PT
" @@ -171,8 +162,5 @@ sections: text: " - - -
DetailsOriginating updateStatusHistory
Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort
Upgrade block: Microsoft has identified issues with certain new Intel display drivers. Intel inadvertently released versions of its display driver (versions 24.20.100.6344, 24.20.100.6345) to OEMs that accidentally turned on unsupported features in Windows. 
 
As a result, after updating to Windows 10, version 1809, audio playback from a monitor or television connected to a PC via HDMI, USB-C, or a DisplayPort may not function correctly on devices with these drivers.
Note: This Intel display driver issue is different from the Intel Smart Sound Technology driver (version 09.21.00.3755) audio issue previously documented.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019 
Next steps: Intel has released updated drivers to OEM device manufacturers. OEMs need to make the updated driver available via Windows Update. For more information, see the Intel Customer Support article.

Resolution: Microsoft has removed the safeguard hold.



Back to top		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
Resolved:
May 21, 2019
07:42 AM PT

Opened:
November 13, 2018
10:00 AM PT
Shared albums may not sync with iCloud for Windows
Upgrade block: Users who attempt to install iCloud for Windows (version 7.7.0.27) will see a message displayed that this version iCloud for Windows isn't supported and the install will fail.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019
To ensure a seamless experience, Microsoft is blocking devices with iCloud for Windows (version 7.7.0.27) software installed from being offered Windows 10, version 1809 until this issue has been resolved. 

We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool from the Microsoft software download website until this issue is resolved. 
 
Resolution: Apple has released an updated version of iCloud for Windows (version 7.8.1) that resolves compatibility issues encountered when updating or synching Shared Albums after updating to Windows 10, version 1809. We recommend that you update your iCloud for Windows to version 7.8.1 when prompted before attempting to upgrade to Windows 10, version 1809. You can also manually download the latest version of iCloud for Windows by visiting https://support.apple.com/HT204283.

Back to top		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4482887		Resolved:
March 01, 2019
10:00 AM PT

Opened:
November 13, 2018
10:00 AM PT
Intel Audio Display (intcdaud.sys) notification during Windows 10 Setup
Upgrade block: Microsoft and Intel have identified a compatibility issue with a range of Intel Display Audio device drivers (intcdaud.sys, versions 10.25.0.3 - 10.25.0.8) that may result in excessive processor demand and reduced battery life. As a result, the update process to the Windows 10 October 2018 Update (Windows 10, version 1809) will fail and affected devices will automatically revert to the previous working configuration. 

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019
If you see a \"What needs your attention\" notification during installation of the October 2018 Update, you have one of these affected drivers on your system. On the notification, click Back to remain on your current version of Windows 10. 
 
To ensure a seamless experience, we are blocking devices from being offered the October 2018 Update until updated Intel device drivers are installed on your current operating system. We recommend that you do not attempt to manually update to Windows 10, version 1809, using the Update Now button or the Media Creation Tool from the Microsoft Software Download Center until newer Intel device drivers are available with the update. You can either wait for newer drivers to be installed automatically through Windows Update or check with your computer manufacturer for the latest device driver software availability and installation procedures. For more information about this issue, see Intel's customer support guidance.
 
Resolution: This issue was resolved in KB4482887 and the upgrade block removed. 

Back to top		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4482887		Resolved:
March 01, 2019
10:00 AM PT

Opened:
November 13, 2018
10:00 AM PT
F5 VPN clients losing network connectivity
Upgrade block: After updating to Windows 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration.

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019
Resolution: This issue was resolved in KB4482887 and the upgrade block removed. 

Back to top		OS Build 17763.134

November 13, 2018
KB4467708		Resolved
KB4482887		Resolved:
March 01, 2019
10:00 AM PT

Opened:
November 13, 2018
10:00 AM PT
" diff --git a/windows/release-information/status-windows-10-1803.yml b/windows/release-information/status-windows-10-1803.yml index c9f0739b5a..fe3c6577c2 100644 --- a/windows/release-information/status-windows-10-1803.yml +++ b/windows/release-information/status-windows-10-1803.yml @@ -65,6 +65,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.

+ @@ -81,6 +82,15 @@ sections:
" +- title: September 2019 +- items: + - type: markdown + text: " +
SummaryOriginating updateStatusLast updated
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 Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17134.950

August 13, 2019
KB4512501		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		August 13, 2019
10:00 AM PT
+ +
DetailsOriginating updateStatusHistory
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\" in the Windows Update dialog and a red \"!\" in the task tray on the Windows Update tray icon. This notification is intended for devices that are 90 days or more out of date, but some users with installed updates released in June or July also saw this notification.

Affected platforms:
  • Client: Windows 10, version 1803
  • Server: Windows Server, version 1803
Resolution: This issue was resolved on the server side on August 30, 2019. Only devices that are out of date by 90 days or more should now see the notification. No action is required by the user to resolve this issue. If you are still seeing the \"Your device is missing important security and quality fixes\" notification, we recommend selecting Check for Updates in the Windows Update dialog. For instructions, see Update Windows 10. Microsoft always recommends trying to keep your devices up to date, as the monthly updates contain important security fixes. 

Back to top		N/A

Resolved
Resolved:
September 03, 2019
12:32 PM PT

Opened:
September 03, 2019
12:32 PM PT
+ " + - title: August 2019 - items: - type: markdown diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index 5dd768299d..72034e1a27 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -75,7 +75,6 @@ sections:
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >OS Build 18362.175

June 11, 2019
KB4503293Resolved External
August 09, 2019
07:03 PM PT
Intermittent loss of Wi-Fi connectivity
Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver.

See details >OS Build 18362.116

May 21, 2019
KB4505057Mitigated External
August 01, 2019
08:44 PM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

See details >OS Build 18362.116

May 21, 2019
KB4505057Mitigated
August 01, 2019
06:27 PM PT -
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers.

See details >OS Build 18362.116

May 21, 2019
KB4505057Resolved
KB4505903July 26, 2019
02:00 PM PT
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU
Some apps or games that needs to perform graphics intensive operations may close or fail to open on Surface Book 2 devices with Nvidia dGPU.

See details >OS Build 18362.145

May 29, 2019
KB4497935Investigating
July 16, 2019
09:04 AM PT
Unable to discover or connect to Bluetooth devices
Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers.

See details >OS Build 18362.116

May 21, 2019
KB4505057Mitigated
May 21, 2019
04:48 PM PT
Intel Audio displays an intcdaud.sys notification
Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain.

See details >OS Build 18362.116

May 21, 2019
KB4505057Mitigated
May 21, 2019
04:47 PM PT @@ -123,7 +122,6 @@ sections:
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4512941.

Back to topOS Build 18362.116

May 20, 2019
KB4505057Resolved
KB4512941Resolved:
August 30, 2019
10:00 AM PT

Opened:
May 24, 2019
04:20 PM PT
Intermittent loss of Wi-Fi connectivity
Some older computers may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM).

To safeguard your upgrade experience, we have applied a hold on devices with this Qualcomm driver from being offered Windows 10, version 1903, until the updated driver is installed.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: Before updating to Windows 10, version 1903, you will need to download and install an updated Wi-Fi driver from your device manufacturer (OEM).
 
Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you.

Back to topOS Build 18362.116

May 21, 2019
KB4505057Mitigated External
Last updated:
August 01, 2019
08:44 PM PT

Opened:
May 21, 2019
07:13 AM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

Microsoft has identified some scenarios in which these features may have issues or stop working, for example:
  • Connecting to (or disconnecting from) an external monitor, dock, or projector
  • Rotating the screen
  • Updating display drivers or making other display mode changes
  • Closing full screen applications
  • Applying custom color profiles
  • Running applications that rely on custom gamma ramps
Affected platforms:
  • Client: Windows 10, version 1903
Workaround: If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer. For other color setting issues, restart your computer to correct the issue.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to topOS Build 18362.116

May 21, 2019
KB4505057Mitigated
Last updated:
August 01, 2019
06:27 PM PT

Opened:
May 21, 2019
07:28 AM PT -
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Windows 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change.

To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4505903 and the safeguard hold has been removed. Please ensure you have applied the resolving update before attempting to update to the Windows 10 May 2019 Update (version 1903). Please note, it can take up to 48 hours for the safeguard to be removed.

Back to topOS Build 18362.116

May 21, 2019
KB4505057Resolved
KB4505903Resolved:
July 26, 2019
02:00 PM PT

Opened:
May 21, 2019
07:56 AM PT
Unable to discover or connect to Bluetooth devices
Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Realtek and Qualcomm. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Realtek or Qualcomm Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Workaround: Check with your device manufacturer (OEM) to see if an updated driver is available and install it.

  • For Qualcomm drivers, you will need to install a driver version greater than 10.0.1.11.
  • For Realtek drivers, you will need to install a driver version greater than 1.5.1011.0.
Note Until an updated driver has been installed, we recommend you do not attempt to manually update using the Update now button or the Media Creation Tool. 

Next steps: Microsoft is working with Realtek and Qualcomm to release new drivers for all affected system via Windows Update.  


Back to topOS Build 18362.116

May 21, 2019
KB4505057Mitigated
Last updated:
May 21, 2019
04:48 PM PT

Opened:
May 21, 2019
07:29 AM PT
Intel Audio displays an intcdaud.sys notification
Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in higher than normal battery drain. If you see an intcdaud.sys notification or “What needs your attention” notification when trying to update to Windows 10, version 1903, you have an affected Intel Audio Display device driver installed on your machine (intcdaud.sys, versions 10.25.0.3 through 10.25.0.8).
  
To safeguard your update experience, we have applied a compatibility hold on devices with drivers from being offered Windows 10, version 1903 until updated device drivers have been installed.

Affected platforms:
  • Client: Windows 10, version 1903; Windows 10, version 1809
Workaround:
On the “What needs your attention\" notification, click the Back button to remain on your current version of Windows 10. (Do not click Confirm as this will proceed with the update and you may experience compatibility issues.) Affected devices will automatically revert to the previous working configuration.

For more information, see Intel's customer support guidance and the Microsoft knowledge base article KB4465877.

Note We recommend you do not attempt to update your devices until newer device drivers are installed.

Next steps: You can opt to wait for newer drivers to be installed automatically through Windows Update or check with the computer manufacturer for the latest device driver software availability and installation procedures.

Back to topOS Build 18362.116

May 21, 2019
KB4505057Mitigated
Last updated:
May 21, 2019
04:47 PM PT

Opened:
May 21, 2019
07:22 AM PT
Cannot launch Camera app
Microsoft and Intel have identified an issue affecting Intel RealSense SR300 and Intel RealSense S200 cameras when using the Camera app. After updating to the Windows 10 May 2019 Update and launching the Camera app, you may get an error message stating:

\"Close other apps, error code: 0XA00F4243.”


To safeguard your update experience, we have applied a protective hold on machines with Intel RealSense SR300 or Intel RealSense S200 cameras installed from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: To temporarily resolve this issue, perform one of the following:

  • Unplug your camera and plug it back in.

or

  • Disable and re-enable the driver in Device Manager. In the Search box, type \"Device Manager\" and press Enter. In the Device Manager dialog box, expand Cameras, then right-click on any RealSense driver listed and select Disable device. Right click on the driver again and select Enable device.

or

  • Restart the RealSense service. In the Search box, type \"Task Manager\" and hit Enter. In the Task Manager dialog box, click on the Services tab, right-click on RealSense, and select Restart. 
Note This workaround will only resolve the issue until your next system restart.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to topOS Build 18362.116

May 21, 2019
KB4505057Mitigated
Last updated:
May 21, 2019
04:47 PM PT

Opened:
May 21, 2019
07:20 AM PT diff --git a/windows/security/threat-protection/TOC.md b/windows/security/threat-protection/TOC.md index 03328a26ed..ccf58c6fc9 100644 --- a/windows/security/threat-protection/TOC.md +++ b/windows/security/threat-protection/TOC.md @@ -398,7 +398,6 @@ ####### [Get domain related alerts](microsoft-defender-atp/get-domain-related-alerts.md) ####### [Get domain related machines](microsoft-defender-atp/get-domain-related-machines.md) ####### [Get domain statistics](microsoft-defender-atp/get-domain-statistics.md) -####### [Is domain seen in organization (Deprecated)](microsoft-defender-atp/is-domain-seen-in-org.md) ###### [File]() ####### [File methods and properties](microsoft-defender-atp/files.md) @@ -409,9 +408,7 @@ ###### [IP]() ####### [Get IP related alerts](microsoft-defender-atp/get-ip-related-alerts.md) -####### [Get IP related machines (Deprecated)](microsoft-defender-atp/get-ip-related-machines.md) ####### [Get IP statistics](microsoft-defender-atp/get-ip-statistics.md) -####### [Is IP seen in organization (Deprecated)](microsoft-defender-atp/is-ip-seen-org.md) ###### [User]() ####### [User methods](microsoft-defender-atp/user.md) @@ -440,13 +437,13 @@ ##### [Experiment with custom threat intelligence alerts (Deprecated)](microsoft-defender-atp/experiment-custom-ti.md) ##### [Troubleshoot custom threat intelligence issues (Deprecated)](microsoft-defender-atp/troubleshoot-custom-ti.md) -#### [Pull alerts to your SIEM tools]() -##### [Learn about different ways to pull alerts](microsoft-defender-atp/configure-siem.md) +#### [Pull detections to your SIEM tools]() +##### [Learn about different ways to pull detections](microsoft-defender-atp/configure-siem.md) ##### [Enable SIEM integration](microsoft-defender-atp/enable-siem-integration.md) -##### [Configure Splunk to pull alerts](microsoft-defender-atp/configure-splunk.md) -##### [Configure HP ArcSight to pull alerts](microsoft-defender-atp/configure-arcsight.md) -##### [Microsoft Defender ATP SIEM alert API fields](microsoft-defender-atp/api-portal-mapping.md) -##### [Pull alerts using SIEM REST API](microsoft-defender-atp/pull-alerts-using-rest-api.md) +##### [Configure Splunk to pull detections](microsoft-defender-atp/configure-splunk.md) +##### [Configure HP ArcSight to pull detections](microsoft-defender-atp/configure-arcsight.md) +##### [Microsoft Defender ATP detection fields](microsoft-defender-atp/api-portal-mapping.md) +##### [Pull detections using SIEM REST API](microsoft-defender-atp/pull-alerts-using-rest-api.md) ##### [Troubleshoot SIEM tool integration issues](microsoft-defender-atp/troubleshoot-siem.md) #### [Reporting]() diff --git a/windows/security/threat-protection/microsoft-defender-atp/api-portal-mapping.md b/windows/security/threat-protection/microsoft-defender-atp/api-portal-mapping.md index 9706e81443..ef351af05d 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/api-portal-mapping.md +++ b/windows/security/threat-protection/microsoft-defender-atp/api-portal-mapping.md @@ -1,7 +1,7 @@ --- -title: Microsoft Defender ATP alert API fields -description: Understand how the alert API fields map to the values in Microsoft Defender Security Center -keywords: alerts, alert fields, fields, api, fields, pull alerts, rest api, request, response +title: Microsoft Defender ATP detections API fields +description: Understand how the Detections API fields map to the values in Microsoft Defender Security Center +keywords: detections, detections fields, fields, api, fields, pull Detections, rest api, request, response search.product: eADQiWindows 10XVcnh search.appverid: met150 ms.prod: w10 @@ -15,10 +15,9 @@ manager: dansimp audience: ITPro ms.collection: M365-security-compliance ms.topic: article -ms.date: 10/16/2017 --- -# Microsoft Defender ATP SIEM alert API fields +# Microsoft Defender ATP detections API fields **Applies to:** @@ -26,10 +25,14 @@ ms.date: 10/16/2017 >Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-apiportalmapping-abovefoldlink) -Understand what data fields are exposed as part of the alerts API and how they map to Microsoft Defender Security Center. +Understand what data fields are exposed as part of the detections API and how they map to Microsoft Defender Security Center. -## Alert API fields and portal mapping -The following table lists the available fields exposed in the alerts API payload. It shows examples for the populated values and a reference on how data is reflected on the portal. +>[!Note] +>- [Microsoft Defender ATP Alert](alerts.md) is composed from one or more detections +>- **Microsoft Defender ATP Detection** is composed from the suspicious event occurred on the Machine and its related **Alert** details. + +## Detections API fields and portal mapping +The following table lists the available fields exposed in the detections API payload. It shows examples for the populated values and a reference on how data is reflected on the portal. The ArcSight field column contains the default mapping between the Microsoft Defender ATP fields and the built-in fields in ArcSight. You can download the mapping file from the portal when you enable the SIEM integration feature and you can modify it to match the needs of your organization. For more information, see [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md). @@ -39,33 +42,33 @@ Field numbers match the numbers in the images below. > > | Portal label | SIEM field name | ArcSight field | Example value | Description | > |------------------|---------------------------|---------------------|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -> | 1 | AlertTitle | name | Windows Defender AV detected 'Mikatz' high-severity malware | Value available for every alert. | -> | 2 | Severity | deviceSeverity | High | Value available for every alert. | -> | 3 | Category | deviceEventCategory | Malware | Value available for every alert. | -> | 4 | Detection source | sourceServiceName | Antivirus | Windows Defender Antivirus or Microsoft Defender ATP. Value available for every alert. | -> | 5 | MachineName | sourceHostName | desktop-4a5ngd6 | Value available for every alert. | -> | 6 | FileName | fileName | Robocopy.exe | Available for alerts associated with a file or process. | -> | 7 | FilePath | filePath | C:\Windows\System32\Robocopy.exe | Available for alerts associated with a file or process. | -> | 8 | UserDomain | sourceNtDomain | CONTOSO | The domain of the user context running the activity, available for Microsoft Defender ATP behavioral based alerts. | -> | 9 | UserName | sourceUserName | liz.bean | The user context running the activity, available for Microsoft Defender ATP behavioral based alerts. | -> | 10 | Sha1 | fileHash | 3da065e07b990034e9db7842167f70b63aa5329 | Available for alerts associated with a file or process. | -> | 11 | Sha256 | deviceCustomString6 | ebf54f745dc81e1958f75e4ca91dd0ab989fc9787bb6b0bf993e2f5 | Available for Windows Defender AV alerts. | -> | 12 | Md5 | deviceCustomString5 | db979c04a99b96d370988325bb5a8b21 | Available for Windows Defender AV alerts. | -> | 13 | ThreatName | deviceCustomString1 | HackTool:Win32/Mikatz!dha | Available for Windows Defender AV alerts. | -> | 14 | IpAddress | sourceAddress | 218.90.204.141 | Available for alerts associated to network events. For example, 'Communication to a malicious network destination'. | -> | 15 | Url | requestUrl | down.esales360.cn | Available for alerts associated to network events. For example, 'Communication to a malicious network destination'. | -> | 16 | RemediationIsSuccess | deviceCustomNumber2 | TRUE | Available for Windows Defender AV alerts. ArcSight value is 1 when TRUE and 0 when FALSE. | -> | 17 | WasExecutingWhileDetected | deviceCustomNumber1 | FALSE | Available for Windows Defender AV alerts. ArcSight value is 1 when TRUE and 0 when FALSE. | -> | 18 | AlertId | externalId | 636210704265059241_673569822 | Value available for every alert. | -> | 19 | LinkToWDATP | flexString1 | `https://securitycenter.windows.com/alert/636210704265059241_673569822` | Value available for every alert. | -> | 20 | AlertTime | deviceReceiptTime | 2017-05-07T01:56:59.3191352Z | The time the activity relevant to the alert occurred. Value available for every alert. | -> | 21 | MachineDomain | sourceDnsDomain | contoso.com | Domain name not relevant for AAD joined machines. Value available for every alert. | +> | 1 | AlertTitle | name | Windows Defender AV detected 'Mikatz' high-severity malware | Value available for every Detection. | +> | 2 | Severity | deviceSeverity | High | Value available for every Detection. | +> | 3 | Category | deviceEventCategory | Malware | Value available for every Detection. | +> | 4 | Detection source | sourceServiceName | Antivirus | Windows Defender Antivirus or Microsoft Defender ATP. Value available for every Detection. | +> | 5 | MachineName | sourceHostName | desktop-4a5ngd6 | Value available for every Detection. | +> | 6 | FileName | fileName | Robocopy.exe | Available for detections associated with a file or process. | +> | 7 | FilePath | filePath | C:\Windows\System32\Robocopy.exe | Available for detections associated with a file or process. | +> | 8 | UserDomain | sourceNtDomain | CONTOSO | The domain of the user context running the activity, available for Microsoft Defender ATP behavioral based detections. | +> | 9 | UserName | sourceUserName | liz.bean | The user context running the activity, available for Microsoft Defender ATP behavioral based detections. | +> | 10 | Sha1 | fileHash | 3da065e07b990034e9db7842167f70b63aa5329 | Available for detections associated with a file or process. | +> | 11 | Sha256 | deviceCustomString6 | ebf54f745dc81e1958f75e4ca91dd0ab989fc9787bb6b0bf993e2f5 | Available for Windows Defender AV detections. | +> | 12 | Md5 | deviceCustomString5 | db979c04a99b96d370988325bb5a8b21 | Available for Windows Defender AV detections. | +> | 13 | ThreatName | deviceCustomString1 | HackTool:Win32/Mikatz!dha | Available for Windows Defender AV detections. | +> | 14 | IpAddress | sourceAddress | 218.90.204.141 | Available for detections associated to network events. For example, 'Communication to a malicious network destination'. | +> | 15 | Url | requestUrl | down.esales360.cn | Available for detections associated to network events. For example, 'Communication to a malicious network destination'. | +> | 16 | RemediationIsSuccess | deviceCustomNumber2 | TRUE | Available for Windows Defender AV detections. ArcSight value is 1 when TRUE and 0 when FALSE. | +> | 17 | WasExecutingWhileDetected | deviceCustomNumber1 | FALSE | Available for Windows Defender AV detections. ArcSight value is 1 when TRUE and 0 when FALSE. | +> | 18 | AlertId | externalId | 636210704265059241_673569822 | Value available for every Detection. | +> | 19 | LinkToWDATP | flexString1 | `https://securitycenter.windows.com/alert/636210704265059241_673569822` | Value available for every Detection. | +> | 20 | AlertTime | deviceReceiptTime | 2017-05-07T01:56:59.3191352Z | The time the event occurred. Value available for every Detection. | +> | 21 | MachineDomain | sourceDnsDomain | contoso.com | Domain name not relevant for AAD joined machines. Value available for every Detection. | > | 22 | Actor | deviceCustomString4 | BORON | Available for alerts related to a known actor group. | -> | 21+5 | ComputerDnsName | No mapping | liz-bean.contoso.com | The machine fully qualified domain name. Value available for every alert. | +> | 21+5 | ComputerDnsName | No mapping | liz-bean.contoso.com | The machine fully qualified domain name. Value available for every Detection. | > | | LogOnUsers | sourceUserId | contoso\liz-bean; contoso\jay-hardee | The domain and user of the interactive logon user/s at the time of the event. Note: For machines on Windows 10 version 1607, the domain information will not be available. | > | | InternalIPv4List | No mapping | 192.168.1.7, 10.1.14.1 | List of IPV4 internal IPs for active network interfaces. | > | | InternalIPv6List | No mapping | fd30:0000:0000:0001:ff4e:003e:0009:000e, FE80:CD00:0000:0CDE:1257:0000:211E:729C | List of IPV6 internal IPs for active network interfaces. | -> | Internal field | LastProcessedTimeUtc | No mapping | 2017-05-07T01:56:58.9936648Z | Time when event arrived at the backend. This field can be used when setting the request parameter for the range of time that alerts are retrieved. | +> | Internal field | LastProcessedTimeUtc | No mapping | 2017-05-07T01:56:58.9936648Z | Time when event arrived at the backend. This field can be used when setting the request parameter for the range of time that detections are retrieved. | > | | Not part of the schema | deviceVendor | | Static value in the ArcSight mapping - 'Microsoft'. | > | | Not part of the schema | deviceProduct | | Static value in the ArcSight mapping - 'Microsoft Defender ATP'. | > | | Not part of the schema | deviceVersion | | Static value in the ArcSight mapping - '2.0', used to identify the mapping versions. @@ -88,7 +91,7 @@ Field numbers match the numbers in the images below. ## Related topics - [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md) -- [Configure Splunk to pull Microsoft Defender ATP alerts](configure-splunk.md) -- [Configure ArcSight to pull Microsoft Defender ATP alerts](configure-arcsight.md) -- [Pull Microsoft Defender ATP alerts using REST API](pull-alerts-using-rest-api.md) +- [Configure Splunk to pull Microsoft Defender ATP detections](configure-splunk.md) +- [Configure ArcSight to pull Microsoft Defender ATP detections](configure-arcsight.md) +- [Pull Microsoft Defender ATP detections using REST API](pull-alerts-using-rest-api.md) - [Troubleshoot SIEM tool integration issues](troubleshoot-siem.md) diff --git a/windows/security/threat-protection/microsoft-defender-atp/configure-arcsight.md b/windows/security/threat-protection/microsoft-defender-atp/configure-arcsight.md index 22c9359f44..736e5fc809 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/configure-arcsight.md +++ b/windows/security/threat-protection/microsoft-defender-atp/configure-arcsight.md @@ -1,6 +1,6 @@ --- -title: Configure HP ArcSight to pull Microsoft Defender ATP alerts -description: Configure HP ArcSight to receive and pull alerts from Microsoft Defender Security Center +title: Configure HP ArcSight to pull Microsoft Defender ATP detections +description: Configure HP ArcSight to receive and pull detections from Microsoft Defender Security Center keywords: configure hp arcsight, security information and events management tools, arcsight search.product: eADQiWindows 10XVcnh search.appverid: met150 @@ -15,10 +15,9 @@ manager: dansimp audience: ITPro ms.collection: M365-security-compliance ms.topic: article -ms.date: 12/20/2018 --- -# Configure HP ArcSight to pull Microsoft Defender ATP alerts +# Configure HP ArcSight to pull Microsoft Defender ATP detections **Applies to:** @@ -29,10 +28,14 @@ ms.date: 12/20/2018 >Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-configurearcsight-abovefoldlink) -You'll need to install and configure some files and tools to use HP ArcSight so that it can pull Microsoft Defender ATP alerts. +You'll need to install and configure some files and tools to use HP ArcSight so that it can pull Microsoft Defender ATP detections. + +>[!Note] +>- [Microsoft Defender ATP Alert](alerts.md) is composed from one or more detections +>- [Microsoft Defender ATP Detection](api-portal-mapping.md) is composed from the suspicious event occurred on the Machine and its related Alert details. ## Before you begin -Configuring the HP ArcSight Connector tool requires several configuration files for it to pull and parse alerts from your Azure Active Directory (AAD) application. +Configuring the HP ArcSight Connector tool requires several configuration files for it to pull and parse detections from your Azure Active Directory (AAD) application. This section guides you in getting the necessary information to set and use the required configuration files correctly. @@ -163,7 +166,7 @@ The following steps assume that you have completed all the required steps in [Be You can now run queries in the HP ArcSight console. -Microsoft Defender ATP alerts will appear as discrete events, with "Microsoft” as the vendor and “Windows Defender ATP” as the device name. +Microsoft Defender ATP detections will appear as discrete events, with "Microsoft” as the vendor and “Windows Defender ATP” as the device name. ## Troubleshooting HP ArcSight connection @@ -187,6 +190,6 @@ Microsoft Defender ATP alerts will appear as discrete events, with "Microsoft” ## Related topics - [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md) -- [Configure Splunk to pull Microsoft Defender ATP alerts](configure-splunk.md) -- [Pull Microsoft Defender ATP alerts using REST API](pull-alerts-using-rest-api.md) +- [Configure Splunk to pull Microsoft Defender ATP detections](configure-splunk.md) +- [Pull Microsoft Defender ATP detections using REST API](pull-alerts-using-rest-api.md) - [Troubleshoot SIEM tool integration issues](troubleshoot-siem.md) diff --git a/windows/security/threat-protection/microsoft-defender-atp/configure-siem.md b/windows/security/threat-protection/microsoft-defender-atp/configure-siem.md index c5e8719018..89fb09887a 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/configure-siem.md +++ b/windows/security/threat-protection/microsoft-defender-atp/configure-siem.md @@ -1,6 +1,6 @@ --- -title: Pull alerts to your SIEM tools from Microsoft Defender Advanced Threat Protection -description: Learn how to use REST API and configure supported security information and events management tools to receive and pull alerts. +title: Pull detections to your SIEM tools from Microsoft Defender Advanced Threat Protection +description: Learn how to use REST API and configure supported security information and events management tools to receive and pull detections. keywords: configure siem, security information and events management tools, splunk, arcsight, custom indicators, rest api, alert definitions, indicators of compromise search.product: eADQiWindows 10XVcnh search.appverid: met150 @@ -18,7 +18,7 @@ ms.topic: article ms.date: 10/16/2017 --- -# Pull alerts to your SIEM tools +# Pull detections to your SIEM tools **Applies to:** @@ -26,8 +26,13 @@ ms.date: 10/16/2017 >Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-configuresiem-abovefoldlink) -## Pull alerts using security information and events management (SIEM) tools -Microsoft Defender ATP supports (SIEM) tools to pull alerts. Microsoft Defender ATP exposes alerts through an HTTPS endpoint hosted in Azure. The endpoint can be configured to pull alerts from your enterprise tenant in Azure Active Directory (AAD) using the OAuth 2.0 authentication protocol for an AAD application that represents the specific SIEM connector installed in your environment. +## Pull detections using security information and events management (SIEM) tools + +>[!Note] +>- [Microsoft Defender ATP Alert](alerts.md) is composed from one or more detections +>- [Microsoft Defender ATP Detection](api-portal-mapping.md) is composed from the suspicious event occurred on the Machine and its related Alert details. + +Microsoft Defender ATP supports (SIEM) tools to pull detections. Microsoft Defender ATP exposes alerts through an HTTPS endpoint hosted in Azure. The endpoint can be configured to pull detections from your enterprise tenant in Azure Active Directory (AAD) using the OAuth 2.0 authentication protocol for an AAD application that represents the specific SIEM connector installed in your environment. Microsoft Defender ATP currently supports the following SIEM tools: @@ -39,16 +44,16 @@ To use either of these supported SIEM tools you'll need to: - [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md) - Configure the supported SIEM tool: - - [Configure Splunk to pull Microsoft Defender ATP alerts](configure-splunk.md) - - [Configure HP ArcSight to pull Microsoft Defender ATP alerts](configure-arcsight.md) + - [Configure Splunk to pull Microsoft Defender ATP detections](configure-splunk.md) + - [Configure HP ArcSight to pull Microsoft Defender ATP detections](configure-arcsight.md) -For more information on the list of fields exposed in the alerts API see, [Microsoft Defender ATP alert API fields](api-portal-mapping.md). +For more information on the list of fields exposed in the Detection API see, [Microsoft Defender ATP Detection fields](api-portal-mapping.md). -## Pull Microsoft Defender ATP alerts using REST API -Microsoft Defender ATP supports the OAuth 2.0 protocol to pull alerts using REST API. +## Pull Microsoft Defender ATP detections using REST API +Microsoft Defender ATP supports the OAuth 2.0 protocol to pull detections using REST API. -For more information, see [Pull Microsoft Defender ATP alerts using REST API](pull-alerts-using-rest-api.md). +For more information, see [Pull Microsoft Defender ATP detections using REST API](pull-alerts-using-rest-api.md). ## In this section @@ -56,8 +61,8 @@ For more information, see [Pull Microsoft Defender ATP alerts using REST API](pu Topic | Description :---|:--- [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md)| Learn about enabling the SIEM integration feature in the **Settings** page in the portal so that you can use and generate the required information to configure supported SIEM tools. -[Configure Splunk to pull Microsoft Defender ATP alerts](configure-splunk.md)| Learn about installing the REST API Modular Input app and other configuration settings to enable Splunk to pull Microsoft Defender ATP alerts. -[Configure HP ArcSight to pull Microsoft Defender ATP alerts](configure-arcsight.md)| Learn about installing the HP ArcSight REST FlexConnector package and the files you need to configure ArcSight to pull Microsoft Defender ATP alerts. -[Microsoft Defender ATP alert API fields](api-portal-mapping.md) | Understand what data fields are exposed as part of the alerts API and how they map to Microsoft Defender Security Center. -[Pull Microsoft Defender ATP alerts using REST API](pull-alerts-using-rest-api.md) | Use the Client credentials OAuth 2.0 flow to pull alerts from Microsoft Defender ATP using REST API. +[Configure Splunk to pull Microsoft Defender ATP detections](configure-splunk.md)| Learn about installing the REST API Modular Input App and other configuration settings to enable Splunk to pull Microsoft Defender ATP detections. +[Configure HP ArcSight to pull Microsoft Defender ATP detections](configure-arcsight.md)| Learn about installing the HP ArcSight REST FlexConnector package and the files you need to configure ArcSight to pull Microsoft Defender ATP detections. +[Microsoft Defender ATP Detection fields](api-portal-mapping.md) | Understand what data fields are exposed as part of the alerts API and how they map to Microsoft Defender Security Center. +[Pull Microsoft Defender ATP detections using REST API](pull-alerts-using-rest-api.md) | Use the Client credentials OAuth 2.0 flow to pull detections from Microsoft Defender ATP using REST API. [Troubleshoot SIEM tool integration issues](troubleshoot-siem.md) | Address issues you might encounter when using the SIEM integration feature. diff --git a/windows/security/threat-protection/microsoft-defender-atp/configure-splunk.md b/windows/security/threat-protection/microsoft-defender-atp/configure-splunk.md index 13cf662e66..6d0db578d1 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/configure-splunk.md +++ b/windows/security/threat-protection/microsoft-defender-atp/configure-splunk.md @@ -1,6 +1,6 @@ --- -title: Configure Splunk to pull Microsoft Defender ATP alerts -description: Configure Splunk to receive and pull alerts from Microsoft Defender Security Center. +title: Configure Splunk to pull Microsoft Defender ATP detections +description: Configure Splunk to receive and pull detections from Microsoft Defender Security Center. keywords: configure splunk, security information and events management tools, splunk search.product: eADQiWindows 10XVcnh search.appverid: met150 @@ -17,7 +17,7 @@ ms.collection: M365-security-compliance ms.topic: article --- -# Configure Splunk to pull Microsoft Defender ATP alerts +# Configure Splunk to pull Microsoft Defender ATP detections **Applies to:** @@ -28,7 +28,11 @@ ms.topic: article >Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-configuresplunk-abovefoldlink) -You'll need to configure Splunk so that it can pull Microsoft Defender ATP alerts. +You'll need to configure Splunk so that it can pull Microsoft Defender ATP detections. + +>[!Note] +>- [Microsoft Defender ATP Alert](alerts.md) is composed from one or more detections +>- [Microsoft Defender ATP Detection](api-portal-mapping.md) is composed from the suspicious event occurred on the Machine and its related Alert details. ## Before you begin @@ -121,8 +125,8 @@ You'll need to configure Splunk so that it can pull Microsoft Defender ATP alert After completing these configuration steps, you can go to the Splunk dashboard and run queries. -## View alerts using Splunk solution explorer -Use the solution explorer to view alerts in Splunk. +## View detections using Splunk solution explorer +Use the solution explorer to view detections in Splunk. 1. In Splunk, go to **Settings** > **Searchers, reports, and alerts**. @@ -141,12 +145,12 @@ Use the solution explorer to view alerts in Splunk. >[!TIP] -> To mininimize alert duplications, you can use the following query: +> To mininimize Detection duplications, you can use the following query: >```source="rest://windows atp alerts" | spath | dedup _raw | table *``` ## Related topics - [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md) -- [Configure ArcSight to pull Microsoft Defender ATP alerts](configure-arcsight.md) -- [Microsoft Defender ATP alert API fields](api-portal-mapping.md) -- [Pull Microsoft Defender ATP alerts using REST API](pull-alerts-using-rest-api.md) +- [Configure ArcSight to pull Microsoft Defender ATP detections](configure-arcsight.md) +- [Microsoft Defender ATP Detection fields](api-portal-mapping.md) +- [Pull Microsoft Defender ATP detections using REST API](pull-alerts-using-rest-api.md) - [Troubleshoot SIEM tool integration issues](troubleshoot-siem.md) diff --git a/windows/security/threat-protection/microsoft-defender-atp/enable-siem-integration.md b/windows/security/threat-protection/microsoft-defender-atp/enable-siem-integration.md index 2c9fa62654..707f89cea2 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/enable-siem-integration.md +++ b/windows/security/threat-protection/microsoft-defender-atp/enable-siem-integration.md @@ -1,6 +1,6 @@ --- title: Enable SIEM integration in Microsoft Defender ATP -description: Enable SIEM integration to receive alerts in your security information and event management (SIEM) solution. +description: Enable SIEM integration to receive detections in your security information and event management (SIEM) solution. keywords: enable siem connector, siem, connector, security information and events search.product: eADQiWindows 10XVcnh search.appverid: met150 @@ -15,7 +15,6 @@ manager: dansimp audience: ITPro ms.collection: M365-security-compliance ms.topic: article -ms.date: 12/10/2018 --- # Enable SIEM integration in Microsoft Defender ATP @@ -26,7 +25,11 @@ ms.date: 12/10/2018 >Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-enablesiem-abovefoldlink) -Enable security information and event management (SIEM) integration so you can pull alerts from Microsoft Defender Security Center using your SIEM solution or by connecting directly to the alerts REST API. +Enable security information and event management (SIEM) integration so you can pull detections from Microsoft Defender Security Center using your SIEM solution or by connecting directly to the detections REST API. + +>[!Note] +>- [Microsoft Defender ATP Alert](alerts.md) is composed from one or more detections +>- [Microsoft Defender ATP Detection](api-portal-mapping.md) is composed from the suspicious event occurred on the Machine and its related Alert details. ## Prerequisites - The user who activates the setting must have permissions to create an app in Azure Active Directory (AAD). This is typically someone with a **Global administrator** role. @@ -55,7 +58,7 @@ Enable security information and event management (SIEM) integration so you can p > - WDATP-connector.jsonparser.properties > - WDATP-connector.properties
- If you want to connect directly to the alerts REST API through programmatic access, choose **Generic API**. + If you want to connect directly to the detections REST API through programmatic access, choose **Generic API**. 4. Copy the individual values or select **Save details to file** to download a file that contains all the values. @@ -64,14 +67,14 @@ Enable security information and event management (SIEM) integration so you can p > [!NOTE] > You'll need to generate a new Refresh token every 90 days. -You can now proceed with configuring your SIEM solution or connecting to the alerts REST API through programmatic access. You'll need to use the tokens when configuring your SIEM solution to allow it to receive alerts from Microsoft Defender Security Center. +You can now proceed with configuring your SIEM solution or connecting to the detections REST API through programmatic access. You'll need to use the tokens when configuring your SIEM solution to allow it to receive detections from Microsoft Defender Security Center. ## Integrate Microsoft Defender ATP with IBM QRadar -You can configure IBM QRadar to collect alerts from Microsoft Defender ATP. For more information, see [IBM Knowledge Center](https://www.ibm.com/support/knowledgecenter/SS42VS_DSM/c_dsm_guide_MS_Win_Defender_ATP_overview.html?cp=SS42VS_7.3.1). +You can configure IBM QRadar to collect detections from Microsoft Defender ATP. For more information, see [IBM Knowledge Center](https://www.ibm.com/support/knowledgecenter/SS42VS_DSM/c_dsm_guide_MS_Win_Defender_ATP_overview.html?cp=SS42VS_7.3.1). ## Related topics -- [Configure Splunk to pull Microsoft Defender ATP alerts](configure-splunk.md) -- [Configure HP ArcSight to pull Microsoft Defender ATP alerts](configure-arcsight.md) -- [Microsoft Defender ATP alert API fields](api-portal-mapping.md) -- [Pull Microsoft Defender ATP alerts using REST API](pull-alerts-using-rest-api.md) +- [Configure Splunk to pull Microsoft Defender ATP detections](configure-splunk.md) +- [Configure HP ArcSight to pull Microsoft Defender ATP detections](configure-arcsight.md) +- [Microsoft Defender ATP Detection fields](api-portal-mapping.md) +- [Pull Microsoft Defender ATP detections using REST API](pull-alerts-using-rest-api.md) - [Troubleshoot SIEM tool integration issues](troubleshoot-siem.md) diff --git a/windows/security/threat-protection/microsoft-defender-atp/get-ip-related-machines.md b/windows/security/threat-protection/microsoft-defender-atp/get-ip-related-machines.md deleted file mode 100644 index c247c9aa81..0000000000 --- a/windows/security/threat-protection/microsoft-defender-atp/get-ip-related-machines.md +++ /dev/null @@ -1,122 +0,0 @@ ---- -title: Get IP related machines API -description: Retrieves a collection of machines related to a given IP address. -keywords: apis, graph api, supported apis, get, ip, related, machines -search.product: eADQiWindows 10XVcnh -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.pagetype: security -ms.author: macapara -author: mjcaparas -ms.localizationpriority: medium -manager: dansimp -audience: ITPro -ms.collection: M365-security-compliance -ms.topic: article ---- - -# Get IP related machines API (Deprecated) - -**Applies to:** - -- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559) - -Retrieves a collection of machines that communicated with or from a particular IP. - -## Permissions -One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Use Microsoft Defender ATP APIs](apis-intro.md) - -Permission type | Permission | Permission display name -:---|:---|:--- -Application | Machine.Read.All | 'Read all machine profiles' -Application | Machine.ReadWrite.All | 'Read and write all machine information' -Delegated (work or school account) | Machine.Read | 'Read machine information' -Delegated (work or school account) | Machine.ReadWrite | 'Read and write machine information' - ->[!Note] -> When obtaining a token using user credentials: ->- The user needs to have at least the following role permission: 'View Data' (See [Create and manage roles](user-roles.md) for more information) ->- Response will include only machines, that the user have access to, based on machine group settings (See [Create and manage machine groups](machine-groups.md) for more information) - -## HTTP request -``` -GET /api/ips/{ip}/machines -``` - -## Request headers - -Name | Type | Description -:---|:---|:--- -Authorization | String | Bearer {token}. **Required**. - - -## Request body -Empty - -## Response -If successful and IP exists - 200 OK with list of [machine](machine.md) entities in the body. If IP do not exist - 404 Not Found. - - -## Example - -**Request** - -Here is an example of the request. - -[!include[Improve request performance](improve-request-performance.md)] - -``` -GET https://api.securitycenter.windows.com/api/ips/10.209.67.177/machines -``` - -**Response** - -Here is an example of the response. - - -``` -HTTP/1.1 200 OK -Content-type: application/json -{ - "@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Machines", - "value": [ - { - "id": "1e5bc9d7e413ddd7902c2932e418702b84d0cc07", - "computerDnsName": "mymachine1.contoso.com", - "firstSeen": "2018-08-02T14:55:03.7791856Z", - "lastSeen": "2018-08-02T14:55:03.7791856Z", - "osPlatform": "Windows10", - "osVersion": "10.0.0.0", - "lastIpAddress": "172.17.230.209", - "lastExternalIpAddress": "167.220.196.71", - "agentVersion": "10.5830.18209.1001", - "osBuild": 18209, - "healthStatus": "Active", - "rbacGroupId": 140, - "riskScore": "Low", - "rbacGroupName": "The-A-Team", - "aadDeviceId": "80fe8ff8-2624-418e-9591-41f0491218f9", - "machineTags": [ "test tag 1", "test tag 2" ] - }, - { - "id": "7292e4b8cb74ff1cc3d8a495eb29dc8858b732f7", - "computerDnsName": "mymachine2.contoso.com", - "firstSeen": "2018-07-09T13:22:45.1250071Z", - "lastSeen": "2018-07-09T13:22:45.1250071Z", - "osPlatform": "Windows10", - "osVersion": "10.0.0.0", - "lastIpAddress": "192.168.12.225", - "lastExternalIpAddress": "79.183.65.82", - "agentVersion": "10.5820.17724.1000", - "osBuild": 17724, - "healthStatus": "Inactive", - "rbacGroupId": 140, - "rbacGroupName": "The-A-Team", - "riskScore": "Low", - "aadDeviceId": null, - "machineTags": [ "test tag 1" ] - } - ] -} -``` diff --git a/windows/security/threat-protection/microsoft-defender-atp/is-domain-seen-in-org.md b/windows/security/threat-protection/microsoft-defender-atp/is-domain-seen-in-org.md deleted file mode 100644 index 38debbe291..0000000000 --- a/windows/security/threat-protection/microsoft-defender-atp/is-domain-seen-in-org.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Is domain seen in org API -description: Use this API to create calls related to checking whether a domain was seen in the organization. -keywords: apis, graph api, supported apis, domain, domain seen -search.product: eADQiWindows 10XVcnh -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.pagetype: security -ms.author: macapara -author: mjcaparas -ms.localizationpriority: medium -manager: dansimp -audience: ITPro -ms.collection: M365-security-compliance -ms.topic: article ---- - -# Was domain seen in org (Deprecated) - -**Applies to:** - -- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559) - -Answers whether a domain was seen in the organization. - -## Permissions -One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Use Microsoft Defender ATP APIs](apis-intro.md) - -Permission type | Permission | Permission display name -:---|:---|:--- -Application | Url.Read.All | 'Read URLs' -Delegated (work or school account) | URL.Read.All | 'Read URLs' - ->[!Note] -> When obtaining a token using user credentials: ->- The user needs to have at least the following role permission: 'View Data' (See [Create and manage roles](user-roles.md) for more information) - -## HTTP request -``` -GET /api/domains/{domain} -``` - -## Request headers - -Header | Value -:---|:--- -Authorization | Bearer {token}. **Required**. - - -## Request body -Empty - -## Response -If successful and domain exists - 200 OK. If domain does not exist - 404 Not Found. - -## Example - -**Request** - -Here is an example of the request. - -[!include[Improve request performance](improve-request-performance.md)] - -``` -GET https://api.securitycenter.windows.com/api/domains/example.com -Content-type: application/json -``` - -**Response** - -Here is an example of the response. - - -``` -HTTP/1.1 200 OK -Content-type: application/json -{ - "@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Domains/$entity", - "host": "example.com" -} -``` diff --git a/windows/security/threat-protection/microsoft-defender-atp/is-ip-seen-org.md b/windows/security/threat-protection/microsoft-defender-atp/is-ip-seen-org.md deleted file mode 100644 index f112796be2..0000000000 --- a/windows/security/threat-protection/microsoft-defender-atp/is-ip-seen-org.md +++ /dev/null @@ -1,82 +0,0 @@ ---- -title: Is IP seen in org API -description: Answers whether an IP was seen in the organization. -keywords: apis, graph api, supported apis, is, ip, seen, org, organization -search.product: eADQiWindows 10XVcnh -ms.prod: w10 -ms.mktglfcycl: deploy -ms.sitesec: library -ms.pagetype: security -ms.author: macapara -author: mjcaparas -ms.localizationpriority: medium -manager: dansimp -audience: ITPro -ms.collection: M365-security-compliance -ms.topic: article ---- - -# Was IP seen in org (Deprecated) - -**Applies to:** - -- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559) - -Answers whether an IP was seen in the organization. - -## Permissions -One of the following permissions is required to call this API. To learn more, including how to choose permissions, see [Use Microsoft Defender ATP APIs](apis-intro.md) - -Permission type | Permission | Permission display name -:---|:---|:--- -Application | Ip.Read.All | 'Read IP address profiles' -Delegated (work or school account) | Ip.Read.All | 'Read IP address profiles' - ->[!Note] -> When obtaining a token using user credentials: ->- The user needs to have at least the following role permission: 'View Data' (See [Create and manage roles](user-roles.md) for more information) - -## HTTP request -``` -GET /api/ips/{ip} -``` - -## Request headers - -Name | Type | Description -:---|:---|:--- -Authorization | String | Bearer {token}. **Required**. - - -## Request body -Empty - -## Response -If successful and IP exists - 200 OK. If IP do not exist - 404 Not Found. - - -## Example - -**Request** - -Here is an example of the request. - -``` -GET https://api.securitycenter.windows.com/api/ips/10.209.67.177 -``` - -**Response** - -Here is an example of the response. - -[!include[Improve request performance](improve-request-performance.md)] - - -``` -HTTP/1.1 200 OK -Content-type: application/json -{ - "@odata.context": "https://api.securitycenter.windows.com/api/$metadata#Ips/$entity", - "id": "10.209.67.177" -} -``` diff --git a/windows/security/threat-protection/microsoft-defender-atp/management-apis.md b/windows/security/threat-protection/microsoft-defender-atp/management-apis.md index 75f1890d2a..40c4a73464 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/management-apis.md +++ b/windows/security/threat-protection/microsoft-defender-atp/management-apis.md @@ -52,7 +52,6 @@ An important aspect of machine management is the ability to analyze the environm Topic | Description :---|:--- Understand threat intelligence concepts | Learn about alert definitions, indicators of compromise, and other threat intelligence concepts. -Supported Microsoft Defender ATP APIs | Learn more about the individual supported entities where you can run API calls to and details such as HTTP request values, request headers and expected responses. Managed security service provider | Get a quick overview on managed security service provider support. diff --git a/windows/security/threat-protection/microsoft-defender-atp/oldTOC.txt b/windows/security/threat-protection/microsoft-defender-atp/oldTOC.txt index f06995f573..9dd1998f62 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/oldTOC.txt +++ b/windows/security/threat-protection/microsoft-defender-atp/oldTOC.txt @@ -392,7 +392,6 @@ ####### [Get domain related alerts](get-domain-related-alerts.md) ####### [Get domain related machines](get-domain-related-machines.md) ####### [Get domain statistics](get-domain-statistics.md) -####### [Is domain seen in organization (Deprecated)](is-domain-seen-in-org.md) ###### [File]() ####### [Methods and properties](files.md) @@ -403,9 +402,7 @@ ###### [IP]() ####### [Get IP related alerts](get-ip-related-alerts.md) -####### [Get IP related machines (Deprecated)](get-ip-related-machines.md) ####### [Get IP statistics](get-ip-statistics.md) -####### [Is IP seen in organization (Deprecated)](is-ip-seen-org.md) ###### [User]() ####### [Methods](user.md) @@ -428,13 +425,13 @@ ##### [Experiment with custom threat intelligence alerts](experiment-custom-ti.md) ##### [Troubleshoot custom threat intelligence issues](troubleshoot-custom-ti.md) -#### [Pull alerts to your SIEM tools]() -##### [Learn about different ways to pull alerts](configure-siem.md) +#### [Pull Detections to your SIEM tools]() +##### [Learn about different ways to pull Detections](configure-siem.md) ##### [Enable SIEM integration](enable-siem-integration.md) -##### [Configure Splunk to pull alerts](configure-splunk.md) -##### [Configure HP ArcSight to pull alerts](configure-arcsight.md) -##### [Microsoft Defender ATP SIEM alert API fields](api-portal-mapping.md) -##### [Pull alerts using SIEM REST API](pull-alerts-using-rest-api.md) +##### [Configure Splunk to pull Detections](configure-splunk.md) +##### [Configure HP ArcSight to pull Detections](configure-arcsight.md) +##### [Microsoft Defender ATP Detection fields](api-portal-mapping.md) +##### [Pull Detections using SIEM REST API](pull-alerts-using-rest-api.md) ##### [Troubleshoot SIEM tool integration issues](troubleshoot-siem.md) #### [Reporting]() diff --git a/windows/security/threat-protection/microsoft-defender-atp/pull-alerts-using-rest-api.md b/windows/security/threat-protection/microsoft-defender-atp/pull-alerts-using-rest-api.md index abf6c2fb00..c8bd39a230 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/pull-alerts-using-rest-api.md +++ b/windows/security/threat-protection/microsoft-defender-atp/pull-alerts-using-rest-api.md @@ -1,7 +1,7 @@ --- -title: Pull Microsoft Defender ATP alerts using REST API -description: Pull alerts from Microsoft Defender ATP REST API. -keywords: alerts, pull alerts, rest api, request, response +title: Pull Microsoft Defender ATP detections using REST API +description: Pull detections from Microsoft Defender ATP REST API. +keywords: detections, pull detections, rest api, request, response search.product: eADQiWindows 10XVcnh search.appverid: met150 ms.prod: w10 @@ -17,7 +17,7 @@ ms.collection: M365-security-compliance ms.topic: article --- -# Pull Microsoft Defender ATP alerts using SIEM REST API +# Pull Microsoft Defender ATP detections using SIEM REST API **Applies to:** - [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP)](https://go.microsoft.com/fwlink/p/?linkid=2069559) @@ -26,7 +26,11 @@ ms.topic: article >Want to experience Microsoft Defender ATP? [Sign up for a free trial.](https://www.microsoft.com/en-us/WindowsForBusiness/windows-atp?ocid=docs-wdatp-pullalerts-abovefoldlink) -Microsoft Defender ATP supports the OAuth 2.0 protocol to pull alerts from the portal. +>[!Note] +>- [Microsoft Defender ATP Alert](alerts.md) is composed from one or more detections +>- [Microsoft Defender ATP Detection](api-portal-mapping.md) is composed from the suspicious event occurred on the Machine and its related Alert details. + +Microsoft Defender ATP supports the OAuth 2.0 protocol to pull detections from the API. In general, the OAuth 2.0 protocol supports four types of flows: - Authorization grant flow @@ -36,19 +40,19 @@ In general, the OAuth 2.0 protocol supports four types of flows: For more information about the OAuth specifications, see the [OAuth Website](http://www.oauth.net). -Microsoft Defender ATP supports the _Authorization grant flow_ and _Client credential flow_ to obtain access to generate alerts from the portal, with Azure Active Directory (AAD) as the authorization server. +Microsoft Defender ATP supports the _Authorization grant flow_ and _Client credential flow_ to obtain access to pull detections, with Azure Active Directory (AAD) as the authorization server. The _Authorization grant flow_ uses user credentials to get an authorization code, which is then used to obtain an access token. The _Client credential flow_ uses client credentials to authenticate against the Microsoft Defender ATP endpoint URL. This flow is suitable for scenarios when an OAuth client creates requests to an API that doesn't require user credentials. -Use the following method in the Microsoft Defender ATP API to pull alerts in JSON format. +Use the following method in the Microsoft Defender ATP API to pull detections in JSON format. >[!NOTE] >Microsoft Defender Security Center merges similar alert detections into a single alert. This API pulls alert detections in its raw form based on the query parameters you set, enabling you to apply your own grouping and filtering. ## Before you begin -- Before calling the Microsoft Defender ATP endpoint to pull alerts, you'll need to enable the SIEM integration application in Azure Active Directory (AAD). For more information, see [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md). +- Before calling the Microsoft Defender ATP endpoint to pull detections, you'll need to enable the SIEM integration application in Azure Active Directory (AAD). For more information, see [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md). - Take note of the following values in your Azure application registration. You need these values to configure the OAuth flow in your service or daemon app: - Application ID (unique to your application) @@ -59,7 +63,7 @@ Use the following method in the Microsoft Defender ATP API to pull alerts in JSO ## Get an access token Before creating calls to the endpoint, you'll need to get an access token. -You'll use the access token to access the protected resource, which are alerts in Microsoft Defender ATP. +You'll use the access token to access the protected resource, which are detections in Microsoft Defender ATP. To get an access token, you'll need to do a POST request to the token issuing endpoint. Here is a sample request: @@ -105,23 +109,23 @@ Use optional query parameters to specify and control the amount of data returned Name | Value| Description :---|:---|:--- -DateTime?sinceTimeUtc | string | Defines the lower time bound alerts are retrieved from, based on field:
`LastProcessedTimeUtc`
The time range will be: from sinceTimeUtc time to current time.

**NOTE**: When not specified, all alerts generated in the last two hours are retrieved. -DateTime?untilTimeUtc | string | Defines the upper time bound alerts are retrieved.
The time range will be: from `sinceTimeUtc` time to `untilTimeUtc` time.

**NOTE**: When not specified, the default value will be the current time. -string ago | string | Pulls alerts in the following time range: from `(current_time - ago)` time to `current_time` time.

Value should be set according to **ISO 8601** duration format
E.g. `ago=PT10M` will pull alerts received in the last 10 minutes. -int?limit | int | Defines the number of alerts to be retrieved. Most recent alerts will be retrieved based on the number defined.

**NOTE**: When not specified, all alerts available in the time range will be retrieved. -machinegroups | String | Specifies machine groups to pull alerts from.

**NOTE**: When not specified, alerts from all machine groups will be retrieved.

Example:

```https://wdatp-alertexporter-eu.securitycenter.windows.com/api/Alerts/?machinegroups=UKMachines&machinegroups=FranceMachines``` +DateTime?sinceTimeUtc | string | Defines the lower time bound detections are retrieved from, based on field:
`LastProcessedTimeUtc`
The time range will be: from sinceTimeUtc time to current time.

**NOTE**: When not specified, all detections generated in the last two hours are retrieved. +DateTime?untilTimeUtc | string | Defines the upper time bound detections are retrieved.
The time range will be: from `sinceTimeUtc` time to `untilTimeUtc` time.

**NOTE**: When not specified, the default value will be the current time. +string ago | string | Pulls detections in the following time range: from `(current_time - ago)` time to `current_time` time.

Value should be set according to **ISO 8601** duration format
E.g. `ago=PT10M` will pull detections received in the last 10 minutes. +int?limit | int | Defines the number of detections to be retrieved. Most recent detections will be retrieved based on the number defined.

**NOTE**: When not specified, all detections available in the time range will be retrieved. +machinegroups | String | Specifies machine groups to pull detections from.

**NOTE**: When not specified, detections from all machine groups will be retrieved.

Example:

```https://wdatp-alertexporter-eu.securitycenter.windows.com/api/Alerts/?machinegroups=UKMachines&machinegroups=FranceMachines``` DeviceCreatedMachineTags | string | Single machine tag from the registry. CloudCreatedMachineTags | string | Machine tags that were created in Microsoft Defender Security Center. ### Request example -The following example demonstrates how to retrieve all the alerts in your organization. +The following example demonstrates how to retrieve all the detections in your organization. ```syntax GET https://wdatp-alertexporter-eu.windows.com/api/alerts Authorization: Bearer ``` -The following example demonstrates a request to get the last 20 alerts since 2016-09-12 00:00:00. +The following example demonstrates a request to get the last 20 detections since 2016-09-12 00:00:00. ```syntax GET https://wdatp-alertexporter-eu.windows.com/api/alerts?limit=20&sinceTimeUtc=2016-09-12T00:00:00.000 @@ -178,14 +182,14 @@ AuthenticationContext context = new AuthenticationContext(string.Format("https:/ ClientCredential clientCredentials = new ClientCredential(clientId, clientSecret); AuthenticationResult authenticationResult = context.AcquireToken(resource, clientCredentials); ``` -### Use token to connect to the alerts endpoint +### Use token to connect to the detections endpoint ``` HttpClient httpClient = new HttpClient(); httpClient.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue(authenticationResult.AccessTokenType, authenticationResult.AccessToken); HttpResponseMessage response = httpClient.GetAsync("https://wdatp-alertexporter-eu.windows.com/api/alert").GetAwaiter().GetResult(); -string alertsJson = response.Content.ReadAsStringAsync().Result; -Console.WriteLine("Got alert list: {0}", alertsJson); +string detectionsJson = response.Content.ReadAsStringAsync().Result; +Console.WriteLine("Got detections list: {0}", detectionsJson); ``` @@ -203,7 +207,7 @@ HTTP error code | Description ## Related topics - [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md) -- [Configure ArcSight to pull Microsoft Defender ATP alerts](configure-arcsight.md) -- [Configure Splunk to pull Microsoft Defender ATP alerts](configure-splunk.md) -- [Microsoft Defender ATP alert API fields](api-portal-mapping.md) +- [Configure ArcSight to pull Microsoft Defender ATP detections](configure-arcsight.md) +- [Configure Splunk to pull Microsoft Defender ATP detections](configure-splunk.md) +- [Microsoft Defender ATP Detection fields](api-portal-mapping.md) - [Troubleshoot SIEM tool integration issues](troubleshoot-siem.md) diff --git a/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-siem.md b/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-siem.md index c45bc362d2..e6d27968c0 100644 --- a/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-siem.md +++ b/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-siem.md @@ -25,7 +25,7 @@ ms.topic: troubleshooting -You might need to troubleshoot issues while pulling alerts in your SIEM tools. +You might need to troubleshoot issues while pulling detections in your SIEM tools. This page provides detailed steps to troubleshoot issues you might encounter. @@ -80,7 +80,7 @@ If you encounter an error when trying to enable the SIEM connector application, ## Related topics - [Enable SIEM integration in Microsoft Defender ATP](enable-siem-integration.md) -- [Configure ArcSight to pull Microsoft Defender ATP alerts](configure-arcsight.md) -- [Configure Splunk to pull Microsoft Defender ATP alerts](configure-splunk.md) -- [Microsoft Defender ATP alert API fields](api-portal-mapping.md) -- [Pull Microsoft Defender ATP alerts using REST API](pull-alerts-using-rest-api.md) +- [Configure ArcSight to pull Microsoft Defender ATP detections](configure-arcsight.md) +- [Configure Splunk to pull Microsoft Defender ATP detections](configure-splunk.md) +- [Microsoft Defender ATP Detection fields](api-portal-mapping.md) +- [Pull Microsoft Defender ATP detections using REST API](pull-alerts-using-rest-api.md) From 5b96a119d9bff60076b32884643cfca4fcd5f227 Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Fri, 6 Sep 2019 18:40:31 -0700 Subject: [PATCH 8/9] CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20190906173611 (#1061) (#1062) --- .../resolved-issues-windows-10-1607.yml | 6 +++--- .../resolved-issues-windows-10-1703.yml | 6 +++--- .../resolved-issues-windows-10-1709.yml | 6 +++--- .../resolved-issues-windows-10-1803.yml | 6 +++--- ...-issues-windows-10-1809-and-windows-server-2019.yml | 6 +++--- .../resolved-issues-windows-10-1903.yml | 10 +++++----- .../status-windows-10-1607-and-windows-server-2016.yml | 6 +++--- windows/release-information/status-windows-10-1703.yml | 6 +++--- windows/release-information/status-windows-10-1709.yml | 6 +++--- windows/release-information/status-windows-10-1803.yml | 6 +++--- .../status-windows-10-1809-and-windows-server-2019.yml | 6 +++--- windows/release-information/status-windows-10-1903.yml | 10 +++++----- 12 files changed, 40 insertions(+), 40 deletions(-) diff --git a/windows/release-information/resolved-issues-windows-10-1607.yml b/windows/release-information/resolved-issues-windows-10-1607.yml index 08b49123c4..6f92dbe2b1 100644 --- a/windows/release-information/resolved-issues-windows-10-1607.yml +++ b/windows/release-information/resolved-issues-windows-10-1607.yml @@ -32,9 +32,9 @@ sections: - type: markdown text: " + - @@ -80,9 +80,9 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate resolved
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		August 13, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 14393.3144

August 13, 2019
KB4512517		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		August 13, 2019
10:00 AM PT
Internet Explorer 11 and apps using the WebBrowser control may fail to render
JavaScript may fail to render as expected in Internet Explorer 11 and in apps using JavaScript or the WebBrowser control.

See details >		OS Build 14393.3085

July 09, 2019
KB4507460		Resolved
KB4512517		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved External
August 09, 2019
07:03 PM PT
SCVMM cannot enumerate and manage logical switches deployed on the host
For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host.

See details >		OS Build 14393.2639

November 27, 2018
KB4467684		Resolved
KB4507459		July 16, 2019
10:00 AM PT
+ -
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507459. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512517 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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 KB4503267 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 KB4512495.

Back to top		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved
KB4512495		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507459. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512517. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Internet Explorer 11 and apps using the WebBrowser control may fail to render
Internet Explorer 11 may fail to render some JavaScript after installing KB4507460. You may also have issues with apps using JavaScript or the WebBrowser control, such as the present PowerPoint feature of Skype Meeting Broadcast.

Affected platforms:
  • Client: Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server 2016
Resolution: This issue was resolved in KB4512517.

Back to top		OS Build 14393.3085

July 09, 2019
KB4507460		Resolved
KB4512517		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 26, 2019
04:58 PM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1703.yml b/windows/release-information/resolved-issues-windows-10-1703.yml index 22ddb295df..582aec0f1a 100644 --- a/windows/release-information/resolved-issues-windows-10-1703.yml +++ b/windows/release-information/resolved-issues-windows-10-1703.yml @@ -32,8 +32,8 @@ sections: - type: markdown text: " + - @@ -71,8 +71,8 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate resolved
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 15063.1955

July 16, 2019
KB4507467		Resolved
KB4512507		August 13, 2019
10:00 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 15063.1988

August 13, 2019
KB4512507		Resolved
KB4512474		August 17, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 15063.1955

July 16, 2019
KB4507467		Resolved
KB4512507		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 15063.1868

June 11, 2019
KB4503279		Resolved External
August 09, 2019
07:03 PM PT
Devices with Hyper-V enabled may receive BitLocker error 0xC0210000
Some devices with Hyper-V enabled may start into BitLocker recovery with error 0xC0210000.

See details >		OS Build 15063.1805

May 14, 2019
KB4499181		Resolved
KB4507450		July 09, 2019
10:00 AM PT
Difficulty connecting to some iSCSI-based SANs
Devices may have difficulty connecting to some Storage Area Network (SAN) devices that leverage iSCSI.

See details >		OS Build 15063.1839

May 28, 2019
KB4499162		Resolved
KB4509476		June 26, 2019
04:00 PM PT
- +
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507467. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512507. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 15063.1955

July 16, 2019
KB4507467		Resolved
KB4512507		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507467. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512507 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 15063.1955

July 16, 2019
KB4507467		Resolved
KB4512507		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1709.yml b/windows/release-information/resolved-issues-windows-10-1709.yml index 9bf77f7d45..0cdbe87fcb 100644 --- a/windows/release-information/resolved-issues-windows-10-1709.yml +++ b/windows/release-information/resolved-issues-windows-10-1709.yml @@ -32,9 +32,9 @@ sections: - type: markdown text: " + - @@ -73,9 +73,9 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate resolved
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		August 13, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved
KB4512494		August 16, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 16299.1331

August 13, 2019
KB4512516		Resolved
KB4512494		August 16, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved External
August 09, 2019
07:03 PM PT
Difficulty connecting to some iSCSI-based SANs
Devices may have difficulty connecting to some Storage Area Network (SAN) devices that leverage iSCSI.

See details >		OS Build 16299.1182

May 28, 2019
KB4499147		Resolved
KB4509477		June 26, 2019
04:00 PM PT
Event Viewer may close or you may receive an error when using Custom Views
When trying to expand, view or create Custom Views in Event Viewer, you may receive an error and the app may stop responding or close.

See details >		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved
KB4503281		June 18, 2019
02:00 PM PT
+ -
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507465. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512516 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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 KB4503284 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 KB4512494.

Back to top		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved
KB4512494		Resolved:
August 16, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507465. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512516. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1803.yml b/windows/release-information/resolved-issues-windows-10-1803.yml index f6b4c85fb6..174aa6ebe6 100644 --- a/windows/release-information/resolved-issues-windows-10-1803.yml +++ b/windows/release-information/resolved-issues-windows-10-1803.yml @@ -32,10 +32,10 @@ sections: - type: markdown text: " + - @@ -83,9 +83,9 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate resolved
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		August 13, 2019
10:00 AM 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 Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17134.950

August 13, 2019
KB4512501		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved External
August 09, 2019
07:03 PM PT
Difficulty connecting to some iSCSI-based SANs
Devices may have difficulty connecting to some Storage Area Network (SAN) devices that leverage iSCSI.

See details >		OS Build 17134.799

May 21, 2019
KB4499183		Resolved
KB4509478		June 26, 2019
04:00 PM PT
Event Viewer may close or you may receive an error when using Custom Views
When trying to expand, view or create Custom Views in Event Viewer, you may receive an error and the app may stop responding or close.

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved
KB4503288		June 18, 2019
02:00 PM PT
+ -
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507466. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512501 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507466. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512501. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml index 99b8f5966a..81e2a0f077 100644 --- a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml +++ b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml @@ -32,9 +32,9 @@ sections: - type: markdown text: " + - @@ -82,9 +82,9 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate resolved
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		August 13, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Resolved
KB4512534		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17763.678

August 13, 2019
KB4511553		Resolved
KB4512534		August 17, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Resolved External
August 09, 2019
07:03 PM PT
Difficulty connecting to some iSCSI-based SANs
Devices may have difficulty connecting to some Storage Area Network (SAN) devices that leverage iSCSI.

See details >		OS Build 17763.529

May 21, 2019
KB4497934		Resolved
KB4509479		June 26, 2019
04:00 PM PT
Devices with Realtek Bluetooth radios drivers may not pair or connect as expected
Devices with some Realtek Bluetooth radios drivers, in some circumstances, may have issues pairing or connecting to devices.

See details >		OS Build 17763.503

May 14, 2019
KB4494441		Resolved
KB4501371		June 18, 2019
02:00 PM PT
+ -
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4505658. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4511553 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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 KB4503327 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 KB4512534.

Back to top		OS Build 17763.557

June 11, 2019
KB4503327		Resolved
KB4512534		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4505658. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4511553. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1903.yml b/windows/release-information/resolved-issues-windows-10-1903.yml index e3349d1356..56fb3d90af 100644 --- a/windows/release-information/resolved-issues-windows-10-1903.yml +++ b/windows/release-information/resolved-issues-windows-10-1903.yml @@ -32,12 +32,12 @@ sections: - type: markdown text: " + + - - @@ -74,11 +74,11 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate resolved
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Issues updating when certain versions of Intel storage drivers are installed
Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Issues updating when certain versions of Intel storage drivers are installed
Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Resolved
KB4512941		August 30, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
August 09, 2019
07:03 PM PT
Display brightness may not respond to adjustments
Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Resolved
KB4505903		July 26, 2019
02:00 PM PT
RASMAN service may stop working and result in the error “0xc0000005”
The Remote Access Connection Manager (RASMAN) service may stop working and result in the error “0xc0000005” with VPN profiles configured as an Always On VPN connection.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4505903		July 26, 2019
02:00 PM PT
- + + -
DetailsOriginating updateStatusHistory
Issues updating when certain versions of Intel storage drivers are installed
Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903).  

To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated.

Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Workaround: To mitigate this issue before the safeguard hold is removed, you will need to update the Intel RST drivers for your device to version 15.5.2.1054 or a later.  Check with your device manufacturer (OEM) to see if an updated driver is available and install it. You can also download the latest Intel RST drivers directly from Intel at Intel® Rapid Storage Technology (Intel® RST) User Interface and Driver. Once your drivers are updated, you can restart the installation process for Windows 10, version 1903. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903.

Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512941 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Issues updating when certain versions of Intel storage drivers are installed
Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903).  

To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated.

Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Resolution: This issue was resolved in KB4512941 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU).

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

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 12, 2019
04:42 PM PT
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 KB4503293 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 KB4512941.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
" diff --git a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml index fb76299a24..da23159b5b 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,9 +60,9 @@ 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.

+ - @@ -95,9 +95,9 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		August 13, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 14393.3144

August 13, 2019
KB4512517		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		August 13, 2019
10:00 AM PT
Internet Explorer 11 and apps using the WebBrowser control may fail to render
JavaScript may fail to render as expected in Internet Explorer 11 and in apps using JavaScript or the WebBrowser control.

See details >		OS Build 14393.3085

July 09, 2019
KB4507460		Resolved
KB4512517		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved External
August 09, 2019
07:03 PM PT
Apps and scripts using the NetQueryDisplayInformation API may fail with error
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data.

See details >		OS Build 14393.3053

June 18, 2019
KB4503294		Investigating
August 01, 2019
05:00 PM PT
+ -
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507459. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512517 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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 KB4503267 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 KB4512495.

Back to top		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved
KB4512495		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507459. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512517. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Internet Explorer 11 and apps using the WebBrowser control may fail to render
Internet Explorer 11 may fail to render some JavaScript after installing KB4507460. You may also have issues with apps using JavaScript or the WebBrowser control, such as the present PowerPoint feature of Skype Meeting Broadcast.

Affected platforms:
  • Client: Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
  • Server: Windows Server 2016
Resolution: This issue was resolved in KB4512517.

Back to top		OS Build 14393.3085

July 09, 2019
KB4507460		Resolved
KB4512517		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 26, 2019
04:58 PM PT
" diff --git a/windows/release-information/status-windows-10-1703.yml b/windows/release-information/status-windows-10-1703.yml index dbe7b4e91e..804da5f5fe 100644 --- a/windows/release-information/status-windows-10-1703.yml +++ b/windows/release-information/status-windows-10-1703.yml @@ -66,8 +66,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
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 15063.1955

July 16, 2019
KB4507467		Resolved
KB4512507		August 13, 2019
10:00 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 15063.1988

August 13, 2019
KB4512507		Resolved
KB4512474		August 17, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 15063.1955

July 16, 2019
KB4507467		Resolved
KB4512507		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 15063.1868

June 11, 2019
KB4503279		Resolved External
August 09, 2019
07:03 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

See details >		OS Build 15063.1563

January 08, 2019
KB4480973		Mitigated
April 25, 2019
02:00 PM PT
@@ -95,8 +95,8 @@ sections: - type: markdown text: " - +
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507467. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512507. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 15063.1955

July 16, 2019
KB4507467		Resolved
KB4512507		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507467. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512507 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 15063.1955

July 16, 2019
KB4507467		Resolved
KB4512507		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
" diff --git a/windows/release-information/status-windows-10-1709.yml b/windows/release-information/status-windows-10-1709.yml index 9fa8392574..27e013f10f 100644 --- a/windows/release-information/status-windows-10-1709.yml +++ b/windows/release-information/status-windows-10-1709.yml @@ -60,9 +60,9 @@ 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
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		August 13, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved
KB4512494		August 16, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 16299.1331

August 13, 2019
KB4512516		Resolved
KB4512494		August 16, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved External
August 09, 2019
07:03 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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
@@ -90,9 +90,9 @@ sections: - type: markdown text: " + -
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507465. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512516 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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 KB4503284 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 KB4512494.

Back to top		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved
KB4512494		Resolved:
August 16, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507465. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512516. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 16299.1296

July 16, 2019
KB4507465		Resolved
KB4512516		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
" diff --git a/windows/release-information/status-windows-10-1803.yml b/windows/release-information/status-windows-10-1803.yml index fe3c6577c2..5b3d8b4dd9 100644 --- a/windows/release-information/status-windows-10-1803.yml +++ b/windows/release-information/status-windows-10-1803.yml @@ -65,10 +65,10 @@ 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.

+ - @@ -106,9 +106,9 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		August 13, 2019
10:00 AM 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 Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17134.950

August 13, 2019
KB4512501		Resolved
KB4512509		August 19, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Resolved External
August 09, 2019
07:03 PM PT
Startup to a black screen after installing updates
Your device may startup to a black screen during the first logon after installing updates.

See details >		OS Build 17134.829

June 11, 2019
KB4503286		Mitigated
June 14, 2019
04:41 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507466. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512501 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4507466. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512501. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 17134.915

July 16, 2019
KB4507466		Resolved
KB4512501		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM 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 5a2c3b8df0..d85effd748 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,9 +64,9 @@ 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.

+ - @@ -98,9 +98,9 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		August 13, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Resolved
KB4512534		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 17763.678

August 13, 2019
KB4511553		Resolved
KB4512534		August 17, 2019
02:00 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Resolved External
August 09, 2019
07:03 PM PT
Apps and scripts using the NetQueryDisplayInformation API may fail with error
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data.

See details >		OS Build 17763.55

October 09, 2018
KB4464330		Investigating
August 01, 2019
05:00 PM PT
Startup to a black screen after installing updates
Your device may startup to a black screen during the first logon after installing updates.

See details >		OS Build 17763.557

June 11, 2019
KB4503327		Mitigated
June 14, 2019
04:41 PM PT
+ -
DetailsOriginating updateStatusHistory
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4505658. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4511553 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
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 KB4503327 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 KB4512534.

Back to top		OS Build 17763.557

June 11, 2019
KB4503327		Resolved
KB4512534		Resolved:
August 17, 2019
02:00 PM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4505658. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4511553. To safeguard your upgrade experience, the compatibility hold on devices from being offered Windows 10, version 1903 or Windows Server, version 1903 is still in place. Once the issue is addressed on Windows 10, version 1903, this safeguard hold will be removed for all affected platforms. Check the Windows 10, version 1903 section of the release information dashboard for the most up to date information on this and other safeguard holds.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Back to top		OS Build 17763.652

July 22, 2019
KB4505658		Resolved
KB4511553		Resolved:
August 13, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
" diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index 9201d1cb20..efe7452abd 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -65,13 +65,13 @@ 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.

+ + - - @@ -115,11 +115,11 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Issues updating when certain versions of Intel storage drivers are installed
Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Windows Desktop Search may not return any results and may have high CPU usage
Windows Desktop Search may not return any results and SearchUI.exe may have high CPU usage after installing KB4512941.

See details >		OS Build 18362.329

August 30, 2019
KB4512941		Investigating
September 04, 2019
02:25 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Issues updating when certain versions of Intel storage drivers are installed
Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Resolved
KB4512941		August 30, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive an error, \"Updates Failed, There were problems installing some updates, but we'll try again later\" and \"Error 0x80073701.\"

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 16, 2019
04:28 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
August 09, 2019
07:03 PM PT
Intermittent loss of Wi-Fi connectivity
Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated External
August 01, 2019
08:44 PM PT
- + + -
DetailsOriginating updateStatusHistory
Issues updating when certain versions of Intel storage drivers are installed
Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903).  

To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated.

Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Workaround: To mitigate this issue before the safeguard hold is removed, you will need to update the Intel RST drivers for your device to version 15.5.2.1054 or a later.  Check with your device manufacturer (OEM) to see if an updated driver is available and install it. You can also download the latest Intel RST drivers directly from Intel at Intel® Rapid Storage Technology (Intel® RST) User Interface and Driver. Once your drivers are updated, you can restart the installation process for Windows 10, version 1903. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903.

Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
+

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512941 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to offered Windows 10, version 1903 or Windows Server, version 1903.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Issues updating when certain versions of Intel storage drivers are installed
Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903).  

To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated.

Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Resolution: This issue was resolved in KB4512941 and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU).

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

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 12, 2019
04:42 PM PT
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 KB4503293 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 KB4512941.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 10, 2019
02:51 PM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected.

To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903.

Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists:
HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms
-

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
  • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016
Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
July 25, 2019
06:10 PM PT
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU
Microsoft has identified a compatibility issue on some Surface Book 2 devices configured with Nvidia discrete graphics processing unit (dGPU). After updating to Windows 10, version 1903 (May 2019 Feature Update), some apps or games that needs to perform graphics intensive operations may close or fail to open.

To safeguard your update experience, we have applied a compatibility hold on Surface Book 2 devices with Nvidia dGPUs from being offered Windows 10, version 1903, until this issue is resolved.

Affected platforms:
  • Client: Windows 10, version 1903
Workaround: To mitigate the issue if you are already on Windows 10, version 1903, you can restart the device or select the Scan for hardware changes button in the Action menu or on the toolbar in Device Manager.

Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
Last updated:
July 16, 2019
09:04 AM PT

Opened:
July 12, 2019
04:20 PM PT
" From dedefa870cc28a81eba91c197c955dfda80661f2 Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Tue, 10 Sep 2019 11:11:51 -0700 Subject: [PATCH 9/9] CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20190910100213 (#1073) (#1074) --- .../resolved-issues-windows-10-1607.yml | 2 ++ ...ssues-windows-10-1809-and-windows-server-2019.yml | 2 -- .../resolved-issues-windows-10-1903.yml | 10 ++++++++++ .../release-information/status-windows-10-1507.yml | 2 -- ...tatus-windows-10-1607-and-windows-server-2016.yml | 6 ++---- .../release-information/status-windows-10-1703.yml | 2 -- .../release-information/status-windows-10-1709.yml | 2 -- .../release-information/status-windows-10-1803.yml | 2 -- ...tatus-windows-10-1809-and-windows-server-2019.yml | 2 -- .../release-information/status-windows-10-1903.yml | 6 ++---- ...atus-windows-7-and-windows-server-2008-r2-sp1.yml | 12 ++++++++++-- ...status-windows-8.1-and-windows-server-2012-r2.yml | 2 -- .../status-windows-server-2008-sp2.yml | 2 -- .../status-windows-server-2012.yml | 2 -- .../release-information/windows-message-center.yml | 1 + 15 files changed, 27 insertions(+), 28 deletions(-) diff --git a/windows/release-information/resolved-issues-windows-10-1607.yml b/windows/release-information/resolved-issues-windows-10-1607.yml index 6f92dbe2b1..6f568f3c14 100644 --- a/windows/release-information/resolved-issues-windows-10-1607.yml +++ b/windows/release-information/resolved-issues-windows-10-1607.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: " + @@ -70,6 +71,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusDate resolved
Apps and scripts using the NetQueryDisplayInformation API may fail with error
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data.

See details >		OS Build 14393.3053

June 18, 2019
KB4503294		Resolved
KB4516044		September 10, 2019
10:00 AM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		August 13, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 14393.3144

August 13, 2019
KB4512517		Resolved
KB4512495		August 17, 2019
02:00 PM PT
+
DetailsOriginating updateStatusHistory
Apps and scripts using the NetQueryDisplayInformation API may fail with error
 Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.”

Affected platforms:
  • Server: Windows Server 2019; Windows Server 2016
Resolution: This issue was resolved in KB4516044.

Back to top		OS Build 14393.3053

June 18, 2019
KB4503294		Resolved
KB4516044		Resolved:
September 10, 2019
10:00 AM PT

Opened:
August 01, 2019
05:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512517, 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 KB4512495. This ‘optional’ update is 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 KB4512495 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 14393.3144

August 13, 2019
KB4512517		Resolved
KB4512495		Resolved:
August 17, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503267) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
diff --git a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml index 81e2a0f077..37df3391a5 100644 --- a/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml +++ b/windows/release-information/resolved-issues-windows-10-1809-and-windows-server-2019.yml @@ -55,7 +55,6 @@ sections:
End-user-defined characters (EUDC) may cause blue screen at startup
If you enable per font end-user-defined characters (EUDC), the system may stop working and a blue screen may appear at startup.

See details >OS Build 17763.404

April 02, 2019
KB4490481Resolved
KB4493509April 09, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding
MSXML6 may cause applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().

See details >OS Build 17763.253

January 08, 2019
KB4480116Resolved
KB4493509April 09, 2019
10:00 AM PT
Error 1309 when installing/uninstalling MSI or MSP files
Users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files.

See details >OS Build 17763.316

February 12, 2019
KB4487044Resolved
KB4489899March 12, 2019
10:00 AM PT -
Global DNS outage affects Windows Update customers
Windows Update customers were recently affected by a network infrastructure event caused by an external DNS service provider's global outage.

See details >N/A

Resolved
March 08, 2019
11:15 AM PT
Apps may stop working after selecting an audio output device other than the default
Users with multiple audio devices that select an audio output device different from the \"Default Audio Device\" may find certain applications stop working unexpectedly.

See details >OS Build 17763.348

March 01, 2019
KB4482887Resolved
KB4490481April 02, 2019
10:00 AM PT " @@ -152,7 +151,6 @@ sections: -
DetailsOriginating updateStatusHistory
Internet Explorer 11 authentication issue with multiple concurrent logons
After installing KB4480116, Internet Explorer 11 and other applications that use WININET.DLL may have authentication issues. This occurs when two or more people use the same user account for multiple, concurrent login sessions on the same Windows Server machine, including Remote Desktop Protocol (RDP) and Terminal Server logons. Symptoms reported by customers include, but may not be limited to: 
  • Cache size and location show zero or empty. 
  • Keyboard shortcuts may not work properly. 
  • Webpages may intermittently fail to load or render correctly. 
  • Issues with credential prompts. 
  • Issues when downloading files. 
Affected platforms: 
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 8.1; Windows 7 SP1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1
Resolution: This issue was resolved in KB4493509. 

Back to top		OS Build 17763.253

January 08, 2019
KB4480116		Resolved
KB4493509		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
MSXML6 may cause applications to stop responding
After installing KB4480116, MSXML6 causes applications to stop responding if an exception was thrown during node operations, such as appendChild(), insertBefore(), and moveNode().
 
The Group Policy editor may stop responding when editing a Group Policy Object (GPO) that contains Group Policy Preferences (GPP) for Internet Explorer 10 settings. 

Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10, version 1607; Windows 10 Enterprise LTSC 2016; Windows 10, version 1507; Windows 10 Enterprise LTSB 2015; Windows 8.1
  • Server: Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012
Resolution: This issue was resolved in KB4493509. 

Back to top		OS Build 17763.253

January 08, 2019
KB4480116		Resolved
KB4493509		Resolved:
April 09, 2019
10:00 AM PT

Opened:
January 08, 2019
10:00 AM PT
Global DNS outage affects Windows Update customers
Windows Update customers were affected by a network infrastructure event on January 29, 2019 (21:00 UTC), caused by an external DNS service provider's global outage. A software update to the external provider's DNS servers resulted in the distribution of corrupted DNS records that affected connectivity to the Windows Update service. The DNS records were restored by January 30, 2019 (00:10 UTC), and the majority of local Internet Service Providers (ISP) have refreshed their DNS servers and customer services have been restored. 
 
Affected platforms:
  • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
  • Server: Windows Server, version 1809; Windows Server 2019
While this was not an issue with Microsoft's services, we take any service disruption for our customers seriously. We will work with partners to better understand this so we can provide higher quality service in the future even across diverse global network providers. 
 
If you are still unable to connect to Windows Update services due to this problem, please contact your local ISP or network administrator. You can also refer to our new KB4493784 for more information to determine if your network is affected, and to provide your local ISP or network administrator with additional information to assist you. 

Back to top		N/A

Resolved
Resolved:
March 08, 2019
11:15 AM PT

Opened:
January 29, 2019
02:00 PM PT
" diff --git a/windows/release-information/resolved-issues-windows-10-1903.yml b/windows/release-information/resolved-issues-windows-10-1903.yml index 56fb3d90af..348d00243a 100644 --- a/windows/release-information/resolved-issues-windows-10-1903.yml +++ b/windows/release-information/resolved-issues-windows-10-1903.yml @@ -32,6 +32,7 @@ sections: - type: markdown text: " + @@ -59,6 +60,15 @@ sections:
" +- title: September 2019 +- items: + - type: markdown + text: " +
SummaryOriginating updateStatusDate resolved
Windows Desktop Search may not return any results and may have high CPU usage
Windows Desktop Search may not return any results and SearchUI.exe may have high CPU usage after installing KB4512941.

See details >		OS Build 18362.329

August 30, 2019
KB4512941		Resolved
KB4515384		September 10, 2019
10:00 AM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Issues updating when certain versions of Intel storage drivers are installed
Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Resolved
KB4512941		August 30, 2019
10:00 AM PT
+ +
DetailsOriginating updateStatusHistory
Windows Desktop Search may not return any results and may have high CPU usage
Microsoft is getting reports that a small number of users may not receive results when using Windows Desktop Search and may see high CPU usage from SearchUI.exe when searching after installing KB4512941. This issue is only encountered on devices in which searching the web from Windows Desktop Search has been disabled.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4515384.

Back to top		OS Build 18362.329

August 30, 2019
KB4512941		Resolved
KB4515384		Resolved:
September 10, 2019
10:00 AM PT

Opened:
September 04, 2019
02:25 PM PT
+ " + - title: August 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 9a8ebe8053..a764bbb877 100644 --- a/windows/release-information/status-windows-10-1507.yml +++ b/windows/release-information/status-windows-10-1507.yml @@ -61,7 +61,6 @@ sections: 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
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 10240.18305

August 13, 2019
KB4512497		Resolved
KB4517276		August 17, 2019
02:00 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 10240.18244

June 11, 2019
KB4503291		Resolved External
August 09, 2019
07:03 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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
" @@ -79,7 +78,6 @@ sections: text: " -
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512497, 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 KB4517276. This ‘optional’ update is 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 KB4517276 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 10240.18305

August 13, 2019
KB4512497		Resolved
KB4517276		Resolved:
August 17, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503291) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 10240.18244

June 11, 2019
KB4503291		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" diff --git a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml index da23159b5b..208a38f5dd 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,12 +60,11 @@ 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,9 +83,8 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Apps and scripts using the NetQueryDisplayInformation API may fail with error
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data.

See details >		OS Build 14393.3053

June 18, 2019
KB4503294		Resolved
KB4516044		September 10, 2019
10:00 AM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 14393.3115

July 16, 2019
KB4507459		Resolved
KB4512517		August 13, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 14393.3144

August 13, 2019
KB4512517		Resolved
KB4512495		August 17, 2019
02:00 PM PT
Internet Explorer 11 and apps using the WebBrowser control may fail to render
JavaScript may fail to render as expected in Internet Explorer 11 and in apps using JavaScript or the WebBrowser control.

See details >		OS Build 14393.3085

July 09, 2019
KB4507460		Resolved
KB4512517		August 13, 2019
10:00 AM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved External
August 09, 2019
07:03 PM PT
Apps and scripts using the NetQueryDisplayInformation API may fail with error
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data.

See details >		OS Build 14393.3053

June 18, 2019
KB4503294		Investigating
August 01, 2019
05:00 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (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
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		Mitigated
February 19, 2019
10:00 AM PT
Cluster service may fail if the minimum password length is set to greater than 14
The cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the Group Policy “Minimum Password Length” is configured with greater than 14 characters.

See details >		OS Build 14393.2639

November 27, 2018
KB4467684		Mitigated
April 25, 2019
02:00 PM PT
+ - -
DetailsOriginating updateStatusHistory
Apps and scripts using the NetQueryDisplayInformation API may fail with error
 Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.”

Affected platforms:
  • Server: Windows Server 2019; Windows Server 2016
Resolution: This issue was resolved in KB4516044.

Back to top		OS Build 14393.3053

June 18, 2019
KB4503294		Resolved
KB4516044		Resolved:
September 10, 2019
10:00 AM PT

Opened:
August 01, 2019
05:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512517, 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 KB4512495. This ‘optional’ update is 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 KB4512495 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 14393.3144

August 13, 2019
KB4512517		Resolved
KB4512495		Resolved:
August 17, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503267) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 14393.3025

June 11, 2019
KB4503267		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
Apps and scripts using the NetQueryDisplayInformation API may fail with error
 Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.”

Affected platforms:
  • Server: Windows Server 2019; Windows Server 2016
Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 14393.3053

June 18, 2019
KB4503294		Investigating
Last updated:
August 01, 2019
05:00 PM PT

Opened:
August 01, 2019
05:00 PM PT
" diff --git a/windows/release-information/status-windows-10-1703.yml b/windows/release-information/status-windows-10-1703.yml index 804da5f5fe..626ca1a8e2 100644 --- a/windows/release-information/status-windows-10-1703.yml +++ b/windows/release-information/status-windows-10-1703.yml @@ -68,7 +68,6 @@ sections: -
SummaryOriginating updateStatusLast updated
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 15063.1955

July 16, 2019
KB4507467		Resolved
KB4512507		August 13, 2019
10:00 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 15063.1988

August 13, 2019
KB4512507		Resolved
KB4512474		August 17, 2019
02:00 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 15063.1868

June 11, 2019
KB4503279		Resolved External
August 09, 2019
07:03 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

See details >		OS Build 15063.1563

January 08, 2019
KB4480973		Mitigated
April 25, 2019
02:00 PM PT
" @@ -86,7 +85,6 @@ sections: text: " -
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512507, 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 KB4512474. This ‘optional’ update is 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 KB4512474 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 15063.1988

August 13, 2019
KB4512507		Resolved
KB4512474		Resolved:
August 17, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503279) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 15063.1868

June 11, 2019
KB4503279		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" diff --git a/windows/release-information/status-windows-10-1709.yml b/windows/release-information/status-windows-10-1709.yml index 27e013f10f..ef4bc11351 100644 --- a/windows/release-information/status-windows-10-1709.yml +++ b/windows/release-information/status-windows-10-1709.yml @@ -63,7 +63,6 @@ sections:
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >OS Build 16299.1296

July 16, 2019
KB4507465Resolved
KB4512516August 13, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >OS Build 16299.1217

June 11, 2019
KB4503284Resolved
KB4512494August 16, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >OS Build 16299.1331

August 13, 2019
KB4512516Resolved
KB4512494August 16, 2019
02:00 PM PT -
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >OS Build 16299.1217

June 11, 2019
KB4503284Resolved External
August 09, 2019
07:03 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

See details >OS Build 16299.904

January 08, 2019
KB4480978Mitigated
April 25, 2019
02:00 PM PT " @@ -81,7 +80,6 @@ sections: text: " -
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512516, 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 KB4512494. 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 KB4512494 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 16299.1331

August 13, 2019
KB4512516		Resolved
KB4512494		Resolved:
August 16, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503284) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 16299.1217

June 11, 2019
KB4503284		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" diff --git a/windows/release-information/status-windows-10-1803.yml b/windows/release-information/status-windows-10-1803.yml index 5b3d8b4dd9..a227eb41e0 100644 --- a/windows/release-information/status-windows-10-1803.yml +++ b/windows/release-information/status-windows-10-1803.yml @@ -69,7 +69,6 @@ sections:
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 Preboot Execution Environment (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 that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (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 -
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >OS Build 17134.829

June 11, 2019
KB4503286Resolved External
August 09, 2019
07:03 PM PT
Startup to a black screen after installing updates
Your device may startup to a black screen during the first logon after installing updates.

See details >OS Build 17134.829

June 11, 2019
KB4503286Mitigated
June 14, 2019
04:41 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, \"STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)\".

See details >OS Build 17134.523

January 08, 2019
KB4480966Mitigated
April 25, 2019
02:00 PM PT @@ -97,7 +96,6 @@ sections: 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
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503286) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 17134.829

June 11, 2019
KB4503286		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM 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 d85effd748..d0f9c241ed 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 @@ -67,7 +67,6 @@ sections:
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >OS Build 17763.652

July 22, 2019
KB4505658Resolved
KB4511553August 13, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >OS Build 17763.557

June 11, 2019
KB4503327Resolved
KB4512534August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >OS Build 17763.678

August 13, 2019
KB4511553Resolved
KB4512534August 17, 2019
02:00 PM PT -
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >OS Build 17763.557

June 11, 2019
KB4503327Resolved External
August 09, 2019
07:03 PM PT
Apps and scripts using the NetQueryDisplayInformation API may fail with error
Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data.

See details >OS Build 17763.55

October 09, 2018
KB4464330Investigating
August 01, 2019
05:00 PM PT
Startup to a black screen after installing updates
Your device may startup to a black screen during the first logon after installing updates.

See details >OS Build 17763.557

June 11, 2019
KB4503327Mitigated
June 14, 2019
04:41 PM PT
Devices with some Asian language packs installed may receive an error
After installing the KB4493509 devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_F

See details >OS Build 17763.437

April 09, 2019
KB4493509Mitigated
May 03, 2019
10:59 AM PT @@ -88,7 +87,6 @@ sections: text: " -
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4511553, 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 KB4512534. This ‘optional’ update is 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 KB4512534 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 17763.678

August 13, 2019
KB4511553		Resolved
KB4512534		Resolved:
August 17, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503327) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 17763.557

June 11, 2019
KB4503327		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
Apps and scripts using the NetQueryDisplayInformation API may fail with error
 Applications and scripts that call the NetQueryDisplayInformation API or the WinNT provider equivalent may fail to return results after the first page of data, often 50 or 100 entries. When requesting additional pages you may receive the error, “1359: an internal error occurred.”

Affected platforms:
  • Server: Windows Server 2019; Windows Server 2016
Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 17763.55

October 09, 2018
KB4464330		Investigating
Last updated:
August 01, 2019
05:00 PM PT

Opened:
August 01, 2019
05:00 PM PT
" diff --git a/windows/release-information/status-windows-10-1903.yml b/windows/release-information/status-windows-10-1903.yml index efe7452abd..d203f071d7 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -65,15 +65,14 @@ 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.

+ - - @@ -95,7 +94,7 @@ sections: - type: markdown text: "
SummaryOriginating updateStatusLast updated
Windows Desktop Search may not return any results and may have high CPU usage
Windows Desktop Search may not return any results and SearchUI.exe may have high CPU usage after installing KB4512941.

See details >		OS Build 18362.329

August 30, 2019
KB4512941		Resolved
KB4515384		September 10, 2019
10:00 AM PT
Domain connected devices that use MIT Kerberos realms will not start up
Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Issues updating when certain versions of Intel storage drivers are installed
Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Windows Desktop Search may not return any results and may have high CPU usage
Windows Desktop Search may not return any results and SearchUI.exe may have high CPU usage after installing KB4512941.

See details >		OS Build 18362.329

August 30, 2019
KB4512941		Investigating
September 04, 2019
02:25 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		OS Build 18362.295

August 13, 2019
KB4512508		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Initiating a Remote Desktop connection may result in black screen
When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Windows Sandbox may fail to start with error code “0x80070002”
Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates

See details >		OS Build 18362.116

May 20, 2019
KB4505057		Resolved
KB4512941		August 30, 2019
10:00 AM PT
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) may fail to start with error \"0xc0000001.\"

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved
KB4512941		August 30, 2019
10:00 AM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive an error, \"Updates Failed, There were problems installing some updates, but we'll try again later\" and \"Error 0x80073701.\"

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
August 16, 2019
04:28 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
August 09, 2019
07:03 PM PT
Intermittent loss of Wi-Fi connectivity
Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated External
August 01, 2019
08:44 PM PT
Gamma ramps, color profiles, and night light settings do not apply in some cases
Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working.

See details >		OS Build 18362.116

May 21, 2019
KB4505057		Mitigated
August 01, 2019
06:27 PM PT
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU
Some apps or games that needs to perform graphics intensive operations may close or fail to open on Surface Book 2 devices with Nvidia dGPU.

See details >		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
July 16, 2019
09:04 AM PT
- +
DetailsOriginating updateStatusHistory
Windows Desktop Search may not return any results and may have high CPU usage
Microsoft is getting reports that a small number of users may not receive results when using Windows Desktop Search and may see high CPU usage from SearchUI.exe when searching after installing KB4512941. This issue is only encountered on devices in which searching the web from Windows Desktop Search has been disabled.

Affected platforms:
  • Client: Windows 10, version 1903
Next steps: We are working on a resolution and estimate a solution will be available in mid-September.

Back to top		OS Build 18362.329

August 30, 2019
KB4512941		Investigating
Last updated:
September 04, 2019
02:25 PM PT

Opened:
September 04, 2019
02:25 PM PT
Windows Desktop Search may not return any results and may have high CPU usage
Microsoft is getting reports that a small number of users may not receive results when using Windows Desktop Search and may see high CPU usage from SearchUI.exe when searching after installing KB4512941. This issue is only encountered on devices in which searching the web from Windows Desktop Search has been disabled.

Affected platforms:
  • Client: Windows 10, version 1903
Resolution: This issue was resolved in KB4515384.

Back to top		OS Build 18362.329

August 30, 2019
KB4512941		Resolved
KB4515384		Resolved:
September 10, 2019
10:00 AM PT

Opened:
September 04, 2019
02:25 PM PT
" @@ -106,7 +105,6 @@ sections: -
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512508, 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 KB4512941. The ‘optional’ update is 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 KB4512941 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 18362.295

August 13, 2019
KB4512508		Resolved
KB4512941		Resolved:
August 30, 2019
10:00 AM PT

Opened:
August 14, 2019
03:34 PM PT
Updates may fail to install and you may receive Error 0x80073701
Installation of updates may fail and you may receive the error message, \"Updates Failed, There were problems installing some updates, but we'll try again later\" or \"Error 0x80073701\" on the Windows Update dialog or within Update history.

Affected platforms:
  • Client: Windows 10, version 1903
  • Server: Windows Server, version 1903
Next steps: We are working on a resolution and will provide an update in an upcoming release.

Back to top		OS Build 18362.145

May 29, 2019
KB4497935		Investigating
Last updated:
August 16, 2019
04:28 PM PT

Opened:
August 16, 2019
01:41 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503293) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		OS Build 18362.175

June 11, 2019
KB4503293		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" diff --git a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml index a8fa52963a..5722012e0f 100644 --- a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml @@ -60,12 +60,12 @@ 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 may receive an error when opening or using the Toshiba Qosmio AV Center
Toshiba Qosmio AV Center may error when opening and you may also receive an error in Event Log related to cryptnet.dll.

See details >		August 13, 2019
KB4512506		Investigating
September 10, 2019
09:48 AM PT
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV
Windows updates that are SHA-2 signed are not available with Symantec or Norton antivirus program installed

See details >		August 13, 2019
KB4512506		Resolved External
August 27, 2019
02:29 PM PT
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503292		Resolved
KB4512514		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512506		Resolved
KB4517297		August 16, 2019
02:00 PM PT
IA64 and x64 devices may fail to start after installing updates
After installing updates released on or after August 13, 2019, IA64 and x64 devices using EFI Boot may fail to start.

See details >		August 13, 2019
KB4512506		Mitigated
August 17, 2019
12:59 PM PT
System may be unresponsive after restart with certain McAfee antivirus products
Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.

See details >		April 09, 2019
KB4493472		Resolved External
August 13, 2019
06:59 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503292		Resolved External
August 09, 2019
07:03 PM PT
" @@ -76,6 +76,15 @@ sections:
" +- title: September 2019 +- items: + - type: markdown + text: " + + +
DetailsOriginating updateStatusHistory
You may receive an error when opening or using the Toshiba Qosmio AV Center
After installing KB4512506, you may receive an error when opening or using the Toshiba Qosmio AV Center. You may also receive an error in Event Log related to cryptnet.dll.

Affected platforms:
  • Client: Windows 7 SP1
Next steps: Microsoft is working with Toshiba to resolve this issue and will provide an update in an upcoming release.

Back to top		August 13, 2019
KB4512506		Investigating
Last updated:
September 10, 2019
09:48 AM PT

Opened:
September 10, 2019
09:48 AM PT
+ " + - title: August 2019 - items: - type: markdown @@ -84,7 +93,6 @@ sections:
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV
Symantec identified the potential for a negative interaction that may occur after Windows Updates code signed with SHA-2 only certificates are installed on devices with Symantec or Norton antivirus programs installed. The software may not correctly identify files included in the update as code signed by Microsoft, putting the device at risk for a delayed or incomplete update.

Affected platforms:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1
Resolution: The safeguard hold has been removed. Symantec has completed its evaluation of the impact of this update and future updates to Windows 7/Windows 2008 R2 and has determined that there is no increased risk of a false positive detection for all in-field versions of Symantec Endpoint Protection and Norton antivirus programs. See the Symantec support article for additional detail and please reach out to Symantec or Norton support if you encounter any issues.

Back to topAugust 13, 2019
KB4512506Resolved External
Last updated:
August 27, 2019
02:29 PM PT

Opened:
August 13, 2019
10:05 AM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512506, 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 KB4517297. The ‘optional’ update is now available on Microsoft Update Catalog and Windows Server Update Services (WSUS).

Back to topAugust 13, 2019
KB4512506Resolved
KB4517297Resolved:
August 16, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
IA64 and x64 devices may fail to start after installing updates
IA64 devices (in any configuration) and x64 devices using EFI boot that were provisioned after the July 9th updates and/or skipped the recommended update (KB3133977), may fail to start with the following error:
\"File: \\Windows\\system32\\winload.efi
Status: 0xc0000428
Info: Windows cannot verify the digital signature for this file.\"

Affected platforms:
  • Client: Windows 7 SP1
  • Server: Windows Server 2008 R2 SP1
Take Action: To resolve this issue please follow the steps outlined in the SHA-2 support FAQ article for error code 0xc0000428.

Back to topAugust 13, 2019
KB4512506Mitigated
Last updated:
August 17, 2019
12:59 PM PT

Opened:
August 13, 2019
08:34 AM PT -
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503292) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to topJune 11, 2019
KB4503292Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT " diff --git a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml index 3efbd362b4..362bc0e782 100644 --- a/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml +++ b/windows/release-information/status-windows-8.1-and-windows-server-2012-r2.yml @@ -63,7 +63,6 @@ sections:
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) may fail to start with error \"0xc0000001.\"

See details >June 11, 2019
KB4503276Resolved
KB4512478August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >August 13, 2019
KB4512488Resolved
KB4517298August 16, 2019
02:00 PM PT
System may be unresponsive after restart with certain McAfee antivirus products
Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup.

See details >April 09, 2019
KB4493446Resolved External
August 13, 2019
06:59 PM PT -
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >June 11, 2019
KB4503276Resolved External
August 09, 2019
07:03 PM PT
Japanese IME doesn't show the new Japanese Era name as a text input option
If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option.

See details >April 25, 2019
KB4493443Mitigated
May 15, 2019
05:53 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.

See details >January 08, 2019
KB4480963Mitigated
April 25, 2019
02:00 PM PT @@ -82,7 +81,6 @@ sections: text: " -
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512488, 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 KB4517298. The ‘optional’ update is now available on Microsoft Update Catalog and Windows Server Update Services (WSUS).

Back to top		August 13, 2019
KB4512488		Resolved
KB4517298		Resolved:
August 16, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503276) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		June 11, 2019
KB4503276		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" diff --git a/windows/release-information/status-windows-server-2008-sp2.yml b/windows/release-information/status-windows-server-2008-sp2.yml index d1010bdae7..2954482f10 100644 --- a/windows/release-information/status-windows-server-2008-sp2.yml +++ b/windows/release-information/status-windows-server-2008-sp2.yml @@ -62,7 +62,6 @@ sections: -
SummaryOriginating updateStatusLast updated
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503273		Resolved
KB4512499		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512476		Resolved
KB4517301		August 16, 2019
02:00 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503273		Resolved External
August 09, 2019
07:03 PM PT
" @@ -79,7 +78,6 @@ sections: text: " -
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512476, 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 KB4517301. The ‘optional’ update is now available on Microsoft Update Catalog and Windows Server Update Services (WSUS).

Back to top		August 13, 2019
KB4512476		Resolved
KB4517301		Resolved:
August 16, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503273) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		June 11, 2019
KB4503273		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" diff --git a/windows/release-information/status-windows-server-2012.yml b/windows/release-information/status-windows-server-2012.yml index 055acb57ff..e78082f2be 100644 --- a/windows/release-information/status-windows-server-2012.yml +++ b/windows/release-information/status-windows-server-2012.yml @@ -62,7 +62,6 @@ sections: -
SummaryOriginating updateStatusLast updated
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) may fail to start with error \"0xc0000001.\"

See details >		June 11, 2019
KB4503285		Resolved
KB4512512		August 17, 2019
02:00 PM PT
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error.

See details >		August 13, 2019
KB4512518		Resolved
KB4517302		August 16, 2019
02:00 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later.

See details >		June 11, 2019
KB4503285		Resolved External
August 09, 2019
07:03 PM PT
Japanese IME doesn't show the new Japanese Era name as a text input option
If previous dictionary updates are installed, the Japanese input method editor (IME) doesn't show the new Japanese Era name as a text input option.

See details >		April 25, 2019
KB4493462		Mitigated
May 15, 2019
05:53 PM PT
Certain operations performed on a Cluster Shared Volume may fail
Certain operations, such as rename, performed on files or folders on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”.

See details >		January 08, 2019
KB4480975		Mitigated
April 25, 2019
02:00 PM PT
@@ -81,7 +80,6 @@ sections: text: " -
DetailsOriginating updateStatusHistory
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
After installing KB4512518, 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 KB4517302. The ‘optional’ update is now available on Microsoft Update Catalog and Windows Server Update Services (WSUS).

Back to top		August 13, 2019
KB4512518		Resolved
KB4517302		Resolved:
August 16, 2019
02:00 PM PT

Opened:
August 14, 2019
03:34 PM PT
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices
You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503285) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.”

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: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue.

Back to top		June 11, 2019
KB4503285		Resolved External
Last updated:
August 09, 2019
07:03 PM PT

Opened:
August 09, 2019
04:25 PM PT
" diff --git a/windows/release-information/windows-message-center.yml b/windows/release-information/windows-message-center.yml index 2785208d7d..eabfaa9012 100644 --- a/windows/release-information/windows-message-center.yml +++ b/windows/release-information/windows-message-center.yml @@ -50,6 +50,7 @@ sections: text: " +
MessageDate
September 2019 security update available for all supported versions of Windows
The September 2019 security update release, referred to as our “B” release, is now available for Windows 10, version 1903 and all supported versions of Windows. We recommend that you install these updates promptly. To be informed about the latest updates and releases, , follow us on Twitter @WindowsUpdate.
September 10, 2019
09:34 AM PT
Status update: Windows 10, version 1903 \"D\" optional release available August 30th
The August optional monthly “D” release for Windows 10, version 1903 is now available. Follow @WindowsUpdate for the latest on the availability of this release.
August 30, 2019
08:00 AM PT
Feature update install notification on Windows 10, version 1809 (the October 2018 Update)
We've had reports on August 29th that some customers running Windows 10, version 1809 (the October 2018 Update) have received notification to install the latest feature update (version 1903) early. Updating remains in your control. To install the update, you must select one of the following options: \"Pick a Time\", \"Restart Tonight,\" or \"Restart Now\". If you are not ready to update at this time, simply dismiss the notification by clicking the arrow in the top right corner. If you have updated to Windows 10, version 1903 and would like to go back to your previous version, see the instructions here.
August 29, 2019
04:39 PM PT
Take Action: Internet Explorer 11 now available on Windows Update/WSUS for Windows Server 2012 and Windows Embedded 8 Standard
Internet Explorer 11 (KB 4492872) is now available via Windows Update (WU) and Windows Server Update Services (WSUS) for commercial customers running Windows Server 2012 and Windows Embedded 8 Standard. For details about these changes and end of support for IE10, please refer to the IT Pro blog. 
August 29, 2019
08:00 AM PT