From 81aa15509772c7142877910b5683b13f6117f2e2 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 16 Oct 2019 13:29:58 -0700 Subject: [PATCH 1/8] added link for new error codes --- windows/deployment/windows-autopilot/self-deploying.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/self-deploying.md b/windows/deployment/windows-autopilot/self-deploying.md index 939b4ac431..ca49b045ee 100644 --- a/windows/deployment/windows-autopilot/self-deploying.md +++ b/windows/deployment/windows-autopilot/self-deploying.md @@ -39,7 +39,7 @@ Self-deploying mode is designed to deploy Windows 10 as a kiosk, digital signage Because self-deploying mode uses a device’s TPM 2.0 hardware to authenticate the device into an organization’s Azure AD tenant, devices without TPM 2.0 cannot be used with this mode. The devices must also support TPM device attestation. (All newly-manufactured Windows devices should meet these requirements.) >[!IMPORTANT] ->If you attempt a self-deploying mode deployment on a device that does not have support TPM 2.0 or on a virtual machine, the process will fail when verifying the device with an 0x800705B4 timeout error (Hyper-V virtual TPMs are not supported).. Also note that Window 10, version 1903 or later is required to use self-deploying mode due to issues with TPM device attestation in Windows 10, version 1809. Since Windows 10 Enterprise 2019 LTSC is based on Windows 10 version 1809, self-deploying mode is also not supported on Windows 10 Enterprise 2019 LTSC. +>If you attempt a self-deploying mode deployment on a device that does not have support TPM 2.0 or on a virtual machine, the process will fail when verifying the device with an 0x800705B4 timeout error (Hyper-V virtual TPMs are not supported). Also note that Window 10, version 1903 or later is required to use self-deploying mode due to issues with TPM device attestation in Windows 10, version 1809. Since Windows 10 Enterprise 2019 LTSC is based on Windows 10 version 1809, self-deploying mode is also not supported on Windows 10 Enterprise 2019 LTSC. See [Windows Autopilot known issues](known-issues.md) to review other known errors and solutions. In order to display an organization-specific logo and organization name during the Autopilot process, Azure Active Directory Company Branding needs to be configured with the images and text that should be displayed. See [Quickstart: Add company branding to your sign-in page in Azure AD](https://docs.microsoft.com/azure/active-directory/fundamentals/customize-branding) for more details. From 986ac38cc318d7f58f5d49613d21e7a357c0d5f4 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 16 Oct 2019 13:47:51 -0700 Subject: [PATCH 2/8] added info into known issues --- .../deployment/windows-autopilot/known-issues.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/windows/deployment/windows-autopilot/known-issues.md b/windows/deployment/windows-autopilot/known-issues.md index b2de8f53ee..52826b1c93 100644 --- a/windows/deployment/windows-autopilot/known-issues.md +++ b/windows/deployment/windows-autopilot/known-issues.md @@ -31,10 +31,8 @@ This happens because Windows 10, version 1903 deletes the AutopilotConfiguration To fix this issue:
  1. Edit the Configuration Manager task sequence and disable the Prepare Windows for Capture step.
  2. Add a new Run command line step that runs c:\windows\system32\sysprep\sysprep.exe /oobe /reboot.
More information -The following known issue will be resolved by installing the KB4517211 update, due to be released in late September 2019. -
 
-TPM attestation fails on Windows 10 1903 due to missing AKI extension in EK certificate. (An additional validation added in Windows 10 1903 to check that the TPM EK certs had the proper attributes according to the TCG specifications uncovered that a number of them don’t, so that validation will be removed). -Download and install the KB4517211 update.

This update is currently pending release. +TPM attestation fails on Windows 10 1903 due to missing AKI extension in EK certificate. (An additional validation added in Windows 10 1903 to check that the TPM EK certs had the proper attributes according to the TCG specifications uncovered that a number of them don’t, so that validation will be removed). +Download and install the [KB4517211 update](https://support.microsoft.com/help/4517211/windows-10-update-kb4517211). The following known issues are resolved by installing the August 30, 2019 KB4512941 update (OS Build 18362.329): - Windows Autopilot for existing devices feature does not properly suppress “Activities” page during OOBE. (Because of this, you’ll see that extra page during OOBE). @@ -53,7 +51,12 @@ TPM attestation fails on Windows 10 1903 due to missing AKI extension in EK cert - You are unable to install UWP apps from the Microsoft Store, causing failures during Windows Autopilot. If you are deploying Company Portal as a blocking app during Windows Autopilot ESP, you’ve probably seen this error. - A user is not granted administrator rights in the Windows Autopilot user-driven Hybrid Azure AD join scenario. This is another non-English OS issue. Download and install the KB4505903 update.

See the section: How to get this update for information on specific release channels you can use to obtain the update. - +Windows Autopilot self-deploying mode fails with an error code: + +
0x800705B4The device is not TPM 2.0 capable, such as a VM. You cannot use this device with self-deploying mode. +
0x801c03eaThe device is TPM 2.0 capable, but the TPM is not currently 2.0 and needs to be upgraded. +
0xc1036501The device cannot do an automatic MDM enrollment because there are multiple MDM configurations in Azure AD. Remove the duplicate configurations. +
White glove gives a red screen and the Microsoft-Windows-User Device Registration/Admin event log displays HResult error code 0x801C03F3This can happen if Azure AD can’t find an AAD device object for the device that you are trying to deploy. This will occur if you manually delete the object. To fix it, remove the device from AAD, Intune, and Autopilot, then re-register it with Autopilot, which will recreate the AAD device object.

To obtain troubleshooting logs use: Mdmdiagnosticstool.exe -area Autopilot;TPM -cab c:\autopilot.cab White glove gives a red screenWhite glove is not supported on a VM. From 2f449f233cc5a3d64c2d67807124b519306ab9d3 Mon Sep 17 00:00:00 2001 From: Matthew Palko Date: Thu, 17 Oct 2019 11:28:04 -0700 Subject: [PATCH 3/8] updating adequate number of domain controller documentation for clarity --- .../hello-adequate-domain-controllers.md | 82 +++++++++---------- 1 file changed, 38 insertions(+), 44 deletions(-) diff --git a/windows/security/identity-protection/hello-for-business/hello-adequate-domain-controllers.md b/windows/security/identity-protection/hello-for-business/hello-adequate-domain-controllers.md index fb9a2e4abd..9197e2d07d 100644 --- a/windows/security/identity-protection/hello-for-business/hello-adequate-domain-controllers.md +++ b/windows/security/identity-protection/hello-for-business/hello-adequate-domain-controllers.md @@ -16,103 +16,97 @@ localizationpriority: medium ms.date: 08/20/2018 ms.reviewer: --- -# Planning an adequate number of Windows Server 2019 Domain Controllers for Windows Hello for Business deployments +# Planning an adequate number of Windows Server 2016 or later Domain Controllers for Windows Hello for Business deployments **Applies to** -- Windows 10, version 1703 or later -- Windows Server, versions 2016 and 2019 -- Hybrid or On-Premises deployment -- Key trust + +- Windows 10, version 1703 or later +- Windows Server, versions 2016 or later +- Hybrid or On-Premises deployment +- Key trust > [!NOTE] >There was an issue with key trust on Windows Server 2019. To fix it, refer to [KB4487044](https://support.microsoft.com/en-us/help/4487044/windows-10-update-kb4487044). ## How many is adequate - -How can you find out how many domain controllers are needed? You can use performance monitoring on your domain controllers to determine existing authentication traffic. Windows Server 2016 and above includes the KDC AS Requests performance counter. You can use this counter to determine how much of a domain controller's load is due to initial Kerberos authentication. It's important to remember that authentication for a Windows Hello for Business key trust deployment does not affect Kerberos authentication - it remains unchanged. +How can you find out how many domain controllers are needed? You can use performance monitoring on your domain controllers to determine existing authentication traffic. Windows Server 2016 and above includes the KDC AS Requests performance counter. You can use this counter to determine how much of a domain controller's load is due to initial Kerberos authentication. It's important to remember that authentication for a Windows Hello for Business key trust deployment does not affect Kerberos authentication - it remains unchanged. - -Windows 10 accomplishes Windows Hello for Business key trust authentication by mapping an Active Directory user account to one or more public keys. This mapping occurs on the domain controller, which is why the deployment needs Windows Server 2016 and above domain controllers. Public key mapping is only supported by Windows Server 2016 domain controllers. Therefore, users in a key trust deployment must authenticate to a Windows Server 2016 and above domain controller. +Windows 10 accomplishes Windows Hello for Business key trust authentication by mapping an Active Directory user account to one or more public keys. This mapping occurs on the domain controller, which is why the deployment needs Windows Server 2016 or later domain controllers. Public key mapping is only supported by Windows Server 2016 domain controllers and above. Therefore, users in a key trust deployment must authenticate to a Windows Server 2016 and above domain controller. - -Determining an adequate number of Windows Server domain controllers is important to ensure you have enough domain controllers to satisfy all authentication requests, including users mapped with public key trust. What many administrators do not realize is that adding the most current version of a domain controller (in this case Windows Server 2019) to a deployment of existing domain controllers (Windows Server 2008R2, Windows Server 2012R2 or Windows Server 2016) instantly makes that single domain controller susceptible to carrying the most load, or what is commonly referred to as "piling on". To illustrate the "piling on" concept, consider the following scenario: +Determining an adequate number of Windows Server domain controllers is important to ensure you have enough domain controllers to satisfy all authentication requests, including users mapped with public key trust. What many administrators do not realize is that adding a domain controller that supports public key mapping (in this case Windows Server 2016 or later) to a deployment of existing domain controllers which do not support public key mapping (Windows Server 2008R2, Windows Server 2012R2) instantly makes that single domain controller susceptible to carrying the most load, or what is commonly referred to as "piling on". To illustrate the "piling on" concept, consider the following scenario: - -Consider a controlled environment where there are 1000 client computers and the authentication load of these 1000 client computers is evenly distributed across 10 domain controllers in the environment. The Kerberos AS requests load would look something like the following: +Consider a controlled environment where there are 1000 client computers and the authentication load of these 1000 client computers is evenly distributed across 10 domain controllers in the environment. The Kerberos AS requests load would look something like the following: ![dc-chart1](images/plan/dc-chart1.png) - -The environment changes. The first change includes DC1 upgraded to Windows Server 2019 to support Windows Hello for Business key-trust authentication. Next, 100 clients enroll for Windows Hello for Business using the public key trust deployment. Given all other factors stay constant, the authentication would now look like the following: +The environment changes. The first change includes DC1 upgraded to Windows Server 2016 or later to support Windows Hello for Business key-trust authentication. Next, 100 clients enroll for Windows Hello for Business using the public key trust deployment. Given all other factors stay constant, the authentication would now look like the following: ![dc-chart2](images/plan/dc-chart2.png) -The Windows Server 2019 domain controller is handling 100 percent of all public key trust authentication. However, it is also handling 10 percent of the password authentication. Why? This behavior occurs because domain controllers 2 - 10 only support password and certificate trust authentication; only a Windows Server 2019 domain controller supports public key trust authentication. The Windows Server 2019 domain controller understands how to authenticate password and certificate trust authentication and will continue to share the load of authenticating those clients. Because DC1 can handle all forms of authentication, it will bear more of the authentication load, and easily become overloaded. What if another Windows Server 2019 domain controller is added, but without deploying Windows Hello for Business to any more clients? - +The Windows Server 2016 or later domain controller is handling 100 percent of all public key trust authentication. However, it is also handling 10 percent of password authentication. Why? This behavior occurs because domain controllers 2 - 10 only support password and certificate trust authentication; only a Windows Server 2016 and above domain controller supports public key trust authentication. The Windows Server 2016 and above domain controller still understands how to authenticate password and certificate trust authentication and will continue to share the load of authenticating those clients. Because DC1 can handle all forms of authentication, it will bear more of the authentication load, and easily become overloaded. What if another Windows Server 2016 or later domain controller is added, but without deploying Windows Hello for Business to any more clients? ![dc-chart3](images/plan/dc-chart3.png) -Upgrading another Windows Server 2019 domain controller distributes the public key trust authentication across two domain controllers - each supporting 50 percent of the load. But it doesn't change the distribution of password and certificate trust authentication. Both Windows Server 2019 domain controllers still share 10 percent of this load. Now look at the scenario when half of the domain controllers are upgraded to Windows Server 2019, but the number of WHFB clients remains the same. +Upgrading another domain controller to Windows Server 2016 or later distributes the public key trust authentication across two domain controllers - each supporting 50 percent of the load. But it doesn't change the distribution of password and certificate trust authentication. Both Windows Server 2019 domain controllers still share 10 percent of this load. Now look at the scenario when half of the domain controllers are upgraded to Windows Server 2016 or later, but the number of WHFB clients remains the same. ![dc-chart4](images/plan/dc-chart4.png) -Domain controllers 1 through 5 now share the public key trust authentication load where each domain controller handles 20 percent of the public key trust load but they each still handle 10 percent of the password and certificate trust authentication. These domain controllers still have a heavier load than domain controllers 6 through 10; however, the load is adequately distributed. Now look the scenario when half of the client computers are upgraded to Windows Hello for Business using a key-trust deployment. +Domain controllers 1 through 5 now share the public key trust authentication load where each domain controller handles 20 percent of the public key trust load but they each still handle 10 percent of the password and certificate trust authentication. These domain controllers still have a heavier load than domain controllers 6 through 10; however, the load is adequately distributed. Now look the scenario when half of the client computers are upgraded to Windows Hello for Business using a key-trust deployment. ![dc-chart5](images/plan/dc-chart5.png) -You'll notice the distribution did not change. Each Windows Server 2019 domain controller handles 20 percent of the public key trust authentication. However, increasing the volume of authentication (by increasing the number of clients) increases the amount of work that is represented by the same 20 percent. In the previous example, 20 percent of public key trust authentication equated to a volume of 20 authentications per domain controller capable of public key trust authentication. However, with upgraded clients, that same 20 percent represents a volume of 100 public key trust authentications per public key trust capable domain controller. Also, the distribution of non-public key trust authentication remained at 10 percent, but the volume of password and certificate trust authentications decreased across the older domain controllers. +You'll notice the distribution did not change. Each Windows Server 2016 or later domain controller handles 20 percent of the public key trust authentication. However, increasing the volume of authentication (by increasing the number of clients) increases the amount of work that is represented by the same 20 percent. In the previous example, 20 percent of public key trust authentication equated to a volume of 20 authentications per domain controller capable of public key trust authentication. However, with upgraded clients, that same 20 percent represents a volume of 100 public key trust authentications per public key trust capable domain controller. Also, the distribution of non-public key trust authentication remained at 10 percent, but the volume of password and certificate trust authentications decreased across the older domain controllers. -There are several conclusions here: -* Upgrading domain controllers changes the distribution of new authentication, but doesn't change the distribution of older authentication. -* Upgrading domain controllers does not affect the distribution of password and certificate trust authentication because newer domain controllers can support password and certificate trust authentication. -* Upgraded domain controllers typically carry a heavier authentication load than down-level domain controllers because they support more forms of authentication. -* Upgrading clients to Windows Hello for Business, increases the volume of public key trust authentication distributed across domain controllers which support it and, reduces the volume of password and certificate trust authentication across all domain controllers -* Upgrading clients to Windows Hello for Business but does not affect the distribution of authentication; only the volume of authentication. - -The preceding was an example to show why it's unrealistic to have a "one-size-fits-all" number to describe what "an adequate amount" means. In the real world, authentication is not evenly distributed across domain controllers. +There are several conclusions here: +- Upgrading domain controllers changes the distribution of new authentication, but doesn't change the distribution of older authentication. +- Upgrading domain controllers does not affect the distribution of password and certificate trust authentication because newer domain controllers can support password and certificate trust authentication. +- Upgraded domain controllers typically carry a heavier authentication load than down-level domain controllers because they support more forms of authentication. +- Upgrading clients to Windows Hello for Business, increases the volume of public key trust authentication distributed across domain controllers which support it and, reduces the volume of password and certificate trust authentication across all domain controllers +- Upgrading clients to Windows Hello for Business but does not affect the distribution of authentication; only the volume of authentication. +The preceding was an example to show why it's unrealistic to have a "one-size-fits-all" number to describe what "an adequate amount" means. In the real world, authentication is not evenly distributed across domain controllers. ## Determining total AS Request load Each organization needs to have a baseline of the AS request load that occurs in their environment. Windows Server provides the KDC AS Requests performance counter that helps you determine this. -Pick a site where you plan to upgrade the clients to Windows Hello for Business public key trust. Pick a time when authentication traffic is most significant--Monday morning is great time as everyone is returning to the office. Enable the performance counter on *all* the domain controllers in that site. Collect KDC AS Requests performance counters for two hours: -* A half-hour before you expect initial authentication (sign-ins and unlocks) to be significant -* The hour you believe initial authentication to be significant -* And a half-hour after you expect initial authentication to be significant +Pick a site where you plan to upgrade the clients to Windows Hello for Business public key trust. Pick a time when authentication traffic is most significant--Monday morning is great time as everyone is returning to the office. Enable the performance counter on *all* the domain controllers in that site. Collect KDC AS Requests performance counters for two hours: -For example, if employees are scheduled to come into the office at 9:00am. Your performance capture should begin at 8:30am and end at 10:30am. Ensure your performance logs do not wrap the data. You want to see authentication trend upward, peak, and trend downward. +- A half-hour before you expect initial authentication (sign-ins and unlocks) to be significant +- The hour you believe initial authentication to be significant +- And a half-hour after you expect initial authentication to be significant + +For example, if employees are scheduled to come into the office at 9:00am. Your performance capture should begin at 8:30am and end at 10:30am. Ensure your performance logs do not wrap the data. You want to see authentication trend upward, peak, and trend downward. > [!NOTE] > To capture all the authentication traffic. Ensure that all computers are powered down to get the most accurate authentication information (computers and services authenticate at first power up--you need to consider this authentication in your evaluation). -Aggregate the performance data of all domain controllers. Look for the maximum KDC AS Requests for each domain controller. Find the median time when the maximum number of requests occurred for the site, this should represent when the site is experiencing the highest amount of authentication. - -Add the number of authentications for each domain controller for the median time. You now have the total authentication for the site during a peak time. Using this metric, you can determine the distribution of authentication across the domain controllers in the site by dividing the domain controller's authentication number for the median time by the total authentication. Multiply the quotient by 10 to convert the distribution to a percentage. To validate your math, all the distributions should equal 100 percent. +Aggregate the performance data of all domain controllers. Look for the maximum KDC AS Requests for each domain controller. Find the median time when the maximum number of requests occurred for the site, this should represent when the site is experiencing the highest amount of authentication. -Review the distribution of authentication. Hopefully, none of these are above 70 percent. It's always good to reserve some capacity for the unexpected. Also, the primary purposes of a domain controller are to provide authentication and handle Active Directory operations. Identify domain controllers with lower distributions of authentication as potential candidates for the initial domain controller upgrades in conjunction with a reasonable distribution of clients provisioned for Windows Hello for Business. +Add the number of authentications for each domain controller for the median time. You now have the total authentication for the site during a peak time. Using this metric, you can determine the distribution of authentication across the domain controllers in the site by dividing the domain controller's authentication number for the median time by the total authentication. Multiply the quotient by 10 to convert the distribution to a percentage. To validate your math, all the distributions should equal 100 percent. + +Review the distribution of authentication. Hopefully, none of these are above 70 percent. It's always good to reserve some capacity for the unexpected. Also, the primary purposes of a domain controller are to provide authentication and handle Active Directory operations. Identify domain controllers with lower distributions of authentication as potential candidates for the initial domain controller upgrades in conjunction with a reasonable distribution of clients provisioned for Windows Hello for Business. ## Monitoring Authentication -Using the same methods described above, monitor the Kerberos authentication after upgrading a domain controller and your first phase of Windows Hello for Business deployments. Make note of the delta of authentication before and after upgrading the domain controller to Windows Server 2019. This delta is representative of authentication resulting from the first phase of your Windows Hello for Business clients. It gives you a baseline for your environment to where you can form a statement such as: - +Using the same methods described above, monitor the Kerberos authentication after upgrading a domain controller and your first phase of Windows Hello for Business deployments. Make note of the delta of authentication before and after upgrading the domain controller to Windows Server 2016 or newer. This delta is representative of authentication resulting from the first phase of your Windows Hello for Business clients. It gives you a baseline for your environment to where you can form a statement such as: ```"Every n Windows Hello for Business clients results in x percentage of key-trust authentication."``` -Where _n_ equals the number of clients you switched to Windows Hello for Business and _x_ equals the increased percentage of authentication from the upgraded domain controller. Armed with this information, you can apply the observations of upgrading domain controllers and increasing Windows Hello for Business client count to appropriately phase your deployment. +Where _n_ equals the number of clients you switched to Windows Hello for Business and _x_ equals the increased percentage of authentication from the upgraded domain controller. Armed with this information, you can apply the observations of upgrading domain controllers and increasing Windows Hello for Business client count to appropriately phase your deployment. -Remember, increasing the number of clients changes the volume of authentication distributed across the Windows Server 2019 domain controllers. If there is only one Windows Server 2019 domain controller, there's no distribution and you are simply increasing the volume of authentication for which THAT domain controller is responsible. +Remember, increasing the number of clients changes the volume of authentication distributed across the Windows Server 2016 or newer domain controllers. If there is only one Windows Server 2016 or newer domain controller, there's no distribution and you are simply increasing the volume of authentication for which THAT domain controller is responsible. Increasing the number of domain controllers distributes the volume of authentication, but doesn't change it. Therefore, as you add more domain controllers, the burden of authentication, for which each domain controller is responsible, decreases. Upgrading two domain controller changes the distribution to 50 percent. Upgrading three domain controllers changes the distribution to 33 percent, and so on. ## Strategy + The simplest strategy you can employ is to upgrade one domain controller and monitor the single domain controller as you continue to phase in new Windows Hello for Business key-trust clients until it reaches a 70 or 80 percent threshold. -Then, upgrade a second domain controller. Monitor the authentication on both domain controllers to determine how the authentication distributes between the two domain controllers. Introduce more Windows Hello for Business clients while monitoring the authentication on the two upgraded domain controllers. Once those reach your environment's designated capacity, you can upgrade another domain controller. +Then, upgrade a second domain controller. Monitor the authentication on both domain controllers to determine how the authentication distributes between the two domain controllers. Introduce more Windows Hello for Business clients while monitoring the authentication on the two upgraded domain controllers. Once those reach your environment's designated capacity, you can upgrade another domain controller. -Repeat until your deployment for that site is complete. Now, monitor authentication across all your domain controllers like you did the very first time. Determine the distribution of authentication for each domain controller. Identify the percentage of distribution for which it is responsible. If a single domain controller is responsible for 70 percent of more of the authentication, you may want to consider adding a domain controller to reduce the distribution of authentication volume. +Repeat until your deployment for that site is complete. Now, monitor authentication across all your domain controllers like you did the very first time. Determine the distribution of authentication for each domain controller. Identify the percentage of distribution for which it is responsible. If a single domain controller is responsible for 70 percent of more of the authentication, you may want to consider adding a domain controller to reduce the distribution of authentication volume. However, before considering this, ensure the high load of authentication is not a result of applications and services where their configuration has a statically-configured domain controller. Adding domain controllers will not resolve the additional authentication load problem in this scenario. Instead, manually distribute the authentication to different domain controllers among all the services or applications. Alternatively, try simply using the domain name rather than a specific domain controller. Each domain controller has an A record registered in DNS for the domain name, which DNS will round robin with each DNS query. It's not the best load balancer, however, it is a better alternative to static domain controller configurations, provided the configuration is compatible with your service or application. - From f0c24374fc469f8e6adebb423a113b46267f173b Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Thu, 17 Oct 2019 11:49:56 -0700 Subject: [PATCH 4/8] codes --- windows/deployment/windows-autopilot/known-issues.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/deployment/windows-autopilot/known-issues.md b/windows/deployment/windows-autopilot/known-issues.md index 52826b1c93..0123c3675c 100644 --- a/windows/deployment/windows-autopilot/known-issues.md +++ b/windows/deployment/windows-autopilot/known-issues.md @@ -51,11 +51,11 @@ This happens because Windows 10, version 1903 deletes the AutopilotConfiguration - You are unable to install UWP apps from the Microsoft Store, causing failures during Windows Autopilot. If you are deploying Company Portal as a blocking app during Windows Autopilot ESP, you’ve probably seen this error. - A user is not granted administrator rights in the Windows Autopilot user-driven Hybrid Azure AD join scenario. This is another non-English OS issue. Download and install the KB4505903 update.

See the section: How to get this update for information on specific release channels you can use to obtain the update. -Windows Autopilot self-deploying mode fails with an error code: +Windows Autopilot self-deploying mode fails with an error code: -
0x800705B4The device is not TPM 2.0 capable, such as a VM. You cannot use this device with self-deploying mode. -
0x801c03eaThe device is TPM 2.0 capable, but the TPM is not currently 2.0 and needs to be upgraded. -
0xc1036501The device cannot do an automatic MDM enrollment because there are multiple MDM configurations in Azure AD. Remove the duplicate configurations. +
0x800705B4This is a general error indicating a timeout. A common cause of this error in self-deploying mode is that the device is not TPM 2.0 capable (ex: a virtual machine). Devices that are not TPM 2.0 capable cannot be used with self-deploying mode. +
0x801c03eaThis error indictes that TPM attestation failed, causing a failure to join Azure Active Directory with a device token. +
0xc1036501The device cannot do an automatic MDM enrollment because there are multiple MDM configurations in Azure AD. See Inside Windows Autopilot self-deploying mode.
White glove gives a red screen and the Microsoft-Windows-User Device Registration/Admin event log displays HResult error code 0x801C03F3This can happen if Azure AD can’t find an AAD device object for the device that you are trying to deploy. This will occur if you manually delete the object. To fix it, remove the device from AAD, Intune, and Autopilot, then re-register it with Autopilot, which will recreate the AAD device object.

To obtain troubleshooting logs use: Mdmdiagnosticstool.exe -area Autopilot;TPM -cab c:\autopilot.cab From 2df6b7172329d19defabff10a3dc483c82c090ff Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Thu, 17 Oct 2019 12:16:09 -0700 Subject: [PATCH 5/8] fix link --- windows/deployment/windows-autopilot/known-issues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/known-issues.md b/windows/deployment/windows-autopilot/known-issues.md index 0123c3675c..9291def4d2 100644 --- a/windows/deployment/windows-autopilot/known-issues.md +++ b/windows/deployment/windows-autopilot/known-issues.md @@ -32,7 +32,7 @@ This happens because Windows 10, version 1903 deletes the AutopilotConfiguration
  • Add a new Run command line step that runs c:\windows\system32\sysprep\sysprep.exe /oobe /reboot. More information TPM attestation fails on Windows 10 1903 due to missing AKI extension in EK certificate. (An additional validation added in Windows 10 1903 to check that the TPM EK certs had the proper attributes according to the TCG specifications uncovered that a number of them don’t, so that validation will be removed). -Download and install the [KB4517211 update](https://support.microsoft.com/help/4517211/windows-10-update-kb4517211). +Download and install the KB4517211 update. The following known issues are resolved by installing the August 30, 2019 KB4512941 update (OS Build 18362.329): - Windows Autopilot for existing devices feature does not properly suppress “Activities” page during OOBE. (Because of this, you’ll see that extra page during OOBE). From fc74f6c409c8609bb18a807bbef187d85e07628d Mon Sep 17 00:00:00 2001 From: Rebecca Agiewich Date: Thu, 17 Oct 2019 12:54:09 -0700 Subject: [PATCH 6/8] fixed spelling issue --- windows/deployment/windows-autopilot/known-issues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/known-issues.md b/windows/deployment/windows-autopilot/known-issues.md index 9291def4d2..c1f9331822 100644 --- a/windows/deployment/windows-autopilot/known-issues.md +++ b/windows/deployment/windows-autopilot/known-issues.md @@ -54,7 +54,7 @@ This happens because Windows 10, version 1903 deletes the AutopilotConfiguration Windows Autopilot self-deploying mode fails with an error code:
    0x800705B4This is a general error indicating a timeout. A common cause of this error in self-deploying mode is that the device is not TPM 2.0 capable (ex: a virtual machine). Devices that are not TPM 2.0 capable cannot be used with self-deploying mode. -
    0x801c03eaThis error indictes that TPM attestation failed, causing a failure to join Azure Active Directory with a device token. +
    0x801c03eaThis error indicates that TPM attestation failed, causing a failure to join Azure Active Directory with a device token.
    0xc1036501The device cannot do an automatic MDM enrollment because there are multiple MDM configurations in Azure AD. See Inside Windows Autopilot self-deploying mode.
    White glove gives a red screen and the Microsoft-Windows-User Device Registration/Admin event log displays HResult error code 0x801C03F3This can happen if Azure AD can’t find an AAD device object for the device that you are trying to deploy. This will occur if you manually delete the object. To fix it, remove the device from AAD, Intune, and Autopilot, then re-register it with Autopilot, which will recreate the AAD device object.
    From 1bf02a21cef6f53f06f4ed073cf9c4ad01291198 Mon Sep 17 00:00:00 2001 From: Daniel Simpson Date: Thu, 17 Oct 2019 17:47:11 -0700 Subject: [PATCH 7/8] Update prevent-changes-to-security-settings-with-tamper-protection.md --- ...event-changes-to-security-settings-with-tamper-protection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-defender-antivirus/prevent-changes-to-security-settings-with-tamper-protection.md b/windows/security/threat-protection/windows-defender-antivirus/prevent-changes-to-security-settings-with-tamper-protection.md index 8324650680..6251363a58 100644 --- a/windows/security/threat-protection/windows-defender-antivirus/prevent-changes-to-security-settings-with-tamper-protection.md +++ b/windows/security/threat-protection/windows-defender-antivirus/prevent-changes-to-security-settings-with-tamper-protection.md @@ -36,7 +36,7 @@ With Tamper Protection, malicious apps are prevented from taking actions like th ## How it works - Tamper Protection essentially locks Microsoft Defender and prevents your security settings from being changed through apps and methods like these: + Tamper Protection essentially locks Windows Defender Antivirus and prevents your security settings from being changed through apps and methods like these: - Configuring settings in Registry Editor on your Windows machine - Changing settings through PowerShell cmdlets - Editing or removing security settings through group policies From 2acf509fde386516d2cdd3127f873f8c788d881f Mon Sep 17 00:00:00 2001 From: John Liu <49762389+ShenLanJohn@users.noreply.github.com> Date: Thu, 17 Oct 2019 19:18:31 -0700 Subject: [PATCH 8/8] CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20191017181659 (#1367) --- .../resolved-issues-windows-10-1507.yml | 2 +- .../resolved-issues-windows-10-1607.yml | 2 +- .../resolved-issues-windows-10-1703.yml | 2 +- .../resolved-issues-windows-10-1709.yml | 2 +- .../resolved-issues-windows-10-1803.yml | 2 +- ...ssues-windows-10-1809-and-windows-server-2019.yml | 2 +- .../resolved-issues-windows-10-1903.yml | 2 +- ...sues-windows-7-and-windows-server-2008-r2-sp1.yml | 2 +- ...issues-windows-8.1-and-windows-server-2012-r2.yml | 2 +- .../resolved-issues-windows-server-2008-sp2.yml | 2 +- .../resolved-issues-windows-server-2012.yml | 2 +- .../release-information/status-windows-10-1507.yml | 2 +- ...tatus-windows-10-1607-and-windows-server-2016.yml | 4 +--- .../release-information/status-windows-10-1703.yml | 4 +--- .../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 | 12 +++++++++++- .../release-information/status-windows-10-1903.yml | 2 +- ...atus-windows-7-and-windows-server-2008-r2-sp1.yml | 2 +- ...status-windows-8.1-and-windows-server-2012-r2.yml | 2 +- .../status-windows-server-2008-sp2.yml | 2 +- .../status-windows-server-2012.yml | 2 +- 22 files changed, 32 insertions(+), 26 deletions(-) diff --git a/windows/release-information/resolved-issues-windows-10-1507.yml b/windows/release-information/resolved-issues-windows-10-1507.yml index 96c938dec5..50c83837eb 100644 --- a/windows/release-information/resolved-issues-windows-10-1507.yml +++ b/windows/release-information/resolved-issues-windows-10-1507.yml @@ -32,7 +32,7 @@ sections: - type: markdown text: " - + diff --git a/windows/release-information/resolved-issues-windows-10-1607.yml b/windows/release-information/resolved-issues-windows-10-1607.yml index 7cbaf548d3..44e89ad24d 100644 --- a/windows/release-information/resolved-issues-windows-10-1607.yml +++ b/windows/release-information/resolved-issues-windows-10-1607.yml @@ -32,7 +32,7 @@ sections: - type: markdown text: "
    SummaryOriginating updateStatusDate resolved
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 10240.18334

    September 23, 2019
    KB4522009    		Resolved
    KB4520011    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 10240.18334

    September 23, 2019
    KB4522009    		Resolved
    KB4520011    		October 08, 2019
    10:00 AM PT
    Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error
    Applications made using VB6, macros using VBA, and VBScript may stop responding and you may receive an error.

    See details >    		OS Build 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 certain Windows devices.

    See details >    		OS Build 10240.18244

    June 11, 2019
    KB4503291    		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 see an error or the app may close.

    See details >    		OS Build 10240.18244

    June 11, 2019
    KB4503291    		Resolved
    KB4507458    		July 09, 2019
    10:00 AM PT
    - + diff --git a/windows/release-information/resolved-issues-windows-10-1703.yml b/windows/release-information/resolved-issues-windows-10-1703.yml index 862a0cb913..b66de78474 100644 --- a/windows/release-information/resolved-issues-windows-10-1703.yml +++ b/windows/release-information/resolved-issues-windows-10-1703.yml @@ -32,7 +32,7 @@ sections: - type: markdown text: "
    SummaryOriginating updateStatusDate resolved
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 14393.3206

    September 23, 2019
    KB4522010    		Resolved
    KB4519998    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 14393.3206

    September 23, 2019
    KB4522010    		Resolved
    KB4519998    		October 08, 2019
    10:00 AM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 14393.3204

    September 10, 2019
    KB4516044    		Resolved
    		September 17, 2019
    04:47 PM PT
    Apps and scripts using the NetQueryDisplayInformation API may fail with error
    Applications and scripts that call NetQueryDisplayInformation may fail to return results after the first page of data.

    See details >    		OS Build 14393.3053

    June 18, 2019
    KB4503294    		Resolved
    KB4516044    		September 10, 2019
    10:00 AM PT
    Domain connected devices that use MIT Kerberos realms will not start up
    Devices may not start after updating when connected to a domain that is configured to use MIT Kerberos realms.

    See details >    		OS Build 14393.3115

    July 16, 2019
    KB4507459    		Resolved
    KB4512517    		August 13, 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 2461882d7f..8a16e56715 100644 --- a/windows/release-information/resolved-issues-windows-10-1709.yml +++ b/windows/release-information/resolved-issues-windows-10-1709.yml @@ -32,7 +32,7 @@ sections: - type: markdown text: "
    SummaryOriginating updateStatusDate resolved
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 15063.2046

    September 23, 2019
    KB4522011    		Resolved
    KB4520010    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 15063.2046

    September 23, 2019
    KB4522011    		Resolved
    KB4520010    		October 08, 2019
    10:00 AM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 15063.2045

    September 10, 2019
    KB4516068    		Resolved
    		September 17, 2019
    04:47 PM PT
    Domain connected devices that use MIT Kerberos realms will not start up
    Devices may not start after updating when connected to a domain that is configured to use MIT Kerberos realms.

    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 made using VB6, macros using 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
    - + diff --git a/windows/release-information/resolved-issues-windows-10-1803.yml b/windows/release-information/resolved-issues-windows-10-1803.yml index 43944d0d5c..aeeb0b6087 100644 --- a/windows/release-information/resolved-issues-windows-10-1803.yml +++ b/windows/release-information/resolved-issues-windows-10-1803.yml @@ -34,7 +34,7 @@ sections:
    SummaryOriginating updateStatusDate resolved
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 16299.1392

    September 23, 2019
    KB4522012    		Resolved
    KB4520004    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 16299.1392

    September 23, 2019
    KB4522012    		Resolved
    KB4520004    		October 08, 2019
    10:00 AM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 16299.1387

    September 10, 2019
    KB4516066    		Resolved
    		September 19, 2019
    04:08 PM PT
    Domain connected devices that use MIT Kerberos realms will not start up
    Devices may not start after updating when connected to a domain that is configured to use MIT Kerberos realms.

    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 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
    - + 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 4558663c3e..d8ce5f8d4a 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 @@ -34,7 +34,7 @@ sections:
    SummaryOriginating updateStatusDate resolved
    Windows Mixed Reality Portal users may intermittently receive a 15-5 error code
    You may receive a 15-5 error code in Windows Mixed Reality Portal and your headset may not wake up from sleep.

    See details >    		OS Build 17134.950

    August 13, 2019
    KB4512501    		Resolved
    KB4519978    		October 15, 2019
    10:00 AM 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    		Resolved
    KB4519978    		October 15, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 17134.1009

    September 23, 2019
    KB4522014    		Resolved
    KB4520008    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 17134.1009

    September 23, 2019
    KB4522014    		Resolved
    KB4520008    		October 08, 2019
    10:00 AM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 17134.1006

    September 10, 2019
    KB4516058    		Resolved
    		September 19, 2019
    04:08 PM PT
    Domain connected devices that use MIT Kerberos realms will not start up
    Devices may not start after updating when connected to a domain that is configured to use MIT Kerberos realms.

    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
    - + diff --git a/windows/release-information/resolved-issues-windows-10-1903.yml b/windows/release-information/resolved-issues-windows-10-1903.yml index 25f5d45af6..5869704b1a 100644 --- a/windows/release-information/resolved-issues-windows-10-1903.yml +++ b/windows/release-information/resolved-issues-windows-10-1903.yml @@ -33,7 +33,7 @@ sections: text: "
    SummaryOriginating updateStatusDate resolved
    Windows Mixed Reality Portal users may intermittently receive a 15-5 error code
    You may receive a 15-5 error code in Windows Mixed Reality Portal and your headset may not wake up from sleep.

    See details >    		OS Build 17763.678

    August 13, 2019
    KB4511553    		Resolved
    KB4520062    		October 15, 2019
    10:00 AM 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    		Resolved
    KB4520062    		October 15, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 17763.740

    September 23, 2019
    KB4522015    		Resolved
    KB4519338    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 17763.740

    September 23, 2019
    KB4522015    		Resolved
    KB4519338    		October 08, 2019
    10:00 AM PT
    Apps and scripts using the NetQueryDisplayInformation API may fail with error
    Applications and scripts that call NetQueryDisplayInformation may fail to return results after the first page of data.

    See details >    		OS Build 17763.55

    October 09, 2018
    KB4464330    		Resolved
    KB4516077    		September 24, 2019
    10:00 AM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 17763.737

    September 10, 2019
    KB4512578    		Resolved
    		September 19, 2019
    04:08 PM PT
    Domain connected devices that use MIT Kerberos realms will not start up
    Devices may not start after updating when connected to a domain that is configured to use MIT Kerberos realms.

    See details >    		OS Build 17763.652

    July 22, 2019
    KB4505658    		Resolved
    KB4511553    		August 13, 2019
    10:00 AM PT
    - + diff --git a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml index 7232cf65f7..018a7f2bc2 100644 --- a/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/resolved-issues-windows-7-and-windows-server-2008-r2-sp1.yml @@ -32,7 +32,7 @@ sections: - type: markdown text: "
    SummaryOriginating updateStatusDate resolved
    dGPU occasionally disappear from device manager on Surface Book 2
    Some apps or games may close or fail to open on Surface Book 2 devices with Nvidia dGPU.

    See details >    		OS Build 18362.145

    May 29, 2019
    KB4497935    		Resolved
    		October 11, 2019
    03:15 PM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 18362.357

    September 23, 2019
    KB4522016    		Resolved
    KB4517389    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 18362.357

    September 23, 2019
    KB4522016    		Resolved
    KB4517389    		October 08, 2019
    10:00 AM PT
    Audio in games is quiet or different than expected
    Microsoft has received reports that audio in certain games is quieter or different than expected.

    See details >    		OS Build 18362.356

    September 10, 2019
    KB4515384    		Resolved
    KB4517211    		September 26, 2019
    02:00 PM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 18362.356

    September 10, 2019
    KB4515384    		Resolved
    		September 19, 2019
    04:08 PM PT
    Some users report issues related to the Start menu and Windows Desktop Search
    A small number of users have reported issues related to the Start menu and Windows Desktop Search.

    See details >    		OS Build 18362.356

    September 10, 2019
    KB4515384    		Resolved
    		September 19, 2019
    04:58 PM 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 c58e1391c1..773e34d6fa 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,7 +32,7 @@ sections: - type: markdown text: "
    SummaryOriginating updateStatusDate resolved
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		September 24, 2019
    KB4516048    		Resolved
    KB4519976    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		September 24, 2019
    KB4516048    		Resolved
    KB4519976    		October 08, 2019
    10:00 AM PT
    You may receive an error when opening or using the Toshiba Qosmio AV Center
    Toshiba Qosmio AV Center may error when opening and you may also receive an error in Event Log related to cryptnet.dll.

    See details >    		August 13, 2019
    KB4512506    		Resolved
    KB4516048    		September 24, 2019
    10:00 AM PT
    Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV
    Windows updates that are SHA-2 signed are not available with Symantec or Norton antivirus program installed

    See details >    		August 13, 2019
    KB4512506    		Resolved External
    		August 27, 2019
    02:29 PM PT
    Devices starting using PXE from a WDS or SCCM servers may fail to start
    Devices that start up using PXE images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\"

    See details >    		June 11, 2019
    KB4503292    		Resolved
    KB4512514    		August 17, 2019
    02:00 PM PT
    - + diff --git a/windows/release-information/resolved-issues-windows-server-2008-sp2.yml b/windows/release-information/resolved-issues-windows-server-2008-sp2.yml index 57adef5214..ae70b4a30e 100644 --- a/windows/release-information/resolved-issues-windows-server-2008-sp2.yml +++ b/windows/release-information/resolved-issues-windows-server-2008-sp2.yml @@ -32,7 +32,7 @@ sections: - type: markdown text: "
    SummaryOriginating updateStatusDate resolved
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		September 24, 2019
    KB4516041    		Resolved
    KB4520005    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		September 24, 2019
    KB4516041    		Resolved
    KB4520005    		October 08, 2019
    10:00 AM PT
    Windows RT 8.1 devices may have issues opening Internet Explorer 11
    On Windows RT 8.1 devices, Internet Explorer 11 may not open and you may receive an error.

    See details >    		September 10, 2019
    KB4516067    		Resolved
    KB4516041    		September 24, 2019
    10:00 AM PT
    Devices starting using PXE from a WDS or SCCM servers may fail to start
    Devices that start up using PXE images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\"

    See details >    		June 11, 2019
    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 made using VB6, macros using 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
    - + diff --git a/windows/release-information/resolved-issues-windows-server-2012.yml b/windows/release-information/resolved-issues-windows-server-2012.yml index 1ca43d3f61..660872c996 100644 --- a/windows/release-information/resolved-issues-windows-server-2012.yml +++ b/windows/release-information/resolved-issues-windows-server-2012.yml @@ -32,7 +32,7 @@ sections: - type: markdown text: "
    SummaryOriginating updateStatusDate resolved
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		September 24, 2019
    KB4516030    		Resolved
    KB4520002    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		September 24, 2019
    KB4516030    		Resolved
    KB4520002    		October 08, 2019
    10:00 AM PT
    Devices starting using PXE from a WDS or SCCM servers may fail to start
    Devices that start up using PXE images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\"

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

    See details >    		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 certain Windows devices.

    See details >    		June 11, 2019
    KB4503273    		Resolved External
    		August 09, 2019
    07:03 PM PT
    - + diff --git a/windows/release-information/status-windows-10-1507.yml b/windows/release-information/status-windows-10-1507.yml index e84e0fc49b..be4512cee7 100644 --- a/windows/release-information/status-windows-10-1507.yml +++ b/windows/release-information/status-windows-10-1507.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    SummaryOriginating updateStatusDate resolved
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		September 24, 2019
    KB4516069    		Resolved
    KB4520007    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		September 24, 2019
    KB4516069    		Resolved
    KB4520007    		October 08, 2019
    10:00 AM PT
    Devices starting using PXE from a WDS or SCCM servers may fail to start
    Devices that start up using PXE images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\"

    See details >    		June 11, 2019
    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 made using VB6, macros using 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 certain Windows devices.

    See details >    		June 11, 2019
    KB4503285    		Resolved External
    		August 09, 2019
    07:03 PM PT
    - +
    SummaryOriginating updateStatusLast updated
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 10240.18334

    September 23, 2019
    KB4522009    		Resolved
    KB4520011    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 10240.18334

    September 23, 2019
    KB4522009    		Resolved
    KB4520011    		October 08, 2019
    10:00 AM PT
    Certain operations performed on a Cluster Shared Volume may fail
    Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5).

    See details >    		OS Build 10240.18094

    January 08, 2019
    KB4480962    		Mitigated
    		April 25, 2019
    02:00 PM PT
    " 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 f91ae43fc4..c75ec5b5a9 100644 --- a/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml +++ b/windows/release-information/status-windows-10-1607-and-windows-server-2016.yml @@ -60,8 +60,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,7 +80,6 @@ sections: text: "
    SummaryOriginating updateStatusLast updated
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 14393.3206

    September 23, 2019
    KB4522010    		Resolved
    KB4519998    		October 08, 2019
    10:00 AM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 14393.3204

    September 10, 2019
    KB4516044    		Resolved
    		September 17, 2019
    04:47 PM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 14393.3206

    September 23, 2019
    KB4522010    		Resolved
    KB4519998    		October 08, 2019
    10:00 AM PT
    Certain operations performed on a Cluster Shared Volume may fail
    Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5).

    See details >    		OS Build 14393.2724

    January 08, 2019
    KB4480961    		Mitigated
    		April 25, 2019
    02:00 PM PT
    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 if “Minimum Password Length” is configured with greater than 14 characters.

    See details >    		OS Build 14393.2639

    November 27, 2018
    KB4467684    		Mitigated
    		April 25, 2019
    02:00 PM PT
    -
    DetailsOriginating updateStatusHistory
    Intermittent issues when printing
    Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
    • Applications interacting with the V4 printer driver might close or error when printing. Issues might only be encountered when printing but might also be encountered at any time the app is running, depending on when the app interacts with the print driver.
    • The printer spooler service (spoolsv.exe) might close or error in jscript.dll with exception code 0xc0000005 causing the print jobs to stop processing. Only part of the print job might print and the rest might be canceled or 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 KB4519998.

    Back to top    		OS Build 14393.3206

    September 23, 2019
    KB4522010    		Resolved
    KB4519998    		Resolved:
    October 08, 2019
    10:00 AM PT

    Opened:
    September 30, 2019
    06:26 PM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) may become unresponsive or may have high CPU usage. Affected IMEs include Chinese Simplified (ChsIME.EXE) and Chinese Traditional (ChtIME.EXE) with Changjie/Quick keyboard.


    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: After investigation, we have found that this issue does not affect this version of Windows.

    Back to top    		OS Build 14393.3204

    September 10, 2019
    KB4516044    		Resolved
    		Resolved:
    September 17, 2019
    04:47 PM PT

    Opened:
    September 13, 2019
    05:25 PM PT
    " diff --git a/windows/release-information/status-windows-10-1703.yml b/windows/release-information/status-windows-10-1703.yml index 519ad969c5..9b774ca109 100644 --- a/windows/release-information/status-windows-10-1703.yml +++ b/windows/release-information/status-windows-10-1703.yml @@ -64,8 +64,7 @@ sections: - type: markdown text: "
    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    - - +
    SummaryOriginating updateStatusLast updated
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 15063.2046

    September 23, 2019
    KB4522011    		Resolved
    KB4520010    		October 08, 2019
    10:00 AM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 15063.2045

    September 10, 2019
    KB4516068    		Resolved
    		September 17, 2019
    04:47 PM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 15063.2046

    September 23, 2019
    KB4522011    		Resolved
    KB4520010    		October 08, 2019
    10:00 AM PT
    Certain operations performed on a Cluster Shared Volume may fail
    Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5).

    See details >    		OS Build 15063.1563

    January 08, 2019
    KB4480973    		Mitigated
    		April 25, 2019
    02:00 PM PT
    " @@ -83,7 +82,6 @@ sections: text: " -
    DetailsOriginating updateStatusHistory
    Intermittent issues when printing
    Applications and printer drivers that leverage the Windows Javascript engine (jscript.dll) for processing print jobs might experience one or more of the following symptoms:
    • Applications interacting with the V4 printer driver might close or error when printing. Issues might only be encountered when printing but might also be encountered at any time the app is running, depending on when the app interacts with the print driver.
    • The printer spooler service (spoolsv.exe) might close or error in jscript.dll with exception code 0xc0000005 causing the print jobs to stop processing. Only part of the print job might print and the rest might be canceled or 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 KB4520010.

    Back to top    		OS Build 15063.2046

    September 23, 2019
    KB4522011    		Resolved
    KB4520010    		Resolved:
    October 08, 2019
    10:00 AM PT

    Opened:
    September 30, 2019
    06:26 PM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) may become unresponsive or may have high CPU usage. Affected IMEs include Chinese Simplified (ChsIME.EXE) and Chinese Traditional (ChtIME.EXE) with Changjie/Quick keyboard.


    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: After investigation, we have found that this issue does not affect this version of Windows.

    Back to top    		OS Build 15063.2045

    September 10, 2019
    KB4516068    		Resolved
    		Resolved:
    September 17, 2019
    04:47 PM PT

    Opened:
    September 13, 2019
    05:25 PM PT
    " diff --git a/windows/release-information/status-windows-10-1709.yml b/windows/release-information/status-windows-10-1709.yml index e7cfb4d349..72f9e6f8fa 100644 --- a/windows/release-information/status-windows-10-1709.yml +++ b/windows/release-information/status-windows-10-1709.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    - +
    SummaryOriginating updateStatusLast updated
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 16299.1392

    September 23, 2019
    KB4522012    		Resolved
    KB4520004    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 16299.1392

    September 23, 2019
    KB4522012    		Resolved
    KB4520004    		October 08, 2019
    10:00 AM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 16299.1387

    September 10, 2019
    KB4516066    		Resolved
    		September 19, 2019
    04:08 PM PT
    Certain operations performed on a Cluster Shared Volume may fail
    Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5).

    See details >    		OS Build 16299.904

    January 08, 2019
    KB4480978    		Mitigated
    		April 25, 2019
    02:00 PM PT
    diff --git a/windows/release-information/status-windows-10-1803.yml b/windows/release-information/status-windows-10-1803.yml index 7ed2748792..5ad00ae3bb 100644 --- a/windows/release-information/status-windows-10-1803.yml +++ b/windows/release-information/status-windows-10-1803.yml @@ -66,7 +66,7 @@ sections: - +
    SummaryOriginating updateStatusLast updated
    Windows Mixed Reality Portal users may intermittently receive a 15-5 error code
    You may receive a 15-5 error code in Windows Mixed Reality Portal and your headset may not wake up from sleep.

    See details >    		OS Build 17134.950

    August 13, 2019
    KB4512501    		Resolved
    KB4519978    		October 15, 2019
    10:00 AM 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    		Resolved
    KB4519978    		October 15, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 17134.1009

    September 23, 2019
    KB4522014    		Resolved
    KB4520008    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 17134.1009

    September 23, 2019
    KB4522014    		Resolved
    KB4520008    		October 08, 2019
    10:00 AM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 17134.1006

    September 10, 2019
    KB4516058    		Resolved
    		September 19, 2019
    04:08 PM PT
    Certain operations performed on a Cluster Shared Volume may fail
    Operations performed on files or folders on a CSV may fail with the error: STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5).

    See details >    		OS Build 17134.523

    January 08, 2019
    KB4480966    		Mitigated
    		April 25, 2019
    02:00 PM PT
    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 a4a29741dd..34b02272a1 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,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.

    + - + @@ -81,6 +82,15 @@ sections:
    " +- title: October 2019 +- items: + - type: markdown + text: " +
    SummaryOriginating updateStatusLast updated
    Microsoft Defender Advanced Threat Protection might stop running
    The Microsoft Defender ATP service might stop running and might fail to send reporting data.

    See details >    		OS Build 17763.832

    October 15, 2019
    KB4520062    		Investigating
    		October 17, 2019
    05:14 PM PT
    Windows Mixed Reality Portal users may intermittently receive a 15-5 error code
    You may receive a 15-5 error code in Windows Mixed Reality Portal and your headset may not wake up from sleep.

    See details >    		OS Build 17763.678

    August 13, 2019
    KB4511553    		Resolved
    KB4520062    		October 15, 2019
    10:00 AM 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    		Resolved
    KB4520062    		October 15, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 17763.740

    September 23, 2019
    KB4522015    		Resolved
    KB4519338    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 17763.740

    September 23, 2019
    KB4522015    		Resolved
    KB4519338    		October 08, 2019
    10:00 AM PT
    Apps and scripts using the NetQueryDisplayInformation API may fail with error
    Applications and scripts that call NetQueryDisplayInformation may fail to return results after the first page of data.

    See details >    		OS Build 17763.55

    October 09, 2018
    KB4464330    		Resolved
    KB4516077    		September 24, 2019
    10:00 AM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 17763.737

    September 10, 2019
    KB4512578    		Resolved
    		September 19, 2019
    04:08 PM PT
    Devices with some Asian language packs installed may receive an error
    Devices with Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.\"

    See details >    		OS Build 17763.437

    April 09, 2019
    KB4493509    		Mitigated
    		May 03, 2019
    10:59 AM PT
    + +
    DetailsOriginating updateStatusHistory
    Microsoft Defender Advanced Threat Protection might stop running
    The Microsoft Defender Advanced Threat Protection (ATP) service might stop running and might fail to send reporting data. You might also receive a 0xc0000409 error in Event Viewer on MsSense.exe.

    Affected platforms:
    • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019
    • Server: Windows Server, version 1809; Windows Server 2019
    Next steps: At this time, we suggest that devices in an affected environment do not install KB4520062. We are working on a resolution and estimate a solution will be available in mid-November.

    Back to top    		OS Build 17763.832

    October 15, 2019
    KB4520062    		Investigating
    		Last updated:
    October 17, 2019
    05:14 PM PT

    Opened:
    October 17, 2019
    05:14 PM PT
    + " + - title: September 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 4a9b8d4364..c5efe999d1 100644 --- a/windows/release-information/status-windows-10-1903.yml +++ b/windows/release-information/status-windows-10-1903.yml @@ -65,7 +65,7 @@ sections: text: "
    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    - + 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 3d71ca817a..8102e3efa0 100644 --- a/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml +++ b/windows/release-information/status-windows-7-and-windows-server-2008-r2-sp1.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    SummaryOriginating updateStatusLast updated
    dGPU occasionally disappear from device manager on Surface Book 2
    Some apps or games may close or fail to open on Surface Book 2 devices with Nvidia dGPU.

    See details >    		OS Build 18362.145

    May 29, 2019
    KB4497935    		Resolved
    		October 11, 2019
    03:15 PM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		OS Build 18362.357

    September 23, 2019
    KB4522016    		Resolved
    KB4517389    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		OS Build 18362.357

    September 23, 2019
    KB4522016    		Resolved
    KB4517389    		October 08, 2019
    10:00 AM PT
    Audio in games is quiet or different than expected
    Microsoft has received reports that audio in certain games is quieter or different than expected.

    See details >    		OS Build 18362.356

    September 10, 2019
    KB4515384    		Resolved
    KB4517211    		September 26, 2019
    02:00 PM PT
    IME may become unresponsive or have High CPU usage
    Some Input Method Editor (IME) including ChsIME.EXE and ChtIME.EXE, may become unresponsive or may have high CPU usage.

    See details >    		OS Build 18362.356

    September 10, 2019
    KB4515384    		Resolved
    		September 19, 2019
    04:08 PM PT
    Some users report issues related to the Start menu and Windows Desktop Search
    A small number of users have reported issues related to the Start menu and Windows Desktop Search.

    See details >    		OS Build 18362.356

    September 10, 2019
    KB4515384    		Resolved
    		September 19, 2019
    04:58 PM PT
    - +
    SummaryOriginating updateStatusLast updated
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		September 24, 2019
    KB4516048    		Resolved
    KB4519976    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		September 24, 2019
    KB4516048    		Resolved
    KB4519976    		October 08, 2019
    10:00 AM PT
    You may receive an error when opening or using the Toshiba Qosmio AV Center
    Toshiba Qosmio AV Center may error when opening and you may also receive an error in Event Log related to cryptnet.dll.

    See details >    		August 13, 2019
    KB4512506    		Resolved
    KB4516048    		September 24, 2019
    10:00 AM PT
    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
    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 378e8da44f..068427814b 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,7 +60,7 @@ sections: - type: markdown text: "
    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    - + diff --git a/windows/release-information/status-windows-server-2008-sp2.yml b/windows/release-information/status-windows-server-2008-sp2.yml index fda671a495..9b171c527f 100644 --- a/windows/release-information/status-windows-server-2008-sp2.yml +++ b/windows/release-information/status-windows-server-2008-sp2.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    SummaryOriginating updateStatusLast updated
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		September 24, 2019
    KB4516041    		Resolved
    KB4520005    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		September 24, 2019
    KB4516041    		Resolved
    KB4520005    		October 08, 2019
    10:00 AM PT
    Windows RT 8.1 devices may have issues opening Internet Explorer 11
    On Windows RT 8.1 devices, Internet Explorer 11 may not open and you may receive an error.

    See details >    		September 10, 2019
    KB4516067    		Resolved
    KB4516041    		September 24, 2019
    10:00 AM PT
    Japanese IME doesn't show the new Japanese Era name as a text input option
    With previous dictionary updates installed, the Japanese IME doesn't show the new Japanese Era name as an 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
    Operations performed on files or folders on a 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
    - +
    SummaryOriginating updateStatusLast updated
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		September 24, 2019
    KB4516030    		Resolved
    KB4520002    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		September 24, 2019
    KB4516030    		Resolved
    KB4520002    		October 08, 2019
    10:00 AM PT
    Issues manually installing updates by double-clicking the .msu file
    You may encounter issues manually installing updates by double-clicking the .msu file and may receive an error.

    See details >    		September 10, 2019
    KB4474419    		Mitigated
    KB4474419    		September 24, 2019
    08:17 AM PT
    " diff --git a/windows/release-information/status-windows-server-2012.yml b/windows/release-information/status-windows-server-2012.yml index 27a39802c2..e05f9d92b9 100644 --- a/windows/release-information/status-windows-server-2012.yml +++ b/windows/release-information/status-windows-server-2012.yml @@ -60,7 +60,7 @@ sections: - type: markdown text: "
    This table offers a summary of current active issues and those issues that have been resolved in the last 30 days.

    - +
    SummaryOriginating updateStatusLast updated
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing.

    See details >    		September 24, 2019
    KB4516069    		Resolved
    KB4520007    		October 08, 2019
    10:00 AM PT
    Intermittent issues when printing
    The print spooler service may intermittently have issues completing a print job and results print job failure.

    See details >    		September 24, 2019
    KB4516069    		Resolved
    KB4520007    		October 08, 2019
    10:00 AM PT
    Japanese IME doesn't show the new Japanese Era name as a text input option
    With previous dictionary updates installed, the Japanese IME doesn't show the new Japanese Era name as an 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
    Operations performed on files or folders on a 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