Post by Cg on Sept 24, 2015 14:22:19 GMT -5
Just in case you cannot get the link to work fallen.
OK it's an OLD post about an older version, but I think the basic logic still holds. Especially the bit about referencing through the correct tool.
VS2012.2 v110_xp broken - "The procedure entry point InitializeCriticalSectionEx could not be located in the dynamic link library KERNEL32.dll" - by Wouter_Demuynck
Status :
Closed
as Deferred Deferred<br /><br />
The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
A more detailed explanation for the resolution of this particular item may have been provided in the comments section.
56
0
Sign in
to vote
ID 783276 Comments 29
Status Closed Workarounds 6
Type Bug Repros 28
Opened 09/04/2013 07:25:56
Access Restriction Public
Description
After installing Visual Studio 2012 Update 2, our C++ modules that were targeting v110_xp are no longer running on Windows XP/Windows Server 2003.
When launching the application, the following error now shows up (messagebox):
"XXXXXX.exe - Entry Point Not Found"
"The procedure entry point InitializeCriticalSectionEx could not be located in the dynamic link library KERNEL32.dll"
The exact same code compiled fine with Update 1 worked fine on XP/Server 2003.
I tried uninstalling Update 2 but now I cannot download Update 1 anymore, all references online have been updated to point to update 2...
DETAILS
Comments (29) | Workarounds (6) | Attachments (0)
Sign in to post a comment.
Posted by Ion [MSFT] on 13/05/2013 at 14:32
Hi simdoc, can you provide more information about your solution setup, it would be ideal if you could give us a self contained repro, that we can try here. By Intel C++ do you mean that you have a custom project flavor? What errors do you see (entry point not found?)? Do you use ATL from your Intel C++ project?
The Intel C++ compiler/VS-integration is not owned by Microsoft, thus for any issues regarding the generated outup or XP support, please check with Intel. However I'd be happy to help you find the problem. If the Intel C++ toolchain does not have a concept of toolset, then try defining "_USING_V110_SDK71_"
Posted by Ion [MSFT] on 13/05/2013 at 14:31
Hi simdoc, can you provide more information about your solution setup, it would be ideal if you could give us a self contained repro, that we can try here. By Intel C++ do you mean that you have a custom project flavor? What errors do you see (entry point not found?)? Do you use ATL from your Intel C++ project?
The Intel C++ compiler/VS-integration is not owned by Microsoft, thus for any issues regarding the generated outup or XP support, please check with Intel. However I'd be happy to help you find the problem. If the Intel C++ toolchain does not have a concept of toolset, then try defining "_USING_V110_SDK71_"
Posted by simdoc on 13/05/2013 at 09:34
I have a mix of Intel C++ and vc110_xp projects in my solution. I need Intel C++ for the math improvements on many of the projects. The issue arises from the projects compiled with Intel C++. How do you recommend solving that?
Posted by Ion [MSFT] on 11/05/2013 at 18:18
Hi tofutim, simdoc
Please do no use the _ATL_XP_TARGETING macro, it is only used internally, please instead target the vc110_xp toolset.
tofutim, did you set the Platform Toolset to vc110_xp?
Posted by tofutim on 11/05/2013 at 17:18
Hi, I have installed Update 3 RC but the problem persists. @simdoc How and where do I define _ATL_XP_TARGETING?
Posted by simdoc on 09/05/2013 at 15:58
It looks like _ATL_XP_TARGETING has to be #define'd. Is that the intent? Is that going to be the case in the RTM and from then out?
Posted by ta.speot.is on 08/05/2013 at 00:39
I think it is worth being more clear: a Release Candidate of Update 3 is now available.
From www.microsoft.com/en-us/download/details.aspx?id=38832
Statement of Support:
Visual Studio 2012 Update 3 RC and Team Foundation Server 2012 with Update 3 RC are “go-live”. This means that customers can use these builds in production environments. **These are still pre-releases**, so there may be some bugs that will be fixed for the final release. Upgrade from Update 3 RC to Update 3 RTM is supported. In order to upgrade to future releases, the customer must first upgrade from Update 3 RC to Update 3 RTM.
Posted by YLzhou on 07/05/2013 at 20:14
I have Installed update 3 .
when I set "PROJECT ->PROPERTIES ->Confiuration properties->general->use of ATL " to "Static Link to ATL " .Then OK .
Posted by Ion [MSFT] on 07/05/2013 at 17:16
Update 3 is now available, please refer to this post for more information blogs.msdn.com/b/vcblog/archive/2013/05/07/fix-visual-studio-2012-update-2-breaks-windows-xp-targeting-with-atl-and-or-statically-linking-mfc.aspx
Posted by Ion [MSFT] on 07/05/2013 at 17:16
Update 3 is now available, please refer to this post for more information blogs.msdn.com/b/vcblog/archive/2013/05/07/fix-visual-studio-2012-update-2-breaks-windows-xp-targeting-with-atl-and-or-statically-linking-mfc.aspx
Posted by Ion [MSFT] on 06/05/2013 at 16:16
Yes, this is fixed in Update 3
Posted by MathiasWe on 30/04/2013 at 06:27
Will this be fixed in Visual Studio 2012 Update 3?
Posted by ITSTH on 24/04/2013 at 01:34
@microsoft: When will this issue be fixed? Currently we're not able to publish new versions of our software due to this problem.
Posted by turmansk on 19/04/2013 at 12:33
Teds fix works for me too.
Was building on Win7 and testing on XP so had to make some mods to Ted's xpatl.cpp file
Also had some projects that did not include asm in the builds and we had to explicitly set the item type by right clicking the asm file and setting conf props->general->Item Type to the MASM asembler
Posted by JC-Winboats on 19/04/2013 at 04:31
Ted's workaround worked for me also. Thanks Ted you are a life saver!
Posted by Anthony Wieser on 18/04/2013 at 22:49
Ted's workaround does the trick, and fixes this.
Posted by JC-Winboats on 18/04/2013 at 17:05
Add another to the list. Update 2 has broken our program on XP. It is a Native C++ using MFC and we statically link. I may try uninstalling VS 2012 and starting over, but only installing SP1. I hope that works cause we have a lot of customers still using XP.
Posted by turmansk on 18/04/2013 at 15:05
One more to the list. Same issue with it not working after Update 2.
Have MFC in a shared DLL, /Md by default.
Tried the workaround from ted with build customization too, didn't work.
Hope we get a fix soon.
Posted by Ion [MSFT] on 16/04/2013 at 16:25
Thanks for your reports on this issue, we are currently tracking this issue thru connect bug 783137
Posted by Ion [MSFT] on 16/04/2013 at 16:24
Thanks for your reports on this issue, we are currently tracking this issue thru connect id 783137
Posted by Ion [MSFT] on 16/04/2013 at 16:24
Thanks for your reports on this issue, we are currently tracking this issue thru connect id 783137
Posted by ExtraValueNeil on 15/04/2013 at 05:51
Same issue here. It wouldn't be a huge problem if we could go back to SP1 for the time being, but that's no longer available from MS. Hopefully an official fix comes out soon.
Posted by MatthiasGross on 13/04/2013 at 01:54
We also have this problem. After updating to SP2 we got reports from our customers, they had exactly this problem.
I hope this can be fixed without uninstalling SP2.
I think a hotfix or instructions how to change the code to avoid this problem would be appropriate,
but I fear the support of XP hasn't highest priority for MS, I believe this is a mistake.
Until this is not fixed SP2 is pointless for us - many of our customers still use XP.
Posted by MobiCat on 11/04/2013 at 12:12
I am facing this exact same problem. I was able to uninstall Update 2 and then do a repair on the main installation to get it working again. I would very much like an official new update that does not break XP targeting.
Posted by Serhiy Horobets on 11/04/2013 at 07:38
Same problem here. I'm going to remove Update 2 and reinstall VS with Update 1.
Posted by Sha007007 on 11/04/2013 at 02:53
We too faced the same problem. MS should provide either a hotfix or a link to Update 1. Else, we have to compile statically linked MFC apps in VS 2010.
Posted by MeasureWithSoundCard on 10/04/2013 at 22:19
I am facing the same problem. Anxiously waiting for the solution. The posted workarounds by VSBs does not work.
Posted by Macy [MSFT] on 09/04/2013 at 23:28
Thanks for your feedback.
We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Macy [MSFT] on 09/04/2013 at 07:51
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
OK it's an OLD post about an older version, but I think the basic logic still holds. Especially the bit about referencing through the correct tool.
VS2012.2 v110_xp broken - "The procedure entry point InitializeCriticalSectionEx could not be located in the dynamic link library KERNEL32.dll" - by Wouter_Demuynck
Status :
Closed
as Deferred Deferred<br /><br />
The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
A more detailed explanation for the resolution of this particular item may have been provided in the comments section.
56
0
Sign in
to vote
ID 783276 Comments 29
Status Closed Workarounds 6
Type Bug Repros 28
Opened 09/04/2013 07:25:56
Access Restriction Public
Description
After installing Visual Studio 2012 Update 2, our C++ modules that were targeting v110_xp are no longer running on Windows XP/Windows Server 2003.
When launching the application, the following error now shows up (messagebox):
"XXXXXX.exe - Entry Point Not Found"
"The procedure entry point InitializeCriticalSectionEx could not be located in the dynamic link library KERNEL32.dll"
The exact same code compiled fine with Update 1 worked fine on XP/Server 2003.
I tried uninstalling Update 2 but now I cannot download Update 1 anymore, all references online have been updated to point to update 2...
DETAILS
Comments (29) | Workarounds (6) | Attachments (0)
Sign in to post a comment.
Posted by Ion [MSFT] on 13/05/2013 at 14:32
Hi simdoc, can you provide more information about your solution setup, it would be ideal if you could give us a self contained repro, that we can try here. By Intel C++ do you mean that you have a custom project flavor? What errors do you see (entry point not found?)? Do you use ATL from your Intel C++ project?
The Intel C++ compiler/VS-integration is not owned by Microsoft, thus for any issues regarding the generated outup or XP support, please check with Intel. However I'd be happy to help you find the problem. If the Intel C++ toolchain does not have a concept of toolset, then try defining "_USING_V110_SDK71_"
Posted by Ion [MSFT] on 13/05/2013 at 14:31
Hi simdoc, can you provide more information about your solution setup, it would be ideal if you could give us a self contained repro, that we can try here. By Intel C++ do you mean that you have a custom project flavor? What errors do you see (entry point not found?)? Do you use ATL from your Intel C++ project?
The Intel C++ compiler/VS-integration is not owned by Microsoft, thus for any issues regarding the generated outup or XP support, please check with Intel. However I'd be happy to help you find the problem. If the Intel C++ toolchain does not have a concept of toolset, then try defining "_USING_V110_SDK71_"
Posted by simdoc on 13/05/2013 at 09:34
I have a mix of Intel C++ and vc110_xp projects in my solution. I need Intel C++ for the math improvements on many of the projects. The issue arises from the projects compiled with Intel C++. How do you recommend solving that?
Posted by Ion [MSFT] on 11/05/2013 at 18:18
Hi tofutim, simdoc
Please do no use the _ATL_XP_TARGETING macro, it is only used internally, please instead target the vc110_xp toolset.
tofutim, did you set the Platform Toolset to vc110_xp?
Posted by tofutim on 11/05/2013 at 17:18
Hi, I have installed Update 3 RC but the problem persists. @simdoc How and where do I define _ATL_XP_TARGETING?
Posted by simdoc on 09/05/2013 at 15:58
It looks like _ATL_XP_TARGETING has to be #define'd. Is that the intent? Is that going to be the case in the RTM and from then out?
Posted by ta.speot.is on 08/05/2013 at 00:39
I think it is worth being more clear: a Release Candidate of Update 3 is now available.
From www.microsoft.com/en-us/download/details.aspx?id=38832
Statement of Support:
Visual Studio 2012 Update 3 RC and Team Foundation Server 2012 with Update 3 RC are “go-live”. This means that customers can use these builds in production environments. **These are still pre-releases**, so there may be some bugs that will be fixed for the final release. Upgrade from Update 3 RC to Update 3 RTM is supported. In order to upgrade to future releases, the customer must first upgrade from Update 3 RC to Update 3 RTM.
Posted by YLzhou on 07/05/2013 at 20:14
I have Installed update 3 .
when I set "PROJECT ->PROPERTIES ->Confiuration properties->general->use of ATL " to "Static Link to ATL " .Then OK .
Posted by Ion [MSFT] on 07/05/2013 at 17:16
Update 3 is now available, please refer to this post for more information blogs.msdn.com/b/vcblog/archive/2013/05/07/fix-visual-studio-2012-update-2-breaks-windows-xp-targeting-with-atl-and-or-statically-linking-mfc.aspx
Posted by Ion [MSFT] on 07/05/2013 at 17:16
Update 3 is now available, please refer to this post for more information blogs.msdn.com/b/vcblog/archive/2013/05/07/fix-visual-studio-2012-update-2-breaks-windows-xp-targeting-with-atl-and-or-statically-linking-mfc.aspx
Posted by Ion [MSFT] on 06/05/2013 at 16:16
Yes, this is fixed in Update 3
Posted by MathiasWe on 30/04/2013 at 06:27
Will this be fixed in Visual Studio 2012 Update 3?
Posted by ITSTH on 24/04/2013 at 01:34
@microsoft: When will this issue be fixed? Currently we're not able to publish new versions of our software due to this problem.
Posted by turmansk on 19/04/2013 at 12:33
Teds fix works for me too.
Was building on Win7 and testing on XP so had to make some mods to Ted's xpatl.cpp file
Also had some projects that did not include asm in the builds and we had to explicitly set the item type by right clicking the asm file and setting conf props->general->Item Type to the MASM asembler
Posted by JC-Winboats on 19/04/2013 at 04:31
Ted's workaround worked for me also. Thanks Ted you are a life saver!
Posted by Anthony Wieser on 18/04/2013 at 22:49
Ted's workaround does the trick, and fixes this.
Posted by JC-Winboats on 18/04/2013 at 17:05
Add another to the list. Update 2 has broken our program on XP. It is a Native C++ using MFC and we statically link. I may try uninstalling VS 2012 and starting over, but only installing SP1. I hope that works cause we have a lot of customers still using XP.
Posted by turmansk on 18/04/2013 at 15:05
One more to the list. Same issue with it not working after Update 2.
Have MFC in a shared DLL, /Md by default.
Tried the workaround from ted with build customization too, didn't work.
Hope we get a fix soon.
Posted by Ion [MSFT] on 16/04/2013 at 16:25
Thanks for your reports on this issue, we are currently tracking this issue thru connect bug 783137
Posted by Ion [MSFT] on 16/04/2013 at 16:24
Thanks for your reports on this issue, we are currently tracking this issue thru connect id 783137
Posted by Ion [MSFT] on 16/04/2013 at 16:24
Thanks for your reports on this issue, we are currently tracking this issue thru connect id 783137
Posted by ExtraValueNeil on 15/04/2013 at 05:51
Same issue here. It wouldn't be a huge problem if we could go back to SP1 for the time being, but that's no longer available from MS. Hopefully an official fix comes out soon.
Posted by MatthiasGross on 13/04/2013 at 01:54
We also have this problem. After updating to SP2 we got reports from our customers, they had exactly this problem.
I hope this can be fixed without uninstalling SP2.
I think a hotfix or instructions how to change the code to avoid this problem would be appropriate,
but I fear the support of XP hasn't highest priority for MS, I believe this is a mistake.
Until this is not fixed SP2 is pointless for us - many of our customers still use XP.
Posted by MobiCat on 11/04/2013 at 12:12
I am facing this exact same problem. I was able to uninstall Update 2 and then do a repair on the main installation to get it working again. I would very much like an official new update that does not break XP targeting.
Posted by Serhiy Horobets on 11/04/2013 at 07:38
Same problem here. I'm going to remove Update 2 and reinstall VS with Update 1.
Posted by Sha007007 on 11/04/2013 at 02:53
We too faced the same problem. MS should provide either a hotfix or a link to Update 1. Else, we have to compile statically linked MFC apps in VS 2010.
Posted by MeasureWithSoundCard on 10/04/2013 at 22:19
I am facing the same problem. Anxiously waiting for the solution. The posted workarounds by VSBs does not work.
Posted by Macy [MSFT] on 09/04/2013 at 23:28
Thanks for your feedback.
We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Macy [MSFT] on 09/04/2013 at 07:51
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
<ouch!> I just copied and pasted a massive amount of info on the subject. 
