Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Visual Studio FIX: Module state is corrupted in a Visual C++ 2010 MFC application that is running in Windows 8


View products that this article applies to.

Symptoms

Assume that you develop a Visual C++ Microsoft Foundation Class (MFC) application by using Microsoft Visual Studio 2010. The application implicitly or explicitly loads additional DLLs during the CRT_INIT phase of MFC DLL initialization. You try to run the application in Windows 8. In this situation, the module state becomes corrupted. Additionally, the application may crash, and you receive an access violation exception.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

 To apply this hotfix, you must have Visual Studio 2010 Service Pack 1 (SP1) installed.

Restart requirement

You do not have to restart the computer after you install the hotfix if the affected files are not being used at the time of installation. We recommend that you close all Visual Studio 2010-related components before you install the hotfix.
File information
The global 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.

File nameFile versionFile sizeDateTimePlatform
Atl100.dll10.0.40219.447138,89610-Apr-201309:34x86
Atl100.dll10.0.40219.447386,19210-Apr-201309:40IA-64
Atl100.dll10.0.40219.447159,37610-Apr-201310:12x64
Mfc100.dll10.0.40219.4475,579,92010-Apr-201310:12x64
Mfc100.dll10.0.40219.4474,400,78410-Apr-201310:37x86
Mfc100chs.dll10.0.40219.44737,01610-Apr-201310:12x64
Mfc100chs.dll10.0.40219.44737,01610-Apr-201310:37x86
Mfc100cht.dll10.0.40219.44737,01610-Apr-201310:12x64
Mfc100cht.dll10.0.40219.44737,01610-Apr-201310:37x86
Mfc100d.dll10.0.40219.4479,144,46410-Apr-201311:11x64
Mfc100d.dll10.0.40219.4477,064,20810-Apr-201311:31x86
Mfc100deu.dll10.0.40219.44765,17610-Apr-201310:12x64
Mfc100deu.dll10.0.40219.44765,17610-Apr-201310:37x86
Mfc100enu.dll10.0.40219.44755,96010-Apr-201310:12x64
Mfc100enu.dll10.0.40219.44755,96010-Apr-201310:37x86
Mfc100esn.dll10.0.40219.44764,66410-Apr-201310:12x64
Mfc100esn.dll10.0.40219.44764,66410-Apr-201310:37x86
Mfc100fra.dll10.0.40219.44765,17610-Apr-201310:12x64
Mfc100fra.dll10.0.40219.44765,17610-Apr-201310:37x86
Mfc100ita.dll10.0.40219.44763,12810-Apr-201310:12x64
Mfc100ita.dll10.0.40219.44763,12810-Apr-201310:37x86
Mfc100jpn.dll10.0.40219.44744,69610-Apr-201310:12x64
Mfc100jpn.dll10.0.40219.44744,69610-Apr-201310:37x86
Mfc100kor.dll10.0.40219.44744,18410-Apr-201310:12x64
Mfc100kor.dll10.0.40219.44744,18410-Apr-201310:37x86
Mfc100rus.dll10.0.40219.44761,59210-Apr-201310:12x64
Mfc100rus.dll10.0.40219.44761,59210-Apr-201310:37x86
Mfc100u.dll10.0.40219.4475,606,03210-Apr-201310:12x64
Mfc100u.dll10.0.40219.4474,425,87210-Apr-201310:37x86
Mfc100ud.dll10.0.40219.4479,220,76010-Apr-201311:11x64
Mfc100ud.dll10.0.40219.4477,132,82410-Apr-201311:31x86
Mfcm100.dll10.0.40219.44793,84010-Apr-201310:12x64
Mfcm100.dll10.0.40219.44782,57610-Apr-201310:37x86
Mfcm100d.dll10.0.40219.447120,47210-Apr-201311:11x64
Mfcm100d.dll10.0.40219.447104,60010-Apr-201311:31x86
Mfcm100u.dll10.0.40219.44793,84810-Apr-201310:12x64
Mfcm100u.dll10.0.40219.44782,58410-Apr-201310:37x86
Mfcm100ud.dll10.0.40219.447122,00810-Apr-201311:11x64
Mfcm100ud.dll10.0.40219.447106,13610-Apr-201311:31x86
Mfcmifc80u.dll10.0.40219.44713,97611-Apr-201305:02x86
Msvcp100.dll10.0.40219.447422,04010-Apr-201309:34x86
Msvcp100.dll10.0.40219.447967,32010-Apr-201309:40IA-64
Msvcp100.dll10.0.40219.447608,92010-Apr-201310:12x64
Msvcp100d.dll10.0.40219.4471,980,05610-Apr-201310:55IA-64
Msvcp100d.dll10.0.40219.4471,015,44810-Apr-201311:14x64
Msvcp100d.dll10.0.40219.447744,60010-Apr-201311:35x86
Msvcr100.dll10.0.40219.447774,29610-Apr-201309:34x86
Msvcr100.dll10.0.40219.4471,500,31210-Apr-201309:40IA-64
Msvcr100.dll10.0.40219.447830,10410-Apr-201310:12x64
Msvcr100d.dll10.0.40219.4473,764,88810-Apr-201310:55IA-64
Msvcr100d.dll10.0.40219.4471,874,07210-Apr-201311:14x64
Msvcr100d.dll10.0.40219.4471,506,45610-Apr-201311:35x86
Vcomp100.dll10.0.40219.447144,53610-Apr-201309:40IA-64
Vcomp100.dll10.0.40219.44759,03210-Apr-201310:12x64
Vcomp100.dll10.0.40219.44752,37610-Apr-201310:37x86
Vcomp100d.dll10.0.40219.447318,61610-Apr-201310:51IA-64
Vcomp100d.dll10.0.40219.447108,69610-Apr-201311:07x64
Vcomp100d.dll10.0.40219.44789,75210-Apr-201311:28x86
Vcomp100ui.dll10.0.40219.44710,39211-Apr-201305:02x86
Vcomp100ui.dll10.0.40219.44710,90411-Apr-201305:02x86
Vcomp100ui.dll10.0.40219.44711,92811-Apr-201305:02x86
Vcomp100ui.dll10.0.40219.44712,44011-Apr-201305:02x86
Vcredist_ia64.exe10.0.40219.4473,049,57610-Apr-201312:30x86
Vcredist_x64.exe10.0.40219.44710,287,20010-Apr-201312:38x86
Vcredist_x86.exe10.0.40219.4479,011,80810-Apr-201312:41x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


References

For more information about the DllMain entry point, go to the following MSDN website:

For more information about the best practices for creating DLLs, go to the following MSDN website:


↑ Back to the top


Keywords: kbqfe, kbhotfixserver, kbfix, kbexpertiseadvanced, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 2820571
Revision : 1
Created on : 1/7/2017
Published on : 5/3/2013
Exists online : False
Views : 288