diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json index 761b93800a..95b887e08a 100644 --- a/.openpublishing.redirection.json +++ b/.openpublishing.redirection.json @@ -6,11 +6,6 @@ "redirect_document_id": true }, { -"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/collect-cab-files-exploit-guard-submission.md", -"redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/troubleshoot-np", -"redirect_document_id": true -}, -{ "source_path": "windows/security/information-protection/windows-information-protection/create-wip-policy-using-mam-intune-azure.md", "redirect_url": "/windows/security/information-protection/windows-information-protection/create-wip-policy-using-intune-azure", "redirect_document_id": true @@ -631,8 +626,8 @@ "redirect_document_id": true }, { -"source_path": "windows/security/threat-protection/device-guard/requirements-and-deployment-planning-guidelines-for-device-guard.md", -"redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/requirements-and-deployment-planning-guidelines-for-virtualization-based-protection-of-code-integrity", +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/attack-surface-reduction-rules-in-windows-10-enterprise-e3.md", +"redirect_url": "windows/security/threat-protection/microsoft-defender-atp/attack-surface-reduction-rules-in-windows-10-enterprise-e3", "redirect_document_id": true }, { @@ -726,96 +721,196 @@ "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/attack-surface-reduction-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/attack-surface-reduction", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/audit-windows-defender-exploit-guard.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/audit-windows-defender-exploit-guard", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/audit-windows-defender-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/audit-windows-defender", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/collect-cab-files-exploit-guard-submission.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/collect-cab-files-exploit-guard-submission", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/collect-cab-files-exploit-guard-submission.md", +"redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/troubleshoot-np", +"redirect_document_id": true +}, +{ +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/troubleshoot-np.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-np", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/controlled-folders-exploit-guard.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/controlled-folders-exploit-guard", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/controlled-folders-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/controlled-folders", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/customize-attack-surface-reduction.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/customize-attack-surface-reduction", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/customize-controlled-folders", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/customize-exploit-protection.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/customize-exploit-protection", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/customize-exploit-protection.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/customize-exploit-protection", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/emet-exploit-protection-exploit-guard.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/emet-exploit-protection-exploit-guard", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/emet-exploit-protection-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/emet-exploit-protection", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/enable-attack-surface-reduction.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/enable-attack-surface-reduction", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/enable-controlled-folders-exploit-guard", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/enable-exploit-protection.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/enable-exploit-protection", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/enable-exploit-protection.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/enable-exploit-protection", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/enable-network-protection.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/enable-network-protection.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/enable-network-protection", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/evaluate-attack-surface-reduction.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/evaluate-attack-surface-reduction", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/evaluate-attack-surface-reduction.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/evaluate-attack-surface-reduction", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/evaluate-controlled-folder-access.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/evaluate-controlled-folder-access", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/evaluate-controlled-folder-access.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/evaluate-controlled-folder-access", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/evaluate-exploit-protection.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/evaluate-exploit-protection", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/evaluate-exploit-protection.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/evaluate-exploit-protection", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/evaluate-network-protection.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/evaluate-network-protection", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/evaluate-network-protection.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/evaluate-network-protection", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/evaluate-windows-defender-exploit-guard.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/evaluate-windows-defender-exploit-guard", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/evaluate-windows-defender-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/evaluate-windows-defender", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/event-views-exploit-guard.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/event-views-exploit-guard", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/event-views-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/event-views", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/exploit-protection-exploit-guard.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/exploit-protection-exploit-guard", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/exploit-protection-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/exploit-protection-exploit-guard", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/graphics.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/graphics", "redirect_document_id": true @@ -826,11 +921,21 @@ "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/import-export-exploit-protection-emet-xml.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/import-export-exploit-protection-emet-xml", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/network-protection-exploit-guard.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/network-protection-exploit-guard", "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/network-protection-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/network-protection", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/prerelease.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/prerelease", "redirect_document_id": true @@ -841,13 +946,18 @@ "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/troubleshoot-asr.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-asr", +"redirect_document_id": true +}, +{ "source_path": "windows/threat-protection/windows-defender-exploit-guard/troubleshoot-exploit-protection-mitigations.md", "redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/troubleshoot-exploit-protection-mitigations", "redirect_document_id": true }, { -"source_path": "windows/threat-protection/windows-defender-exploit-guard/troubleshoot-np.md", -"redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/troubleshoot-np", +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/troubleshoot-exploit-protection-mitigations.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/troubleshoot-exploit-protection-mitigations", "redirect_document_id": true }, { @@ -856,6 +966,11 @@ "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/windows-defender-exploit-guard.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-advanced-threat-protection", +"redirect_document_id": false +}, +{ "source_path": "windows/keep-secure/advanced-features-windows-defender-advanced-threat-protection.md", "redirect_url": "/windows/threat-protection/windows-defender-atp/advanced-features-windows-defender-advanced-threat-protection", "redirect_document_id": true @@ -1005,7 +1120,6 @@ "redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/configure-attack-surface-reduction", "redirect_document_id": true }, - { "source_path": "windows/security/threat-protection/windows-defender-atp/configuration-score.md", "redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/configuration-score", @@ -3087,11 +3201,6 @@ "redirect_document_id": true }, { -"source_path": "windows/device-security/device-guard/deploy-device-guard-enable-virtualization-based-security.md", -"redirect_url": "/windows/security/threat-protection/device-guard/deploy-device-guard-enable-virtualization-based-security", -"redirect_document_id": true -}, -{ "source_path": "windows/device-security/device-guard/deploy-managed-installer-for-device-guard.md", "redirect_url": "/windows/security/threat-protection/device-guard/deploy-managed-installer-for-device-guard", "redirect_document_id": true @@ -3132,6 +3241,16 @@ "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/requirements-and-deployment-planning-guidelines-for-virtualization-based-protection-of-code-integrity.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/requirements-and-deployment-planning-guidelines-for-virtualization-based-protection-of-code-integrity", +"redirect_document_id": true +}, +{ +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/memory-integrity.md", +"redirect_url": "/windows/security/threat-protection/device-guard/memory-integrity", +"redirect_document_id": true +}, +{ "source_path": "windows/device-security/device-guard/steps-to-deploy-windows-defender-application-control.md", "redirect_url": "/windows/security/threat-protection/windows-defender-application-control/create-initial-default-policy", "redirect_document_id": true @@ -4422,6 +4541,11 @@ "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/windows-defender-exploit-guard/enable-virtualization-based-protection-of-code-integrity.md", +"redirect_url": "/windows/security/threat-protection/device-guard/enable-virtualization-based-protection-of-code-integrity", +"redirect_document_id": true +}, +{ "source_path": "windows/device-security/get-support-for-security-baselines.md", "redirect_url": "/windows/security/threat-protection/get-support-for-security-baselines", "redirect_document_id": true @@ -9642,6 +9766,11 @@ "redirect_document_id": true }, { +"source_path": "windows/device-security/device-guard/deploy-device-guard-enable-virtualization-based-security.md", +"redirect_url": "/windows/security/threat-protection/device-guard/deploy-device-guard-enable-virtualization-based-security", +"redirect_document_id": true +}, +{ "source_path": "windows/keep-secure/deploy-manage-report-windows-defender-antivirus.md", "redirect_url": "/windows/threat-protection/windows-defender-antivirus/deploy-manage-report-windows-defender-antivirus", "redirect_document_id": true @@ -12167,11 +12296,6 @@ "redirect_document_id": true }, { -"source_path": "windows/keep-secure/requirements-and-deployment-planning-guidelines-for-device-guard.md", -"redirect_url": "/windows/security/threat-protection/windows-defender-exploit-guard/requirements-and-deployment-planning-guidelines-for-virtualization-based-protection-of-code-integrity", -"redirect_document_id": true -}, -{ "source_path": "windows/keep-secure/requirements-for-deploying-applocker-policies.md", "redirect_url": "/windows/device-security/applocker/requirements-for-deploying-applocker-policies", "redirect_document_id": true @@ -14654,7 +14778,7 @@ { "source_path": "windows/security/threat-protection/windows-defender-atp/get-ip-related-alerts-windows-defender-advanced-threat-protection-new.md", "redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/get-ip-related-alerts", -"redirect_document_id": true +"redirect_document_id": false }, { "source_path": "windows/security/threat-protection/windows-defender-atp/get-ip-related-machines-windows-defender-advanced-threat-protection.md", @@ -14664,7 +14788,7 @@ { "source_path": "windows/security/threat-protection/windows-defender-atp/get-ip-related-machines-windows-defender-advanced-threat-protection-new.md", "redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/get-ip-related-machines", -"redirect_document_id": true +"redirect_document_id": false }, { "source_path": "windows/security/threat-protection/windows-defender-atp/get-ip-statistics-windows-defender-advanced-threat-protection.md", @@ -14867,9 +14991,14 @@ "redirect_document_id": true }, { - "source_path": "windows/security/threat-protection/windows-defender-atp/api-power-bi.md", - "redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/api-power-bi", - "redirect_document_id": true +"source_path": "windows/security/threat-protection/windows-defender-atp/run-advanced-query-sample-power-bi-app-token.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/run-advanced-query-sample-power-bi-app-token", +"redirect_document_id": true +}, +{ +"source_path": "windows/security/threat-protection/microsoft-defender-atp/run-advanced-query-sample-power-bi-app-token.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/api-power-bi", +"redirect_document_id": true }, { "source_path": "windows/security/threat-protection/windows-defender-atp/run-advanced-query-sample-powershell.md", @@ -15002,6 +15131,21 @@ "redirect_document_id": true }, { +"source_path": "windows/security/threat-protection/microsoft-defender-atp/is-domain-seen-in-org.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/get-domain-related-alerts", +"redirect_document_id": false +}, +{ +"source_path": "windows/security/threat-protection/microsoft-defender-atp/get-ip-related-machines.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/get-ip-related-alerts", +"redirect_document_id": true +}, +{ +"source_path": "windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp/is-ip-seen-org.md", +"redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/microsoft-defender-atp/exposed-apis-list", +"redirect_document_id": false +}, +{ "source_path": "windows/security/threat-protection/windows-defender-atp/machineaction-windows-defender-advanced-threat-protection-new.md", "redirect_url": "/windows/security/threat-protection/microsoft-defender-atp/machineaction", "redirect_document_id": true diff --git a/browsers/edge/about-microsoft-edge.md b/browsers/edge/about-microsoft-edge.md index c9801bd936..1b86c5d81f 100644 --- a/browsers/edge/about-microsoft-edge.md +++ b/browsers/edge/about-microsoft-edge.md @@ -45,7 +45,7 @@ Some of the components might also need additional system resources. Check the co ## Supported languages -Microsoft Edge supports all of the same languages as Windows 10 and you can use the [Microsoft Translator extension](https://www.microsoft.com/en-us/p/translator-for-microsoft-edge/9nblggh4n4n3) to translate foreign language web pages and text selections for 60+ languages. +Microsoft Edge supports all of the same languages as Windows 10 and you can use the [Microsoft Translator extension](https://www.microsoft.com/p/translator-for-microsoft-edge/9nblggh4n4n3) to translate foreign language web pages and text selections for 60+ languages. If the extension does not work after install, restart Microsoft Edge. If the extension still does not work, provide feedback through the Feedback Hub. diff --git a/browsers/edge/emie-to-improve-compatibility.md b/browsers/edge/emie-to-improve-compatibility.md index c7882f76e7..e9ec39db3f 100644 --- a/browsers/edge/emie-to-improve-compatibility.md +++ b/browsers/edge/emie-to-improve-compatibility.md @@ -41,7 +41,7 @@ If you're having trouble deciding whether Microsoft Edge is right for your organ |Microsoft Edge |IE11 | |---------|---------| -|Microsoft Edge takes you beyond just browsing to actively engaging with the web through features like Web Note, Reading View, and Cortana.
Surface Hub 2S deployment checklist
- -Deploy with provisioning package
+Surface Hub 2S adoption and training
+ +Windows 10 editions for education customers
Windows 10, version 1607 introduces two editions designed for the unique needs of K-12 institutions: Windows 10 Pro Education and Windows 10 Education. These editions provide education-specific default settings for the evolving landscape in K-12 education IT environments.
Compare each Windows edition
Find out more about the features and functionality we support in each edition of Windows.
Get Windows 10 Education or Windows 10 Pro Education
When you've made your decision, find out how to buy Windows for your school.
Compare each Windows edition
Find out more about the features and functionality we support in each edition of Windows.
Get Windows 10 Education or Windows 10 Pro Education
When you've made your decision, find out how to buy Windows for your school.
Microsoft SQL Server 2016
Standard, Enterprise, or Datacenter
SP1
64-bit
64-bit
Microsoft SQL Server 2014
Standard, Enterprise, or Datacenter
Value | -Description | -
---|---|
EVENT_TRACE_FILE_MODE_SEQUENTIAL (0x00000001) |
-Writes events to a log file sequentially; stops when the file reaches its maximum size. |
-
EVENT_TRACE_FILE_MODE_CIRCULAR (0x00000002) |
-Writes events to a log file. After the file reaches the maximum size, the oldest events are replaced with incoming events. |
-
Value | -Description | -
---|---|
1 – TRACE_LEVEL_CRITICAL |
-Abnormal exit or termination events |
-
2 – TRACE_LEVEL_ERROR |
-Severe error events |
-
3 – TRACE_LEVEL_WARNING |
-Warning events such as allocation failures |
-
4 – TRACE_LEVEL_INFORMATION |
-Non-error events, such as entry or exit events |
-
5 – TRACE_LEVEL_VERBOSE |
-Detailed information |
-
Value | -Description | -
---|---|
TRUE |
-Provider is enabled in the trace session. |
-
FALSE |
-Provider is disables in the trace session. |
-
Value | -Description | -
---|---|
TRUE |
-Channel is enabled. |
-
FALSE |
-Channel is disabled. |
-
Added new CSP in Windows 10, version 1903.
Added version 1.4 of the CSP in Windows 10, version 1903. Added the new 1.4 version of the DDF. Added the following new nodes:
+Policy, Policy/Channels, Policy/Channels/ChannelName, Policy/Channels/ChannelName/MaximumFileSize, Policy/Channels/ChannelName/SDDL, Policy/Channels/ChannelName/ActionWhenFull, Policy/Channels/ChannelName/Enabled, DiagnosticArchive, DiagnosticArchive/ArchiveDefinition, DiagnosticArchive/ArchiveResults.
+
Added new CSP in Windows 10, version 1903.
Cmdlet | Use this cmdlet to | Syntax | |
---|---|---|---|
Add-ProvisioningPackage | Apply a provisioning package | Add-ProvisioningPackage [-Path] <string> [-ForceInstall] [-LogsFolder <string>] [-WprpFile <string>] [<CommonParameters>] | |
Add-ProvisioningPackage | Apply a provisioning package | Add-ProvisioningPackage [-Path] <string> [-ForceInstall] [-LogsFolder <string>] [-QuietInstall] [-WprpFile <string>] [<CommonParameters>] | |
Remove-ProvisioningPackage | Remove a provisioning package | Remove-ProvisioningPackage -PackageId <string> [-LogsFolder <string>] [-WprpFile <string>] [<CommonParameters>] | |
Remove-ProvisioningPackage -Path <string> [-LogsFolder <string>] [-WprpFile <string>] [<CommonParameters>] | |||
Remove-ProvisioningPackage -AllInstalledPackages [-LogsFolder <string>] [-WprpFile <string>] [<CommonParameters>] | |||
Get-ProvisioningPackage | Get information about an installed provisioning package | Get-ProvisioningPackage -PackageId <string> [-LogsFolder <string>] [-WprpFile <string>] [<CommonParameters>] | |
Get-ProvisioningPackage -Path <string> [-LogsFolder <string>] [-WprpFile <string>] [<CommonParameters>] | |||
Get-ProvisioningPackage -AllInstalledPackages [-LogsFolder <string>] [-WprpFile <string>] [<CommonParameters>] | |||
Export-ProvisioningPackage | Extract the contents of a provisioning package | Export-ProvisioningPackage -PackageId <string> -OutputFolder <string> [-Overwrite] [-AnswerFileOnly] [-LogsFolder <string>] [-WprpFile <string>] [<CommonParameters>] | |
Export-ProvisioningPackage -Path <string> -OutputFolder <string> [-Overwrite] [-AnswerFileOnly] [-LogsFolder <string>] [-WprpFile <string>] [<CommonParameters>] |
Topic | -Description | -
---|---|
- | This section provides information about using the Compatibility Administrator tool. |
-
Managing Application-Compatibility Fixes and Custom Fix Databases |
-This section provides information about managing your application-compatibility fixes and custom-compatibility fix databases. This section explains the reasons for using compatibility fixes and how to deploy custom-compatibility fix databases. |
-
- | You must deploy your customized database (.sdb) files to other computers in your organization before your compatibility fixes, compatibility modes, and AppHelp messages are applied. You can deploy your customized database files in several ways, including by using a logon script, by using Group Policy, or by performing file copy operations. |
-
Topic | +Description | +
---|---|
+ | This section provides information about using the Compatibility Administrator tool. |
+
Managing Application-Compatibility Fixes and Custom Fix Databases |
+This section provides information about managing your application-compatibility fixes and custom-compatibility fix databases. This section explains the reasons for using compatibility fixes and how to deploy custom-compatibility fix databases. |
+
+ | You must deploy your customized database (.sdb) files to other computers in your organization before your compatibility fixes, compatibility modes, and AppHelp messages are applied. You can deploy your customized database files in several ways, including by using a logon script, by using Group Policy, or by performing file copy operations. |
+
Fix | -Fix Description | -
---|---|
8And16BitAggregateBlts |
-Applications that are mitigated by 8/16-bit mitigation can exhibit performance issues. This layer aggregates all the blt operations and improves performance. |
-
8And16BitDXMaxWinMode |
-Applications that use DX8/9 and are mitigated by the 8/16-bit mitigation are run in a maximized windowed mode. This layer mitigates applications that exhibit graphical corruption in full screen mode. |
-
8And16BitGDIRedraw |
-This fix repairs applications that use GDI and that work in 8-bit color mode. The application is forced to repaint its window on RealizePalette. |
-
AccelGdipFlush |
-This fix increases the speed of GdipFlush, which has perf issues in DWM. |
-
AoaMp4Converter |
-This fix resolves a display issue for the AoA Mp4 Converter. |
-
BIOSRead |
-This problem is indicated when an application cannot access the Device\PhysicalMemory object beyond the kernel-mode drivers, on any of the Windows Server® 2003 operating systems. -The fix enables OEM executable (.exe) files to use the GetSystemFirmwareTable function instead of the NtOpenSection function when the BIOS is queried for the \Device\Physical memory information.. |
-
BlockRunasInteractiveUser |
-This problem occurs when InstallShield creates installers and uninstallers that fail to complete and that generate error messages or warnings. -The fix blocks InstallShield from setting the value of RunAs registry keys to InteractiveUser Because InteractiveUser no longer has Administrator rights. -
-Note
-For more detailed information about this application fix, see Using the BlockRunAsInteractiveUser Fix. -
-
- |
-
ChangeFolderPathToXPStyle |
-This fix is required when an application cannot return shell folder paths when it uses the SHGetFolder API. -The fix intercepts the SHGetFolder path request to the common appdata file path and returns the Windows® XP-style file path instead of the Windows Vista-style file path. |
-
ClearLastErrorStatusonIntializeCriticalSection |
-This fix is indicated when an application fails to start. -The fix modifies the InitializeCriticalSection function call so that it checks the NTSTATUS error code, and then sets the last error to ERROR_SUCCESS. |
-
CopyHKCUSettingsFromOtherUsers |
-This problem occurs when an application's installer must run in elevated mode and depends on the HKCU settings that are provided for other users. -The fix scans the existing user profiles and tries to copy the specified keys into the HKEY_CURRENT_USER registry area. -You can control this fix further by entering the relevant registry keys as parameters that are separated by the ^ Symbol; for example:
-Note
-For more detailed information about this application fix, see Using the CopyHKCUSettingsFromOtherUsers Fix. -
-
- |
-
CorrectCreateBrushIndirectHatch |
-The problem is indicated by an access violation error message that displays and when the application fails when you select or crop an image. -The fix corrects the brush style hatch value, which is passed to the CreateBrushIndirect() function and enables the information to be correctly interpreted. |
-
CorrectFilePaths |
-The problem is indicated when an application tries to write files to the hard disk and is denied access or receives a file not found or path not found error message. -The fix modifies the file path names to point to a new location on the hard disk. -
-Note
-For more detailed information about the CorrectFilePaths application fix, see Using the CorrectFilePaths Fix. We recommend that you use this fix together with the CorrectFilePathsUninstall fix if you are applying it to a setup installation file. -
-
- |
-
CorrectFilePathsUninstall |
-This problem occurs when an uninstalled application leaves behind files, directories, and links. -The fix corrects the file paths that are used by the uninstallation process of an application. -
-Note
-For more detailed information about this fix, see Using the CorrectFilePathsUninstall Fix. We recommend that you use this fix together with the CorrectFilePaths fix if you are applying it to a setup installation file. -
-
- |
-
CorrectShellExecuteHWND |
-This problem occurs when you start an executable (.exe) and a taskbar item blinks instead of an elevation prompt being opened, or when the application does not provide a valid HWND value when it calls the ShellExecute(Ex) function. -The fix intercepts the ShellExecute(Ex) calls, and then inspects the HWND value. If the value is invalid, this fix enables the call to use the currently active HWND value. -
-Note
-For more detailed information about the CorrectShellExecuteHWND application fix, see Using the CorrectShellExecuteHWND Fix. -
-
- |
-
CustomNCRender |
-This fix instructs DWM to not render the non-client area, thereby forcing the application to do its own NC rendering. This often gives windows an XP look. |
-
DelayApplyFlag |
-This fix applies a KERNEL, USER, or PROCESS flag if the specified DLL is loaded. -You can control this fix further by typing the following command at the command prompt: -DLL_Name;Flag_Type;Hexidecimal_Value -Where the DLL_Name is the name of the specific DLL, including the file extension. Flag_Type is KERNEL, USER, or PROCESS, and a Hexidecimal_Value, starting with 0x and up to 64-bits long. -
-Note
-The PROCESS flag type can have a 32-bit length only. You can separate multiple entries with a backslash (). -
-
- |
-
DeprecatedServiceShim |
-The problem is indicated when an application tries to install a service that has a dependency on a deprecated service. An error message displays. -The fix intercepts the CreateService function calls and removes the deprecated dependency service from the lpDependencies parameter. -You can control this fix further by typing the following command at the command prompt: -Deprecated_Service\App_Service/Deprecated_Service2 \App_Service2 -Where Deprecated_Service is the name of the service that has been deprecated and App_Service is the name of the specific application service that is to be modified; for example, NtLmSsp\WMI. -
-Note
-If you do not provide an App_Service name, the deprecated service will be removed from all newly created services. -
-
-
-
-Note
-You can separate multiple entries with a forward slash (/). -
-
- |
-
DirectXVersionLie |
-This problem occurs when an application fails because it does not find the correct version number for DirectX®. -The fix modifies the DXDIAGN GetProp function call to return the correct DirectX version. -You can control this fix further by typing the following command at the command prompt: -MAJORVERSION.MINORVERSION.LETTER -For example, |
-
DetectorDWM8And16Bit |
-This fix offeres mitigation for applications that work in 8/16-bit display color mode because these legacy color modes are not supported in Windows 8 . |
-
Disable8And16BitD3D |
-This fix improves performance of 8/16-bit color applications that render using D3D and do not mix directdraw. |
-
Disable8And16BitModes |
-This fix disables 8/16-bit color mitigation and enumeration of 8/16-bit color modes. |
-
DisableDWM |
-The problem occurs when some objects are not drawn or object artifacts remain on the screen in an application. -The fix temporarily disables the Windows Aero menu theme functionality for unsupported applications. -
-Note
-For more detailed information about this application fix, see Using the DisableDWM Fix. -
-
- |
-
DisableFadeAnimations |
-The problem is indicated when an application fade animations, buttons, or other controls do not function properly. -The fix disables the fade animations functionality for unsupported applications. |
-
DisableThemeMenus |
-The problem is indicated by an application that behaves unpredictably when it tries to detect and use the correct Windows settings. -The fix temporarily disables the Windows Aero menu theme functionality for unsupported applications. |
-
DisableWindowsDefender |
-The fix disables Windows Defender for security applications that do not work with Windows Defender. |
-
DWM8And16BitMitigation |
-The fix offers mitigation for applications that work in 8/16-bit display color mode because these legacy color modes are not supported in Windows 8. |
-
DXGICompat |
-The fix allows application-specific compatibility instructions to be passed to the DirectX engine. |
-
DXMaximizedWindowedMode |
-Applications that use DX8/9 are run in a maximized windowed mode. This is required for applications that use GDI/DirectDraw in addition to Direct3D. |
-
ElevateCreateProcess |
-The problem is indicated when installations, de-installations, or updates fail because the host process calls the CreateProcess function and it returns an ERROR_ELEVATION_REQUIRED error message. -The fix handles the error code and attempts to recall the CreateProcess function together with requested elevation. If the fixed application already has a UAC manifest, the error code will be returned unchanged. -
-Note
-For more detailed information about this application fix, see Using the ElevateCreateProcess Fix. -
-
- |
-
EmulateOldPathIsUNC |
-The problem occurs when an application fails because of an incorrect UNC path. -The fix changes the PathIsUNC function to return a value of True for UNC paths in Windows. |
-
EmulateGetDiskFreeSpace |
-The problem is indicated when an application fails to install or to run, and it generates an error message that there is not enough free disk space to install or use the application, even though there is enough free disk space to meet the application requirements. -The fix determines the amount of free space, so that if the amount of free space is larger than 2 GB, the compatibility fix returns a value of 2 GB, but if the amount of free space is smaller than 2 GB, the compatibility fix returns the actual free space amount. -
-Note
-For more detailed information about this application fix, see Using the EmulateGetDiskFreeSpace Fix. -
-
- |
-
EmulateSorting |
-The problem occurs when an application experiences search functionality issues. -The fix forces applications that use the CompareStringW/LCMapString sorting table to use an older version of the table. -
-Note
-For more detailed information about this e application fix, see Using the EmulateSorting Fix. -
-
- |
-
EmulateSortingWindows61 |
-The fix emulates the sorting order of Windows 7 and Windows Server 2008 R2 for various APIs. |
-
EnableRestarts |
-The problem is indicated when an application and computer appear to hang because processes cannot end to allow the computer to complete its restart processes. -The fix enables the computer to restart and finish the installation process by verifying and enabling that the SeShutdownPrivilege service privilege exists. -
-Note
-For more detailed information about this application fix, see Using the EnableRestarts Fix. -
-
- |
-
ExtraAddRefDesktopFolder |
-The problem occurs when an application invokes the Release() method too many times and causes an object to be prematurely destroyed. -The fix counteracts the application's tries to obtain the shell desktop folder by invoking the AddRef() method on the Desktop folder, which is returned by the SHGetDesktopFolder function. |
-
FailObsoleteShellAPIs |
-The problem occurs when an application fails because it generated deprecated API calls. -The fix either fully implements the obsolete functions or implements the obsolete functions with stubs that fail. -
-Note
-You can type FailAll=1 at the command prompt to suppress the function implementation and force all functions to fail. -
-
- |
-
FailRemoveDirectory |
-The problem occurs when an application uninstallation process does not remove all of the application files and folders. -This fix fails calls to RemoveDirectory() when called with a path matching the one specified in the shim command-line. Only a single path is supported. The path can contain environment variables, but must be an exact path – no partial paths are supported. -The fix can resolve an issue where an application expects RemoveDirectory() to delete a folder immediately even though a handle is open to it. |
-
FakeLunaTheme |
-The problem occurs when a theme application does not properly display: the colors are washed out or the user interface is not detailed. -The fix intercepts the GetCurrentThemeName API and returns the value for the Windows XP default theme, (Luna). -
-Note
-For more detailed information about the FakeLunaTheme application fix, see Using the FakeLunaTheme Fix. -
-
- |
-
FlushFile |
-This problem is indicated when a file is updated and changes do not immediately appear on the hard disk. Applications cannot see the file changes. -The fix enables the WriteFile function to call to the FlushFileBuffers APIs, which flush the file cache onto the hard disk. |
-
FontMigration |
-The fix replaces an application-requested font with a better font selection, to avoid text truncation. |
-
ForceAdminAccess |
-The problem occurs when an application fails to function during an explicit administrator check. -The fix allows the user to temporarily imitate being a part of the Administrators group by returning a value of True during the administrator check. -
-Note
-For more detailed information about this application fix, see Using the ForceAdminAccess Fix. -
-
- |
-
ForceInvalidateOnClose |
-The fix invalidates any windows that exist under a closing or hiding window for applications that rely on the invalidation messages. |
-
ForceLoadMirrorDrvMitigation |
-The fix loads the Windows 8 mirror driver mitigation for applications where the mitigation is not automatically applied. |
-
FreestyleBMX |
-The fix resolves an application race condition that is related to window message order. |
-
GetDriveTypeWHook |
-The application presents unusual behavior during installation; for example, the setup program states that it cannot install to a user-specified location. -The fix changes GetDriveType() so that only the root information appears for the file path. This is required when an application passes an incomplete or badly-formed file path when it tries to retrieve the drive type on which the file path exists. |
-
GlobalMemoryStatusLie |
-The problem is indicated by a Computer memory full error message that displays when you start an application. -The fix modifies the memory status structure, so that it reports a swap file that is 400 MB, regardless of the true swap file size. |
-
HandleBadPtr |
-The problem is indicated by an access violation error message that displays because an API is performing pointer validation before it uses a parameter. -The fix supports using lpBuffer validation from the InternetSetOptionA and InternetSetOptionW functions to perform the additional parameter validation. |
-
HandleMarkedContentNotIndexed |
-The problem is indicated by an application that fails when it changes an attribute on a file or directory. -The fix intercepts any API calls that return file attributes and directories that are invoked from the %TEMP% directory, and resets the FILE_ATTRIBUTE_NOT_CONTENT_INDEXED attribute to its original state. |
-
HeapClearAllocation |
-The problem is indicated when the allocation process shuts down unexpectedly. -The fix uses zeros to clear out the heap allocation for an application. |
-
IgnoreAltTab |
-The problem occurs when an application fails to function when special key combinations are used. -The fix intercepts the RegisterRawInputDevices API and prevents the delivery of the WM_INPUT messages. This delivery failure forces the included hooks to be ignored and forces DInput to use Windows-specific hooks. -
-Note
-For more detailed information about this application fix, see Using the IgnoreAltTab Fix. -
-
- |
-
IgnoreChromeSandbox |
-The fix allows Google Chrome to run on systems that have ntdll loaded above 4GB. |
-
IgnoreDirectoryJunction |
-The problem is indicated by a read or access violation error message that displays when an application tries to find or open files. -The fix links the FindNextFileW, FindNextFileA, FindFirstFileExW, FindFirstFileExA, FindFirstFileW and FindFirstFileA APIs to prevent them from returning directory junctions. -
-Note
-Symbolic links appear starting in Windows Vista. -
-
- |
-
IgnoreException |
-The problem is indicated when an application stops functioning immediately after it starts, or the application starts with only a cursor appearing on the screen. -The fix enables the application to ignore specified exceptions. By default, this fix ignores privileged-mode exceptions; however, it can be configured to ignore any exception. -You can control this fix further by typing the following command at the command prompt: -Exception1;Exception2 -Where Exception1 and Exception2 are specific exceptions to be ignored. For example: ACCESS_VIOLATION_READ:1;ACCESS_VIOLATION_WRITE:1. -
-Important
-You should use this compatibility fix only if you are certain that it is acceptable to ignore the exception. You might experience additional compatibility issues if you choose to incorrectly ignore an exception. -
-
-
-
-Note
-For more detailed information about this application fix, see Using the IgnoreException Fix. -
-
- |
-
IgnoreFloatingPointRoundingControl |
-This fix enables an application to ignore the rounding control request and to behave as expected in previous versions of the application. -Before floating point SSE2 support in the C runtime library, the rounding control request was being ignored which would use round to nearest option by default. This shim ignores the rounding control request to support applications relying on old behavior. |
-
IgnoreFontQuality |
-The problem occurs when application text appears to be distorted. -The fix enables color-keyed fonts to properly work with anti-aliasing. |
-
IgnoreMessageBox |
-The problem is indicated by a message box that displays with debugging or extraneous content when the application runs on an unexpected operating system. -The fix intercepts the MessageBox* APIs and inspects them for specific message text. If matching text is found, the application continues without showing the message box. -
-Note
-For more detailed information about this application fix, see Using the IgnoreMessageBox Fix. -
-
- |
-
IgnoreMSOXMLMF |
-The problem is indicated by an error message that states that the operating system cannot locate the MSVCR80D.DLL file. -The fix ignores the registered MSOXMLMF.DLL object, which Microsoft® Office 2007 loads into the operating system any time that you load an XML file, and then it fails the CoGetClassObject for its CLSID. This compatibility fix will just ignore the registered MSOXMLMF and fail the CoGetClassObject for its CLSID. |
-
IgnoreSetROP2 |
-The fix ignores read-modify-write operations on the desktop to avoid performance issues. |
-
InstallComponent |
-The fix prompts the user to install.Net 3.5 or .Net 2.0 because .Net is not included with Windows 8. |
-
LoadLibraryRedirect |
-The fix forces an application to load system versions of libraries instead of loading redistributable versions that shipped with the application. |
-
LocalMappedObject |
-The problem occurs when an application unsuccessfully tries to create an object in the Global namespace. -The fix intercepts the function call to create the object and replaces the word Global with Local. -
-Note
-For more detailed information about this application fix, see Using the LocalMappedObject Fix. -
-
- |
-
MakeShortcutRunas |
-The problem is indicated when an application fails to uninstall because of access-related errors. -The fix locates any RunDLL.exe-based uninstallers and forces them to run with different credentials during the application installation. After it applies this fix, the installer will create a shortcut that specifies a matching string to run during the application installation, thereby enabling the uninstallation to occur later. -
-Note
-For more detailed information about this application fix, see Using the MakeShortcutRunas Fix -
-
- |
-
ManageLinks |
-The fix intercepts common APIs that are going to a directory or to an executable (.exe) file, and then converts any symbolic or directory junctions before passing it back to the original APIs. |
-
MirrorDriverWithComposition |
-The fix allows mirror drivers to work properly with acceptable performance with desktop composition. |
-
MoveToCopyFileShim |
-The problem occurs when an application experiences security access issues during setup. -The fix forces the CopyFile APIs to run instead of the MoveFile APIs. CopyFile APIs avoid moving the security descriptor, which enables the application files to get the default descriptor of the destination folder and prevents the security access issue. |
-
OpenDirectoryAcl |
-The problem is indicated by an error message that states that you do not have the appropriate permissions to access the application. -The fix reduces the security privilege levels on a specified set of files and folders. -
-Note
-For more detailed information about this application fix, see Using the OpenDirectoryACL Fix. -
-
- |
-
PopCapGamesForceResPerf |
-The fix resolves the performance issues in PopCap games like Bejeweled2. The performance issues are visible in certain low-end cards at certain resolutions where the 1024x768 buffer is scaled to fit the display resolution. |
-
PreInstallDriver |
-The fix preinstalls drivers for applications that would otherwise try to install or start drivers during the initial start process. |
-
PreInstallSmarteSECURE |
-The fix preinstalls computer-wide CLSIDs for applications that use SmartSECURE copy protection, which would otherwise try to install the CLSIDs during the initial start process. |
-
ProcessPerfData |
-The problem is indicated by an Unhandled Exception error message because the application tried to read the process performance data registry value to determine if another instance of the application is running. -The fix handles the failure case by passing a fake process performance data registry key, so that the application perceives that it is the only instance running. -
-Note
-This issue seems to occur most frequently with .NET applications. -
-
- |
-
PromoteDAM |
-The fix registers an application for power state change notifications. |
-
PropagateProcessHistory |
-The problem occurs when an application incorrectly fails to apply an application fix. -The fix sets the _PROCESS_HISTORY environment variable so that child processes can look in the parent directory for matching information while searching for application fixes. |
-
ProtectedAdminCheck |
-The problem occurs when an application fails to run because of incorrect Protected Administrator permissions. -The fix addresses the issues that occur when applications use non-standard Administrator checks, thereby generating false positives for user accounts that are being run as Protected Administrators. In this case, the associated SID exists, but it is set as deny-only. |
-
RedirectCRTTempFile |
-The fix intercepts failing CRT calls that try to create a temporary file at the root of the volume, thereby redirecting the calls to a temporary file in the user's temporary directory. |
-
RedirectHKCUKeys |
-The problem occurs when an application cannot be accessed because of User Account Control (UAC) restrictions. -The fix duplicates any newly created HKCU keys to other users' HKCU accounts. This fix is generic for UAC restrictions, whereby the HKCU keys are required, but are unavailable to an application at runtime. |
-
RedirectMP3Codec |
-This problem occurs when you cannot play MP3 files. -The fix intercepts the CoCreateInstance call for the missing filter and then redirects it to a supported version. |
-
RedirectShortcut |
-The problem occurs when an application cannot be accessed by its shortcut, or application shortcuts are not removed during the application uninstallation process. -The fix redirects all of the shortcuts created during the application setup to appear according to a specified path. -
This issue occurs because of UAC restrictions: specifically, when an application setup runs by using elevated privileges and stores the shortcuts according to the elevated user's context. In this situation, a restricted user cannot access the shortcuts. -You cannot apply this fix to an .exe file that includes a manifest and provides a runlevel. |
-
RelaunchElevated |
-The problem occurs when installers, uninstallers, or updaters fail when they are started from a host application. -The fix enables a child .exe file to run with elevated privileges when it is difficult to determine the parent process with either the ElevateCreateProcess fix or by marking the .exe files to RunAsAdmin. -
-Note
-For more detailed information about this application fix, see Using the RelaunchElevated Fix. -
-
- |
-
RetryOpenSCManagerWithReadAccess |
-The problem occurs when an application tries to open the Service Control Manager (SCM) and receives an Access Denied error message. -The fix retries the call and requests a more restricted set of rights that include the following: -
|
-
RetryOpenServiceWithReadAccess |
-The problem occurs when an Unable to open service due to your application using the OpenService() API to test for the existence of a particular service error message displays. -The fix retries the OpenService() API call and verifies that the user has Administrator rights, is not a Protected Administrator, and by using read-only access. Applications can test for the existence of a service by calling the OpenService() API but some applications ask for all access when making this check. This fix retries the call but only asking for read-only access. The user needs to be an administrator for this to work -
-Note
-For more detailed information about this application fix, see Using the RetryOpenServiceWithReadAccess Fix. -
-
- |
-
RunAsAdmin |
-The problem occurs when an application fails to function by using the Standard User or Protected Administrator account. -The fix enables the application to run by using elevated privileges. The fix is the equivalent of specifying requireAdministrator in an application manifest. -
-Note
-For more detailed information about this application fix, see Using the RunAsAdmin Fix. -
-
- |
-
RunAsHighest |
-The problem occurs when administrators cannot view the read/write version of an application that presents a read-only view to standard users. -The fix enables the application to run by using the highest available permissions. This is the equivalent of specifying highestAvailable in an application manifest. -
-Note
-For more detailed information about this application fix, see Using the RunAsHighest Fix. -
-
- |
-
RunAsInvoker |
-The problem occurs when an application is not detected as requiring elevation. -The fix enables the application to run by using the privileges that are associated with the creation process, without requiring elevation. This is the equivalent of specifying asInvoker in an application manifest. -
-Note
-For more detailed information about this application fix, see Using the RunAsInvoker Fix. -
-
- |
-
SecuROM7 |
-The fix repairs applications by using SecuROM7 for copy protection. |
-
SessionShim |
-The fix intercepts API calls from applications that are trying to interact with services that are running in another session, by using the terminal service name prefix (Global or Local) as the parameter. -At the command prompt, you can supply a list of objects to modify, separating the values by a double backslash (). Or, you can choose not to include any parameters, so that all of the objects are modified. -
-Important
-Users cannot log in as Session 0 (Global Session) in Windows Vista and later. Therefore, applications that require access to Session 0 automatically fail. -
-
-
-
-Note
-For more detailed information about this application fix, see Using the SessionShim Fix. -
-
- |
-
SetProtocolHandler |
-The fix registers an application as a protocol handler. -You can control this fix further by typing the following command at the command prompt: -Client;Protocol;App -Where the Client is the name of the email protocol, Protocol is mailto, and App is the name of the application. -
-Note
-Only the mail client and the mailto protocol are supported. You can separate multiple clients by using a backslash (). -
-
- |
-
SetupCommitFileQueueIgnoreWow |
-The problem occurs when a 32-bit setup program fails to install because it requires 64-bit drivers. -The fix disables the Wow64 file system that is used by the 64-bit editions of Windows, to prevent 32-bit applications from accessing 64-bit file systems during the application setup. |
-
SharePointDesigner2007 |
-The fix resolves an application bug that severely slows the application when it runs in DWM. |
-
ShimViaEAT |
-The problem occurs when an application fails, even after applying acompatibility fix that is known to fix an issue. Applications that use unicows.dll or copy protection often present this issue. -The fix applies the specified compatibility fixes by modifying the export table and by nullifying the use of module inclusion and exclusion. -
-Note
-For more information about this application fix, see Using the ShimViaEAT Fix. -
-
- |
-
ShowWindowIE |
-The problem occurs when a web application experiences navigation and display issues because of the tabbing feature. -The fix intercepts the ShowWindow API call to address the issues that can occur when a web application determines that it is in a child window. This fix calls the real ShowWindow API on the top-level parent window. |
-
SierraWirelessHideCDROM |
-The fix repairs the Sierra Wireless Driver installation, thereby preventing bugcheck. |
-
Sonique2 |
-The application uses an invalid window style, which breaks in DWM. This fix replaces the window style with a valid value. |
-
SpecificInstaller |
-The problem occurs when an application installation file fails to be picked up by the GenericInstaller function. -The fix flags the application as being an installer file (for example, setup.exe), and then prompts for elevation. -
-Note
-For more detailed information about this application fix, see Using the SpecificInstaller Fix. -
-
- |
-
SpecificNonInstaller |
-The problem occurs when an application that is not an installer (and has sufficient privileges) generates a false positive from the GenericInstaller function. -The fix flags the application to exclude it from detection by the GenericInstaller function. -
-Note
-For more detailed information about this application fix, see Using the SpecificNonInstaller Fix. -
-
- |
-
SystemMetricsLie |
-The fix replaces SystemMetrics values and SystemParametersInfo values with the values of previous Windows versions. |
-
TextArt |
-The application receives different mouse coordinates with DWM ON versus DWM OFF, which causes the application to hang. This fix resolves the issue. |
-
TrimDisplayDeviceNames |
-The fix trims the names of the display devices that are returned by the EnumDisplayDevices API. |
-
UIPICompatLogging |
-The fix enables the logging of Windows messages from Internet Explorer and other processes. |
-
UIPIEnableCustomMsgs |
-The problem occurs when an application does not properly communicate with other processes because customized Windows messages are not delivered. -The fix enables customized Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the RegisterWindowMessage function, followed by the ChangeWindowMessageFilter function in the code. -You can control this fix further by typing the following command at the command prompt: -MessageString1 MessageString2 -Where MessageString1 and MessageString2 reflect the message strings that can pass. -
-Note
-Multiple message strings must be separated by spaces. For more detailed information about this application fix, see Using the UIPIEnableCustomMsgs Fix. -
-
- |
-
UIPIEnableStandardMsgs |
-The problem occurs when an application does not communicate properly with other processes because standard Windows messages are not delivered. -The fix enables standard Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the ChangeWindowMessageFilter function in the code. -You can control this fix further by typing the following command at the command prompt: -1055 1056 1069 -Where 1055 reflects the first message ID, 1056 reflects the second message ID, and 1069 reflects the third message ID that can pass. -
-Note
-Multiple messages can be separated by spaces. For more detailed information about this application fix, see Using the UIPIEnableStandardMsgs Fix [act]. -
-
- |
-
VirtualizeDeleteFileLayer |
-The fix virtualizes DeleteFile operations for applications that try to delete protected files. |
-
VirtualizeDesktopPainting |
-This fix improves the performance of a number of operations on the Desktop DC while using DWM. |
-
VirtualRegistry |
-The problem is indicated when a Component failed to be located error message displays when an application is started. -The fix enables the registry functions to allow for virtualization, redirection, expansion values, version spoofing, the simulation of performance data counters, and so on. -For more detailed information about this application fix, see Using the VirtualRegistry Fix. |
-
VirtualizeDeleteFile |
-The problem occurs when several error messages display and the application cannot delete files. -The fix makes the application's DeleteFile function call a virtual call in an effort to remedy the UAC and file virtualization issues that were introduced with Windows Vista. This fix also links other file APIs (for example, GetFileAttributes) to ensure that the virtualization of the file is deleted. -
-Note
-For more detailed information about this application fix, see Using the VirtualizeDeleteFile Fix. -
-
- |
-
VirtualizeHKCRLite |
-The problem occurs when an application fails to register COM components at runtime. -The fix redirects the HKCR write calls (HKLM) to the HKCU hive for a per-user COM registration. This operates much like the VirtualRegistry fix when you use the VirtualizeHKCR parameter; however, VirtualizeHKCRLite provides better performance. -HKCR is a virtual merge of the HKCU\Software\Classes and HKLM\Software\Classes directories. The use of HKCU is preferred if an application is not elevated and is ignored if the application is elevated. -You typically will use this compatibility fix in conjunction with the VirtualizeRegisterTypeLib fix. -For more detailed information about this application fix, see Using the VirtualizeHKCRLite Fix. |
-
VirtualizeRegisterTypeLib |
-The fix, when it is used with the VirtualizeHKCRLite fix, ensures that the type library and the COM class registration happen simultaneously. This functions much like the RegistryTypeLib fix when the RegisterTypeLibForUser parameter is used. -
-Note
-For more detailed information about this application fix, see Using the VirtualizeRegisterTypelib Fix. -
-
- |
-
WaveOutIgnoreBadFormat |
-This problem is indicated by an error message that states: Unable to initialize sound device from your audio driver; the application then closes. -The fix enables the application to ignore the format error and continue to function properly. |
-
WerDisableReportException |
-The fix turns off the silent reporting of exceptions to the Windows Error Reporting tool, including those that are reported by Object Linking and Embedding-Database (OLE DB). The fix intercepts the RtlReportException API and returns a STATUS_NOT_SUPPORTED error message. |
-
Win7RTM/Win8RTM |
-The layer provides the application with Windows 7/Windows 8 compatibility mode. |
-
WinxxRTMVersionLie |
-The problem occurs when an application fails because it does not find the correct version number for the required Windows operating system. -All version lie compatibility fixes address the issue whereby an application fails to function because it is checking for, but not finding, a specific version of the operating system. The version lie fix returns the appropriate operating system version information. For example, the VistaRTMVersionLie returns the Windows Vista version information to the application, regardless of the actual operating system version that is running on the computer. |
-
Wing32SystoSys32 |
-The problem is indicated by an error message that states that the WinG library was not properly installed. -The fix detects whether the WinG32 library exists in the correct directory. If the library is located in the wrong location, this fix copies the information (typically during the runtime of the application) into the %WINDIR% \system32 directory. -
-Important
-The application must have Administrator privileges for this fix to work. -
-
- |
-
WinSrv08R2RTM |
-- |
WinXPSP2VersionLie |
-The problem occurs when an application experiences issues because of a VB runtime DLL. -The fix forces the application to follow these steps: -
|
-
WRPDllRegister |
-The application fails when it tries to register a COM component that is released together with Windows Vista and later. -The fix skips the processes of registering and unregistering WRP-protected COM components when calling the DLLRegisterServer and DLLUnregisterServer functions. -You can control this fix further by typing the following command at the command prompt: -Component1.dll;Component2.dll -Where Component1.dll and Component2.dll reflect the components to be skipped. -
-Note
-For more detailed information about this application fix, see Using the WRPDllRegister Fix. -
-
- |
-
WRPMitigation |
-The problem is indicated when an access denied error message displays when the application tries to access a protected operating system resource by using more than read-only access. -The fix emulates the successful authentication and modification of file and registry APIs, so that the application can continue. -
-Note
-For more detailed information about WRPMitigation, see Using the WRPMitigation Fix. -
-
- |
-
WRPRegDeleteKey |
-The problem is indicated by an access denied error message that displays when the application tries to delete a registry key. -The fix verifies whether the registry key is WRP-protected. If the key is protected, this fix emulates the deletion process. |
-
XPAfxIsValidAddress |
-The fix emulates the behavior of Windows XP for MFC42!AfxIsValidAddress. |
-
Compatibility Mode Name | -Description | -Included Compatibility Fixes | -
---|---|---|
WinSrv03 |
-Emulates the Windows Server 2003 operating system. |
-
|
-
WinSrv03Sp1 |
-Emulates the Windows Server 2003 with Service Pack 1 (SP1) operating system. |
-
|
-
Fix | +Fix Description | +
---|---|
8And16BitAggregateBlts |
+Applications that are mitigated by 8/16-bit mitigation can exhibit performance issues. This layer aggregates all the blt operations and improves performance. |
+
8And16BitDXMaxWinMode |
+Applications that use DX8/9 and are mitigated by the 8/16-bit mitigation are run in a maximized windowed mode. This layer mitigates applications that exhibit graphical corruption in full screen mode. |
+
8And16BitGDIRedraw |
+This fix repairs applications that use GDI and that work in 8-bit color mode. The application is forced to repaint its window on RealizePalette. |
+
AccelGdipFlush |
+This fix increases the speed of GdipFlush, which has perf issues in DWM. |
+
AoaMp4Converter |
+This fix resolves a display issue for the AoA Mp4 Converter. |
+
BIOSRead |
+This problem is indicated when an application cannot access the Device\PhysicalMemory object beyond the kernel-mode drivers, on any of the Windows Server® 2003 operating systems. +The fix enables OEM executable (.exe) files to use the GetSystemFirmwareTable function instead of the NtOpenSection function when the BIOS is queried for the \Device\Physical memory information.. |
+
BlockRunasInteractiveUser |
+This problem occurs when InstallShield creates installers and uninstallers that fail to complete and that generate error messages or warnings. +The fix blocks InstallShield from setting the value of RunAs registry keys to InteractiveUser Because InteractiveUser no longer has Administrator rights. +
+Note
+For more detailed information about this application fix, see Using the BlockRunAsInteractiveUser Fix. +
+
+ |
+
ChangeFolderPathToXPStyle |
+This fix is required when an application cannot return shell folder paths when it uses the SHGetFolder API. +The fix intercepts the SHGetFolder path request to the common appdata file path and returns the Windows® XP-style file path instead of the Windows Vista-style file path. |
+
ClearLastErrorStatusonIntializeCriticalSection |
+This fix is indicated when an application fails to start. +The fix modifies the InitializeCriticalSection function call so that it checks the NTSTATUS error code, and then sets the last error to ERROR_SUCCESS. |
+
CopyHKCUSettingsFromOtherUsers |
+This problem occurs when an application's installer must run in elevated mode and depends on the HKCU settings that are provided for other users. +The fix scans the existing user profiles and tries to copy the specified keys into the HKEY_CURRENT_USER registry area. +You can control this fix further by entering the relevant registry keys as parameters that are separated by the ^ Symbol; for example:
+Note
+For more detailed information about this application fix, see Using the CopyHKCUSettingsFromOtherUsers Fix. +
+
+ |
+
CorrectCreateBrushIndirectHatch |
+The problem is indicated by an access violation error message that displays and when the application fails when you select or crop an image. +The fix corrects the brush style hatch value, which is passed to the CreateBrushIndirect() function and enables the information to be correctly interpreted. |
+
CorrectFilePaths |
+The problem is indicated when an application tries to write files to the hard disk and is denied access or receives a file not found or path not found error message. +The fix modifies the file path names to point to a new location on the hard disk. +
+Note
+For more detailed information about the CorrectFilePaths application fix, see Using the CorrectFilePaths Fix. We recommend that you use this fix together with the CorrectFilePathsUninstall fix if you are applying it to a setup installation file. +
+
+ |
+
CorrectFilePathsUninstall |
+This problem occurs when an uninstalled application leaves behind files, directories, and links. +The fix corrects the file paths that are used by the uninstallation process of an application. +
+Note
+For more detailed information about this fix, see Using the CorrectFilePathsUninstall Fix. We recommend that you use this fix together with the CorrectFilePaths fix if you are applying it to a setup installation file. +
+
+ |
+
CorrectShellExecuteHWND |
+This problem occurs when you start an executable (.exe) and a taskbar item blinks instead of an elevation prompt being opened, or when the application does not provide a valid HWND value when it calls the ShellExecute(Ex) function. +The fix intercepts the ShellExecute(Ex) calls, and then inspects the HWND value. If the value is invalid, this fix enables the call to use the currently active HWND value. +
+Note
+For more detailed information about the CorrectShellExecuteHWND application fix, see Using the CorrectShellExecuteHWND Fix. +
+
+ |
+
CustomNCRender |
+This fix instructs DWM to not render the non-client area, thereby forcing the application to do its own NC rendering. This often gives windows an XP look. |
+
DelayApplyFlag |
+This fix applies a KERNEL, USER, or PROCESS flag if the specified DLL is loaded. +You can control this fix further by typing the following command at the command prompt: +DLL_Name;Flag_Type;Hexidecimal_Value +Where the DLL_Name is the name of the specific DLL, including the file extension. Flag_Type is KERNEL, USER, or PROCESS, and a Hexidecimal_Value, starting with 0x and up to 64-bits long. +
+Note
+The PROCESS flag type can have a 32-bit length only. You can separate multiple entries with a backslash (). +
+
+ |
+
DeprecatedServiceShim |
+The problem is indicated when an application tries to install a service that has a dependency on a deprecated service. An error message displays. +The fix intercepts the CreateService function calls and removes the deprecated dependency service from the lpDependencies parameter. +You can control this fix further by typing the following command at the command prompt: +Deprecated_Service\App_Service/Deprecated_Service2 \App_Service2 +Where Deprecated_Service is the name of the service that has been deprecated and App_Service is the name of the specific application service that is to be modified; for example, NtLmSsp\WMI. +
+Note
+If you do not provide an App_Service name, the deprecated service will be removed from all newly created services. +
+
+
+
+Note
+You can separate multiple entries with a forward slash (/). +
+
+ |
+
DirectXVersionLie |
+This problem occurs when an application fails because it does not find the correct version number for DirectX®. +The fix modifies the DXDIAGN GetProp function call to return the correct DirectX version. +You can control this fix further by typing the following command at the command prompt: +MAJORVERSION.MINORVERSION.LETTER +For example, |
+
DetectorDWM8And16Bit |
+This fix offeres mitigation for applications that work in 8/16-bit display color mode because these legacy color modes are not supported in Windows 8 . |
+
Disable8And16BitD3D |
+This fix improves performance of 8/16-bit color applications that render using D3D and do not mix directdraw. |
+
Disable8And16BitModes |
+This fix disables 8/16-bit color mitigation and enumeration of 8/16-bit color modes. |
+
DisableDWM |
+The problem occurs when some objects are not drawn or object artifacts remain on the screen in an application. +The fix temporarily disables the Windows Aero menu theme functionality for unsupported applications. +
+Note
+For more detailed information about this application fix, see Using the DisableDWM Fix. +
+
+ |
+
DisableFadeAnimations |
+The problem is indicated when an application fade animations, buttons, or other controls do not function properly. +The fix disables the fade animations functionality for unsupported applications. |
+
DisableThemeMenus |
+The problem is indicated by an application that behaves unpredictably when it tries to detect and use the correct Windows settings. +The fix temporarily disables the Windows Aero menu theme functionality for unsupported applications. |
+
DisableWindowsDefender |
+The fix disables Windows Defender for security applications that do not work with Windows Defender. |
+
DWM8And16BitMitigation |
+The fix offers mitigation for applications that work in 8/16-bit display color mode because these legacy color modes are not supported in Windows 8. |
+
DXGICompat |
+The fix allows application-specific compatibility instructions to be passed to the DirectX engine. |
+
DXMaximizedWindowedMode |
+Applications that use DX8/9 are run in a maximized windowed mode. This is required for applications that use GDI/DirectDraw in addition to Direct3D. |
+
ElevateCreateProcess |
+The problem is indicated when installations, de-installations, or updates fail because the host process calls the CreateProcess function and it returns an ERROR_ELEVATION_REQUIRED error message. +The fix handles the error code and attempts to recall the CreateProcess function together with requested elevation. If the fixed application already has a UAC manifest, the error code will be returned unchanged. +
+Note
+For more detailed information about this application fix, see Using the ElevateCreateProcess Fix. +
+
+ |
+
EmulateOldPathIsUNC |
+The problem occurs when an application fails because of an incorrect UNC path. +The fix changes the PathIsUNC function to return a value of True for UNC paths in Windows. |
+
EmulateGetDiskFreeSpace |
+The problem is indicated when an application fails to install or to run, and it generates an error message that there is not enough free disk space to install or use the application, even though there is enough free disk space to meet the application requirements. +The fix determines the amount of free space, so that if the amount of free space is larger than 2 GB, the compatibility fix returns a value of 2 GB, but if the amount of free space is smaller than 2 GB, the compatibility fix returns the actual free space amount. +
+Note
+For more detailed information about this application fix, see Using the EmulateGetDiskFreeSpace Fix. +
+
+ |
+
EmulateSorting |
+The problem occurs when an application experiences search functionality issues. +The fix forces applications that use the CompareStringW/LCMapString sorting table to use an older version of the table. +
+Note
+For more detailed information about this e application fix, see Using the EmulateSorting Fix. +
+
+ |
+
EmulateSortingWindows61 |
+The fix emulates the sorting order of Windows 7 and Windows Server 2008 R2 for various APIs. |
+
EnableRestarts |
+The problem is indicated when an application and computer appear to hang because processes cannot end to allow the computer to complete its restart processes. +The fix enables the computer to restart and finish the installation process by verifying and enabling that the SeShutdownPrivilege service privilege exists. +
+Note
+For more detailed information about this application fix, see Using the EnableRestarts Fix. +
+
+ |
+
ExtraAddRefDesktopFolder |
+The problem occurs when an application invokes the Release() method too many times and causes an object to be prematurely destroyed. +The fix counteracts the application's tries to obtain the shell desktop folder by invoking the AddRef() method on the Desktop folder, which is returned by the SHGetDesktopFolder function. |
+
FailObsoleteShellAPIs |
+The problem occurs when an application fails because it generated deprecated API calls. +The fix either fully implements the obsolete functions or implements the obsolete functions with stubs that fail. +
+Note
+You can type FailAll=1 at the command prompt to suppress the function implementation and force all functions to fail. +
+
+ |
+
FailRemoveDirectory |
+The problem occurs when an application uninstallation process does not remove all of the application files and folders. +This fix fails calls to RemoveDirectory() when called with a path matching the one specified in the shim command-line. Only a single path is supported. The path can contain environment variables, but must be an exact path – no partial paths are supported. +The fix can resolve an issue where an application expects RemoveDirectory() to delete a folder immediately even though a handle is open to it. |
+
FakeLunaTheme |
+The problem occurs when a theme application does not properly display: the colors are washed out or the user interface is not detailed. +The fix intercepts the GetCurrentThemeName API and returns the value for the Windows XP default theme, (Luna). +
+Note
+For more detailed information about the FakeLunaTheme application fix, see Using the FakeLunaTheme Fix. +
+
+ |
+
FlushFile |
+This problem is indicated when a file is updated and changes do not immediately appear on the hard disk. Applications cannot see the file changes. +The fix enables the WriteFile function to call to the FlushFileBuffers APIs, which flush the file cache onto the hard disk. |
+
FontMigration |
+The fix replaces an application-requested font with a better font selection, to avoid text truncation. |
+
ForceAdminAccess |
+The problem occurs when an application fails to function during an explicit administrator check. +The fix allows the user to temporarily imitate being a part of the Administrators group by returning a value of True during the administrator check. +
+Note
+For more detailed information about this application fix, see Using the ForceAdminAccess Fix. +
+
+ |
+
ForceInvalidateOnClose |
+The fix invalidates any windows that exist under a closing or hiding window for applications that rely on the invalidation messages. |
+
ForceLoadMirrorDrvMitigation |
+The fix loads the Windows 8 mirror driver mitigation for applications where the mitigation is not automatically applied. |
+
FreestyleBMX |
+The fix resolves an application race condition that is related to window message order. |
+
GetDriveTypeWHook |
+The application presents unusual behavior during installation; for example, the setup program states that it cannot install to a user-specified location. +The fix changes GetDriveType() so that only the root information appears for the file path. This is required when an application passes an incomplete or badly-formed file path when it tries to retrieve the drive type on which the file path exists. |
+
GlobalMemoryStatusLie |
+The problem is indicated by a Computer memory full error message that displays when you start an application. +The fix modifies the memory status structure, so that it reports a swap file that is 400 MB, regardless of the true swap file size. |
+
HandleBadPtr |
+The problem is indicated by an access violation error message that displays because an API is performing pointer validation before it uses a parameter. +The fix supports using lpBuffer validation from the InternetSetOptionA and InternetSetOptionW functions to perform the additional parameter validation. |
+
HandleMarkedContentNotIndexed |
+The problem is indicated by an application that fails when it changes an attribute on a file or directory. +The fix intercepts any API calls that return file attributes and directories that are invoked from the %TEMP% directory, and resets the FILE_ATTRIBUTE_NOT_CONTENT_INDEXED attribute to its original state. |
+
HeapClearAllocation |
+The problem is indicated when the allocation process shuts down unexpectedly. +The fix uses zeros to clear out the heap allocation for an application. |
+
IgnoreAltTab |
+The problem occurs when an application fails to function when special key combinations are used. +The fix intercepts the RegisterRawInputDevices API and prevents the delivery of the WM_INPUT messages. This delivery failure forces the included hooks to be ignored and forces DInput to use Windows-specific hooks. +
+Note
+For more detailed information about this application fix, see Using the IgnoreAltTab Fix. +
+
+ |
+
IgnoreChromeSandbox |
+The fix allows Google Chrome to run on systems that have ntdll loaded above 4GB. |
+
IgnoreDirectoryJunction |
+The problem is indicated by a read or access violation error message that displays when an application tries to find or open files. +The fix links the FindNextFileW, FindNextFileA, FindFirstFileExW, FindFirstFileExA, FindFirstFileW and FindFirstFileA APIs to prevent them from returning directory junctions. +
+Note
+Symbolic links appear starting in Windows Vista. +
+
+ |
+
IgnoreException |
+The problem is indicated when an application stops functioning immediately after it starts, or the application starts with only a cursor appearing on the screen. +The fix enables the application to ignore specified exceptions. By default, this fix ignores privileged-mode exceptions; however, it can be configured to ignore any exception. +You can control this fix further by typing the following command at the command prompt: +Exception1;Exception2 +Where Exception1 and Exception2 are specific exceptions to be ignored. For example: ACCESS_VIOLATION_READ:1;ACCESS_VIOLATION_WRITE:1. +
+Important
+You should use this compatibility fix only if you are certain that it is acceptable to ignore the exception. You might experience additional compatibility issues if you choose to incorrectly ignore an exception. +
+
+
+
+Note
+For more detailed information about this application fix, see Using the IgnoreException Fix. +
+
+ |
+
IgnoreFloatingPointRoundingControl |
+This fix enables an application to ignore the rounding control request and to behave as expected in previous versions of the application. +Before floating point SSE2 support in the C runtime library, the rounding control request was being ignored which would use round to nearest option by default. This shim ignores the rounding control request to support applications relying on old behavior. |
+
IgnoreFontQuality |
+The problem occurs when application text appears to be distorted. +The fix enables color-keyed fonts to properly work with anti-aliasing. |
+
IgnoreMessageBox |
+The problem is indicated by a message box that displays with debugging or extraneous content when the application runs on an unexpected operating system. +The fix intercepts the MessageBox* APIs and inspects them for specific message text. If matching text is found, the application continues without showing the message box. +
+Note
+For more detailed information about this application fix, see Using the IgnoreMessageBox Fix. +
+
+ |
+
IgnoreMSOXMLMF |
+The problem is indicated by an error message that states that the operating system cannot locate the MSVCR80D.DLL file. +The fix ignores the registered MSOXMLMF.DLL object, which Microsoft® Office 2007 loads into the operating system any time that you load an XML file, and then it fails the CoGetClassObject for its CLSID. This compatibility fix will just ignore the registered MSOXMLMF and fail the CoGetClassObject for its CLSID. |
+
IgnoreSetROP2 |
+The fix ignores read-modify-write operations on the desktop to avoid performance issues. |
+
InstallComponent |
+The fix prompts the user to install.Net 3.5 or .Net 2.0 because .Net is not included with Windows 8. |
+
LoadLibraryRedirect |
+The fix forces an application to load system versions of libraries instead of loading redistributable versions that shipped with the application. |
+
LocalMappedObject |
+The problem occurs when an application unsuccessfully tries to create an object in the Global namespace. +The fix intercepts the function call to create the object and replaces the word Global with Local. +
+Note
+For more detailed information about this application fix, see Using the LocalMappedObject Fix. +
+
+ |
+
MakeShortcutRunas |
+The problem is indicated when an application fails to uninstall because of access-related errors. +The fix locates any RunDLL.exe-based uninstallers and forces them to run with different credentials during the application installation. After it applies this fix, the installer will create a shortcut that specifies a matching string to run during the application installation, thereby enabling the uninstallation to occur later. +
+Note
+For more detailed information about this application fix, see Using the MakeShortcutRunas Fix +
+
+ |
+
ManageLinks |
+The fix intercepts common APIs that are going to a directory or to an executable (.exe) file, and then converts any symbolic or directory junctions before passing it back to the original APIs. |
+
MirrorDriverWithComposition |
+The fix allows mirror drivers to work properly with acceptable performance with desktop composition. |
+
MoveToCopyFileShim |
+The problem occurs when an application experiences security access issues during setup. +The fix forces the CopyFile APIs to run instead of the MoveFile APIs. CopyFile APIs avoid moving the security descriptor, which enables the application files to get the default descriptor of the destination folder and prevents the security access issue. |
+
OpenDirectoryAcl |
+The problem is indicated by an error message that states that you do not have the appropriate permissions to access the application. +The fix reduces the security privilege levels on a specified set of files and folders. +
+Note
+For more detailed information about this application fix, see Using the OpenDirectoryACL Fix. +
+
+ |
+
PopCapGamesForceResPerf |
+The fix resolves the performance issues in PopCap games like Bejeweled2. The performance issues are visible in certain low-end cards at certain resolutions where the 1024x768 buffer is scaled to fit the display resolution. |
+
PreInstallDriver |
+The fix preinstalls drivers for applications that would otherwise try to install or start drivers during the initial start process. |
+
PreInstallSmarteSECURE |
+The fix preinstalls computer-wide CLSIDs for applications that use SmartSECURE copy protection, which would otherwise try to install the CLSIDs during the initial start process. |
+
ProcessPerfData |
+The problem is indicated by an Unhandled Exception error message because the application tried to read the process performance data registry value to determine if another instance of the application is running. +The fix handles the failure case by passing a fake process performance data registry key, so that the application perceives that it is the only instance running. +
+Note
+This issue seems to occur most frequently with .NET applications. +
+
+ |
+
PromoteDAM |
+The fix registers an application for power state change notifications. |
+
PropagateProcessHistory |
+The problem occurs when an application incorrectly fails to apply an application fix. +The fix sets the _PROCESS_HISTORY environment variable so that child processes can look in the parent directory for matching information while searching for application fixes. |
+
ProtectedAdminCheck |
+The problem occurs when an application fails to run because of incorrect Protected Administrator permissions. +The fix addresses the issues that occur when applications use non-standard Administrator checks, thereby generating false positives for user accounts that are being run as Protected Administrators. In this case, the associated SID exists, but it is set as deny-only. |
+
RedirectCRTTempFile |
+The fix intercepts failing CRT calls that try to create a temporary file at the root of the volume, thereby redirecting the calls to a temporary file in the user's temporary directory. |
+
RedirectHKCUKeys |
+The problem occurs when an application cannot be accessed because of User Account Control (UAC) restrictions. +The fix duplicates any newly created HKCU keys to other users' HKCU accounts. This fix is generic for UAC restrictions, whereby the HKCU keys are required, but are unavailable to an application at runtime. |
+
RedirectMP3Codec |
+This problem occurs when you cannot play MP3 files. +The fix intercepts the CoCreateInstance call for the missing filter and then redirects it to a supported version. |
+
RedirectShortcut |
+The problem occurs when an application cannot be accessed by its shortcut, or application shortcuts are not removed during the application uninstallation process. +The fix redirects all of the shortcuts created during the application setup to appear according to a specified path. +
This issue occurs because of UAC restrictions: specifically, when an application setup runs by using elevated privileges and stores the shortcuts according to the elevated user's context. In this situation, a restricted user cannot access the shortcuts. +You cannot apply this fix to an .exe file that includes a manifest and provides a runlevel. |
+
RelaunchElevated |
+The problem occurs when installers, uninstallers, or updaters fail when they are started from a host application. +The fix enables a child .exe file to run with elevated privileges when it is difficult to determine the parent process with either the ElevateCreateProcess fix or by marking the .exe files to RunAsAdmin. +
+Note
+For more detailed information about this application fix, see Using the RelaunchElevated Fix. +
+
+ |
+
RetryOpenSCManagerWithReadAccess |
+The problem occurs when an application tries to open the Service Control Manager (SCM) and receives an Access Denied error message. +The fix retries the call and requests a more restricted set of rights that include the following: +
|
+
RetryOpenServiceWithReadAccess |
+The problem occurs when an Unable to open service due to your application using the OpenService() API to test for the existence of a particular service error message displays. +The fix retries the OpenService() API call and verifies that the user has Administrator rights, is not a Protected Administrator, and by using read-only access. Applications can test for the existence of a service by calling the OpenService() API but some applications ask for all access when making this check. This fix retries the call but only asking for read-only access. The user needs to be an administrator for this to work +
+Note
+For more detailed information about this application fix, see Using the RetryOpenServiceWithReadAccess Fix. +
+
+ |
+
RunAsAdmin |
+The problem occurs when an application fails to function by using the Standard User or Protected Administrator account. +The fix enables the application to run by using elevated privileges. The fix is the equivalent of specifying requireAdministrator in an application manifest. +
+Note
+For more detailed information about this application fix, see Using the RunAsAdmin Fix. +
+
+ |
+
RunAsHighest |
+The problem occurs when administrators cannot view the read/write version of an application that presents a read-only view to standard users. +The fix enables the application to run by using the highest available permissions. This is the equivalent of specifying highestAvailable in an application manifest. +
+Note
+For more detailed information about this application fix, see Using the RunAsHighest Fix. +
+
+ |
+
RunAsInvoker |
+The problem occurs when an application is not detected as requiring elevation. +The fix enables the application to run by using the privileges that are associated with the creation process, without requiring elevation. This is the equivalent of specifying asInvoker in an application manifest. +
+Note
+For more detailed information about this application fix, see Using the RunAsInvoker Fix. +
+
+ |
+
SecuROM7 |
+The fix repairs applications by using SecuROM7 for copy protection. |
+
SessionShim |
+The fix intercepts API calls from applications that are trying to interact with services that are running in another session, by using the terminal service name prefix (Global or Local) as the parameter. +At the command prompt, you can supply a list of objects to modify, separating the values by a double backslash (). Or, you can choose not to include any parameters, so that all of the objects are modified. +
+Important
+Users cannot log in as Session 0 (Global Session) in Windows Vista and later. Therefore, applications that require access to Session 0 automatically fail. +
+
+
+
+Note
+For more detailed information about this application fix, see Using the SessionShim Fix. +
+
+ |
+
SetProtocolHandler |
+The fix registers an application as a protocol handler. +You can control this fix further by typing the following command at the command prompt: +Client;Protocol;App +Where the Client is the name of the email protocol, Protocol is mailto, and App is the name of the application. +
+Note
+Only the mail client and the mailto protocol are supported. You can separate multiple clients by using a backslash (). +
+
+ |
+
SetupCommitFileQueueIgnoreWow |
+The problem occurs when a 32-bit setup program fails to install because it requires 64-bit drivers. +The fix disables the Wow64 file system that is used by the 64-bit editions of Windows, to prevent 32-bit applications from accessing 64-bit file systems during the application setup. |
+
SharePointDesigner2007 |
+The fix resolves an application bug that severely slows the application when it runs in DWM. |
+
ShimViaEAT |
+The problem occurs when an application fails, even after applying acompatibility fix that is known to fix an issue. Applications that use unicows.dll or copy protection often present this issue. +The fix applies the specified compatibility fixes by modifying the export table and by nullifying the use of module inclusion and exclusion. +
+Note
+For more information about this application fix, see Using the ShimViaEAT Fix. +
+
+ |
+
ShowWindowIE |
+The problem occurs when a web application experiences navigation and display issues because of the tabbing feature. +The fix intercepts the ShowWindow API call to address the issues that can occur when a web application determines that it is in a child window. This fix calls the real ShowWindow API on the top-level parent window. |
+
SierraWirelessHideCDROM |
+The fix repairs the Sierra Wireless Driver installation, thereby preventing bugcheck. |
+
Sonique2 |
+The application uses an invalid window style, which breaks in DWM. This fix replaces the window style with a valid value. |
+
SpecificInstaller |
+The problem occurs when an application installation file fails to be picked up by the GenericInstaller function. +The fix flags the application as being an installer file (for example, setup.exe), and then prompts for elevation. +
+Note
+For more detailed information about this application fix, see Using the SpecificInstaller Fix. +
+
+ |
+
SpecificNonInstaller |
+The problem occurs when an application that is not an installer (and has sufficient privileges) generates a false positive from the GenericInstaller function. +The fix flags the application to exclude it from detection by the GenericInstaller function. +
+Note
+For more detailed information about this application fix, see Using the SpecificNonInstaller Fix. +
+
+ |
+
SystemMetricsLie |
+The fix replaces SystemMetrics values and SystemParametersInfo values with the values of previous Windows versions. |
+
TextArt |
+The application receives different mouse coordinates with DWM ON versus DWM OFF, which causes the application to hang. This fix resolves the issue. |
+
TrimDisplayDeviceNames |
+The fix trims the names of the display devices that are returned by the EnumDisplayDevices API. |
+
UIPICompatLogging |
+The fix enables the logging of Windows messages from Internet Explorer and other processes. |
+
UIPIEnableCustomMsgs |
+The problem occurs when an application does not properly communicate with other processes because customized Windows messages are not delivered. +The fix enables customized Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the RegisterWindowMessage function, followed by the ChangeWindowMessageFilter function in the code. +You can control this fix further by typing the following command at the command prompt: +MessageString1 MessageString2 +Where MessageString1 and MessageString2 reflect the message strings that can pass. +
+Note
+Multiple message strings must be separated by spaces. For more detailed information about this application fix, see Using the UIPIEnableCustomMsgs Fix. +
+
+ |
+
UIPIEnableStandardMsgs |
+The problem occurs when an application does not communicate properly with other processes because standard Windows messages are not delivered. +The fix enables standard Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the ChangeWindowMessageFilter function in the code. +You can control this fix further by typing the following command at the command prompt: +1055 1056 1069 +Where 1055 reflects the first message ID, 1056 reflects the second message ID, and 1069 reflects the third message ID that can pass. +
+Note
+Multiple messages can be separated by spaces. For more detailed information about this application fix, see Using the UIPIEnableStandardMsgs Fix [act]. +
+
+ |
+
VirtualizeDeleteFileLayer |
+The fix virtualizes DeleteFile operations for applications that try to delete protected files. |
+
VirtualizeDesktopPainting |
+This fix improves the performance of a number of operations on the Desktop DC while using DWM. |
+
VirtualRegistry |
+The problem is indicated when a Component failed to be located error message displays when an application is started. +The fix enables the registry functions to allow for virtualization, redirection, expansion values, version spoofing, the simulation of performance data counters, and so on. +For more detailed information about this application fix, see Using the VirtualRegistry Fix. |
+
VirtualizeDeleteFile |
+The problem occurs when several error messages display and the application cannot delete files. +The fix makes the application's DeleteFile function call a virtual call in an effort to remedy the UAC and file virtualization issues that were introduced with Windows Vista. This fix also links other file APIs (for example, GetFileAttributes) to ensure that the virtualization of the file is deleted. +
+Note
+For more detailed information about this application fix, see Using the VirtualizeDeleteFile Fix. +
+
+ |
+
VirtualizeHKCRLite |
+The problem occurs when an application fails to register COM components at runtime. +The fix redirects the HKCR write calls (HKLM) to the HKCU hive for a per-user COM registration. This operates much like the VirtualRegistry fix when you use the VirtualizeHKCR parameter; however, VirtualizeHKCRLite provides better performance. +HKCR is a virtual merge of the HKCU\Software\Classes and HKLM\Software\Classes directories. The use of HKCU is preferred if an application is not elevated and is ignored if the application is elevated. +You typically will use this compatibility fix in conjunction with the VirtualizeRegisterTypeLib fix. +For more detailed information about this application fix, see Using the VirtualizeHKCRLite Fix. |
+
VirtualizeRegisterTypeLib |
+The fix, when it is used with the VirtualizeHKCRLite fix, ensures that the type library and the COM class registration happen simultaneously. This functions much like the RegistryTypeLib fix when the RegisterTypeLibForUser parameter is used. +
+Note
+For more detailed information about this application fix, see Using the VirtualizeRegisterTypelib Fix. +
+
+ |
+
WaveOutIgnoreBadFormat |
+This problem is indicated by an error message that states: Unable to initialize sound device from your audio driver; the application then closes. +The fix enables the application to ignore the format error and continue to function properly. |
+
WerDisableReportException |
+The fix turns off the silent reporting of exceptions to the Windows Error Reporting tool, including those that are reported by Object Linking and Embedding-Database (OLE DB). The fix intercepts the RtlReportException API and returns a STATUS_NOT_SUPPORTED error message. |
+
Win7RTM/Win8RTM |
+The layer provides the application with Windows 7/Windows 8 compatibility mode. |
+
WinxxRTMVersionLie |
+The problem occurs when an application fails because it does not find the correct version number for the required Windows operating system. +All version lie compatibility fixes address the issue whereby an application fails to function because it is checking for, but not finding, a specific version of the operating system. The version lie fix returns the appropriate operating system version information. For example, the VistaRTMVersionLie returns the Windows Vista version information to the application, regardless of the actual operating system version that is running on the computer. |
+
Wing32SystoSys32 |
+The problem is indicated by an error message that states that the WinG library was not properly installed. +The fix detects whether the WinG32 library exists in the correct directory. If the library is located in the wrong location, this fix copies the information (typically during the runtime of the application) into the %WINDIR% \system32 directory. +
+Important
+The application must have Administrator privileges for this fix to work. +
+
+ |
+
WinSrv08R2RTM |
++ |
WinXPSP2VersionLie |
+The problem occurs when an application experiences issues because of a VB runtime DLL. +The fix forces the application to follow these steps: +
|
+
WRPDllRegister |
+The application fails when it tries to register a COM component that is released together with Windows Vista and later. +The fix skips the processes of registering and unregistering WRP-protected COM components when calling the DLLRegisterServer and DLLUnregisterServer functions. +You can control this fix further by typing the following command at the command prompt: +Component1.dll;Component2.dll +Where Component1.dll and Component2.dll reflect the components to be skipped. +
+Note
+For more detailed information about this application fix, see Using the WRPDllRegister Fix. +
+
+ |
+
WRPMitigation |
+The problem is indicated when an access denied error message displays when the application tries to access a protected operating system resource by using more than read-only access. +The fix emulates the successful authentication and modification of file and registry APIs, so that the application can continue. +
+Note
+For more detailed information about WRPMitigation, see Using the WRPMitigation Fix. +
+
+ |
+
WRPRegDeleteKey |
+The problem is indicated by an access denied error message that displays when the application tries to delete a registry key. +The fix verifies whether the registry key is WRP-protected. If the key is protected, this fix emulates the deletion process. |
+
XPAfxIsValidAddress |
+The fix emulates the behavior of Windows XP for MFC42!AfxIsValidAddress. |
+
Compatibility Mode Name | +Description | +Included Compatibility Fixes | +
---|---|---|
WinSrv03 |
+Emulates the Windows Server 2003 operating system. |
+
|
+
WinSrv03Sp1 |
+Emulates the Windows Server 2003 with Service Pack 1 (SP1) operating system. |
+
|
+
Vendor name |
-Product description |
-HWID |
-Windows Update availability |
-
Broadcom |
-802.11abgn Wireless SDIO adapter |
-sd\vid_02d0&pid_4330&fn_1 |
-Contact the system OEM or Broadcom for driver availability. |
-
Broadcom |
-802.11n Network Adapter |
-pci\ven_14e4&dev_4331&subsys_00d6106b&rev_02 |
-Contact the system OEM or Broadcom for driver availability. |
-
Broadcom |
-802.11n Network Adapter |
-pci\ven_14e4&dev_4331&subsys_00f5106b&rev_02 |
-Contact the system OEM or Broadcom for driver availability. |
-
Broadcom |
-802.11n Network Adapter |
-pci\ven_14e4&dev_4331&subsys_00ef106b&rev_02 |
-Contact the system OEM or Broadcom for driver availability. |
-
Broadcom |
-802.11n Network Adapter |
-pci\ven_14e4&dev_4331&subsys_00f4106b&rev_02 |
-Contact the system OEM or Broadcom for driver availability. |
-
Broadcom |
-802.11n Network Adapter |
-pci\ven_14e4&dev_4331&subsys_010e106b&rev_02 |
-Contact the system OEM or Broadcom for driver availability. |
-
Broadcom |
-802.11n Network Adapter |
-pci\ven_14e4&dev_4331&subsys_00e4106b&rev_02 |
-Contact the system OEM or Broadcom for driver availability. |
-
Broadcom |
-802.11n Network Adapter |
-pci\ven_14e4&dev_4331&subsys_433114e4&rev_02 |
-Contact the system OEM or Broadcom for driver availability. |
-
Broadcom |
-802.11n Network Adapter |
-pci\ven_14e4&dev_4331&subsys_010f106b&rev_02 |
-Contact the system OEM or Broadcom for driver availability. |
-
Marvell |
-Yukon 88E8001/8003/8010 PCI Gigabit Ethernet |
-pci\ven_11ab&dev_4320&subsys_811a1043 |
-- | -
Marvell |
-Libertas 802.11b/g Wireless |
-pci\ven_11ab&dev_1faa&subsys_6b001385&rev_03 |
-- | -
Qualcomm |
-Atheros AR6004 Wireless LAN Adapter |
-sd\vid_0271&pid_0401 |
-
- 64-bit driver not available |
-
Qualcomm |
-Atheros AR5BWB222 Wireless Network Adapter |
-pci\ven_168c&dev_0034&subsys_20031a56 |
-
- 64-bit driver not available |
-
Qualcomm |
-Atheros AR5BWB222 Wireless Network Adapter |
-pci\ven_168c&dev_0034&subsys_020a1028&rev_01 |
-Contact the system OEM or Qualcom for driver availability. |
-
Qualcomm |
-Atheros AR5005G Wireless Network Adapter |
-pci\ven_168c&dev_001a&subsys_04181468&rev_01 |
-- | -
Ralink |
-Wireless-G PCI Adapter |
-pci\ven_1814&dev_0301&subsys_00551737&rev_00 |
-- | -
Ralink |
-Turbo Wireless LAN Card |
-pci\ven_1814&dev_0301&subsys_25611814&rev_00 |
-- | -
Ralink |
-Wireless LAN Card V1 |
-pci\ven_1814&dev_0302&subsys_3a711186&rev_00 |
-- | -
Ralink |
-D-Link AirPlus G DWL-G510 Wireless PCI Adapter(rev.C) |
-pci\ven_1814&dev_0302&subsys_3c091186&rev_00 |
-- | -
Vendor name |
+Product description |
+HWID |
+Windows Update availability |
+
Broadcom |
+802.11abgn Wireless SDIO adapter |
+sd\vid_02d0&pid_4330&fn_1 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_00d6106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_00f5106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_00ef106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_00f4106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_010e106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_00e4106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_433114e4&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Broadcom |
+802.11n Network Adapter |
+pci\ven_14e4&dev_4331&subsys_010f106b&rev_02 |
+Contact the system OEM or Broadcom for driver availability. |
+
Marvell |
+Yukon 88E8001/8003/8010 PCI Gigabit Ethernet |
+pci\ven_11ab&dev_4320&subsys_811a1043 |
++ | +
Marvell |
+Libertas 802.11b/g Wireless |
+pci\ven_11ab&dev_1faa&subsys_6b001385&rev_03 |
++ | +
Qualcomm |
+Atheros AR6004 Wireless LAN Adapter |
+sd\vid_0271&pid_0401 |
+
+ 64-bit driver not available |
+
Qualcomm |
+Atheros AR5BWB222 Wireless Network Adapter |
+pci\ven_168c&dev_0034&subsys_20031a56 |
+
+ 64-bit driver not available |
+
Qualcomm |
+Atheros AR5BWB222 Wireless Network Adapter |
+pci\ven_168c&dev_0034&subsys_020a1028&rev_01 |
+Contact the system OEM or Qualcom for driver availability. |
+
Qualcomm |
+Atheros AR5005G Wireless Network Adapter |
+pci\ven_168c&dev_001a&subsys_04181468&rev_01 |
++ | +
Ralink |
+Wireless-G PCI Adapter |
+pci\ven_1814&dev_0301&subsys_00551737&rev_00 |
++ | +
Ralink |
+Turbo Wireless LAN Card |
+pci\ven_1814&dev_0301&subsys_25611814&rev_00 |
++ | +
Ralink |
+Wireless LAN Card V1 |
+pci\ven_1814&dev_0302&subsys_3a711186&rev_00 |
++ | +
Ralink |
+D-Link AirPlus G DWL-G510 Wireless PCI Adapter(rev.C) |
+pci\ven_1814&dev_0302&subsys_3c091186&rev_00 |
++ | +
Item | -Requirement | -
---|---|
Boot process |
-Capable of USB boot |
-
Firmware |
-USB boot enabled. (PCs certified for use with Windows 7 or later can be configured to boot directly from USB, check with the hardware manufacturer if you are unsure of the ability of your PC to boot from USB) |
-
Processor architecture |
-Must support the image on the Windows To Go drive |
-
External USB Hubs |
-Not supported; connect the Windows To Go drive directly to the host machine |
-
Processor |
-1 Ghz or faster |
-
RAM |
-2 GB or greater |
-
Graphics |
-DirectX 9 graphics device with WDDM 1.2 or greater driver |
-
USB port |
-USB 2.0 port or greater |
-
Host PC Firmware Type | -Host PC Processor Architecture | -Compatible Windows To Go Image Architecture | -
---|---|---|
Legacy BIOS |
-32-bit |
-32-bit only |
-
Legacy BIOS |
-64-bit |
-32-bit and 64-bit |
-
UEFI BIOS |
-32-bit |
-32-bit only |
-
UEFI BIOS |
-64-bit |
-64-bit only |
-
Item | +Requirement | +
---|---|
Boot process |
+Capable of USB boot |
+
Firmware |
+USB boot enabled. (PCs certified for use with Windows 7 or later can be configured to boot directly from USB, check with the hardware manufacturer if you are unsure of the ability of your PC to boot from USB) |
+
Processor architecture |
+Must support the image on the Windows To Go drive |
+
External USB Hubs |
+Not supported; connect the Windows To Go drive directly to the host machine |
+
Processor |
+1 Ghz or faster |
+
RAM |
+2 GB or greater |
+
Graphics |
+DirectX 9 graphics device with WDDM 1.2 or greater driver |
+
USB port |
+USB 2.0 port or greater |
+
Host PC Firmware Type | +Host PC Processor Architecture | +Compatible Windows To Go Image Architecture | +
---|---|---|
Legacy BIOS |
+32-bit |
+32-bit only |
+
Legacy BIOS |
+64-bit |
+32-bit and 64-bit |
+
UEFI BIOS |
+32-bit |
+32-bit only |
+
UEFI BIOS |
+64-bit |
+64-bit only |
+
Details | Originating update | Status | History |
Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. Affected platforms:
Resolution: This issue is resolved in KB4493475. Back to top | OS Build 10240.18132 February 12, 2019 KB4487018 | Resolved KB4493475 | Resolved: April 09, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
Error 1309 when installing/uninstalling MSI or MSP files After installing KB4487018, users may receive “Error 1309” while installing or uninstalling certain types of MSI and MSP files. Affected platforms:
Resolution: This issue is resolved in KB4489872. Back to top | OS Build 10240.18132 February 12, 2019 KB4487018 | Resolved KB4489872 | Resolved: March 12, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
Internet Explorer may fail to load images After installing KB4487018, Internet Explorer may fail to load images with a backslash (\\) in their relative source path. Affected platforms:
Resolution: This issue is resolved in KB4491101. Back to top | OS Build 10240.18132 February 12, 2019 KB4487018 | Resolved KB4491101 | Resolved: February 21, 2019 02:00 PM PT Opened: February 12, 2019 10:00 AM PT |
First character of Japanese era name not recognized After installing KB4487018, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Affected platforms:
Resolution: This issue is resolved in KB4489872. Back to top | OS Build 10240.18132 February 12, 2019 KB4487018 | Resolved KB4489872 | Resolved: March 12, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. Affected platforms:
Resolution: This issue is resolved in KB4489872. Back to top | OS Build 10240.18132 February 12, 2019 KB4487018 | Resolved KB4489872 | Resolved: March 12, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
Summary | Originating update | Status | Date resolved |
Notification issue: \"Your device is missing important security and quality fixes.\" Some users may have incorrectly received the notification \"Your device is missing important security and quality fixes.\" See details > | N/A | Resolved | September 03, 2019 12:32 PM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved KB4512509 | August 19, 2019 02:00 PM PT |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 17134.950 August 13, 2019 KB4512501 | Resolved KB4512509 | August 19, 2019 02:00 PM PT |
Domain connected devices that use MIT Kerberos realms will not start up Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating. See details > | OS Build 17134.915 July 16, 2019 KB4507466 | Resolved KB4512501 | August 13, 2019 10:00 AM PT |
Details | Originating update | Status | History |
Notification issue: \"Your device is missing important security and quality fixes.\" Some users may have incorrectly received the notification \"Your device is missing important security and quality fixes\" in the Windows Update dialog and a red \"!\" in the task tray on the Windows Update tray icon. This notification is intended for devices that are 90 days or more out of date, but some users with installed updates released in June or July also saw this notification. Affected platforms:
Resolution: This issue was resolved on the server side on August 30, 2019. Only devices that are out of date by 90 days or more should now see the notification. No action is required by the user to resolve this issue. If you are still seeing the \"Your device is missing important security and quality fixes\" notification, we recommend selecting Check for Updates in the Windows Update dialog. For instructions, see Update Windows 10. Microsoft always recommends trying to keep your devices up to date, as the monthly updates contain important security fixes. Back to top | N/A | Resolved | Resolved: September 03, 2019 12:32 PM PT Opened: September 03, 2019 12:32 PM PT |
Details | Originating update | Status | History |
Embedded objects may display incorrectly Any compound document (OLE) server application that places embedded objects into the Windows Metafile (WMF) using the PatBlt API may display embedded objects incorrectly. For example, if you paste a Microsoft Excel worksheet object into a Microsoft Word document, the cells may render with a different background color. Affected platforms:
Resolution: This issue is resolved in KB4493509. Back to top | OS Build 17763.316 February 12, 2019 KB4487044 | Resolved KB4493509 | Resolved: April 09, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
Error 1309 when installing/uninstalling MSI or MSP files After installing KB4487044, users may receive \"Error 1309\" while installing or uninstalling certain types of MSI and MSP files. Affected platforms:
Resolution: This issue is resolved in KB4489899. Back to top | OS Build 17763.316 February 12, 2019 KB4487044 | Resolved KB4489899 | Resolved: March 12, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
Internet Explorer may fail to load images After installing KB4487044, Internet Explorer may fail to load images with a backslash (\\) in their relative source path. Affected platforms:
Resolution: This issue is resolved in KB4482887. Back to top | OS Build 17763.316 February 12, 2019 KB4487044 | Resolved KB4482887 | Resolved: March 01, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
First character of the Japanese era name not recognized After installing KB4487044, the first character of the Japanese era name is not recognized as an abbreviation and may cause date parsing issues. Affected platforms:
Resolution: This issue is resolved in KB4482887. Back to top | OS Build 17763.316 February 12, 2019 KB4487044 | Resolved KB4482887 | Resolved: March 01, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
Applications using Microsoft Jet database and Access 95 file format stop working Applications that use a Microsoft Jet database with the Microsoft Access 95 file format may randomly stop working. Affected platforms:
Resolution: This issue is resolved in KB4482887. Back to top | OS Build 17763.316 February 12, 2019 KB4487044 | Resolved KB4482887 | Resolved: March 01, 2019 10:00 AM PT Opened: February 12, 2019 10:00 AM PT |
Details | Originating update | Status | History |
Audio not working on monitors or TV connected to a PC via HDMI, USB, or DisplayPort Upgrade block: Microsoft has identified issues with certain new Intel display drivers. Intel inadvertently released versions of its display driver (versions 24.20.100.6344, 24.20.100.6345) to OEMs that accidentally turned on unsupported features in Windows. As a result, after updating to Windows 10, version 1809, audio playback from a monitor or television connected to a PC via HDMI, USB-C, or a DisplayPort may not function correctly on devices with these drivers. Note: This Intel display driver issue is different from the Intel Smart Sound Technology driver (version 09.21.00.3755) audio issue previously documented. Affected platforms:
Next steps: Intel has released updated drivers to OEM device manufacturers. OEMs need to make the updated driver available via Windows Update. For more information, see the Intel Customer Support article. Resolution: Microsoft has removed the safeguard hold. Back to top | OS Build 17763.134 November 13, 2018 KB4467708 | Resolved | Resolved: May 21, 2019 07:42 AM PT Opened: November 13, 2018 10:00 AM PT |
Shared albums may not sync with iCloud for Windows Upgrade block: Users who attempt to install iCloud for Windows (version 7.7.0.27) will see a message displayed that this version iCloud for Windows isn't supported and the install will fail. Affected platforms:
To ensure a seamless experience, Microsoft is blocking devices with iCloud for Windows (version 7.7.0.27) software installed from being offered Windows 10, version 1809 until this issue has been resolved. We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool from the Microsoft software download website until this issue is resolved. Resolution: Apple has released an updated version of iCloud for Windows (version 7.8.1) that resolves compatibility issues encountered when updating or synching Shared Albums after updating to Windows 10, version 1809. We recommend that you update your iCloud for Windows to version 7.8.1 when prompted before attempting to upgrade to Windows 10, version 1809. You can also manually download the latest version of iCloud for Windows by visiting https://support.apple.com/HT204283. Back to top | OS Build 17763.134 November 13, 2018 KB4467708 | Resolved KB4482887 | Resolved: March 01, 2019 10:00 AM PT Opened: November 13, 2018 10:00 AM PT |
Intel Audio Display (intcdaud.sys) notification during Windows 10 Setup Upgrade block: Microsoft and Intel have identified a compatibility issue with a range of Intel Display Audio device drivers (intcdaud.sys, versions 10.25.0.3 - 10.25.0.8) that may result in excessive processor demand and reduced battery life. As a result, the update process to the Windows 10 October 2018 Update (Windows 10, version 1809) will fail and affected devices will automatically revert to the previous working configuration. Affected platforms:
If you see a \"What needs your attention\" notification during installation of the October 2018 Update, you have one of these affected drivers on your system. On the notification, click Back to remain on your current version of Windows 10. To ensure a seamless experience, we are blocking devices from being offered the October 2018 Update until updated Intel device drivers are installed on your current operating system. We recommend that you do not attempt to manually update to Windows 10, version 1809, using the Update Now button or the Media Creation Tool from the Microsoft Software Download Center until newer Intel device drivers are available with the update. You can either wait for newer drivers to be installed automatically through Windows Update or check with your computer manufacturer for the latest device driver software availability and installation procedures. For more information about this issue, see Intel's customer support guidance. Resolution: This issue was resolved in KB4482887 and the upgrade block removed. Back to top | OS Build 17763.134 November 13, 2018 KB4467708 | Resolved KB4482887 | Resolved: March 01, 2019 10:00 AM PT Opened: November 13, 2018 10:00 AM PT |
F5 VPN clients losing network connectivity Upgrade block: After updating to Windows 10, version 1809, F5 VPN clients may lose network connectivity when the VPN service is in a split tunnel configuration. Affected platforms:
Resolution: This issue was resolved in KB4482887 and the upgrade block removed. Back to top | OS Build 17763.134 November 13, 2018 KB4467708 | Resolved KB4482887 | Resolved: March 01, 2019 10:00 AM PT Opened: November 13, 2018 10:00 AM PT |
Summary | Originating update | Status | Date resolved |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 18362.295 August 13, 2019 KB4512508 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Issues updating when certain versions of Intel storage drivers are installed Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Initiating a Remote Desktop connection may result in black screen When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Domain connected devices that use MIT Kerberos realms will not start up Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved External | August 09, 2019 07:03 PM PT |
Display brightness may not respond to adjustments Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved KB4505903 | July 26, 2019 02:00 PM PT |
RASMAN service may stop working and result in the error “0xc0000005” The Remote Access Connection Manager (RASMAN) service may stop working and result in the error “0xc0000005” with VPN profiles configured as an Always On VPN connection. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4505903 | July 26, 2019 02:00 PM PT |
Details | Originating update | Status | History |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512508, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an \"invalid procedure call error.\" Affected platforms:
Resolution: This issue was resolved in KB4512941. The ‘optional’ update is available on Microsoft Update Catalog, Windows Update, Microsoft Update and Windows Server Update Services (WSUS). As with any 'optional' update, you will need to Check for updates to receive KB4512941 and install. For instructions, see Update Windows 10. Note Windows Update for Business customers should apply the update via Microsoft Update Catalog or Windows Server Update Services (WSUS). Back to top | OS Build 18362.295 August 13, 2019 KB4512508 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: August 14, 2019 03:34 PM PT |
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503293) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.” Affected platforms:
Resolution: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue. Back to top | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved External | Last updated: August 09, 2019 07:03 PM PT Opened: August 09, 2019 04:25 PM PT |
Details | Originating update | Status | History |
Issues updating when certain versions of Intel storage drivers are installed Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903). To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated. Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050. Affected platforms:
Workaround: To mitigate this issue before the safeguard hold is removed, you will need to update the Intel RST drivers for your device to version 15.5.2.1054 or a later. Check with your device manufacturer (OEM) to see if an updated driver is available and install it. You can also download the latest Intel RST drivers directly from Intel at Intel® Rapid Storage Technology (Intel® RST) User Interface and Driver. Once your drivers are updated, you can restart the installation process for Windows 10, version 1903. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903. Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
Initiating a Remote Desktop connection may result in black screen When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU). Affected platforms:
Resolution: This issue was resolved in KB4512941. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 12, 2019 04:42 PM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503293 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512941. Back to top | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 10, 2019 02:51 PM PT |
Domain connected devices that use MIT Kerberos realms will not start up Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected. To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903. Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists: HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms + Affected platforms:
Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
Details | Originating update | Status | History |
Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903. Affected platforms:
Resolution: This issue was resolved in KB4512941. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: May 24, 2019 04:20 PM PT |
Display brightness may not respond to adjustments Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Windows 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change. To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Resolution: This issue was resolved in KB4505903 and the safeguard hold has been removed. Please ensure you have applied the resolving update before attempting to update to the Windows 10 May 2019 Update (version 1903). Please note, it can take up to 48 hours for the safeguard to be removed. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved KB4505903 | Resolved: July 26, 2019 02:00 PM PT Opened: May 21, 2019 07:56 AM PT |
Loss of functionality in Dynabook Smartphone Link app Some users may experience a loss of functionality after updating to Windows 10, version 1903 when using the Dynabook Smartphone Link application on Windows devices. Loss of functionality may affect the display of phone numbers in the Call menu and the ability to answer phone calls on the Windows PC. To safeguard your update experience, we have applied a compatibility hold on devices with Dynabook Smartphone Link from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Resolution: This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Resolved | Resolved: July 11, 2019 01:54 PM PT Opened: May 24, 2019 03:10 PM PT |
Error attempting to update with external USB device or memory card attached If you have an external USB device or SD memory card attached when installing Windows 10, version 1903, you may get an error message stating \"This PC can't be upgraded to Windows 10.\" This is caused by inappropriate drive reassignment during installation. Sample scenario: An update to Windows 10, version 1903 is attempted on a computer that has a thumb drive inserted into its USB port. Before the update, the thumb drive is mounted in the system as drive G based on the existing drive configuration. After the feature update is installed; however, the device is reassigned a different drive letter (e.g., drive H). Note The drive reassignment is not limited to removable drives. Internal hard drives may also be affected. To safeguard your update experience, we have applied a hold on devices with an external USB device or SD memory card attached from being offered Windows 10, version 1903 until this issue is resolved. Affected platforms:
Resolution: This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved | Resolved: July 11, 2019 01:53 PM PT Opened: May 21, 2019 07:38 AM PT |
Summary | Originating update | Status | Date resolved |
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV Windows updates that are SHA-2 signed are not available with Symantec or Norton antivirus program installed See details > | August 13, 2019 KB4512506 | Resolved External | August 27, 2019 02:29 PM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503292 | Resolved KB4512514 | August 17, 2019 02:00 PM PT |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | August 13, 2019 KB4512506 | Resolved KB4517297 | August 16, 2019 02:00 PM PT |
System may be unresponsive after restart with certain McAfee antivirus products Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup. See details > | April 09, 2019 KB4493472 | Resolved External | August 13, 2019 06:59 PM PT |
Details | Originating update | Status | History |
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV Symantec identified the potential for a negative interaction that may occur after Windows Updates code signed with SHA-2 only certificates are installed on devices with Symantec or Norton antivirus programs installed. The software may not correctly identify files included in the update as code signed by Microsoft, putting the device at risk for a delayed or incomplete update. Affected platforms:
Resolution: The safeguard hold has been removed. Symantec has completed its evaluation of the impact of this update and future updates to Windows 7/Windows 2008 R2 and has determined that there is no increased risk of a false positive detection for all in-field versions of Symantec Endpoint Protection and Norton antivirus programs. See the Symantec support article for additional detail and please reach out to Symantec or Norton support if you encounter any issues. Back to top | August 13, 2019 KB4512506 | Resolved External | Last updated: August 27, 2019 02:29 PM PT Opened: August 13, 2019 10:05 AM PT |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512506, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an \"invalid procedure call error.\" Affected platforms:
Resolution: This issue was resolved in KB4517297. The ‘optional’ update is now available on Microsoft Update Catalog and Windows Server Update Services (WSUS). Back to top | August 13, 2019 KB4512506 | Resolved KB4517297 | Resolved: August 16, 2019 02:00 PM PT Opened: August 14, 2019 03:34 PM PT |
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503292) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.” Affected platforms:
Resolution: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue. Back to top | June 11, 2019 KB4503292 | Resolved External | Last updated: August 09, 2019 07:03 PM PT Opened: August 09, 2019 04:25 PM PT |
Details | Originating update | Status | History |
SCVMM cannot enumerate and manage logical switches deployed on the host For hosts managed by System Center Virtual Machine Manager (VMM), VMM cannot enumerate and manage logical switches deployed on the host after installing KB4467684. Additionally, if you do not follow the best practices, a stop error may occur in vfpext.sys on the hosts. Affected platforms:
Resolution: This issue was resolved in KB4507459. Back to top | OS Build 14393.2639 November 27, 2018 KB4467684 | Resolved KB4507459 | Resolved: July 16, 2019 10:00 AM PT Opened: November 27, 2018 10:00 AM PT |
Windows may not start on certain Lenovo and Fujitsu laptops with less than 8GB of RAM After installing KB4467691, Windows may fail to start on certain Lenovo and Fujitsu laptops that have less than 8 GB of RAM. Affected platforms:
Workaround: Restart the affected machine using the Unified Extensible Firmware Interface (UEFI). Disable Secure Boot and then restart. If BitLocker is enabled on your machine, you may have to go through BitLocker recovery after Secure Boot has been disabled. Next steps: Lenovo and Fujitsu are aware of this issue. Please contact your OEM to ask if there is a firmware update available for your device. Back to top | OS Build 14393.2608 November 13, 2018 KB4467691 | Mitigated | Last updated: February 19, 2019 10:00 AM PT Opened: November 13, 2018 10:00 AM PT |
Cluster service may fail if the minimum password length is set to greater than 14 After installing KB4467684, the cluster service may fail to start with the error \"2245 (NERR_PasswordTooShort)\" if the Group Policy \"Minimum Password Length\" is configured with greater than 14 characters. Affected platforms:
Workaround: Set the domain default \"Minimum Password Length\" policy to less than or equal to 14 characters. Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 14393.2639 November 27, 2018 KB4467684 | Mitigated | Last updated: April 25, 2019 02:00 PM PT Opened: November 27, 2018 10:00 AM PT |
Current status as of August 23, 2019: + The Enterprise and Education editions of Windows 10, version 1703 (the Windows 10 Creators Update) will reach end of life on October 9, 2019. The Home, Pro, Pro for Workstations, and IoT Core editions reached end of service on October 8, 2018.
+There is no extended support available for any edition of Windows 10, version 1703. Therefore, it will no longer be supported after October 9, 2019 and will not receive monthly security and quality updates containing protections from the latest security threats. To continue receiving security and quality updates, Microsoft recommends that you update your devices to the latest version of Windows 10. For more information on end of service dates and currently supported versions of Windows 10, see the Windows lifecycle fact sheet. + |
Summary | Originating update | Status | Last updated |
Notification issue: \"Your device is missing important security and quality fixes.\" Some users may have incorrectly received the notification \"Your device is missing important security and quality fixes.\" See details > | N/A | Resolved | September 03, 2019 12:32 PM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 17134.829 June 11, 2019 KB4503286 | Resolved KB4512509 | August 19, 2019 02:00 PM PT |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 17134.950 August 13, 2019 KB4512501 | Resolved KB4512509 | August 19, 2019 02:00 PM PT |
Domain connected devices that use MIT Kerberos realms will not start up Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating. See details > | OS Build 17134.915 July 16, 2019 KB4507466 | Resolved KB4512501 | August 13, 2019 10:00 AM PT |
Details | Originating update | Status | History |
Notification issue: \"Your device is missing important security and quality fixes.\" Some users may have incorrectly received the notification \"Your device is missing important security and quality fixes\" in the Windows Update dialog and a red \"!\" in the task tray on the Windows Update tray icon. This notification is intended for devices that are 90 days or more out of date, but some users with installed updates released in June or July also saw this notification. Affected platforms:
Resolution: This issue was resolved on the server side on August 30, 2019. Only devices that are out of date by 90 days or more should now see the notification. No action is required by the user to resolve this issue. If you are still seeing the \"Your device is missing important security and quality fixes\" notification, we recommend selecting Check for Updates in the Windows Update dialog. For instructions, see Update Windows 10. Microsoft always recommends trying to keep your devices up to date, as the monthly updates contain important security fixes. Back to top | N/A | Resolved | Resolved: September 03, 2019 12:32 PM PT Opened: September 03, 2019 12:32 PM PT |
Details | Originating update | Status | History |
Devices with some Asian language packs installed may receive an error After installing the April 2019 Cumulative Update (KB4493509), devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.\" Affected platforms:
Workaround:
Note: If reinstalling the language pack does not mitigate the issue, reset your PC as follows:
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 17763.437 April 09, 2019 KB4493509 | Mitigated | Last updated: May 03, 2019 10:59 AM PT Opened: May 02, 2019 04:36 PM PT |
Devices with some Asian language packs installed may receive an error After installing the April 2019 Cumulative Update (KB4493509), devices with some Asian language packs installed may receive the error, \"0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.\" Affected platforms:
Workaround:
Note: If reinstalling the language pack does not mitigate the issue, reset your PC as follows:
Next steps: Microsoft is working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 17763.437 April 09, 2019 KB4493509 | Mitigated | Last updated: May 03, 2019 10:59 AM PT Opened: May 02, 2019 04:36 PM PT |
Summary | Originating update | Status | Last updated |
Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Investigating | August 20, 2019 10:50 AM PT |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 18362.295 August 13, 2019 KB4512508 | Investigating | August 17, 2019 01:49 PM PT |
Windows Desktop Search may not return any results and may have high CPU usage Windows Desktop Search may not return any results and SearchUI.exe may have high CPU usage after installing KB4512941. See details > | OS Build 18362.329 August 30, 2019 KB4512941 | Investigating | September 04, 2019 02:25 PM PT |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | OS Build 18362.295 August 13, 2019 KB4512508 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Issues updating when certain versions of Intel storage drivers are installed Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Initiating a Remote Desktop connection may result in black screen When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language was changed between updates See details > | OS Build 18362.116 May 20, 2019 KB4505057 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Domain connected devices that use MIT Kerberos realms will not start up Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | August 30, 2019 10:00 AM PT |
Updates may fail to install and you may receive Error 0x80073701 Installation of updates may fail and you may receive an error, \"Updates Failed, There were problems installing some updates, but we'll try again later\" and \"Error 0x80073701.\" See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | August 16, 2019 04:28 PM PT |
Domain connected devices that use MIT Kerberos realms will not start up Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after updating. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | August 13, 2019 06:59 PM PT |
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved External | August 09, 2019 07:03 PM PT |
Issues updating when certain versions of Intel storage drivers are installed Certain versions of Intel Rapid Storage Technology (Intel RST) drivers may cause updating to Windows 10, version 1903 to fail. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Mitigated External | August 09, 2019 07:03 PM PT |
Intermittent loss of Wi-Fi connectivity Some older devices may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated External | August 01, 2019 08:44 PM PT |
Gamma ramps, color profiles, and night light settings do not apply in some cases Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | August 01, 2019 06:27 PM PT |
Display brightness may not respond to adjustments Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved KB4505903 | July 26, 2019 02:00 PM PT |
RASMAN service may stop working and result in the error “0xc0000005” The Remote Access Connection Manager (RASMAN) service may stop working and result in the error “0xc0000005” with VPN profiles configured as an Always On VPN connection. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4505903 | July 26, 2019 02:00 PM PT |
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU Some apps or games that needs to perform graphics intensive operations may close or fail to open on Surface Book 2 devices with Nvidia dGPU. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | July 16, 2019 09:04 AM PT |
Initiating a Remote Desktop connection may result in black screen When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. See details > | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | July 12, 2019 04:42 PM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | OS Build 18362.175 June 11, 2019 KB4503293 | Mitigated | July 10, 2019 07:09 PM PT |
Unable to discover or connect to Bluetooth devices Microsoft has identified compatibility issues with some versions of Realtek and Qualcomm Bluetooth radio drivers. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:48 PM PT |
Intel Audio displays an intcdaud.sys notification Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in battery drain. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:47 PM PT |
Cannot launch Camera app Microsoft and Intel have identified an issue affecting Intel RealSense SR300 or Intel RealSense S200 camera apps. See details > | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | May 21, 2019 04:47 PM PT |
Details | Originating update | Status | History |
Windows Desktop Search may not return any results and may have high CPU usage Microsoft is getting reports that a small number of users may not receive results when using Windows Desktop Search and may see high CPU usage from SearchUI.exe when searching after installing KB4512941. This issue is only encountered on devices in which searching the web from Windows Desktop Search has been disabled. Affected platforms:
Next steps: We are working on a resolution and estimate a solution will be available in mid-September. Back to top | OS Build 18362.329 August 30, 2019 KB4512941 | Investigating | Last updated: September 04, 2019 02:25 PM PT Opened: September 04, 2019 02:25 PM PT |
Details | Originating update | Status | History |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512508, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an \"invalid procedure call error.\" Affected platforms:
Next steps: Microsoft is working on a resolution and estimates a solution will be available late August. The ‘optional’ update will be available on Microsoft Update Catalog, Windows Update, Microsoft Update and Windows Server Update Services (WSUS). As with any 'optional' update, you will need to Check for updates to receive the update once it is released. Note Windows Update for Business customers should apply the update via Microsoft Update Catalog or Windows Server Update Services (WSUS). Back to top | OS Build 18362.295 August 13, 2019 KB4512508 | Investigating | Last updated: August 17, 2019 01:49 PM PT Opened: August 14, 2019 03:34 PM PT |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512508, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an \"invalid procedure call error.\" Affected platforms:
Resolution: This issue was resolved in KB4512941. The ‘optional’ update is available on Microsoft Update Catalog, Windows Update, Microsoft Update and Windows Server Update Services (WSUS). As with any 'optional' update, you will need to Check for updates to receive KB4512941 and install. For instructions, see Update Windows 10. Note Windows Update for Business customers should apply the update via Microsoft Update Catalog or Windows Server Update Services (WSUS). Back to top | OS Build 18362.295 August 13, 2019 KB4512508 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: August 14, 2019 03:34 PM PT |
Updates may fail to install and you may receive Error 0x80073701 Installation of updates may fail and you may receive the error message, \"Updates Failed, There were problems installing some updates, but we'll try again later\" or \"Error 0x80073701\" on the Windows Update dialog or within Update history. Affected platforms:
Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | Last updated: August 16, 2019 04:28 PM PT Opened: August 16, 2019 01:41 PM PT |
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503293) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.” Affected platforms:
Resolution: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue. Back to top | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved External | Last updated: August 09, 2019 07:03 PM PT Opened: August 09, 2019 04:25 PM PT |
Details | Originating update | Status | History |
Domain connected devices that use MIT Kerberos realms will not start up Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected. To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903. Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists: HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms - Affected platforms:
Next steps: At this time, we suggest that devices in an affected environment do not install KB4497935. We are working on a resolution and estimate a solution will be available in late August. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | Last updated: August 13, 2019 06:59 PM PT Opened: July 25, 2019 06:10 PM PT |
Issues updating when certain versions of Intel storage drivers are installed Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903). To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated. Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050. Affected platforms:
Workaround: To mitigate this issue before the resolution is released, you will need to update the Intel RST drivers for your device to version 15.5.2.1054 or a later. Check with your device manufacturer (OEM) to see if an updated driver is available and install it. You can also download the latest Intel RST drivers directly from Intel at Intel® Rapid Storage Technology (Intel® RST) User Interface and Driver. Once your drivers are updated, you can restart the installation process for Windows 10, version 1903. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903. Note Until an updated driver has been installed, we recommend you do not attempt to manually update using the Update now button or the Media Creation Tool. Next Steps: We are working on a resolution and estimate a solution will be available in late August. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Mitigated External | Last updated: August 09, 2019 07:03 PM PT Opened: July 25, 2019 06:10 PM PT |
Issues updating when certain versions of Intel storage drivers are installed Intel and Microsoft have found incompatibility issues with certain versions of the Intel Rapid Storage Technology (Intel RST) drivers and the Windows 10 May 2019 Update (Windows 10, version 1903). To safeguard your update experience, we have applied a compatibility hold on devices with Intel RST drivers, versions 15.1.0.1002 through version 15.5.2.1053 installed from installing or being offered Windows 10, version 1903 or Windows Server, version 1903, until the driver has been updated. Versions 15.5.2.1054 or later are compatible, and a device that has these drivers installed can install the Windows 10 May 2019 Update. For affected devices, the recommended version is 15.9.8.1050. Affected platforms:
Workaround: To mitigate this issue before the safeguard hold is removed, you will need to update the Intel RST drivers for your device to version 15.5.2.1054 or a later. Check with your device manufacturer (OEM) to see if an updated driver is available and install it. You can also download the latest Intel RST drivers directly from Intel at Intel® Rapid Storage Technology (Intel® RST) User Interface and Driver. Once your drivers are updated, you can restart the installation process for Windows 10, version 1903. Please note, it can take up to 48 hours before you can update to Windows 10, version 1903. Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
Initiating a Remote Desktop connection may result in black screen When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU). Affected platforms:
Resolution: This issue was resolved in KB4512941. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 12, 2019 04:42 PM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503293 on a WDS server. Affected platforms:
Resolution: This issue was resolved in KB4512941. Back to top | OS Build 18362.175 June 11, 2019 KB4503293 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 10, 2019 02:51 PM PT |
Domain connected devices that use MIT Kerberos realms will not start up Devices connected to a domain that is configured to use MIT Kerberos realms will not start up or may continue to restart after installation of KB4497935. Devices that are domain controllers or domain members are both affected. To safeguard your update experience, we have applied a compatibility hold on devices configured to use MIT Kerberos realm from being offered Windows 10, version 1903 or Windows Server, version 1903. Note If you are not sure if your device is affected, contact your administrator. Advanced users can check for “Define interoperable Kerberos v5 realm settings” policy under Computer Configuration -> Policies -> Administrative Templates > System -> Kerberos or check if this registry key exists: HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\Policies\\System\\Kerberos\\MitRealms + Affected platforms:
Resolution: This issue was resolved in KB4512941. The safeguard hold is estimated to be removed in early September. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: July 25, 2019 06:10 PM PT |
The dGPU may occasionally disappear from device manager on Surface Book 2 with dGPU Microsoft has identified a compatibility issue on some Surface Book 2 devices configured with Nvidia discrete graphics processing unit (dGPU). After updating to Windows 10, version 1903 (May 2019 Feature Update), some apps or games that needs to perform graphics intensive operations may close or fail to open. To safeguard your update experience, we have applied a compatibility hold on Surface Book 2 devices with Nvidia dGPUs from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Workaround: To mitigate the issue if you are already on Windows 10, version 1903, you can restart the device or select the Scan for hardware changes button in the Action menu or on the toolbar in Device Manager. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | Last updated: July 16, 2019 09:04 AM PT Opened: July 12, 2019 04:20 PM PT |
Initiating a Remote Desktop connection may result in black screen When initiating a Remote Desktop connection to devices with some older GPU drivers, you may receive a black screen. Any version of Windows may encounter this issue when initiating a Remote Desktop connection to a Windows 10, version 1903 device which is running an affected display driver, including the drivers for the Intel 4 series chipset integrated GPU (iGPU). Affected platforms:
Next steps: We are working on a resolution that will be made available in upcoming release. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Investigating | Last updated: July 12, 2019 04:42 PM PT Opened: July 12, 2019 04:42 PM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) may fail to start with the error \"Status: 0xc0000001, Info: A required device isn't connected or can't be accessed\" after installing KB4503293 on a WDS server. Affected platforms:
Workaround: To mitigate this issue on an SCCM server:
Note Try the default values for TFTP block size and TFTP window size first but depending on your environment and overall settings, you may need to adjust them for your setup. You can also try the Enable a PXE responder without Windows Deployment Service setting. For more information on this setting, see Install and configure distribution points in Configuration Manager. To mitigate this issue on a WDS server without SCCM:
Note Try the default values for RamDiskTFTPBlockSize and RamDiskTFTPWindowSize first but depending on your environment and overall settings, you may need to adjust them for your setup. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.175 June 11, 2019 KB4503293 | Mitigated | Last updated: July 10, 2019 07:09 PM PT Opened: July 10, 2019 02:51 PM PT |
Details | Originating update | Status | History |
RASMAN service may stop working and result in the error “0xc0000005” The Remote Access Connection Manager (RASMAN) service may stop working and you may receive the error “0xc0000005” on devices where the diagnostic data level is manually configured to the non-default setting of 0. You may also receive an error in the Application section of Windows Logs in Event Viewer with Event ID 1000 referencing “svchost.exe_RasMan” and “rasman.dll”. This issue only occurs when a VPN profile is configured as an Always On VPN (AOVPN) connection with or without device tunnel. This does not affect manual only VPN profiles or connections. Affected platforms
Resolution: This issue was resolved in KB4505903. Back to top | OS Build 18362.145 May 29, 2019 KB4497935 | Resolved KB4505903 | Resolved: July 26, 2019 02:00 PM PT Opened: June 28, 2019 05:01 PM PT |
Details | Originating update | Status | History |
Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903. Affected platforms:
Next steps: We are working on a resolution and estimates a solution will be available in late August. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Investigating | Last updated: August 20, 2019 10:50 AM PT Opened: May 24, 2019 04:20 PM PT |
Windows Sandbox may fail to start with error code “0x80070002” Windows Sandbox may fail to start with \"ERROR_FILE_NOT_FOUND (0x80070002)\" on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903. Affected platforms:
Resolution: This issue was resolved in KB4512941. Back to top | OS Build 18362.116 May 20, 2019 KB4505057 | Resolved KB4512941 | Resolved: August 30, 2019 10:00 AM PT Opened: May 24, 2019 04:20 PM PT |
Intermittent loss of Wi-Fi connectivity Some older computers may experience loss of Wi-Fi connectivity due to an outdated Qualcomm driver. An updated Wi-Fi driver should be available from your device manufacturer (OEM). To safeguard your upgrade experience, we have applied a hold on devices with this Qualcomm driver from being offered Windows 10, version 1903, until the updated driver is installed. Affected platforms:
Workaround: Before updating to Windows 10, version 1903, you will need to download and install an updated Wi-Fi driver from your device manufacturer (OEM). Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until a new driver has been installed and the Windows 10, version 1903 feature update has been automatically offered to you. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated External | Last updated: August 01, 2019 08:44 PM PT Opened: May 21, 2019 07:13 AM PT |
Gamma ramps, color profiles, and night light settings do not apply in some cases Microsoft has identified some scenarios where gamma ramps, color profiles and night light settings may stop working. Microsoft has identified some scenarios in which these features may have issues or stop working, for example:
Affected platforms:
Workaround: If you find that your night light has stopped working, try turning the night light off and on, or restarting your computer. For other color setting issues, restart your computer to correct the issue. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: August 01, 2019 06:27 PM PT Opened: May 21, 2019 07:28 AM PT |
Display brightness may not respond to adjustments Microsoft and Intel have identified a driver compatibility issue on devices configured with certain Intel display drivers. After updating to Windows 10, version 1903, brightness settings may sometime appear as if changes applied took effect, yet the actual display brightness doesn't change. To safeguard your update experience, we have applied a compatibility hold on devices with certain Intel drivers from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Resolution: This issue was resolved in KB4505903 and the safeguard hold has been removed. Please ensure you have applied the resolving update before attempting to update to the Windows 10 May 2019 Update (version 1903). Please note, it can take up to 48 hours for the safeguard to be removed. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Resolved KB4505903 | Resolved: July 26, 2019 02:00 PM PT Opened: May 21, 2019 07:56 AM PT |
Unable to discover or connect to Bluetooth devices Microsoft has identified compatibility issues with some driver versions for Bluetooth radios made by Realtek and Qualcomm. To safeguard your update experience, we have applied a compatibility hold on devices with affected driver versions for Realtek or Qualcomm Bluetooth radios from being offered Windows 10, version 1903 or Windows Server, version 1903 until the driver has been updated. Affected platforms:
Workaround: Check with your device manufacturer (OEM) to see if an updated driver is available and install it.
Note Until an updated driver has been installed, we recommend you do not attempt to manually update using the Update now button or the Media Creation Tool. Next steps: Microsoft is working with Realtek and Qualcomm to release new drivers for all affected system via Windows Update. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:48 PM PT Opened: May 21, 2019 07:29 AM PT |
Intel Audio displays an intcdaud.sys notification Microsoft and Intel have identified an issue with a range of Intel Display Audio device drivers that may result in higher than normal battery drain. If you see an intcdaud.sys notification or “What needs your attention” notification when trying to update to Windows 10, version 1903, you have an affected Intel Audio Display device driver installed on your machine (intcdaud.sys, versions 10.25.0.3 through 10.25.0.8). To safeguard your update experience, we have applied a compatibility hold on devices with drivers from being offered Windows 10, version 1903 until updated device drivers have been installed. Affected platforms:
Workaround: On the “What needs your attention\" notification, click the Back button to remain on your current version of Windows 10. (Do not click Confirm as this will proceed with the update and you may experience compatibility issues.) Affected devices will automatically revert to the previous working configuration. For more information, see Intel's customer support guidance and the Microsoft knowledge base article KB4465877. Note We recommend you do not attempt to update your devices until newer device drivers are installed. Next steps: You can opt to wait for newer drivers to be installed automatically through Windows Update or check with the computer manufacturer for the latest device driver software availability and installation procedures. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:47 PM PT Opened: May 21, 2019 07:22 AM PT |
Cannot launch Camera app Microsoft and Intel have identified an issue affecting Intel RealSense SR300 and Intel RealSense S200 cameras when using the Camera app. After updating to the Windows 10 May 2019 Update and launching the Camera app, you may get an error message stating: \"Close other apps, error code: 0XA00F4243.” To safeguard your update experience, we have applied a protective hold on machines with Intel RealSense SR300 or Intel RealSense S200 cameras installed from being offered Windows 10, version 1903, until this issue is resolved. Affected platforms:
Workaround: To temporarily resolve this issue, perform one of the following:
or
or
Note This workaround will only resolve the issue until your next system restart. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. Next steps: We are working on a resolution and will provide an update in an upcoming release. Back to top | OS Build 18362.116 May 21, 2019 KB4505057 | Mitigated | Last updated: May 21, 2019 04:47 PM PT Opened: May 21, 2019 07:20 AM PT |
Summary | Originating update | Status | Last updated |
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV Windows updates that are SHA-2 signed are not available with Symantec or Norton antivirus program installed See details > | August 13, 2019 KB4512506 | Resolved External | August 27, 2019 02:29 PM PT |
Devices starting using PXE from a WDS or SCCM servers may fail to start Devices that start up using Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) may fail to start with error \"0xc0000001.\" See details > | June 11, 2019 KB4503292 | Resolved KB4512514 | August 17, 2019 02:00 PM PT |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error Applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and VBScript may stop responding and you may receive an error. See details > | August 13, 2019 KB4512506 | Resolved KB4517297 | August 16, 2019 02:00 PM PT |
IA64 and x64 devices may fail to start after installing updates After installing updates released on or after August 13, 2019, IA64 and x64 devices using EFI Boot may fail to start. See details > | August 13, 2019 KB4512506 | Mitigated | August 17, 2019 12:59 PM PT |
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV Windows udates that are SHA-2 signed are not available with Symantec or Norton antivirus program installed See details > | August 13, 2019 KB4512506 | Investigating | August 16, 2019 04:28 PM PT |
System may be unresponsive after restart with certain McAfee antivirus products Devices with McAfee Endpoint Security Threat Prevention 10.x, Host Intrusion Prevention 8.0, or VirusScan Enterprise 8.8 may be slow or unresponsive at startup. See details > | April 09, 2019 KB4493472 | Resolved External | August 13, 2019 06:59 PM PT |
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on MacOS when trying to access network shares via CIFS or SMBv1 on Windows devices that installed updates on June 11, 2019 or later. See details > | June 11, 2019 KB4503292 | Resolved External | August 09, 2019 07:03 PM PT |
Details | Originating update | Status | History |
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV Symantec identified the potential for a negative interaction that may occur after Windows Updates code signed with SHA-2 only certificates are installed on devices with Symantec or Norton antivirus programs installed. The software may not correctly identify files included in the update as code signed by Microsoft, putting the device at risk for a delayed or incomplete update. Affected platforms:
Resolution: The safeguard hold has been removed. Symantec has completed its evaluation of the impact of this update and future updates to Windows 7/Windows 2008 R2 and has determined that there is no increased risk of a false positive detection for all in-field versions of Symantec Endpoint Protection and Norton antivirus programs. See the Symantec support article for additional detail and please reach out to Symantec or Norton support if you encounter any issues. Back to top | August 13, 2019 KB4512506 | Resolved External | Last updated: August 27, 2019 02:29 PM PT Opened: August 13, 2019 10:05 AM PT |
Apps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error After installing KB4512506, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an \"invalid procedure call error.\" Affected platforms:
Resolution: This issue was resolved in KB4517297. The ‘optional’ update is now available on Microsoft Update Catalog and Windows Server Update Services (WSUS). Back to top | August 13, 2019 KB4512506 | Resolved KB4517297 | Resolved: August 16, 2019 02:00 PM PT Opened: August 14, 2019 03:34 PM PT |
IA64 and x64 devices may fail to start after installing updates IA64 devices (in any configuration) and x64 devices using EFI boot that were provisioned after the July 9th updates and/or skipped the recommended update (KB3133977), may fail to start with the following error: \"File: \\Windows\\system32\\winload.efi Status: 0xc0000428 Info: Windows cannot verify the digital signature for this file.\" Affected platforms:
Take Action: To resolve this issue please follow the steps outlined in the SHA-2 support FAQ article for error code 0xc0000428. Back to top | August 13, 2019 KB4512506 | Mitigated | Last updated: August 17, 2019 12:59 PM PT Opened: August 13, 2019 08:34 AM PT |
Windows updates that are SHA-2 signed may not be offered for Symantec and Norton AV Symantec has identified an issue that occurs when a device is running any Symantec or Norton antivirus program and installs updates for Windows that are signed with SHA-2 certificates only. The Windows updates are blocked or deleted by the antivirus program during installation, which may then cause Windows to stop working or fail to start. Affected platforms:
Workaround: Guidance for Symantec customers can be found in the Symantec support article and the Norton support article. Next steps: To safeguard your update experience, Microsoft and Symantec have partnered to place a safeguard hold on devices with an affected version of Symantec Antivirus or Norton Antivirus installed to prevent them from receiving this type of Windows update until a solution is available. We recommend that you do not manually install affected updates until a solution is available. Please reach out to Symantec or Norton support for further guidance. Back to top | August 13, 2019 KB4512506 | Investigating | Last updated: August 16, 2019 04:28 PM PT Opened: August 13, 2019 10:05 AM PT |
MacOS may be unable to access network shares via CIFS or SMBv1 on Windows devices You may receive an error on your Apple MacOS device when trying to access network shares via CIFS or SMBv1 on a Windows devices that has installed updates on June 11, 2019 (KB4503292) or later. When you encounter this issue, in MacOS you may receive the error, “There was a problem connecting to the server “{Server Host Name}”. Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator.” Affected platforms:
Resolution: For guidance on this issue, see the Apple support article If your Mac can't use NTLM to connect to a Windows server. There is no update for Windows needed for this issue. Back to top | June 11, 2019 KB4503292 | Resolved External | Last updated: August 09, 2019 07:03 PM PT Opened: August 09, 2019 04:25 PM PT |
Message | Date | |
Resolved: Delays starting Internet Explorer 11 On August 16, 2019 at 7:16 AM a server required for downloading the Internet Explorer 11 (IE11) startup page, went down. As a result of the server outage, IE 11 became unresponsive for some customers who had not yet installed the August 2019 security updates. Customers who had the August 2019 security update installed were not affected. In order to ensure your devices remain in a serviced and secure state, we recommend you install the latest monthly update. This issue was resolved on the server side at 1:00 pm PST. | August 16, 2019 04:00 PM PT | |
Status update: Windows 10, version 1903 \"D\" optional release available August 30th The August optional monthly “D” release for Windows 10, version 1903 is now available. Follow @WindowsUpdate for the latest on the availability of this release. | August 30, 2019 08:00 AM PT | |
Feature update install notification on Windows 10, version 1809 (the October 2018 Update) We've had reports on August 29th that some customers running Windows 10, version 1809 (the October 2018 Update) have received notification to install the latest feature update (version 1903) early. Updating remains in your control. To install the update, you must select one of the following options: \"Pick a Time\", \"Restart Tonight,\" or \"Restart Now\". If you are not ready to update at this time, simply dismiss the notification by clicking the arrow in the top right corner. If you have updated to Windows 10, version 1903 and would like to go back to your previous version, see the instructions here. | August 29, 2019 04:39 PM PT | |
Take Action: Internet Explorer 11 now available on Windows Update/WSUS for Windows Server 2012 and Windows Embedded 8 Standard Internet Explorer 11 (KB 4492872) is now available via Windows Update (WU) and Windows Server Update Services (WSUS) for commercial customers running Windows Server 2012 and Windows Embedded 8 Standard. For details about these changes and end of support for IE10, please refer to the IT Pro blog. | August 29, 2019 08:00 AM PT | |
Take action: SHA-2 code signing support guidance for Windows 7 SP1 and Windows Server 2008 RS2 SP1 Windows 7 SP1 and Windows Server 2008 R2 SP1 update signatures are now SHA-2 based signatures and requires that SHA-2 support to be installed. For important customer guidance on installation and troubleshooting tips, please read the knowledge base article 2019 SHA-2 Code Signing Support requirement for Windows and WSUS. | August 23, 2019 03:35 PM PT | |
Take action: Windows 10, version 1703 (the Windows 10 Creators Update) reaches end of life on October 9, 2019 The Enterprise and Education editions of Windows 10, version 1703 (the Windows 10 Creators Update) will reach end of life on October 9, 2019. The Home, Pro, Pro for Workstations, and IoT Core editions reached end of service on October 8, 2018. There is no extended support available for any edition of Windows 10, version 1703. Therefore, it will no longer be supported after October 9, 2019 and will not receive monthly security and quality updates containing protections from the latest security threats. To continue receiving security and quality updates, Microsoft recommends that you update your devices to the latest version of Windows 10. For more information on end of service dates and currently supported versions of Windows 10, see the Windows lifecycle fact sheet. | August 23, 2019 02:17 PM PT | |
Resolved: Delays starting Internet Explorer 11 On August 16, 2019 at 7:16 AM a server required for downloading the Internet Explorer 11 (IE11) startup page, went down. As a result of the server outage, IE 11 became unresponsive for some customers who had not yet installed the August 2019 security updates. Customers who had the August 2019 security update installed were not affected. In order to ensure your devices remain in a serviced and secure state, we recommend you install the latest monthly update. This issue was resolved on the server side at 1:00 pm PST. | August 16, 2019 04:00 PM PT | |
August 2019 security update now available for Windows 10, version 1903 and all supported versions of Windows The August 2019 security update release, referred to as our “B” release, is now available for Windows 10, version 1903 and all supported versions of Windows. A “B” release is the primary, regular update event for each month and is the only regular release that contains security fixes. As a result, we recommend that you install these updates promptly. For more information on the different types of monthly quality updates, see our Windows 10 update servicing cadence primer. To be informed about the latest updates and releases, follow us on Twitter @WindowsUpdate. | August 13, 2019 10:00 AM PT | |
Advisory: Bluetooth encryption key size vulnerability disclosed (CVE-2019-9506) On August 13, 2019, Microsoft released security updates to address a Bluetooth key length encryption vulnerability. To exploit this vulnerability, an attacker would need specialized hardware and would be limited by the signal range of the Bluetooth devices in use. For more information about this industry-wide issue, see CVE-2019-9506 | Bluetooth Encryption Key Size Vulnerability in the Microsoft Security Update Guide and important guidance for IT pros in KB4514157. (Note: we are documenting this vulnerability together with guidance for IT admins as part of a coordinated industry disclosure effort.) | August 13, 2019 10:00 AM PT | |
Advisory: Windows Advanced Local Procedure Call Elevation of Privilege vulnerability disclosed (CVE-2019-1162) On August 13, 2019, Google Project Zero (GPZ) disclosed an Elevation of Privilege (EoP) vulnerability in how Windows handles calls to Advanced Local Procedure Call (ALPC) that affects Windows operating systems, versions 8.1 and higher. An attacker must already have code execution on the target system to leverage these vulnerabilities. Microsoft released security updates on August 13, 2019 that partially address this issue. Other items disclosed by GPZ require more time to address and we are working to release a resolution in mid-September. For more information, see CVE-2019-1162 | Windows ALPC Elevation of Privilege Vulnerability | August 13, 2019 10:00 AM PT | |
Take action: Install required updates for Windows 7 SP1 and Windows Server 2008 RS2 SP1 for SHA-2 code sign support As of August 13, 2019, Windows 7 SP1 and Windows Server 2008 R2 SP1 updates signatures only support SHA-2 code signing. As outlined in 2019 SHA-2 Code Signing Support requirement for Windows and WSUS, we are requiring that SHA-2 code signing support be installed. If you have Windows Update enabled and have applied the security updates released in March 2019 (KB4490628) and August 2019 (KB4474419), you are protected automatically; no further configuration is necessary. If you have not installed the March 2019 updates, you will need to do so in order to continue to receive updates on devices running Windows 7 SP1 and Windows Server 2008 R2 SP1. | August 13, 2019 10:00 AM PT | |
Take action: Windows 10, version 1803 (the April 2018 Update) reaches end of service on November 12, 2019 Windows 10, version 1803 (the April 2018 Update) will reach end of service on November 12, 2019 for Home and Pro editions. We will begin updating devices running Windows 10, version 1803 to Windows 10, version 1903 (the May 2019 Update) starting July 16, 2019 to help ensure that these devices remain in a serviced and secure state. For more information, see the Windows 10, version 1903 section of the Windows release health dashboard. | August 13, 2019 10:00 AM PT | |
Advisory: Windows Kernel Information Disclosure Vulnerability (CVE-2019-1125) On July 9, 2019, Microsoft released a security update for a Windows kernel information disclosure vulnerability (CVE-2019-1125). Customers who have Windows Update enabled and have applied the security updates released on July 9, 2019 are protected automatically; no further configuration is necessary. For more information, see CVE-2019-1125 | Windows Kernel Information Disclosure Vulnerability in the Microsoft Security Update Guide. (Note: we are documenting this mitigation publicly today, instead of back in July, as part of a coordinated industry disclosure effort.) | August 06, 2019 10:00 AM PT | |
Resolved August 1, 2019 16:00 PT: Microsoft Store users may encounter blank screens when clicking on certain buttons Some customers running the version of the Microsoft Store app released on July 29, 2019 encountered a blank screen when selecting “Switch out of S mode,” “Get Genuine,” or some “Upgrade to [version]” OS upgrade options. This issue has now been resolved and a new version of the Microsoft Store app has been released. Users who encountered this issue will need to update the Microsoft Store app on their device. If you are still encountering an issue, please see Fix problems with apps from Microsoft Store. | August 01, 2019 02:00 PM PT | |
Reminder: Windows 10 update servicing cadence This month we received questions about the cadence of updates we released in April and May 2019. Here's a quick recap of our releases and servicing cadence:
| May 10, 2019 10:00 AM PT | The AIK certificate is no longer valid | Sign out and then sign in again. | -
0x801C044D | +||
0x801C03F2 | +Windows Hello key registration failed. | +ERROR_BAD_DIRECTORY_REQUEST. Another object with the same value for property proxyAddresses already exists. To resolve the issue refer to Duplicate Attributes Prevent Dirsync. | +
0x801C044D | Unable to obtain user token | Sign out and then sign in again. Check network and credentials. |
0x801C044E | Failed to receive user creds input | Sign out and then sign in again. | diff --git a/windows/security/identity-protection/hello-for-business/hello-how-it-works-provisioning.md b/windows/security/identity-protection/hello-for-business/hello-how-it-works-provisioning.md index 9a2711dc1c..c876fbd351 100644 --- a/windows/security/identity-protection/hello-for-business/hello-how-it-works-provisioning.md +++ b/windows/security/identity-protection/hello-for-business/hello-how-it-works-provisioning.md @@ -32,6 +32,8 @@ Windows Hello for Business provisioning enables a user to enroll a new, strong, [Domain joined provisioning in an On-premises Key Trust deployment](#domain-joined-provisioning-in-an-on-premises-key-trust-deployment)