How to Open and Run 32-bit Command Prompt in 64-bit (x64) Windows如何打开和运行32位命令提示符在64位（ x64 ）的Windows
64-bit or x64 version of Windows operating system such as Windows Server 2003, Windows XP Professional x64 Edition, Windows Vista and Windows Server 2008 uses the Microsoft Windows-32-on-Windows-64 (WOW64) subsystem layer to run 32-bit programs, binaries or drivers without modifications, change or transition to 64-bit based binaries, as the 64-bit OS is optimized to run native 64-bit programs and does not provide support for 16-bit binaries or 32-bit drivers. 64位或x64版本的Windows作业系统，例如在Windows Server 2003 ， Windows XP Professional x64版本， Windows Vista和Windows Server 2008使用Microsoft Windows - 32 -对-的Windows 64 （ wow64 ）子系统层，以运行32位程序，二进制文件或司机没有修改，改变或过渡到64位基于二进制文件，由于64位元作业系统的优化运行64位程序，并不提供支持16位的二进制文件或32位驱动程序。
To reduce compatibility issue and prevent a 32-bit program from accidentally accessing data from 64-bit application, WOW64 subsystem isolates 32-bit binaries from 64-bit binaries by redirecting registry calls and some file system calls.以减少兼容性问题，并防止32位元程式从意外进入数据从64位应用， WOW64子系统株32位的二进制文件，从64位的二进制文件是由注册表中呼吁重新导向和一些档案系统的来电。 Other than separate registry hive for WOW64 redirected 32-bit values, %systemroot%\System32 and Program Files folder is designated as 64-bit DLLs only too, and all access or I/O of 32-bit binaries been redirected from %windir%\System32 folder to the %windir%\SysWOW64 folder, and from Program Files to Program Files (x86) directory.以外的其他单独的登录Hive wow64自由的32位的价值观，将％ SystemRoot ％ \ system32和Program Files文件夹被指定为64位的DLL ，只有太，所有访问或I / O的32位的二进制文件被自由的％ windir ％ \ System32文件夹到％ windir ％ \ Syswow64资料夹，并从程序文件程序文件（ x86 ）的目录。
The command prompt (cmd.exe) is also affected by命令提示符（ cmd.exe ）也受 File System Redirection文件系统重定向 feature, where command line commands or .bat and .cmd batch script may not be able to access, install, change, modify, delete or write to “Program Files” or “%windir%\System32″ folder.功能，命令行命令或。蝙蝠和。 cmd批处理脚本可能无法存取，安装，变更，修改，删除或写信给“程序文件”或“的％ windir ％ \ system32 ”文件夹中。 The WOW64 subsystem redirects and installs 32-bit programs in the “Program Files (x86)” and “%systemroot%\SysWOW64″ folder. WOW64子系统重定向并安装32位元程式，在“程序文件（ x86 ）的”和“的％ SystemRoot ％ \ syswow64 ”文件夹中。
To access the correct folder, programmer or developer must change the command-line script, or using获得正确的资料夹，程序员或开发商必须改变的命令行脚本，或使用 Sysnative virtual directory alias to access %windir%\System32 sysnative虚拟目录别名访问的％ windir ％ \ system32 instead of %windir%\SysWOW64.不是的％ windir ％ \ syswow64 。 When this is not possible, or when have to access original native Program Files folder, user can type the command-line script at a 32-bit command prompt.时，这是不可能的，或者当有存取原本土Program Files文件夹，用户可以键入命令行脚本在一个32位命令提示符。 The 32-bit command prompt automatically redirects file system calls to the correct 32-bit directory. 32位命令提示符自动重定向文件系统调用到正确的32位目录。
To start and open a 32-bit command prompt, follow these steps:启动并打开一个32位命令提示符下，按照下列步骤进行：
- Click Start .单击开始 。
- Type %windir%\SysWoW64\cmd.exe in Start Search box.键入％ windir ％ \ syswow64 \ cmd.exe在开始的搜索框。
Alternatively, press Win + R keys (or type Run in Start Search) to open Run dialog, and type %windir%\SysWoW64\cmd.exe .另外，新闻双赢 + R键不放（或类型来说，在开始搜索）打开运行对话框，键入％ windir ％ \ syswow64 \ cmd.exe 。
- Press Enter .按下ENTER 。
In 32-bit command prompt, the %programfiles% path variable will point to Program Files (x86) folder which stores all 32-bit binaries.在32位命令提示符下，在％ programfiles ％ PATH变量将指向程序文件（ x86 ）的文件夹，其中存储所有的32位二进制文件。
IMPORTANT : You're reading a machine translated page which is provided "as is" without warranty. 重要说明：您正在阅读的机器翻译网页是“按原样”提供的担保。 Unlike human translation, machine translation does not understand the grammar, semantics, syntax, idioms of natural language, thus often produce inaccurate and low quality text which is misleading and incomprehensible.不像人类翻译，机器翻译不明白的语法，语义，语法，成语自然语言，因此，往往产生不准确的和低品质的文字，是具误导性的和难以理解的。 Thus, please refer to因此，请参阅 original English article英文原版的文章 when in doubt.有疑问时。
Related Articles相关文章
- How to Suppress and Bypass System32 File System Redirect to SysWOW64 Folder with Sysnative如何制止和绕道system32文件系统重定向到SysWow64文件夹与sysnative
- Error 1721: There Is A Problem With This Windows Installer Package When Install or Uninstall on Vista错误1721 ：有一个问题与此Windows Installer程序包时，安装或卸载Vista上
- How Open Command Prompt as Administrator on Elevation in Vista如何打开命令提示符，作为管理员，海拔在Vista
- Microsoft Releases MUI Language Packs for Windows Vista Ultimate SP1微软发布MUI语言包Windows Vista旗舰版SP1的
- Fix Setup Installer Package Access Denied Failure Error Code 0×80070005 (Or 5 Or 0×5)修复安装安装程序包的访问被拒绝失败的错误代码0 × 80070005 （或五或0 × 5 ）
- Microsoft Virtual PC (VPC) 2007 SP1 Free Download微软的Virtual PC （ vpc ） 2007 SP1的免费下载
- ImageX 6001.18000 (x86 and x64 for Windows Server 2008 and Vista SP1) Standalone Download imagex 6001.18000 （ x86和x64的Windows Server 2008和Vista SP1 ）的独立下载
- Workaround to Run VMWare Server on Windows Vista其他可行方案运行VMware服务器在Windows Vista
- Windows Vista Startup Hang and Boot Failure after SP1 on Corrupt Driver File (atapi.sys and ataport.sys) Windows Vista启动坑及启动失败的SP1之后对腐败的驱动程序文件（的Atapi.sys和ataport.sys ）
- Windows Cannot Hibernate Computer with More Than 4 GB Memory Windows无法休眠的电脑与4 GB以上的记忆
May 23rd, 2008 14:29 2008年5月23日14时29分
As you described in the article, the original %SystemRoot%\System32 is not accessible to 32-bit processes.正如您所描述的在文章中，原来的％ systemroot ％ \ System32中无法访问的32位进程。 Unfortunately, there are several tools existing uniquely as 64-bit binaries (eg logogg.exe and tsshutdn.exe).不幸的是，有几个工具，现有的独特的64位的二进制文件（例如logogg.exe和tsshutdn.exe ） 。 In one of my articles, I describe two techniques circumventing the limitation of launching 64-bit system tools from 32-bit processes:在一个我的文章，我描述两种方法规避限制发射的64位系统管理工具从32位的进程： http://blogs.sepago.de/nicholas/2008/03/13/jailed-32-bit-processes-on-windows-x64/
Enjoy,享受，
Nicholas.尼古拉斯。
August 21st, 2008 11:37 2008年8月21日11时37分
i tried using your advice to try and get some 32bit apps to run a bit better on my 64bit box.我曾尝试使用您的意见，以尝试并取得了一些32位应用程序运行有点更好的就我的64位框。 problem is, now i get weird errors from some key software.问题是，我现在得到奇怪的错误，从一些关键软件。 i don’t know how to undo the change… which may serve me right for swimming in deep waters…我不知道如何撤消的变化… …从而可我的权利，游泳，在深水域…
throw me a raft, ya?丢我一个筏，亚？
here’sa sample error that showed up mid-execution after i’d run the %windir%\SysWoW64\cmd.exe command:以下是抽样误差表明了中执行后，我要运行的％ windir ％ \ syswow64 \ cmd.exe命令：
Error: can’t define “ProgramFiles(x86)”: name refers to an element in an array错误：无法界定什么是“程序文件（ x86 ）或” ：名称是指一个要素在一个数组
while evaluating script: namespace eval :: {source {C:/Program Files (x86)/[directory tree]/RMSExpression.tcl}}而评估的脚本：名字空间eval ： ： （来源（ c ： /程式档案（ x86 ）或/ [目录树] / rmsexpression.tcl ） ）
August 21st, 2008 14:34 2008年8月21日14时34分
I may be dipping the raft but I reckon the TCL interpreter does not allow brackets in the path to a file which it is about to source.我可能是浸渍竹排上，但我估计，东涌口译不容许方括号中的路径文件，该文件是关于源。
Does it help to move the installation directory to a location outside of “c:\Program Files (x86)”, eg “c:\progs”?这是否有助于动议安装目录的某个位置以外的“ C ： \程式档案（ x86 ）的” ，例如“为C ： \ progs ” ？
Hope that helps,希望帮助，
Nicholas.尼古拉斯。
August 21st, 2008 17:42 2008年8月21日17时42分
i thought that might be a solution, but before i tried it, i tried just running it from a normal shell, instead of through the batchfile that launched the app in question, and it worked fine.我认为这可能是一个解决办法，但之前我曾尝试它，我只是试图运行它从一个正常的壳，而不是通过batchfile发起亚洲浆纸在的问题，和它的罚款。 so much weirdness.这么多怪物。
the batchfile no longer works, but direct command line does.该batchfile不再工程，但直接指挥线路。 how weird is that?!如何怪异的是吗！
i’ll also try a different path without brackets to see if that re-enables my batchfile’s ability to launch.我还会尝试一条不同的道路，没有括号内，看看是否能重新启用我batchfile的执政能力发射。 reaaaly need the batchfile to work again… reaaaly需要batchfile工作再次…
thank Nicholas.感谢尼古拉斯。 i’ll keep you posted.我将让你张贴。
WR!西铁！