Compatibility Fixes for Windows 10, Windows 8, Windows 7, and Windows Vista

The fix enables OEM executable (.exe) files to use the GetSystemFirmwareTable function instead of the NtOpenSection function when the BIOS is queried for the \Device\Physical memory information.

The fix blocks InstallShield from setting the value of RunAs registry keys to InteractiveUser Because InteractiveUser no longer has Administrator rights.

The fix intercepts the SHGetFolderpath request to the common appdata file path and returns the Windows® XP-style file path instead of the Windows Vista-style file path.

The fix modifies the InitializeCriticalSection function call so that it checks the NTSTATUS error code, and then sets the last error to ERROR_SUCCESS.

The fix scans the existing user profiles and tries to copy the specified keys into the HKEY_CURRENT_USER registry area.

You can control this fix further by entering the relevant registry keys as parameters that are separated by the ^ Symbol; for example: Software\MyCompany\Key1^Software\MyCompany\Key2.

The fix corrects the brush style hatch value, which is passed to the CreateBrushIndirect() function and enables the information to be correctly interpreted.

• An application tries to write files to the hard disk and is denied access.
• An application receives a file not found or path not found error message.

The fix modifies the file path names to point to a new location on the hard disk.

The fix corrects the file paths that are used by the uninstallation process of an application.

• A taskbar item blinks instead of an elevation prompt being opened, or when the application doesn't provide a valid HWND value when it calls the ShellExecute(Ex) function.

  The fix intercepts the ShellExecute(Ex) calls, and then inspects the HWND value. If the value is invalid, this fix enables the call to use the currently active HWND value.

  Note: For more detailed information about the CorrectShellExecuteHWND application fix, see Using the CorrectShellExecuteHWND Fix.

You can control this fix further by typing the following command at the command prompt:

DLL_Name;Flag_Type;Hexidecimal_Value
Where the DLL_Name is the name of the specific DLL, including the file extension. Flag_Type is KERNEL, USER, or PROCESS, and a Hexidecimal_Value, starting with 0x and up to 64 bits long.

The fix intercepts the CreateService function calls and removes the deprecated dependency service from the lpDependencies parameter.

You can control this fix further by typing the following command at the command prompt:

Deprecated_Service\App_Service/Deprecated_Service2 \App_Service2 where:

• Deprecated_Service is the name of the deprecated service
• App_Service is the name of the specific application service that is to be modified

The fix modifies the DXDIAGN GetProp function call to return the correct DirectX version.

You can control this fix further by typing the following command at the command prompt:
MAJORVERSION.MINORVERSION.LETTER

For example, 9.0.c.

The fix temporarily disables the Windows Aero menu theme functionality for unsupported applications.

The fix disables the fade animations functionality for unsupported applications.

The fix temporarily disables the Windows Aero menu theme functionality for unsupported applications.

• installations
• de-installations
• updates

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 is returned unchanged.

The fix exchanges the PathIsUNC function to return a value of True for UNC paths in Windows.

The fix determines the amount of free space. If the amount of free space is larger than 2 GB, the compatibility fix returns a value of 2 GB. However, if the amount of free space is smaller than 2 GB, the compatibility fix returns the actual-free space amount.

The fix forces applications that use the CompareStringW/LCMapString sorting table to use an older version of the table.

The fix enables the computer to restart and finish the installation process by verifying and enabling that the SeShutdownPrivilege service privilege exists.

The fix invokes the AddRef() method on the Desktop folder, which the SHGetDesktopFolder function returns, to counteract the problem.

The fix either fully implements the obsolete functions or implements the obsolete functions with stubs that fail.

This fix fails calls to RemoveDirectory() when called with a path matching the one specified in the shim command line. Only a single path is supported. The path can contain environment variables, but must be an exact path - no partial paths are supported.

The fix resolves an issue where an application expects RemoveDirectory() to delete a folder immediately even though a handle is open to it.

The fix intercepts the GetCurrentThemeName API and returns the value for the Windows XP default theme (Luna).

The fix enables the WriteFile function to call to the FlushFileBuffers APIs, which flush the file cache onto the hard disk.

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.

The fix exchanges GetDriveType() so that only the root information appears for the file path. This is required when an application passes an incomplete or badly formed file path when it tries to retrieve the drive type on which the file path exists.

The fix modifies the memory status structure, so that it reports a swap file that is 400 MB, regardless of the true swap file size.

The fix supports using lpBuffer validation from the InternetSetOptionA and InternetSetOptionW functions to perform the more parameter validation.

The fix intercepts any API calls that return file attributes and directories that are invoked from the %TEMP% directory. The fix then resets the FILE_ATTRIBUTE_NOT_CONTENT_INDEXED attribute to its original state.

The fix uses zeros to clear out the heap allocation for an application.

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.

The fix links the FindNextFileW, FindNextFileA, FindFirstFileExW, FindFirstFileExA, FindFirstFileW, and FindFirstFileA APIs to prevent them from returning directory junctions.

The fix enables the application to ignore specified exceptions. By default, this fix ignores privileged-mode exceptions; however, it can be configured to ignore any exception.

You can control this fix further by typing the following command at the command prompt:

Exception1;Exception2
Where Exception1 and Exception2 are specific exceptions to be ignored. For example: ACCESS_VIOLATION_READ:1;ACCESS_VIOLATION_WRITE:1.

Important: You should use this compatibility fix only if you're certain that it's acceptable to ignore the exception. You might experience more compatibility issues if you choose to incorrectly ignore an exception.

Before the C runtime library supported floating point SSE2, it ignored the rounding control request and used the round to nearest option by default. This shim ignores the rounding control request to support applications relying on old behavior.

The fix enables color-keyed fonts to properly work with anti-aliasing.

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.

