My 64-bit computer thinks it's 32-bit

Xenrac

Reputable
Mar 28, 2014
2
0
4,510
I have a 64-bit HP Pavillion with 64-bit Windows 7 installed. However, my 64-bit command prompt will not run, giving me an error that it is incompatible with my machine no matter where I run it from or how.

I've limped along for a long while without a command prompt (because it's not vital to my day to day use of this computer), but I recently noticed that running the 32-bit command prompt as an Admin runs it through C:\Windows\System32>
This is a lie. [strike]All 64-bit files are inaccessible.[/strike]
Update: More tinkering with system variables seems to have let me access the right place. However, the overall problem still exists, as everything the command prompt writes to a file still ends up in C:\Windows\SysWOW64 regardless.

Just now, I was tinkering with my system variables (for a relatively unrelated project), and noticed that while all of the most vital functions redirected through System32, none of the program-related System variables lead through the Programs file: all are through Programs (86).

I'm starting to get the sinking feeling that my computer is slow simply because it's a 64-bit machine that, to do anything other than scratch it's nose, has to emulate itself as a 32-bit machine.
 
Solution
There are still many applications that are still 32-bit only. That doesn't mean they are slower than 64-bit applications. Also many 32-bit programs use less memory. 64-bit Windows still retains many 32-bit libraries that are used by 32-bit applications. c:\windows\system32 contains 64-bit binaries. C:\Windows\SysWOW64 contains 32-bit binaries.

pbm86

Distinguished
Jan 9, 2012
372
0
18,960
There are still many applications that are still 32-bit only. That doesn't mean they are slower than 64-bit applications. Also many 32-bit programs use less memory. 64-bit Windows still retains many 32-bit libraries that are used by 32-bit applications. c:\windows\system32 contains 64-bit binaries. C:\Windows\SysWOW64 contains 32-bit binaries.
 
Solution

Xenrac

Reputable
Mar 28, 2014
2
0
4,510


Probably crap specs, but that last comment was just feverdreams of not understanding the problem
But yes, I do know the flip flop of names. My computer doesn't run the 64-bit command prompt. Thinks it's incompatible.
It will run the 32-bit command prompt in the SysWOW64 file.

Also included some updates because I'm working on this as I go. Just found a workaround for the reason this problem has become an issue, but the core problem is still there.