How to Suppress and Bypass System32 File System Redirect to SysWOW64 Folder with Sysnative如何制止和繞道system32文件系統重定向到SysWow64文件夾與sysnative

In 64-bit (x64) Windows operating system, including Windows Vista, Microsoft implements a feature called File System Redirector on WOW64 (Windows-32-on-Windows-64 that runs 32-bit programs without modifications) subsystem layer for 32-bit programs or DLL (dynamic link libraries) which provides a WOW64 sandbox for registry calls and some file system calls.在64位（ x64 ）的Windows作業系統，包括Windows Vista中，微軟實現了一個功能叫做文件系統重定向器wow64 （在Windows - 32 -對-的Windows 64上運行32位程序沒有修改）子系統層為32位程序或DLL （動態鏈接庫）提供了一個wow64 Sandbox中，為登錄呼叫和一些檔案系統的來電。 The filesystem redirection forces 32-bit application attempts to be installed into or accessed from %windir%\System32, been intercepted and get redirected or re-pointed to %windir%\SysWOW64 instead.文件重定向勢力的32位元應用程式，企圖將其安裝入或訪問的％ windir ％ \ System32 ，則一直被截獲並獲得自由的或重新指出的％ windir ％ \ syswow64不是。

The reason for the Filesystem Redirector is that in x64 edition of Windows OS, %windir%\System32 directory is reserved for 64-bit applications.原因文件重定向是，在x64版的Windows操作系統， ％ Windir ％ \ System32目錄是預留作的64位元應用程式。 However, most DLL implements Windows API has the same file names and paths that were not changed when porting to 64-bit.然而，大多數的DLL執行的Windows API具有相同的文件名和路徑不改變，當移植到64位。 As there cannot be two 32-bit and 64-bit DLLs with same name and same path exist on the same system at the same time, so File System Redirector automatically isolates and makes 32-bit applications or non-64-bit aware programs use a different directory as their System32 directory, which is %windir%\SysWOW64 folder.由於不能有兩個32位和64位的DLL與相同名稱和相同的路徑存在於同一系統在同一時間內，所以文件系統重定向器自動分離，使32位應用程序或非64位知道程序使用在不同的目錄，作為他們的System32目錄，是％ windir ％ \ SysWow64文件夾中。 It’s also as a way to avoid incompatibility issue to prevent a 32-bit binary from accidentally accessing data from a 64-bit binary.這也是一種方式，以避免不兼容問題，以防止一個32位二進制從意外進入數據從一個64位二進制。

However, in some cases, such as when然而，在某些情況下，例如當 patching the 64-bit tcpip.sys修修補補的64位Tcpip.sys中 resides in %windir%\System32, the original System32 directory has to be accessed and used in order to avoid “File not found” or “The system cannot find the file specified” error.居住在的％ windir ％ \ System32 ，則原來的System32目錄中，要訪問和使用，以避免“未找到文件”或“系統無法找到指定的文件”的錯誤。 The similar symptoms is especially evident for command-line batch script which has to access 32-bit programs in the Program Files or %windir%\System32 folder, which both get redirected to Program Files (x86) and %windir%\SysWOW64 folder.類似的症狀，尤其是明顯的命令行腳本，其中一批已進入32位元程式在Program Files或的％ windir ％ \ System32文件夾中，這兩個重定向到程序文件（ x86 ）的和％ windir ％ \ Syswow64資料夾。

To workaround the problem, and forces a program or batch command script to get access to 32-bit programs in %windir%\System32 folder, bypassing the以可行的問題，和力量的程序或批處理命令腳本，以獲取32位元程式的％ windir ％ \ System32文件夾中，繞過 file system redirection文件系統重定向 , a special alias or pseudo-directory name been added on WOW64 subsystem starting with Windows Vista.一個特別的別名或偽目錄名稱，增加了對WOW64子系統開始，與Windows Vista 。

32-bit applications can access the native system directory by substituting %windir%\Sysnative for %windir%\System32. 32位元應用程式可以存取本土系統目錄代的％ windir ％ \ sysnative為的％ windir ％ \ system32 。 WOW64 recognizes Sysnative as a special alias used to indicate that the file system should not redirect the access. wow64承認sysnative作為一個特殊的別名使用表明，該文件系統不應該重定向訪問。 The Sysnative is just a virtual directory, alias or pseudo-directory that is not visible in Windows Explorer, directory listing, and does not support native 64-bit processes that already been accessing the %windir%\System32 folder.該sysnative只是一個虛擬目錄，別名或偽的目錄是不可見在Windows Explorer中，目錄列表，不支持64位的進程已經進入的％ windir ％ \ System32文件夾中。 As such, Sysnative can only be used in file system calls, and not in application’s user interface such as dialog box to open or select folder.這樣， sysnative只能用來在文件系統調用，而不是在應用程序的用戶界面，如對話框，打開或選擇文件夾。

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 Open and Run 32-bit Command Prompt in 64-bit (x64) Windows如何打開和運行32位命令提示符在64位（ x64 ）的Windows
• Fix Deleted SAM File Causing Windows Vista Unable to Boot Error修正刪除薩姆文件造成的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 ）
• Fix Logitech QuickCam (Messenger, Chat, Zoom, IM, Express) Not Compatible Driver Issue in Windows Vista SP1修復羅技快（即時通訊，聊天，變焦，即時通訊，快遞）不兼容的驅動程序問題在Windows Vista SP1的
• Windows Vista Fails to Boot After Installing SP1 with ntoskrnl.exe 0xc0000098 Error Windows Vista中未能啟動後，安裝SP1與0xc0000098錯誤的Ntoskrnl.exe
• Quick and Direct Access To Favourite Files or Folders With ‘Direct Folders’快速和直接進入最喜愛的檔案或資料夾與直接文件夾'
• Download Direct Folder v3.3 for Fast Folders and Files Access on Your PC直接下載文件夾v3.3快速的文件夾和文件訪問在您的PC上
• Windows XP SP3 BSoD Endless Reboot Loop with Stop c0000139 on GDI32.dll Error Windows XP的SP3的bsod無休止的重新啟動迴路停止c0000139對GDI32.DLL的錯誤
• Bypass or Disable UAC for Selected Excluded Programs Only with Elevator (SkipUAC)繞道或禁用的UAC為選定的排除程序，只有電梯（ skipuac ）
• 0X80070002 License Check Failure and Unable to Logon Error After Installing Windows XP SP3 0x80070002授權檢查失敗，無法登錄錯誤後，安裝Windows XP SP3的

This entry was posted on Wednesday, May 21st, 2008 at 5:46 pm and is filed under 此項目被張貼在週三， 2008年5月21日在下午5時46分，並提交下 Windows Vista Windows Vista的 . 。 You can follow any responses to this entry through the 您可以按照任何的反應，此項目通過 RSS 2.0 2.0 feed. 餵養。 You can 您可以 leave a response 留下的回應 , or ，或 trackback Trackback跟踪 from your own site. 從你自己的網站。