Home/ Questions/Q 493339
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T02:12:17+00:00

I’m updating my operating system to Windows 7 x64, I only have experience with

  • 0

I’m updating my operating system to Windows 7 x64, I only have experience with running 32-bit operating systems. Does anyone have any bad/good experiences with a 64 bit environment?

For reference, the tools I use are:

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Running on a 64-bit operating system has a number of side effects that will be noticeable to some extent. The most common issues:

    • Edit and Continue in Visual Studio won’t work. You can fix this by forcing your .NET app to run in 32-bit mode. Project + Properties, Build tab, Platform Target = x86. Resolved in VS2013.

    • If you use any ActiveX controls or COM components in your .NET app you may find your program no longer works since your machine doesn’t have a corresponding 64-bit version of the COM server. You’ll get error 0x80040154, REGDB_E_CLASSNOTREG, “Class not registered”. Same fix as above.

    • The 64-bit debugger doesn’t support mixed-mode debugging, you’ll have to commit to either Managed only or Native only debugging. Same fix as above, as long as you don’t have 64-bit specific issues. Resolved in VS2010.

    • Poorly written P/Invoke declarations that declare an uint or int where an IntPtr is required will stop working in 64-bit mode. You’ll generally get an AccessViolation exception or a failure return code. Or a PInvokeStackImbalance MDA warning. You should not have any trouble locating the mistake, just fix the declaration.

    • Several legacy end-of-life Microsoft libraries are not available in a 64-bit version. That’s most commonly a problem with Microsoft Access databases. Same fix as above.

    • You must use the correct version of Regasm.exe to register [ComVisible] assemblies. Select the one from either Framework or Framework64, depending on whether the client program is going to run in 64-bit or 32-bit mode. Or both if you want the server to be available in either.

    • A few COM type libraries contain bit-ness dependent arguments in their method declarations. ADO 2.8 is a notable one. Be sure to use the correct bitness of Tlbimp.exe to generate the correct COM interop assembly, Visual Studio won’t do this right. Same approach as Regasm.exe

    • A 32-bit program has a different view of the registry from a 64-bit program. Specifically the HKCR and HKLM\Software hives are virtualized. In Regedit.exe, the 32-bit visible keys are seen under the HKLM\Software\Wow6432Node key. This can cause many subtle problems with programs that use the registry. The .NET 4 RegistryKey.OpenBaseKey() allows specifying the view you want.

    • Again for COM, you’ll have the use the correct bitness of Regsvr32.exe to register an unmanaged COM server (not .NET servers, they use Regasm.exe). Use the one in c:\windows\system32 for 64-bit servers, c:\windows\syswow64 for 32-bit servers.

    • Folders in the file system are virtualized, specifically c:\windows\system32 and c:\program files. A 32-bit program will see c:\windows\syswow64 and c:\program files (x86).

    • Installers need to take all the above issues in consideration.

    • 0