Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8725533
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T08:03:40+00:00 2026-06-13T08:03:40+00:00

I created a 64bit c++ project in Visual Studio 2010 (under Windows 7 64bit);

  • 0

I created a 64bit c++ project in Visual Studio 2010 (under Windows 7 64bit);

I thought I was running a 64bit application, and the following code returned true:

bool is64bit = (sizeof(void*)==8);

but if I called the function IsWow64Process, it returned FALSE…

More weird things:

  • calling LoadLibrary() to load a dll under c:\windows\system32\some.dll works well
  • loading a dll under c:\windows\sysWow64\some.dll will fail (error code 193: some.dll is not a valid win32 application)

All these failures suggest the application is running under 32bit mode,
but this is against the truth the pointer type is 8-byte length

I am confused, any help will be appreciated!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-13T08:03:41+00:00Added an answer on June 13, 2026 at 8:03 am

    calling LoadLibrary() to load a dll under c:\windows\system32\some.dll works well; loading a dll under c:\windows\sysWow64\some.dll will fail

    Everything you say suggests that you are running 64 bit.

    In Windows 64bit, the System32 folder contains the 64 bit versions of the DLLs, and the SysWow64 folder contains the 32 bit versions. When IsWow64Process returns TRUE, it means that you’re a 32bit application on a 64bit OS.

    This is the opposite of what the names in the folder suggests, which is likely why this seems confusing. Basically, the SysWow64 folder is the 32 bit versions for use under WoW64, which is “Windows 32-bit on Windows 64-bit” – basically, you use the WoW64 DLLs when you run 32bit, and the normal DLLs when you run 64bit.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I've created a new project using the Visual Studio 2010's wizard. Once VS was
On a 32 bit Windows Server 2003 machine I have created a Visual Studio
I have several Windows Service projects in one solution in Visual Studio 2010, they
I'm developing a Windows Forms application using Visual Studio 2008 C# that uses an
I have created a very simple window service using visual studio 2010 and .NُET
I created a C# Project in Visual Studio and used an assembly on the
I want to create a Windows 7 64-bit (Ultimate) virtual machine with: Visual Studio
I'm having some problems with Edit and Continue when using Visual Studio 2010 on
After converting to Visual Studio 2010 with ReSharper5 some of my unit tests started
All: We are using Visual Studio 2010, and we have recently upgraded our workstations

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.