Article ID: 921337 - View products that this article applies to.
When you add a manifest that has the Microsoft Windows Vista extension to an .exe file or to a .dll file, the computer may restart. This problem occurs on a Windows XP Service Pack 2 (SP2)-based computer and on a Windows Embedded for Point of Service (WEPOS) device. Additionally, this problem occurs when the .exe file runs or when the .dll file loads. The following is a sample of a manifest segment that has the Microsoft Windows Vista extension.
//The section between >>>>> and <<<< is the problematic section. <assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0"> <assemblyIdentity version="184.108.40.206" processorArchitecture="X86" name="Synergex.Synergyde.lm" type="win32"> </assemblyIdentity> <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="Microsoft.VC80.CRT" version="8.0.50608.0" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"> </assemblyIdentity> </dependentAssembly> </dependency> >>>>>>>>>>> <ms_asmv3:trustInfo xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3" xmlns="urn:schemas-microsoft-com:asm.v3"> <ms_asmv3:security xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3"> <requestedPrivileges> <requestedExecutionLevel level="requireAdministrator" uiAccess="false"> </requestedExecutionLevel> </requestedPrivileges> </ms_asmv3:security> </ms_asmv3:trustInfo> <<<<<<<<<<< </assembly>
This problem occurs when Csrss.exe is loading an .exe file or a .dll file that contains a manifest that has Windows Vista extensions. When parsing the embedded manifest, its internal memory can be corrupted if it finds a single tag that has two schema properties. Here is the tag from the example earlier in this article that has two schema properties:
<ms_asmv3:trustInfo xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3" xmlns="urn:schemas-microsoft-com:asm.v3">When Csrss.exe encounters such a tag, the memory corruption causes an access violation in Csrss.exe. This causes Windows to restart. End-users can resolve this by obtaining the hotfix that is mentioned in this article. Software developers can avoid this problem by making sure that only a single schema exists for all properties in a manifest. For this example, the following tag would avoid this problem.
<ms_asmv3:trustInfo xmlns:ms_asmv3="urn:schemas-microsoft-com:asm.v3">Manifests that are created by Visual Studio 2005 can exhibit this behavior. This issue will be addressed by an updated Mt.exe file in Visual Studio 2005 Service Pack 1.
Hotfix informationA supported feature that modifies the default behavior of the product is available from Microsoft. However, this feature is intended to modify only the behavior that this article describes. Apply this feature only to systems that specifically require it. This feature might receive additional testing. Therefore, if the system is not severely affected by the lack of this feature, we recommend that you wait for the next software update that contains this feature.
If the feature is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the feature.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific feature. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
PrerequisitesTo apply this hotfix, you must have Windows XP Service Pack 2 or WEPOS installed on the computer.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Contact us for more help
Connect with Answer Desk for expert help.