Compatibility Issues With Windows Vista
Error Code 5 in Windows VistaInstalling ColorMunki Photo or ColorMunki Design software on the Windows Vista platform and getting Error Code 5Microsoft has released an update to resolve reliability and application compatibility issues in Windows Vista. If you have received an Error Code 5 message, please go to the following link to download an update from Microsoft that will resolve this problem.Microsoft explains that 'this update resolves reliability and application compatibility issues in Microsoft XML Core Service 4.0 Service Pack 2.
By installing this update, you can achieve better reliability and application compatibility. After you install this item, you may have to restart your computer. Once you have installed this item, it cannot be removed.'
ImportantThe 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 FixesThe 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.
FixFix Description8And16BitAggregateBltsApplications that are mitigated by 8/16-bit mitigation can exhibit performance issues. This layer aggregates all the blt operations and improves performance.8And16BitDXMaxWinModeApplications that use DX8/9 and are mitigated by the 8/16-bit mitigation are run in a maximized windowed mode. This layer mitigates applications that exhibit graphical corruption in full screen mode.8And16BitGDIRedrawThis fix repairs applications that use GDI and that work in 8-bit color mode. CorrectCreateBrushIndirectHatchThe problem is indicated by an access violation error message that displays and when the application fails when you select or crop an image.The fix corrects the brush style hatch value, which is passed to the CreateBrushIndirect function and enables the information to be correctly interpreted.CorrectFilePathsThe problem is indicated when an application tries to write files to the hard disk and is denied access or receives a file not found or path not found error message.The fix modifies the file path names to point to a new location on the hard disk.
CustomNCRenderThis fix instructs DWM to not render the non-client area, thereby forcing the application to do its own NC rendering. This often gives windows an XP look.DelayApplyFlagThis fix applies a KERNEL, USER, or PROCESS flag if the specified DLL is loaded.You can control this fix further by typing the following command at the command prompt:DLLName;FlagType;HexidecimalValueWhere the DLLName is the name of the specific DLL, including the file extension.
FlagType is KERNEL, USER, or PROCESS, and a HexidecimalValue, starting with 0x and up to 64-bits long. DeprecatedServiceShimThe problem is indicated when an application tries to install a service that has a dependency on a deprecated service. An error message displays.The fix intercepts the CreateService function calls and removes the deprecated dependency service from the lpDependencies parameter.You can control this fix further by typing the following command at the command prompt:DeprecatedServiceAppService/DeprecatedService2 AppService2Where DeprecatedService is the name of the service that has been deprecated and AppService is the name of the specific application service that is to be modified; for example, NtLmSspWMI. ExtraAddRefDesktopFolderThe problem occurs when an application invokes the Release method too many times and causes an object to be prematurely destroyed.The fix counteracts the application's tries to obtain the shell desktop folder by invoking the AddRef method on the Desktop folder, which is returned by the SHGetDesktopFolder function.FailObsoleteShellAPIsThe problem occurs when an application fails because it generated deprecated API calls.The fix either fully implements the obsolete functions or implements the obsolete functions with stubs that fail.
FailRemoveDirectoryThe problem occurs when an application uninstallation process does not remove all of the application files and folders.This fix fails calls to RemoveDirectory when called with a path matching the one specified in the shim command-line. Only a single path is supported. The path can contain environment variables, but must be an exact path – no partial paths are supported.The fix can resolve an issue where an application expects RemoveDirectory to delete a folder immediately even though a handle is open to it.FakeLunaThemeThe problem occurs when a theme application does not properly display: the colors are washed out or the user interface is not detailed.The fix intercepts the GetCurrentThemeName API and returns the value for the Windows XP default theme, (Luna). FlushFileThis problem is indicated when a file is updated and changes do not immediately appear on the hard disk. Applications cannot see the file changes.The fix enables the WriteFile function to call to the FlushFileBuffers APIs, which flush the file cache onto the hard disk.FontMigrationThe fix replaces an application-requested font with a better font selection, to avoid text truncation.ForceAdminAccessThe problem occurs when an application fails to function during an explicit administrator check.The fix allows the user to temporarily imitate being a part of the Administrators group by returning a value of True during the administrator check. IgnoreExceptionThe problem is indicated when an application stops functioning immediately after it starts, or the application starts with only a cursor appearing on the screen.The fix enables the application to ignore specified exceptions.
By default, this fix ignores privileged-mode exceptions; however, it can be configured to ignore any exception.You can control this fix further by typing the following command at the command prompt:Exception1;Exception2Where Exception1 and Exception2 are specific exceptions to be ignored. For example: ACCESSVIOLATIONREAD:1;ACCESSVIOLATIONWRITE:1. IgnoreFloatingPointRoundingControlThis fix enables an application to ignore the rounding control request and to behave as expected in previous versions of the application.Before floating point SSE2 support in the C runtime library, the rounding control request was being ignored which would use round to nearest option by default. This shim ignores the rounding control request to support applications relying on old behavior.IgnoreFontQualityThe problem occurs when application text appears to be distorted.The fix enables color-keyed fonts to properly work with anti-aliasing.IgnoreMessageBoxThe problem is indicated by a message box that displays with debugging or extraneous content when the application runs on an unexpected operating system.The fix intercepts the MessageBox. APIs and inspects them for specific message text.
If matching text is found, the application continues without showing the message box. IgnoreMSOXMLMFThe problem is indicated by an error message that states that the operating system cannot locate the MSVCR80D.DLL file.The fix ignores the registered MSOXMLMF.DLL object, which Microsoft® Office 2007 loads into the operating system any time that you load an XML file, and then it fails the CoGetClassObject for its CLSID. ManageLinksThe fix intercepts common APIs that are going to a directory or to an executable (.exe) file, and then converts any symbolic or directory junctions before passing it back to the original APIs.MirrorDriverWithCompositionThe fix allows mirror drivers to work properly with acceptable performance with desktop composition.MoveToCopyFileShimThe problem occurs when an application experiences security access issues during setup.The fix forces the CopyFile APIs to run instead of the MoveFile APIs. CopyFile APIs avoid moving the security descriptor, which enables the application files to get the default descriptor of the destination folder and prevents the security access issue.OpenDirectoryAclThe problem is indicated by an error message that states that you do not have the appropriate permissions to access the application.The fix reduces the security privilege levels on a specified set of files and folders.
PopCapGamesForceResPerfThe fix resolves the performance issues in PopCap games like Bejeweled2. RetryOpenServiceWithReadAccessThe problem occurs when an Unable to open service due to your application using the OpenService API to test for the existence of a particular service error message displays.The fix retries the OpenService API call and verifies that the user has Administrator rights, is not a Protected Administrator, and by using read-only access. Applications can test for the existence of a service by calling the OpenService API but some applications ask for all access when making this check. This fix retries the call but only asking for read-only access. The user needs to be an administrator for this to work.
SetupCommitFileQueueIgnoreWowThe problem occurs when a 32-bit setup program fails to install because it requires 64-bit drivers.The fix disables the Wow64 file system that is used by the 64-bit editions of Windows, to prevent 32-bit applications from accessing 64-bit file systems during the application setup.SharePointDesigner2007The fix resolves an application bug that severely slows the application when it runs in DWM.ShimViaEATThe problem occurs when an application fails, even after applying acompatibility fix that is known to fix an issue. Serial xpand rally xtreme para pc. Applications that use unicows.dll or copy protection often present this issue.The fix applies the specified compatibility fixes by modifying the export table and by nullifying the use of module inclusion and exclusion. ShowWindowIEThe problem occurs when a web application experiences navigation and display issues because of the tabbing feature.The fix intercepts the ShowWindow API call to address the issues that can occur when a web application determines that it is in a child window. This fix calls the real ShowWindow API on the top-level parent window.SierraWirelessHideCDROMThe fix repairs the Sierra Wireless Driver installation, thereby preventing bugcheck.Sonique2The application uses an invalid window style, which breaks in DWM. This fix replaces the window style with a valid value.SpecificInstallerThe problem occurs when an application installation file fails to be picked up by the GenericInstaller function.The fix flags the application as being an installer file (for example, setup.exe), and then prompts for elevation. SystemMetricsLieThe fix replaces SystemMetrics values and SystemParametersInfo values with the values of previous Windows versions.TextArtThe application receives different mouse coordinates with DWM ON versus DWM OFF, which causes the application to hang.
This fix resolves the issue.TrimDisplayDeviceNamesThe fix trims the names of the display devices that are returned by the EnumDisplayDevices API.UIPICompatLoggingThe fix enables the logging of Windows messages from Internet Explorer and other processes.UIPIEnableCustomMsgsThe problem occurs when an application does not properly communicate with other processes because customized Windows messages are not delivered.The fix enables customized Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the RegisterWindowMessage function, followed by the ChangeWindowMessageFilter function in the code.You can control this fix further by typing the following command at the command prompt:MessageString1 MessageString2Where MessageString1 and MessageString2 reflect the message strings that can pass. UIPIEnableStandardMsgsThe problem occurs when an application does not communicate properly with other processes because standard Windows messages are not delivered.The fix enables standard Windows messages to pass through to the current process from a lower Desktop integrity level. This fix is the equivalent of calling the ChangeWindowMessageFilter function in the code.You can control this fix further by typing the following command at the command prompt:1055 1056 1069Where 1055 reflects the first message ID, 1056 reflects the second message ID, and 1069 reflects the third message ID that can pass. VirtualizeHKCRLiteThe problem occurs when an application fails to register COM components at runtime.The fix redirects the HKCR write calls (HKLM) to the HKCU hive for a per-user COM registration.
This operates much like the VirtualRegistry fix when you use the VirtualizeHKCR parameter; however, VirtualizeHKCRLite provides better performance.HKCR is a virtual merge of the HKCUSoftwareClasses and HKLMSoftwareClasses directories. The use of HKCU is preferred if an application is not elevated and is ignored if the application is elevated.You typically will use this compatibility fix in conjunction with the VirtualizeRegisterTypeLib fix.For more detailed information about this application fix, see.VirtualizeRegisterTypeLibThe 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. WaveOutIgnoreBadFormatThis problem is indicated by an error message that states: Unable to initialize sound device from your audio driver; the application then closes.The fix enables the application to ignore the format error and continue to function properly.WerDisableReportExceptionThe fix turns off the silent reporting of exceptions to the Windows Error Reporting tool, including those that are reported by Object Linking and Embedding-Database (OLE DB). The fix intercepts the RtlReportException API and returns a STATUSNOTSUPPORTED error message.Win7RTM/Win8RTMThe layer provides the application with Windows 7/Windows 8 compatibility mode.WinxxRTMVersionLieThe problem occurs when an application fails because it does not find the correct version number for the required Windows operating system.All version lie compatibility fixes address the issue whereby an application fails to function because it is checking for, but not finding, a specific version of the operating system.
Compatibility Issues With Windows Vista 10
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.Wing32SystoSys32The problem is indicated by an error message that states that the WinG library was not properly installed.The fix detects whether the WinG32 library exists in the correct directory. If the library is located in the wrong location, this fix copies the information (typically during the runtime of the application) into the%WINDIR% system32 directory.
Windows Vista Definition
WinSrv08R2RTMWinXPSP2VersionLieThe problem occurs when an application experiences issues because of a VB runtime DLL.The fix forces the application to follow these steps:.Open the Compatibility Administrator, and then select None for Operating System Mode.On the Compatibility Fixes page, click WinXPSP2VersionLie, and then click Parameters.The Options for dialog box appears.Type vbrun60.dll into the Module Name box, click Include, and then click Add.Save the custom database. WRPRegDeleteKeyThe problem is indicated by an access denied error message that displays when the application tries to delete a registry key.The fix verifies whether the registry key is WRP-protected. If the key is protected, this fix emulates the deletion process.XPAfxIsValidAddressThe fix emulates the behavior of Windows XP for MFC42!AfxIsValidAddress.Compatibility ModesThe following table lists the known compatibility modes.