64-bit 3.3 python.exe crashes with 0xc000007b error

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Fresh installs of 3.3.2.1 or 3.3.2.0.
2. IPython, SPyder, WinPython shortcuts crash silently.
3. Double-click on python.exe in python-3.3.2.amd64 folder.

What is the expected output? What do you see instead?
Python.exe won't start on my work desktop; raises a 0xc000007b error. But it 
works on my personal laptop.

What version of the product are you using? On what operating system?
64-bit 3.3.2.1 or 3.3.2.0 crash on my Windows 7 Pro work desktop.
64-bit 3.3.2.0 works on my Windows 7 Home laptop (haven't tried 3.3.2.1).
64-bit 2.7.5.1 works on both machines.
32-bit versions work on both machines.

Please provide any additional information below.
Used Dependency Walker to find that MSVCR100.dll in the python-3.3.2.amd64 
folder is a 32-bit version. Downloaded the MS redistributable package to get a 
64-bit version, copied it into the above folder, and now everything appears to 
work (although it sometimes takes a second attempt). Perhaps my laptop was able 
to use the correct DLL from a different location.

Original issue reported on code.google.com by btcoooo...@gmail.com on 12 Jun 2013 at 3:32

[GoogleCodeExporter]

I confirm that the embedded DLLs in WinPython 64bit 3.3.2.1 are in fact 32-bit 
versions due to an anomaly on one of my build machines. I've already 
implemented a way to avoid such architecture mismatch in the future but I 
haven't found a way to fix this machine configuration. In the meantime, I'll 
build WinPython with another machine (don't have the time to dig further 
unfortunately).

WinPython 32bit 3.3, 32bit 2.7 and 64bit 2.7 are indeed not affected by this 
bug.

Original comment by pierre.raybaut on 17 Jun 2013 at 3:42

• Changed state: Started
• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Thanks for all of your hard work on this project!

Original comment by btcoooo...@gmail.com on 17 Jun 2013 at 4:27

[GoogleCodeExporter]

I would very much appreciate it if you could roll out a new release with this 
fix. My university is planning to use WinPython for its upcoming introduction 
to programming and we have to start distributing the software to the university 
computers soon.

When do you think the next release of winpython 3.3 Win64 will be released?

Original comment by basti.be...@gmail.com on 8 Aug 2013 at 9:02

[GoogleCodeExporter]

I'll try and look into it next week and I should be able to make a new release 
during next week. 

Original comment by pierre.raybaut on 8 Aug 2013 at 8:55

[GoogleCodeExporter]

This should be fixed with v3.3.2.2, hopefully.

Original comment by pierre.raybaut on 15 Aug 2013 at 7:43

• Changed state: Fixed

[GoogleCodeExporter]

Issue 53 has been merged into this issue.

Original comment by pierre.raybaut on 15 Aug 2013 at 7:45