Note: Microsoft recommends to install Office 32bit as some of the add-ins are not compatible with 64bit version of Office. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. In reply to Anula D'Souza's post on June 30, I'll try that, its volume licensing. Ive tried view and changing the shown files plus and standard, I had done this before but I forgot how I did it. I need it on exchange server I know I found the x64 folder but can't find it again Palcouk Volunteer Moderator.
In reply to John Reedy's post on June 30, Do you actually need to use the 64bit version? In reply to Palcouk's post on June 30, Yes it is for exchange import export pst mailboxes Otherwise I wouldn't. Ok I just copied the dvdto the desktop same there is no x64 bit folder? The reason is to make upgrading a program to bit easier for developers. Similarly, the registry entries are isolated between bit and bit programs. This prevents conflicts from unknowing developers who just change their compilation mode to bit without putting much thought into it, and prevents an enormous amount of work for developers who want users to be able to install both and bit versions of their software simultaneously.
But why would any program want to allow both version to be installed simultaneously? One example: Photoshop and IE have extensions that are native. You cannot have and bit code mixed in the same process, so an addon for the bit version cannot be used with the bit version, and vice-versa. Programs that runs on "Program Files x86 " use the WOW64 subsystem Windows bit on Windows bit is a set of drivers and APIs intented to run x32 applications over a x64 architecture system :. The WoW64 subsystem comprises a lightweight compatibility layer that has similar interfaces on all bit versions of Windows.
It aims to create a bit environment that provides the interfaces required to run unmodified bit Windows applications on a bit system. It's interesting that the answers here and across the internet vary quite a bit. Finding an accurate answer to this important question has been a challenge. There appears to be quite a bit of false information presented on the internet, leading to confusion. I've performed a significant amount of research, and have drawn the following conclusion, which I believe is accurate:.
This happens automatically, and is independent of where the application is stored. There is no speed, reliability, or other functional benefit to having separate bit and bit folders. The sole reason for the default separation into two folders 'Program Files' and 'Program Files x86 ' is that if you have two versions of the same program a bit and bit version , it provides a simple way to keep overlapping files separate.
Even in this case, as long as all the filenames are unique, they could actually exist in the same folder without any consequence. There is a caveat to the above conclusion, and that is the one of poorly coded applications. If an application has any paths hardcoded into it, it will only use that path.
As a rule, paths should never be hardcoded into an application, but occasionally a programmer will make this mistake. In this case, the program will use the hardcoded path; the directory in which the application is installed will not affect where it actually looks for files. Having to separate folders makes it possible to keep the native bit applications and thos that require the WoW64 apart. This can be useful — as OliverSalzburg already pointed out — if you wish to install both he bit and bit of a web browser for example , since some plug-ins and add-ons might only available for one of the two.
Having to separate folders makes this separation automatic , using techniques such as registry redirection. Suppose an installer tries to determine the program files folder by reading the registry by using, e. However, if the installer is a bit application, registry redirection will cause the regitry key. Why these particular folder names have been used can only be answered by the people who made this choice.
You could always change the default folders' names if you want to. I doubt it. Most installers permit you to choose a custom installation folder, so it doesn't really matter where a program gets installed. MS did this to solve the case where a DLL is used by both older bit applications and newer bit applications. The older method could not be changed System32, Program Files, etc. So MS created a folder to store bit specific programs, assemblies and libraries so that new programs could link to the proper libraries, and older programs would continue working as normal.
As it stands,. Net DLLs can coexist with other versions on the same machine. For example, you can have Library. And this is only for a specific bit size 32 or If separate folders are not used, then every assembly needs to have a 32 and 64 bit version. This would severely clutter up a directory that already contains multiple versions of the same assembly.
This is all developer stuff. As a user I only have to deal with it when I'm working with a bit program on Windows 7 And I prefer having the ability to run a bit version and the same application in bit as well.
When I'm working on a bit application that I need to compile in bit, all I do is tell the compiler to do so. Dll names and everything else stays the same. It faked bit execution with something named "thunking". It is not necessary at all.
Of course, this prevents me to install both versions 32 and 64 bit of one application, but this is no problem in my case. This DLL determines whether your program is a 32 or 64 bit application. Depending on that you are redirected to WoW64 which is mentioned in several answers already. Sign up to join this community.
The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Why does bit Windows need a separate "Program Files x86 " folder?
Ask Question. Asked 9 years, 4 months ago. Active 6 years, 6 months ago. Viewed k times. Improve this question. Der Hochstapler Stephen Jennings Stephen Jennings One-liner answer and hence a comment : since you can easily run any application from any folder without knowing its architecture, then there's clearly no compulsory reason for this separation.
It is a matter of convenience to support double installs of applications with both architectures. In some cases it makes a difference as they are not necessarily simple recompiles. The main problem is that 32 bit apps can't load 64 bit dlls, so you can't typically install both versions in the same place.
The other alternative is having two "bin" folders for each application. Synetech I even had programs installing under x86 just to have x64 binaries.. It's horrible sometimes. Show 4 more comments. Hi friends, In my suite installer , i have to set the program files folder path based on x64 and x Why is it so? Currently i did a work-around to fetch the details using Environment variable, but i want to know the reason behind this issue - Why ProgramFiles64Folder doesnt return the correct value?
Any thoughts guys? Labels 1. Advertisement bit versus bit computers and Windows Since the mids almost all computers that have been sold have been bit computers, and mostly they have had a bit Windows installed. But after the release of Windows 7 , the sales of bit computers with a bit Windows installed have increased a lot. In the coming years, more and more people will have a bit computer with a bit Windows in their home or office.
One reason to this is that the price of a bit computer have decreased so much that they are almost as cheap as bit computers. And people will prefer bit computers over bit computers because they can handle much more RAM memory and they are generally faster because they use more modern technology.
Mostly around 3 GB because a large part of the address space is used by video cards and other devices such as network cards, sound cards etc. This is true even if you install 4 GB in the computer. With bit computers and bit Windows things are different.
0コメント