The fix ignores the registered MSOXMLMF.DLL object, which Microsoft® Office 2007 loads into the operating system anytime that you load an XML file, and then it fails the CoGetClassObject for its CLSID. This compatibility fix ignores the registered MSOXMLMF and fails the CoGetClassObject for its CLSID.

The fix intercepts the function call to create the object and replaces the word Global with Local.

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 installationenabling the uninstallation to occur later.

The fix forces the CopyFile APIs to run instead of the MoveFile APIs. CopyFile APIs avoid moving the security descriptor, which enables the application files to get the default descriptor of the destination folder and prevents the security access issue.

The fix reduces the security privilege levels on a specified set of files and folders.

The fix handles the failure case by passing a fake process performance data registry key, so that the application perceives that it's the only instance running.

The fix sets the _PROCESS_HISTORY environment variable so that child processes can look in the parent directory for matching information while searching for application fixes.

The fix addresses the issues that occur when applications use non-standard Administrator checks. This issue can result in false positives for user accounts that are being run as Protected Administrators. In this case, the associated SID exists, but the SID is set as deny-only.

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.

The fix intercepts the CoCreateInstance call for the missing filter and then redirects it to a supported version.

The fix redirects all of the shortcuts created during the application setup to appear according to a specified path.

Start Menu shortcuts: Appear in the \ProgramData\Microsoft\Windows\Start Menu directory for all users.
Desktop or Quick Launch shortcuts: You must manually place the shortcuts on the individual user's desktop or Quick Launch bar.

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 can't access the shortcuts.

You can't apply this fix to an .exe file that includes a manifest and provides a run level.

The fix enables a child .exe file to run with elevated privileges when it's difficult to determine the parent process with either the ElevateCreateProcess fix or by marking the .exe files to RunAsAdmin.

The fix retries the call and requests a more restricted set of rights that include the following items:

The fix retries the OpenService() API call and verifies that the user has Administrator rights, isn't 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 fix to work

The fix enables the application to run by using elevated privileges. The fix is the equivalent of specifying requireAdministrator in an application manifest.

The fix enables the application to run by using the highest available permissions. This fix is the equivalent of specifying highestAvailable in an application manifest.

The fix enables the application to run by using the privileges that are associated with the creation process, without requiring elevation. This fix is the equivalent of specifying asInvoker in an application manifest.

At the command prompt, you can supply a list of objects to modify, separating the values by a double backslash (). Or, you can choose not to include any parameters, so that all of the objects are modified.

Important: Users can't sign in as Session 0 (Global Session) in Windows Vista and later. Therefore, applications that require access to Session 0 automatically fail.

You can control this fix further by typing the following command at the command prompt:Client;Protocol;App
Where the Client is the name of the email protocol, Protocol is mailto, and App is the name of the application.

The fix disables the Wow64 file system that is used by the 64-bit editions of Windows, to prevent 32-bit applications from accessing 64-bit file systems during the application setup.

The fix applies the specified compatibility fixes by modifying the export table and by nullifying the use of module inclusion and exclusion.

The fix intercepts the ShowWindow API call to address the issues that can occur when a web application determines that it is in a child window. This fix calls the real ShowWindow API on the top-level parent window.

The fix flags the application as being an installer file (for example, setup.exe), and then prompts for elevation.

The fix flags the application to exclude it from detection by the GenericInstaller function.

The fix enables customized Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the RegisterWindowMessage function, followed by the ChangeWindowMessageFilter function in the code.

You can control this fix further by typing the following command at the command prompt:

MessageString1 MessageString2
Where MessageString1 and MessageString2 reflect the message strings that can pass.

The fix enables standard Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the ChangeWindowMessageFilter function in the code.

You can control this fix further by typing the following command at the command prompt:

1055 1056 1069

Where 1055 reflects the first message ID, 1056 reflects the second message ID, and 1069 reflects the third message ID that can pass.

The fix enables the registry functions to allow for virtualization, redirection, expansion values, version spoofing, the simulation of performance data counters, and so on.

For more detailed information about this application fix, see Using the VirtualRegistry Fix.

The fix makes the application's DeleteFile function call a virtual call 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.

The fix redirects the HKCR write calls (HKLM) to the HKCU hive for a per-user COM registration. This fix operates much like the VirtualRegistry fix when you use the VirtualizeHKCR parameter; however, VirtualizeHKCRLite provides better performance.

HKCR is a virtual merge of the HKCU\Software\Classes and HKLM\Software\Classes directories. The use of HKCU is preferred if an application isn't elevated and is ignored if the application is elevated.

You typically use this compatibility fix with the VirtualizeRegisterTypeLib fix.
For more detailed information about this application fix, see Using the VirtualizeHKCRLite Fix.

The fix enables the application to ignore the format error and continue to function properly.

All version lie compatibility fixes address the issue whereby an application fails to function because it's checking for, but not finding, a specific version of the operating system. The version lie fix returns the appropriate operating system version information. For example, the VistaRTMVersionLie returns the Windows Vista version information to the application, regardless of the actual operating system version that is running on the computer.

The fix detects whether the WinG32 library exists in the correct directory. If the library is located in the wrong location, this fix copies the information (typically during the runtime of the application) into the %WINDIR% \system32 directory.

Important: The application must have Administrator privileges for this fix to work.

The fix forces the application to follow these steps:

The fix skips the processes of registering and unregistering WRP-protected COM components when calling the DLLRegisterServer and DLLUnregisterServer functions.

You can control this fix further by typing the following command at the command prompt:

Component1.dll;Component2.dll
Where Component1.dll and Component2.dll reflect the components to be skipped.

The fix emulates the successful authentication and modification of file and registry APIs, so that the application can continue.

The fix verifies whether the registry key is WRP-protected. If the key is protected, this fix emulates the deletion process.