mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-17 11:23:45 +00:00
CI Update
This commit is contained in:
@ -19,12 +19,12 @@ ms.topic: article
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
The Compatibility Administrator tool provides a way to query your custom-compatibility databases.
|
||||
|
||||
@ -136,7 +136,7 @@ The following table shows the attributes you can use for querying your customize
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
## Available Operators
|
||||
|
||||
@ -200,11 +200,10 @@ The following table shows the operators that you can use for querying your custo
|
||||
<td align="left"><p>A special SQL operator used to check if the left-hand operand contains a substring specified by the right-hand operand.</p></td>
|
||||
<td align="left"><p><strong>Left-hand operand</strong>. MATCHFILE_NAME, MODE_NAME, FIX_NAME</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Only the HAS operator can be applied to the MATCHFILE_NAME, MODE_NAME, and FIX_NAME attributes.</p>
|
||||
<strong>Note</strong><br/><p>Only the HAS operator can be applied to the MATCHFILE_NAME, MODE_NAME, and FIX_NAME attributes.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div>
|
||||
<p><strong>Right-hand operand</strong>. String</p></td>
|
||||
<td align="left"><p>1</p></td>
|
||||
@ -224,14 +223,14 @@ The following table shows the operators that you can use for querying your custo
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
[Using the Compatibility Administrator Tool](using-the-compatibility-administrator-tool.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -25,6 +25,7 @@ The topics in this library have been updated for Windows 10, version 1703 (also
|
||||
- [Windows 10 Enterprise - FAQ for IT Professionals](windows-10-enterprise-faq-itpro.md)
|
||||
|
||||
## January 2017
|
||||
|
||||
| New or changed topic | Description |
|
||||
|----------------------|-------------|
|
||||
| [Windows 10 Infrastructure Requirements](windows-10-infrastructure-requirements.md) | Added link for Windows Server 2008 R2 and Windows 7 activation and a link to Windows Server 2016 Volume Activation Tips |
|
||||
@ -64,7 +65,7 @@ The topics in this library have been updated for Windows 10, version 1607 (also
|
||||
| New or changed topic | Description |
|
||||
|--------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
|
||||
| [Application Compatibility Toolkit (ACT) Technical Reference](act-technical-reference.md) (multiple topics) | New |
|
||||
|
||||
|
||||
|
||||
## November 2015
|
||||
|
||||
@ -75,7 +76,7 @@ The topics in this library have been updated for Windows 10, version 1607 (also
|
||||
| [Windows Update for Business](../update/waas-manage-updates-wufb.md) (multiple topics) | New |
|
||||
| [Windows To Go: feature overview](windows-to-go-overview.md) (multiple topics) | Updated |
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
@ -85,9 +86,9 @@ The topics in this library have been updated for Windows 10, version 1607 (also
|
||||
[Change history for Deploy Windows 10](../change-history-for-deploy-windows-10.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -41,7 +41,7 @@ The following flowchart shows the steps for using the Compatibility Administrato
|
||||
**Important**
|
||||
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create and work with custom databases for 32-bit applications, and the 64-bit version to create and work with custom databases for 64-bit applications.
|
||||
|
||||
|
||||
|
||||
|
||||
## In this section
|
||||
|
||||
@ -59,25 +59,25 @@ Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version o
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Using the Compatibility Administrator Tool](using-the-compatibility-administrator-tool.md)</p></td>
|
||||
<td align="left"><p><a href="using-the-compatibility-administrator-tool.md" data-raw-source="[Using the Compatibility Administrator Tool](using-the-compatibility-administrator-tool.md)">Using the Compatibility Administrator Tool</a></p></td>
|
||||
<td align="left"><p>This section provides information about using the Compatibility Administrator tool.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Managing Application-Compatibility Fixes and Custom Fix Databases](managing-application-compatibility-fixes-and-custom-fix-databases.md)</p></td>
|
||||
<td align="left"><p><a href="managing-application-compatibility-fixes-and-custom-fix-databases.md" data-raw-source="[Managing Application-Compatibility Fixes and Custom Fix Databases](managing-application-compatibility-fixes-and-custom-fix-databases.md)">Managing Application-Compatibility Fixes and Custom Fix Databases</a></p></td>
|
||||
<td align="left"><p>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.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Using the Sdbinst.exe Command-Line Tool](using-the-sdbinstexe-command-line-tool.md)</p></td>
|
||||
<td align="left"><p><a href="using-the-sdbinstexe-command-line-tool.md" data-raw-source="[Using the Sdbinst.exe Command-Line Tool](using-the-sdbinstexe-command-line-tool.md)">Using the Sdbinst.exe Command-Line Tool</a></p></td>
|
||||
<td align="left"><p>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.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -19,12 +19,12 @@ ms.topic: article
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
After you determine that you will use compatibility fixes in your application-compatibility mitigation strategy, you must define a strategy to manage your custom compatibility-fix database. Typically, you can use one of two approaches:
|
||||
|
||||
@ -101,10 +101,10 @@ If you decide to use the centralized compatibility-fix database deployment strat
|
||||
|
||||
5. The team that manages the centralized database opens Custom DB1 and uses the Compatibility Administrator to include the new compatibility fixes that were included in Custom DB2.
|
||||
|
||||
**Note**
|
||||
**Note**
|
||||
Custom DB1 contains a unique GUID that makes updating the database easier. For example, if you install a new version of the custom compatibility-fix database that uses the same GUID as the previous version, the computer will automatically uninstall the old version.
|
||||
|
||||
|
||||
|
||||
|
||||
6. The centralized management team then redeploys the new version of Custom DB1 to all of the end users in your organization.
|
||||
|
||||
@ -122,23 +122,25 @@ In order to meet the two requirements above, we recommend that you use one of th
|
||||
|
||||
You can package your .sdb file and a custom deployment script into an .msi file, and then deploy the .msi file into your organization.
|
||||
|
||||
**Important**
|
||||
**Important**
|
||||
You must ensure that you mark your custom script so that it does not impersonate the calling user. For example, if you use Microsoft® Visual Basic® Scripting Edition (VBScript), the custom action type would be:
|
||||
|
||||
|
||||
|
||||
``` syntax
|
||||
msidbCustomActionTypeVBScript + msidbCustomActionTypeInScript + msidbCustomActionTypeNoImpersonate = 0x0006 + 0x0400 + 0x0800 = 0x0C06 = 3078 decimal)
|
||||
```
|
||||
|
||||
~~~
|
||||
``` syntax
|
||||
msidbCustomActionTypeVBScript + msidbCustomActionTypeInScript + msidbCustomActionTypeNoImpersonate = 0x0006 + 0x0400 + 0x0800 = 0x0C06 = 3078 decimal)
|
||||
```
|
||||
~~~
|
||||
|
||||
- **Using a network share and a custom script**
|
||||
|
||||
You can store your .sdb file on your network share and then call to a script that resides on your specified computers.
|
||||
|
||||
**Important**
|
||||
**Important**
|
||||
You must ensure that you call the script at a time when it will receive elevated rights. For example, you should call the script by using computer startup scripts instead of a user logon script. You must also ensure that the installation of the custom compatibility-fix database occurs with Administrator rights.
|
||||
|
||||
|
||||
|
||||
|
||||
### Example Script for an Installation of the .sdb File based on an .msi File
|
||||
|
||||
|
@ -19,26 +19,26 @@ ms.topic: article
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
You can fix some compatibility issues that are due to the changes made between Windows operating system versions. These issues can include User Account Control (UAC) restrictions.
|
||||
|
||||
**Important**
|
||||
**Important**
|
||||
The Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator. You must use the 32-bit version for 32-bit applications and the 64-bit version to work for 64-bit applications. You will receive an error message if you try to use the wrong version.
|
||||
|
||||
If you start the Compatibility Administrator as an Administrator (with elevated privileges), all repaired applications can run successfully; however, virtualization and redirection might not occur as expected. To verify that a compatibility fix addresses an issue, you must test the repaired application by running it under the destination user account.
|
||||
|
||||
|
||||
|
||||
|
||||
## Compatibility Fixes
|
||||
|
||||
|
||||
The following table lists the known compatibility fixes for all Windows operating systems that have been released from Windows Vista through Windows 10. The fixes are listed in alphabetical order.
|
||||
The following table lists the known compatibility fixes for all Windows operating systems that have been released from Windows Vista through Windows 10. The fixes are listed in alphabetical order.
|
||||
|
||||
<table>
|
||||
<colgroup>
|
||||
@ -74,25 +74,24 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>BIOSRead</p></td>
|
||||
<td align="left"><p>This problem is indicated when an application cannot access the <strong>Device\PhysicalMemory</strong> object beyond the kernel-mode drivers, on any of the Windows Server® 2003 operating systems.</p>
|
||||
<p>The fix enables OEM executable (.exe) files to use the GetSystemFirmwareTable function instead of the NtOpenSection function when the BIOS is queried for the <strong>\\Device\Physical</strong> memory information..</p></td>
|
||||
<td align="left"><p>This problem is indicated when an application cannot access the <strong>Device\PhysicalMemory</strong> object beyond the kernel-mode drivers, on any of the Windows Server® 2003 operating systems.</p>
|
||||
<p>The fix enables OEM executable (.exe) files to use the GetSystemFirmwareTable function instead of the NtOpenSection function when the BIOS is queried for the <strong>\Device\Physical</strong> memory information..</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>BlockRunasInteractiveUser</p></td>
|
||||
<td align="left"><p>This problem occurs when <strong>InstallShield</strong> creates installers and uninstallers that fail to complete and that generate error messages or warnings.</p>
|
||||
<p>The fix blocks <strong>InstallShield</strong> from setting the value of <strong>RunAs</strong> registry keys to InteractiveUser Because InteractiveUser no longer has Administrator rights.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the BlockRunAsInteractiveUser Fix](https://go.microsoft.com/fwlink/p/?LinkId=690328).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690328" data-raw-source="[Using the BlockRunAsInteractiveUser Fix](https://go.microsoft.com/fwlink/p/?LinkId=690328)">Using the BlockRunAsInteractiveUser Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>ChangeFolderPathToXPStyle</p></td>
|
||||
<td align="left"><p>This fix is required when an application cannot return shell folder paths when it uses the <strong>SHGetFolder</strong> API.</p>
|
||||
<p>The fix intercepts the <strong>SHGetFolder</strong> path request to the common <strong>appdata</strong> file path and returns the Windows® XP-style file path instead of the Windows Vista-style file path.</p></td>
|
||||
<p>The fix intercepts the <strong>SHGetFolder</strong> path request to the common <strong>appdata</strong> file path and returns the Windows® XP-style file path instead of the Windows Vista-style file path.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ClearLastErrorStatusonIntializeCriticalSection</p></td>
|
||||
@ -101,15 +100,14 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>CopyHKCUSettingsFromOtherUsers</p></td>
|
||||
<td align="left"><p>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.</p>
|
||||
<td align="left"><p>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.</p>
|
||||
<p>The fix scans the existing user profiles and tries to copy the specified keys into the HKEY_CURRENT_USER registry area.</p>
|
||||
<p>You can control this fix further by entering the relevant registry keys as parameters that are separated by the ^ Symbol; for example: <code>Software\MyCompany\Key1^Software\MyCompany\Key2</code>.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the CopyHKCUSettingsFromOtherUsers Fix](https://go.microsoft.com/fwlink/p/?LinkId=690329).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690329" data-raw-source="[Using the CopyHKCUSettingsFromOtherUsers Fix](https://go.microsoft.com/fwlink/p/?LinkId=690329)">Using the CopyHKCUSettingsFromOtherUsers Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -122,11 +120,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>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.</p>
|
||||
<p>The fix modifies the file path names to point to a new location on the hard disk.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about the CorrectFilePaths application fix, see [Using the CorrectFilePaths Fix](https://go.microsoft.com/fwlink/p/?LinkId=690330). We recommend that you use this fix together with the CorrectFilePathsUninstall fix if you are applying it to a setup installation file.</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about the CorrectFilePaths application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690330" data-raw-source="[Using the CorrectFilePaths Fix](https://go.microsoft.com/fwlink/p/?LinkId=690330)">Using the CorrectFilePaths Fix</a>. We recommend that you use this fix together with the CorrectFilePathsUninstall fix if you are applying it to a setup installation file.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -134,11 +131,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>This problem occurs when an uninstalled application leaves behind files, directories, and links.</p>
|
||||
<p>The fix corrects the file paths that are used by the uninstallation process of an application.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this fix, see [Using the CorrectFilePathsUninstall Fix](https://go.microsoft.com/fwlink/p/?LinkId=690331). We recommend that you use this fix together with the CorrectFilePaths fix if you are applying it to a setup installation file.</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690331" data-raw-source="[Using the CorrectFilePathsUninstall Fix](https://go.microsoft.com/fwlink/p/?LinkId=690331)">Using the CorrectFilePathsUninstall Fix</a>. We recommend that you use this fix together with the CorrectFilePaths fix if you are applying it to a setup installation file.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -146,11 +142,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>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.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about the CorrectShellExecuteHWND application fix, see [Using the CorrectShellExecuteHWND Fix](https://go.microsoft.com/fwlink/p/?LinkId=690332).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about the CorrectShellExecuteHWND application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690332" data-raw-source="[Using the CorrectShellExecuteHWND Fix](https://go.microsoft.com/fwlink/p/?LinkId=690332)">Using the CorrectShellExecuteHWND Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -164,11 +159,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<p>DLL_Name;Flag_Type;Hexidecimal_Value</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>The PROCESS flag type can have a 32-bit length only. You can separate multiple entries with a backslash ().</p>
|
||||
<strong>Note</strong><br/><p>The PROCESS flag type can have a 32-bit length only. You can separate multiple entries with a backslash ().</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -179,18 +173,16 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<p>Deprecated_Service\App_Service/Deprecated_Service2 \App_Service2</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>If you do not provide an App_Service name, the deprecated service will be removed from all newly created services.</p>
|
||||
<strong>Note</strong><br/><p>If you do not provide an App_Service name, the deprecated service will be removed from all newly created services.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>You can separate multiple entries with a forward slash (/).</p>
|
||||
<strong>Note</strong><br/><p>You can separate multiple entries with a forward slash (/).</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -203,7 +195,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>DetectorDWM8And16Bit</p></td>
|
||||
<td align="left"><p>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 .</p></td>
|
||||
<td align="left"><p>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 .</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Disable8And16BitD3D</p></td>
|
||||
@ -218,11 +210,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when some objects are not drawn or object artifacts remain on the screen in an application.</p>
|
||||
<p>The fix temporarily disables the Windows Aero menu theme functionality for unsupported applications.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the DisableDWM Fix]( https://go.microsoft.com/fwlink/p/?LinkId=690334).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690334" data-raw-source="[Using the DisableDWM Fix]( https://go.microsoft.com/fwlink/p/?LinkId=690334)">Using the DisableDWM Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -241,7 +232,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>DWM8And16BitMitigation</p></td>
|
||||
<td align="left"><p>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.</p></td>
|
||||
<td align="left"><p>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.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>DXGICompat</p></td>
|
||||
@ -256,28 +247,26 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>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.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the ElevateCreateProcess Fix](https://go.microsoft.com/fwlink/p/?LinkId=690335).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690335" data-raw-source="[Using the ElevateCreateProcess Fix](https://go.microsoft.com/fwlink/p/?LinkId=690335)">Using the ElevateCreateProcess Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>EmulateOldPathIsUNC</p></td>
|
||||
<td align="left"><p>The problem occurs when an application fails because of an incorrect UNC path.</p>
|
||||
<p>The fix changes the PathIsUNC function to return a value of True for UNC paths in Windows. </p></td>
|
||||
<p>The fix changes the PathIsUNC function to return a value of True for UNC paths in Windows. </p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>EmulateGetDiskFreeSpace</p></td>
|
||||
<td align="left"><p>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.</p>
|
||||
<p>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.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the EmulateGetDiskFreeSpace Fix](https://go.microsoft.com/fwlink/p/?LinkId=690336).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690336" data-raw-source="[Using the EmulateGetDiskFreeSpace Fix](https://go.microsoft.com/fwlink/p/?LinkId=690336)">Using the EmulateGetDiskFreeSpace Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -285,62 +274,58 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when an application experiences search functionality issues.</p>
|
||||
<p>The fix forces applications that use the CompareStringW/LCMapString sorting table to use an older version of the table.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this e application fix, see [Using the EmulateSorting Fix](https://go.microsoft.com/fwlink/p/?LinkId=690337).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this e application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690337" data-raw-source="[Using the EmulateSorting Fix](https://go.microsoft.com/fwlink/p/?LinkId=690337)">Using the EmulateSorting Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>EmulateSortingWindows61</p></td>
|
||||
<td align="left"><p>The fix emulates the sorting order of Windows 7 and Windows Server 2008 R2 for various APIs.</p></td>
|
||||
<td align="left"><p>The fix emulates the sorting order of Windows 7 and Windows Server 2008 R2 for various APIs.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>EnableRestarts</p></td>
|
||||
<td align="left"><p>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.</p>
|
||||
<p>The fix enables the computer to restart and finish the installation process by verifying and enabling that the SeShutdownPrivilege service privilege exists.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the EnableRestarts Fix](https://go.microsoft.com/fwlink/p/?LinkId=690338).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690338" data-raw-source="[Using the EnableRestarts Fix](https://go.microsoft.com/fwlink/p/?LinkId=690338)">Using the EnableRestarts Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ExtraAddRefDesktopFolder</p></td>
|
||||
<td align="left"><p>The problem occurs when an application invokes the Release() method too many times and causes an object to be prematurely destroyed.</p>
|
||||
<p>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.</p></td>
|
||||
<p>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.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>FailObsoleteShellAPIs</p></td>
|
||||
<td align="left"><p>The problem occurs when an application fails because it generated deprecated API calls.</p>
|
||||
<p>The fix either fully implements the obsolete functions or implements the obsolete functions with stubs that fail.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>You can type FailAll=1 at the command prompt to suppress the function implementation and force all functions to fail.</p>
|
||||
<strong>Note</strong><br/><p>You can type FailAll=1 at the command prompt to suppress the function implementation and force all functions to fail.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>FailRemoveDirectory</p></td>
|
||||
<td align="left"><p>The problem occurs when an application uninstallation process does not remove all of the application files and folders.</p>
|
||||
<p>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.</p>
|
||||
<p>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.</p>
|
||||
<p>The fix can resolve an issue where an application expects RemoveDirectory() to delete a folder immediately even though a handle is open to it.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>FakeLunaTheme</p></td>
|
||||
<td align="left"><p>The problem occurs when a theme application does not properly display: the colors are washed out or the user interface is not detailed.</p>
|
||||
<p>The fix intercepts the GetCurrentThemeName API and returns the value for the Windows XP default theme, (Luna).</p>
|
||||
<p>The fix intercepts the GetCurrentThemeName API and returns the value for the Windows XP default theme, (Luna).</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about the FakeLunaTheme application fix, see [Using the FakeLunaTheme Fix](https://go.microsoft.com/fwlink/p/?LinkId=690339).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about the FakeLunaTheme application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690339" data-raw-source="[Using the FakeLunaTheme Fix](https://go.microsoft.com/fwlink/p/?LinkId=690339)">Using the FakeLunaTheme Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -357,11 +342,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when an application fails to function during an explicit administrator check.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the ForceAdminAccess Fix](https://go.microsoft.com/fwlink/p/?LinkId=690342).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690342" data-raw-source="[Using the ForceAdminAccess Fix](https://go.microsoft.com/fwlink/p/?LinkId=690342)">Using the ForceAdminAccess Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -370,7 +354,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>ForceLoadMirrorDrvMitigation</p></td>
|
||||
<td align="left"><p>The fix loads the Windows 8 mirror driver mitigation for applications where the mitigation is not automatically applied.</p></td>
|
||||
<td align="left"><p>The fix loads the Windows 8 mirror driver mitigation for applications where the mitigation is not automatically applied.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>FreestyleBMX</p></td>
|
||||
@ -394,7 +378,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<tr class="even">
|
||||
<td align="left"><p>HandleMarkedContentNotIndexed</p></td>
|
||||
<td align="left"><p>The problem is indicated by an application that fails when it changes an attribute on a file or directory.</p>
|
||||
<p>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.</p></td>
|
||||
<p>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.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>HeapClearAllocation</p></td>
|
||||
@ -406,11 +390,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when an application fails to function when special key combinations are used.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the IgnoreAltTab Fix](https://go.microsoft.com/fwlink/p/?LinkId=690343).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690343" data-raw-source="[Using the IgnoreAltTab Fix](https://go.microsoft.com/fwlink/p/?LinkId=690343)">Using the IgnoreAltTab Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -422,11 +405,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem is indicated by a read or access violation error message that displays when an application tries to find or open files.</p>
|
||||
<p>The fix links the FindNextFileW, FindNextFileA, FindFirstFileExW, FindFirstFileExA, FindFirstFileW and FindFirstFileA APIs to prevent them from returning directory junctions.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Symbolic links appear starting in Windows Vista.</p>
|
||||
<strong>Note</strong><br/><p>Symbolic links appear starting in Windows Vista.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -437,18 +419,16 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<p>Exception1;Exception2</p>
|
||||
<p>Where Exception1 and Exception2 are specific exceptions to be ignored. For example: ACCESS_VIOLATION_READ:1;ACCESS_VIOLATION_WRITE:1.</p>
|
||||
<div class="alert">
|
||||
<strong>Important</strong>
|
||||
<p>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.</p>
|
||||
<strong>Important</strong><br/><p>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.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the IgnoreException Fix](https://go.microsoft.com/fwlink/p/?LinkId=690344).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690344" data-raw-source="[Using the IgnoreException Fix](https://go.microsoft.com/fwlink/p/?LinkId=690344)">Using the IgnoreException Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -466,11 +446,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem is indicated by a message box that displays with debugging or extraneous content when the application runs on an unexpected operating system.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the IgnoreMessageBox Fix](https://go.microsoft.com/fwlink/p/?LinkId=690345).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690345" data-raw-source="[Using the IgnoreMessageBox Fix](https://go.microsoft.com/fwlink/p/?LinkId=690345)">Using the IgnoreMessageBox Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -484,7 +463,7 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>InstallComponent</p></td>
|
||||
<td align="left"><p>The fix prompts the user to install.Net 3.5 or .Net 2.0 because .Net is not included with Windows 8.</p></td>
|
||||
<td align="left"><p>The fix prompts the user to install.Net 3.5 or .Net 2.0 because .Net is not included with Windows 8.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>LoadLibraryRedirect</p></td>
|
||||
@ -495,11 +474,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when an application unsuccessfully tries to create an object in the Global namespace.</p>
|
||||
<p>The fix intercepts the function call to create the object and replaces the word Global with Local.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the LocalMappedObject Fix](https://go.microsoft.com/fwlink/p/?LinkId=690346).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690346" data-raw-source="[Using the LocalMappedObject Fix](https://go.microsoft.com/fwlink/p/?LinkId=690346)">Using the LocalMappedObject Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -507,11 +485,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem is indicated when an application fails to uninstall because of access-related errors.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the MakeShortcutRunas Fix]( https://go.microsoft.com/fwlink/p/?LinkId=690347)</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690347" data-raw-source="[Using the MakeShortcutRunas Fix]( https://go.microsoft.com/fwlink/p/?LinkId=690347)">Using the MakeShortcutRunas Fix</a></p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -532,11 +509,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem is indicated by an error message that states that you do not have the appropriate permissions to access the application.</p>
|
||||
<p>The fix reduces the security privilege levels on a specified set of files and folders.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the OpenDirectoryACL Fix](https://go.microsoft.com/fwlink/p/?LinkId=690348).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690348" data-raw-source="[Using the OpenDirectoryACL Fix](https://go.microsoft.com/fwlink/p/?LinkId=690348)">Using the OpenDirectoryACL Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -556,11 +532,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>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.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>This issue seems to occur most frequently with .NET applications.</p>
|
||||
<strong>Note</strong><br/><p>This issue seems to occur most frequently with .NET applications.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -579,12 +554,12 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>RedirectCRTTempFile</p></td>
|
||||
<td align="left"><p>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.</p></td>
|
||||
<td align="left"><p>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.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>RedirectHKCUKeys</p></td>
|
||||
<td align="left"><p>The problem occurs when an application cannot be accessed because of User Account Control (UAC) restrictions.</p>
|
||||
<p>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.</p></td>
|
||||
<p>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.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>RedirectMP3Codec</p></td>
|
||||
@ -596,10 +571,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when an application cannot be accessed by its shortcut, or application shortcuts are not removed during the application uninstallation process.</p>
|
||||
<p>The fix redirects all of the shortcuts created during the application setup to appear according to a specified path.</p>
|
||||
<ul>
|
||||
<li><p>Start Menu shortcuts: Appear in the \\ProgramData\Microsoft\Windows\Start Menu directory for all users.</p></li>
|
||||
<li><p>Desktop or Quick Launch shortcuts:You must manually place the shortcuts on the individual user's desktop or Quick Launch bar.</p></li>
|
||||
<li><p>Start Menu shortcuts: Appear in the \ProgramData\Microsoft\Windows\Start Menu directory for all users.</p></li>
|
||||
<li><p>Desktop or Quick Launch shortcuts:You must manually place the shortcuts on the individual user's desktop or Quick Launch bar.</p></li>
|
||||
</ul>
|
||||
<p>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.</p>
|
||||
<p>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.</p>
|
||||
<p>You cannot apply this fix to an .exe file that includes a manifest and provides a runlevel.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -607,11 +582,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when installers, uninstallers, or updaters fail when they are started from a host application.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the RelaunchElevated Fix](https://go.microsoft.com/fwlink/p/?LinkId=690349).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690349" data-raw-source="[Using the RelaunchElevated Fix](https://go.microsoft.com/fwlink/p/?LinkId=690349)">Using the RelaunchElevated Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -624,11 +598,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<li><p>SC_MANAGER_QUERY_LOCK_STATUS</p></li>
|
||||
<li><p>STANDARD_READ_RIGHTS</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the RetryOpenSCManagerwithReadAccess Fix](https://go.microsoft.com/fwlink/p/?LinkId=690350).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690350" data-raw-source="[Using the RetryOpenSCManagerwithReadAccess Fix](https://go.microsoft.com/fwlink/p/?LinkId=690350)">Using the RetryOpenSCManagerwithReadAccess Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></li>
|
||||
</ul></td>
|
||||
</tr>
|
||||
@ -637,11 +610,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>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.</p>
|
||||
<p>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</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the RetryOpenServiceWithReadAccess Fix](https://go.microsoft.com/fwlink/p/?LinkId=690351).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690351" data-raw-source="[Using the RetryOpenServiceWithReadAccess Fix](https://go.microsoft.com/fwlink/p/?LinkId=690351)">Using the RetryOpenServiceWithReadAccess Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -649,11 +621,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when an application fails to function by using the Standard User or Protected Administrator account.</p>
|
||||
<p>The fix enables the application to run by using elevated privileges. The fix is the equivalent of specifying requireAdministrator in an application manifest.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the RunAsAdmin Fix](https://go.microsoft.com/fwlink/p/?LinkId=690353).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690353" data-raw-source="[Using the RunAsAdmin Fix](https://go.microsoft.com/fwlink/p/?LinkId=690353)">Using the RunAsAdmin Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -661,11 +632,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when administrators cannot view the read/write version of an application that presents a read-only view to standard users.</p>
|
||||
<p>The fix enables the application to run by using the highest available permissions. This is the equivalent of specifying highestAvailable in an application manifest.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the RunAsHighest Fix](https://go.microsoft.com/fwlink/p/?LinkId=690355).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690355" data-raw-source="[Using the RunAsHighest Fix](https://go.microsoft.com/fwlink/p/?LinkId=690355)">Using the RunAsHighest Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -673,11 +643,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when an application is not detected as requiring elevation.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the RunAsInvoker Fix](https://go.microsoft.com/fwlink/p/?LinkId=690356).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690356" data-raw-source="[Using the RunAsInvoker Fix](https://go.microsoft.com/fwlink/p/?LinkId=690356)">Using the RunAsInvoker Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -687,20 +656,18 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<tr class="odd">
|
||||
<td align="left"><p>SessionShim</p></td>
|
||||
<td align="left"><p>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.</p>
|
||||
<p>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.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Important</strong>
|
||||
<p>Users cannot log in as Session 0 (Global Session) in Windows Vista and later. Therefore, applications that require access to Session 0 automatically fail.</p>
|
||||
<strong>Important</strong><br/><p>Users cannot log in as Session 0 (Global Session) in Windows Vista and later. Therefore, applications that require access to Session 0 automatically fail.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the SessionShim Fix](https://go.microsoft.com/fwlink/p/?LinkId=690358).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690358" data-raw-source="[Using the SessionShim Fix](https://go.microsoft.com/fwlink/p/?LinkId=690358)">Using the SessionShim Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -710,11 +677,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<p>Client;Protocol;App</p>
|
||||
<p>Where the Client is the name of the email protocol, Protocol is mailto, and App is the name of the application.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Only the mail client and the mailto protocol are supported. You can separate multiple clients by using a backslash ().</p>
|
||||
<strong>Note</strong><br/><p>Only the mail client and the mailto protocol are supported. You can separate multiple clients by using a backslash ().</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -731,11 +697,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>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.</p>
|
||||
<p>The fix applies the specified compatibility fixes by modifying the export table and by nullifying the use of module inclusion and exclusion.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more information about this application fix, see [Using the ShimViaEAT Fix](https://go.microsoft.com/fwlink/p/?LinkId=690359).</p>
|
||||
<strong>Note</strong><br/><p>For more information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690359" data-raw-source="[Using the ShimViaEAT Fix](https://go.microsoft.com/fwlink/p/?LinkId=690359)">Using the ShimViaEAT Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -756,11 +721,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when an application installation file fails to be picked up by the GenericInstaller function.</p>
|
||||
<p>The fix flags the application as being an installer file (for example, setup.exe), and then prompts for elevation.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the SpecificInstaller Fix]( https://go.microsoft.com/fwlink/p/?LinkId=690361).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690361" data-raw-source="[Using the SpecificInstaller Fix]( https://go.microsoft.com/fwlink/p/?LinkId=690361)">Using the SpecificInstaller Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -768,11 +732,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>The problem occurs when an application that is not an installer (and has sufficient privileges) generates a false positive from the GenericInstaller function.</p>
|
||||
<p>The fix flags the application to exclude it from detection by the GenericInstaller function.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the SpecificNonInstaller Fix](https://go.microsoft.com/fwlink/p/?LinkId=690363).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690363" data-raw-source="[Using the SpecificNonInstaller Fix](https://go.microsoft.com/fwlink/p/?LinkId=690363)">Using the SpecificNonInstaller Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -799,11 +762,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<p>MessageString1 MessageString2</p>
|
||||
<p>Where MessageString1 and MessageString2 reflect the message strings that can pass.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Multiple message strings must be separated by spaces. For more detailed information about this application fix, see [Using the UIPIEnableCustomMsgs Fix](https://go.microsoft.com/fwlink/p/?LinkId=690365).</p>
|
||||
<strong>Note</strong><br/><p>Multiple message strings must be separated by spaces. For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690365" data-raw-source="[Using the UIPIEnableCustomMsgs Fix](https://go.microsoft.com/fwlink/p/?LinkId=690365)">Using the UIPIEnableCustomMsgs Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -814,11 +776,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<p>1055 1056 1069</p>
|
||||
<p>Where 1055 reflects the first message ID, 1056 reflects the second message ID, and 1069 reflects the third message ID that can pass.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>Multiple messages can be separated by spaces. For more detailed information about this application fix, see [Using the UIPIEnableStandardMsgs Fix [act]](https://go.microsoft.com/fwlink/p/?LinkId=690367).</p>
|
||||
<strong>Note</strong><br/><p>Multiple messages can be separated by spaces. For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690367" data-raw-source="[Using the UIPIEnableStandardMsgs Fix [act]](https://go.microsoft.com/fwlink/p/?LinkId=690367)">Using the UIPIEnableStandardMsgs Fix [act]</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -833,18 +794,17 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>VirtualRegistry</p></td>
|
||||
<td align="left"><p>The problem is indicated when a Component failed to be located error message displays when an application is started.</p>
|
||||
<p>The fix enables the registry functions to allow for virtualization, redirection, expansion values, version spoofing, the simulation of performance data counters, and so on.</p>
|
||||
<p>For more detailed information about this application fix, see [Using the VirtualRegistry Fix](https://go.microsoft.com/fwlink/p/?LinkId=690368).</p></td>
|
||||
<p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690368" data-raw-source="[Using the VirtualRegistry Fix](https://go.microsoft.com/fwlink/p/?LinkId=690368)">Using the VirtualRegistry Fix</a>.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>VirtualizeDeleteFile</p></td>
|
||||
<td align="left"><p>The problem occurs when several error messages display and the application cannot delete files.</p>
|
||||
<p>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.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the VirtualizeDeleteFile Fix](https://go.microsoft.com/fwlink/p/?LinkId=690369).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690369" data-raw-source="[Using the VirtualizeDeleteFile Fix](https://go.microsoft.com/fwlink/p/?LinkId=690369)">Using the VirtualizeDeleteFile Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -853,17 +813,16 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<p>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.</p>
|
||||
<p>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.</p>
|
||||
<p>You typically will use this compatibility fix in conjunction with the VirtualizeRegisterTypeLib fix.</p>
|
||||
<p>For more detailed information about this application fix, see [Using the VirtualizeHKCRLite Fix](https://go.microsoft.com/fwlink/p/?LinkId=690370).</p></td>
|
||||
<p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690370" data-raw-source="[Using the VirtualizeHKCRLite Fix](https://go.microsoft.com/fwlink/p/?LinkId=690370)">Using the VirtualizeHKCRLite Fix</a>.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>VirtualizeRegisterTypeLib</p></td>
|
||||
<td align="left"><p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the VirtualizeRegisterTypelib Fix](https://go.microsoft.com/fwlink/p/?LinkId=690371).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690371" data-raw-source="[Using the VirtualizeRegisterTypelib Fix](https://go.microsoft.com/fwlink/p/?LinkId=690371)">Using the VirtualizeRegisterTypelib Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -887,13 +846,12 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Wing32SystoSys32</p></td>
|
||||
<td align="left"><p>The problem is indicated by an error message that states that the WinG library was not properly installed.</p>
|
||||
<p>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.</p>
|
||||
<p>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.</p>
|
||||
<div class="alert">
|
||||
<strong>Important</strong>
|
||||
<p>The application must have Administrator privileges for this fix to work.</p>
|
||||
<strong>Important</strong><br/><p>The application must have Administrator privileges for this fix to work.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -911,27 +869,25 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<li><p>Type vbrun60.dll into the <strong>Module Name</strong> box, click <strong>Include</strong>, and then click <strong>Add</strong>.</p></li>
|
||||
<li><p>Save the custom database.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more information about the WinXPSP2VersionLie application fix, see [Using the WinXPSP2VersionLie Fix](https://go.microsoft.com/fwlink/p/?LinkId=690374).</p>
|
||||
<strong>Note</strong><br/><p>For more information about the WinXPSP2VersionLie application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690374" data-raw-source="[Using the WinXPSP2VersionLie Fix](https://go.microsoft.com/fwlink/p/?LinkId=690374)">Using the WinXPSP2VersionLie Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></li>
|
||||
</ol></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>WRPDllRegister</p></td>
|
||||
<td align="left"><p>The application fails when it tries to register a COM component that is released together with Windows Vista and later.</p>
|
||||
<td align="left"><p>The application fails when it tries to register a COM component that is released together with Windows Vista and later.</p>
|
||||
<p>The fix skips the processes of registering and unregistering WRP-protected COM components when calling the DLLRegisterServer and DLLUnregisterServer functions.</p>
|
||||
<p>You can control this fix further by typing the following command at the command prompt:</p>
|
||||
<p>Component1.dll;Component2.dll</p>
|
||||
<p>Where Component1.dll and Component2.dll reflect the components to be skipped.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about this application fix, see [Using the WRPDllRegister Fix](https://go.microsoft.com/fwlink/p/?LinkId=690375).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about this application fix, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690375" data-raw-source="[Using the WRPDllRegister Fix](https://go.microsoft.com/fwlink/p/?LinkId=690375)">Using the WRPDllRegister Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -939,11 +895,10 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
<td align="left"><p>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.</p>
|
||||
<p>The fix emulates the successful authentication and modification of file and registry APIs, so that the application can continue.</p>
|
||||
<div class="alert">
|
||||
<strong>Note</strong>
|
||||
<p>For more detailed information about WRPMitigation, see [Using the WRPMitigation Fix](https://go.microsoft.com/fwlink/p/?LinkId=690376).</p>
|
||||
<strong>Note</strong><br/><p>For more detailed information about WRPMitigation, see <a href="https://go.microsoft.com/fwlink/p/?LinkId=690376" data-raw-source="[Using the WRPMitigation Fix](https://go.microsoft.com/fwlink/p/?LinkId=690376)">Using the WRPMitigation Fix</a>.</p>
|
||||
</div>
|
||||
<div>
|
||||
|
||||
|
||||
</div></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -953,12 +908,12 @@ The following table lists the known compatibility fixes for all Windows operatin
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>XPAfxIsValidAddress</p></td>
|
||||
<td align="left"><p>The fix emulates the behavior of Windows XP for MFC42!AfxIsValidAddress.</p></td>
|
||||
<td align="left"><p>The fix emulates the behavior of Windows XP for MFC42!AfxIsValidAddress.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
## Compatibility Modes
|
||||
|
||||
@ -981,7 +936,7 @@ The following table lists the known compatibility modes.
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>WinSrv03</p></td>
|
||||
<td align="left"><p>Emulates the Windows Server 2003 operating system.</p></td>
|
||||
<td align="left"><p>Emulates the Windows Server 2003 operating system.</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Win2k3RTMVersionLie</p></li>
|
||||
<li><p>VirtualRegistry</p></li>
|
||||
@ -999,7 +954,7 @@ The following table lists the known compatibility modes.
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>WinSrv03Sp1</p></td>
|
||||
<td align="left"><p>Emulates the Windows Server 2003 with Service Pack 1 (SP1) operating system.</p></td>
|
||||
<td align="left"><p>Emulates the Windows Server 2003 with Service Pack 1 (SP1) operating system.</p></td>
|
||||
<td align="left"><ul>
|
||||
<li><p>Win2K3SP1VersionLie</p></li>
|
||||
<li><p>VirtualRegistry</p></li>
|
||||
|
@ -31,7 +31,7 @@ The Compatibility Administrator tool uses the term *fix* to describe the combina
|
||||
**Important**
|
||||
Fixes apply to a single application only; therefore, you must create multiple fixes if you need to fix the same issue in multiple applications.
|
||||
|
||||
|
||||
|
||||
|
||||
## What is a Compatibility Fix?
|
||||
|
||||
@ -46,7 +46,7 @@ The Compatibility Administrator tool has preloaded fixes for many common applica
|
||||
**Important**
|
||||
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create custom databases for 32-bit applications and the 64-bit version to create custom databases for 64-bit applications.
|
||||
|
||||
|
||||
|
||||
|
||||
**To search for an existing application**
|
||||
|
||||
@ -76,9 +76,9 @@ If you are unable to find a preloaded compatibility fix for your application, yo
|
||||
## Related topics
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -19,12 +19,12 @@ ms.topic: article
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
- Windows 10
|
||||
- Windows 8.1
|
||||
- Windows 8
|
||||
- Windows 7
|
||||
- Windows Server 2012
|
||||
- Windows Server 2008 R2
|
||||
|
||||
Windows® provides several *compatibility modes*, groups of compatibility fixes found to resolve many common application-compatibility issues. While working with Compatibility Administrator, you might decide to group some of your individual compatibility fixes into a custom-compatibility mode, which you can then deploy and use on any of your compatibility databases.
|
||||
|
||||
@ -38,10 +38,10 @@ A compatibility mode is a group of compatibility fixes. A compatibility fix, pre
|
||||
|
||||
The Compatibility Administrator tool has preloaded fixes for many common applications, including known compatibility fixes, compatibility modes, and AppHelp messages. Before you create a new compatibility mode, you can search for an existing application and then copy and paste the known fixes into your custom database.
|
||||
|
||||
**Important**
|
||||
**Important**
|
||||
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create custom databases for 32-bit applications and the 64-bit version to create custom databases for 64-bit applications.
|
||||
|
||||
|
||||
|
||||
|
||||
**To search for an existing application**
|
||||
|
||||
@ -54,10 +54,10 @@ Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version o
|
||||
|
||||
If you are unable to find a preloaded compatibility mode for your application, you can create a new one for use by your custom database.
|
||||
|
||||
**Important**
|
||||
**Important**
|
||||
A compatibility mode includes a set of compatibility fixes and must be deployed as a group. Therefore, you should include only fixes that you intend to deploy together to the database.
|
||||
|
||||
|
||||
|
||||
|
||||
**To create a new compatibility mode**
|
||||
|
||||
@ -67,23 +67,25 @@ A compatibility mode includes a set of compatibility fixes and must be deployed
|
||||
|
||||
3. Select each of the available compatibility fixes to include in your custom-compatibility mode and then click **>**.
|
||||
|
||||
**Important**
|
||||
**Important**
|
||||
If you are unsure which compatibility fixes to add, you can click **Copy Mode**. The **Select Compatibility Mode** dialog box appears and enables you to select from the preloaded compatibility modes. After you select a compatibility mode and click **OK**, any compatibility fixes that are included in the preloaded compatibility mode will be automatically added to your custom-compatibility mode.
|
||||
|
||||
|
||||
|
||||
If you have any compatibility fixes that require additional parameters, you can select the fix, and then click **Parameters**. The **Options for <Compatibility\_Fix\_Name>** dialog box appears, enabling you to update the parameter fields.
|
||||
|
||||
4. After you are done selecting the compatibility fixes to include, click **OK**.
|
||||
~~~
|
||||
If you have any compatibility fixes that require additional parameters, you can select the fix, and then click **Parameters**. The **Options for <Compatibility\_Fix\_Name>** dialog box appears, enabling you to update the parameter fields.
|
||||
~~~
|
||||
|
||||
The compatibility mode is added to your custom database.
|
||||
4. After you are done selecting the compatibility fixes to include, click **OK**.
|
||||
|
||||
The compatibility mode is added to your custom database.
|
||||
|
||||
## Related topics
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -43,7 +43,7 @@ The Compatibility Administrator tool has preloaded fixes for many common applica
|
||||
**Important**
|
||||
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to create custom databases for 32-bit applications and the 64-bit version to create custom databases for 64-bit applications.
|
||||
|
||||
|
||||
|
||||
|
||||
**To search for an existing application**
|
||||
|
||||
|
@ -29,7 +29,7 @@ From the start, Windows To Go was designed to minimize differences between the u
|
||||
**Note**
|
||||
Windows To Go does not support operating system upgrades. Windows To Go is designed as a feature that is managed centrally. IT departments that plan to transition from one operating system version to a later version will need to incorporate re-imaging their existing Windows To Go drives as part of their upgrade deployment process.
|
||||
|
||||
|
||||
|
||||
|
||||
The following sections discuss the boot experience, deployment methods, and tools that you can use with Windows To Go.
|
||||
|
||||
@ -65,7 +65,7 @@ When the Windows To Go workspace is going to be used first on an off-premises co
|
||||
**Tip**
|
||||
Applying BitLocker Drive Encryption to the drives before provisioning is a much faster process than encrypting the drives after data has already been stored on them due to a new feature called used-disk space only encryption. For more information, see [What's New in BitLocker](https://go.microsoft.com/fwlink/p/?LinkId=619076).
|
||||
|
||||
|
||||
|
||||
|
||||
DirectAccess can be used to ensure that the user can login with their domain credentials without needing a local account. For instructions on setting up a DirectAccess solution, for a small pilot deployment see [Deploy a Single Remote Access Server using the Getting Started Wizard](https://go.microsoft.com/fwlink/p/?LinkId=619077) for a larger scale deployment, see [Deploy Remote Access in an Enterprise](https://go.microsoft.com/fwlink/p/?LinkId=619078). If you do not want to use DirectAccess as an alternative users could log on using a local user account on the Windows To Go workspace and then use a virtual private network for remote access to your organizational network.
|
||||
|
||||
@ -80,7 +80,7 @@ The simplest way to provision a Windows To Go drive is to use the Windows To Go
|
||||
**Tip**
|
||||
When you create your Windows To Go image use sysprep /generalize, just as you do when you deploy Windows 10 to a standard PC. In fact, if appropriate, use the same image for both deployments.
|
||||
|
||||
|
||||
|
||||
|
||||
**Driver considerations**
|
||||
|
||||
@ -162,28 +162,28 @@ The following list of commonly used Wi-Fi network adapters that are not supporte
|
||||
<td align="left"><p>Marvell</p></td>
|
||||
<td align="left"><p>Yukon 88E8001/8003/8010 PCI Gigabit Ethernet</p></td>
|
||||
<td align="left"><p>pci\ven_11ab&dev_4320&subsys_811a1043</p></td>
|
||||
<td align="left"><p>[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619080)</p>
|
||||
<p>[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619082)</p></td>
|
||||
<td align="left"><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619080" data-raw-source="[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619080)">32-bit driver</a></p>
|
||||
<p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619082" data-raw-source="[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619082)">64-bit driver</a></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Marvell</p></td>
|
||||
<td align="left"><p>Libertas 802.11b/g Wireless</p></td>
|
||||
<td align="left"><p>pci\ven_11ab&dev_1faa&subsys_6b001385&rev_03</p></td>
|
||||
<td align="left"><p>[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619128)</p>
|
||||
<p>[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619129)</p></td>
|
||||
<td align="left"><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619128" data-raw-source="[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619128)">32-bit driver</a></p>
|
||||
<p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619129" data-raw-source="[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619129)">64-bit driver</a></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Qualcomm</p></td>
|
||||
<td align="left"><p>Atheros AR6004 Wireless LAN Adapter</p></td>
|
||||
<td align="left"><p>sd\vid_0271&pid_0401</p></td>
|
||||
<td align="left"><p>[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619086)</p>
|
||||
<td align="left"><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619086" data-raw-source="[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619086)">32-bit driver</a></p>
|
||||
<p>64-bit driver not available</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Qualcomm</p></td>
|
||||
<td align="left"><p>Atheros AR5BWB222 Wireless Network Adapter</p></td>
|
||||
<td align="left"><p>pci\ven_168c&dev_0034&subsys_20031a56</p></td>
|
||||
<td align="left"><p>[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619348)</p>
|
||||
<td align="left"><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619348" data-raw-source="[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619348)">32-bit driver</a></p>
|
||||
<p>64-bit driver not available</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
@ -196,41 +196,41 @@ The following list of commonly used Wi-Fi network adapters that are not supporte
|
||||
<td align="left"><p>Qualcomm</p></td>
|
||||
<td align="left"><p>Atheros AR5005G Wireless Network Adapter</p></td>
|
||||
<td align="left"><p>pci\ven_168c&dev_001a&subsys_04181468&rev_01</p></td>
|
||||
<td align="left"><p>[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619349)</p>
|
||||
<p>[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619091)</p></td>
|
||||
<td align="left"><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619349" data-raw-source="[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619349)">32-bit driver</a></p>
|
||||
<p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619091" data-raw-source="[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619091)">64-bit driver</a></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Ralink</p></td>
|
||||
<td align="left"><p>Wireless-G PCI Adapter</p></td>
|
||||
<td align="left"><p>pci\ven_1814&dev_0301&subsys_00551737&rev_00</p></td>
|
||||
<td align="left"><p>[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619092)</p>
|
||||
<p>[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619093)</p></td>
|
||||
<td align="left"><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619092" data-raw-source="[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619092)">32-bit driver</a></p>
|
||||
<p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619093" data-raw-source="[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619093)">64-bit driver</a></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Ralink</p></td>
|
||||
<td align="left"><p>Turbo Wireless LAN Card</p></td>
|
||||
<td align="left"><p>pci\ven_1814&dev_0301&subsys_25611814&rev_00</p></td>
|
||||
<td align="left"><p>[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619094)</p>
|
||||
<p>[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619095)</p></td>
|
||||
<td align="left"><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619094" data-raw-source="[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619094)">32-bit driver</a></p>
|
||||
<p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619095" data-raw-source="[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619095)">64-bit driver</a></p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>Ralink</p></td>
|
||||
<td align="left"><p>Wireless LAN Card V1</p></td>
|
||||
<td align="left"><p>pci\ven_1814&dev_0302&subsys_3a711186&rev_00</p></td>
|
||||
<td align="left"><p>[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619097)</p>
|
||||
<p>[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619098)</p></td>
|
||||
<td align="left"><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619097" data-raw-source="[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619097)">32-bit driver</a></p>
|
||||
<p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619098" data-raw-source="[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619098)">64-bit driver</a></p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Ralink</p></td>
|
||||
<td align="left"><p>D-Link AirPlus G DWL-G510 Wireless PCI Adapter(rev.C)</p></td>
|
||||
<td align="left"><p>pci\ven_1814&dev_0302&subsys_3c091186&rev_00</p></td>
|
||||
<td align="left"><p>[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619099)</p>
|
||||
<p>[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619100)</p></td>
|
||||
<td align="left"><p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619099" data-raw-source="[32-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619099)">32-bit driver</a></p>
|
||||
<p><a href="https://go.microsoft.com/fwlink/p/?LinkId=619100" data-raw-source="[64-bit driver](https://go.microsoft.com/fwlink/p/?LinkId=619100)">64-bit driver</a></p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
IT administrators that want to target Windows To Go images for specific systems should test their images to ensure that the necessary system drivers are in the image, especially for critical functionality like Wi-Fi that is not supported by class drivers. Some consumer devices require OEM specific driver packages, which may not be available on Windows Update. For more information on how to add a driver to a Windows Image, please refer to the [Basic Windows Deployment Step-by-Step Guide](https://go.microsoft.com/fwlink/p/?LinkId=619079).
|
||||
|
||||
@ -253,7 +253,7 @@ The use of the Store on Windows To Go workspaces that are running Windows 8 can
|
||||
**Important**
|
||||
For the host-PC to resume correctly when hibernation is enabled the Windows To Go workspace must continue to use the same USB port.
|
||||
|
||||
|
||||
|
||||
|
||||
- **Disallow standby sleep states (S1-S3) when starting from a Windows To Go workspace**
|
||||
|
||||
@ -268,7 +268,7 @@ The use of the Store on Windows To Go workspaces that are running Windows 8 can
|
||||
**Important**
|
||||
Enabling this policy setting will cause PCs running Windows to attempt to boot from any USB device that is inserted into the PC before it is started.
|
||||
|
||||
|
||||
|
||||
|
||||
## <a href="" id="wtg-bootusb"></a>Supporting booting from USB
|
||||
|
||||
@ -278,7 +278,7 @@ The biggest hurdle for a user wanting to use Windows To Go is configuring their
|
||||
**Note**
|
||||
Enabling a system to always boot from USB first has implications that you should consider. For example, a USB device that includes malware could be booted inadvertently to compromise the system, or multiple USB drives could be plugged in to cause a boot conflict. For this reason, the Windows To Go startup options are disabled by default. In addition, administrator privileges are required to configure Windows To Go startup options.
|
||||
|
||||
|
||||
|
||||
|
||||
If you are going to be using a Windows 7 computer as a host-PC, see the wiki article [Tips for configuring your BIOS settings to work with Windows To Go](https://go.microsoft.com/fwlink/p/?LinkID=618951).
|
||||
|
||||
@ -311,7 +311,7 @@ Windows To Go Startup Options is a setting available on Windows 10-based PCs th
|
||||
**Tip**
|
||||
If your computer is part of a domain, the Group Policy setting can be used to enable the startup options instead of the dialog.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Click **Save Changes**. If the User Account Control dialog box is displayed, confirm that the action it displays is what you want, and then click **Yes**.
|
||||
|
||||
@ -330,9 +330,9 @@ If you choose to not use the Windows To Go startup options or are using a PC run
|
||||
|
||||
[Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ Customized compatibility databases can become quite complex as you add your fixe
|
||||
**Important**
|
||||
Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version of the Compatibility Administrator tool. You must use the 32-bit version to work with custom databases for 32-bit applications and the 64-bit version to work with custom databases for 64-bit applications.
|
||||
|
||||
|
||||
|
||||
|
||||
**To disable a compatibility fix within a database**
|
||||
|
||||
@ -49,7 +49,7 @@ Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version o
|
||||
**Important**
|
||||
When you disable an entry, it will remain disabled even if you do not save the database file.
|
||||
|
||||
|
||||
|
||||
|
||||
## Enabling Compatibility Fixes
|
||||
|
||||
|
@ -35,7 +35,7 @@ Application Compatibility Toolkit (ACT) installs a 32-bit and a 64-bit version o
|
||||
|
||||
In addition, you must deploy your databases to your organization’s computers before the included fixes will have any effect on the application issue. For more information about deploying your database, see [Using the Sdbinst.exe Command-Line Tool](using-the-sdbinstexe-command-line-tool.md).
|
||||
|
||||
|
||||
|
||||
|
||||
## Installing a Custom Database
|
||||
|
||||
|
@ -44,21 +44,21 @@ This section provides information about managing your application-compatibility
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Understanding and Using Compatibility Fixes](understanding-and-using-compatibility-fixes.md)</p></td>
|
||||
<td align="left"><p><a href="understanding-and-using-compatibility-fixes.md" data-raw-source="[Understanding and Using Compatibility Fixes](understanding-and-using-compatibility-fixes.md)">Understanding and Using Compatibility Fixes</a></p></td>
|
||||
<td align="left"><p>As the Windows operating system evolves to support new technology and functionality, the implementations of some functions may change. This can cause problems for applications that relied upon the original implementation. You can avoid compatibility issues by using the Microsoft Windows Application Compatibility (Compatibility Fix) infrastructure to create a specific application fix for a particular version of an application.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Compatibility Fix Database Management Strategies and Deployment](compatibility-fix-database-management-strategies-and-deployment.md)</p></td>
|
||||
<td align="left"><p><a href="compatibility-fix-database-management-strategies-and-deployment.md" data-raw-source="[Compatibility Fix Database Management Strategies and Deployment](compatibility-fix-database-management-strategies-and-deployment.md)">Compatibility Fix Database Management Strategies and Deployment</a></p></td>
|
||||
<td align="left"><p>After you determine that you will use compatibility fixes in your application-compatibility mitigation strategy, you must define a strategy to manage your custom compatibility-fix database. Typically, you can use one of two approaches:</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Testing Your Application Mitigation Packages](testing-your-application-mitigation-packages.md)</p></td>
|
||||
<td align="left"><p><a href="testing-your-application-mitigation-packages.md" data-raw-source="[Testing Your Application Mitigation Packages](testing-your-application-mitigation-packages.md)">Testing Your Application Mitigation Packages</a></p></td>
|
||||
<td align="left"><p>This topic provides details about testing your application-mitigation packages, including recommendations about how to report your information and how to resolve any outstanding issues.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
@ -61,7 +61,7 @@ The following scenarios are examples of situations in which Windows To Go worksp
|
||||
**Note**
|
||||
If the employee wants to work offline for the majority of the time, but still maintain the ability to use the drive on the enterprise network, they should be informed of how often the Windows To Go workspace needs to be connected to the enterprise network. Doing so will ensure that the drive retains its access privileges and the workspace’s computer object is not potentially deleted from Active Directory Domain Services (AD DS).
|
||||
|
||||
|
||||
|
||||
|
||||
## Infrastructure considerations
|
||||
|
||||
@ -80,7 +80,7 @@ You should investigate other software manufacturer’s licensing requirements to
|
||||
**Note**
|
||||
Using Multiple Activation Key (MAK) activation is not a supported activation method for Windows To Go as each different PC-host would require separate activation. MAK activation should not be used for activating Windows, Office, or any other application on a Windows To Go drive.
|
||||
|
||||
|
||||
|
||||
|
||||
See [Plan for Volume Activation](https://go.microsoft.com/fwlink/p/?LinkId=618923) for more information about these activation methods and how they can be used in your organization.
|
||||
|
||||
@ -121,9 +121,9 @@ If you want Windows To Go to be able to connect back to organizational resources
|
||||
|
||||
[Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ The **Query Compatibility Databases** tool provides additional search options. F
|
||||
**Important**
|
||||
You must perform your search with the correct version of the Compatibility Administrator tool. If you are searching for a 32-bit custom database, you must use the 32-bit version of Compatibility Administrator. If you are searching for a 64-bit custom database, you must use the 64-bit version of Compatibility Administrator.
|
||||
|
||||
|
||||
|
||||
|
||||
**To search for previous fixes**
|
||||
|
||||
@ -69,9 +69,9 @@ You can export your search results to a text (.txt) file for later review or arc
|
||||
## Related topics
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -33,7 +33,7 @@ For information about the Search feature, see [Searching for Fixed Applications
|
||||
**Important**
|
||||
You must perform your search with the correct version of the Compatibility Administrator tool. To use the Query tool to search for a 32-bit custom database, you must use the 32-bit version of Compatibility Administrator. To use the Query tool to search for a 64-bit custom database, you must use the 64-bit version of Compatibility Administrator.
|
||||
|
||||
|
||||
|
||||
|
||||
## Querying by Using the Program Properties Tab
|
||||
|
||||
@ -65,7 +65,7 @@ You can use the **Program Properties** tab of the Query tool to search for any c
|
||||
**Important**
|
||||
If you do not select any of the check boxes, the search will look for all types of compatibility fixes. Do not select multiple check boxes because only applications that match all of the requirements will appear.
|
||||
|
||||
|
||||
|
||||
|
||||
6. Click **Find Now**.
|
||||
|
||||
@ -89,14 +89,14 @@ You can use the **Fix Properties** tab of the Query tool to search for any appli
|
||||
**Note**
|
||||
You can use the percent (%) symbol as a wildcard in your fix-properties query, as a substitute for any string of zero or more characters.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Select the check box for either **Search in Compatibility Fixes** or **Search in Compatibility Modes**.
|
||||
|
||||
**Important**
|
||||
Your text must match the type of compatibility fix or mode for which you are performing the query. For example, entering the name of a compatibility fix and selecting the compatibility mode check box will not return any results. Additionally, if you select both check boxes, the query will search for the fix by compatibility mode and compatibility fix. Only applications that match both requirements appear.
|
||||
|
||||
|
||||
|
||||
|
||||
6. Click **Find Now**.
|
||||
|
||||
@ -120,7 +120,7 @@ You can use the **Fix Description** tab of the Query tool to add parameters that
|
||||
**Important**
|
||||
You cannot use wildcards as part of the Fix Description search query because the default behavior is to search for any entry that meets your search criteria.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Refine your search by selecting **Match any word** or **Match all words** from the drop-down list.
|
||||
|
||||
@ -173,9 +173,9 @@ You can export any of your search results into a tab-delimited text (.txt) file
|
||||
## Related topics
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -43,7 +43,7 @@ You can enable BitLocker while using the Windows To Go Creator wizard as part of
|
||||
**Tip**
|
||||
If the Windows To Go Creator wizard is not able to enable BitLocker, see [Why can't I enable BitLocker from Windows To Go Creator?](windows-to-go-frequently-asked-questions.md#wtg-faq-blfail)
|
||||
|
||||
|
||||
|
||||
|
||||
If you are using a host computer running Windows 7 that has BitLocker enabled, you should suspend BitLocker before changing the BIOS settings to boot from USB and then resume BitLocker protection. If BitLocker is not suspended first, the next time the computer is started it will boot into recovery mode.
|
||||
|
||||
@ -76,9 +76,9 @@ Windows to Go is a core capability of Windows when it is deployed on the drive a
|
||||
|
||||
[Windows To Go: frequently asked questions](windows-to-go-frequently-asked-questions.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -50,18 +50,18 @@ You can use SUA in either of the following ways:
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Using the SUA Wizard](using-the-sua-wizard.md)</p></td>
|
||||
<td align="left"><p><a href="using-the-sua-wizard.md" data-raw-source="[Using the SUA Wizard](using-the-sua-wizard.md)">Using the SUA Wizard</a></p></td>
|
||||
<td align="left"><p>The Standard User Analyzer (SUA) Wizard works much like the SUA tool to evaluate User Account Control (UAC) issues. However, the SUA Wizard does not offer detailed analysis, and it cannot disable virtualization or elevate your permissions.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Using the SUA Tool](using-the-sua-tool.md)</p></td>
|
||||
<td align="left"><p><a href="using-the-sua-tool.md" data-raw-source="[Using the SUA Tool](using-the-sua-tool.md)">Using the SUA Tool</a></p></td>
|
||||
<td align="left"><p>By using the Standard User Analyzer (SUA) tool, you can test your applications and monitor API calls to detect compatibility issues with the User Account Control (UAC) feature.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -74,7 +74,7 @@ At this point, you probably cannot resolve any unresolved application compatibil
|
||||
**Note**
|
||||
For more information about using Compatibility Administrator to apply compatibility fixes and compatibility modes, see [Using the Compatibility Administrator Tool](using-the-compatibility-administrator-tool.md).
|
||||
|
||||
|
||||
|
||||
|
||||
- Run the application in a virtual environment.
|
||||
|
||||
|
@ -44,7 +44,7 @@ Specifically, the process modifies the address of the affected Windows function
|
||||
**Note**
|
||||
For statically linked DLLs, the code redirection occurs as the application loads. You can also fix dynamically linked DLLs by hooking into the GetProcAddress API.
|
||||
|
||||
|
||||
|
||||
|
||||
## Design Implications of the Compatibility Fix Infrastructure
|
||||
|
||||
@ -60,7 +60,7 @@ There are important considerations to keep in mind when determining your applica
|
||||
**Note**
|
||||
Some antivirus, firewall, and anti-spyware code runs in kernel mode.
|
||||
|
||||
|
||||
|
||||
|
||||
## Determining When to Use a Compatibility Fix
|
||||
|
||||
|
@ -44,49 +44,49 @@ This section provides information about using the Compatibility Administrator to
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Available Data Types and Operators in Compatibility Administrator](available-data-types-and-operators-in-compatibility-administrator.md)</p></td>
|
||||
<td align="left"><p><a href="available-data-types-and-operators-in-compatibility-administrator.md" data-raw-source="[Available Data Types and Operators in Compatibility Administrator](available-data-types-and-operators-in-compatibility-administrator.md)">Available Data Types and Operators in Compatibility Administrator</a></p></td>
|
||||
<td align="left"><p>The Compatibility Administrator tool provides a way to query your custom-compatibility databases.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Searching for Fixed Applications in Compatibility Administrator](searching-for-fixed-applications-in-compatibility-administrator.md)</p></td>
|
||||
<td align="left"><p><a href="searching-for-fixed-applications-in-compatibility-administrator.md" data-raw-source="[Searching for Fixed Applications in Compatibility Administrator](searching-for-fixed-applications-in-compatibility-administrator.md)">Searching for Fixed Applications in Compatibility Administrator</a></p></td>
|
||||
<td align="left"><p>With the search functionality in Compatibility Administrator, you can locate specific executable (.exe) files with previously applied compatibility fixes, compatibility modes, or AppHelp messages. This is particularly useful if you are trying to identify applications with a specific compatibility fix or identifying which fixes are applied to a specific application.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Searching for Installed Compatibility Fixes with the Query Tool in Compatibility Administrator](searching-for-installed-compatibility-fixes-with-the-query-tool-in-compatibility-administrator.md)</p></td>
|
||||
<td align="left"><p><a href="searching-for-installed-compatibility-fixes-with-the-query-tool-in-compatibility-administrator.md" data-raw-source="[Searching for Installed Compatibility Fixes with the Query Tool in Compatibility Administrator](searching-for-installed-compatibility-fixes-with-the-query-tool-in-compatibility-administrator.md)">Searching for Installed Compatibility Fixes with the Query Tool in Compatibility Administrator</a></p></td>
|
||||
<td align="left"><p>You can access the Query tool from within Compatibility Administrator. The Query tool provides the same functionality as using the Search feature.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Creating a Custom Compatibility Fix in Compatibility Administrator](creating-a-custom-compatibility-fix-in-compatibility-administrator.md)</p></td>
|
||||
<td align="left"><p><a href="creating-a-custom-compatibility-fix-in-compatibility-administrator.md" data-raw-source="[Creating a Custom Compatibility Fix in Compatibility Administrator](creating-a-custom-compatibility-fix-in-compatibility-administrator.md)">Creating a Custom Compatibility Fix in Compatibility Administrator</a></p></td>
|
||||
<td align="left"><p>The Compatibility Administrator tool uses the term <em>fix</em> to describe the combination of compatibility information added to a customized database for a specific application. This combination can include single application fixes, groups of fixes that work together as a compatibility mode, and blocking and non-blocking AppHelp messages.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Creating a Custom Compatibility Mode in Compatibility Administrator](creating-a-custom-compatibility-mode-in-compatibility-administrator.md)</p></td>
|
||||
<td align="left"><p><a href="creating-a-custom-compatibility-mode-in-compatibility-administrator.md" data-raw-source="[Creating a Custom Compatibility Mode in Compatibility Administrator](creating-a-custom-compatibility-mode-in-compatibility-administrator.md)">Creating a Custom Compatibility Mode in Compatibility Administrator</a></p></td>
|
||||
<td align="left"><p>Windows® provides several <em>compatibility modes</em>, groups of compatibility fixes found to resolve many common application-compatibility issues. While working with Compatibility Administrator, you might decide to group some of your individual compatibility fixes into a custom-compatibility mode, which you can then deploy and use on any of your compatibility databases.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Creating an AppHelp Message in Compatibility Administrator](creating-an-apphelp-message-in-compatibility-administrator.md)</p></td>
|
||||
<td align="left"><p><a href="creating-an-apphelp-message-in-compatibility-administrator.md" data-raw-source="[Creating an AppHelp Message in Compatibility Administrator](creating-an-apphelp-message-in-compatibility-administrator.md)">Creating an AppHelp Message in Compatibility Administrator</a></p></td>
|
||||
<td align="left"><p>The Compatibility Administrator tool enables you to create an AppHelp text message. This is a blocking or non-blocking message that appears when a user starts an application that you know has major functionality issues on the Windows® operating system.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Viewing the Events Screen in Compatibility Administrator](viewing-the-events-screen-in-compatibility-administrator.md)</p></td>
|
||||
<td align="left"><p><a href="viewing-the-events-screen-in-compatibility-administrator.md" data-raw-source="[Viewing the Events Screen in Compatibility Administrator](viewing-the-events-screen-in-compatibility-administrator.md)">Viewing the Events Screen in Compatibility Administrator</a></p></td>
|
||||
<td align="left"><p>The <strong>Events</strong> screen enables you to record and to view your activities in the Compatibility Administrator tool, provided that the screen is open while you perform the activities.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Enabling and Disabling Compatibility Fixes in Compatibility Administrator](enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md)</p></td>
|
||||
<td align="left"><p><a href="enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md" data-raw-source="[Enabling and Disabling Compatibility Fixes in Compatibility Administrator](enabling-and-disabling-compatibility-fixes-in-compatibility-administrator.md)">Enabling and Disabling Compatibility Fixes in Compatibility Administrator</a></p></td>
|
||||
<td align="left"><p>You can disable and enable individual compatibility fixes in your customized databases for testing and troubleshooting purposes.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Installing and Uninstalling Custom Compatibility Databases in Compatibility Administrator](installing-and-uninstalling-custom-compatibility-databases-in-compatibility-administrator.md)</p></td>
|
||||
<td align="left"><p><a href="installing-and-uninstalling-custom-compatibility-databases-in-compatibility-administrator.md" data-raw-source="[Installing and Uninstalling Custom Compatibility Databases in Compatibility Administrator](installing-and-uninstalling-custom-compatibility-databases-in-compatibility-administrator.md)">Installing and Uninstalling Custom Compatibility Databases in Compatibility Administrator</a></p></td>
|
||||
<td align="left"><p>The Compatibility Administrator tool enables the creation and the use of custom-compatibility and standard-compatibility databases. Both the custom databases and the standard databases store the known compatibility fixes, compatibility modes, and AppHelp messages. They also store the required application-matching information for installation on your local computers.</p></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -31,7 +31,7 @@ The **Events** screen enables you to record and to view your activities in the C
|
||||
**Important**
|
||||
The **Events** screen only records your activities when the screen is open. If you perform an action before opening the **Events** screen, the action will not appear in the list.
|
||||
|
||||
|
||||
|
||||
|
||||
**To open the Events screen**
|
||||
|
||||
@ -49,9 +49,9 @@ If you open the **Events** screen and then perform the copy operation, you can s
|
||||
|
||||
[Compatibility Administrator User's Guide](compatibility-administrator-users-guide.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -21,10 +21,11 @@ Each version of Windows 10 adds new features and functionality; occasionally we
|
||||
|
||||
The following features and functionalities are removed from the installed product image for Windows 10, version 1903, or are planned for removal in an upcoming release. Applications or code that depend on these features won't function in this release unless you use another method.
|
||||
|
||||
|Feature |Details|
|
||||
|-----------|--------------------|---------
|
||||
|XDDM-based remote display driver|Starting with this release the Remote Desktop Services uses a Windows Display Driver Model (WDDM) based Indirect Display Driver (IDD) for a single session remote desktop. The support for Windows 2000 Display Driver Model (XDDM) based remote display drivers will be removed in a future release. Independent Software Vendors that use XDDM-based remote display driver should plan a migration to the WDDM driver model. For more information on implementing remote indirect display driver ISVs can reach out to [rdsdev@microsoft.com](mailto:rdsdev@microsoft.com).
|
||||
| Desktop messaging app doesn't offer messages sync| The messaging app on Desktop has a sync feature that can be used to sync SMS text messages received from Windows Mobile and keep a copy of them on the Desktop. The sync feature has been removed from all devices. Due to this change, you will only be able to access messages from the device that received the message. |
|
||||
|
||||
| Feature | Details |
|
||||
|---------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| XDDM-based remote display driver | Starting with this release the Remote Desktop Services uses a Windows Display Driver Model (WDDM) based Indirect Display Driver (IDD) for a single session remote desktop. The support for Windows 2000 Display Driver Model (XDDM) based remote display drivers will be removed in a future release. Independent Software Vendors that use XDDM-based remote display driver should plan a migration to the WDDM driver model. For more information on implementing remote indirect display driver ISVs can reach out to [rdsdev@microsoft.com](mailto:rdsdev@microsoft.com). |
|
||||
| Desktop messaging app doesn't offer messages sync | The messaging app on Desktop has a sync feature that can be used to sync SMS text messages received from Windows Mobile and keep a copy of them on the Desktop. The sync feature has been removed from all devices. Due to this change, you will only be able to access messages from the device that received the message. |
|
||||
|
||||
## Features we’re no longer developing
|
||||
|
||||
@ -32,7 +33,7 @@ We're no longer actively developing these features and may remove them from a fu
|
||||
|
||||
If you have feedback about the proposed replacement of any of these features, you can use the [Feedback Hub app](https://support.microsoft.com/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app).
|
||||
|
||||
|Feature |Details|
|
||||
|Feature |Details|
|
||||
|-----------|---------------------|
|
||||
| Taskbar settings roaming| Roaming of taskbar settings is no longer being developed and we plan to disable this capability in a future release|
|
||||
|Wi-Fi WEP and TKIP|In this release a warning message will appear when connecting to Wi-Fi networks secured with WEP or TKIP, which are not as secure as those using WPA2 or WPA3. In a future release, any connection to a Wi-Fi network using these old ciphers will be disallowed. Wi-Fi routers should be updated to use AES ciphers, available with WPA2 or WPA3. |
|
||||
|
@ -183,7 +183,7 @@ In the **Windows To Go Startup Options** dialog box select **Yes** and then clic
|
||||
**Note**
|
||||
Your IT department can use Group Policy to configure Windows To Go Startup Options in your organization.
|
||||
|
||||
|
||||
|
||||
|
||||
If the host computer is running an earlier version of the Windows operating system need to configure the computer to boot from USB manually.
|
||||
|
||||
@ -198,7 +198,7 @@ For more detailed instructions, see the wiki article, [Tips for configuring your
|
||||
**Warning**
|
||||
Configuring a computer to boot from USB will cause your computer to attempt to boot from any bootable USB device connected to your computer. This potentially includes malicious devices. Users should be informed of this risk and instructed to not have any bootable USB storage devices plugged in to their computers except for their Windows To Go drive.
|
||||
|
||||
|
||||
|
||||
|
||||
## <a href="" id="wtg-faq-noboot"></a>Why isn’t my computer booting from USB?
|
||||
|
||||
@ -221,7 +221,7 @@ If the Windows To Go drive is removed, the computer will freeze and the user wil
|
||||
**Warning**
|
||||
You should never remove your Windows To Go drive when your workspace is running. The computer freeze is a safety measure to help mitigate the risk of accidental removal. Removing the Windows To Go drive without shutting down the Windows To Go workspace could result in corruption of the Windows To Go drive.
|
||||
|
||||
|
||||
|
||||
|
||||
## <a href="" id="wtg-faq-bitlocker"></a>Can I use BitLocker to protect my Windows To Go drive?
|
||||
|
||||
@ -279,7 +279,7 @@ Windows To Go Creator and the recommended deployment steps for Windows To Go set
|
||||
**Warning**
|
||||
It is strongly recommended that you do not plug your Windows To Go drive into a running computer. If the computer is compromised, your Windows To Go workspace can also be compromised.
|
||||
|
||||
|
||||
|
||||
|
||||
## <a href="" id="wtg-faq-san4"></a>I’m booted into Windows To Go, but I can’t browse to the internal hard drive of the host computer. Why not?
|
||||
|
||||
@ -289,7 +289,7 @@ Windows To Go Creator and the recommended deployment steps for Windows To Go set
|
||||
**Warning**
|
||||
It is strongly recommended that you do not mount internal hard drives when booted into the Windows To Go workspace. If the internal drive contains a hibernated Windows 8 or later operating system, mounting the drive will lead to loss of hibernation state and therefor user state or any unsaved user data when the host operating system is booted. If the internal drive contains a hibernated Windows 7 or earlier operating system, mounting the drive will lead to corruption when the host operating system is booted.
|
||||
|
||||
|
||||
|
||||
|
||||
## <a href="" id="wtg-faq-fatmbr"></a>Why does my Windows To Go drive have an MBR disk format with a FAT32 system partition?
|
||||
|
||||
@ -403,7 +403,7 @@ The host computer will now be able to be booted from a USB drive without trigger
|
||||
**Note**
|
||||
The default BitLocker protection profile in Windows 8 or later does not monitor the boot order.
|
||||
|
||||
|
||||
|
||||
|
||||
## <a href="" id="wtg-faq-reformat"></a>I decided to stop using a drive for Windows To Go and reformatted it – why doesn’t it have a drive letter assigned and how can I fix it?
|
||||
|
||||
@ -415,7 +415,7 @@ Reformatting the drive erases the data on the drive, but doesn’t reconfigure t
|
||||
**Note**
|
||||
If your user account is a member of the Administrators group, but is not the Administrator account itself, then, by default, the programs that you run only have standard user permissions unless you explicitly choose to elevate them.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Start the [diskpart](https://go.microsoft.com/fwlink/p/?LinkId=619070) command interpreter, by typing `diskpart` at the command prompt.
|
||||
|
||||
@ -452,9 +452,9 @@ There is no support in Windows for upgrading a Windows To Go drive. Deployed Win
|
||||
|
||||
- [Security and data protection considerations for Windows To Go](security-and-data-protection-considerations-for-windows-to-go.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
@ -36,7 +36,7 @@ PCs that meet the Windows 7 or later [certification requirements](https://go.mi
|
||||
**Note**
|
||||
Windows To Go is not supported on Windows RT.
|
||||
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-wtgdif"></a>Differences between Windows To Go and a typical installation of Windows
|
||||
|
||||
@ -72,7 +72,7 @@ These same tools can be used to provision Windows To Go drive, just as you would
|
||||
**Important**
|
||||
Make sure you use the versions of the deployment tools provided for the version of Windows you are deploying. There have been many enhancements made to support Windows To Go. Using versions of the deployment tools released for earlier versions of Windows to provision a Windows To Go drive is not supported.
|
||||
|
||||
|
||||
|
||||
|
||||
As you decide what to include in your Windows To Go image, be sure to consider the following questions:
|
||||
|
||||
@ -106,7 +106,7 @@ As of the date of publication, the following are the USB drives currently certif
|
||||
**Warning**
|
||||
Using a USB drive that has not been certified is not supported
|
||||
|
||||
|
||||
|
||||
|
||||
- IronKey Workspace W700 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w700.html](https://go.microsoft.com/fwlink/p/?LinkId=618714))
|
||||
|
||||
@ -125,14 +125,14 @@ Using a USB drive that has not been certified is not supported
|
||||
**Important**
|
||||
You must use the Spyrus Deployment Suite for Windows To Go to provision the Spyrus Secure Portable Workplace. For more information about the Spyrus Deployment Suite for Windows To Go please refer to [http://www.spyruswtg.com/](https://go.microsoft.com/fwlink/p/?LinkId=618720).
|
||||
|
||||
|
||||
|
||||
|
||||
- Spyrus Worksafe ([http://www.spyruswtg.com/](https://go.microsoft.com/fwlink/p/?LinkId=618720))
|
||||
|
||||
**Tip**
|
||||
This device contains an embedded smart card.
|
||||
|
||||
|
||||
|
||||
|
||||
- Super Talent Express RC4 for Windows To Go
|
||||
|
||||
@ -205,7 +205,7 @@ The following table details the characteristics that the host computer must have
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
**Checking for architectural compatibility between the host PC and the Windows To Go drive**
|
||||
|
||||
@ -248,7 +248,7 @@ In addition to the USB boot support in the BIOS, the Windows 10 image on your W
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
|
||||
|
||||
|
||||
## Additional resources
|
||||
|
||||
@ -274,9 +274,9 @@ In addition to the USB boot support in the BIOS, the Windows 10 image on your W
|
||||
|
||||
- [Best practice recommendations for Windows To Go](best-practice-recommendations-for-windows-to-go.md)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user