You have to place the file in the systemwow folder, run the cmd there FIRST, THEN place the file in your system32 as well and run the cmd there. Doing just one or the other won't work. Both are required if you have a program that depends on the comdlg32.ocx being present on a 64bit Windows 7 installation.Just now found that out myself.
Hire is the reason for the problem and why non of this solutions work:
Check your Windows directory name!
C:\Windows
C:\WINXP
C:\???
By default the xx software is looking for .ocx in the windows folder
For XP Pro C:\Windows is the correct directory
if you use a butchered copy of WINDOWS you usually get this kind of timewasteng pain in the ass stupidity where correct solution its good 4 nothing
This files are usually associated with hardware fingerprinting so if its specific machine locked software, key-gens or similar its extremely frustrating
Quote