| 0x0 | 操作順利完成。 |
The operation completed successfully. |
| 0x1 | 功能錯誤。 |
Incorrect function. |
| 0x2 | 系統找不到指定的檔案。 |
The system cannot find the file specified. |
| 0x3 | 系統找不到指定的路徑。 |
The system cannot find the path specified. |
| 0x4 | 系統無法開啟檔案。 |
The system cannot open the file. |
| 0x5 | 存取被拒。 |
Access is denied. |
| 0x6 | 控制代碼無效。 |
The handle is invalid. |
| 0x7 | 存放控制區塊已損壞。 |
The storage control blocks were destroyed. |
| 0x8 | 存放體空間不足，無法處理此命令。 |
Not enough storage is available to process this command. |
| 0x9 | 存放控制區塊位址無效。 |
The storage control block address is invalid. |
| 0xA | 環境錯誤。 |
The environment is incorrect. |
| 0xB | 試圖載入格式錯誤的程式。 |
An attempt was made to load a program with an incorrect format. |
| 0xC | 存取碼不正確。 |
The access code is invalid. |
| 0xD | 資料不正確。 |
The data is invalid. |
| 0xE | 存放裝置空間不足，無法完成此操作。 |
Not enough storage is available to complete this operation. |
| 0xF | 系統找不到指定的磁碟機。 |
The system cannot find the drive specified. |
| 0x10 | 無法移除目錄。 |
The directory cannot be removed. |
| 0x11 | 系統無法將檔案移到不同的磁碟機。 |
The system cannot move the file to a different disk drive. |
| 0x12 | 沒有其他檔案。 |
There are no more files. |
| 0x13 | 媒體有防寫保護。 |
The media is write protected. |
| 0x14 | 系統找不到指定的裝置。 |
The system cannot find the device specified. |
| 0x15 | 裝置未就緒。 |
The device is not ready. |
| 0x16 | 裝置無法辨識命令。 |
The device does not recognize the command. |
| 0x17 | 資料錯誤 (循環冗餘檢查)。 |
Data error (cyclic redundancy check). |
| 0x18 | 程式發出命令，但命令長度錯誤。 |
The program issued a command but the command length is incorrect. |
| 0x19 | 磁碟機無法找出磁碟上特定區域或磁軌的位置。 |
The drive cannot locate a specific area or track on the disk. |
| 0x1A | 無法存取指定的磁碟或磁片。 |
The specified disk or diskette cannot be accessed. |
| 0x1B | 磁碟機找不到需要的磁區。 |
The drive cannot find the sector requested. |
| 0x1C | 印表機紙張用完。 |
The printer is out of paper. |
| 0x1D | 系統無法寫入指定的裝置。 |
The system cannot write to the specified device. |
| 0x1E | 系統無法從指定的裝置進行讀取。 |
The system cannot read from the specified device. |
| 0x1F | 連結到系統的某個裝置失去作用。 |
A device attached to the system is not functioning. |
| 0x20 | 程序無法存取檔案，因為檔案正由另一個程序使用。 |
The process cannot access the file because it is being used by another process. |
| 0x21 | 程序無法存取檔案，因為另一個程序已鎖定檔案的一部分。 |
The process cannot access the file because another process has locked a portion of the file. |
| 0x22 | 磁碟機中錯誤的磁片。插入 %2 (磁碟區序號: %3) 到磁碟機 %1。 |
The wrong diskette is in the drive.Insert %2 (Volume Serial Number: %3) into drive %1. |
| 0x24 | 開啟的共用檔案過多。 |
Too many files opened for sharing. |
| 0x26 | 到達檔案結尾。 |
Reached the end of the file. |
| 0x27 | 磁碟已滿。 |
The disk is full. |
| 0x32 | 不支援這個要求。 |
The request is not supported. |
| 0x33 | Windows 找不到網路路徑。請確認網路路徑正確，且目的電腦不是忙碌中或已關機。如果 Windows 仍舊找不到網路路徑，請連絡您的網路系統管理員。 |
Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator. |
| 0x34 | 您並未連線，因為網路上有重複的名稱。如果您要是加入網域，請至 [控制台] 中的 [系統] 變更電腦名稱，然後再試一次。如果您是要加入工作群組，請選擇其他工作群組名稱。 |
You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name. |
| 0x35 | 找不到網路路徑。 |
The network path was not found. |
| 0x36 | 網路忙碌中。 |
The network is busy. |
| 0x37 | 指定的網路資源或裝置無法再使用。 |
The specified network resource or device is no longer available. |
| 0x38 | 已達網路 BIOS 命令限制。 |
The network BIOS command limit has been reached. |
| 0x39 | 發生網路介面卡硬體錯誤。 |
A network adapter hardware error occurred. |
| 0x3A | 指定的伺服器無法執行要求的操作。 |
The specified server cannot perform the requested operation. |
| 0x3B | 發生意外的網路錯誤。 |
An unexpected network error occurred. |
| 0x3C | 遠端介面卡不相容。 |
The remote adapter is not compatible. |
| 0x3D | 印表機佇列已滿。 |
The printer queue is full. |
| 0x3E | 無法在伺服器上取得儲存等待列印檔案的空間。 |
Space to store the file waiting to be printed is not available on the server. |
| 0x3F | 等候列印的檔案已刪除。 |
Your file waiting to be printed was deleted. |
| 0x40 | 指定的網路名稱無法使用。 |
The specified network name is no longer available. |
| 0x41 | 網路存取被拒。 |
Network access is denied. |
| 0x42 | 網路資源類型錯誤。 |
The network resource type is not correct. |
| 0x43 | 找不到網路名稱。 |
The network name cannot be found. |
| 0x44 | 超過本機電腦網路介面卡的名稱限制。 |
The name limit for the local computer network adapter card was exceeded. |
| 0x45 | 超過網路 BIOS 工作階段限制。 |
The network BIOS session limit was exceeded. |
| 0x46 | 遠端伺服器已暫停，或正在啟動過程中。 |
The remote server has been paused or is in the process of being started. |
| 0x47 | 目前已無法再連線到這台遠端電腦，因為已達到電腦的連線數目極限。 |
No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. |
| 0x48 | 指定的印表機或磁碟裝置已暫停。 |
The specified printer or disk device has been paused. |
| 0x50 | 檔案存在。 |
The file exists. |
| 0x52 | 無法建立目錄或檔案。 |
The directory or file cannot be created. |
| 0x53 | 失敗發生在 INT 24。 |
Fail on INT 24. |
| 0x54 | 處理這個要求的存放裝置無法使用。 |
Storage to process this request is not available. |
| 0x55 | 本機裝置名稱已在使用中。 |
The local device name is already in use. |
| 0x56 | 指定的網路密碼錯誤。 |
The specified network password is not correct. |
| 0x57 | 參數錯誤。 |
The parameter is incorrect. |
| 0x58 | 網路上發生寫入錯誤。 |
A write fault occurred on the network. |
| 0x59 | 系統無法在這時候啟動另一個處理程序。 |
The system cannot start another process at this time. |
| 0x64 | 無法建立另一個系統信號。 |
Cannot create another system semaphore. |
| 0x65 | 這個獨佔的信號是由另一個處理程序擁有。 |
The exclusive semaphore is owned by another process. |
| 0x66 | 信號已設定而且無法關閉。 |
The semaphore is set and cannot be closed. |
| 0x67 | 無法再次設定信號。 |
The semaphore cannot be set again. |
| 0x68 | 無法在插斷時間中要求獨佔的信號。 |
Cannot request exclusive semaphores at interrupt time. |
| 0x69 | 這個信號的上一個擁有權已結束。 |
The previous ownership of this semaphore has ended. |
| 0x6A | 在磁碟機 %1 插入磁片。 |
Insert the diskette for drive %1. |
| 0x6B | 程式停止，因為未插入磁片。 |
The program stopped because an alternate diskette was not inserted. |
| 0x6C | 磁碟使用中，或被另一個處理程序鎖定。 |
The disk is in use or locked by another process. |
| 0x6D | 管道已結束。 |
The pipe has been ended. |
| 0x6E | 系統無法開啟指定的裝置或檔案。 |
The system cannot open the device or file specified. |
| 0x6F | 檔案名稱太長。 |
The file name is too long. |
| 0x70 | 磁碟的空間不足。 |
There is not enough space on the disk. |
| 0x71 | 無法再獲得內部檔案的識別元。 |
No more internal file identifiers available. |
| 0x72 | 目標內部檔案的識別元錯誤。 |
The target internal file identifier is incorrect. |
| 0x75 | 應用程式發出的 IOCTL 呼叫不正確。 |
The IOCTL call made by the application program is not correct. |
| 0x76 | verify-on-write 切換參數值不正確。 |
The verify-on-write switch parameter value is not correct. |
| 0x77 | 系統不支援請求的命令。 |
The system does not support the command requested. |
| 0x78 | 系統不支援這個功能。 |
This function is not supported on this system. |
| 0x79 | 信號等待逾時。 |
The semaphore timeout period has expired. |
| 0x7A | 傳遞到系統呼叫的資料區太小。 |
The data area passed to a system call is too small. |
| 0x7B | 檔案名稱、目錄名稱或磁碟區標籤語法錯誤。 |
The filename, directory name, or volume label syntax is incorrect. |
| 0x7C | 系統呼叫層級錯誤。 |
The system call level is not correct. |
| 0x7D | 磁碟沒有磁碟區標籤。 |
The disk has no volume label. |
| 0x7E | 找不到指定的模組。 |
The specified module could not be found. |
| 0x7F | 找不到指定的程序。 |
The specified procedure could not be found. |
| 0x80 | 沒有等候的子處理程序。 |
There are no child processes to wait for. |
| 0x81 | %1 應用程式無法在 Win32 模式中執行。 |
The %1 application cannot be run in Win32 mode. |
| 0x82 | 企圖使用已開啟的磁碟分割的檔案控制代碼來進行操作，而不用原始磁碟 I/O。 |
Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O. |
| 0x83 | 企圖在檔案開頭之前移動檔案指標。 |
An attempt was made to move the file pointer before the beginning of the file. |
| 0x84 | 無法在指定的裝置或檔案上設定檔案指標。 |
The file pointer cannot be set on the specified device or file. |
| 0x85 | 先前已加入其他磁碟的磁碟機無法再使用 JOIN 或 SUBST 命令。 |
A JOIN or SUBST command cannot be used for a drive that contains previously joined drives. |
| 0x86 | 企圖在已加入的磁碟機上使用 JOIN 或 SUBST 命令。 |
An attempt was made to use a JOIN or SUBST command on a drive that has already been joined. |
| 0x87 | 企圖在已被取代的磁碟機上使用 JOIN 或 SUBST 命令。 |
An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted. |
| 0x88 | 系統試圖刪除根本沒被加入的磁碟機 JOIN。 |
The system tried to delete the JOIN of a drive that is not joined. |
| 0x89 | 系統試圖刪除未被取代的磁碟機取代。 |
The system tried to delete the substitution of a drive that is not substituted. |
| 0x8A | 系統試圖將磁碟機加入到已被加入的磁碟機目錄。 |
The system tried to join a drive to a directory on a joined drive. |
| 0x8B | 系統試圖將磁碟機取代到已被取代過的磁碟目錄。 |
The system tried to substitute a drive to a directory on a substituted drive. |
| 0x8C | 系統試圖將磁碟機加入到被取代的磁碟目錄。 |
The system tried to join a drive to a directory on a substituted drive. |
| 0x8D | 系統試圖將磁碟機 SUBST 到已被加入的磁碟目錄。 |
The system tried to SUBST a drive to a directory on a joined drive. |
| 0x8E | 系統無法在此時執行 JOIN 或 SUBST。 |
The system cannot perform a JOIN or SUBST at this time. |
| 0x8F | 系統無法將磁碟機加入到或替代為相同磁碟機上的目錄。 |
The system cannot join or substitute a drive to or for a directory on the same drive. |
| 0x90 | 目錄並非根目錄下的子目錄。 |
The directory is not a subdirectory of the root directory. |
| 0x91 | 目錄不是空的。 |
The directory is not empty. |
| 0x92 | 指定的路徑已被取代指令所使用。 |
The path specified is being used in a substitute. |
| 0x93 | 資源不足無法處理此命令。 |
Not enough resources are available to process this command. |
| 0x94 | 指定的路徑無法在此時使用。 |
The path specified cannot be used at this time. |
| 0x95 | 企圖將磁碟機加入或取代磁碟機，磁碟上的目錄是前一個取代的目標。 |
An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute. |
| 0x96 | 系統追蹤資訊未在 CONFIG.SYS 檔案中指定，或不允許追蹤。 |
System trace information was not specified in your CONFIG.SYS file, or tracing is disallowed. |
| 0x97 | DosMuxSemWait 指定的信號事件個數錯誤。 |
The number of specified semaphore events for DosMuxSemWait is not correct. |
| 0x98 | DosMuxSemWait 不執行; 已設定過多的信號。 |
DosMuxSemWait did not execute; too many semaphores are already set. |
| 0x99 | DosMuxSemWait 清單錯誤。 |
The DosMuxSemWait list is not correct. |
| 0x9A | 輸入的磁碟區標籤超過目標檔案系統的標籤字元限制。 |
The volume label you entered exceeds the label character limit of the target file system. |
| 0x9B | 無法建立另一個執行緒。 |
Cannot create another thread. |
| 0x9C | 接收處理已拒絕信號。 |
The recipient process has refused the signal. |
| 0x9D | 已放棄區段且無法鎖定。 |
The segment is already discarded and cannot be locked. |
| 0x9E | 已解除鎖定區段。 |
The segment is already unlocked. |
| 0x9F | 執行緒識別碼的位址錯誤。 |
The address for the thread ID is not correct. |
| 0xA0 | 有一些引數不正確。 |
One or more arguments are not correct. |
| 0xA1 | 指定的路徑不正確。 |
The specified path is invalid. |
| 0xA2 | 信號已暫停。 |
A signal is already pending. |
| 0xA4 | 無法在系統中建立更多的執行緒。 |
No more threads can be created in the system. |
| 0xA7 | 無法鎖定檔案區域。 |
Unable to lock a region of a file. |
| 0xAA | 請求的資源正在使用中。 |
The requested resource is in use. |
| 0xAB | 裝置的命令支援偵測正在進行。 |
Device's command support detection is in progress. |
| 0xAD | 對於提供取消區域鎖定的請求不明顯。 |
A lock request was not outstanding for the supplied cancel region. |
| 0xAE | 檔案系統不支援鎖定類型的原子變更。 |
The file system does not support atomic changes to the lock type. |
| 0xB4 | 系統偵測出錯誤的區段個數。 |
The system detected a segment number that was not correct. |
| 0xB6 | 作業系統無法執行 %1。 |
The operating system cannot run %1. |
| 0xB7 | 當檔案已存在時，無法建立該檔案。 |
Cannot create a file when that file already exists. |
| 0xBA | 傳遞的旗標錯誤。 |
The flag passed is not correct. |
| 0xBB | 找不到指定的系統信號名稱。 |
The specified system semaphore name was not found. |
| 0xBF | 無法在 Win32 模式中執行 %1。 |
Cannot run %1 in Win32 mode. |
| 0xC1 | %1 不是有效的 Win32 應用程式。 |
%1 is not a valid Win32 application. |
| 0xC4 | 作業系統無法執行此應用程式。 |
The operating system cannot run this application program. |
| 0xC5 | 作業系統目前未設定成執行此應用程式。 |
The operating system is not presently configured to run this application. |
| 0xC8 | 程式碼區段不能大於或等於 64 K。 |
The code segment cannot be greater than or equal to 64K. |
| 0xCB | 作業系統找不到已輸入的環境選項。 |
The system could not find the environment option that was entered. |
| 0xCD | 在命令子目錄樹狀結構中無程序具有信號的處理常式。 |
No process in the command subtree has a signal handler. |
| 0xCE | 檔名或副檔名太長。 |
The filename or extension is too long. |
| 0xCF | 環形第 2 堆疊正在使用中。 |
The ring 2 stack is in use. |
| 0xD0 | 輸入錯誤的通用檔案名稱字元 * 或 ?，或指定過多的全域檔案名稱字元。 |
The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified. |
| 0xD1 | 正在登記的信號錯誤。 |
The signal being posted is not correct. |
| 0xD2 | 無法設定信號處理常式。 |
The signal handler cannot be set. |
| 0xD4 | 已鎖定區段且無法重新配置。 |
The segment is locked and cannot be reallocated. |
| 0xD6 | 這個程式或動態連結模組連結了太多動態連結模組。 |
Too many dynamic-link modules are attached to this program or dynamic-link module. |
| 0xD7 | 無法對 LoadModule 進行巢狀呼叫。 |
Cannot nest calls to LoadModule. |
| 0xD8 | 此版本的 %1 與您執行的 Windows 版本不相容。請檢查電腦的系統資訊，然後連絡軟體發行者。 |
This version of %1 is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher. |
| 0xD9 | 映像檔 %1 已簽章，無法修改。 |
The image file %1 is signed, unable to modify. |
| 0xDA | 映像檔 %1 已增強式簽章，無法修改。 |
The image file %1 is strong signed, unable to modify. |
| 0xDC | 此檔案已由其他使用者取出或封鎖編輯。 |
This file is checked out or locked for editing by another user. |
| 0xDD | 儲存變更前必須取出檔案。 |
The file must be checked out before saving changes. |
| 0xDE | 儲存或抓取的檔案類型已封鎖。 |
The file type being saved or retrieved has been blocked. |
| 0xDF | 檔案大小超過允許的限制，無法儲存。 |
The file size exceeds the limit allowed and cannot be saved. |
| 0xE0 | 拒絕存取。在此位置開啟檔案前，您必須先將網站加入您信任的網站清單、瀏覽到網站並選取自動登入的選項。 |
Access Denied. Before opening files in this location, you must first add the web site to your trusted sites list, browse to the web site, and select the option to login automatically. |
| 0xE1 | 因為檔案包含病毒或潛在的垃圾軟體，所以作業未順利完成。 |
Operation did not complete successfully because the file contains a virus or potentially unwanted software. |
| 0xE2 | 這個檔案包含病毒或潛在的垃圾軟體，因此無法開啟。有鑑於病毒或潛在的垃圾軟體的本質，檔案已從此位置中移除。 |
This file contains a virus or potentially unwanted software and cannot be opened. Due to the nature of this virus or potentially unwanted software, the file has been removed from this location. |
| 0xE5 | 管道為本機管道。 |
The pipe is local. |
| 0xE6 | 管道狀態不正確。 |
The pipe state is invalid. |
| 0xE7 | 所有的管道例項都在使用中。 |
All pipe instances are busy. |
| 0xE8 | 管道正關閉中。 |
The pipe is being closed. |
| 0xE9 | 管道的另一端上無任何處理程序。 |
No process is on the other end of the pipe. |
| 0xEA | 有更多資料可供使用。 |
More data is available. |
| 0xEB | 要求的動作造成未執行任何工作。已執行錯誤樣式清除。 |
The action requested resulted in no work being done. Error-style clean-up has been performed. |
| 0xF0 | 工作階段已被取消。 |
The session was canceled. |
| 0xFE | 指定的擴充屬性名稱不正確。 |
The specified extended attribute name was invalid. |
| 0xFF | 擴充屬性不一致。 |
The extended attributes are inconsistent. |
| 0x102 | 等候操作已逾時。 |
The wait operation timed out. |
| 0x103 | 不再有任何資料。 |
No more data is available. |
| 0x10A | 複製函數無法使用。 |
The copy functions cannot be used. |
| 0x10B | 目錄名稱無效。 |
The directory name is invalid. |
| 0x113 | 擴充屬性在緩衝區中不適用。 |
The extended attributes did not fit in the buffer. |
| 0x114 | 已架設在檔案系統上的擴充屬性檔案損毀。 |
The extended attribute file on the mounted file system is corrupt. |
| 0x115 | 擴充屬性表格檔案已滿。 |
The extended attribute table file is full. |
| 0x116 | 指定的擴充屬性代碼不正確。 |
The specified extended attribute handle is invalid. |
| 0x11A | 已掛接的檔案系統不支援擴充屬性。 |
The mounted file system does not support extended attributes. |
| 0x120 | 企圖釋出不屬於呼叫者的多使用者終端執行程式。 |
Attempt to release mutex not owned by caller. |
| 0x12A | 製作過多的 post 信號。 |
Too many posts were made to a semaphore. |
| 0x12B | 僅完成部分的 ReadProcessMemory 或 WriteProcessMemory 要求。 |
Only part of a ReadProcessMemory or WriteProcessMemory request was completed. |
| 0x12C | Oplock 要求被拒。 |
The oplock request is denied. |
| 0x12D | 系統收到無效的 oplock 認可。 |
An invalid oplock acknowledgment was received by the system. |
| 0x12E | 磁碟區太過分散，以致無法完成這個操作。 |
The volume is too fragmented to complete this operation. |
| 0x12F | 無法開啟檔案，因為該檔案正處於刪除程序中。 |
The file cannot be opened because it is in the process of being deleted. |
| 0x130 | 由於全域登錄設定，可能不會變更這個磁碟區上的簡短名稱設定。 |
Short name settings may not be changed on this volume due to the global registry setting. |
| 0x131 | 未在這個磁碟區上啟用簡短名稱。 |
Short names are not enabled on this volume. |
| 0x132 | 所指定磁碟區的安全性資料流處於不一致狀態。請在磁碟區上執行 CHKDSK。 |
The security stream for the given volume is in an inconsistent state.Please run CHKDSK on the volume. |
| 0x133 | 無法處理要求的檔案鎖定操作，因為位元組範圍無效。 |
A requested file lock operation cannot be processed due to an invalid byte range. |
| 0x134 | 支援映像類型所需的子系統不存在。 |
The subsystem needed to support the image type is not present. |
| 0x135 | 指定的檔案已經有相關的通知 GUID。 |
The specified file already has a notification GUID associated with it. |
| 0x136 | 偵測到無效的例外處理常式。 |
An invalid exception handler routine has been detected. |
| 0x137 | 指定給權杖的權限重複。 |
Duplicate privileges were specified for the token. |
| 0x138 | 無法處理所指定作業的範圍。 |
No ranges for the specified operation were able to be processed. |
| 0x139 | 不允許對檔案系統內部檔案執行作業。 |
Operation is not allowed on a file system internal file. |
| 0x13A | 此磁碟的實體資源已用完。 |
The physical resources of this disk have been exhausted. |
| 0x13B | 代表資料無效的語彙基元。 |
The token representing the data is invalid. |
| 0x13C | 裝置不支援命令功能。 |
The device does not support the command feature. |
| 0x13D | 系統在 %2 的訊息檔中找不到訊息編號 0x%1 的訊息文字。 |
The system cannot find message text for message number 0x%1 in the message file for %2. |
| 0x13E | 找不到指定的領域。 |
The scope specified was not found. |
| 0x13F | 目標電腦未定義指定的集中存取原則。 |
The Central Access Policy specified is not defined on the target machine. |
| 0x140 | 從 Active Directory 取得的集中存取原則無效。 |
The Central Access Policy obtained from Active Directory is invalid. |
| 0x141 | 裝置無法連線。 |
The device is unreachable. |
| 0x142 | 目標裝置沒有足夠資源可以完成作業。 |
The target device has insufficient resources to complete the operation. |
| 0x143 | 發生資料完整性總和檢查碼錯誤。檔案資料流中的資料損毀。 |
A data integrity checksum error occurred. Data in the file stream is corrupt. |
| 0x144 | 嘗試在相同作業中同時修改 KERNEL 與一般擴充屬性 (EA)。 |
An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation. |
| 0x146 | 裝置不支援檔案層級 TRIM。 |
Device does not support file-level TRIM. |
| 0x147 | 命令指定的資料位移未對齊裝置的資料粒度/對齊方式。 |
The command specified a data offset that does not align to the device's granularity/alignment. |
| 0x148 | 命令在其參數清單中指定了無效的欄位。 |
The command specified an invalid field in its parameter list. |
| 0x149 | 裝置目前正在進行作業。 |
An operation is currently in progress with the device. |
| 0x14A | 嘗試透過無效的目標裝置路徑向下傳送命令。 |
An attempt was made to send down the command via an invalid path to the target device. |
| 0x14B | 命令指定的描述元數目超過裝置支援的上限。 |
The command specified a number of descriptors that exceeded the maximum supported by the device. |
| 0x14C | 指定的檔案已停用清除 (Scrub)。 |
Scrub is disabled on the specified file. |
| 0x14D | 存放裝置未提供備援。 |
The storage device does not provide redundancy. |
| 0x14E | 駐留檔案不支援作業。 |
An operation is not supported on a resident file. |
| 0x14F | 壓縮檔案不支援作業。 |
An operation is not supported on a compressed file. |
| 0x150 | 目錄不支援作業。 |
An operation is not supported on a directory. |
| 0x151 | 無法讀取指定的要求資料複本。 |
The specified copy of the requested data could not be read. |
| 0x152 | 無法將指定的資料寫入到任一複本。 |
The specified data could not be written to any of the copies. |
| 0x153 | 此裝置上的一或多份資料複本未同步。完成資料完整性掃描之前，無法執行寫入。 |
One or more copies of data on this device may be out of sync. No writes may be performed until a data integrity scan is completed. |
| 0x154 | 提供的核心資訊版本無效。 |
The supplied kernel information version is invalid. |
| 0x155 | 提供的 PEP 資訊版本無效。 |
The supplied PEP information version is invalid. |
| 0x156 | 此物件未受任何外部提供者支援。 |
This object is not externally backed by any provider. |
| 0x157 | 無法識別該外部支援提供者。 |
The external backing provider is not recognized. |
| 0x158 | 壓縮此物件並不會節省空間。 |
Compressing this object would not save space. |
| 0x159 | 要求失敗，因為存放裝置拓撲識別碼不符。 |
The request failed due to a storage topology ID mismatch. |
| 0x15A | 操作已由家長監護封鎖。 |
The operation was blocked by parental controls. |
| 0x15B | 正在參考的檔案系統區塊已達到參考計數上限，因此無法再繼續參考。 |
A file system block being referenced has already reached the maximum reference count and can't be referenced any further. |
| 0x15C | 要求的作業失敗，因為檔案資料流已標示為不允許寫入。 |
The requested operation failed because the file stream is marked to disallow writes. |
| 0x15D | 要求的作業失敗，並顯示架構特定的失敗碼。 |
The requested operation failed with an architecture-specific failure code. |
| 0x15E | 因為需要重新啟動系統，因此未採取任何動作。 |
No action was taken as a system reboot is required. |
| 0x15F | 關機作業失敗。 |
The shutdown operation failed. |
| 0x160 | 重新啟動作業失敗。 |
The restart operation failed. |
| 0x161 | 已達到工作階段的數目上限。 |
The maximum number of sessions has been reached. |
| 0x162 | 「Windows 資訊保護」原則不允許存取此網路資源。 |
Windows Information Protection policy does not allow access to this network resource. |
| 0x163 | 裝置提示名稱緩衝區太小，無法接收剩餘的名稱。 |
The device hint name buffer is too small to receive the remaining name. |
| 0x164 | 「Windows 資訊保護」原則已經封鎖要求的作業。如需詳細資訊，請連絡您的系統管理員。 |
The requested operation was blocked by Windows Information Protection policy. For more information, contact your system administrator. |
| 0x165 | 無法執行要求的作業，因為裝置的硬體或軟體設定不符合 [鎖定] 原則下的 [Windows 資訊保護]。請檢查是否已建立使用者 PIN。如需詳細資訊，請連絡您的系統管理員。 |
The requested operation cannot be performed because hardware or software configuration of the device does not comply with Windows Information Protection under Lock policy. Please, verify that user PIN has been created. For more information, contact your system administrator. |
| 0x166 | 雲端檔案提供者是未知的。 |
The Cloud File provider is unknown. |
| 0x167 | 裝置處於維護模式。 |
The device is in maintenance mode. |
| 0x168 | DAX 磁碟區上不支援此作業。 |
This operation is not supported on a DAX volume. |
| 0x169 | 磁碟區具有作用中 DAX 對應。 |
The volume has active DAX mappings. |
| 0x16A | 雲端檔案提供者未執行。 |
The Cloud File provider is not running. |
| 0x16B | 雲端檔案中繼資料已損毀且無法讀取。 |
The Cloud File metadata is corrupt and unreadable. |
| 0x16C | 因為「雲端檔案」中繼資料太大，所以無法完成作業。 |
The operation could not be completed because the Cloud File metadata is too large. |
| 0x16D | 作業無法完成，因為雲端檔案屬性 Blob 太大。 |
The operation could not be completed because the Cloud File property blob is too large. |
| 0x16E | 雲端檔案屬性 Blob 可能已損毀。磁碟上的總和檢查碼與計算的總和檢查碼不符。 |
The Cloud File property blob is possibly corrupt. The on-disk checksum does not match the computed checksum. |
| 0x16F | 處理程序建立作業已被封鎖。 |
The process creation has been blocked. |
| 0x170 | 該存放裝置已遺失資料或持續性。 |
The storage device has lost data or persistence. |
| 0x171 | 支援檔案系統虛擬化的提供者暫時無法使用。 |
The provider that supports file system virtualization is temporarily unavailable. |
| 0x172 | 檔案系統虛擬化的中繼資料已損毀且無法讀取。 |
The metadata for file system virtualization is corrupt and unreadable. |
| 0x173 | 支援檔案系統虛擬化的提供者太忙，因此無法完成此作業。 |
The provider that supports file system virtualization is too busy to complete this operation. |
| 0x174 | 支援檔案系統虛擬化的提供者未知。 |
The provider that supports file system virtualization is unknown. |
| 0x175 | GDI 控制代碼可能已被應用程式洩漏。 |
GDI handles were potentially leaked by the application. |
| 0x176 | 因為會超過「雲端檔案」屬性 Blob 數目上限，所以無法完成作業。 |
The operation could not be completed because the maximum number of Cloud File property blobs would be exceeded. |
| 0x177 | 因為不支援「雲端檔案」中繼資料版本，所以無法完成作業。 |
The operation could not be completed because the Cloud File metadata version is not supported. |
| 0x178 | 因為檔案不是「雲端檔案」，所以無法完成作業。 |
The operation could not be completed because the file is not a Cloud File. |
| 0x179 | 因為「雲端檔案」不同步，所以無法完成作業。 |
The operation could not be completed because the Cloud File is not in sync. |
| 0x190 | 執行緒已在背景處理模式中。 |
The thread is already in background processing mode. |
| 0x191 | 執行緒未在背景處理模式中。 |
The thread is not in background processing mode. |
| 0x192 | 處理程序已在背景處理模式中。 |
The process is already in background processing mode. |
| 0x193 | 處理程序未在背景處理模式中。 |
The process is not in background processing mode. |
| 0x1C2 | 裝置上未啟用開發人員解鎖模式側載模式。 |
Neither developer unlocked mode nor side loading mode is enabled on the device. |
| 0x1C3 | 無法在升級或重新佈建期間變更應用程式類型。 |
Can not change application type during upgrade or re-provision. |
| 0x1C4 | 應用程式未佈建。 |
The application has not been provisioned. |
| 0x1C5 | 無法針對此應用程式授與要求的功能。 |
The requested capability can not be authorized for this application. |
| 0x1C6 | 裝置上沒有功能授權原則。 |
There is no capability authorization policy on the device. |
| 0x1C7 | 功能授權資料庫已損毀。 |
The capability authorization database has been corrupted. |
| 0x1E0 | 等候此裝置完成 PnP 查詢移除要求的作業逾時，因為其裝置堆疊中可能發生無回應的情況。系統可能需要重新開機，才能完成該要求。 |
The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in its device stack. The system may need to be rebooted to complete the request. |
| 0x1E1 | 等候此裝置完成 PnP 查詢移除要求的作業逾時，因為相關裝置的堆疊中可能發生無回應的情況。系統可能需要重新開機，才能完成該作業。 |
The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of a related device. The system may need to be rebooted to complete the operation. |
| 0x1E2 | 等候此裝置完成 PnP 查詢移除要求的作業逾時，因為不相關裝置的堆疊中可能發生無回應的情況。系統可能需要重新開機，才能完成該作業。 |
The operation timed out waiting for this device to complete a PnP query-remove request due to a potential hang in the device stack of an unrelated device. The system may need to be rebooted to complete the operation. |
| 0x1E3 | 要求失敗，因為發生嚴重的裝置硬體錯誤。 |
The request failed due to a fatal device hardware error. |
| 0x1E7 | 企圖存取不正確的位址。 |
Attempt to access invalid address. |
| 0x1F4 | 無法載入使用者設定檔。 |
User profile cannot be loaded. |
| 0x216 | 計算結果超過 32 位元。 |
Arithmetic result exceeded 32 bits. |
| 0x217 | 管道的另一端有處理程序進行。 |
There is a process on other end of the pipe. |
| 0x218 | 等候開啟管道另一端的處理程序。 |
Waiting for a process to open the other end of the pipe. |
| 0x219 | 應用程式驗證器已在目前的處理程序中找到錯誤。 |
Application verifier has found an error in the current process. |
| 0x21A | ABIOS 子系統中發生錯誤。 |
An error occurred in the ABIOS subsystem. |
| 0x21B | WX86 子系統中發生警告。 |
A warning occurred in the WX86 subsystem. |
| 0x21C | WX86 子系統中發生錯誤。 |
An error occurred in the WX86 subsystem. |
| 0x21D | 試圖取消或設定具關聯 APC 的計時器及主體執行緒中非原始以關聯 APC 例行程序設定計時器的執行緒。 |
An attempt was made to cancel or set a timer that has an associated APC and the subject thread is not the thread that originally set the timer with an associated APC routine. |
| 0x21E | 解除例外狀況代碼。 |
Unwind exception code. |
| 0x21F | 在解除操作時遇到無效或不正確配置的堆疊。 |
An invalid or unaligned stack was encountered during an unwind operation. |
| 0x220 | 在解除操作時遇到不正確的解除目標。 |
An invalid unwind target was encountered during an unwind operation. |
| 0x221 | 指定給 NtCreatePort 不正確的物件屬性或指定給 NtConnectPort 不正確的連接埠屬性。 |
Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort |
| 0x222 | 傳送給 NtRequestPort 或 NtRequestWaitReplyPort 的訊息長度大於連接埠允許的最大長度。 |
Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port. |
| 0x223 | 試圖將配額限制降到低於目前的使用率。 |
An attempt was made to lower a quota limit below the current usage. |
| 0x224 | 試圖連結一個已連結至其他裝置的裝置。 |
An attempt was made to attach to a device that was already attached to another device. |
| 0x225 | 試圖在未配置的位址上執行指令，且主機系統不支援未配置的指令參考。 |
An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references. |
| 0x226 | 未啟動分析。 |
Profiling not started. |
| 0x227 | 未停止分析。 |
Profiling not stopped. |
| 0x228 | 傳遞出的 ACL 並未包含所需的最少資訊。 |
The passed ACL did not contain the minimum required information. |
| 0x229 | 使用中分析物件的數量已到達最大值且無法啟動任一物件。 |
The number of active profiling objects is at the maximum and no more may be started. |
| 0x22A | 用來表示 I/O 沒有區塊化時，就無法繼續操作。 |
Used to indicate that an operation cannot continue without blocking for I/O. |
| 0x22B | 表示有一執行緒試圖依預設值終止其本身 (以 NULL 呼叫 NtTerminateThread) 且為目前程序中的最後一個執行緒。 |
Indicates that a thread attempted to terminate itself by default (called NtTerminateThread with NULL) and it was the last thread in the current process. |
| 0x22C | 如果傳回的 MM 錯誤不是定義在標準 FsRtl 篩選器，它會被轉換到一個下列保證在篩選器中的錯誤值。在這個狀況下，資訊會遺失，但篩選器可以正確處理意外狀況。 |
If an MM error is returned which is not defined in the standard FsRtl filter, it is converted to one of the following errors which is guaranteed to be in the filter.In this case information is lost, however, the filter correctly handles the exception. |
| 0x22F | 在釋放操作時遇到形式錯誤的功能表格。 |
A malformed function table was encountered during an unwind operation. |
| 0x230 | 嘗試將保護設定指派給檔案系統的檔案或目錄，有一個可能由檔案系統所儲存的 SID 安全性描述元無法被轉譯成 GUID。這會造成保護嘗試失敗，可能導致檔案建立的嘗試失敗。 |
Indicates that an attempt was made to assign protection to a file system file or directory and one of the SIDs in the security descriptor could not be translated into a GUID that could be stored by the file system.This causes the protection attempt to fail, which may cause a file creation attempt to fail. |
| 0x231 | 表示嘗試藉由設定 LDT 的值將它變大，或所設定的大小與選擇器號碼不相等。 |
Indicates that an attempt was made to grow an LDT by setting its size, or that the size was not an even number of selectors. |
| 0x233 | 這表示 LDT 資訊的啟動值不是選擇器大小的整數倍數。 |
Indicates that the starting value for the LDT information was not an integral multiple of the selector size. |
| 0x234 | 這表示使用者在試著設定 LDT 描述元時，提供不正確的描述元。 |
Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors. |
| 0x235 | 表示想執行要求動作的程序中執行緒太多。例如，您只能在程序沒有執行緒或只有一個執行緒時指定主要權杖。 |
Indicates a process has too many threads to perform the requested action. For example, assignment of a primary token may only be performed when a process has zero or one threads. |
| 0x236 | 試圖在特定的程序中執行緒，但所指定的執行緒不在指定的程序中。 |
An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified. |
| 0x237 | 超過分頁檔配額。 |
Page file quota was exceeded. |
| 0x238 | 因在網域中執行的其他 Netlogon 服務與指定的角色衝突而無法啟動 Netlogon 服務。 |
The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role. |
| 0x239 | Windows Server 上的 SAM 資料庫無法與網域控制站上的備份同步。兩者必須完全同步。 |
The SAM database on a Windows Server is significantly out of synchronization with the copy on the Domain Controller. A complete synchronization is required. |
| 0x23A | NtCreateFile API 失敗。此錯誤不應傳回應用程式，它是 Windows LAN 管理員重新導向器在內部錯誤對應常式中所使用的預留位置。 |
The NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows Lan Manager Redirector to use in its internal error mapping routines. |
| 0x23B | {特殊權限失敗}無法更改程序的 I/O 使用權限。 |
{Privilege Failed}The I/O permissions for the process could not be changed. |
| 0x23C | {使用 CTRL+C 結束應用程式}使用 CTRL+C 終止應用程式。 |
{Application Exit by CTRL+C}The application terminated as a result of a CTRL+C. |
| 0x23D | {系統檔案遺失}必要的系統檔案 %hs 損毀或遺失。 |
{Missing System File}The required system file %hs is bad or missing. |
| 0x23E | {應用程式錯誤}應用程式發生例外 %s (0x%08lx) 於位置 0x%08lx。 |
{Application Error}The exception %s (0x%08lx) occurred in the application at location 0x%08lx. |
| 0x23F | {應用程式錯誤}應用程式無法正確啟動 (0x%lx)。請按一下 [確定] 關閉應用程式。 |
{Application Error}The application was unable to start correctly (0x%lx). Click OK to close the application. |
| 0x240 | {無法建立分頁檔}建立分頁檔 %hs 失敗 (%lx)。而要求的檔案大小為 %ld。 |
{Unable to Create Paging File}The creation of the paging file %hs failed (%lx). The requested size was %ld. |
| 0x241 | Windows 無法驗證此檔案的數位簽章。最近的硬體或軟體變更所安裝的檔案，可能未正確簽署或已損毀，或可能來自不明來源的惡意軟體。 |
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. |
| 0x242 | {未指定分頁檔}未在系統設定中指定分頁檔。 |
{No Paging File Specified}No paging file was specified in the system configuration. |
| 0x243 | {例外}真實模式的應用程式發出浮點運算指令，而浮點運算硬體不存在。 |
{EXCEPTION}A real-mode application issued a floating-point instruction and floating-point hardware is not present. |
| 0x244 | 這個事件配對同步處理操作必須使用指定執行緒的用戶端/伺服器事件配對物件來執行，但沒有事件配對物件與該執行緒關聯。 |
An event pair synchronization operation was performed using the thread specific client/server event pair object, but no event pair object was associated with the thread. |
| 0x245 | Windows Server 的組態不正確。 |
A Windows Server has an incorrect configuration. |
| 0x246 | 遭遇不正確的字元。多位元組字元集必須包含一前導位元組且無結尾位元組。Unicode 字元集則包含字元 0xFFFF 及 0xFFFE。 |
An illegal character was encountered. For a multi-byte character set this includes a lead byte without a succeeding trail byte. For the Unicode character set this includes the characters 0xFFFF and 0xFFFE. |
| 0x247 | 本 Unicode 字元未定義在系統安裝的 Unicode 字元集。 |
The Unicode character is not defined in the Unicode character set installed on the system. |
| 0x248 | 無法在磁片中建立分頁檔。 |
The paging file cannot be created on a floppy diskette. |
| 0x249 | 系統 BIOS 無法將系統插斷連接到裝置，或裝置連接的匯流排。 |
The system BIOS failed to connect a system interrupt to the device or bus for which the device is connected. |
| 0x24A | 這項操作只能在網域的網域主控站上執行。 |
This operation is only allowed for the Primary Domain Controller of the domain. |
| 0x24B | 嘗試取得一超過最大計數值的 semaphor。 |
An attempt was made to acquire a mutant such that its maximum count would have been exceeded. |
| 0x24C | 因為一個必要但尚未載入的檔案系統驅動程式，所以存取磁碟區。 |
A volume has been accessed for which a file system driver is required that has not yet been loaded. |
| 0x24D | {登錄檔案失敗}登錄無法載入 hive 檔案:%hs或它的記錄檔或替代資料。檔案可能已經損毀、不存在或是無法寫入。 |
{Registry File Failure}The registry cannot load the hive (file):%hsor its log or alternate.It is corrupt, absent, or not writable. |
| 0x24E | {意外錯誤 DebugActiveProcess}當處理 DebugActiveProcess API 要求時，發生意外的錯誤。您可以選擇 [確定] 將處理程序終止，或選擇 [取消] 以略過這個錯誤。 |
{Unexpected Failure in DebugActiveProcess}An unexpected failure occurred while processing a DebugActiveProcess API request. You may choose OK to terminate the process, or Cancel to ignore the error. |
| 0x24F | {致命的系統錯誤}%hs 系統處理程序意外地終止，它的狀態為 0x%08x (0x%08x 0x%08x)。系統已被關機。 |
{Fatal System Error}The %hs system process terminated unexpectedly with a status of 0x%08x (0x%08x 0x%08x).The system has been shut down. |
| 0x250 | {無法接受資料}TDI 用戶端無法在指示的時間內處理接收的資料。 |
{Data Not Accepted}The TDI client could not handle the data received during an indication. |
| 0x251 | NTVDM 遭遇硬體錯誤。 |
NTVDM encountered a hard error. |
| 0x252 | {取消逾時值}驅動程式 %hs 無法在指定的時間內完成一已取消的 I/O 請求。 |
{Cancel Timeout}The driver %hs failed to complete a cancelled I/O request in the allotted time. |
| 0x253 | {回應訊息不符}嘗試回應一 LPC 訊息，但由訊息中用戶端識別碼所指定的執行緒並未等待該訊息。 |
{Reply Message Mismatch}An attempt was made to reply to an LPC message, but the thread specified by the client ID in the message was not waiting on that message. |
| 0x254 | {延遲寫入失敗}Windows 無法儲存檔案 %hs 的所有資料。資料已遺失。這個錯誤可能是因為您的電腦硬體或網路連線失敗所造成。請嘗試在其他位置儲存這個檔案。 |
{Delayed Write Failed}Windows was unable to save all the data for the file %hs. The data has been lost.This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere. |
| 0x255 | 傳送給在用戶端/伺服器共用記憶體視窗中的伺服器參數不正確。共用記憶體視窗中可能放入過多的資料。 |
The parameter(s) passed to the server in the client/server shared memory window were invalid. Too much data may have been put in the shared memory window. |
| 0x256 | 這個資料流不是一個微小的資料流。 |
The stream is not a tiny stream. |
| 0x257 | 本要求必須由堆疊溢位代碼處理。 |
The request must be handled by the stack overflow code. |
| 0x258 | 內部 OFS 狀態碼顯示了配置操作的執行方式。它在所包含的 onode 被移動或將擴充資料流轉換為大型的資料流後，重試一次。 |
Internal OFS status codes indicating how an allocation operation is handled. Either it is retried after the containing onode is moved or the extent stream is converted to a large stream. |
| 0x259 | 嘗試尋找物件時，在磁碟區上找到符合識別碼的物件，但是它已經超出操作所使用的控制代碼領域。 |
The attempt to find the object found an object matching by ID on the volume but it is out of the scope of the handle used for the operation. |
| 0x25A | bucket 陣列必須增加。請在執行此工作後重新嘗試交易。 |
The bucket array must be grown. Retry transaction after doing so. |
| 0x25B | 使用者/核心排列緩衝區已經溢位。 |
The user/kernel marshalling buffer has overflowed. |
| 0x25C | 提供的不同架構包含不正確的資料。 |
The supplied variant structure contains invalid data. |
| 0x25D | 指定的緩衝區中包含錯誤類型的資料。 |
The specified buffer contains ill-formed data. |
| 0x25E | {稽核失敗}嘗試產生安全性稽核時發生失敗。 |
{Audit Failed}An attempt to generate a security audit failed. |
| 0x25F | 目前的程序未設定計時器解析度。 |
The timer resolution was not previously set by the current process. |
| 0x260 | 帳戶資訊不足，無法讓您登入。 |
There is insufficient account information to log you on. |
| 0x261 | {不正確的 DLL 輸入點}動態連結程式庫 %hs 寫入錯誤。堆疊指標已經處於不一致的狀態。輸入點應該宣告成 WINAPI 或 STDCALL。請選取 [是] 以取消 DLL 載入，或選取 [否] 繼續執行。您若選取 [否] 可能導致應用程式執行不正確。 |
{Invalid DLL Entrypoint}The dynamic link library %hs is not written correctly. The stack pointer has been left in an inconsistent state.The entrypoint should be declared as WINAPI or STDCALL. Select YES to fail the DLL load. Select NO to continue execution. Selecting NO may cause the application to operate incorrectly. |
| 0x262 | {不正確的服務回撥輸入點}%hs 服務寫入發生錯誤。堆疊指標已經處在不一致的狀態。回撥輸入點應該宣告為 WINAPI 或 STDCALL。選取 [確定] 將導致服務繼續操作。服務處理程序可能會執行錯誤。 |
{Invalid Service Callback Entrypoint}The %hs service is not written correctly. The stack pointer has been left in an inconsistent state.The callback entrypoint should be declared as WINAPI or STDCALL. Selecting OK will cause the service to continue operation. However, the service process may operate incorrectly. |
| 0x263 | 有一個 IP 位址與網路上的另一個系統衝突。 |
There is an IP address conflict with another system on the network |
| 0x265 | {登錄檔空間不足}登錄檔內准許系統部分使用的空間已經達到最大值，將會略過其他的存放要求。 |
{Low On Registry Space}The system has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored. |
| 0x266 | 沒有使用中的回撥功能時，回撥系統服務就無法執行。 |
A callback return system service cannot be executed when no callback is active. |
| 0x267 | 提供的密碼太短，不符合使用者帳戶的原則要求。請輸入較長的密碼。 |
The password provided is too short to meet the policy of your user account.Please choose a longer password. |
| 0x268 | 您的使用者帳戶原則不允許太頻繁的密碼變更。這個是為了防止使用者所變更的密碼與上一個太相似，有被破解的潛在危險。如果您覺得您的密碼已經被盜用，請連絡您的系統管理員立即指定一個新密碼給你。 |
The policy of your user account does not allow you to change passwords too frequently.This is done to prevent users from changing back to a familiar, but potentially discovered, password.If you feel your password has been compromised then please contact your administrator immediately to have a new one assigned. |
| 0x269 | 變更的密碼過去曾經用過。您的使用者帳戶原則不允許您這樣做，請選還沒有用過的密碼。 |
You have attempted to change your password to one that you have used in the past.The policy of your user account does not allow this. Please select a password that you have not previously used. |
| 0x26A | 不支援指定的壓縮格式。 |
The specified compression format is unsupported. |
| 0x26B | 指定的硬體設定檔組態不正確。 |
The specified hardware profile configuration is invalid. |
| 0x26C | 指定的隨插即用登錄裝置路徑不正確。 |
The specified Plug and Play registry device path is invalid. |
| 0x26D | 指定的配額清單內部與其描述元不一致。 |
The specified quota list is internally inconsistent with its descriptor. |
| 0x26E | {Windows 評估通知}這個 Windows 安裝的評估期已經到期。這個系統將於 1 小時內關機。如果您要還原這個 Windows 安裝的存取，請使用合法授權的發佈產品來進行升級安裝。 |
{Windows Evaluation Notification}The evaluation period for this installation of Windows has expired. This system will shutdown in 1 hour. To restore access to this installation of Windows, please upgrade this installation using a licensed distribution of this product. |
| 0x26F | {系統 DLL 重新定位不正確}系統 DLL %hs 已在記憶體中重新定位。應用程式將不會正確執行。進行重新定位的原因是 DLL %hs 佔據的位址範圍是保留給 Windows 系統 DLL。請連絡廠商，提供新的 DLL。 |
{Illegal System DLL Relocation}The system DLL %hs was relocated in memory. The application will not run properly.The relocation occurred because the DLL %hs occupied an address range reserved for Windows system DLLs. The vendor supplying the DLL should be contacted for a new DLL. |
| 0x270 | {DLL 初始化失敗}應用程式無法初始，因為視窗工作站正在關機。 |
{DLL Initialization Failed}The application failed to initialize because the window station is shutting down. |
| 0x271 | 確認處理程序需要繼續下一步。 |
The validation process needs to continue on to the next step. |
| 0x272 | 找不到目前索引列舉的項目。 |
There are no more matches for the current index enumeration. |
| 0x273 | 範圍無法加入範圍清單，因為發生衝突。 |
The range could not be added to the range list because of a conflict. |
| 0x274 | 正在 SID 之下執行伺服器處理程序，這不是用戶端要求的 SID。 |
The server process is running under a SID different than that required by client. |
| 0x275 | 無法啟用標記為 [只可用來拒絕] 的群組。 |
A group marked use for deny only cannot be enabled. |
| 0x276 | {EXCEPTION}多重浮點指標錯誤。 |
{EXCEPTION}Multiple floating point faults. |
| 0x277 | {EXCEPTION}多重浮點指標陷阱。 |
{EXCEPTION}Multiple floating point traps. |
| 0x278 | 不支援要求的介面。 |
The requested interface is not supported. |
| 0x279 | {系統待命失敗} 驅動程式 %hs 無法支援待命模式。更新此驅動程式或許可以讓系統轉換成待命模式。 |
{System Standby Failed}The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode. |
| 0x27A | 系統檔案 %1 損毀，並且已經被取代。 |
The system file %1 has become corrupt and has been replaced. |
| 0x27B | {虛擬記憶體最小值太低}您的系統執行的虛擬記憶體太低。Windows 將自動為您增加虛擬記憶體分頁檔。過程中某些應用程式的記憶體要求可能會被拒絕。需要其他資訊，請參考 [說明]。 |
{Virtual Memory Minimum Too Low}Your system is low on virtual memory. Windows is increasing the size of your virtual memory paging file.During this process, memory requests for some applications may be denied. For more information, see Help. |
| 0x27C | 裝置已經移除，列舉必須重新開始。 |
A device was removed so enumeration must be restarted. |
| 0x27D | {嚴重的系統錯誤}系統映像 %s 未正確簽署。檔案已經被簽署檔案所取代。系統已關機。 |
{Fatal System Error}The system image %s is not properly signed.The file has been replaced with the signed file.The system has been shut down. |
| 0x27E | 沒有重新開機的話，裝置將不會啟動。 |
Device will not start without a reboot. |
| 0x27F | 電源不足，無法完成要求的操作。 |
There is not enough power to complete the requested operation. |
| 0x280 | ERROR_MULTIPLE_FAULT_VIOLATION |
ERROR_MULTIPLE_FAULT_VIOLATION |
| 0x281 | 系統正處於關機程序中。 |
The system is in the process of shutting down. |
| 0x282 | 嘗試移除 DebugPort 處理程序，但是該處理程序尚未與連接埠關聯。 |
An attempt to remove a processes DebugPort was made, but a port was not already associated with the process. |
| 0x283 | 這個版本的 Windows 與目錄樹系、網域或網域控制站的行為版本不相容。 |
This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller. |
| 0x284 | 在範圍清單中找不到指定的範圍。 |
The specified range could not be found in the range list. |
| 0x286 | 驅動程式沒有載入，原因是系統以安全模式開機。 |
The driver was not loaded because the system is booting into safe mode. |
| 0x287 | 驅動程式沒有載入，原因是初始化呼叫失敗。 |
The driver was not loaded because it failed its initialization call. |
| 0x288 | \"%hs\" 在套用電源或讀取裝置設定時遭遇錯誤。這可能是由於硬體失敗、或接觸不良所致。 |
The \"%hs\" encountered an error while applying power or reading the device configuration.This may be caused by a failure of your hardware or by a poor connection. |
| 0x289 | 建立的操作失敗，原因是名稱中含有至少一個掛接點，該掛接點解析成磁碟區，而所指定的裝置物件沒有連結到這個磁碟區。 |
The create operation failed because the name contained at least one mount point which resolves to a volume to which the specified device object is not attached. |
| 0x28A | 裝置物件參數不是正確的裝置物件、或者沒有連結到檔案名稱所指定的磁碟區。 |
The device object parameter is either not a valid device object or is not attached to the volume specified by the file name. |
| 0x28B | 發生電腦檢查錯誤，其他資訊請檢查系統事件記錄檔。 |
A Machine Check Error has occurred. Please check the system eventlog for additional information. |
| 0x28C | 處理驅動程式資料庫時發生錯誤 [%2]。 |
There was error [%2] processing the driver database. |
| 0x28D | 系統儲存檔大小已超出它的限制。 |
System hive size has exceeded its limit. |
| 0x28E | 無法載入驅動程式，因為前版的驅動程式仍在記憶體中。 |
The driver could not be loaded because a previous version of the driver is still in memory. |
| 0x28F | {磁碟區陰影複製服務}請稍候，磁碟區陰影複製服務正在準備磁碟區 %hs 休眠。 |
{Volume Shadow Copy Service}Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation. |
| 0x290 | 系統休眠失敗 (錯誤碼為 %hs)。在系統重新啟動前，休眠將被停用。 |
The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted. |
| 0x291 | 提供的密碼太長，不符合您的使用者帳戶原則。請選擇較短的密碼。 |
The password provided is too long to meet the policy of your user account.Please choose a shorter password. |
| 0x299 | 因為檔案系統限制，所以無法完成要求的作業。 |
The requested operation could not be completed due to a file system limitation |
| 0x29C | 發生宣告失敗。 |
An assertion failure has occurred. |
| 0x29D | ACPI 子系統中發生錯誤。 |
An error occurred in the ACPI subsystem. |
| 0x29E | WOW 宣告錯誤。 |
WOW Assertion Error. |
| 0x29F | 系統 BIOS MPS 表格中的某項裝置遺失。這個裝置將不被使用。請連絡您的系統廠商以取得系統 BIOS 更新。 |
A device is missing in the system BIOS MPS table. This device will not be used.Please contact your system vendor for system BIOS update. |
| 0x2A0 | 某個轉譯器無法轉譯資源。 |
A translator failed to translate resources. |
| 0x2A1 | 某個 IRQ 轉譯器無法轉譯資源。 |
A IRQ translator failed to translate resources. |
| 0x2A2 | 驅動程式 %2 為子裝置 (%3) 傳回無效的識別碼。 |
Driver %2 returned invalid ID for a child device (%3). |
| 0x2A3 | {核心偵錯工具觸發}由插斷觸發的系統偵錯工具。 |
{Kernel Debugger Awakened}the system debugger was awakened by an interrupt. |
| 0x2A4 | {控制代碼已關閉}依操作要求而自動關閉的物件控制代碼。 |
{Handles Closed}Handles to objects have been automatically closed as a result of the requested operation. |
| 0x2A5 | {過多的資訊}指定的存取控制清單 (ACL) 中包含過多的資訊。 |
{Too Much Information}The specified access control list (ACL) contained more information than was expected. |
| 0x2A6 | 這個警告等級狀態指出交易狀態已經存在於登錄子目錄，但交易確認動作已中止。確認動作並未完成，也未還原到上一步的操作。(它可能還處在確認狀態)。 |
This warning level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted.The commit has NOT been completed, but has not been rolled back either (so it may still be committed if desired). |
| 0x2A7 | {媒體變更}媒體可能已變更。 |
{Media Changed}The media may have changed. |
| 0x2A8 | {GUID 取代}通用識別元 (GUID) 轉譯成 Windows 安全性識別碼 (SID) 的過程中，找不到系統管理員定義的 GUID 首碼。使用的取代首碼不會危及系統安全性。不過，這可能會提供比原先預期更嚴格的存取限制。 |
{GUID Substitution}During the translation of a global identifier (GUID) to a Windows security ID (SID), no administratively-defined GUID prefix was found.A substitute prefix was used, which will not compromise system security. However, this may provide a more restrictive access than intended. |
| 0x2A9 | 到達符號連結後，建立作業已停止。 |
The create operation stopped after reaching a symbolic link |
| 0x2AA | 已經執行一個長跳躍。 |
A long jump has been executed. |
| 0x2AB | 隨插即用查詢操作沒有成功。 |
The Plug and Play query operation was not successful. |
| 0x2AC | 框架合併已執行。 |
A frame consolidation has been executed. |
| 0x2AD | {登錄 Hive 已修復}登錄 hive (檔案):%hs原已毀損，現已修復。某些資料可能已遺失。 |
{Registry Hive Recovered}Registry hive (file):%hswas corrupted and it has been recovered. Some data might have been lost. |
| 0x2AE | 應用程式嘗試執行來自模組 %hs 的可執行程式碼，這可能不安全，另外的選擇是可以使用 %hs。應用程式是否使用安全模組 %hs? |
The application is attempting to run executable code from the module %hs. This may be insecure. An alternative, %hs, is available. Should the application use the secure module %hs? |
| 0x2AF | 應用程式正在從模組 %hs 下載可執行程式碼，這雖安全，但可能和前版作業系統不相容，另外的選擇是可以使用 %hs。應用程式是否使用安全模組 %hs? |
The application is loading executable code from the module %hs. This is secure, but may be incompatible with previous releases of the operating system. An alternative, %hs, is available. Should the application use the secure module %hs? |
| 0x2B0 | 偵錯工具並未處理例外狀況。 |
Debugger did not handle the exception. |
| 0x2B1 | 偵錯工具稍後將回覆。 |
Debugger will reply later. |
| 0x2B2 | 偵錯工具無法提供控制代碼。 |
Debugger cannot provide handle. |
| 0x2B3 | 偵錯工具已經終止執行緒。 |
Debugger terminated thread. |
| 0x2B4 | 偵錯工具已經終止處理程序。 |
Debugger terminated process. |
| 0x2B5 | 偵錯工具取得控制 C。 |
Debugger got control C. |
| 0x2B6 | 偵錯工具列印出在控制 C 上的例外。 |
Debugger printed exception on control C. |
| 0x2B7 | 偵錯工具收到 RIP 例外。 |
Debugger received RIP exception. |
| 0x2B8 | 偵錯工具收到控制中斷。 |
Debugger received control break. |
| 0x2B9 | 偵錯工具命令通訊例外狀況。 |
Debugger command communication exception. |
| 0x2BA | {物件已存在}試圖建立一名稱已存在的物件。 |
{Object Exists}An attempt was made to create an object and the object name already existed. |
| 0x2BB | {暫停執行緒}暫停執行緒時，發生執行緒終止情況。當恢復執行緒時即取消終止。 |
{Thread Suspended}A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded. |
| 0x2BC | {映像重配置}無法在映像檔指定的位址對應該映像檔。必須執行本機映像檔修正。 |
{Image Relocated}An image file could not be mapped at the address specified in the image file. Local fixups must be performed on this image. |
| 0x2BD | 這個資訊層級狀態表示某個特定登錄的子目錄交易狀態不存在，且必須建立。 |
This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created. |
| 0x2BE | {區段載入}正載入、解除載入一個虛擬 DOS 電腦 (VDM)，或移動一個 MS-DOS 或 Win16 程式區段映像。產生例外讓偵錯工具能在這些 16 位元區段中載入、解除載入或追蹤符號與中斷點。 |
{Segment Load}A virtual DOS machine (VDM) is loading, unloading, or moving an MS-DOS or Win16 program segment image.An exception is raised so a debugger can load, unload or track symbols and breakpoints within these 16-bit segments. |
| 0x2BF | {目前的目錄無效}處理程序無法切換到啟動目前目錄 %hs。請選取 [確定]，將目前的目錄設定為 %hs，或選取 [取消] 離開。 |
{Invalid Current Directory}The process cannot switch to the startup current directory %hs.Select OK to set current directory to %hs, or select CANCEL to exit. |
| 0x2C0 | {複件讀取}為了完成讀取要求，NT 容錯檔案系統成功地從複製檔中讀取所要求的資料。這是因為檔案系統在一個容錯磁碟區的成員遇到失敗，無法重新指派裝置的失敗區域。 |
{Redundant Read}To satisfy a read request, the NT fault-tolerant file system successfully read the requested data from a redundant copy.This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was unable to reassign the failing area of the device. |
| 0x2C1 | {複件寫入}為了完成讀取要求，NT 容錯檔案系統成功地從複製檔中寫入所要求的資料。這是因為檔案系統在一個容錯磁碟區的成員遇到失敗，無法重新指派裝置的失敗區域。 |
{Redundant Write}To satisfy a write request, the NT fault-tolerant file system successfully wrote a redundant copy of the information.This was done because the file system encountered a failure on a member of the fault-tolerant volume, but was not able to reassign the failing area of the device. |
| 0x2C2 | {電腦類型不符}映像檔 %hs 是正確的，但不屬於目前的電腦類型。選擇 [確定] 以繼續操作，或選擇 [取消] 不讓 DLL 載入。 |
{Machine Type Mismatch}The image file %hs is valid, but is for a machine type other than the current machine. Select OK to continue, or CANCEL to fail the DLL load. |
| 0x2C3 | {已接收部分資料}網路已傳輸部分資料至用戶端。稍後再傳輸其餘資料。 |
{Partial Data Received}The network transport returned partial data to its client. The remaining data will be sent later. |
| 0x2C4 | {已接收資料}網路傳輸資料至用戶端並在遠端系統上標記已傳輸。 |
{Expedited Data Received}The network transport returned data to its client that was marked as expedited by the remote system. |
| 0x2C5 | {已接收部分資料}網路已傳輸部分資料至用戶端且在遠端系統上標記該資料。稍後再傳輸其餘資料。 |
{Partial Expedited Data Received}The network transport returned partial data to its client and this data was marked as expedited by the remote system. The remaining data will be sent later. |
| 0x2C6 | {TDI 事件完成}TDI 指標已成功完成。 |
{TDI Event Done}The TDI indication has completed successfully. |
| 0x2C7 | {TDI 事件擱置}TDI 指標進入等待狀態。 |
{TDI Event Pending}The TDI indication has entered the pending state. |
| 0x2C8 | 檢查 %wZ 上的檔案系統 |
Checking file system on %wZ |
| 0x2C9 | {嚴重的應用程式結束}%hs |
{Fatal Application Exit}%hs |
| 0x2CA | 指定的登錄機碼被一個預先定義的控制代碼所參照。 |
The specified registry key is referenced by a predefined handle. |
| 0x2CB | {解除分頁鎖定}分頁鎖定的保護狀態變更為 [不允許存取] 且從記憶體及程序中解除分頁鎖定。 |
{Page Unlocked}The page protection of a locked page was changed to 'No Access' and the page was unlocked from memory and from the process. |
| 0x2CC | %hs |
%hs |
| 0x2CD | {分頁鎖定}欲鎖定的分頁之一已鎖定。 |
{Page Locked}One of the pages to lock was already locked. |
| 0x2CE | 應用程式快顯: %1: %2 |
Application popup: %1 : %2 |
| 0x2CF | ERROR_ALREADY_WIN32 |
ERROR_ALREADY_WIN32 |
| 0x2D0 | {電腦類型不符}映像檔 %hs 正確，但不屬於目前的電腦類型。 |
{Machine Type Mismatch}The image file %hs is valid, but is for a machine type other than the current machine. |
| 0x2D1 | 執行 yield 而沒有可用來執行的執行緒。 |
A yield execution was performed and no thread was available to run. |
| 0x2D2 | 略過計時器 API 的可恢復旗標。 |
The resumable flag to a timer API was ignored. |
| 0x2D3 | 仲裁程式已經將這些資源的仲裁順延到它的父系上 |
The arbiter has deferred arbitration of these resources to its parent |
| 0x2D4 | 因為 \"%hs\" 發生組態錯誤，所以無法啟動插入的 CardBus 裝置。 |
The inserted CardBus device cannot be started because of a configuration error on \"%hs\". |
| 0x2D5 | 這個多處理器系統內的 CPU 的修訂等級各不相同。要使用所有處理器，作業系統只能使用系統內最少的功能。如果這個系統發生問題，請與 CPU 製造商聯繫，了解這樣組合的處理器是否受到支援。 |
The CPUs in this multiprocessor system are not all the same revision level. To use all processors the operating system restricts itself to the features of the least capable processor in the system. Should problems occur with this system, contact the CPU manufacturer to see if this mix of processors is supported. |
| 0x2D6 | 系統已進入休眠狀態中。 |
The system was put into hibernation. |
| 0x2D7 | 系統已從休眠狀態復甦繼續。 |
The system was resumed from hibernation. |
| 0x2D8 | Windows 偵測到系統韌體 (BIOS) 已更新 [前版韌體日期 = %2，目前的韌體日期 %3]。 |
Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3]. |
| 0x2D9 | 裝置驅動程式正在漏出鎖定的 I/O 分頁，造成系統降級。系統擁有自動啟動的追蹤程式以嘗試抓住這類問題。 |
A device driver is leaking locked I/O pages causing system degradation. The system has automatically enabled tracking code in order to try and catch the culprit. |
| 0x2DA | 系統已經醒機 |
The system has awoken |
| 0x2DB | ERROR_WAIT_1 |
ERROR_WAIT_1 |
| 0x2DC | ERROR_WAIT_2 |
ERROR_WAIT_2 |
| 0x2DD | ERROR_WAIT_3 |
ERROR_WAIT_3 |
| 0x2DE | ERROR_WAIT_63 |
ERROR_WAIT_63 |
| 0x2DF | ERROR_ABANDONED_WAIT_0 |
ERROR_ABANDONED_WAIT_0 |
| 0x2E0 | ERROR_ABANDONED_WAIT_63 |
ERROR_ABANDONED_WAIT_63 |
| 0x2E1 | ERROR_USER_APC |
ERROR_USER_APC |
| 0x2E2 | ERROR_KERNEL_APC |
ERROR_KERNEL_APC |
| 0x2E3 | ERROR_ALERTED |
ERROR_ALERTED |
| 0x2E4 | 要求的作業需要提升的權限。 |
The requested operation requires elevation. |
| 0x2E5 | 因為檔案名稱產生符號連結，所以需由物件管理員執行重新分析的操作。 |
A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link. |
| 0x2E6 | 在 oplock 中斷進行中，完成一項開啟/建立操作。 |
An open/create operation completed while an oplock break is underway. |
| 0x2E7 | 檔案系統已裝上新的磁碟區。 |
A new volume has been mounted by a file system. |
| 0x2E8 | 這個成功等級狀態指出交易狀態已存在於登錄子目錄，但交易確認在先前已中止。目前已經完成這個確認。 |
This success level status indicates that the transaction state already exists for the registry sub-tree, but that a transaction commit was previously aborted.The commit has now been completed. |
| 0x2E9 | 表示因關閉控制代碼而產生的提示變更請求已完成。 |
This indicates that a notify change request has been completed due to closing the handle which made the notify change request. |
| 0x2EA | {主要傳輸連線錯誤}以主要傳輸連接遠端伺服器 %hs 錯誤。本電腦可以用次層傳輸連線。 |
{Connect Failure on Primary Transport}An attempt was made to connect to the remote server %hs on the primary transport, but the connection failed.The computer WAS able to connect on a secondary transport. |
| 0x2EB | 分頁錯誤為轉換錯誤。 |
Page fault was a transition fault. |
| 0x2EC | 分頁錯誤為請求 0 錯誤。 |
Page fault was a demand zero fault. |
| 0x2EF | 讀取次級存放裝置時，分頁檔發生錯誤。 |
Page fault was satisfied by reading from a secondary storage device. |
| 0x2F0 | 操作時鎖定快取記憶體頁。 |
Cached page was locked during operation. |
| 0x2F1 | 分頁檔含有損毀傾印資料。 |
Crash dump exists in paging file. |
| 0x2F2 | 指定的緩衝區中包含所有的 0。 |
Specified buffer contains all zeros. |
| 0x2F4 | 裝置已經完成 '查詢停止'，而且它的資源需求已變更。 |
The device has succeeded a query-stop and its resource requirements have changed. |
| 0x2F5 | 轉譯程式已將這些資源轉譯到通用空間，不應該再執行進一步的轉譯。 |
The translator has translated these resources into the global space and no further translations should be performed. |
| 0x2F6 | 即將終止的處理程序沒有執行緒可供終止。 |
A process being terminated has no threads to terminate. |
| 0x2F7 | 指定的處理程序不是工作的一部分。 |
The specified process is not part of a job. |
| 0x2F8 | 指定的處理程序是工作的一部分。 |
The specified process is part of a job. |
| 0x2F9 | {磁碟區陰影複製服務}系統已準備好休眠。 |
{Volume Shadow Copy Service}The system is now ready for hibernation. |
| 0x2FA | 檔案系統或檔案系統篩選器驅動程式已經成功的完成 FsFilter 操作。 |
A file system or file system filter driver has successfully completed an FsFilter operation. |
| 0x2FB | 指定的插斷向量已連接。 |
The specified interrupt vector was already connected. |
| 0x2FC | 指定的插斷向量仍在連接中。 |
The specified interrupt vector is still connected. |
| 0x2FD | 中止操作，以等候 oplock。 |
An operation is blocked waiting for an oplock. |
| 0x2FE | 偵錯工具處理了例外 |
Debugger handled exception |
| 0x2FF | 偵錯工具已經繼續 |
Debugger continued |
| 0x300 | 使用者模式回呼發生例外，且應該移除核心回呼框架。 |
An exception occurred in a user mode callback and the kernel callback frame should be removed. |
| 0x301 | 已停用此磁碟區的壓縮。 |
Compression is disabled for this volume. |
| 0x302 | 資料提供者無法向後擷取結果集。 |
The data provider cannot fetch backwards through a result set. |
| 0x303 | 資料提供者無法向後捲動結果集。 |
The data provider cannot scroll backwards through a result set. |
| 0x304 | 資料提供者需要釋放之前擷取的資料，才能要求更多資料。 |
The data provider requires that previously fetched data is released before asking for more data. |
| 0x305 | 資料提供者無法解譯針對存取子中的欄位繫結所設定的旗標。 |
The data provider was not able to interpret the flags set for a column binding in an accessor. |
| 0x306 | 處理要求時，發生一或多個錯誤。 |
One or more errors occurred while processing the request. |
| 0x307 | 執行方式無法執行要求。 |
The implementation is not capable of performing the request. |
| 0x308 | 元件用戶端要求了作業，而作業指定的元件執行個體無效。 |
The client of a component requested an operation which is not valid given the state of the component instance. |
| 0x309 | 無法解析版本號碼。 |
A version number could not be parsed. |
| 0x30A | iterator 的起始位置無效。 |
The iterator's start position is invalid. |
| 0x30B | 硬體已報告無法修正的記憶體錯誤。 |
The hardware has reported an uncorrectable memory error. |
| 0x30C | 嘗試的作業需要啟用自我修復的功能。 |
The attempted operation required self healing to be enabled. |
| 0x30D | 桌面堆積在配置工作階段記憶體時發生錯誤。在系統事件記錄檔中會有詳細資訊。 |
The Desktop heap encountered an error while allocating session memory. There is more information in the system event log. |
| 0x30E | 系統電源狀態正由 %2 轉換為 %3。 |
The system power state is transitioning from %2 to %3. |
| 0x30F | 系統電源狀態正由 %2 轉換為 %3，但可能會進入 %4。 |
The system power state is transitioning from %2 to %3 but could enter %4. |
| 0x310 | 因為 MCA，執行緒正在中斷與 MCA EXCEPTION 的連線。 |
A thread is getting dispatched with MCA EXCEPTION because of MCA. |
| 0x311 | 對 %1 的存取是由原則規則 %2 監視。 |
Access to %1 is monitored by policy rule %2. |
| 0x312 | 系統管理員依照原則規則 %2，已經限制了對 %1 的存取。 |
Access to %1 has been restricted by your Administrator by policy rule %2. |
| 0x313 | 有效的休眠檔案已經失效，且應該將其丟棄。 |
A valid hibernation file has been invalidated and should be abandoned. |
| 0x314 | {延遲寫入失敗}Windows 無法儲存檔案 %hs 的所有資料; 資料已經遺失。這個錯誤可能是因為網路連線問題所造成。請嘗試在其他位置儲存這個檔案。 |
{Delayed Write Failed}Windows was unable to save all the data for the file %hs; the data has been lost.This error may be caused by network connectivity issues. Please try to save this file elsewhere. |
| 0x315 | {延遲寫入失敗}Windows 無法儲存檔案 %hs 的所有資料; 資料已遺失。這個錯誤是由檔案所在的伺服器傳回。請嘗試在其他位置儲存這個檔案。 |
{Delayed Write Failed}Windows was unable to save all the data for the file %hs; the data has been lost.This error was returned by the server on which the file exists. Please try to save this file elsewhere. |
| 0x316 | {延遲寫入失敗}Windows 無法儲存檔案 %hs 的所有資料; 資料已遺失。如果裝置已移除或媒體具有防寫保護，便會發生此錯誤。 |
{Delayed Write Failed}Windows was unable to save all the data for the file %hs; the data has been lost.This error may be caused if the device has been removed or the media is write-protected. |
| 0x317 | 此裝置所需的資源與 MCFG 表格互相衝突。 |
The resources required for this device conflict with the MCFG table. |
| 0x318 | 無法在磁碟區連線時執行磁碟區修復。請排程讓磁碟區離線，以進行修復。 |
The volume repair could not be performed while it is online.Please schedule to take the volume offline so that it can be repaired. |
| 0x319 | 磁碟區修復失敗。 |
The volume repair was not successful. |
| 0x31A | 其中一個磁碟區損毀記錄檔已滿。將不會記錄之後偵測到的損毀。 |
One of the volume corruption logs is full. Further corruptions that may be detected won't be logged. |
| 0x31B | 其中一個磁碟區損毀記錄檔內部損毀，需要重建。磁碟區可能包含未偵測的損毀，因此必須進行掃描。 |
One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned. |
| 0x31C | 無法在其中一個磁碟區損毀記錄檔上進行操作。 |
One of the volume corruption logs is unavailable for being operated on. |
| 0x31D | 已刪除其中一個磁碟區損毀記錄檔，但其中仍然有損毀記錄。磁碟區包含已偵測的損毀，因此必須進行掃描。 |
One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned. |
| 0x31E | chkdsk 已清除其中一個磁碟區損毀記錄檔，因此不再包含實際的損毀。 |
One of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions. |
| 0x31F | 孤立檔案存在於磁碟區上，但因為無法再於復原目錄中建立新名稱，所以無法進行復原。必須從復原目錄中移動檔案。 |
Orphaned files exist on the volume but could not be recovered because no more new names could be created in the recovery directory. Files must be moved from the recovery directory. |
| 0x320 | 與此控制代碼關聯的 Oplock 現在已與其他控制代碼相關聯。 |
The oplock that was associated with this handle is now associated with a different handle. |
| 0x321 | 不允許所要求層級的 Oplock。應有可用的較低層級 Oplock。 |
An oplock of the requested level cannot be granted. An oplock of a lower level may be available. |
| 0x322 | 無法順利完成操作，因為該操作會造成 Oplock 中斷。呼叫者已要求現有的 Oplock 不得中斷。 |
The operation did not complete successfully because it would cause an oplock to be broken. The caller has requested that existing oplocks not be broken. |
| 0x323 | 與這個 Oplock 關聯的控制代碼已經關閉。Oplock 現在已經中斷。 |
The handle with which this oplock was associated has been closed. The oplock is now broken. |
| 0x324 | 指定的存取控制項目 (ACE) 未包含條件。 |
The specified access control entry (ACE) does not contain a condition. |
| 0x325 | 指定的存取控制項目 (ACE) 包含有效的條件。 |
The specified access control entry (ACE) contains an invalid condition. |
| 0x326 | 已撤銷對所指定檔案控制代碼的存取權。 |
Access to the specified file handle has been revoked. |
| 0x327 | {映像重新放置}映像並非從所指定映像檔中的位址對應，但仍會在該映像上執行自動修正。 |
{Image Relocated}An image file was mapped at a different address from the one specified in the image file but fixups will still be automatically performed on the image. |
| 0x328 | 無法完成加密檔案的讀取或寫入操作，因為尚未開啟該檔案進行資料存取。 |
The read or write operation to an encrypted file could not be completed because the file has not been opened for data access. |
| 0x329 | 已經在進行檔案中繼資料最佳化。 |
File metadata optimization is already in progress. |
| 0x32A | 由於仍在執行配額操作，因此要求的操作失敗。 |
The requested operation failed due to quota operation is still in progress. |
| 0x32B | 已撤銷對所指定控制代碼的存取權。 |
Access to the specified handle has been revoked. |
| 0x32C | 回呼函式必須以內嵌方式叫用。 |
The callback function must be invoked inline. |
| 0x32D | 指定的 CPU 設定識別碼無效。 |
The specified CPU Set IDs are invalid. |
| 0x3E2 | 存取擴充屬性被拒。 |
Access to the extended attribute was denied. |
| 0x3E3 | 因為執行緒結束或應用程式要求，所以已中止 I/O 操作。 |
The I/O operation has been aborted because of either a thread exit or an application request. |
| 0x3E4 | 重疊的 I/O 事件不處於信號狀態中。 |
Overlapped I/O event is not in a signaled state. |
| 0x3E5 | 重疊的 I/O 操作正在進行中。 |
Overlapped I/O operation is in progress. |
| 0x3E6 | 記憶體配置存取不正確。 |
Invalid access to memory location. |
| 0x3E7 | Inpage 操作執行錯誤。 |
Error performing inpage operation. |
| 0x3E9 | 循環太深，堆疊溢位。 |
Recursion too deep; the stack overflowed. |
| 0x3EA | 視窗無法在傳送訊息上動作。 |
The window cannot act on the sent message. |
| 0x3EB | 無法完成此功能。 |
Cannot complete this function. |
| 0x3EC | 旗標不正確。 |
Invalid flags. |
| 0x3ED | 磁碟區未包含可辨識的檔案系統。請確定所有必需的檔案系統驅動程式都已載入，而且磁碟區未損毀。 |
The volume does not contain a recognized file system.Please make sure that all required file system drivers are loaded and that the volume is not corrupted. |
| 0x3EE | 檔案的磁碟區已經從外部做了變更，這個開啟的檔案已無法使用。 |
The volume for a file has been externally altered so that the opened file is no longer valid. |
| 0x3EF | 無法在全螢幕模式中執行要求的操作。 |
The requested operation cannot be performed in full-screen mode. |
| 0x3F0 | 企圖參考不存在的權杖。 |
An attempt was made to reference a token that does not exist. |
| 0x3F1 | 設定登錄資料庫損毀。 |
The configuration registry database is corrupt. |
| 0x3F2 | 設定登錄機碼不正確。 |
The configuration registry key is invalid. |
| 0x3F3 | 無法開啟設定登錄機碼。 |
The configuration registry key could not be opened. |
| 0x3F4 | 無法讀取設定登錄機碼。 |
The configuration registry key could not be read. |
| 0x3F5 | 無法寫入設定登錄機碼。 |
The configuration registry key could not be written. |
| 0x3F6 | 登錄資料庫中的檔案之一必須用記錄檔或其他備份檔進行復原。復原已完成。 |
One of the files in the registry database had to be recovered by use of a log or alternate copy. The recovery was successful. |
| 0x3F7 | 登錄已損毀。可能是登錄資料中的檔案結構損毀，或記憶體中的檔案系統映像損毀，或因為缺少某些複件，或是記錄檔損毀，造成檔案無法復原。 |
The registry is corrupted. The structure of one of the files containing registry data is corrupted, or the system's memory image of the file is corrupted, or the file could not be recovered because the alternate copy or log was absent or corrupted. |
| 0x3F8 | 根據登錄所進行的 I/O 操作初始失敗，無法還原。登錄無法讀取，寫入或清除某個含有系統映像的檔案。 |
An I/O operation initiated by the registry failed unrecoverably. The registry could not read in, or write out, or flush, one of the files that contain the system's image of the registry. |
| 0x3F9 | 系統已經嘗試要載入或還原檔案到登錄中，但指定的檔案不是登錄檔案格式。 |
The system has attempted to load or restore a file into the registry, but the specified file is not in a registry file format. |
| 0x3FA | 試圖在一個已經標記為刪除的登錄機碼中進行不正確的操作。 |
Illegal operation attempted on a registry key that has been marked for deletion. |
| 0x3FB | 系統無法將所需的空間配置給登錄記錄檔。 |
System could not allocate the required space in a registry log. |
| 0x3FC | 無法在已含有子機碼或數值的登錄機碼上建立符號連結。 |
Cannot create a symbolic link in a registry key that already has subkeys or values. |
| 0x3FD | 無法在變動的父系機碼下建立穩定的子機碼。 |
Cannot create a stable subkey under a volatile parent key. |
| 0x3FE | 通知變更請求正完成中，且資訊並未傳回呼叫者緩衝器中。目前呼叫者必須列舉檔案來尋找變更。 |
A notify change request is being completed and the information is not being returned in the caller's buffer. The caller now needs to enumerate the files to find the changes. |
| 0x41B | 已經將停止控制傳送給一個服務，有其他正在執行的服務依存在這個服務上。 |
A stop control has been sent to a service that other running services are dependent on. |
| 0x41C | 所要求的控制對於這個服務來說是不正確的。 |
The requested control is not valid for this service. |
| 0x41D | 服務並未以適時的方式回應啟動或控制請求。 |
The service did not respond to the start or control request in a timely fashion. |
| 0x41E | 無法建立此服務的執行緒。 |
A thread could not be created for the service. |
| 0x41F | 服務資料庫已鎖定。 |
The service database is locked. |
| 0x420 | 服務的例項已在執行中。 |
An instance of the service is already running. |
| 0x421 | 這個帳戶名稱不正確或不存在，或指定的帳戶名稱密碼不正確。 |
The account name is invalid or does not exist, or the password is invalid for the account name specified. |
| 0x422 | 無法啟動服務，可能因為服務已停用，或它沒有相關的啟用裝置。 |
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. |
| 0x423 | 指定循環服務相依性。 |
Circular service dependency was specified. |
| 0x424 | 指定的服務並不是已安裝的服務。 |
The specified service does not exist as an installed service. |
| 0x425 | 服務無法在此時接受控制訊息。 |
The service cannot accept control messages at this time. |
| 0x426 | 服務尚未啟動。 |
The service has not been started. |
| 0x427 | 服務程序無法連接到服務控制站。 |
The service process could not connect to the service controller. |
| 0x428 | 當處理控制請求時，在服務中發生例外。 |
An exception occurred in the service when handling the control request. |
| 0x429 | 指定的資料庫不存在。 |
The database specified does not exist. |
| 0x42A | 服務已傳回特定的服務錯誤碼。 |
The service has returned a service-specific error code. |
| 0x42B | 處理程序意外終止。 |
The process terminated unexpectedly. |
| 0x42C | 相依性服務或群組無法啟動。 |
The dependency service or group failed to start. |
| 0x42D | 登入失敗所以服務無法啟動。 |
The service did not start due to a logon failure. |
| 0x42E | 啟動之後，服務停留在啟動暫停狀態。 |
After starting, the service hung in a start-pending state. |
| 0x42F | 指定的服務資料庫鎖定無效。 |
The specified service database lock is invalid. |
| 0x430 | 指定的服務已標註刪除。 |
The specified service has been marked for deletion. |
| 0x431 | 指定的服務已存在。 |
The specified service already exists. |
| 0x432 | 系統正在執行上次的正確設定。 |
The system is currently running with the last-known-good configuration. |
| 0x433 | 相依性服務不存在，或已標記為刪除。 |
The dependency service does not exist or has been marked for deletion. |
| 0x434 | 已接受使用目前的開機設定做為正確的控制組。 |
The current boot has already been accepted for use as the last-known-good control set. |
| 0x435 | 上次開機之後，尚未嘗試啟動服務。 |
No attempts to start the service have been made since the last boot. |
| 0x436 | 名稱已使用為服務名稱或服務顯示名稱。 |
The name is already in use as either a service name or a service display name. |
| 0x437 | 為這個服務所指定的帳戶，與其他在相同處理上所執行的服務帳戶不同。 |
The account specified for this service is different from the account specified for other services running in the same process. |
| 0x438 | 只有 Win32 服務能設定失敗動作，驅動程式不能。 |
Failure actions can only be set for Win32 services, not for drivers. |
| 0x439 | 這個服務所執行的處理和服務控制管理員相同。所以，如果服務的處理程序意外終止的話，服務控制管理員無法進行任何動作。 |
This service runs in the same process as the service control manager.Therefore, the service control manager cannot take action if this service's process terminates unexpectedly. |
| 0x43A | 這個服務尚未設定復原程式。 |
No recovery program has been configured for this service. |
| 0x43B | 這個服務設定要啟動的可執行檔無法執行服務。 |
The executable program that this service is configured to run in does not implement the service. |
| 0x43C | 無法在安全模式中啟動這項服務 |
This service cannot be started in Safe Mode |
| 0x44C | 已達磁帶的實體結尾。 |
The physical end of the tape has been reached. |
| 0x44D | 磁帶存取已達檔案標記。 |
A tape access reached a filemark. |
| 0x44E | 遇到磁碟分割或磁帶的起頭。 |
The beginning of the tape or a partition was encountered. |
| 0x44F | 磁帶存取已達一組檔案的結尾。 |
A tape access reached the end of a set of files. |
| 0x450 | 磁帶上不再有任何資料。 |
No more data is on the tape. |
| 0x451 | 無法分割磁帶。 |
Tape could not be partitioned. |
| 0x452 | 存取多重磁碟區磁碟分割的新磁帶時，目前的區塊大小不正確。 |
When accessing a new tape of a multivolume partition, the current block size is incorrect. |
| 0x453 | 載入磁帶時，找不到磁帶磁碟分割資訊。 |
Tape partition information could not be found when loading a tape. |
| 0x454 | 無法鎖定媒體退出機能。 |
Unable to lock the media eject mechanism. |
| 0x455 | 無法解除載入媒體。 |
Unable to unload the media. |
| 0x456 | 磁碟機中的媒體可能已經變更。 |
The media in the drive may have changed. |
| 0x457 | 重設 I/O 匯流排。 |
The I/O bus was reset. |
| 0x458 | 磁碟機中沒有磁帶。 |
No media in drive. |
| 0x459 | 在多位元組的目的字碼頁中，沒有這個 Unicode 字元可以對應到的字元。 |
No mapping for the Unicode character exists in the target multi-byte code page. |
| 0x45A | 動態連結程式庫 (DLL) 初始化例行程序失敗。 |
A dynamic link library (DLL) initialization routine failed. |
| 0x45B | 系統關機進行中。 |
A system shutdown is in progress. |
| 0x45C | 因為沒有任何進行中的關機，所以無法中止系統關機。 |
Unable to abort the system shutdown because no shutdown was in progress. |
| 0x45D | 因為 I/O 裝置錯誤，所以無法執行請求。 |
The request could not be performed because of an I/O device error. |
| 0x45E | 序列裝置並未成功初始。序列驅動程式將解除載入。 |
No serial device was successfully initialized. The serial driver will unload. |
| 0x45F | 無法開啟正在與其他裝置共用插斷要求 (IRQ) 的裝置。至少有一個使用該 IRQ 的其他裝置已開啟。 |
Unable to open a device that was sharing an interrupt request (IRQ) with other devices. At least one other device that uses that IRQ was already opened. |
| 0x460 | 序列 I/O 操作已由另一個序列埠的寫入完成。(IOCTL_SERIAL_XOFF_COUNTER 已達零。) |
A serial I/O operation was completed by another write to the serial port.(The IOCTL_SERIAL_XOFF_COUNTER reached zero.) |
| 0x461 | 因為暫停期間已到期，所以序列 I/O 操作完成。(IOCTL_SERIAL_XOFF_COUNTER 未到達零。) |
A serial I/O operation completed because the timeout period expired.(The IOCTL_SERIAL_XOFF_COUNTER did not reach zero.) |
| 0x462 | 在磁片上找不到 ID 位址標記。 |
No ID address mark was found on the floppy disk. |
| 0x463 | 磁碟片的磁區識別碼欄位與軟碟機控制器磁軌位址間不相符。 |
Mismatch between the floppy disk sector ID field and the floppy disk controller track address. |
| 0x464 | 軟碟機控制器提出無法被軟碟機驅動程式識別的錯誤報表。 |
The floppy disk controller reported an error that is not recognized by the floppy disk driver. |
| 0x465 | 軟碟機控制器傳回登錄中不一致的結果。 |
The floppy disk controller returned inconsistent results in its registers. |
| 0x466 | 存取硬碟時，重新校準操作失敗，重試後還是失敗。 |
While accessing the hard disk, a recalibrate operation failed, even after retries. |
| 0x467 | 存取硬碟時，磁碟操作失敗，重試後還是失敗。 |
While accessing the hard disk, a disk operation failed even after retries. |
| 0x468 | 存取硬碟時，需要重設磁碟控制卡，但失敗了。 |
While accessing the hard disk, a disk controller reset was needed, but even that failed. |
| 0x469 | 已達磁帶實體結尾。 |
Physical end of tape encountered. |
| 0x46A | 伺服器存放空間不足，無法處理此命令。 |
Not enough server storage is available to process this command. |
| 0x46B | 偵測出潛在的鎖死狀態。 |
A potential deadlock condition has been detected. |
| 0x46C | 指定的起始位址或檔案位移沒有適當的對齊方式。 |
The base address or the file offset specified does not have the proper alignment. |
| 0x474 | 變更系統電源狀態的嘗試，已被另一個應用程式或驅動程式所否決。 |
An attempt to change the system power state was vetoed by another application or driver. |
| 0x475 | 系統 BIOS 嘗試變更系統電源狀態失敗。 |
The system BIOS failed an attempt to change the system power state. |
| 0x476 | 嘗試建立比檔案系統所支援還多的檔案連結。 |
An attempt was made to create more links on a file than the file system supports. |
| 0x47E | 所指定的程式需要較新版的 Windows。 |
The specified program requires a newer version of Windows. |
| 0x47F | 所指定的程式不是 Windows 或 MS-DOS 程式。 |
The specified program is not a Windows or MS-DOS program. |
| 0x480 | 一次只能開啟一個指定程式的例項。 |
Cannot start more than one instance of the specified program. |
| 0x481 | 指定的程式是寫給舊的 Windows 版本使用的。 |
The specified program was written for an earlier version of Windows. |
| 0x482 | 執行這個應用程式所需的某個程式庫檔案已經損毀。 |
One of the library files needed to run this application is damaged. |
| 0x483 | 沒有任何應用程式與此操作的指定檔案有關聯。 |
No application is associated with the specified file for this operation. |
| 0x484 | 將命令送往應用程式時，發生錯誤。 |
An error occurred in sending the command to the application. |
| 0x485 | 找不到執行這個應用程式所需的某個程式庫檔案。 |
One of the library files needed to run this application cannot be found. |
| 0x486 | 目前的程序已經使用了視窗管理員物件所有的系統可用控制代碼。 |
The current process has used all of its system allowance of handles for Window Manager objects. |
| 0x487 | 訊息只能與同步操作一起使用。 |
The message can be used only with synchronous operations. |
| 0x488 | 被指出的來源元素沒有媒體。 |
The indicated source element has no media. |
| 0x489 | 指出的目的地元素已經包含媒體。 |
The indicated destination element already contains media. |
| 0x48A | 指出的元素不存在。 |
The indicated element does not exist. |
| 0x48B | 指出的元素屬於目前不存在的雜誌。 |
The indicated element is part of a magazine that is not present. |
| 0x48C | 指出的裝置需要重新初始化，因為硬體錯誤。 |
The indicated device requires reinitialization due to hardware errors. |
| 0x48D | 裝置已經指出在嘗試進一步的操作之前需要清除。 |
The device has indicated that cleaning is required before further operations are attempted. |
| 0x48E | 裝置已經指出它的門沒有關好。 |
The device has indicated that its door is open. |
| 0x48F | 裝置沒有連線。 |
The device is not connected. |
| 0x490 | 元素找不到。 |
Element not found. |
| 0x491 | 在索引中找不到符合指定機碼的項目。 |
There was no match for the specified key in the index. |
| 0x492 | 指定的內容組不存在於物件中。 |
The property set specified does not exist on the object. |
| 0x493 | 傳到 GetMouseMovePoints 的指標不在緩衝區中。 |
The point passed to GetMouseMovePoints is not in the buffer. |
| 0x494 | 追蹤 (工作站) 服務並未執行。 |
The tracking (workstation) service is not running. |
| 0x495 | 找不到磁碟區 ID。 |
The Volume ID could not be found. |
| 0x497 | 無法移除要被取代的檔案。 |
Unable to remove the file to be replaced. |
| 0x498 | 無法取代可執行檔案。檔案名稱是原始名稱。 |
Unable to move the replacement file to the file to be replaced. The file to be replaced has retained its original name. |
| 0x499 | 無法進行檔案取代。要被取代的檔案已被以備份名稱重新命名了。 |
Unable to move the replacement file to the file to be replaced. The file to be replaced has been renamed using the backup name. |
| 0x49A | 正在刪除磁碟區變更日誌。 |
The volume change journal is being deleted. |
| 0x49B | 磁碟區變更日誌不在使用中。 |
The volume change journal is not active. |
| 0x49C | 找到一個檔案，但它可能不是正確的檔案。 |
A file was found, but it may not be the correct file. |
| 0x49D | 日誌項目已從日誌中刪除。 |
The journal entry has been deleted from the journal. |
| 0x49F | 當 CFG 已啟用時，無法設定驅動程式檢查器揮發性設定。 |
Driver Verifier Volatile settings cannot be set when CFG is enabled. |
| 0x4A6 | 已排程系統關閉。 |
A system shutdown has already been scheduled. |
| 0x4A7 | 因為有其他使用者登入電腦，所以無法初始化系統關閉。 |
The system shutdown cannot be initiated because there are other users logged on to the computer. |
| 0x4B0 | 指定的裝置名稱不正確。 |
The specified device name is invalid. |
| 0x4B1 | 裝置目前未連接，但它被記憶為連接狀態。 |
The device is not currently connected but it is a remembered connection. |
| 0x4B2 | 本機裝置名稱有一個記憶連線可接往別的網路資源。 |
The local device name has a remembered connection to another network resource. |
| 0x4B3 | 輸入的網路路徑不正確、不存在，或網路提供者目前無法使用。請嘗試重新輸入路徑，或連絡您的網路系統管理員。 |
The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator. |
| 0x4B4 | 指定的網路提供者名稱無效。 |
The specified network provider name is invalid. |
| 0x4B5 | 無法開啟網路連線設定檔。 |
Unable to open the network connection profile. |
| 0x4B6 | 網路連線設定檔損毀。 |
The network connection profile is corrupted. |
| 0x4B7 | 無法列舉不是容器的項目。 |
Cannot enumerate a noncontainer. |
| 0x4B8 | 發生延伸錯誤。 |
An extended error has occurred. |
| 0x4B9 | 指定的群組名稱格式不正確。 |
The format of the specified group name is invalid. |
| 0x4BA | 指定的電腦名稱格式不正確。 |
The format of the specified computer name is invalid. |
| 0x4BB | 指定的事件名稱格式不正確。 |
The format of the specified event name is invalid. |
| 0x4BC | 指定的網域名稱格式不正確。 |
The format of the specified domain name is invalid. |
| 0x4BD | 指定的服務名稱格式不正確。 |
The format of the specified service name is invalid. |
| 0x4BE | 指定的網路名稱格式不正確。 |
The format of the specified network name is invalid. |
| 0x4BF | 指定的共用名稱格式不正確。 |
The format of the specified share name is invalid. |
| 0x4C0 | 指定的密碼格式不正確。 |
The format of the specified password is invalid. |
| 0x4C1 | 指定的訊息名稱格式不正確。 |
The format of the specified message name is invalid. |
| 0x4C2 | 指定訊息目的地格式不正確。 |
The format of the specified message destination is invalid. |
| 0x4C3 | 不允許使用多於一個使用者名稱的相同使用者有多個連線到一個伺服器或共用資源。中斷所有之前到伺服器或共用資源的連線，然後再試。 |
Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again. |
| 0x4C4 | 嘗試建立網路伺服器的工作階段，但已對該伺服器建立過多的工作階段。 |
An attempt was made to establish a session to a network server, but there are already too many sessions established to that server. |
| 0x4C5 | 工作群組或網域名稱已由網路上的另一部電腦使用中。 |
The workgroup or domain name is already in use by another computer on the network. |
| 0x4C6 | 網路不存在或尚未啟動。 |
The network is not present or not started. |
| 0x4C7 | 操作被使用者取消。 |
The operation was canceled by the user. |
| 0x4C8 | 要求的檔案操作無法執行，因為檔案的使用者對應區段在開啟狀態。 |
The requested operation cannot be performed on a file with a user-mapped section open. |
| 0x4C9 | 遠端電腦拒絕網路連線。 |
The remote computer refused the network connection. |
| 0x4CA | 網路連線已順利關閉。 |
The network connection was gracefully closed. |
| 0x4CB | 網路傳輸端點已有與其關聯的位址。 |
The network transport endpoint already has an address associated with it. |
| 0x4CC | 位址仍未與網路端點關聯。 |
An address has not yet been associated with the network endpoint. |
| 0x4CD | 嘗試操作一個不存在的網路連線。 |
An operation was attempted on a nonexistent network connection. |
| 0x4CE | 企圖在使用中網路連線上進行不正確的操作。 |
An invalid operation was attempted on an active network connection. |
| 0x4CF | 無法連接網路位置。有關網路疑難排解資訊，請參考 Windows 說明。 |
The network location cannot be reached. For information about network troubleshooting, see Windows Help. |
| 0x4D2 | 沒有任何服務正在遠端系統上的目的地網路端點上操作。 |
No service is operating at the destination network endpoint on the remote system. |
| 0x4D3 | 要求已經中止。 |
The request was aborted. |
| 0x4D4 | 本機系統已中止網路連線。 |
The network connection was aborted by the local system. |
| 0x4D5 | 操作無法完成。必須重試。 |
The operation could not be completed. A retry should be performed. |
| 0x4D6 | 已達這個帳戶的最大連線數目，所以無法連接伺服器。 |
A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached. |
| 0x4D7 | 試圖在未授權給這個帳戶的時段中進行登入。 |
Attempting to log in during an unauthorized time of day for this account. |
| 0x4D8 | 帳戶沒有獲得可從此站台登入的授權。 |
The account is not authorized to log in from this station. |
| 0x4D9 | 不能使用這個網路位址進行所要求的操作。 |
The network address could not be used for the operation requested. |
| 0x4DA | 服務已經登錄。 |
The service is already registered. |
| 0x4DB | 指定的服務不存在。 |
The specified service does not exist. |
| 0x4DC | 使用者尚未被驗證，因此無法執行所要求的操作。 |
The operation being requested was not performed because the user has not been authenticated. |
| 0x4DD | 使用者尚未登入網路，因此無法執行所要求的操作。指定的服務不存在。 |
The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. |
| 0x4DE | 繼續執行工作。 |
Continue with work in progress. |
| 0x4DF | 初始化完成後，還嘗試執行初始化操作。 |
An attempt was made to perform an initialization operation when initialization has already been completed. |
| 0x4E0 | 已沒有其他本機裝置。 |
No more local devices. |
| 0x4E1 | 指定的站台不存在。 |
The specified site does not exist. |
| 0x4E2 | 指定名稱的網域控制站已存在。 |
A domain controller with the specified name already exists. |
| 0x4E3 | 這操作只有在和伺服器連線時才能獲得支援。 |
This operation is supported only when you are connected to the server. |
| 0x4E4 | 即使沒有任何變更，群組原則架構也應該呼叫副檔名。 |
The group policy framework should call the extension even if there are no changes. |
| 0x4E5 | 指定的使用者沒有正確的設定檔。 |
The specified user does not have a valid profile. |
| 0x4E6 | 這項操作在執行 Windows Server 2003 for Small Business Server 的電腦上不支援 |
This operation is not supported on a computer running Windows Server 2003 for Small Business Server |
| 0x4E7 | 伺服器電腦正在關機。 |
The server machine is shutting down. |
| 0x4E8 | 遠端系統無法使用。有關網路疑難排解的資訊，請參閱 Windows 說明。 |
The remote system is not available. For information about network troubleshooting, see Windows Help. |
| 0x4E9 | 所提供的安全性識別碼不是來自帳戶網域。 |
The security identifier provided is not from an account domain. |
| 0x4EA | 所提供的安全性識別碼沒有網域元件。 |
The security identifier provided does not have a domain component. |
| 0x4EB | AppHelp 對話已取消，因此防止了應用程式的啟動。 |
AppHelp dialog canceled thus preventing the application from starting. |
| 0x4EC | 此程式已由群組原則封鎖。如需詳細資訊，請連絡您的系統管理員。 |
This program is blocked by group policy. For more information, contact your system administrator. |
| 0x4ED | 某個程式企圖使用不正確的登錄值，這通常是由於登錄未初始化所致。這個錯誤屬於 Itanium 特定。 |
A program attempt to use an invalid register value. Normally caused by an uninitialized register. This error is Itanium specific. |
| 0x4EE | 共用目前離線中，或者並不存在。 |
The share is currently offline or does not exist. |
| 0x4EF | 在智慧卡登入期間，Kerberos 通訊協定在確認 KDC 憑證時發生錯誤。在系統事件記錄檔中會有詳細資訊。 |
The Kerberos protocol encountered an error while validating the KDC certificate during smartcard logon. There is more information in the system event log. |
| 0x4F0 | Kerberos 通訊協定嘗試使用智慧卡子系統時發生錯誤。 |
The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem. |
| 0x4F1 | 系統無法連絡網域控制站以提供驗證要求。請稍後再試一次。 |
The system cannot contact a domain controller to service the authentication request. Please try again later. |
| 0x4F7 | 電腦已鎖定，不能在沒有強制選項下關機。 |
The machine is locked and cannot be shut down without the force option. |
| 0x4F8 | 您無法存取此共用資料夾，因為您組織的安全性原則已封鎖未經驗證的來賓存取。這些原則可協助保護您的電腦，以防禦網路上不安全或惡意的裝置。 |
You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network. |
| 0x4F9 | 應用程式定義的回撥在呼叫時送出不正確的資料。 |
An application-defined callback gave invalid data when called. |
| 0x4FA | 群組原則架構應該在同步幕前原則重新整理中呼叫擴充。 |
The group policy framework should call the extension in the synchronous foreground policy refresh. |
| 0x4FB | 這個驅動程式已被防止載入 |
This driver has been blocked from loading |
| 0x4FC | 動態連結程式庫 (DLL) 參照了既不是 DLL 也不是程序的可執行檔的模組。 |
A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image. |
| 0x4FD | Windows 無法開啟這個程式，因為它已被停用。 |
Windows cannot open this program since it has been disabled. |
| 0x4FE | Windows 無法開啟這個程式，因為授權強制系統已被削弱或已毀損。 |
Windows cannot open this program because the license enforcement system has been tampered with or become corrupted. |
| 0x4FF | 交易還原失敗。 |
A transaction recover failed. |
| 0x500 | 目前的執行緒已轉換為 fiber。 |
The current thread has already been converted to a fiber. |
| 0x501 | 目前的執行緒已是轉換自 fiber。 |
The current thread has already been converted from a fiber. |
| 0x502 | 系統偵測到這個應用程式中堆疊為主緩衝區的滿溢，這個滿溢有可能讓心懷不軌的使用者取得這個電腦的控制。 |
The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application. |
| 0x503 | 呈現在其中一個參數中的資料超出功能函數可以運作。 |
Data present in one of the parameters is more than the function can operate on. |
| 0x504 | 企圖在偵錯物件上進行操作的嘗試失敗，因為正在刪除該物件。 |
An attempt to do an operation on a debug object failed because the object is in the process of being deleted. |
| 0x505 | 延遲載入 .dll，或於延遲載入的 .dll 中取得功能函數位址的嘗試失敗。 |
An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed. |
| 0x506 | %1 是一個 16 位元應用程式。您沒有許可可執行 16 位元應用程式。請向您的系統管理員查詢您的許可。 |
%1 is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator. |
| 0x507 | 沒有足夠的資訊可用來辨識失敗的原因。 |
Insufficient information exists to identify the cause of failure. |
| 0x508 | 傳遞到 C 執行階段函數的參數錯誤。 |
The parameter passed to a C runtime function is incorrect. |
| 0x509 | 作業發生超出有效的檔案資料長度。 |
The operation occurred beyond the valid data length of the file. |
| 0x50A | 因為相同處理程序中的一或多個服務具有不相容的服務 SID 類型設定，所以服務啟動失敗。具有限制服務 SID 類型的服務只能與其他具有限制 SID 類型的服務共存在相同的處理程序中。如果此服務的服務 SID 類型剛剛才完成設定，則必須重新啟動主控處理程序，才能夠啟動此服務。 |
The service start failed since one or more services in the same process have an incompatible service SID type setting. A service with restricted service SID type can only coexist in the same process with other services with a restricted SID type. If the service SID type for this service was just configured, the hosting process must be restarted in order to start this service. |
| 0x50B | 主控此裝置驅動程式的處理程序已終止。 |
The process hosting the driver for this device has been terminated. |
| 0x50C | 作業嘗試超過執行定義的限制。 |
An operation attempted to exceed an implementation-defined limit. |
| 0x50D | 目標處理程序或目標執行緒包含的處理程序是受保護的處理程序。 |
Either the target process, or the target thread's containing process, is a protected process. |
| 0x50E | 服務通知用戶端過度落後機器中目前的服務狀態。 |
The service notification client is lagging too far behind the current state of services in the machine. |
| 0x50F | 要求的檔案操作失敗，因為已超過儲存配額。若要釋出磁碟空間，請將檔案移動到其他位置或刪除不必要的檔案。如需詳細資訊，請連絡您的系統管理員。 |
The requested file operation failed because the storage quota was exceeded.To free up disk space, move files to a different location or delete unnecessary files. For more information, contact your system administrator. |
| 0x510 | 要求的檔案操作失敗，因為存放原則已封鎖該檔案類型。如需詳細資訊，請連絡您的系統管理員。 |
The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator. |
| 0x511 | 服務正常運作所需的權限不存在於此服務帳戶設定中。您可以使用 Microsoft Management Console (MMC) 的服務嵌入式管理單元 (services.msc) 及本機安全性設定 MMC 嵌入式管理單元 (secpol.msc) 來檢視服務設定及帳戶設定。 |
A privilege that the service requires to function properly does not exist in the service account configuration.You may use the Services Microsoft Management Console (MMC) snap-in (services.msc) and the Local Security Settings MMC snap-in (secpol.msc) to view the service configuration and the account configuration. |
| 0x512 | 涉及此操作的執行緒似乎沒有回應。 |
A thread involved in this operation appears to be unresponsive. |
| 0x513 | 指出可能無法將特定的安全性識別碼指派為物件的標籤。 |
Indicates a particular Security ID may not be assigned as the label of an object. |
| 0x514 | 並非所有參考到的特殊權限或群組都指定給呼叫者。 |
Not all privileges or groups referenced are assigned to the caller. |
| 0x515 | 帳戶名稱和安全性識別碼間的某些對應未完成。 |
Some mapping between account names and security IDs was not done. |
| 0x516 | 未特別設定系統配額限制給此帳戶。 |
No system quota limits are specifically set for this account. |
| 0x517 | 無法獲得任何加密金鑰。傳回通用的加密金鑰。 |
No encryption key is available. A well-known encryption key was returned. |
| 0x518 | 密碼太複雜，無法轉換成 LAN Manager 密碼。傳回的 LAN Manager 密碼是無效的字串。 |
The password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string. |
| 0x519 | 修正階層不明。 |
The revision level is unknown. |
| 0x51A | 標示兩個修正層級不相容。 |
Indicates two revision levels are incompatible. |
| 0x51B | 這個安全性識別碼不能被指派給這個物件的擁有者。 |
This security ID may not be assigned as the owner of this object. |
| 0x51C | 這個安全性識別碼不能被指派給物件的主要群組。 |
This security ID may not be assigned as the primary group of an object. |
| 0x51D | 嘗試用執行緒對模擬權杖進行操作，這個執行緒目前不是模擬用戶端。 |
An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client. |
| 0x51E | 群組可能未被停用。 |
The group may not be disabled. |
| 0x51F | 因為您的網域無法使用，所以您無法使用此認證登入。請確定裝置已連線到組織網路後，再試一次。如果您先前使用另一個認證登入此裝置，則可以使用該認證登入。 |
We can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again. If you previously signed in on this device with another credential, you can sign in with that credential. |
| 0x520 | 指定的登入工作階段不存在。可能已被終止。 |
A specified logon session does not exist. It may already have been terminated. |
| 0x521 | 指定的特殊權限不存在。 |
A specified privilege does not exist. |
| 0x522 | 用戶端沒有這項特殊權限。 |
A required privilege is not held by the client. |
| 0x523 | 提供的名稱並非適當的帳戶名稱形式。 |
The name provided is not a properly formed account name. |
| 0x524 | 指定的帳戶已存在。 |
The specified account already exists. |
| 0x525 | 指定的帳戶不存在。 |
The specified account does not exist. |
| 0x526 | 指定的群組已存在。 |
The specified group already exists. |
| 0x527 | 指定的群組不存在。 |
The specified group does not exist. |
| 0x528 | 指定的使用者帳戶已是指定群組的成員，或是因為群組包含成員所以無法刪除指定的群組。 |
Either the specified user account is already a member of the specified group, or the specified group cannot be deleted because it contains a member. |
| 0x529 | 指定的使用者帳戶不是指定群組帳戶的成員。 |
The specified user account is not a member of the specified group account. |
| 0x52A | 不允許此操作，因為它可能會造成系統管理員帳戶被停用、刪除或無法登入。 |
This operation is disallowed as it could result in an administration account being disabled, deleted or unable to logon. |
| 0x52B | 無法更新密碼。您提供的目前密碼值錯誤。 |
Unable to update the password. The value provided as the current password is incorrect. |
| 0x52C | 無法更新密碼。新密碼的值中包含不正確的字元。 |
Unable to update the password. The value provided for the new password contains values that are not allowed in passwords. |
| 0x52D | 無法更新密碼。因為提供的密碼值不符合網域要求的長度、複雜度，或歷程記錄。 |
Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain. |
| 0x52E | 使用者名稱或密碼不正確。 |
The user name or password is incorrect. |
| 0x52F | 帳戶限制導致這個使用者無法登入。例如: 不允許空的密碼、登入時間限制，或強制的原則限制。 |
Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced. |
| 0x530 | 您的帳戶設有時間限制，導致您現在無法登入。 |
Your account has time restrictions that keep you from signing in right now. |
| 0x531 | 不允許這個使用者登入到此電腦。 |
This user isn't allowed to sign in to this computer. |
| 0x532 | 此帳戶的密碼已到期。 |
The password for this account has expired. |
| 0x533 | 這個使用者無法登入，因為此帳戶目前已停用。 |
This user can't sign in because this account is currently disabled. |
| 0x534 | 帳戶名稱與安全性識別碼無法對應。 |
No mapping between account names and security IDs was done. |
| 0x535 | 一次要求過多的本機使用者識別碼 (LUIDs)。 |
Too many local user identifiers (LUIDs) were requested at one time. |
| 0x536 | 無可用的本機使用者識別碼 (LUIDs)。 |
No more local user identifiers (LUIDs) are available. |
| 0x537 | 安全性識別碼的子授權碼無法用在這項特殊的操作。 |
The subauthority part of a security ID is invalid for this particular use. |
| 0x538 | 存取控制清單 (ACL) 結構不正確。 |
The access control list (ACL) structure is invalid. |
| 0x539 | 安全性識別碼結構不正確。 |
The security ID structure is invalid. |
| 0x53A | 安全性描述元結構不正確。 |
The security descriptor structure is invalid. |
| 0x53C | 無法建立繼承的存取控制清單 (ACL) 或存取控制項目 (ACE)。 |
The inherited access control list (ACL) or access control entry (ACE) could not be built. |
| 0x53D | 伺服器目前已停用。 |
The server is currently disabled. |
| 0x53E | 伺服器目前已啟用。 |
The server is currently enabled. |
| 0x53F | 提供給識別元的授權值不正確。 |
The value provided was an invalid value for an identifier authority. |
| 0x540 | 無更多可用的記憶體以更新安全性資訊。 |
No more memory is available for security information updates. |
| 0x541 | 指定的屬性不正確，或與整個群組的屬性不相容。 |
The specified attributes are invalid, or incompatible with the attributes for the group as a whole. |
| 0x542 | 未提供所要求的模擬層，或所提供的模擬層不正確。 |
Either a required impersonation level was not provided, or the provided impersonation level is invalid. |
| 0x543 | 無法開啟匿名層級的安全性權杖。 |
Cannot open an anonymous level security token. |
| 0x544 | 要求的確認資訊類別不正確。 |
The validation information class requested was invalid. |
| 0x545 | 權杖的類型不適用於這項操作。 |
The type of the token is inappropriate for its attempted use. |
| 0x546 | 無法在沒有相關安全性的物件上執行安全性操作。 |
Unable to perform a security operation on an object that has no associated security. |
| 0x547 | 無法從網域控制站讀取設定資訊，可能是電腦無法使用，或是存取被拒絕。 |
Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. |
| 0x548 | 安全性帳戶管理員 (SAM) 或本機安全性授權 (LSA) 伺服器的安全性操作處於執行錯誤狀態。 |
The security account manager (SAM) or local security authority (LSA) server was in the wrong state to perform the security operation. |
| 0x549 | 網域處於錯誤的狀態，所以無法執行安全性操作。 |
The domain was in the wrong state to perform the security operation. |
| 0x54B | 指定的網域可能不存在或無法連線。 |
The specified domain either does not exist or could not be contacted. |
| 0x54C | 指定的網域已存在。 |
The specified domain already exists. |
| 0x54D | 企圖超出每個伺服器網域個數的限制。 |
An attempt was made to exceed the limit on the number of domains per server. |
| 0x54E | 無法完成請求的操作，因為磁碟上的異常媒體失敗或資料結構損毀。 |
Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk. |
| 0x54F | 發生內部錯誤。 |
An internal error occurred. |
| 0x550 | 存取遮罩中包含一般性的存取類型，這個類型應該已經對應到非一般性的類型。 |
Generic access types were contained in an access mask which should already be mapped to nongeneric types. |
| 0x551 | 安全性描述元的格式不正確 (絕對或自我相對的)。 |
A security descriptor is not in the right format (absolute or self-relative). |
| 0x552 | 這項要求動作只能用在登入程序。所呼叫的程序並未登錄為登入程序。 |
The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process. |
| 0x553 | 不能把正在使用中的識別碼拿來啟動新的登入工作階段。 |
Cannot start a new logon session with an ID that is already in use. |
| 0x554 | 指定的驗證封裝不明。 |
A specified authentication package is unknown. |
| 0x555 | 登入工作階段跟要求操作的狀態不一致。 |
The logon session is not in a state that is consistent with the requested operation. |
| 0x556 | 登入工作階段識別碼已在使用中。 |
The logon session ID is already in use. |
| 0x557 | 登入要求中的登入類型值不正確。 |
A logon request contained an invalid logon type value. |
| 0x558 | 除非已經讀取管道資料，否則無法模擬使用具名管道。 |
Unable to impersonate using a named pipe until data has been read from that pipe. |
| 0x559 | 登錄樹狀子目錄的交易狀態與要求的操作不相容。 |
The transaction state of a registry subtree is incompatible with the requested operation. |
| 0x55A | 內部安全性資料庫損毀。 |
An internal security database corruption has been encountered. |
| 0x55B | 無法在內建帳戶上執行此操作。 |
Cannot perform this operation on built-in accounts. |
| 0x55C | 無法在此內建特殊群組上執行此操作。 |
Cannot perform this operation on this built-in special group. |
| 0x55D | 無法在此內建特殊使用者上執行此操作。 |
Cannot perform this operation on this built-in special user. |
| 0x55E | 無法從群組中移除使用者，因為目前群組為使用者的主要群組。 |
The user cannot be removed from a group because the group is currently the user's primary group. |
| 0x55F | 權杖已用來作為主要權杖。 |
The token is already in use as a primary token. |
| 0x560 | 指定的本機群組不存在。 |
The specified local group does not exist. |
| 0x561 | 指定的帳戶名稱不是群組的成員。 |
The specified account name is not a member of the group. |
| 0x562 | 指定的帳戶名稱已是群組的成員。 |
The specified account name is already a member of the group. |
| 0x563 | 指定的本機群組已存在。 |
The specified local group already exists. |
| 0x564 | 登入失敗: 未授與使用者這個電腦所要求的登入類型。 |
Logon failure: the user has not been granted the requested logon type at this computer. |
| 0x565 | 已超過在單一系統中可存放的秘密最大數目。 |
The maximum number of secrets that may be stored in a single system has been exceeded. |
| 0x566 | 秘密的長度超過允許的最大長度。 |
The length of a secret exceeds the maximum length allowed. |
| 0x567 | 本機安全性授權資料庫內部有不一致。 |
The local security authority database contains an internal inconsistency. |
| 0x568 | 在嘗試登入時，使用者資訊安全內容累積過多的安全性識別碼。 |
During a logon attempt, the user's security context accumulated too many security IDs. |
| 0x56A | 變更使用者密碼時需要交互加密的密碼。 |
A cross-encrypted password is necessary to change a user password. |
| 0x56B | 無法將成員加入本機群組或從本機群組移除，因為成員不存在。 |
A member could not be added to or removed from the local group because the member does not exist. |
| 0x56C | 無法將新成員加入到本機群組中，因為成員的帳戶類型錯誤。 |
A new member could not be added to a local group because the member has the wrong account type. |
| 0x56D | 已指定過多的安全性識別碼。 |
Too many security IDs have been specified. |
| 0x56E | 變更這個使用者密碼時需要交互加密的密碼。 |
A cross-encrypted password is necessary to change this user password. |
| 0x56F | 發現有一個 ACL 包含無法繼承的元件。 |
Indicates an ACL contains no inheritable components. |
| 0x570 | 檔案或目錄損毀而且無法讀取。 |
The file or directory is corrupted and unreadable. |
| 0x571 | 磁碟結構損毀而且無法讀取。 |
The disk structure is corrupted and unreadable. |
| 0x572 | 沒有提供使用者工作階段金鑰給指定的登入工作階段。 |
There is no user session key for the specified logon session. |
| 0x573 | 正在存取的服務有連線數目的限制。這時候已經無法讓他人連線，原因是已經到了可容許的連線數目上限。 |
The service being accessed is licensed for a particular number of connections. No more connections can be made to the service at this time because there are already as many connections as the service can accept. |
| 0x574 | 目標帳戶名稱不正確。 |
The target account name is incorrect. |
| 0x575 | 相互驗證失敗。網域控制站的伺服器密碼已過期。 |
Mutual Authentication failed. The server's password is out of date at the domain controller. |
| 0x576 | 在用戶端及伺服器的時間及 (或) 日期不一致。 |
There is a time and/or date difference between the client and server. |
| 0x577 | 無法在目前的網域中執行這個操作。 |
This operation cannot be performed on the current domain. |
| 0x578 | 無效的視窗控制代碼。 |
Invalid window handle. |
| 0x579 | 無效的功能表控制代碼。 |
Invalid menu handle. |
| 0x57A | 無效的游標控制代碼。 |
Invalid cursor handle. |
| 0x57B | 無效的快速鍵對應表控制代碼。 |
Invalid accelerator table handle. |
| 0x57C | 無效的勾點控制代碼。 |
Invalid hook handle. |
| 0x57D | 無效的多重視窗位置結構控制代碼。 |
Invalid handle to a multiple-window position structure. |
| 0x57E | 無法建立最上層子視窗。 |
Cannot create a top-level child window. |
| 0x57F | 找不到視窗類別。 |
Cannot find window class. |
| 0x580 | 不正確的視窗; 它屬於其他執行緒。 |
Invalid window; it belongs to other thread. |
| 0x581 | 快速鍵已登錄。 |
Hot key is already registered. |
| 0x582 | 類別已存在。 |
Class already exists. |
| 0x583 | 類別不存在。 |
Class does not exist. |
| 0x584 | 類別仍有開啟的視窗。 |
Class still has open windows. |
| 0x585 | 無效的索引。 |
Invalid index. |
| 0x586 | 無效的圖示控制代碼。 |
Invalid icon handle. |
| 0x587 | 使用私有的 DIALOG 視窗文字。 |
Using private DIALOG window words. |
| 0x588 | 找不到清單方塊識別元。 |
The list box identifier was not found. |
| 0x589 | 找不到萬用字元。 |
No wildcards were found. |
| 0x58A | 執行緒不含開啟的剪貼簿。 |
Thread does not have a clipboard open. |
| 0x58B | 快速鍵未登錄。 |
Hot key is not registered. |
| 0x58C | 視窗不是有效的對話視窗。 |
The window is not a valid dialog window. |
| 0x58D | 找不到控制識別碼。 |
Control ID not found. |
| 0x58E | 因為沒有編輯控制項，所以下拉式清單方塊的訊息無效。 |
Invalid message for a combo box because it does not have an edit control. |
| 0x58F | 視窗不是下拉式清單方塊。 |
The window is not a combo box. |
| 0x590 | 高度必須小於 256。 |
Height must be less than 256. |
| 0x591 | 無效的裝置範圍 (DC) 控制代碼。 |
Invalid device context (DC) handle. |
| 0x592 | 無效的勾點程序類型。 |
Invalid hook procedure type. |
| 0x593 | 無效的勾點程序。 |
Invalid hook procedure. |
| 0x594 | 沒有模組控制代碼，無法設定非本機勾點。 |
Cannot set nonlocal hook without a module handle. |
| 0x595 | 這個勾點程序只可設定為全域性。 |
This hook procedure can only be set globally. |
| 0x596 | 日誌勾點程序已安裝。 |
The journal hook procedure is already installed. |
| 0x597 | 勾點程序尚未安裝。 |
The hook procedure is not installed. |
| 0x598 | 單一選取式的清單方塊的無效訊息。 |
Invalid message for single-selection list box. |
| 0x599 | LB_SETCOUNT 已傳給 non-lazy 清單方塊。 |
LB_SETCOUNT sent to non-lazy list box. |
| 0x59A | 此清單方塊不支援定位點。 |
This list box does not support tab stops. |
| 0x59B | 無法中止由另一個執行緒建立的物件。 |
Cannot destroy object created by another thread. |
| 0x59C | 子視窗不可有功能表。 |
Child windows cannot have menus. |
| 0x59D | 視窗沒有系統功能表。 |
The window does not have a system menu. |
| 0x59E | 無效的訊息方塊樣式。 |
Invalid message box style. |
| 0x59F | 無效的全系統 (SPI_*) 參數。 |
Invalid system-wide (SPI_*) parameter. |
| 0x5A0 | 已鎖定螢幕。 |
Screen already locked. |
| 0x5A1 | 多重視窗位置結構中視窗的所有控制代碼必須具有相同的父系。 |
All handles to windows in a multiple-window position structure must have the same parent. |
| 0x5A2 | 視窗不是子視窗。 |
The window is not a child window. |
| 0x5A3 | 無效的 GW_* 命令。 |
Invalid GW_* command. |
| 0x5A4 | 無效的執行緒識別元。 |
Invalid thread identifier. |
| 0x5A5 | 無法處理非多重文件介面 (MDI) 視窗中的訊息。 |
Cannot process a message from a window that is not a multiple document interface (MDI) window. |
| 0x5A6 | 快顯功能表已在使用中。 |
Popup menu already active. |
| 0x5A7 | 視窗沒有捲軸。 |
The window does not have scroll bars. |
| 0x5A8 | 捲軸範圍不可大於 MAXLONG。 |
Scroll bar range cannot be greater than MAXLONG. |
| 0x5A9 | 無法以指定的方式顯示或移除視窗。 |
Cannot show or remove the window in the way specified. |
| 0x5AA | 系統資源不足，無法完成要求的服務。 |
Insufficient system resources exist to complete the requested service. |
| 0x5AD | 配額不足，無法完成要求的服務。 |
Insufficient quota to complete the requested service. |
| 0x5AF | 分頁檔太小，無法完成操作。 |
The paging file is too small for this operation to complete. |
| 0x5B0 | 找不到某個功能表項目。 |
A menu item was not found. |
| 0x5B1 | 鍵盤配置控制代碼錯誤。 |
Invalid keyboard layout handle. |
| 0x5B2 | 不可有勾點類型。 |
Hook type not allowed. |
| 0x5B3 | 這個操作需要一個互動式視窗。 |
This operation requires an interactive window station. |
| 0x5B4 | 已逾時，因此傳回此操作。 |
This operation returned because the timeout period expired. |
| 0x5B5 | 不正確的監視器控制代碼。 |
Invalid monitor handle. |
| 0x5B6 | 大小引數不正確。 |
Incorrect size argument. |
| 0x5B7 | 因為符號連結的類型已停用，所以無法遵循符號連結。 |
The symbolic link cannot be followed because its type is disabled. |
| 0x5B8 | 此應用程式不支援符號連結上的目前作業。 |
This application does not support the current operation on symbolic links. |
| 0x5B9 | Windows 無法剖析要求的 XML 資料。 |
Windows was unable to parse the requested XML data. |
| 0x5BA | 處理 XML 數位簽章時發生錯誤。 |
An error was encountered while processing an XML digital signature. |
| 0x5BB | 這個應用程式必須重新啟動。 |
This application must be restarted. |
| 0x5BC | 呼叫者以錯誤的路由區間進行連線要求。 |
The caller made the connection request in the wrong routing compartment. |
| 0x5BD | 嘗試連線到遠端主機時發生 AuthIP 失敗。 |
There was an AuthIP failure when attempting to connect to the remote host. |
| 0x5BE | NVRAM 資源不足，無法完成要求的服務。可能需要重新開機。 |
Insufficient NVRAM resources exist to complete the requested service. A reboot might be required. |
| 0x5BF | 無法完成要求的作業，因為指定的處理程序不是 GUI 處理程序。 |
Unable to finish the requested operation because the specified process is not a GUI process. |
| 0x5DC | 事件記錄檔已損毀。 |
The event log file is corrupted. |
| 0x5DD | 無法開啟事件記錄檔，因此未啟動事件記錄服務。 |
No event log file could be opened, so the event logging service did not start. |
| 0x5DE | 事件記錄檔已滿。 |
The event log file is full. |
| 0x5DF | 讀取操作時，事件記錄檔已經變更。 |
The event log file has changed between read operations. |
| 0x5E0 | 指定的工作已經有指派給它的容器。 |
The specified Job already has a container assigned to it. |
| 0x5E1 | 指定的工作並沒有被指派容器。 |
The specified Job does not have a container assigned to it. |
| 0x60E | 指定的工作名稱無效。 |
The specified task name is invalid. |
| 0x60F | 指定的工作索引無效。 |
The specified task index is invalid. |
| 0x610 | 指定的執行緒已加入工作。 |
The specified thread is already joining a task. |
| 0x641 | 無法存取 Windows Installer 服務。如果 Windows Installer 未正確安裝，就可能發生。請連絡您的支援人員尋求協助。 |
The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance. |
| 0x642 | 使用者取消安裝。 |
User cancelled installation. |
| 0x643 | 安裝時發生嚴重錯誤。 |
Fatal error during installation. |
| 0x644 | 安裝已暫停，安裝不完整。 |
Installation suspended, incomplete. |
| 0x645 | 這個動作只有對目前已經安裝的產品才有效。 |
This action is only valid for products that are currently installed. |
| 0x646 | 功能識別碼並未登錄。 |
Feature ID not registered. |
| 0x647 | 元件識別碼並未登錄。 |
Component ID not registered. |
| 0x648 | 不明的內容。 |
Unknown property. |
| 0x649 | 控制代碼處於不正確的狀態。 |
Handle is in an invalid state. |
| 0x64A | 這個產品的設定資料已損毀。請連絡您的支援人員。 |
The configuration data for this product is corrupt. Contact your support personnel. |
| 0x64B | 沒有元件辨識符號。 |
Component qualifier not present. |
| 0x64C | 這個產品的安裝來源無法使用。請確認來源是否存在及您可以存取來源。 |
The installation source for this product is not available. Verify that the source exists and that you can access it. |
| 0x64D | Windows Installer 服務無法安裝這個安裝封裝。您必須安裝包含新版 Windows Installer 服務的 Windows Service Pack。 |
This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. |
| 0x64E | 產品被解除安裝。 |
Product is uninstalled. |
| 0x64F | SQL 查詢語法不正確或不受支援。 |
SQL query syntax invalid or unsupported. |
| 0x650 | 記錄欄位不存在。 |
Record field does not exist. |
| 0x651 | 裝置已移除。 |
The device has been removed. |
| 0x652 | 其他安裝正在進行。在進行這個安裝之前請先完成現在正在進行的安裝。 |
Another installation is already in progress. Complete that installation before proceeding with this install. |
| 0x653 | 無法開啟安裝封裝。請確認封裝是否存在及您是否有存取權，或連絡應用程式廠商確認這是一個正確的 Windows Installer 封裝。 |
This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. |
| 0x654 | 無法開啟安裝封裝。請連絡應用程式廠商確認這是一個正確的 Windows Installer 封裝。 |
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. |
| 0x655 | 啟動 Windows Installer 服務使用者介面時發生錯誤。請連絡您的支援人員。 |
There was an error starting the Windows Installer service user interface. Contact your support personnel. |
| 0x656 | 開啟安裝記錄檔時發生錯誤。請驗證指定的記錄檔位置已存在而且您可以寫入。 |
Error opening installation log file. Verify that the specified log file location exists and that you can write to it. |
| 0x657 | 您的系統不支援這個語言的安裝封裝。 |
The language of this installation package is not supported by your system. |
| 0x658 | 轉型套用錯誤。請確認指定的轉型路徑是否正確。 |
Error applying transforms. Verify that the specified transform paths are valid. |
| 0x659 | 安裝被系統原則拒絕。請連絡您的系統管理員。 |
This installation is forbidden by system policy. Contact your system administrator. |
| 0x65A | 無法執行功能。 |
Function could not be executed. |
| 0x65B | 執行功能時失敗。 |
Function failed during execution. |
| 0x65C | 指定的表格不正確或不明。 |
Invalid or unknown table specified. |
| 0x65D | 提供的資料類型錯誤。 |
Data supplied is of wrong type. |
| 0x65E | 不支援這類型的資料。 |
Data of this type is not supported. |
| 0x65F | Windows Installer 服務無法啟動。請連絡您的支援人員。 |
The Windows Installer service failed to start. Contact your support personnel. |
| 0x660 | 暫時資料夾存在於已滿或是無法存取的磁碟上。請在該磁碟上釋出可用空間，或確認您對暫時資料夾有寫入權限。 |
The Temp folder is on a drive that is full or is inaccessible. Free up space on the drive or verify that you have write permission on the Temp folder. |
| 0x661 | 安裝封裝不受這個處理器類型支援。請連絡您的產品供應商。 |
This installation package is not supported by this processor type. Contact your product vendor. |
| 0x662 | 元件未在這電腦上使用。 |
Component not used on this computer. |
| 0x663 | 無法開啟更新封裝。請確認更新封裝是否存在及您是否有存取權，或連絡應用程式廠商確認這是一個正確的 Windows Installer 更新封裝。 |
This update package could not be opened. Verify that the update package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer update package. |
| 0x664 | 無法開啟更新封裝。請連絡應用程式廠商確認這是一個正確的 Windows Installer 更新封裝。 |
This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package. |
| 0x665 | Windows Installer 服務無法處理這個更新封裝。您必須安裝包含新版 Windows Installer 服務的 Windows Service Pack。 |
This update package cannot be processed by the Windows Installer service. You must install a Windows service pack that contains a newer version of the Windows Installer service. |
| 0x666 | 已安裝這個產品的其他版本。無法繼續安裝這個版本。要設定或移除已存在的產品版本，請使用 [控制台] 的 [新增/移除程式]。 |
Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel. |
| 0x667 | 不正確的命令列引數。請參考 Windows Installer SDK 詳細命令列說明。 |
Invalid command line argument. Consult the Windows Installer SDK for detailed command line help. |
| 0x668 | 只有系統管理員才有權在終端機服務遠端工作階段中新增、移除、或設定伺服器軟體。如果您要安裝或設定軟體到伺服器上，請與您的網路系統管理員聯繫。 |
Only administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator. |
| 0x669 | 要求的操作已成功地完成。系統將重新啟動，變更才會生效。 |
The requested operation completed successfully. The system will be restarted so the changes can take effect. |
| 0x66A | Windows Installer 服務無法安裝升級，因為要升級的程式可能遺失或升級可能更新不同版本的程式。請檢查要升級的程式是否存在您的電腦，而且您有正確版本的升級。 |
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade. |
| 0x66B | 軟體限制原則未許可這個更新封裝。 |
The update package is not permitted by software restriction policy. |
| 0x66C | 軟體限制原則未許可一或多個自訂設定。 |
One or more customizations are not permitted by software restriction policy. |
| 0x66D | Windows Installer 不允許從遠端桌面連線來安裝。 |
The Windows Installer does not permit installation from a Remote Desktop Connection. |
| 0x66E | 不支援解除安裝更新封裝。 |
Uninstallation of the update package is not supported. |
| 0x66F | 尚未套用更新到此產品。 |
The update is not applied to this product. |
| 0x670 | 找不到更新組的正確順序。 |
No valid sequence could be found for the set of updates. |
| 0x671 | 原則不允許移除更新。 |
Update removal was disallowed by policy. |
| 0x672 | XML 更新資料不正確。 |
The XML update data is invalid. |
| 0x673 | Windows Installer 不允許更新管理的通告產品。在套用更新之前，必須最少要先安裝產品的一項功能。 |
Windows Installer does not permit updating of managed advertised products. At least one feature of the product must be installed before applying the update. |
| 0x674 | 在安全模式中無法存取 Windows Installer 服務。當您的電腦不是安全模式時請再試一次，或者您可使用系統還原讓您的機器回到之前的良好狀態。 |
The Windows Installer service is not accessible in Safe Mode. Please try again when your computer is not in Safe Mode or you can use System Restore to return your machine to a previous good state. |
| 0x675 | 發生立即失敗例外狀況。將不啟動例外處理常式，並將立即終止處理程序。 |
A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately. |
| 0x676 | 此版本的 Windows 不支援您嘗試執行的應用程式。 |
The app that you are trying to run is not supported on this version of Windows. |
| 0x677 | 因為程序禁止動態程式碼產生，已禁止操作。 |
The operation was blocked as the process prohibits dynamic code generation. |
| 0x678 | 物件不相同。 |
The objects are not identical. |
| 0x679 | 已封鎖指定映像檔的載入，因為它未啟用處理程序所需的功能: 控制流程防護。 |
The specified image file was blocked from loading because it does not enable a feature required by the process: Control Flow Guard. |
| 0x67A | 已封鎖指定映像檔的載入，因為它未啟用處理程序所需的功能: 傳回流程防護。 |
The specified image file was blocked from loading because it does not enable a feature required by the process: Return Flow Guard. |
| 0x67B | 「傳回流程防護」受限區域發生無效記憶體存取。 |
An invalid memory access occurred to a Return Flow Guard restricted region. |
| 0x67C | 執行緒內容已限為處理程序使用，因此無法更新。 |
The thread context could not be updated because this has been restricted for the process. |
| 0x67D | 嘗試存取的跨磁碟分割私密檔案/區段無效。 |
An invalid cross-partition private file/section access was attempted. |
| 0x6A4 | 字串繫結無效。 |
The string binding is invalid. |
| 0x6A5 | 連結控制代碼類型不正確。 |
The binding handle is not the correct type. |
| 0x6A6 | 連結控制代碼不正確。 |
The binding handle is invalid. |
| 0x6A7 | 不支援 RPC 通訊協定順序。 |
The RPC protocol sequence is not supported. |
| 0x6A8 | RPC 通訊協定順序不正確。 |
The RPC protocol sequence is invalid. |
| 0x6A9 | 字串通用唯一識別碼 (UUID) 無效。 |
The string universal unique identifier (UUID) is invalid. |
| 0x6AA | 端點格式不正確。 |
The endpoint format is invalid. |
| 0x6AB | 網路位址不正確。 |
The network address is invalid. |
| 0x6AC | 找不到端點。 |
No endpoint was found. |
| 0x6AD | 逾時值不正確。 |
The timeout value is invalid. |
| 0x6AE | 找不到物件通用唯一識別碼 (UUID)。 |
The object universal unique identifier (UUID) was not found. |
| 0x6AF | 物件通用唯一識別碼 (UUID) 已登錄。 |
The object universal unique identifier (UUID) has already been registered. |
| 0x6B0 | 類型通用唯一識別碼 (UUID) 已登錄。 |
The type universal unique identifier (UUID) has already been registered. |
| 0x6B1 | RPC 伺服器已在聽候。 |
The RPC server is already listening. |
| 0x6B2 | 未登錄任何通訊協定順序。 |
No protocol sequences have been registered. |
| 0x6B3 | RPC 伺服器不在聽候。 |
The RPC server is not listening. |
| 0x6B4 | 管理員類型不明。 |
The manager type is unknown. |
| 0x6B5 | 不明的介面。 |
The interface is unknown. |
| 0x6B6 | 沒有任何連結。 |
There are no bindings. |
| 0x6B7 | 無任何通訊協定順序。 |
There are no protocol sequences. |
| 0x6B8 | 無法建立端點。 |
The endpoint cannot be created. |
| 0x6B9 | 資源不足無法完成此操作。 |
Not enough resources are available to complete this operation. |
| 0x6BA | RPC 伺服器無法使用。 |
The RPC server is unavailable. |
| 0x6BB | RPC 伺服器忙線中，無法完成此操作。 |
The RPC server is too busy to complete this operation. |
| 0x6BC | 網路選項無效。 |
The network options are invalid. |
| 0x6BD | 這個執行緒沒有使用中的遠端程序呼叫。 |
There are no remote procedure calls active on this thread. |
| 0x6BE | 遠端程序呼叫失敗。 |
The remote procedure call failed. |
| 0x6BF | 遠端程序呼叫失敗且未執行。 |
The remote procedure call failed and did not execute. |
| 0x6C0 | 遠端程序呼叫 (RPC) 通訊協定發生錯誤。 |
A remote procedure call (RPC) protocol error occurred. |
| 0x6C1 | 拒絕存取 HTTP Proxy。 |
Access to the HTTP proxy is denied. |
| 0x6C2 | RPC 伺服器不支援傳輸語法。 |
The transfer syntax is not supported by the RPC server. |
| 0x6C4 | 不支援通用唯一識別碼 (UUID) 類型。 |
The universal unique identifier (UUID) type is not supported. |
| 0x6C5 | 標記不正確。 |
The tag is invalid. |
| 0x6C6 | 陣列界限不正確。 |
The array bounds are invalid. |
| 0x6C7 | 連結不包含項目名稱。 |
The binding does not contain an entry name. |
| 0x6C8 | 名稱語法不正確。 |
The name syntax is invalid. |
| 0x6C9 | 不支援名稱語法。 |
The name syntax is not supported. |
| 0x6CB | 沒有可用來建構通用唯一識別碼 (UUID) 的網路位址。 |
No network address is available to use to construct a universal unique identifier (UUID). |
| 0x6CC | 端點是一個複製項。 |
The endpoint is a duplicate. |
| 0x6CD | 驗證類型不明。 |
The authentication type is unknown. |
| 0x6CE | 呼叫的最大極限太小。 |
The maximum number of calls is too small. |
| 0x6CF | 字串太長。 |
The string is too long. |
| 0x6D0 | 找不到 RPC 通訊協定順序。 |
The RPC protocol sequence was not found. |
| 0x6D1 | 程序數字超出範圍。 |
The procedure number is out of range. |
| 0x6D2 | 連結不包含任何驗證資訊。 |
The binding does not contain any authentication information. |
| 0x6D3 | 驗證服務不明。 |
The authentication service is unknown. |
| 0x6D4 | 驗證層級不明。 |
The authentication level is unknown. |
| 0x6D5 | 資訊安全內容不正確。 |
The security context is invalid. |
| 0x6D6 | 不明的授權服務。 |
The authorization service is unknown. |
| 0x6D7 | 項目不正確。 |
The entry is invalid. |
| 0x6D8 | 伺服器端點無法執行操作。 |
The server endpoint cannot perform the operation. |
| 0x6D9 | 端點對應表中無更多可用的端點。 |
There are no more endpoints available from the endpoint mapper. |
| 0x6DA | 未匯出任何介面。 |
No interfaces have been exported. |
| 0x6DB | 項目名稱不完整。 |
The entry name is incomplete. |
| 0x6DC | 版本選項無效。 |
The version option is invalid. |
| 0x6DD | 不再有成員。 |
There are no more members. |
| 0x6DE | 沒有項目可供解除匯出。 |
There is nothing to unexport. |
| 0x6DF | 找不到介面。 |
The interface was not found. |
| 0x6E0 | 項目已存在。 |
The entry already exists. |
| 0x6E1 | 找不到項目。 |
The entry is not found. |
| 0x6E2 | 沒有可用的名稱服務。 |
The name service is unavailable. |
| 0x6E3 | 網路位址家族無效。 |
The network address family is invalid. |
| 0x6E4 | 不支援要求的操作。 |
The requested operation is not supported. |
| 0x6E5 | 無可用的資訊安全內容以允許模擬。 |
No security context is available to allow impersonation. |
| 0x6E6 | 遠端程序呼叫 (RPC) 發生內部錯誤。 |
An internal error occurred in a remote procedure call (RPC). |
| 0x6E7 | RPC 伺服器企圖以零除整數。 |
The RPC server attempted an integer division by zero. |
| 0x6E8 | RPC 伺服器中發生位址錯誤。 |
An addressing error occurred in the RPC server. |
| 0x6E9 | RPC 伺服器上的浮點操作引起以零除。 |
A floating-point operation at the RPC server caused a division by zero. |
| 0x6EA | RPC 伺服器上發生浮點反向溢位。 |
A floating-point underflow occurred at the RPC server. |
| 0x6EB | RPC 伺服器上發生浮點溢位。 |
A floating-point overflow occurred at the RPC server. |
| 0x6EC | 自動控制代碼連結的可用 RPC 伺服器清單已用完。 |
The list of RPC servers available for the binding of auto handles has been exhausted. |
| 0x6ED | 無法開啟字元轉譯表格檔案。 |
Unable to open the character translation table file. |
| 0x6EE | 包含字元轉譯表格的檔案少於 512 個位元組。 |
The file containing the character translation table has fewer than 512 bytes. |
| 0x6EF | 在遠端程序呼叫時，將空內容控制代碼從用戶端傳遞到主機。 |
A null context handle was passed from the client to the host during a remote procedure call. |
| 0x6F1 | 在遠端程序呼叫時，內容控制代碼變更。 |
The context handle changed during a remote procedure call. |
| 0x6F2 | 傳遞到遠端程序呼叫的連結控制代碼不相符。 |
The binding handles passed to a remote procedure call do not match. |
| 0x6F3 | 虛設常式無法獲得遠端程序呼叫控制代碼。 |
The stub is unable to get the remote procedure call handle. |
| 0x6F4 | NULL 參考指標被傳遞到虛設常式。 |
A null reference pointer was passed to the stub. |
| 0x6F5 | 列舉值超出範圍。 |
The enumeration value is out of range. |
| 0x6F6 | 位元組計數太小。 |
The byte count is too small. |
| 0x6F7 | 虛設常式接收到損壞的資料。 |
The stub received bad data. |
| 0x6F8 | 提供給請求操作的使用者緩衝區無效。 |
The supplied user buffer is not valid for the requested operation. |
| 0x6F9 | 磁碟媒體未被確認。可能未格式化。 |
The disk media is not recognized. It may not be formatted. |
| 0x6FA | 工作站沒有信任的秘密。 |
The workstation does not have a trust secret. |
| 0x6FB | 伺服器上的安全性資料庫沒有此工作站信任關係的電腦帳戶。 |
The security database on the server does not have a computer account for this workstation trust relationship. |
| 0x6FC | 主要網域和受信任網域間的信任關係失敗。 |
The trust relationship between the primary domain and the trusted domain failed. |
| 0x6FD | 此工作站和主要網域間的信任關係失敗。 |
The trust relationship between this workstation and the primary domain failed. |
| 0x6FE | 網路登入失敗。 |
The network logon failed. |
| 0x6FF | 執行緒的遠端程序呼叫已在進行中。 |
A remote procedure call is already in progress for this thread. |
| 0x700 | 企圖登入，但未啟動網路登入服務。 |
An attempt was made to logon, but the network logon service was not started. |
| 0x701 | 使用者帳戶已到期。 |
The user's account has expired. |
| 0x702 | 重新導向器正在使用中，無法被解除載入。 |
The redirector is in use and cannot be unloaded. |
| 0x703 | 指定的印表機驅動程式已安裝。 |
The specified printer driver is already installed. |
| 0x704 | 不明的指定連接埠。 |
The specified port is unknown. |
| 0x705 | 不明的印表機驅動程式。 |
The printer driver is unknown. |
| 0x706 | 不明的列印處理器。 |
The print processor is unknown. |
| 0x707 | 指定的分隔頁檔案無效。 |
The specified separator file is invalid. |
| 0x708 | 指定的優先權無效。 |
The specified priority is invalid. |
| 0x709 | 印表機名稱無效。 |
The printer name is invalid. |
| 0x70A | 印表機已存在。 |
The printer already exists. |
| 0x70B | 印表機命令無效。 |
The printer command is invalid. |
| 0x70C | 指定的資料類型無效。 |
The specified datatype is invalid. |
| 0x70D | 指定的環境無效。 |
The environment specified is invalid. |
| 0x70E | 不再有連結。 |
There are no more bindings. |
| 0x70F | 使用的帳戶是網域間的信任帳戶。請使用您的通用使用者帳戶或本機使用者帳戶來存取此伺服器。 |
The account used is an interdomain trust account. Use your global user account or local user account to access this server. |
| 0x710 | 使用的帳戶是電腦帳戶。請使用您的通用使用者帳戶或本機使用者帳戶來存取此伺服器。 |
The account used is a computer account. Use your global user account or local user account to access this server. |
| 0x711 | 使用的帳戶是伺服器信任帳戶。請使用您的通用使用者帳戶或本機使用者帳戶來存取此伺服器。 |
The account used is a server trust account. Use your global user account or local user account to access this server. |
| 0x712 | 指定網域的名稱或安全性識別碼 (SID) 與該網域的信任資訊不一致。 |
The name or security ID (SID) of the domain specified is inconsistent with the trust information for that domain. |
| 0x713 | 伺服器使用中且無法被解除載入。 |
The server is in use and cannot be unloaded. |
| 0x714 | 指定的映像檔不包含資源區段。 |
The specified image file did not contain a resource section. |
| 0x715 | 映像檔中找不到指定的資源類型。 |
The specified resource type cannot be found in the image file. |
| 0x716 | 映像檔中找不到指定的資源名稱。 |
The specified resource name cannot be found in the image file. |
| 0x717 | 映像檔中找不到指定的資源語言識別碼。 |
The specified resource language ID cannot be found in the image file. |
| 0x718 | 配額不足無法處理此命令。 |
Not enough quota is available to process this command. |
| 0x719 | 未登錄任何介面。 |
No interfaces have been registered. |
| 0x71A | 遠端程序呼叫已取消。 |
The remote procedure call was cancelled. |
| 0x71B | 連結控制代碼不包含所有需要的資訊。 |
The binding handle does not contain all required information. |
| 0x71C | 遠端程序呼叫發生通訊失敗。 |
A communications failure occurred during a remote procedure call. |
| 0x71D | 不支援請求的驗證層級。 |
The requested authentication level is not supported. |
| 0x71E | 未登錄任何主體名稱。 |
No principal name registered. |
| 0x71F | 指定的錯誤不是正確的 Windows RPC 錯誤碼。 |
The error specified is not a valid Windows RPC error code. |
| 0x720 | 已配置一個只在這部電腦有效的 UUID。 |
A UUID that is valid only on this computer has been allocated. |
| 0x721 | 發生安全性封裝特定錯誤。 |
A security package specific error occurred. |
| 0x722 | 執行緒未取消。 |
Thread is not canceled. |
| 0x723 | 不正確的編碼/解碼控制代碼操作。 |
Invalid operation on the encoding/decoding handle. |
| 0x724 | 序列化封裝的版本不相容。 |
Incompatible version of the serializing package. |
| 0x725 | RPC 虛設常式的版本不相容。 |
Incompatible version of the RPC stub. |
| 0x726 | RPC 管道物件不正確或已損毀。 |
The RPC pipe object is invalid or corrupted. |
| 0x727 | 在 RPC 管道物件上的操作嘗試不正確。 |
An invalid operation was attempted on an RPC pipe object. |
| 0x728 | 未支援的 RPC 管道版本。 |
Unsupported RPC pipe version. |
| 0x729 | HTTP Proxy 伺服器已拒絕連線，因為 Cookie 驗證失敗。 |
HTTP proxy server rejected the connection because the cookie authentication failed. |
| 0x72A | 已暫停 RPC 伺服器，無法針對此要求繼續執行。呼叫並未執行。 |
The RPC server is suspended, and could not be resumed for this request. The call did not execute. |
| 0x72B | RPC 呼叫包含太多控制代碼，無法在單一要求中傳送。 |
The RPC call contains too many handles to be transmitted in a single request. |
| 0x72C | RPC 呼叫包含的控制代碼與宣告的控制代碼類型不同。 |
The RPC call contains a handle that differs from the declared handle type. |
| 0x76A | 找不到群組成員。 |
The group member was not found. |
| 0x76B | 無法建立端點對應資料庫項目。 |
The endpoint mapper database entry could not be created. |
| 0x76C | 物件通用唯一識別碼 (UUID) 為零 (nil) UUID。 |
The object universal unique identifier (UUID) is the nil UUID. |
| 0x76D | 指定的時間無效。 |
The specified time is invalid. |
| 0x76E | 指定的表單名稱無效。 |
The specified form name is invalid. |
| 0x76F | 指定的表單大小不正確。 |
The specified form size is invalid. |
| 0x770 | 指定的印表機控制代碼正在等候中 |
The specified printer handle is already being waited on |
| 0x771 | 指定的印表機已被刪除。 |
The specified printer has been deleted. |
| 0x772 | 印表機狀態不正確。 |
The state of the printer is invalid. |
| 0x773 | 登入之前必須先變更使用者的密碼。 |
The user's password must be changed before signing in. |
| 0x774 | 找不到網域的網域控制站。 |
Could not find the domain controller for this domain. |
| 0x775 | 參考到的帳戶目前已鎖定，且可能無法登入。 |
The referenced account is currently locked out and may not be logged on to. |
| 0x776 | 找不到指定的物件輸出程式。 |
The object exporter specified was not found. |
| 0x777 | 找不到指定的物件。 |
The object specified was not found. |
| 0x778 | 找不到指定的物件解析程式。 |
The object resolver set specified was not found. |
| 0x779 | 在要求緩衝區中，仍有一些資料需要傳送。 |
Some data remains to be sent in the request buffer. |
| 0x77A | 不正確的非同步遠端程序呼叫控制代碼。 |
Invalid asynchronous remote procedure call handle. |
| 0x77B | 這個操作的非同步 RPC 呼叫控制代碼不正確。 |
Invalid asynchronous RPC call handle for this operation. |
| 0x77C | RPC 管道物件已經關閉。 |
The RPC pipe object has already been closed. |
| 0x77D | 在 RPC 呼叫完成之前全部的管道都已處理完成。 |
The RPC call completed before all pipes were processed. |
| 0x77E | 沒有其他來自 RPC 管道的可用資料。 |
No more data is available from the RPC pipe. |
| 0x77F | 這台電腦沒有可用的站台名稱。 |
No site name is available for this machine. |
| 0x780 | 系統無法存取該檔案。 |
The file cannot be accessed by the system. |
| 0x781 | 系統無法解析該檔案的名稱。 |
The name of the file cannot be resolved by the system. |
| 0x782 | 這項目不是預期中的類型。 |
The entry is not of the expected type. |
| 0x783 | 不是所有的物件 UUID 都可以匯出到指定的項目。 |
Not all object UUIDs could be exported to the specified entry. |
| 0x784 | 無法將介面匯出到指定的項目。 |
Interface could not be exported to the specified entry. |
| 0x785 | 無法新增指定的設定檔項目。 |
The specified profile entry could not be added. |
| 0x786 | 無法新增指定的設定檔元素。 |
The specified profile element could not be added. |
| 0x787 | 無法移除指定的設定檔元素。 |
The specified profile element could not be removed. |
| 0x788 | 無法新增群組元素。 |
The group element could not be added. |
| 0x789 | 無法移除群組元素。 |
The group element could not be removed. |
| 0x78A | 印表機驅動程式與電腦上已啟用的原則 (用來封鎖 NT 4.0 驅動程式) 不相容。 |
The printer driver is not compatible with a policy enabled on your computer that blocks NT 4.0 drivers. |
| 0x78B | 內容已經到期，不可再使用。 |
The context has expired and can no longer be used. |
| 0x78C | 已超過目前使用者委派的信任建立配額。 |
The current user's delegated trust creation quota has been exceeded. |
| 0x78D | 已超過委派的信任建立配額總額。 |
The total delegated trust creation quota has been exceeded. |
| 0x78E | 已超過目前使用者委派的信任刪除配額。 |
The current user's delegated trust deletion quota has been exceeded. |
| 0x78F | 您要登入的電腦受到驗證防火牆的保護。不允許指定的帳戶向該電腦驗證。 |
The computer you are signing into is protected by an authentication firewall. The specified account is not allowed to authenticate to the computer. |
| 0x790 | 遠端連線到列印多工緩衝處理器受到您電腦上設定的原則阻擋。 |
Remote connections to the Print Spooler are blocked by a policy set on your machine. |
| 0x791 | 驗證失敗，因為 NTLM 驗證已停用。 |
Authentication failed because NTLM authentication has been disabled. |
| 0x792 | 登入失敗: EAS 原則要求使用者必須先變更密碼，才能執行此作業。 |
Logon Failure: EAS policy requires that the user change their password before this operation can be performed. |
| 0x793 | 系統管理員已限制登入。若要登入，請確定您的裝置已連線到網際網路，並要求您的系統管理員先登入。 |
An administrator has restricted sign in. To sign in, make sure your device is connected to the Internet, and have your administrator sign in first. |
| 0x7D0 | 無效的像素格式。 |
The pixel format is invalid. |
| 0x7D1 | 指定的驅動程式無效。 |
The specified driver is invalid. |
| 0x7D2 | 視窗樣式或類別屬性對這項操作無效。 |
The window style or class attribute is invalid for this operation. |
| 0x7D3 | 未支援要求的中繼檔操作。 |
The requested metafile operation is not supported. |
| 0x7D4 | 未支援要求的格式變更操作。 |
The requested transformation operation is not supported. |
| 0x7D5 | 未支援要求的剪輯操作。 |
The requested clipping operation is not supported. |
| 0x7DA | 指定的色彩管理模組無效。 |
The specified color management module is invalid. |
| 0x7DB | 指定的色彩設定檔無效。 |
The specified color profile is invalid. |
| 0x7DC | 找不到指定的標記。 |
The specified tag was not found. |
| 0x7DD | 要求的標記不存在。 |
A required tag is not present. |
| 0x7DE | 指定的標記已存在。 |
The specified tag is already present. |
| 0x7DF | 指定的色彩設定檔未與指定的裝置相關。 |
The specified color profile is not associated with the specified device. |
| 0x7E0 | 找不到指定的色彩設定檔。 |
The specified color profile was not found. |
| 0x7E1 | 指定的色彩空間無效。 |
The specified color space is invalid. |
| 0x7E2 | 影像色彩管理尚未啟用。 |
Image Color Management is not enabled. |
| 0x7E3 | 刪除色彩轉換時發生錯誤。 |
There was an error while deleting the color transform. |
| 0x7E4 | 指定的色彩轉換無效。 |
The specified color transform is invalid. |
| 0x7E5 | 指定的轉換不符合點陣圖的色彩空間。 |
The specified transform does not match the bitmap's color space. |
| 0x7E6 | 設定檔中沒有指定的命名色彩索引。 |
The specified named color index is not present in the profile. |
| 0x7E7 | 指定的設定檔是供不同於指定裝置的裝置使用。 |
The specified profile is intended for a device of a different type than the specified device. |
| 0x83C | 網路連線成功，但必須要求使用者另外輸入一個密碼，不要用原始的指定密碼。 |
The network connection was made successfully, but the user had to be prompted for a password other than the one originally specified. |
| 0x83D | 網路連線已成功以預設認證建立。 |
The network connection was made successfully using default credentials. |
| 0x89A | 指定的使用者名稱無效。 |
The specified username is invalid. |
| 0x8CA | 這個網路連線不存在。 |
This network connection does not exist. |
| 0x961 | 這個網路連線有開啟的檔案或等待中的要求。 |
This network connection has files open or requests pending. |
| 0x962 | 使用中連線仍存在。 |
Active connections still exist. |
| 0x964 | 有程序正在使用裝置，無法切斷連線。 |
The device is in use by an active process and cannot be disconnected. |
| 0xBB8 | 指定了不明的列印監視器。 |
The specified print monitor is unknown. |
| 0xBB9 | 指定的印表機驅動程式目前正在使用中。 |
The specified printer driver is currently in use. |
| 0xBBA | 找不到多工緩衝檔。 |
The spool file was not found. |
| 0xBBB | 未發送 StartDocPrinter 呼叫。 |
A StartDocPrinter call was not issued. |
| 0xBBC | 未發送 AddJob 呼叫。 |
An AddJob call was not issued. |
| 0xBBD | 指定的列印處理器已經安裝。 |
The specified print processor has already been installed. |
| 0xBBE | 指定的列印監視器已經安裝。 |
The specified print monitor has already been installed. |
| 0xBBF | 指定的列印監視器沒有所需的功能。 |
The specified print monitor does not have the required functions. |
| 0xBC0 | 指定的列印監視器目前正在使用中。 |
The specified print monitor is currently in use. |
| 0xBC1 | 印表機的佇列中有工作時，不能執行所要求的操作。 |
The requested operation is not allowed when there are jobs queued to the printer. |
| 0xBC2 | 已成功執行所要求的操作。請重新開機，變更才能生效。 |
The requested operation is successful. Changes will not be effective until the system is rebooted. |
| 0xBC3 | 已成功執行所要求的操作。請重新啟動服務，變更才能生效。 |
The requested operation is successful. Changes will not be effective until the service is restarted. |
| 0xBC4 | 找不到印表機。 |
No printers were found. |
| 0xBC5 | 這個印表機驅動程式已知是不可靠的。 |
The printer driver is known to be unreliable. |
| 0xBC6 | 這個印表機驅動程式已知會傷害系統。 |
The printer driver is known to harm the system. |
| 0xBC7 | 指定的印表機驅動程式套件目前使用中。 |
The specified printer driver package is currently in use. |
| 0xBC8 | 找不到印表機驅動程式套件所需的核心驅動程式套件。 |
Unable to find a core driver package that is required by the printer driver package. |
| 0xBC9 | 要求的作業失敗。需要重新開機系統，才能復原所做的變更。 |
The requested operation failed. A system reboot is required to roll back changes made. |
| 0xBCA | 要求的作業失敗。已初始化系統重新開機，以復原所做的變更。 |
The requested operation failed. A system reboot has been initiated to roll back changes made. |
| 0xBCB | 系統上找不到指定的印表機驅動程式，因此需要進行下載。 |
The specified printer driver was not found on the system and needs to be downloaded. |
| 0xBCC | 無法列印要求的列印工作。列印系統更新要求必須重新提交工作。 |
The requested print job has failed to print. A print system update requires the job to be resubmitted. |
| 0xBCD | 印表機驅動程式不包含有效的資訊清單，或包含太多資訊清單。 |
The printer driver does not contain a valid manifest, or contains too many manifests. |
| 0xBCE | 無法共用指定的印表機。 |
The specified printer cannot be shared. |
| 0xBEA | 作業已暫停。 |
The operation was paused. |
| 0xF6E | 重新發出指定的操作做為快取的 IO 操作 |
Reissue the given operation as a cached IO operation |
| 0xFA0 | WINS 在處理命令時遭遇到錯誤。 |
WINS encountered an error while processing the command. |
| 0xFA1 | 本機的 WINS 不能刪除。 |
The local WINS cannot be deleted. |
| 0xFA2 | 檔案匯入操作失敗。 |
The importation from the file failed. |
| 0xFA3 | 備份失敗。您之前曾做過完整備份嗎? |
The backup failed. Was a full backup done before? |
| 0xFA4 | 備份失敗。請檢查資料庫備份目錄。 |
The backup failed. Check the directory to which you are backing the database. |
| 0xFA5 | WINS 資料庫中沒有這個名稱。 |
The name does not exist in the WINS database. |
| 0xFA6 | 不允許複寫未設定的協力電腦。 |
Replication with a nonconfigured partner is not allowed. |
| 0xFD2 | 不支援所提供內容資訊的版本。 |
The version of the supplied content information is not supported. |
| 0xFD3 | 所提供內容資訊的格式不正確。 |
The supplied content information is malformed. |
| 0xFD4 | 在本機或對等快取中找不到要求的資料。 |
The requested data cannot be found in local or peer caches. |
| 0xFD5 | 沒有可供使用的資料，或不再需要資料。 |
No more data is available or required. |
| 0xFD6 | 尚未初始化提供的物件。 |
The supplied object has not been initialized. |
| 0xFD7 | 已初始化提供的物件。 |
The supplied object has already been initialized. |
| 0xFD8 | 目前正在進行關機操作。 |
A shutdown operation is already in progress. |
| 0xFD9 | 提供的物件已失效。 |
The supplied object has already been invalidated. |
| 0xFDA | 元素已經存在，而且未予取代。 |
An element already exists and was not replaced. |
| 0xFDB | 要求的操作已完成，因此無法取消要求的操作。 |
Can not cancel the requested operation as it has already been completed. |
| 0xFDC | 已執行要求的操作，因此無法執行要求的操作。 |
Can not perform the reqested operation because it has already been carried out. |
| 0xFDD | 操作所存取的資料超出有效資料的範圍。 |
An operation accessed data beyond the bounds of valid data. |
| 0xFDE | 不支援要求的版本。 |
The requested version is not supported. |
| 0xFDF | 設定值不正確。 |
A configuration value is invalid. |
| 0xFE0 | 未授權 SKU。 |
The SKU is not licensed. |
| 0xFE1 | PeerDist 服務仍然正在初始化，稍後就可以使用。 |
PeerDist Service is still initializing and will be available shortly. |
| 0xFE2 | 因為最近的錯誤，將暫時封鎖與一或多部電腦的通訊。 |
Communication with one or more computers will be temporarily blocked due to recent errors. |
| 0x1004 | DHCP 用戶端取得一個 IP 位址，但這個位址已經在網路中使用。本機介面將被停用，直到 DHCP 用戶端取得新位址。 |
The DHCP client has obtained an IP address that is already in use on the network. The local interface will be disabled until the DHCP client can obtain a new address. |
| 0x1068 | 無法辨識傳來的 guid 是否為有效的 WMI 資料提供者。 |
The GUID passed was not recognized as valid by a WMI data provider. |
| 0x1069 | 無法辨識傳來的例項名稱是否為有效的 WMI 資料提供者。 |
The instance name passed was not recognized as valid by a WMI data provider. |
| 0x106A | 無法辨識傳來的資料項目識別碼是否為有效的 WMI 資料提供者。 |
The data item ID passed was not recognized as valid by a WMI data provider. |
| 0x106B | 無法完成 WMI 要求，應該重試一次。 |
The WMI request could not be completed and should be retried. |
| 0x106C | 找不到 WMI 資料提供者。 |
The WMI data provider could not be located. |
| 0x106D | WMI 資料提供者參照到一個未登錄的例項組。 |
The WMI data provider references an instance set that has not been registered. |
| 0x106E | WMI 資料區塊或事件通知已啟用。 |
The WMI data block or event notification has already been enabled. |
| 0x106F | WMI 資料區塊已經無法使用。 |
The WMI data block is no longer available. |
| 0x1070 | WMI 資料服務無法使用。 |
The WMI data service is not available. |
| 0x1071 | WMI 資料提供者無法完成要求。 |
The WMI data provider failed to carry out the request. |
| 0x1072 | WMI MOF 資訊不正確。 |
The WMI MOF information is not valid. |
| 0x1073 | WMI 登錄資訊不正確。 |
The WMI registration information is not valid. |
| 0x1074 | WMI 資料區塊或事件通知已停用。 |
The WMI data block or event notification has already been disabled. |
| 0x1075 | WMI 資料項目或資料區塊是唯讀屬性。 |
The WMI data item or data block is read only. |
| 0x1076 | 無法變更 WMI 資料項目或資料區塊。 |
The WMI data item or data block could not be changed. |
| 0x109A | 此作業只有在應用程式容器的內容中才有效。 |
This operation is only valid in the context of an app container. |
| 0x109B | 此應用程式只能在應用程式容器的內容中執行。 |
This application can only run in the context of an app container. |
| 0x109C | 在應用程式容器的內容中不支援此功能。 |
This functionality is not supported in the context of an app container. |
| 0x109D | 提供的 SID 長度不是有效的應用程式容器 SID 長度。 |
The length of the SID supplied is not a valid length for app container SIDs. |
| 0x10CC | 媒體識別元不是正確的媒體。 |
The media identifier does not represent a valid medium. |
| 0x10CD | 程式庫識別元不是正確的程式庫。 |
The library identifier does not represent a valid library. |
| 0x10CE | 媒體集區識別元不是正確的媒體集區。 |
The media pool identifier does not represent a valid media pool. |
| 0x10CF | 磁碟機和媒體不相容或位於不同的程式庫。 |
The drive and medium are not compatible or exist in different libraries. |
| 0x10D0 | 媒體目前位在離線程式庫中，您必須在連線時執行這個操作。 |
The medium currently exists in an offline library and must be online to perform this operation. |
| 0x10D1 | 操作無法在離線程式庫中執行。 |
The operation cannot be performed on an offline library. |
| 0x10D2 | 程式庫、磁碟機或媒體集區是空的。 |
The library, drive, or media pool is empty. |
| 0x10D3 | 程式庫、磁碟或媒體集區必須是空的，才能執行這個操作。 |
The library, drive, or media pool must be empty to perform this operation. |
| 0x10D4 | 在這個媒體集區或程式庫中目前沒有可用的媒體。 |
No media is currently available in this media pool or library. |
| 0x10D5 | 這個操作所必需的資源已停用。 |
A resource required for this operation is disabled. |
| 0x10D6 | 媒體識別元不是正確的清除器。 |
The media identifier does not represent a valid cleaner. |
| 0x10D7 | 無法清除磁碟機或不支援清除。 |
The drive cannot be cleaned or does not support cleaning. |
| 0x10D8 | 物件識別元不是一個正確物件。 |
The object identifier does not represent a valid object. |
| 0x10D9 | 無法讀取或寫入資料庫。 |
Unable to read from or write to the database. |
| 0x10DA | 資料庫已滿。 |
The database is full. |
| 0x10DB | 媒體與裝置或媒體集區不相容。 |
The medium is not compatible with the device or media pool. |
| 0x10DC | 這個操作必需的資源不存在。 |
The resource required for this operation does not exist. |
| 0x10DD | 操作識別元不正確。 |
The operation identifier is not valid. |
| 0x10DE | 媒體未架設或尚未就緒，所以無法使用。 |
The media is not mounted or ready for use. |
| 0x10DF | 裝置尚未就緒。 |
The device is not ready for use. |
| 0x10E0 | 操作員或系統管理員已拒絕此要求。 |
The operator or administrator has refused the request. |
| 0x10E1 | 磁碟機識別元不是正確的磁碟機。 |
The drive identifier does not represent a valid drive. |
| 0x10E2 | 程式庫已滿，沒有可使用的插槽。 |
Library is full. No slot is available for use. |
| 0x10E3 | 傳輸無法存取媒體。 |
The transport cannot access the medium. |
| 0x10E4 | 無法將媒體載入磁碟機。 |
Unable to load the medium into the drive. |
| 0x10E5 | 無法抓取磁碟機狀態。 |
Unable to retrieve the drive status. |
| 0x10E6 | 無法抓取插槽狀態。 |
Unable to retrieve the slot status. |
| 0x10E7 | 無法抓取媒體傳輸狀態。 |
Unable to retrieve status about the transport. |
| 0x10E8 | 無法使用這個傳輸，因為它已在使用中。 |
Cannot use the transport because it is already in use. |
| 0x10E9 | 無法開啟或關閉插入/退出連接埠。 |
Unable to open or close the inject/eject port. |
| 0x10EA | 無法退出媒體，因為它在磁碟機內。 |
Unable to eject the medium because it is in a drive. |
| 0x10EB | 已經保留一個清除器插槽。 |
A cleaner slot is already reserved. |
| 0x10EC | 並未保留清除器插槽。 |
A cleaner slot is not reserved. |
| 0x10ED | 清除器卡匣已經執行最大次數的磁碟清除工作。 |
The cleaner cartridge has performed the maximum number of drive cleanings. |
| 0x10EE | 意外的媒體上識別元。 |
Unexpected on-medium identifier. |
| 0x10EF | 無法刪除這個群組或資源中最後剩下的項目。 |
The last remaining item in this group or resource cannot be deleted. |
| 0x10F0 | 提供的訊息超過這個參數所允許的最大值。 |
The message provided exceeds the maximum size allowed for this parameter. |
| 0x10F1 | 磁碟區包含系統檔案或分頁檔。 |
The volume contains system or paging files. |
| 0x10F2 | 無法從這個媒體櫃移除此媒體類型，因為媒體櫃中至少有一個磁碟機表示它能支援此媒體類型。 |
The media type cannot be removed from this library since at least one drive in the library reports it can support this media type. |
| 0x10F3 | 這個離線媒體無法安裝在此系統上，因為沒有可以使用的已啟用磁碟機。 |
This offline media cannot be mounted on this system since no enabled drives are present which can be used. |
| 0x10F4 | 清潔卡匣出現在磁帶媒體櫃。 |
A cleaner cartridge is present in the tape library. |
| 0x10F5 | 無法使用這個插入/退出連接埠，因為它不是空的。 |
Cannot use the inject/eject port because it is not empty. |
| 0x10FE | 此檔案目前無法在此電腦上使用。 |
This file is currently not available for use on this computer. |
| 0x10FF | 遠端存放服務此時無法操作。 |
The remote storage service is not operational at this time. |
| 0x1100 | 遠端存放服務遇到媒體錯誤。 |
The remote storage service encountered a media error. |
| 0x1126 | 檔案或目錄不是重新分析點。 |
The file or directory is not a reparse point. |
| 0x1127 | 無法設定重新分析點的屬性，因為它和另一個現存屬性互相衝突。 |
The reparse point attribute cannot be set because it conflicts with an existing attribute. |
| 0x1128 | 重新分析點緩衝區中的資料不正確。 |
The data present in the reparse point buffer is invalid. |
| 0x1129 | 重新分析點緩衝區的標記不正確。 |
The tag present in the reparse point buffer is invalid. |
| 0x112A | 要求中所指定的標記與重新分析點上的標記不符。 |
There is a mismatch between the tag specified in the request and the tag present in the reparse point. |
| 0x112B | 物件管理員在抓取物件時發現重新分析點。 |
The object manager encountered a reparse point while retrieving an object. |
| 0x1130 | 找不到快速快取資料。 |
Fast Cache data not found. |
| 0x1131 | 快速快取資料已到期。 |
Fast Cache data expired. |
| 0x1132 | 快速快取資料損毀。 |
Fast Cache data corrupt. |
| 0x1133 | 快速快取資料已超出其大小上限，因此無法更新。 |
Fast Cache data has exceeded its max size and cannot be updated. |
| 0x1134 | 快速快取已重設授權狀態，因此需要重新開機才能更新。 |
Fast Cache has been ReArmed and requires a reboot until it can be updated. |
| 0x1144 | 安全開機偵測到已嘗試復原保護的資料。 |
Secure Boot detected that rollback of protected data has been attempted. |
| 0x1145 | 值受安全開機原則保護，因此無法修改或刪除。 |
The value is protected by Secure Boot policy and cannot be modified or deleted. |
| 0x1146 | 安全開機原則無效。 |
The Secure Boot policy is invalid. |
| 0x1147 | 新安全開機原則的更新清單中未包含目前的發行者。 |
A new Secure Boot policy did not contain the current publisher on its update list. |
| 0x1148 | 安全開機原則未簽署，或者是由非信任的簽署人所簽署。 |
The Secure Boot policy is either not signed or is signed by a non-trusted signer. |
| 0x1149 | 此電腦未啟用安全開機。 |
Secure Boot is not enabled on this machine. |
| 0x114A | 安全開機需要某些檔案與驅動程式未被其他檔案或驅動程式取代。 |
Secure Boot requires that certain files and drivers are not replaced by other files or drivers. |
| 0x114B | 此電腦上的安全開機增補原則檔案未獲授權。 |
The Secure Boot Supplemental Policy file was not authorized on this machine. |
| 0x114C | 無法識別此裝置上的「增補原則」。 |
The Supplemntal Policy is not recognized on this device. |
| 0x114D | 在安全開機原則中找不到 Antirollback 版本。 |
The Antirollback version was not found in the Secure Boot Policy. |
| 0x114E | 在安全開機原則中指定的平台識別碼不符合此裝置上的平台識別碼。 |
The Platform ID specified in the Secure Boot policy does not match the Platform ID on this device. |
| 0x114F | 安全開機原則檔案具有比此裝置舊的 Antirollback 版本。 |
The Secure Boot policy file has an older Antirollback Version than this device. |
| 0x1150 | 安全開機原則檔案不符合已升級的舊版原則。 |
The Secure Boot policy file does not match the upgraded legacy policy. |
| 0x1151 | 「安全開機」原則檔案為必要項目，但找不到該檔案。 |
The Secure Boot policy file is required but could not be found. |
| 0x1152 | 增補「安全開機」原則檔案無法載入為基礎「安全開機」原則。 |
Supplemental Secure Boot policy file can not be loaded as a base Secure Boot policy. |
| 0x1153 | 基礎「安全開機」原則檔案無法載入為增補「安全開機」原則。 |
Base Secure Boot policy file can not be loaded as a Supplemental Secure Boot policy. |
| 0x1158 | 篩選器不支援複製卸載讀取操作。 |
The copy offload read operation is not supported by a filter. |
| 0x1159 | 篩選器不支援複製卸載寫入操作。 |
The copy offload write operation is not supported by a filter. |
| 0x115A | 檔案不支援複製卸載讀取操作。 |
The copy offload read operation is not supported for the file. |
| 0x115B | 檔案不支援複製卸載寫入操作。 |
The copy offload write operation is not supported for the file. |
| 0x115C | 這個檔案目前與不同的串流識別碼相關聯。 |
This file is currently associated with a different stream id. |
| 0x1194 | 單一例項存放在這個磁碟區上無法使用。 |
Single Instance Storage is not available on this volume. |
| 0x11C6 | 「系統完整性」偵測到已嘗試回復原則。 |
System Integrity detected that policy rollback has been attempted. |
| 0x11C7 | 您的組織使用 Device Guard 來封鎖此 App。如需詳細資訊，請連絡您的支援人員。 |
Your organization used Device Guard to block this app. Contact your support person for more info. |
| 0x11C8 | 「系統完整性」原則無效。 |
The System Integrity policy is invalid. |
| 0x11C9 | 「系統完整性」原則未經簽署或不是由信任的簽署人簽署。 |
The System Integrity policy is either not signed or is signed by a non-trusted signer. |
| 0x11D0 | 虛擬安全模式 (VSM) 未初始化。Hypervisor 或 VSM 可能不存在或未啟用。 |
Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. |
| 0x11D1 | Hypervisor 並沒有在保護 DMA，因為 BIOS 中的 IOMMU 不存在或未啟用。 |
The hypervisor is not protecting DMA because an IOMMU is not present or not enabled in the BIOS. |
| 0x11DA | 此電腦上的平台資訊清單檔案未獲授權。 |
The Platform Manifest file was not authorized on this machine. |
| 0x11DB | 平台資訊清單檔案無效。 |
The Platform Manifest file was not valid. |
| 0x11DC | 此平台上的該檔案未獲授權，因為在平台資訊清單中找不到項目。 |
The file is not authorized on this platform because an entry was not found in the Platform Manifest. |
| 0x11DD | 此平台上的該類別目錄未獲授權，因為在平台資訊清單中找不到項目。 |
The catalog is not authorized on this platform because an entry was not found in the Platform Manifest. |
| 0x11DE | 此平台上的該檔案未獲授權，因為在內嵌簽章中找不到二進位識別碼。 |
The file is not authorized on this platform because a Binary ID was not found in the embedded signature. |
| 0x11DF | 此系統上沒有作用中平台資訊清單存在。 |
No active Platform Manifest exists on this system. |
| 0x11E0 | 平台資訊清單檔案未正確簽署。 |
The Platform Manifest file was not properly signed. |
| 0x1389 | 因為其他資源依賴這個資源，所以作業無法完成。 |
The operation cannot be completed because other resources are dependent on this resource. |
| 0x138A | 找不到叢集資源相依性。 |
The cluster resource dependency cannot be found. |
| 0x138B | 叢集資源無法相依到指定的資源，因為它已經在依存狀態。 |
The cluster resource cannot be made dependent on the specified resource because it is already dependent. |
| 0x138C | 叢集資源並未連線。 |
The cluster resource is not online. |
| 0x138D | 叢集節點無法用來進行這個操作。 |
A cluster node is not available for this operation. |
| 0x138E | 叢集資源無法使用。 |
The cluster resource is not available. |
| 0x138F | 找不到叢集資源。 |
The cluster resource could not be found. |
| 0x1390 | 叢集正在關機。 |
The cluster is being shut down. |
| 0x1391 | 叢集節點必須先關閉，或變成最後一個節點之後，才能將它從叢集中撤出。 |
A cluster node cannot be evicted from the cluster unless the node is down or it is the last node. |
| 0x1392 | 物件已經存在。 |
The object already exists. |
| 0x1393 | 物件已經在清單中。 |
The object is already in the list. |
| 0x1394 | 叢集群組無法用來執行新要求。 |
The cluster group is not available for any new requests. |
| 0x1395 | 找不到叢集群組。 |
The cluster group could not be found. |
| 0x1396 | 操作無法完成，因為叢集群組未連線。 |
The operation could not be completed because the cluster group is not online. |
| 0x1397 | 因為指定的叢集節點不是資源的擁有者，或節點不是資源的可能擁有者，所以操作失敗。 |
The operation failed because either the specified cluster node is not the owner of the resource, or the node is not a possible owner of the resource. |
| 0x1398 | 因為指定的叢集節點不是群組的擁有者，或節點不是群組的可能擁有者，所以操作失敗。 |
The operation failed because either the specified cluster node is not the owner of the group, or the node is not a possible owner of the group. |
| 0x1399 | 叢集資源無法建立在指定的資源監視器上。 |
The cluster resource could not be created in the specified resource monitor. |
| 0x139A | 無法用資源監視器來將叢集資源連線。 |
The cluster resource could not be brought online by the resource monitor. |
| 0x139B | 操作無法完成，因為叢集資源是連線狀態。 |
The operation could not be completed because the cluster resource is online. |
| 0x139C | 叢集資源無法被刪除或離線，因為它是仲裁資源。 |
The cluster resource could not be deleted or brought offline because it is the quorum resource. |
| 0x139D | 叢集無法將指定的資源建立成仲裁資源，因為它沒有成為仲裁資源的能力。 |
The cluster could not make the specified resource a quorum resource because it is not capable of being a quorum resource. |
| 0x139E | 叢集軟體正在關機。 |
The cluster software is shutting down. |
| 0x139F | 群組或資源不是處在執行要求操作的正確狀態。 |
The group or resource is not in the correct state to perform the requested operation. |
| 0x13A0 | 內容已存放，但要到下次資源連線時，變更才會全部生效。 |
The properties were stored but not all changes will take effect until the next time the resource is brought online. |
| 0x13A1 | 叢集無法使指定的資源成為仲裁資源，因為它不屬於共用存放類別。 |
The cluster could not make the specified resource a quorum resource because it does not belong to a shared storage class. |
| 0x13A2 | 無法刪除叢集資源，因為它是核心資源。 |
The cluster resource could not be deleted since it is a core resource. |
| 0x13A3 | 仲裁資源無法連線。 |
The quorum resource failed to come online. |
| 0x13A4 | 仲裁記錄檔無法成功建立或掛接。 |
The quorum log could not be created or mounted successfully. |
| 0x13A5 | 叢集記錄檔已損毀。 |
The cluster log is corrupt. |
| 0x13A6 | 記錄無法寫入叢集記錄檔，因為它的大小超過上限。 |
The record could not be written to the cluster log since it exceeds the maximum size. |
| 0x13A7 | 叢集記錄檔超過它的大小上限。 |
The cluster log exceeds its maximum size. |
| 0x13A8 | 叢集記錄檔中找不到檢查點記錄。 |
No checkpoint record was found in the cluster log. |
| 0x13A9 | 記錄必需的最小磁碟空間已無法使用。 |
The minimum required disk space needed for logging is not available. |
| 0x13AA | 由於資源為另一使用中節點所擁有，叢集節點無法控制仲裁資源。 |
The cluster node failed to take control of the quorum resource because the resource is owned by another active node. |
| 0x13AB | 這個操作沒有叢集網路可用。 |
A cluster network is not available for this operation. |
| 0x13AD | 所有叢集節點都需執行才能進行這項操作。 |
All cluster nodes must be running to perform this operation. |
| 0x13AE | 某個叢集資源失敗了。 |
A cluster resource failed. |
| 0x13AF | 這個叢集節點不正確。 |
The cluster node is not valid. |
| 0x13B0 | 這個叢集節點已經存在了。 |
The cluster node already exists. |
| 0x13B1 | 某個節點正在加入叢集中。 |
A node is in the process of joining the cluster. |
| 0x13B2 | 這個叢集節點找不到。 |
The cluster node was not found. |
| 0x13B3 | 找不到這個叢集的本機節點資訊。 |
The cluster local node information was not found. |
| 0x13B4 | 這個叢集網路已經存在了。 |
The cluster network already exists. |
| 0x13B5 | 找不到這個叢集網路。 |
The cluster network was not found. |
| 0x13B6 | 這個叢集網路介面已經存在了。 |
The cluster network interface already exists. |
| 0x13B7 | 找不到這個叢集網路介面。 |
The cluster network interface was not found. |
| 0x13B8 | 這個叢集要求不適用於這個物件。 |
The cluster request is not valid for this object. |
| 0x13B9 | 這個叢集網路提供者不正確。 |
The cluster network provider is not valid. |
| 0x13BA | 叢集節點已關閉。 |
The cluster node is down. |
| 0x13BB | 無法連線到叢集節點。 |
The cluster node is not reachable. |
| 0x13BC | 這個叢集節點不是叢集的成員之一。 |
The cluster node is not a member of the cluster. |
| 0x13BD | 目前沒有叢集加入操作在進行中。 |
A cluster join operation is not in progress. |
| 0x13BE | 這個叢集網路不正確。 |
The cluster network is not valid. |
| 0x13C0 | 這個叢集節點已啟動。 |
The cluster node is up. |
| 0x13C1 | 這個叢集 IP 位址已經在使用中。 |
The cluster IP address is already in use. |
| 0x13C2 | 這個叢集節點並未暫停。 |
The cluster node is not paused. |
| 0x13C3 | 沒有可用的叢集資訊安全內容。 |
No cluster security context is available. |
| 0x13C4 | 這個叢集網路不是設定為內部叢集通訊之用。 |
The cluster network is not configured for internal cluster communication. |
| 0x13C5 | 這個叢集節點已經啟用了。 |
The cluster node is already up. |
| 0x13C7 | 這個叢集網路已經連線了。 |
The cluster network is already online. |
| 0x13C8 | 這個叢集網路介面已經離線了。 |
The cluster network is already offline. |
| 0x13C9 | 這個叢集節點已是叢集的成員之一。 |
The cluster node is already a member of the cluster. |
| 0x13CA | 這個叢集網路是為兩個或以上使用中叢集節點內部叢集通訊而設定的唯一網路。這個內部通訊能力不可從網路上移除。 |
The cluster network is the only one configured for internal cluster communication between two or more active cluster nodes. The internal communication capability cannot be removed from the network. |
| 0x13CB | 有些叢集資源必須依賴網路提供服務到用戶端。用戶端存取能力不可從網路上移除。 |
One or more cluster resources depend on the network to provide service to clients. The client access capability cannot be removed from the network. |
| 0x13CC | 此操作目前無法在包含仲裁資源的叢集群組上執行。 |
This operation cannot currently be performed on the cluster group containing the quorum resource. |
| 0x13CD | 叢集仲裁資源不容許有任何依存。 |
The cluster quorum resource is not allowed to have any dependencies. |
| 0x13CE | 這個叢集節點已經暫停。 |
The cluster node is paused. |
| 0x13CF | 叢集資源無法連線。擁有者節點無法執行這個資源。 |
The cluster resource cannot be brought online. The owner node cannot run this resource. |
| 0x13D0 | 叢集節點尚未準備好執行要求的操作。 |
The cluster node is not ready to perform the requested operation. |
| 0x13D1 | 叢集節點正在關閉中。 |
The cluster node is shutting down. |
| 0x13D2 | 叢集結合操作已中止。 |
The cluster join operation was aborted. |
| 0x13D3 | 節點無法加入叢集，因為要加入的節點與叢集中其他節點的作業系統版本不相容。若要取得有關叢集作業系統版本的詳細資訊，請執行「驗證設定精靈」或 Test-Cluster Windows PowerShell Cmdlet。 |
The node failed to join the cluster because the joining node and other nodes in the cluster have incompatible operating system versions. To get more information about operating system versions of the cluster, run the Validate a Configuration Wizard or the Test-Cluster Windows PowerShell cmdlet. |
| 0x13D4 | 這個資源無法建立，因為叢集已經達到能夠監視資源數目的上限。 |
This resource cannot be created because the cluster has reached the limit on the number of resources it can monitor. |
| 0x13D5 | 在叢集結合或建立操作時，系統設定發生變更。結合或建立操作因而中止。 |
The system configuration changed during the cluster join or form operation. The join or form operation was aborted. |
| 0x13D6 | 找不到指定的資源類型。 |
The specified resource type was not found. |
| 0x13D7 | 指定的節點不支援這個類型的資源。可能是因為版本不同或節點上沒有資源 DLL 檔。 |
The specified node does not support a resource of this type. This may be due to version inconsistencies or due to the absence of the resource DLL on this node. |
| 0x13D8 | 指定的資源名稱不受這個資源 DLL 檔支援。可能是因為提供到資源 DLL 的不良 (或變更的) 名稱。 |
The specified resource name is not supported by this resource DLL. This may be due to a bad (or changed) name supplied to the resource DLL. |
| 0x13D9 | 無法在這個 RPC 伺服器上登錄任何驗證封裝。 |
No authentication package could be registered with the RPC server. |
| 0x13DA | 您無法讓群組連線，因為群組擁有者不在群組的慣用清單中，如果您要變更群組擁有者的節點，請移動群組。 |
You cannot bring the group online because the owner of the group is not in the preferred list for the group. To change the owner node for the group, move the group. |
| 0x13DB | 結合操作失敗，因為叢集資料庫的序號改變或與鎖定節點不相容。原因可能是在結合操作進行時，叢集資料被改變。 |
The join operation failed because the cluster database sequence number has changed or is incompatible with the locker node. This may happen during a join operation if the cluster database was changing during the join. |
| 0x13DC | 資源處在目前的狀態時，資源監視器不允許執行失敗的操作。原因可能是資源處在擱置狀態中。 |
The resource monitor will not allow the fail operation to be performed while the resource is in its current state. This may happen if the resource is in a pending state. |
| 0x13DD | 一個非鎖定碼收到保留鎖定以進行全域更新的要求。 |
A non locker code got a request to reserve the lock for making global updates. |
| 0x13DE | 叢集服務找不到仲裁磁碟。 |
The quorum disk could not be located by the cluster service. |
| 0x13DF | 備份的叢集資料庫可能損毀了。 |
The backed up cluster database is possibly corrupt. |
| 0x13E0 | 這個叢集節點中已經存在一個 DFS 根目錄。 |
A DFS root already exists in this cluster node. |
| 0x13E1 | 嘗試修改資源內容失敗，因為它與另一現存的內容發生衝突。 |
An attempt to modify a resource property failed because it conflicts with another existing property. |
| 0x13E2 | 在沒有「系統管理員存取點」的叢集上不支援此操作。 |
This operation is not supported on a cluster without an Administrator Access Point. |
| 0x1702 | 嘗試的操作與節點目前的成員資格狀態不相容。 |
An operation was attempted that is incompatible with the current membership state of the node. |
| 0x1703 | 仲裁資源未包含仲裁記錄。 |
The quorum resource does not contain the quorum log. |
| 0x1704 | 成員資格引擎要求關閉在這個節點上的叢集服務。 |
The membership engine requested shutdown of the cluster service on this node. |
| 0x1705 | 結合操作失敗，因為結合節點的叢集例項 ID 與贊助節點的叢集例項 ID 不符合。 |
The join operation failed because the cluster instance ID of the joining node does not match the cluster instance ID of the sponsor node. |
| 0x1706 | 找不到對應於所指定的 IP 位址的叢集網路。 |
A matching cluster network for the specified IP address could not be found. |
| 0x1707 | 真正的內容資料類型與預定的內容資料類型不符合。 |
The actual data type of the property did not match the expected data type of the property. |
| 0x1708 | 已順利將該叢集節點從叢集撤出，但未清除該節點。若要判斷哪些清理步驟失敗，以及修復的方法，請使用事件檢視器檢視容錯移轉叢集應用程式事件記錄檔。 |
The cluster node was evicted from the cluster successfully, but the node was not cleaned up. To determine what cleanup steps failed and how to recover, see the Failover Clustering application event log using Event Viewer. |
| 0x1709 | 為資源的內容所指定的兩個或更多的參數值相互衝突。 |
Two or more parameter values specified for a resource's properties are in conflict. |
| 0x170A | 這電腦無法成為叢集成員。 |
This computer cannot be made a member of a cluster. |
| 0x170B | 這電腦無法成為叢集成員，因為它沒有安裝正確的 Windows 版本。 |
This computer cannot be made a member of a cluster because it does not have the correct version of Windows installed. |
| 0x170C | 叢集無法以指定的叢集名稱建立，因為該叢集名稱已在使用中，請為叢集指定不同的名稱。 |
A cluster cannot be created with the specified cluster name because that cluster name is already in use. Specify a different name for the cluster. |
| 0x170D | 叢集設定動作已認可。 |
The cluster configuration action has already been committed. |
| 0x170E | 叢集設定動作無法回返。 |
The cluster configuration action could not be rolled back. |
| 0x170F | 指派給一節點上系統磁碟的磁碟機代號和指派給另一節點上磁碟的磁碟機代號相衝突。 |
The drive letter assigned to a system disk on one node conflicted with the drive letter assigned to a disk on another node. |
| 0x1710 | 叢集中一或多個節點上所執行的 Windows 版本不支援這個操作。 |
One or more nodes in the cluster are running a version of Windows that does not support this operation. |
| 0x1711 | 相對應電腦帳戶的名稱和這個資源的網路名稱不相符。 |
The name of the corresponding computer account doesn't match the Network Name for this resource. |
| 0x1712 | 沒有可用的網路介面卡。 |
No network adapters are available. |
| 0x1713 | 叢集節點已受污染。 |
The cluster node has been poisoned. |
| 0x1714 | 因為群組正移動到其他節點，所以無法接受要求。 |
The group is unable to accept the request since it is moving to another node. |
| 0x1715 | 因為資源類型正忙著執行其他作業，所以無法接受要求。 |
The resource type cannot accept the request since is too busy performing another operation. |
| 0x1716 | 叢集資源 DLL 的呼叫逾時。 |
The call to the cluster resource DLL timed out. |
| 0x1717 | 此位址對 IPv6 位址資源而言無效。必須有通用 IPv6 位址，並且它必須符合叢集網路。不允許使用相容的位址。 |
The address is not valid for an IPv6 Address resource. A global IPv6 address is required, and it must match a cluster network. Compatibility addresses are not permitted. |
| 0x1718 | 發生內部叢集錯誤。嘗試呼叫無效的函式。 |
An internal cluster error occurred. A call to an invalid function was attempted. |
| 0x1719 | 參數值超出可接受的範圍。 |
A parameter value is out of acceptable range. |
| 0x171A | 將資料傳送到叢集中的其他節點時，發生網路錯誤。傳輸的位元組數小於所需的位元組數。 |
A network error occurred while sending data to another node in the cluster. The number of bytes transmitted was less than required. |
| 0x171B | 嘗試的叢集登錄作業無效。 |
An invalid cluster registry operation was attempted. |
| 0x171C | 字元輸入字串未正確終止。 |
An input string of characters is not properly terminated. |
| 0x171D | 字元輸入字串呈現的資料格式無效。 |
An input string of characters is not in a valid format for the data it represents. |
| 0x171E | 發生內部叢集錯誤。已嘗試叢集資料庫交易，而交易進行中。 |
An internal cluster error occurred. A cluster database transaction was attempted while a transaction was already in progress. |
| 0x171F | 發生內部叢集錯誤。嘗試提交叢集資料庫交易，而沒有任何交易進行中。 |
An internal cluster error occurred. There was an attempt to commit a cluster database transaction while no transaction was in progress. |
| 0x1720 | 發生內部叢集錯誤。資料未正確初始化。 |
An internal cluster error occurred. Data was not properly initialized. |
| 0x1721 | 從資料資料流讀取時發生錯誤。傳回非預期的位元組數。 |
An error occurred while reading from a stream of data. An unexpected number of bytes was returned. |
| 0x1722 | 寫入資料資料流時發生錯誤。無法寫入要求的位元組數。 |
An error occurred while writing to a stream of data. The required number of bytes could not be written. |
| 0x1723 | 還原序列化叢集資料資料流時發生錯誤。 |
An error occurred while deserializing a stream of cluster data. |
| 0x1724 | 此資源的一或多個屬性值與其相依資源關聯的一或多個屬性值衝突。 |
One or more property values for this resource are in conflict with one or more property values associated with its dependent resource(s). |
| 0x1725 | 未呈現叢集節點仲裁以組成叢集。 |
A quorum of cluster nodes was not present to form a cluster. |
| 0x1726 | 叢集網路對 IPv6 位址資源而言無效，或是它與設定的位址不符。 |
The cluster network is not valid for an IPv6 Address resource, or it does not match the configured address. |
| 0x1727 | 叢集網路對 IPv6 通道資源而言無效。請檢查 IPv6 通道資源所使用之 IP 位址資源的設定。 |
The cluster network is not valid for an IPv6 Tunnel resource. Check the configuration of the IP Address resource on which the IPv6 Tunnel resource depends. |
| 0x1728 | 仲裁資源不能存在於「可用存放裝置」群組中。 |
Quorum resource cannot reside in the Available Storage group. |
| 0x1729 | 此資源的依存性巢狀結構太深。 |
The dependencies for this resource are nested too deeply. |
| 0x172A | 呼叫資源 DLL 引發一個無法處理的例外。 |
The call into the resource DLL raised an unhandled exception. |
| 0x172B | RHS 處理程序無法初始化。 |
The RHS process failed to initialize. |
| 0x172C | 這個節點沒有安裝容錯移轉叢集功能。 |
The Failover Clustering feature is not installed on this node. |
| 0x172D | 若要進行這個操作，資源必須在相同節點連線 |
The resources must be online on the same node for this operation |
| 0x172E | 無法新增新節點，因為此叢集已達到其最大的節點數目。 |
A new node can not be added since this cluster is already at its maximum number of nodes. |
| 0x172F | 無法建立此叢集，因為指定的節點數目超過最大允許的限制。 |
This cluster can not be created since the specified number of nodes exceeds the maximum allowed limit. |
| 0x1730 | 嘗試使用指定的叢集名稱失敗，因為在網域中已經有相同指定名稱的已啟用電腦物件。 |
An attempt to use the specified cluster name failed because an enabled computer object with the given name already exists in the domain. |
| 0x1731 | 無法損毀此叢集。它有非核心的應用程式群組，必須先刪除這些群組，才能損毀叢集。 |
This cluster cannot be destroyed. It has non-core application groups which must be deleted before the cluster can be destroyed. |
| 0x1732 | 此叢集或任何其節點無法裝載與檔案共用見證資源關聯的檔案共用。 |
File share associated with file share witness resource cannot be hosted by this cluster or any of its nodes. |
| 0x1733 | 目前無法將此節點撤出。由於仲裁需求，撤出該節點將會使叢集關閉。如果是叢集中的最後一個節點，則應該使用損毀叢集命令。 |
Eviction of this node is invalid at this time. Due to quorum requirements node eviction will result in cluster shutdown.If it is the last node in the cluster, destroy cluster command should be used. |
| 0x1734 | 在叢集中只允許一個此資源類型的例項。 |
Only one instance of this resource type is allowed in the cluster. |
| 0x1735 | 每個資源群組只允許一個此資源類型的例項。 |
Only one instance of this resource type is allowed per resource group. |
| 0x1736 | 此資源無法上線，因為一或多個提供者資源失敗。 |
The resource failed to come online due to the failure of one or more provider resources. |
| 0x1737 | 資源已指出它無法在任何節點上連線。 |
The resource has indicated that it cannot come online on any node. |
| 0x1738 | 此時無法在此群祖上執行目前的操作。 |
The current operation cannot be performed on this group at this time. |
| 0x1739 | 目錄或檔案不在叢集共用磁碟區中。 |
The directory or file is not located on a cluster shared volume. |
| 0x173A | 安全性描述元不符合叢集的需求。 |
The Security Descriptor does not meet the requirements for a cluster. |
| 0x173B | 叢集中已設定一或多個共用磁碟區資源。必須將這些資源移至可用存放裝置，才能順利操作。 |
There is one or more shared volumes resources configured in the cluster.Those resources must be moved to available storage in order for operation to succeed. |
| 0x173C | 無法直接操縱這個群組或資源。請使用共用磁碟區 API 執行想要的操作。 |
This group or resource cannot be directly manipulated.Use shared volume APIs to perform desired operation. |
| 0x173D | 正在進行備份。請先等待備份完成，再重試這項操作。 |
Back up is in progress. Please wait for backup completion before trying this operation again. |
| 0x173E | 路徑不屬於叢集共用磁碟區。 |
The path does not belong to a cluster shared volume. |
| 0x173F | 叢集共用磁碟區沒有掛接在本機的此節點上。 |
The cluster shared volume is not locally mounted on this node. |
| 0x1740 | 正在終止叢集看門狗。 |
The cluster watchdog is terminating. |
| 0x1741 | 資源已否決在兩個節點間的移動，因為它們不相容。 |
A resource vetoed a move between two nodes because they are incompatible. |
| 0x1742 | 要求無效，可能是因為當叢集處於只使用磁碟做為仲裁的模式時無法變更節點權重，或因為變更節點權重會違反最低叢集仲裁需求。 |
The request is invalid either because node weight cannot be changed while the cluster is in disk-only quorum mode, or because changing the node weight would violate the minimum cluster quorum requirements. |
| 0x1743 | 資源已否決呼叫。 |
The resource vetoed the call. |
| 0x1744 | 資源無法啟動或執行，因為它無法保留足夠的系統資源。 |
Resource could not start or run because it could not reserve sufficient system resources. |
| 0x1745 | 資源已否決在兩個節點間的移動，因為目的地目前沒有足夠資源可以完成作業。 |
A resource vetoed a move between two nodes because the destination currently does not have enough resources to complete the operation. |
| 0x1746 | 資源已否決在兩個節點間的移動，因為來源目前沒有足夠資源可以完成作業。 |
A resource vetoed a move between two nodes because the source currently does not have enough resources to complete the operation. |
| 0x1747 | 無法完成要求的作業，因為群組已排入佇列以準備執行作業。 |
The requested operation can not be completed because the group is queued for an operation. |
| 0x1748 | 無法完成要求的作業，因為資源已鎖定狀態。 |
The requested operation can not be completed because a resource has locked status. |
| 0x1749 | 資源無法移至另一個節點，因為叢集共用磁碟區已否決該作業。 |
The resource cannot move to another node because a cluster shared volume vetoed the operation. |
| 0x174A | 節點清空已在進行中。 |
A node drain is already in progress. |
| 0x174B | 叢集存放裝置未連線至節點。 |
Clustered storage is not connected to the node. |
| 0x174C | 磁碟未以搭配 CSV 使用的方式設定。CSV 磁碟至少必須有一個格式化為 NTFS 或 REFS 的磁碟分割。 |
The disk is not configured in a way to be used with CSV. CSV disks must have at least one partition that is formatted with NTFS or REFS. |
| 0x174D | 資源必須屬於「可用存放裝置」群組，才能完成此動作。 |
The resource must be part of the Available Storage group to complete this action. |
| 0x174E | CSVFS 作業失敗，因為磁碟區是重新導向模式。 |
CSVFS failed operation as volume is in redirected mode. |
| 0x174F | CSVFS 作業失敗，因為磁碟區不是重新導向模式。 |
CSVFS failed operation as volume is not in redirected mode. |
| 0x1750 | 目前無法傳回叢集特性。 |
Cluster properties cannot be returned at this time. |
| 0x1751 | 叢集磁碟資源包含「叢集共用磁碟區」不支援的軟體快照差異區域。 |
The clustered disk resource contains software snapshot diff area that are not supported for Cluster Shared Volumes. |
| 0x1752 | 無法完成作業，因為資源處於維護模式。 |
The operation cannot be completed because the resource is in maintenance mode. |
| 0x1753 | 無法完成該操作，因為發生叢集親和性衝突 |
The operation cannot be completed because of cluster affinity conflicts |
| 0x1754 | 無法完成該操作，因為該資源是複本虛擬機器。 |
The operation cannot be completed because the resource is a replica virtual machine. |
| 0x1755 | 「叢集功能等級」無法提升，因為並非叢集中的所有節點都支援更新的版本。 |
The Cluster Functional Level could not be increased because not all nodes in the cluster support the updated version. |
| 0x1756 | 更新叢集功能等級失敗，因為叢集目前是在修正仲裁模式下執行。請啟動叢集的其他成員節點，直到叢集達到仲裁，叢集將會自動切換脫離修正仲裁模式，或是請將叢集停止後再重新啟動而不進行 FixQuorum 切換。叢集脫離修正仲裁模式之後，請重試 Update-ClusterFunctionalLevel PowerShell Cmdlet 來更新叢集功能等級。 |
Updating the cluster functional level failed because the cluster is running in fix quorum mode.Start additional nodes which are members of the cluster until the cluster reaches quorum and the cluster will automaticallyswitch out of fix quorum mode, or stop and restart the cluster without the FixQuorum switch. Once the cluster is outof fix quorum mode retry the Update-ClusterFunctionalLevel PowerShell cmdlet to update the cluster functional level. |
| 0x1757 | 已順利更新叢集功能等級，但並非所有功能都已可用。請執行 Stop-Cluster PowerShell Cmdlet再執行 Start-Cluster PowerShell Cmdlet 重新啟動叢集，這樣所有叢集功能就可以使用。 |
The cluster functional level has been successfully updated but not all features are available yet. Restart the cluster byusing the Stop-Cluster PowerShell cmdlet followed by the Start-Cluster PowerShell cmdlet and all cluster features willbe available. |
| 0x1758 | 叢集目前正在執行版本升級。 |
The cluster is currently performing a version upgrade. |
| 0x1759 | 叢集未成功完成版本升級。 |
The cluster did not successfully complete the version upgrade. |
| 0x175A | 叢集節點處於寬限期中。 |
The cluster node is in grace period. |
| 0x175B | 操作失敗，因為 CSV 磁碟區無法在此檔案物件上指定的時間內復原。 |
The operation has failed because CSV volume was not able to recover in time specified on this file object. |
| 0x175C | 操作失敗，因為要求的節點目前不是使用中叢集成員資格的一部分。 |
The operation failed because the requested node is not currently part of active cluster membership. |
| 0x175D | 操作失敗，因為要求的叢集資源目前未受監視。 |
The operation failed because the requested cluster resource is currently unmonitored. |
| 0x175E | 操作失敗，因為資源不支援在未受監視的狀態下執行。 |
The operation failed because a resource does not support running in an unmonitored state. |
| 0x175F | 無法完成操作，因為有資源參與複寫。 |
The operation cannot be completed because a resource participates in replication. |
| 0x1760 | 操作失敗，因為要求的叢集節點已被隔離 |
The operation failed because the requested cluster node has been isolated |
| 0x1762 | 操作失敗，因為不符合指定的資料庫更新條件 |
The operation failed because the specified database update condition was not met |
| 0x1763 | 叢集空間處於已降級情況，因此目前無法完成要求的動作。 |
A clustered space is in a degraded condition and the requested action cannot be completed at this time. |
| 0x1764 | 操作失敗，因為不支援此控制項的權杖委派。 |
The operation failed because token delegation for this control is not supported. |
| 0x1765 | 作業失敗，因為 CSV 已將此檔案物件判定為無效。 |
The operation has failed because CSV has invalidated this file object. |
| 0x1766 | 只有 CSV 協調器節點上才支援此作業。 |
This operation is supported only on the CSV coordinator node. |
| 0x1767 | 叢集群組集合在所有進一步的要求中將無法使用。 |
The cluster group set is not available for any further requests. |
| 0x1768 | 找不到叢集群組集合。 |
The cluster group set could not be found. |
| 0x1769 | 目前無法完成該動作，因為叢集群組集合將低於仲裁且無法做為提供者使用。 |
The action cannot be completed at this time because the cluster group set would fall below quorum and not be able to act as a provider. |
| 0x176A | 找不到指定的父系容錯網域。 |
The specified parent fault domain is not found. |
| 0x176B | 容錯網域不能是指定之父系的子系。 |
The fault domain cannot be a child of the parent specified. |
| 0x176C | 儲存空間直接存取已拒絕建議的容錯網域變更，因為該變更會影響存放裝置容錯。 |
Storage Spaces Direct has rejected the proposed fault domain changes because it impacts the fault tolerance of the storage. |
| 0x176D | 儲存空間直接存取已拒絕建議的容錯網域變更，因為該變更會減少連線至系統的存放裝置。 |
Storage Spaces Direct has rejected the proposed fault domain changes because it reduces the storage connected to the system. |
| 0x1770 | 無法加密指定的檔案。 |
The specified file could not be encrypted. |
| 0x1771 | 無法解密指定的檔案。 |
The specified file could not be decrypted. |
| 0x1772 | 指定的檔案已加密，而且使用者沒有能力解密。 |
The specified file is encrypted and the user does not have the ability to decrypt it. |
| 0x1773 | 沒有為這個系統所設定的正確加密修復原則。 |
There is no valid encryption recovery policy configured for this system. |
| 0x1774 | 必要的加密驅動程式並未載入系統中。 |
The required encryption driver is not loaded for this system. |
| 0x1775 | 檔案加密所使用的加密驅動程式，與目前載入的加密驅動程式不同。 |
The file was encrypted with a different encryption driver than is currently loaded. |
| 0x1776 | 沒有為使用者定義 EFS 金鑰。 |
There are no EFS keys defined for the user. |
| 0x1777 | 指定的檔案並未加密。 |
The specified file is not encrypted. |
| 0x1778 | 指定的檔案不是定義的 EFS 匯出格式。 |
The specified file is not in the defined EFS export format. |
| 0x1779 | 指定的檔案是唯讀屬性。 |
The specified file is read only. |
| 0x177A | 目錄因加密而停用。 |
The directory has been disabled for encryption. |
| 0x177B | 伺服器不受遠端加密操作信任。 |
The server is not trusted for remote encryption operation. |
| 0x177C | 為這個系統所設定的修復原則含有不正確的修復憑證。 |
Recovery policy configured for this system contains invalid recovery certificate. |
| 0x177D | 使用於來源檔的加密演算法比目的檔所使用的需要更大的金鑰緩衝區。 |
The encryption algorithm used on the source file needs a bigger key buffer than the one on the destination file. |
| 0x177E | 這個磁碟分割不支援檔案加密。 |
The disk partition does not support file encryption. |
| 0x177F | 這台電腦已停用檔案加密。 |
This machine is disabled for file encryption. |
| 0x1780 | 要求較新的系統來解密這個加密的檔案。 |
A newer system is required to decrypt this encrypted file. |
| 0x1781 | 遠端伺服器已將無效的回應傳送給以用戶端加密開啟的檔案。 |
The remote server sent an invalid response for a file being opened with Client Side Encryption. |
| 0x1782 | 遠端伺服器雖然聲稱支援用戶端加密，但其實不支援。 |
Client Side Encryption is not supported by the remote server even though it claims to support it. |
| 0x1783 | 檔案已加密，且應在用戶端加密模式下開啟。 |
File is encrypted and should be opened in Client Side Encryption mode. |
| 0x1784 | 已建立新的加密檔案，且需要提供 $EFS。 |
A new encrypted file is being created and a $EFS needs to be provided. |
| 0x1785 | SMB 用戶端在非 CSE 檔案上要求 CSE FSCTL。 |
The SMB client requested a CSE FSCTL on a non-CSE file. |
| 0x1786 | 原則已經封鎖要求的操作。如需詳細資訊，請連絡您的系統管理員。 |
The requested operation was blocked by policy. For more information, contact your system administrator. |
| 0x17E6 | 此工作群組的伺服器清單目前無法使用 |
The list of servers for this workgroup is not currently available |
| 0x1838 | 工作排程器服務必須設定成在系統帳戶中執行，才能正常運作。獨立的工作必須設定成在其他帳戶中執行。 |
The Task Scheduler service must be configured to run in the System account to function properly. Individual tasks may be configured to run in other accounts. |
| 0x19C8 | 記錄服務遇到無效的記錄磁區。 |
Log service encountered an invalid log sector. |
| 0x19C9 | 記錄服務遇到具有無效區塊同位檢查的記錄磁區。 |
Log service encountered a log sector with invalid block parity. |
| 0x19CA | 記錄服務遇到重新對應的記錄磁區。 |
Log service encountered a remapped log sector. |
| 0x19CB | 記錄服務遇到部分或未完成的記錄區塊。 |
Log service encountered a partial or incomplete log block. |
| 0x19CC | 記錄服務遇到嘗試存取使用中記錄範圍外的資料。 |
Log service encountered an attempt access data outside the active log range. |
| 0x19CD | 記錄服務使用者排列緩衝區已耗盡， |
Log service user marshalling buffers are exhausted. |
| 0x19CE | 記錄服務遇到從具有無效讀取內容之排列區域讀取的嘗試。 |
Log service encountered an attempt read from a marshalling area with an invalid read context. |
| 0x19CF | 記錄服務遇到無效的記錄重新啟動區域。 |
Log service encountered an invalid log restart area. |
| 0x19D0 | 記錄服務遇到無效的記錄區塊版本。 |
Log service encountered an invalid log block version. |
| 0x19D1 | 記錄服務遇到無效的記錄區塊。 |
Log service encountered an invalid log block. |
| 0x19D2 | 記錄服務遇到讀取具有無效讀取模式的嘗試。 |
Log service encountered an attempt to read the log with an invalid read mode. |
| 0x19D3 | 記錄服務遇到沒有重新啟動區域的記錄資料流。 |
Log service encountered a log stream with no restart area. |
| 0x19D4 | 記錄服務遇到毀損的中繼資料檔案。 |
Log service encountered a corrupted metadata file. |
| 0x19D5 | 記錄服務遇到的中繼資料檔案無法由記錄檔案系統建立。 |
Log service encountered a metadata file that could not be created by the log file system. |
| 0x19D6 | 記錄服務遇到資料不一致的中繼資料檔案。 |
Log service encountered a metadata file with inconsistent data. |
| 0x19D7 | 記錄服務遇到錯誤配置或放置保留空間的嘗試。 |
Log service encountered an attempt to erroneous allocate or dispose reservation space. |
| 0x19D8 | 記錄服務無法刪除記錄檔或檔案系統容器。 |
Log service cannot delete log file or file system container. |
| 0x19D9 | 記錄服務已達到配置給記錄檔的可允許容器上限。 |
Log service has reached the maximum allowable containers allocated to a log file. |
| 0x19DA | 記錄服務已嘗試超過記錄開頭向後讀取或寫入。 |
Log service has attempted to read or write backward past the start of the log. |
| 0x19DB | 因為相同類型的原則已存在，所以無法安裝記錄原則。 |
Log policy could not be installed because a policy of the same type is already present. |
| 0x19DC | 問題記錄原則此時未依要求安裝。 |
Log policy in question was not installed at the time of the request. |
| 0x19DD | 記錄上安裝的原則集無效。 |
The installed set of policies on the log is invalid. |
| 0x19DE | 問題記錄上的原則導致作業無法完成。 |
A policy on the log in question prevented the operation from completing. |
| 0x19DF | 因為記錄空間已由封存結尾所釘選，所以無法收回。 |
Log space cannot be reclaimed because the log is pinned by the archive tail. |
| 0x19E0 | 記錄不是記錄檔中的記錄。 |
Log record is not a record in the log file. |
| 0x19E1 | 保留的記錄數或保留記錄數的調整無效。 |
Number of reserved log records or the adjustment of the number of reserved log records is invalid. |
| 0x19E2 | 保留的記錄空間或記錄空間的調整無效。 |
Reserved log space or the adjustment of the log space is invalid. |
| 0x19E3 | 新的或現有封存結尾或使用中記錄的基底無效。 |
An new or existing archive tail or base of the active log is invalid. |
| 0x19E4 | 記錄空間已耗盡。 |
Log space is exhausted. |
| 0x19E5 | 無法將記錄設定為要求的大小。 |
The log could not be set to the requested size. |
| 0x19E6 | 記錄為多工，不允許直接寫入實體記錄。 |
Log is multiplexed, no direct writes to the physical log is allowed. |
| 0x19E7 | 因為記錄是固定記錄，所以作業失敗。 |
The operation failed because the log is a dedicated log. |
| 0x19E8 | 作業需要封存內容。 |
The operation requires an archive context. |
| 0x19E9 | 記錄封存進行中。 |
Log archival is in progress. |
| 0x19EA | 作業需要非暫時的記錄，但記錄為暫時。 |
The operation requires a non-ephemeral log, but the log is ephemeral. |
| 0x19EB | 記錄必須至少有兩個容器，才能供讀取或寫入。 |
The log must have at least two containers before it can be read from or written to. |
| 0x19EC | 記錄用戶端已在資料流上登錄。 |
A log client has already registered on the stream. |
| 0x19ED | 記錄用戶端未在資料流上登錄。 |
A log client has not been registered on the stream. |
| 0x19EE | 已發出要求來處理記錄已滿的狀況。 |
A request has already been made to handle the log full condition. |
| 0x19EF | 記錄服務嘗試從記錄容器讀取時發生錯誤。 |
Log service encountered an error when attempting to read from a log container. |
| 0x19F0 | 記錄服務嘗試寫入記錄容器時發生錯誤。 |
Log service encountered an error when attempting to write to a log container. |
| 0x19F1 | 記錄服務嘗試開啟記錄容器時發生錯誤。 |
Log service encountered an error when attempting open a log container. |
| 0x19F2 | 記錄服務嘗試進行要求的動作時，遇到無效的容器狀態。 |
Log service encountered an invalid container state when attempting a requested action. |
| 0x19F3 | 記錄服務狀態錯誤，無法執行要求的動作。 |
Log service is not in the correct state to perform a requested action. |
| 0x19F4 | 因為記錄空間已釘選，所以無法收回記錄空間。 |
Log space cannot be reclaimed because the log is pinned. |
| 0x19F5 | 記錄中繼資料清除失敗。 |
Log metadata flush failed. |
| 0x19F6 | 記錄上的安全性及其容器不一致。 |
Security on the log and its containers is inconsistent. |
| 0x19F7 | 記錄已附加到記錄檔或保留項目有所變更，但無法清除記錄檔。 |
Records were appended to the log or reservation changes were made, but the log could not be flushed. |
| 0x19F8 | 保留項目耗用了大部分的記錄檔空間，所以已釘選記錄檔。請釋放一些保留的記錄以釋出空間。 |
The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available. |
| 0x1A2C | 與此作業相關的交易控制代碼無效。 |
The transaction handle associated with this operation is not valid. |
| 0x1A2D | 在交易的內容中已進行要求的動作，但是交易不再作用。 |
The requested operation was made in the context of a transaction that is no longer active. |
| 0x1A2E | 交易物件處於目前狀態時，要求的作業無效。 |
The requested operation is not valid on the Transaction object in its current state. |
| 0x1A2F | 呼叫者已呼叫回應 API，但因為 TM 未發出對應的要求給呼叫者，所以預期不會得到回應。 |
The caller has called a response API, but the response is not expected because the TM did not issue the corresponding request to the caller. |
| 0x1A30 | 因為交易已取消，所以要執行要求的作業已經太晚。 |
It is too late to perform the requested operation, since the Transaction has already been aborted. |
| 0x1A31 | 因為交易已認可，所以要執行要求的作業已經太晚。 |
It is too late to perform the requested operation, since the Transaction has already been committed. |
| 0x1A32 | 無法順利初始化交易管理員。不支援交易的作業。 |
The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported. |
| 0x1A33 | 指定的 ResourceManager 對此交易下的資源未進行任何變更或更新。 |
The specified ResourceManager made no changes or updates to the resource under this transaction. |
| 0x1A34 | 資源管理員已嘗試準備其未順利加入的交易。 |
The resource manager has attempted to prepare a transaction that it has not successfully joined. |
| 0x1A35 | 交易物件已具有上層登記，而呼叫者嘗試的作業可能建立新的上層。只會允許一個上層登記。 |
The Transaction object already has a superior enlistment, and the caller attempted an operation that would have created a new superior. Only a single superior enlistment is allow. |
| 0x1A36 | RM 嘗試登錄的通訊協定已存在。 |
The RM tried to register a protocol that already exists. |
| 0x1A37 | 傳播交易的嘗試失敗。 |
The attempt to propagate the Transaction failed. |
| 0x1A38 | 要求的傳播通訊協定未登錄為 CRM。 |
The requested propagation protocol was not registered as a CRM. |
| 0x1A39 | 傳遞到 PushTransaction 或 PullTransaction 之緩衝區的格式無效。 |
The buffer passed in to PushTransaction or PullTransaction is not in a valid format. |
| 0x1A3A | 與執行緒關聯的目前交易內容不是交易物件的有效控制代碼。 |
The current transaction context associated with the thread is not a valid handle to a transaction object. |
| 0x1A3B | 因為找不到指定的 Transaction 物件，所以無法開啟。 |
The specified Transaction object could not be opened, because it was not found. |
| 0x1A3C | 因為找不到指定的 ResourceManager 物件，所以無法開啟。 |
The specified ResourceManager object could not be opened, because it was not found. |
| 0x1A3D | 因為找不到指定的 Enlistment 物件，所以無法開啟。 |
The specified Enlistment object could not be opened, because it was not found. |
| 0x1A3E | 因為找不到指定的 TransactionManager 物件，所以無法開啟。 |
The specified TransactionManager object could not be opened, because it was not found. |
| 0x1A3F | 無法建立或開啟指定的物件，因為物件關聯的 TransactionManager 並未連線。必須呼叫 RecoverTransactionManager 讓 TransactionManager 完全連線，以復原到 LogFile 結尾，才能開啟 Transaction 或 ResourceManager 中的物件。此外，將記錄寫入 LogFile 時發生的錯誤可能會造成 TransactionManager 離線。 |
The object specified could not be created or opened, because its associated TransactionManager is not online. The TransactionManager must be brought fully Online by calling RecoverTransactionManager to recover to the end of its LogFile before objects in its Transaction or ResourceManager namespaces can be opened. In addition, errors in writing records to its LogFile can cause a TransactionManager to go offline. |
| 0x1A40 | 指定的 TransactionManager 無法建立包含在其 Ob 命名空間之記錄檔中的物件。因此，TransactionManager 無法修復。 |
The specified TransactionManager was unable to create the objects contained in its logfile in the Ob namespace. Therefore, the TransactionManager was unable to recover. |
| 0x1A41 | 無法完成呼叫以在此 Transaction 物件上建立上層 Enlistment，因為針對徵募指定的 Transaction 物件是該 Transaction 的下層分支。只有 Transaction 的根項目可以徵募為上層。 |
The call to create a superior Enlistment on this Transaction object could not be completed, because the Transaction object specified for the enlistment is a subordinate branch of the Transaction. Only the root of the Transaction can be enlisted on as a superior. |
| 0x1A42 | 關聯的交易管理員或資源管理員已關閉，因此控制代碼已無效。 |
Because the associated transaction manager or resource manager has been closed, the handle is no longer valid. |
| 0x1A43 | 無法在這個上層徵募執行指定的操作，因為徵募不是以 NotificationMask 中相對應的完成回應所建立。 |
The specified operation could not be performed on this Superior enlistment, because the enlistment was not created with the corresponding completion response in the NotificationMask. |
| 0x1A44 | 無法執行指定的操作，因為記錄的記錄太長。發生這個狀況的原因有二: 這個交易的徵募太多，或是代表這些徵募記錄的組合 RecoveryInformation 太長。 |
The specified operation could not be performed, because the record that would be logged was too long. This can occur because of two conditions: either there are too many Enlistments on this Transaction, or the combined RecoveryInformation being logged on behalf of those Enlistments is too long. |
| 0x1A45 | 不支援隱含交易。 |
Implicit transaction are not supported. |
| 0x1A46 | 核心交易管理員已中止或放棄交易，因為它已封鎖轉送程序。 |
The kernel transaction manager had to abort or forget the transaction because it blocked forward progress. |
| 0x1A47 | 提供的 TransactionManager 識別碼與 TransactionManager 記錄檔中所記錄的識別碼不相符。 |
The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file. |
| 0x1A48 | 無法繼續此快照操作，因為無法凍結處於目前狀態的交易資源管理員。請再試一次。 |
This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again. |
| 0x1A49 | 無法使用指定的 EnlistmentMask 徵募交易，因為交易已經完成 PrePrepare 階段。若要確保正確性，ResourceManager 必須切換到寫入模式，並且停止快取此交易內的資料。只徵募後續的交易階段可能仍會成功。 |
The transaction cannot be enlisted on with the specified EnlistmentMask, because the transaction has already completed the PrePrepare phase. In order to ensure correctness, the ResourceManager must switch to a write-through mode and cease caching data within this transaction. Enlisting for only subsequent transaction phases may still succeed. |
| 0x1A4A | 這個交易沒有上層徵募。 |
The transaction does not have a superior enlistment. |
| 0x1A4B | 認可交易的嘗試已完成，但交易樹狀目錄的某些部分可能因啟發學習法而沒有認可成功。因此，交易中的部分修改資料可能尚未認可，這會導致交易的不一致。如果可能，請檢查關聯資料的一致性。 |
The attempt to commit the Transaction completed, but it is possible that some portion of the transaction tree did not commit successfully due to heuristics. Therefore it is possible that some data modified in the transaction may not have committed, resulting in transactional inconsistency. If possible, check the consistency of the associated data. |
| 0x1A90 | 函數嘗試使用的名稱，已保留給其他交易使用。 |
The function attempted to use a name that is reserved for use by another transaction. |
| 0x1A91 | 未啟動指定資源管理員內的交易支援，或因為錯誤而關閉。 |
Transaction support within the specified resource manager is not started or was shut down due to an error. |
| 0x1A92 | RM 的中繼資料已損毀。RM 將無法運作。 |
The metadata of the RM has been corrupted. The RM will not function. |
| 0x1A93 | 指定的目錄未包含資源管理員。 |
The specified directory does not contain a resource manager. |
| 0x1A95 | 遠端伺服器或共用不支援交易的檔案作業。 |
The remote server or share does not support transacted file operations. |
| 0x1A96 | 要求的記錄大小無效。 |
The requested log size is invalid. |
| 0x1A97 | 對應到控制代碼的物件 (檔案、資料流、連結) 已被交易儲存點復原刪除。 |
The object (file, stream, link) corresponding to the handle has been deleted by a Transaction Savepoint Rollback. |
| 0x1A98 | 找不到此開啟之交易檔案的指定檔案迷你版本。 |
The specified file miniversion was not found for this transacted file open. |
| 0x1A99 | 找到指定的檔案迷你版本，但已失效。可能是因為交易儲存點復原而造成。 |
The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback. |
| 0x1A9A | 只能在建立迷你版本的交易內容中開啟迷你版本。 |
A miniversion may only be opened in the context of the transaction that created it. |
| 0x1A9B | 無法使用修改存取來開啟迷你版本。 |
It is not possible to open a miniversion with modify access. |
| 0x1A9C | 無法再為此資料流建立任何的迷你版本。 |
It is not possible to create any more miniversions for this stream. |
| 0x1A9E | 遠端伺服器已傳送不符的版本號碼或 Fid 給以交易開啟的檔案。 |
The remote server sent mismatching version number or Fid for a file opened with transactions. |
| 0x1A9F | 交易已讓控制代碼失效。最可能的原因是當交易結束或回復到儲存點時，檔案或開啟的控制代碼上存在記憶體對應。 |
The handle has been invalidated by a transaction. The most likely cause is the presence of memory mapping on a file or an open handle when the transaction ended or rolled back to savepoint. |
| 0x1AA0 | 檔案上沒有任何交易中繼資料。 |
There is no transaction metadata on the file. |
| 0x1AA1 | 記錄資料已毀損。 |
The log data is corrupt. |
| 0x1AA2 | 因為檔案中仍有開啟的控制代碼，所以無法復原檔案。 |
The file can't be recovered because there is a handle still open on it. |
| 0x1AA3 | 因為負責交易結果的資源管理員已中斷連線，所以無法取得交易結果。 |
The transaction outcome is unavailable because the resource manager responsible for it has disconnected. |
| 0x1AA4 | 因為問題徵募不是上層徵募，所以拒絕要求。 |
The request was rejected because the enlistment in question is not a superior enlistment. |
| 0x1AA5 | 交易資源管理員已經一致。不需要進行修復。 |
The transactional resource manager is already consistent. Recovery is not needed. |
| 0x1AA6 | 交易資源管理員已經啟動。 |
The transactional resource manager has already been started. |
| 0x1AA7 | 無法以交易開啟檔案，因為檔案的識別碼依賴未解決交易的結果。 |
The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction. |
| 0x1AA8 | 因為其他交易依賴這個屬性不會改變的事實，所以無法執行作業。 |
The operation cannot be performed because another transaction is depending on the fact that this property will not change. |
| 0x1AA9 | 作業將牽涉到單一檔案及兩個交易資源管理員，因此不允許作業。 |
The operation would involve a single file with two transactional resource managers and is therefore not allowed. |
| 0x1AAA | $Txf 目錄必須為空，這個作業才能成功。 |
The $Txf directory must be empty for this operation to succeed. |
| 0x1AAB | 作業會讓交易資源管理員處於不一致的狀態，因此不允許作業。 |
The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed. |
| 0x1AAC | 因為交易管理員沒有記錄檔，所以無法完成作業。 |
The operation could not be completed because the transaction manager does not have a log. |
| 0x1AAD | 因為已經執行之前排程的復原，或排程的復原已進入佇列等候執行，所以無法排程復原。 |
A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution. |
| 0x1AAE | 檔案或目錄上的交易中繼資料屬性已損毀且無法讀取。 |
The transactional metadata attribute on the file or directory is corrupt and unreadable. |
| 0x1AAF | 因為交易為使用中，所以無法完成加密作業。 |
The encryption operation could not be completed because a transaction is active. |
| 0x1AB0 | 不允許在交易中開啟此物件。 |
This object is not allowed to be opened in a transaction. |
| 0x1AB1 | 嘗試在交易資源管理員的記錄檔中建立空間失敗。已在事件記錄檔中記錄失敗狀態。 |
An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log. |
| 0x1AB2 | 不支援在交易下記憶體對應 (建立對應區段) 遠端檔案。 |
Memory mapping (creating a mapped section) a remote file under a transaction is not supported. |
| 0x1AB3 | 交易中繼資料已存在此檔案中，且無法取代。 |
Transaction metadata is already present on this file and cannot be superseded. |
| 0x1AB4 | 因為無法初始化範圍處理常式，所以無法輸入交易範圍。 |
A transaction scope could not be entered because the scope handler has not been initialized. |
| 0x1AB5 | 需要升級才能讓資源管理員徵募，但交易已設定為不允許升級。 |
Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it. |
| 0x1AB6 | 已在未解決的交易中開啟此檔案以進行修改，且只可由交易讀取器開啟來執行。 |
This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader. |
| 0x1AB7 | 因為交易之前未被凍結，所以已略過取消凍結交易的要求。 |
The request to thaw frozen transactions was ignored because transactions had not previously been frozen. |
| 0x1AB8 | 因為正在進行凍結，所以無法取消凍結交易。 |
Transactions cannot be frozen because a freeze is already in progress. |
| 0x1AB9 | 目標磁碟區不是快照磁碟區。只有在掛接為快照的磁碟區上，此作業才有效。 |
The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot. |
| 0x1ABA | 因為檔案在交易上開啟，所以儲存點作業失敗。不允許這項動作。 |
The savepoint operation failed because files are open on the transaction. This is not permitted. |
| 0x1ABB | Windows 已探查到檔案中的毀損，且該檔案已經修復。資料可能會遺失。 |
Windows has discovered corruption in a file, and that file has since been repaired. Data loss may have occurred. |
| 0x1ABC | 因為交易正在檔案上作用，所以無法完成鬆散作業。 |
The sparse operation could not be completed because a transaction is active on the file. |
| 0x1ABD | 建立 TransactionManager 物件的呼叫失敗，因為儲存在記錄檔的 Tm 識別碼與傳遞入當引數的 Tm 識別碼不符。 |
The call to create a TransactionManager object failed because the Tm Identity stored in the logfile does not match the Tm Identity that was passed in as an argument. |
| 0x1ABE | 已在區段物件上嘗試 I/O，而該 I/O 因為交易結束的原因而浮動。沒有有效的資料。 |
I/O was attempted on a section object that has been floated as a result of a transaction ending. There is no valid data. |
| 0x1ABF | 因為發生暫時性的狀況 (例如資源不足)，所以交易資源管理員目前無法接受交易工作。 |
The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources. |
| 0x1AC0 | 交易資源管理員有太多無法中止的待處理交易。交易資源管理員已關閉。 |
The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down. |
| 0x1AC1 | 無法完成此操作，因為磁碟上的叢集已損壞。 |
The operation could not be completed due to bad clusters on disk. |
| 0x1AC2 | 無法完成壓縮操作，因為該檔案上有作用中的交易。 |
The compression operation could not be completed because a transaction is active on the file. |
| 0x1AC3 | 操作無法完成，因為磁碟區不乾淨。請執行 chkdsk 然後再試一次。 |
The operation could not be completed because the volume is dirty. Please run chkdsk and try again. |
| 0x1AC4 | 無法完成連結追蹤操作，因為交易是使用中狀態。 |
The link tracking operation could not be completed because a transaction is active. |
| 0x1AC5 | 無法在交易中執行此操作。 |
This operation cannot be performed in a transaction. |
| 0x1AC6 | 控制代碼與其交易已不再正確地關聯。它可能在交易資源管理員中開啟，隨後被強制重新啟動。請關閉該控制代碼，然後開啟新的控制代碼。 |
The handle is no longer properly associated with its transaction. It may have been opened in a transactional resource manager that was subsequently forced to restart. Please close the handle and open a new one. |
| 0x1AC7 | 無法執行指定的操作，因為交易中未徵募資源管理員。 |
The specified operation could not be performed because the resource manager is not enlisted in the transaction. |
| 0x1B59 | 指定的工作階段名稱不正確。 |
The specified session name is invalid. |
| 0x1B5A | 指定的通訊協定驅動程式不正確。 |
The specified protocol driver is invalid. |
| 0x1B5B | 系統路徑中找不到指定的通訊協定驅動程式。 |
The specified protocol driver was not found in the system path. |
| 0x1B5C | 系統路徑中找不到指定的終端機連線驅動程式。 |
The specified terminal connection driver was not found in the system path. |
| 0x1B5D | 無法建立這個工作階段的事件記錄登錄機碼。 |
A registry key for event logging could not be created for this session. |
| 0x1B5E | 系統中已有名稱相同的服務。 |
A service with the same name already exists on the system. |
| 0x1B5F | 一個關閉的操作正擱置於工作階段中。 |
A close operation is pending on the session. |
| 0x1B60 | 沒有可用的輸出緩衝區。 |
There are no free output buffers available. |
| 0x1B61 | 找不到 MODEM.INF 檔案。 |
The MODEM.INF file was not found. |
| 0x1B62 | MODEM.INF 中找不到數據機名稱。 |
The modem name was not found in MODEM.INF. |
| 0x1B63 | 數據機不接受傳送給它的命令。請檢查設定的數據機名稱是否與連結的數據機相符。 |
The modem did not accept the command sent to it. Verify that the configured modem name matches the attached modem. |
| 0x1B64 | 數據機沒有回應傳送給它的命令。請檢查數據機的電纜是否已正確接妥，電源是否已開啟。 |
The modem did not respond to the command sent to it. Verify that the modem is properly cabled and powered on. |
| 0x1B65 | 載波偵測失敗。或是因為斷線，所以載波遺失。 |
Carrier detect has failed or carrier has been dropped due to disconnect. |
| 0x1B66 | 要求的時間內沒有偵測出撥號音。請檢查電話電纜是否已正確連接，是否正常運作。 |
Dial tone not detected within the required time. Verify that the phone cable is properly attached and functional. |
| 0x1B67 | 回撥時偵測到遠端站台的忙線信號。 |
Busy signal detected at remote site on callback. |
| 0x1B68 | 回撥時偵測出遠端站台的聲音。 |
Voice detected at remote site on callback. |
| 0x1B69 | 傳輸驅動程式錯誤 |
Transport driver error |
| 0x1B6E | 找不到指定的工作階段。 |
The specified session cannot be found. |
| 0x1B6F | 指定的工作階段名稱已在使用中。 |
The specified session name is already in use. |
| 0x1B70 | 目前嘗試的工作無法完成，因為遠端桌面服務目前忙碌中。請稍後再試一次。其他使用者應該仍然可以登入。 |
The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on. |
| 0x1B71 | 嘗試連線到視訊模式不受目前用戶端支援的工作階段。 |
An attempt has been made to connect to a session whose video mode is not supported by the current client. |
| 0x1B7B | 應用程式嘗試啟用 DOS 圖形模式。DOS 圖形模式不受支援。 |
The application attempted to enable DOS graphics mode. DOS graphics mode is not supported. |
| 0x1B7D | 您的互動登入特殊權限已停用。請連絡您的系統管理員。 |
Your interactive logon privilege has been disabled. Please contact your administrator. |
| 0x1B7E | 要求的操作只能在系統主控台上執行。這經常是驅動程式或系統 DLL 要求直接存取主控台的結果。 |
The requested operation can be performed only on the system console. This is most often the result of a driver or system DLL requiring direct console access. |
| 0x1B80 | 用戶端無法回應伺服器連線訊息。 |
The client failed to respond to the server connect message. |
| 0x1B81 | 不支援中斷主控台工作階段。 |
Disconnecting the console session is not supported. |
| 0x1B82 | 不支援將中斷的工作階段重新連線到主控台。 |
Reconnecting a disconnected session to the console is not supported. |
| 0x1B84 | 拒絕在另一個工作階段遠端控制的要求。 |
The request to control another session remotely was denied. |
| 0x1B85 | 拒絕存取要求的工作階段。 |
The requested session access is denied. |
| 0x1B89 | 指定的終端機連線驅動程式不正確。 |
The specified terminal connection driver is invalid. |
| 0x1B8A | 無法在要求的工作階段遠端控制。這可能是因為這個工作階段已中斷連線，或目前沒使用者登入。 |
The requested session cannot be controlled remotely.This may be because the session is disconnected or does not currently have a user logged on. |
| 0x1B8B | 要求的工作階段並非設定成允許遠端控制。 |
The requested session is not configured to allow remote control. |
| 0x1B8C | 您想要建立終端機伺服器的連線要求被拒絕。您的終端機伺服器用戶端授權號碼目前正被其他使用者使用。請和您的系統管理員連絡以獲得一個唯一的授權號碼。 |
Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number is currently being used by another user. Please call your system administrator to obtain a unique license number. |
| 0x1B8D | 您想要建立終端機伺服器的連線要求被拒絕。尚未針對此終端機伺服器用戶端輸入您的終端機伺服器用戶端授權號碼。請連絡您的系統管理員。 |
Your request to connect to this Terminal Server has been rejected. Your Terminal Server client license number has not been entered for this copy of the Terminal Server client. Please contact your system administrator. |
| 0x1B8E | 這部電腦已達到允許的連線數目上限，而且所有連線目前都在使用中。請稍後再嘗試連線，或連絡您的系統管理員。 |
The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator. |
| 0x1B8F | 您所使用的用戶端並未被授權來使用這個系統。您的登入要求已被拒絕。 |
The client you are using is not licensed to use this system. Your logon request is denied. |
| 0x1B90 | 系統授權已逾期。您的登入要求被拒。 |
The system license has expired. Your logon request is denied. |
| 0x1B91 | 無法終止遠端控制，因為所指定的工作階段目前不受遠端控制。 |
Remote control could not be terminated because the specified session is not currently being remotely controlled. |
| 0x1B92 | 主控台的遠端控制已終止，原因是顯示模式已經變更。在遠端控制工作階段中變更顯示模式是不受支援的。 |
The remote control of the console was terminated because the display mode was changed. Changing the display mode in a remote control session is not supported. |
| 0x1B93 | 這個安裝的啟用已經重設了允許的最大次數。您的啟用計時將不會清除。 |
Activation has already been reset the maximum number of times for this installation. Your activation timer will not be cleared. |
| 0x1B94 | 遠端登入目前已停用。 |
Remote logins are currently disabled. |
| 0x1B95 | 您沒有適當的加密層級，無法存取這個工作階段。 |
You do not have the proper encryption level to access this Session. |
| 0x1B96 | 使用者 %s\\\\%s 目前已登入到這部電腦。只有目前的使用者或系統管理員可登入這部電腦。 |
The user %s\\\\%s is currently logged on to this computer. Only the current user or an administrator can log on to this computer. |
| 0x1B97 | 使用者 %s\\\\%s 已登入這部電腦的主控台。您此時沒有權限登入。若要解決此問題，請連絡 %s\\\\%s，並將他們登出。 |
The user %s\\\\%s is already logged on to the console of this computer. You do not have permission to log in at this time. To resolve this issue, contact %s\\\\%s and have them log off. |
| 0x1B98 | 無法讓您登入，因為有帳戶限制。 |
Unable to log you on because of an account restriction. |
| 0x1B99 | RDP 通訊協定元件 %2 偵測出通訊協定資料流中有錯誤，已經中斷用戶端連線。 |
The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client. |
| 0x1B9A | 終端機連線的用戶端磁碟對應服務已經連線。 |
The Client Drive Mapping Service Has Connected on Terminal Connection. |
| 0x1B9B | 終端機連線的用戶端磁碟對應服務已經中斷連線。 |
The Client Drive Mapping Service Has Disconnected on Terminal Connection. |
| 0x1B9C | 終端機伺服器安全性階層已偵測到通訊協定資料流中的錯誤，並已中斷用戶端的連線。 |
The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. |
| 0x1B9D | 目標工作階段與目前的工作階段不相容。 |
The target session is incompatible with the current session. |
| 0x1B9E | Windows 無法連線到您的工作階段，因為 Windows 視訊子系統發生問題。請稍後再次嘗試連線，或連絡伺服器系統管理員以取得協助。 |
Windows can't connect to your session because a problem occurred in the Windows video subsystem. Try connecting again later, or contact the server administrator for assistance. |
| 0x1F41 | 檔案複寫服務 API 呼叫不正確。 |
The file replication service API was called incorrectly. |
| 0x1F42 | 無法啟動檔案複寫服務。 |
The file replication service cannot be started. |
| 0x1F43 | 無法停止檔案複寫服務。 |
The file replication service cannot be stopped. |
| 0x1F44 | 檔案複寫服務 API 已中止要求。事件記錄檔可能有其他資訊。 |
The file replication service API terminated the request. The event log may have more information. |
| 0x1F45 | 檔案複寫服務已中止要求。事件記錄檔可能有其他資訊。 |
The file replication service terminated the request. The event log may have more information. |
| 0x1F46 | 無法連絡檔案複寫服務。事件記錄檔可能有其他資訊。 |
The file replication service cannot be contacted. The event log may have more information. |
| 0x1F47 | 檔案複寫服務無法滿足要求，因為使用者的特殊權限不足。事件記錄檔可能有其他資訊。 |
The file replication service cannot satisfy the request because the user has insufficient privileges. The event log may have more information. |
| 0x1F48 | 檔案複寫服務無法滿足要求，因為驗證 RPC 無法使用。事件記錄檔可能有其他資訊。 |
The file replication service cannot satisfy the request because authenticated RPC is not available. The event log may have more information. |
| 0x1F49 | 檔案複寫服務無法滿足要求，因為使用者沒有網域控制站的足夠權限。事件記錄檔可能有其他資訊。 |
The file replication service cannot satisfy the request because the user has insufficient privileges on the domain controller. The event log may have more information. |
| 0x1F4A | 檔案複寫服務無法滿足要求，因為在網域控制站上的驗證 RPC 無法使用。事件記錄檔可能有其他資訊。 |
The file replication service cannot satisfy the request because authenticated RPC is not available on the domain controller. The event log may have more information. |
| 0x1F4B | 檔案複寫服務無法與網域控制站的檔案複寫服務進行通訊。事件記錄檔可能有其他資訊。 |
The file replication service cannot communicate with the file replication service on the domain controller. The event log may have more information. |
| 0x1F4C | 網域控制站的檔案複寫服務無法與這台電腦的檔案複寫服務進行通訊。事件記錄檔可能有其他資訊。 |
The file replication service on the domain controller cannot communicate with the file replication service on this computer. The event log may have more information. |
| 0x1F4D | 檔案複寫服務無法填入系統磁碟區資料，因為發生內部錯誤。事件記錄檔可能有其他資訊。 |
The file replication service cannot populate the system volume because of an internal error. The event log may have more information. |
| 0x1F4E | 檔案複寫服務無法填入系統磁碟區資料，因為內部等候逾時。事件記錄檔可能有其他資訊。 |
The file replication service cannot populate the system volume because of an internal timeout. The event log may have more information. |
| 0x1F4F | 檔案複寫服務無法處理要求。系統磁碟區忙著處理前一個要求。 |
The file replication service cannot process the request. The system volume is busy with a previous request. |
| 0x1F50 | 檔案複寫服務無法停止系統磁碟區複寫，因為發生內部錯誤。事件記錄檔可能有其他資訊。 |
The file replication service cannot stop replicating the system volume because of an internal error. The event log may have more information. |
| 0x1F51 | 檔案複寫服務偵測出一個不正確的參數。 |
The file replication service detected an invalid parameter. |
| 0x2008 | 安裝目錄服務時發生錯誤。如需詳細資訊，請參閱事件記錄檔。 |
An error occurred while installing the directory service. For more information, see the event log. |
| 0x2009 | 目錄服務只在本機評估群組成員。 |
The directory service evaluated group memberships locally. |
| 0x200A | 指定的目錄服務屬性或服務值不存在。 |
The specified directory service attribute or value does not exist. |
| 0x200B | 目錄服務中所指定的屬性語法不正確。 |
The attribute syntax specified to the directory service is invalid. |
| 0x200C | 目錄服務中所指定的屬性類型並未定義。 |
The attribute type specified to the directory service is not defined. |
| 0x200D | 指定的目錄服務屬性或服務值已存在。 |
The specified directory service attribute or value already exists. |
| 0x200E | 目錄服務忙碌中。 |
The directory service is busy. |
| 0x200F | 目錄服務無法使用。 |
The directory service is unavailable. |
| 0x2010 | 目錄服務無法配置相關的識別元。 |
The directory service was unable to allocate a relative identifier. |
| 0x2011 | 目錄服務已用盡所有相關的識別元。 |
The directory service has exhausted the pool of relative identifiers. |
| 0x2012 | 要求的操作無法執行，因為目錄服務不是該操作的主要類型。 |
The requested operation could not be performed because the directory service is not the master for that type of operation. |
| 0x2013 | 目錄服務無法將配置了相關識別元的子系統初始化。 |
The directory service was unable to initialize the subsystem that allocates relative identifiers. |
| 0x2014 | 要求的操作不符合一個或多個與物件類別相關的限制。 |
The requested operation did not satisfy one or more constraints associated with the class of the object. |
| 0x2015 | 目錄服務只有在分葉物件中才能執行要求的操作。 |
The directory service can perform the requested operation only on a leaf object. |
| 0x2016 | 目錄服務無法在物件的 RDN 屬性上執行要求的操作。 |
The directory service cannot perform the requested operation on the RDN attribute of an object. |
| 0x2017 | 目錄服務偵測出曾嘗試修改物件的物件類別。 |
The directory service detected an attempt to modify the object class of an object. |
| 0x2018 | 無法執行要求的跨網域移動操作。 |
The requested cross-domain move operation could not be performed. |
| 0x2019 | 無法連絡通用類別目錄伺服器。 |
Unable to contact the global catalog server. |
| 0x201A | 原則物件已共用，而且只能在根目錄修改。 |
The policy object is shared and can only be modified at the root. |
| 0x201B | 原則物件不存在。 |
The policy object does not exist. |
| 0x201C | 要求的原則資訊只存在於目錄服務中。 |
The requested policy information is only in the directory service. |
| 0x201D | 網域控制站升級已在使用中。 |
A domain controller promotion is currently active. |
| 0x201E | 網域控制站升級目前不在使用中 |
A domain controller promotion is not currently active |
| 0x2020 | 發生一個操作錯誤。 |
An operations error occurred. |
| 0x2021 | 發生一個通訊協定錯誤。 |
A protocol error occurred. |
| 0x2022 | 這個要求超過時間限制。 |
The time limit for this request was exceeded. |
| 0x2023 | 這個要求超過大小限制。 |
The size limit for this request was exceeded. |
| 0x2024 | 這個要求超過系統管理限制。 |
The administrative limit for this request was exceeded. |
| 0x2025 | 比較的回應為偽。 |
The compare response was false. |
| 0x2026 | 比較的回應為真。 |
The compare response was true. |
| 0x2027 | 伺服器不支援要求的驗證方法。 |
The requested authentication method is not supported by the server. |
| 0x2028 | 這台伺服器需要其他安全性驗證方法。 |
A more secure authentication method is required for this server. |
| 0x2029 | 不適當的驗證。 |
Inappropriate authentication. |
| 0x202A | 驗證機制不明。 |
The authentication mechanism is unknown. |
| 0x202B | 從伺服器傳回一個轉介。 |
A referral was returned from the server. |
| 0x202C | 伺服器不支援要求的關鍵延伸。 |
The server does not support the requested critical extension. |
| 0x202D | 這個要求需要一個安全性連線。 |
This request requires a secure connection. |
| 0x202E | 不適當的對應。 |
Inappropriate matching. |
| 0x202F | 發生一個限制違規。 |
A constraint violation occurred. |
| 0x2030 | 伺服器中沒有這個物件。 |
There is no such object on the server. |
| 0x2031 | 別名有問題。 |
There is an alias problem. |
| 0x2032 | 指定一個不正確的 dn 語法。 |
An invalid dn syntax has been specified. |
| 0x2033 | 物件是一個分葉物件。 |
The object is a leaf object. |
| 0x2034 | 有一個別名解除參照的問題。 |
There is an alias dereferencing problem. |
| 0x2035 | 伺服器不願意處理此要求。 |
The server is unwilling to process the request. |
| 0x2036 | 偵測出一個迴圈。 |
A loop has been detected. |
| 0x2037 | 有一個命名違規。 |
There is a naming violation. |
| 0x2038 | 結果值太大。 |
The result set is too large. |
| 0x2039 | 操作影響數個 DSA |
The operation affects multiple DSAs |
| 0x203A | 無法操作伺服器。 |
The server is not operational. |
| 0x203B | 發生一個本機錯誤。 |
A local error has occurred. |
| 0x203C | 發生一個編碼錯誤。 |
An encoding error has occurred. |
| 0x203D | 發生一個解碼錯誤。 |
A decoding error has occurred. |
| 0x203E | 無法辨識搜尋篩選器。 |
The search filter cannot be recognized. |
| 0x203F | 一些參數不正確。 |
One or more parameters are illegal. |
| 0x2040 | 不支援指定的方法。 |
The specified method is not supported. |
| 0x2041 | 沒有傳回結果。 |
No results were returned. |
| 0x2042 | 伺服器不支援指定的控制。 |
The specified control is not supported by the server. |
| 0x2043 | 用戶端偵測出一個轉介迴圈。 |
A referral loop was detected by the client. |
| 0x2044 | 超過預設轉介限制。 |
The preset referral limit was exceeded. |
| 0x2045 | 這個搜尋需要 SORT 控制。 |
The search requires a SORT control. |
| 0x2046 | 搜尋結果超過所指定的位移範圍。 |
The search results exceed the offset range specified. |
| 0x2047 | 目錄服務偵測到配置相對識別碼的子系統已停用。當系統判斷大部分的相對識別碼 (RID) 已耗盡時，就會採取此保護機制。請瀏覽 http://go.microsoft.com/fwlink/?LinkId=228610，了解建議的診斷步驟以及重新建立帳戶的程序。 |
The directory service detected the subsystem that allocates relative identifiers is disabled. This can occur as a protective mechanism when the system determines a significant portion of relative identifiers (RIDs) have been exhausted. Please see http://go.microsoft.com/fwlink/?LinkId=228610 for recommended diagnostic steps and the procedure to re-enable account creation. |
| 0x206D | 根物件必須是最原始的命名內容。根物件不能含有繼承父系。 |
The root object must be the head of a naming context. The root object cannot have an instantiated parent. |
| 0x206E | 無法執行新增複本操作。命名內容必須是可寫入的屬性，才能建立複本。 |
The add replica operation cannot be performed. The naming context must be writeable in order to create the replica. |
| 0x206F | 參照的屬性在架構格式中並未定義。 |
A reference to an attribute that is not defined in the schema occurred. |
| 0x2070 | 已經超過物件容量最大值。 |
The maximum size of an object has been exceeded. |
| 0x2071 | 嘗試用已存在的物件名稱將物件新增到目錄中。 |
An attempt was made to add an object to the directory with a name that is already in use. |
| 0x2072 | 嘗試新增一個在架構格式中沒有 RDN 定義的類別物件。 |
An attempt was made to add an object of a class that does not have an RDN defined in the schema. |
| 0x2073 | 嘗試新增一個物件，但物件使用的 RDN 並未定義在架構格式中。 |
An attempt was made to add an object using an RDN that is not the RDN defined in the schema. |
| 0x2074 | 物件中找不到任何要求的屬性。 |
None of the requested attributes were found on the objects. |
| 0x2075 | 使用者緩衝區太小。 |
The user buffer is too small. |
| 0x2076 | 在操作中指定的屬性不存在於物件中。 |
The attribute specified in the operation is not present on the object. |
| 0x2077 | 不正確的修改操作。有些修改不被允許。 |
Illegal modify operation. Some aspect of the modification is not permitted. |
| 0x2078 | 指定的物件太大。 |
The specified object is too large. |
| 0x2079 | 指定的例項類型不正確。 |
The specified instance type is not valid. |
| 0x207A | 操作必須在主要 DSA 中執行。 |
The operation must be performed at a master DSA. |
| 0x207B | 必須指定物件類別屬性。 |
The object class attribute must be specified. |
| 0x207C | 必需的屬性遺失。 |
A required attribute is missing. |
| 0x207D | 嘗試修改物件，但物件包含一個不合法的類別屬性。 |
An attempt was made to modify an object to include an attribute that is not legal for its class. |
| 0x207E | 指定的屬性已經存在於物件中。 |
The specified attribute is already present on the object. |
| 0x2080 | 指定的屬性不存在，或缺少屬性值。 |
The specified attribute is not present, or has no values. |
| 0x2081 | 已將多重數值指定給只能擁有一個數值的屬性。 |
Multiple values were specified for an attribute that can have only one value. |
| 0x2082 | 屬性的數值不在可接受的數值範圍內。 |
A value for the attribute was not in the acceptable range of values. |
| 0x2083 | 指定的數值已經存在。 |
The specified value already exists. |
| 0x2084 | 無法移除屬性，因為它不存在於物件中。 |
The attribute cannot be removed because it is not present on the object. |
| 0x2085 | 無法移除屬性值，因為它不存在於物件中。 |
The attribute value cannot be removed because it is not present on the object. |
| 0x2086 | 指定的根物件不能是子參照物件。 |
The specified root object cannot be a subref. |
| 0x2087 | 不允許鏈結。 |
Chaining is not permitted. |
| 0x2088 | 不允許鏈結評估。 |
Chained evaluation is not permitted. |
| 0x2089 | 無法執行操作，因為物件的父系可能無法建立例項或已被刪除。 |
The operation could not be performed because the object's parent is either uninstantiated or deleted. |
| 0x208A | 父系不能是一個別名。別名只能用在分葉物件上。 |
Having a parent that is an alias is not permitted. Aliases are leaf objects. |
| 0x208B | 物件及父系必須是相同的類型，可以兩個都是主物件，或是兩個都是複製物件。 |
The object and parent must be of the same type, either both masters or both replicas. |
| 0x208C | 無法執行操作，因為子物件已存在。這項操作只能在分葉物件中執行。 |
The operation cannot be performed because child objects exist. This operation can only be performed on a leaf object. |
| 0x208D | 找不到目錄物件。 |
Directory object not found. |
| 0x208E | 別名物件遺失。 |
The aliased object is missing. |
| 0x208F | 物件名稱的語法錯誤。 |
The object name has bad syntax. |
| 0x2090 | 不允許一個別名再參照到其他別名。 |
It is not permitted for an alias to refer to another alias. |
| 0x2091 | 別名無法解除參照。 |
The alias cannot be dereferenced. |
| 0x2092 | 操作超出領域範圍。 |
The operation is out of scope. |
| 0x2093 | 操作無法繼續，因為物件正在移除的處理程序中。 |
The operation cannot continue because the object is in the process of being removed. |
| 0x2094 | 無法刪除 DSA 物件。 |
The DSA object cannot be deleted. |
| 0x2095 | 發生一個目錄服務錯誤。 |
A directory service error has occurred. |
| 0x2096 | 操作只能在內部主 DSA 物件中執行。 |
The operation can only be performed on an internal master DSA object. |
| 0x2097 | 物件必須屬於 DSA 類別。 |
The object must be of class DSA. |
| 0x2098 | 存取權限不足，無法執行操作。 |
Insufficient access rights to perform the operation. |
| 0x2099 | 無法新增物件，因為父系不在可能的上層清單中。 |
The object cannot be added because the parent is not on the list of possible superiors. |
| 0x209A | 不允許存取屬性，因為屬性是由安全性帳戶管理員 (SAM) 所擁有。 |
Access to the attribute is not permitted because the attribute is owned by the Security Accounts Manager (SAM). |
| 0x209B | 名稱含有太多部分。 |
The name has too many parts. |
| 0x209C | 名稱太長。 |
The name is too long. |
| 0x209D | 名稱值太長。 |
The name value is too long. |
| 0x209E | 目錄服務分析處理名稱時，遇到一個錯誤。 |
The directory service encountered an error parsing a name. |
| 0x209F | 目錄服務無法取得名稱的屬性類型。 |
The directory service cannot get the attribute type for a name. |
| 0x20A0 | 這個名稱並未指到物件。它指到一個虛設的項目。 |
The name does not identify an object; the name identifies a phantom. |
| 0x20A1 | 安全性描述元太短。 |
The security descriptor is too short. |
| 0x20A2 | 安全性描述元不正確。 |
The security descriptor is invalid. |
| 0x20A3 | 無法為已刪除的物件建立名稱。 |
Failed to create name for deleted object. |
| 0x20A4 | 新增子參照的父系必須存在。 |
The parent of a new subref must exist. |
| 0x20A5 | 物件必須是一個命名內容。 |
The object must be a naming context. |
| 0x20A6 | 不允許新增系統屬性。 |
It is not permitted to add an attribute which is owned by the system. |
| 0x20A7 | 物件類別必須是實體類別，您無法建立抽象類別的例項。 |
The class of the object must be structural; you cannot instantiate an abstract class. |
| 0x20A8 | 找不到架構物件。 |
The schema object could not be found. |
| 0x20A9 | 含有這個 GUID 的本機物件 (啟用中或停用中) 已經存在。 |
A local object with this GUID (dead or alive) already exists. |
| 0x20AA | 操作無法在上個連結中執行。 |
The operation cannot be performed on a back link. |
| 0x20AB | 找不到指定命名內容的交互參照。 |
The cross reference for the specified naming context could not be found. |
| 0x20AC | 操作無法執行，因為目錄服務已關閉。 |
The operation could not be performed because the directory service is shutting down. |
| 0x20AD | 目錄服務要求不正確。 |
The directory service request is invalid. |
| 0x20AE | 無法讀取角色擁有者的屬性。 |
The role owner attribute could not be read. |
| 0x20AF | 要求的 FSMO 操作失敗，無法連接目前的 FSMO 持有人。 |
The requested FSMO operation failed. The current FSMO holder could not be contacted. |
| 0x20B0 | 不能跨過命名內容來修改 DN。 |
Modification of a DN across a naming context is not permitted. |
| 0x20B1 | 無法修改屬性，因為它是系統屬性。 |
The attribute cannot be modified because it is owned by the system. |
| 0x20B2 | 只有複寫器可以執行這個功能。 |
Only the replicator can perform this function. |
| 0x20B3 | 指定的類別並未定義。 |
The specified class is not defined. |
| 0x20B4 | 指定的類別不是子類別。 |
The specified class is not a subclass. |
| 0x20B5 | 名稱參照不正確。 |
The name reference is invalid. |
| 0x20B6 | 交互參照已存在。 |
A cross reference already exists. |
| 0x20B7 | 不允許刪除主要交互參照。 |
It is not permitted to delete a master cross reference. |
| 0x20B8 | 樹狀子目錄通知只在 NC 頭上受到支援。 |
Subtree notifications are only supported on NC heads. |
| 0x20B9 | 通知篩選器太複雜。 |
Notification filter is too complex. |
| 0x20BA | 架構更新失敗: 重複的 RDN。 |
Schema update failed: duplicate RDN. |
| 0x20BB | 架構更新失敗: 重複的 OID。 |
Schema update failed: duplicate OID. |
| 0x20BC | 架構更新失敗: 重複的 Mapi 識別元。 |
Schema update failed: duplicate MAPI identifier. |
| 0x20BD | 架構更新失敗: 重複的 schema-id GUID。 |
Schema update failed: duplicate schema-id GUID. |
| 0x20BE | 架構更新失敗:重複的 ldap 顯示名稱。 |
Schema update failed: duplicate LDAP display name. |
| 0x20BF | 架構更新失敗: 下層範圍少於上層範圍。 |
Schema update failed: range-lower less than range upper. |
| 0x20C0 | 架構更新失敗: 語法不相符。 |
Schema update failed: syntax mismatch. |
| 0x20C1 | 架構刪除失敗: 屬性被用在 must-contain。 |
Schema deletion failed: attribute is used in must-contain. |
| 0x20C2 | 架構刪除失敗: 屬性被用在 may-contain。 |
Schema deletion failed: attribute is used in may-contain. |
| 0x20C3 | 架構更新失敗: 屬性在 may-contain 中不存在。 |
Schema update failed: attribute in may-contain does not exist. |
| 0x20C4 | 架構更新失敗: 屬性在 must-contain 中不存在。 |
Schema update failed: attribute in must-contain does not exist. |
| 0x20C5 | 架構更新失敗: 在 aux-class 清單中的類別不存在，或不是輔助類別。 |
Schema update failed: class in aux-class list does not exist or is not an auxiliary class. |
| 0x20C6 | 架構更新失敗: 類別在 poss-superiors 中不存在。 |
Schema update failed: class in poss-superiors does not exist. |
| 0x20C7 | 架構更新失敗: 類別在 subclassof 清單中不存在，或不符合階層規則。 |
Schema update failed: class in subclassof list does not exist or does not satisfy hierarchy rules. |
| 0x20C8 | 架構更新失敗: Rdn-Att-Id 語法錯誤。 |
Schema update failed: Rdn-Att-Id has wrong syntax. |
| 0x20C9 | 架構刪除失敗: 類別被用來當作輔助類別。 |
Schema deletion failed: class is used as auxiliary class. |
| 0x20CA | 架構刪除失敗: 類別被用來作為子類別。 |
Schema deletion failed: class is used as sub class. |
| 0x20CB | 架構刪除失敗: 類別被用來做為 poss 的上層。 |
Schema deletion failed: class is used as poss superior. |
| 0x20CC | 在重新計算快取確認時，架構更新失敗。 |
Schema update failed in recalculating validation cache. |
| 0x20CD | 尚未完成樹狀目錄刪除。必須再要求一次才能繼續刪除樹狀目錄。 |
The tree deletion is not finished. The request must be made again to continue deleting the tree. |
| 0x20CE | 無法執行要求的刪除操作。 |
The requested delete operation could not be performed. |
| 0x20CF | 無法讀取架構記錄的法定類別識別元。 |
Cannot read the governs class identifier for the schema record. |
| 0x20D0 | 屬性架構的語法錯誤。 |
The attribute schema has bad syntax. |
| 0x20D1 | 屬性無法進行快取處理。 |
The attribute could not be cached. |
| 0x20D2 | 類別無法進行快取處理。 |
The class could not be cached. |
| 0x20D3 | 無法從快取中移除屬性。 |
The attribute could not be removed from the cache. |
| 0x20D4 | 無法從快取中移除這個類別。 |
The class could not be removed from the cache. |
| 0x20D5 | 無法讀取這個分辨名稱的屬性。 |
The distinguished name attribute could not be read. |
| 0x20D6 | 尚未為目錄服務設定上層參照。目錄服務因此無法發行轉介給這個樹系外的物件。 |
No superior reference has been configured for the directory service. The directory service is therefore unable to issue referrals to objects outside this forest. |
| 0x20D7 | 無法抓取例項類型屬性。 |
The instance type attribute could not be retrieved. |
| 0x20D9 | 發生資料庫錯誤。 |
A database error has occurred. |
| 0x20DA | 屬性 GOVERNSID 遺失。 |
The attribute GOVERNSID is missing. |
| 0x20DB | 遺失一個必需屬性。 |
An expected attribute is missing. |
| 0x20DC | 指定的命名內容遺失一個交互參照。 |
The specified naming context is missing a cross reference. |
| 0x20DD | 發生一個安全性檢查錯誤。 |
A security checking error has occurred. |
| 0x20DE | 並未載入架構格式。 |
The schema is not loaded. |
| 0x20DF | 架構配置失敗。請檢查電腦記憶體是否太低。 |
Schema allocation failed. Please check if the machine is running low on memory. |
| 0x20E0 | 無法取得屬性架構的必要語法。 |
Failed to obtain the required syntax for the attribute schema. |
| 0x20E1 | 通用類別目錄驗證失敗。通用類別目錄無法使用，或不支援這項操作。部分的目錄目前無法使用。 |
The global catalog verification failed. The global catalog is not available or does not support the operation. Some part of the directory is currently not available. |
| 0x20E2 | 複寫操作失敗，因為架構格式和伺服器不相符。 |
The replication operation failed because of a schema mismatch between the servers involved. |
| 0x20E3 | 找不到 DSA 物件。 |
The DSA object could not be found. |
| 0x20E4 | 找不到命名內容。 |
The naming context could not be found. |
| 0x20E5 | 快取中找不到命名內容。 |
The naming context could not be found in the cache. |
| 0x20E6 | 無法抓取子物件。 |
The child object could not be retrieved. |
| 0x20E7 | 因為安全性的理由不允許修改。 |
The modification was not permitted for security reasons. |
| 0x20E8 | 操作無法取代隱藏的記錄。 |
The operation cannot replace the hidden record. |
| 0x20E9 | 階層檔案不正確。 |
The hierarchy file is invalid. |
| 0x20EA | 嘗試建立階層表格失敗。 |
The attempt to build the hierarchy table failed. |
| 0x20EB | 登錄中的目錄設定參數遺失。 |
The directory configuration parameter is missing from the registry. |
| 0x20EC | 嘗試計數通訊錄指示器失敗。 |
The attempt to count the address book indices failed. |
| 0x20ED | 階層表格配置失敗。 |
The allocation of the hierarchy table failed. |
| 0x20EE | 目錄服務遇到一個內部失敗。 |
The directory service encountered an internal failure. |
| 0x20EF | 目錄服務遇到一個不明的失敗。 |
The directory service encountered an unknown failure. |
| 0x20F0 | 根物件需要一個頂層類別。 |
A root object requires a class of 'top'. |
| 0x20F1 | 這個目錄伺服器正在關機，無法取得新的浮動單一主機操作角色的擁有權。 |
This directory server is shutting down, and cannot take ownership of new floating single-master operation roles. |
| 0x20F2 | 目錄服務遺失必要設定資訊，無法判定浮動單一主機操作角色的擁有權。 |
The directory service is missing mandatory configuration information, and is unable to determine the ownership of floating single-master operation roles. |
| 0x20F3 | 目錄服務無法將一或多個浮動單一主機操作角色的擁有權轉送到其他伺服器。 |
The directory service was unable to transfer ownership of one or more floating single-master operation roles to other servers. |
| 0x20F4 | 複寫操作失敗。 |
The replication operation failed. |
| 0x20F5 | 指定了不正確的參數給這項複寫操作。 |
An invalid parameter was specified for this replication operation. |
| 0x20F6 | 目錄服務太忙碌而無法完成這項複寫操作。 |
The directory service is too busy to complete the replication operation at this time. |
| 0x20F7 | 為這個複寫操作指定的分辨名稱不正確。 |
The distinguished name specified for this replication operation is invalid. |
| 0x20F8 | 為這個複寫操作指定的命名內容不正確。 |
The naming context specified for this replication operation is invalid. |
| 0x20F9 | 為這個複寫操作指定的分辨名稱已經存在。 |
The distinguished name specified for this replication operation already exists. |
| 0x20FA | 複寫系統發生一個內部錯誤。 |
The replication system encountered an internal error. |
| 0x20FB | 複寫操作發生資料庫不一致的情形。 |
The replication operation encountered a database inconsistency. |
| 0x20FC | 無法連接到指定給這項複寫操作的伺服器。 |
The server specified for this replication operation could not be contacted. |
| 0x20FD | 複寫操作遇到一個例項類型不正確的物件。 |
The replication operation encountered an object with an invalid instance type. |
| 0x20FE | 複寫操作無法配置記憶體。 |
The replication operation failed to allocate memory. |
| 0x20FF | 複寫操作發生郵件系統的錯誤。 |
The replication operation encountered an error with the mail system. |
| 0x2100 | 目標伺服器的複寫參照資訊已存在。 |
The replication reference information for the target server already exists. |
| 0x2101 | 目標伺服器的複寫參照資訊不存在。 |
The replication reference information for the target server does not exist. |
| 0x2102 | 無法移除命名內容，因為它已被複寫到另一台伺服器。 |
The naming context cannot be removed because it is replicated to another server. |
| 0x2103 | 複寫操作發生資料庫錯誤。 |
The replication operation encountered a database error. |
| 0x2104 | 命名內容已放在移除處理的程序中，或是並未從指定的伺服器複寫過來。 |
The naming context is in the process of being removed or is not replicated from the specified server. |
| 0x2105 | 複寫存取被拒。 |
Replication access was denied. |
| 0x2106 | 這一版目錄服務不支援要求的操作。 |
The requested operation is not supported by this version of the directory service. |
| 0x2107 | 複寫遠端程序呼叫已被取消。 |
The replication remote procedure call was cancelled. |
| 0x2108 | 來源伺服器目前拒絕複寫要求。 |
The source server is currently rejecting replication requests. |
| 0x2109 | 目的地伺服器目前拒絕複寫要求。 |
The destination server is currently rejecting replication requests. |
| 0x210A | 因為物件名稱的衝突，造成複寫操作失敗。 |
The replication operation failed due to a collision of object names. |
| 0x210B | 已重新安裝複寫來源。 |
The replication source has been reinstalled. |
| 0x210C | 因為要求的父系物件遺失，造成複寫操作失敗。 |
The replication operation failed because a required parent object is missing. |
| 0x210D | 優先執行這項複寫操作。 |
The replication operation was preempted. |
| 0x210E | 因為缺乏更新，而放棄複寫同步化嘗試。 |
The replication synchronization attempt was abandoned because of a lack of updates. |
| 0x210F | 因為系統正在關機，造成複寫操作終止。 |
The replication operation was terminated because the system is shutting down. |
| 0x2110 | 同步處理常式失敗，因為目標 DC 目前正在等待同步處理來自資源新的部分屬性。如果最近的架構變更修改了這部分的屬性組的話，這個情形是正常的。目標部分屬性組不是來源部分屬性組的子集合。 |
Synchronization attempt failed because the destination DC is currently waiting to synchronize new partial attributes from source. This condition is normal if a recent schema change modified the partial attribute set. The destination partial attribute set is not a subset of source partial attribute set. |
| 0x2111 | 複寫同步處理常式失敗，因為嘗試將從附屬複本對主複本進行同步。 |
The replication synchronization attempt failed because a master replica attempted to sync from a partial replica. |
| 0x2112 | 已連接到這個複寫操作所指定的伺服器，但伺服器無法連絡其他完成操作所需要的伺服器。 |
The server specified for this replication operation was contacted, but that server was unable to contact an additional server needed to complete the operation. |
| 0x2113 | 來源樹系的目錄服務架構版本與這台電腦的目錄服務版本不相容。 |
The version of the directory service schema of the source forest is not compatible with the version of directory service on this computer. |
| 0x2114 | 架構更新失敗: 含有相同的連結識別元的屬性已存在。 |
Schema update failed: An attribute with the same link identifier already exists. |
| 0x2115 | 名稱轉譯: 一般處理錯誤。 |
Name translation: Generic processing error. |
| 0x2116 | 名稱轉譯: 找不到名稱或沒有查看名稱的權限。 |
Name translation: Could not find the name or insufficient right to see name. |
| 0x2117 | 名稱轉譯: 輸入名稱對應到多於一個的輸出名稱。 |
Name translation: Input name mapped to more than one output name. |
| 0x2118 | 名稱轉譯: 找到所輸入的名稱，但不是相關聯的輸出格式。 |
Name translation: Input name found, but not the associated output format. |
| 0x2119 | 名稱轉譯: 無法完全解析，找到單一網域。 |
Name translation: Unable to resolve completely, only the domain was found. |
| 0x211A | 名稱轉譯: 無法只在用戶端執行純粹語法上的對應。 |
Name translation: Unable to perform purely syntactical mapping at the client without going out to the wire. |
| 0x211B | 不允許修改已建立好的屬性。 |
Modification of a constructed attribute is not allowed. |
| 0x211C | 指定的 OM-Object-Class 屬性指定語法不正確。 |
The OM-Object-Class specified is incorrect for an attribute with the specified syntax. |
| 0x211D | 已經發出複寫要求; 正在等待回覆。 |
The replication request has been posted; waiting for reply. |
| 0x211E | 要求的操作需要目錄服務，但是沒有可用的目錄服務。 |
The requested operation requires a directory service, and none was available. |
| 0x211F | LDAP 顯示類別名稱或屬性包含非 ASCII 碼的字元。 |
The LDAP display name of the class or attribute contains non-ASCII characters. |
| 0x2120 | 只有在基本搜尋時，您要求的搜尋操作才能獲得支援。 |
The requested search operation is only supported for base searches. |
| 0x2121 | 搜尋無法從資料庫中抓取屬性。 |
The search failed to retrieve attributes from the database. |
| 0x2122 | 架構更新操作嘗試加入一個反向連結屬性，但這連結屬性缺少相對的正向連結。 |
The schema update operation tried to add a backward link attribute that has no corresponding forward link. |
| 0x2123 | 來源和目的地的跨網域移動均不同意物件的 epoch 編號。可能是來源或目的地沒有最新版本的物件。 |
Source and destination of a cross-domain move do not agree on the object's epoch number. Either source or destination does not have the latest version of the object. |
| 0x2124 | 來源和目的地的跨網域移動並沒有同意物件的 epoch 編號。可能是來源或目的地沒有最新版本的物件。 |
Source and destination of a cross-domain move do not agree on the object's current name. Either source or destination does not have the latest version of the object. |
| 0x2125 | 跨網域移動的來源和目的地相同。呼叫者應該使用本機移動的操作來取代原先跨網域移動的操作。 |
Source and destination for the cross-domain move operation are identical. Caller should use local move operation instead of cross-domain move operation. |
| 0x2126 | 跨網域移動的來源和目的地均不同意樹系的命名內容。呼叫者應該使用本機移動的操作來取代原先跨網域移動的操作。可能是來源或目的地沒有最新版本的分割容器。 |
Source and destination for a cross-domain move are not in agreement on the naming contexts in the forest. Either source or destination does not have the latest version of the Partitions container. |
| 0x2127 | 跨網域移動的目的地不是授權的目的地命名內容。 |
Destination of a cross-domain move is not authoritative for the destination naming context. |
| 0x2128 | 跨網域移動的來源和目的地均不同意來源物件的身分識別。可能是來源或目的地沒有最新版本的來源物件。 |
Source and destination of a cross-domain move do not agree on the identity of the source object. Either source or destination does not have the latest version of the source object. |
| 0x2129 | 目的地的伺服器已經刪除跨網域移動的物件。來源的伺服器沒有最新版本的來源物件。 |
Object being moved across-domains is already known to be deleted by the destination server. The source server does not have the latest version of the source object. |
| 0x212A | 另一個操作正對 PDC FSMO 進行獨佔式存取要求。 |
Another operation which requires exclusive access to the PDC FSMO is already in progress. |
| 0x212B | 跨網域移動操作失敗，因為兩個移動物件的版本分別存在於來源和目的地中。目的地中的物件必須移除，系統才能還原到一致的狀態。 |
A cross-domain move operation failed such that two versions of the moved object exist - one each in the source and destination domains. The destination object needs to be removed to restore the system to a consistent state. |
| 0x212C | 這個物件可能無法移動過網域界限。原因可能是不允許跨網域移動，或者物件包含有限制移動的特殊字元，例如: trust account 或 restricted RID。 |
This object may not be moved across domain boundaries either because cross-domain moves for this class are disallowed, or the object has some special characteristics, e.g.: trust account or restricted RID, which prevent its move. |
| 0x212D | 這個物件和它的成員資格無法移動過網域界限。這個移動是違反該帳戶群組的成員資格條件。請從所有的帳戶群組中移除這個物件，重新再試。 |
Can't move objects with memberships across domain boundaries as once moved, this would violate the membership conditions of the account group. Remove the object from any account group memberships and retry. |
| 0x212E | 一個命名內容標頭必須以子連結方式指到最靠近的命名內容的標頭，而不是內部的節點。 |
A naming context head must be the immediate child of another naming context head, not of an interior node. |
| 0x212F | 目錄無法確認提議的命名內容名稱，因為它不能在提議的命名內容上執行複寫。請確認網域命名主機角色是由設定為通用類別目錄伺服器所執行，而且此伺服器與複寫協力電腦同步。(只適用於 Windows 2000 網域命名主機) |
The directory cannot validate the proposed naming context name because it does not hold a replica of the naming context above the proposed naming context. Please ensure that the domain naming master role is held by a server that is configured as a global catalog server, and that the server is up to date with its replication partners. (Applies only to Windows 2000 Domain Naming masters) |
| 0x2130 | 目的地網域必須處於原生模式。 |
Destination domain must be in native mode. |
| 0x2131 | 無法執行這個操作，因相關網域中的伺服器沒有基礎架構容器。 |
The operation cannot be performed because the server does not have an infrastructure container in the domain of interest. |
| 0x2132 | 含有帳戶的帳戶群組不能作跨網域移動。 |
Cross-domain move of non-empty account groups is not allowed. |
| 0x2133 | 含有資源的資源群組不能作跨網域移動。 |
Cross-domain move of non-empty resource groups is not allowed. |
| 0x2134 | 這個屬性的搜尋旗標不正確。ANR 位元只有在 Unicode 屬性或 Teletex 字串時有效。 |
The search flags for the attribute are invalid. The ANR bit is valid only on attributes of Unicode or Teletex strings. |
| 0x2135 | 不允許由以 NC 表頭為繼承的物件啟動的樹狀目錄刪除。 |
Tree deletions starting at an object which has an NC head as a descendant are not allowed. |
| 0x2136 | 目錄服務在準備刪除樹狀目錄時無法鎖定樹狀目錄，因為這個樹狀目錄正在使用中。 |
The directory service failed to lock a tree in preparation for a tree deletion because the tree was in use. |
| 0x2137 | 嘗試刪除樹狀目錄時，目錄服務無法找出要刪除的物件清單。 |
The directory service failed to identify the list of objects to delete while attempting a tree deletion. |
| 0x2138 | 安全性帳戶管理員初始化失敗，因為發生下列錯誤: %1。錯誤狀態: 0x%2。請將系統關機，並重新開機成目錄服務還原模式，然後檢查事件記錄檔，以取得詳細資訊。 |
Security Accounts Manager initialization failed because of the following error: %1.Error Status: 0x%2. Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information. |
| 0x2139 | 只有系統管理員才能修改系統管理群組的成員資格清單。 |
Only an administrator can modify the membership list of an administrative group. |
| 0x213A | 無法變更網域控制站帳戶的主要群組識別碼。 |
Cannot change the primary group ID of a domain controller account. |
| 0x213B | 嘗試修改基本架構。 |
An attempt is made to modify the base schema. |
| 0x213C | 不允許新增強制屬性到現存類別、從現存類別刪除強制屬性、或將選擇性屬性新增到不是 backlink 屬性 (直接或透過繼承，例如新增或刪除輔助類別) 的特殊類別端。 |
Adding a new mandatory attribute to an existing class, deleting a mandatory attribute from an existing class, or adding an optional attribute to the special class Top that is not a backlink attribute (directly or through inheritance, for example, by adding or deleting an auxiliary class) is not allowed. |
| 0x213D | 不容許在這個 DC 執行架構更新。可能登錄機碼尚未設定或 DC 不是架構 FSMO 角色擁有者。 |
Schema update is not allowed on this DC because the DC is not the schema FSMO Role Owner. |
| 0x213E | 在此架構容器下，無法建立此類別的物件。您只能在此架構容器內建立屬性-架構和類別-架構物件。 |
An object of this class cannot be created under the schema container. You can only create attribute-schema and class-schema objects under the schema container. |
| 0x213F | [複寫/子係] 安裝無法取得來源 DC 架構容器上的物件版本屬性。可能是架構容器的屬性遺失了或套用的認證無權讀取它。 |
The replica/child install failed to get the objectVersion attribute on the schema container on the source DC. Either the attribute is missing on the schema container or the credentials supplied do not have permission to read it. |
| 0x2140 | [複寫/子係] 安裝無法讀取目錄 system32 檔案 schema.ini 中 SCHEMA 區段的物件版本屬性。 |
The replica/child install failed to read the objectVersion attribute in the SCHEMA section of the file schema.ini in the system32 directory. |
| 0x2141 | 指定的群組類型不正確。 |
The specified group type is invalid. |
| 0x2142 | 如果群組的安全性已啟用，在混合網域中，您無法將本機群組與其他本機群組放在一起。 |
You cannot nest global groups in a mixed domain if the group is security-enabled. |
| 0x2144 | 本機群組不可以是通用群組的成員。 |
A global group cannot have a local group as a member. |
| 0x2145 | 萬用群組不可以是通用群組的成員。 |
A global group cannot have a universal group as a member. |
| 0x2146 | 本機群組不可以是萬用群組的成員。 |
A universal group cannot have a local group as a member. |
| 0x2147 | 通用群組不可以有跨網域成員。 |
A global group cannot have a cross-domain member. |
| 0x2148 | 本機群組不可以有另一個跨網域的本機群組作為成員。 |
A local group cannot have another cross domain local group as a member. |
| 0x2149 | 這個群組內有主要成員，無法變更安全性已停用的群組。 |
A group with primary members cannot change to a security-disabled group. |
| 0x214A | 架構快取載入無法轉換等級-架構物件上的字串預設 SD。 |
The schema cache load failed to convert the string default SD on a class-schema object. |
| 0x214B | 只有被設定成通用類別目錄伺服器的 DSA，才能擔任網域命名主機 FSMO 的角色。(只適用於 Windows 2000 伺服器) |
Only DSAs configured to be Global Catalog servers should be allowed to hold the Domain Naming Master FSMO role. (Applies only to Windows 2000 servers) |
| 0x214C | DSA 操作無法繼續，因為 DNS 查閱失敗。 |
The DSA operation is unable to proceed because of a DNS lookup failure. |
| 0x214D | 當物件正在進行變更成 DNS 主機名稱，服務主體名稱值無法保持同步。 |
While processing a change to the DNS Host Name for an object, the Service Principal Name values could not be kept in sync. |
| 0x214E | 無法讀取安全性描述元的屬性。 |
The Security Descriptor attribute could not be read. |
| 0x214F | 找不到要求的物件，但找到具有該機碼的物件。 |
The object requested was not found, but an object with that key was found. |
| 0x2150 | 新增的連結屬性語法不正確。正向連結的語法只能為 2.5.5.1、2.5.5.7、及 2.5.5.14，且反向連結的語法只能為 2.5.5.1 |
The syntax of the linked attribute being added is incorrect. Forward links can only have syntax 2.5.5.1, 2.5.5.7, and 2.5.5.14, and backlinks can only have syntax 2.5.5.1 |
| 0x2151 | 安全性帳戶管理員需要取得開機密碼。 |
Security Account Manager needs to get the boot password. |
| 0x2152 | 安全性帳戶管理員需要從磁片取得開機識別碼。 |
Security Account Manager needs to get the boot key from floppy disk. |
| 0x2153 | 目錄服務無法啟動。 |
Directory Service cannot start. |
| 0x2155 | 用戶端與伺服器間的連線需要封包私密性或更佳的保護。 |
The connection between client and server requires packet privacy or better. |
| 0x2156 | 來源網域和目的地網域可能不在同一樹系中。 |
The source domain may not be in the same forest as destination. |
| 0x2157 | 目的地網域必須在樹系中。 |
The destination domain must be in the forest. |
| 0x2158 | 操作需要已啟動稽核的目的地網域。 |
The operation requires that destination domain auditing be enabled. |
| 0x2159 | 操作找不到來源網域的 DC。 |
The operation couldn't locate a DC for the source domain. |
| 0x215A | 來源物件必須是個群組或使用者。 |
The source object must be a group or user. |
| 0x215B | 目的地樹系中已經有來源物件的 SID。 |
The source object's SID already exists in destination forest. |
| 0x215C | 來源和目的地物件必須類型相同。 |
The source and destination object must be of the same type. |
| 0x215D | 安全性帳戶管理員初始化失敗，因為發生下列錯誤: %1。錯誤狀態: 0x%2。請按 [確定] 將系統關機，並重新開機至 [安全模式]。請檢查事件記錄檔以取得詳細資訊。 |
Security Accounts Manager initialization failed because of the following error: %1.Error Status: 0x%2. Click OK to shut down the system and reboot into Safe Mode. Check the event log for detailed information. |
| 0x215E | 架構資訊不可包含在複寫要求中。 |
Schema information could not be included in the replication request. |
| 0x215F | 因為架構不相容，無法完成複寫操作。 |
The replication operation could not be completed due to a schema incompatibility. |
| 0x2160 | 因為之前的架構不相容，無法完成複寫操作。 |
The replication operation could not be completed due to a previous schema incompatibility. |
| 0x2161 | 無法套用複寫更新，因為來源或目的地尚未收到關於最近跨網域移動操作的資訊。 |
The replication update could not be applied because either the source or the destination has not yet received information regarding a recent cross-domain move operation. |
| 0x2162 | 無法刪除要求的網域，因為存在的網域控制站仍然主控這個網域。 |
The requested domain could not be deleted because there exist domain controllers that still host this domain. |
| 0x2163 | 要求的操作只能在通用類別目錄伺服器上執行。 |
The requested operation can be performed only on a global catalog server. |
| 0x2164 | 本機群組只能是同樣網域的其他本機群組的成員。 |
A local group can only be a member of other local groups in the same domain. |
| 0x2165 | 外部安全性主體不可以是萬用群組的成員。 |
Foreign security principals cannot be members of universal groups. |
| 0x2166 | 基於安全性因素，不容許屬性複寫到 GC。 |
The attribute is not allowed to be replicated to the GC because of security reasons. |
| 0x2167 | 因為目前正在處理許多修正，不可取走 PDC 檢查點。 |
The checkpoint with the PDC could not be taken because there too many modifications being processed currently. |
| 0x2168 | 操作需要來源網域的稽核被啟用。 |
The operation requires that source domain auditing be enabled. |
| 0x2169 | 安全性主體物件只能建立在網域命名內容中。 |
Security principal objects can only be created inside domain naming contexts. |
| 0x216A | 無法建立服務主體名稱 (SPN)，因為提供的主機名稱不是需要的格式。 |
A Service Principal Name (SPN) could not be constructed because the provided hostname is not in the necessary format. |
| 0x216B | 通過了一個使用建構屬性的篩選器。 |
A Filter was passed that uses constructed attributes. |
| 0x216C | unicodePwd 屬性值必須包含在雙引號內。 |
The unicodePwd attribute value must be enclosed in double quotes. |
| 0x216D | 您的電腦無法加入網域。因為您已經超過這個網域所允許建立的電腦帳戶上限。請連絡您的系統管理員，重設或提高這個限制。 |
Your computer could not be joined to the domain. You have exceeded the maximum number of computer accounts you are allowed to create in this domain. Contact your system administrator to have this limit reset or increased. |
| 0x216E | 因為安全性的緣故，這個操作必須在目的 DC 上執行。 |
For security reasons, the operation must be run on the destination DC. |
| 0x216F | 因為安全性的緣故，來源 DC 必須是 NT4SP4 或更新的版本。 |
For security reasons, the source DC must be NT4SP4 or greater. |
| 0x2170 | 執行樹狀目錄刪除操作時，無法刪除關鍵目錄服務系統物件。可能已執行部分的樹狀目錄刪除操作。 |
Critical Directory Service System objects cannot be deleted during tree delete operations. The tree delete may have been partially performed. |
| 0x2171 | 無法啟動目錄服務，這是由於以下錯誤: %1。錯誤狀態: 0x%2。請按 [確定] 以便關機。您可以使用修復主控台進一步診斷系統。 |
Directory Services could not start because of the following error: %1.Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further. |
| 0x2172 | 無法初始化安全性帳戶管理員，這是由於以下錯誤: %1。錯誤狀態: 0x%2。請按 [確定] 以便關機。您可以使用修復主控台進一步診斷系統。 |
Security Accounts Manager initialization failed because of the following error: %1.Error Status: 0x%2. Please click OK to shutdown the system. You can use the recovery console to diagnose the system further. |
| 0x2173 | 作業系統版本與目前的 AD DS 樹系功能等級或 AD LDS 組態集功能等級不相容。在這個伺服器可以成為 AD DS 網域控制站，或是在這個 AD DS 樹系或 AD LDS 組態集中新增 AD LDS 執行個體之前，您必須先升級到新版的作業系統。 |
The version of the operating system is incompatible with the current AD DS forest functional level or AD LDS Configuration Set functional level. You must upgrade to a new version of the operating system before this server can become an AD DS Domain Controller or add an AD LDS Instance in this AD DS Forest or AD LDS Configuration Set. |
| 0x2174 | 所安裝的作業系統版本和目前網域的功能等級不相容。在這個伺服器可以成為樹系中的網域控制站之前，您必須先升級到新版的作業系統。 |
The version of the operating system installed is incompatible with the current domain functional level. You must upgrade to a new version of the operating system before this server can become a domain controller in this domain. |
| 0x2175 | 這個伺服器上所安裝的作業系統版本已不再支援目前 AD DS 樹系功能等級或 AD LDS 組態集功能等級。在這個伺服器可以成為 AD DS 網域控制站或是此樹系或組態集的 AD LDS 執行個體之前，您必須先提升 AD DS 樹系功能等級或 AD LDS 組態集功能等級。 |
The version of the operating system installed on this server no longer supports the current AD DS Forest functional level or AD LDS Configuration Set functional level. You must raise the AD DS Forest functional level or AD LDS Configuration Set functional level before this server can become an AD DS Domain Controller or an AD LDS Instance in this Forest or Configuration Set. |
| 0x2176 | 這個伺服器上所安裝的作業系統版本已不再支援目前網域的功能等級。在這個伺服器可以成為樹系中的網域控制站之前，您必須先提升網域的功能等級。 |
The version of the operating system installed on this server no longer supports the current domain functional level. You must raise the domain functional level before this server can become a domain controller in this domain. |
| 0x2177 | 這個伺服器上所安裝的作業系統版本與網域或樹系的功能等級不相容。 |
The version of the operating system installed on this server is incompatible with the functional level of the domain or forest. |
| 0x2178 | 無法提升網域 (或樹系) 的功能等級到要求的數值，因為在網域 (或樹系) 中存在一或多個網域控制站處於較低不相容的功能等級。 |
The functional level of the domain (or forest) cannot be raised to the requested value, because there exist one or more domain controllers in the domain (or forest) that are at a lower incompatible functional level. |
| 0x2179 | 無法提升樹系功能等級到要求的數值，因為一或多個網域仍然處於混和的網域模式。所有在樹系中的網域必須是在原生模式，您才能提升樹系的功能等級。 |
The forest functional level cannot be raised to the requested value since one or more domains are still in mixed domain mode. All domains in the forest must be in native mode, for you to raise the forest functional level. |
| 0x217A | 不支援所要求的排序方式。 |
The sort order requested is not supported. |
| 0x217B | 要求的名稱已以唯一識別碼存在。 |
The requested name already exists as a unique identifier. |
| 0x217C | 電腦帳戶是在 NT4 以前的作業系統上所建立。需要重新建立該帳戶。 |
The machine account was created pre-NT4. The account needs to be recreated. |
| 0x217D | 資料庫已用盡版本存放。 |
The database is out of version store. |
| 0x217E | 無法繼續操作，原因是使用了數個相衝突的控制項。 |
Unable to continue operation because multiple conflicting controls were used. |
| 0x217F | 找不到這個分割的正確安全性描述元參照網域。 |
Unable to find a valid security descriptor reference domain for this partition. |
| 0x2180 | 架構更新失敗: 已保留連結識別元。 |
Schema update failed: The link identifier is reserved. |
| 0x2181 | 架構更新失敗: 沒有可用的連結識別元。 |
Schema update failed: There are no link identifiers available. |
| 0x2182 | 帳戶群組不能將萬用群組視為成員。 |
An account group cannot have a universal group as a member. |
| 0x2183 | 不允許在命名內容標頭或唯讀物件上重新命名或移動操作。 |
Rename or move operations on naming context heads or read-only objects are not allowed. |
| 0x2184 | 不允許在架構命名內容的物件上移動操作。 |
Move operations on objects in the schema naming context are not allowed. |
| 0x2185 | 物件上已經設有系統旗標，不允許移動或重新命名該物件。 |
A system flag has been set on the object and does not allow the object to be moved or renamed. |
| 0x2186 | 不允許這個物件變更其上二層容器。並不禁止移動這個物件，但是只限於同層容器。 |
This object is not allowed to change its grandparent container. Moves are not forbidden on this object, but are restricted to sibling containers. |
| 0x2187 | 無法完全解析，已產生其他樹系參照。 |
Unable to resolve completely, a referral to another forest is generated. |
| 0x2188 | 所要求的操作不受標準伺服器支援。 |
The requested action is not supported on standard server. |
| 0x2189 | 無法存取位於遠端伺服器的目錄服務分割。請確定至少有一台伺服器正在請求的分割中執行。 |
Could not access a partition of the directory service located on a remote server. Make sure at least one server is running for the partition in question. |
| 0x218A | 目錄無法確認所提議的命名內容 (或分割) 的名稱，因為它沒有複本，也無法連絡到所提議命名內容的命名內容複本。請確認上層命名內容已正確登錄在 DNS，而且網域名稱主管理員能夠連接到至少一個這個命名內容的複本。 |
The directory cannot validate the proposed naming context (or partition) name because it does not hold a replica nor can it contact a replica of the naming context above the proposed naming context. Please ensure that the parent naming context is properly registered in DNS, and at least one replica of this naming context is reachable by the Domain Naming master. |
| 0x218B | 這個要求已經超過執行緒限制。 |
The thread limit for this request was exceeded. |
| 0x218C | 通用類別目錄伺服器不在最近的站台。 |
The Global catalog server is not in the closest site. |
| 0x218D | DS 無法繼承服務主體名稱 (SPN) 以便用來互相驗證目標伺服器，因為在本機 DS 資料庫的對應伺服器物件沒有伺服器參照屬性。 |
The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the corresponding server object in the local DS database has no serverReference attribute. |
| 0x218E | 目錄服務無法進入單一使用者模式。 |
The Directory Service failed to enter single user mode. |
| 0x218F | 目錄服務因為語法錯誤而無法剖析指令碼。 |
The Directory Service cannot parse the script because of a syntax error. |
| 0x2190 | 目錄服務因為錯誤而無法處理指令碼。 |
The Directory Service cannot process the script because of an error. |
| 0x2191 | 目錄服務無法執行要求的操作，因為有關的伺服器是不同的複寫 epoch (一般與進行中的網域重新命名有關)。 |
The directory service cannot perform the requested operation because the servers involved are of different replication epochs (which is usually related to a domain rename that is in progress). |
| 0x2192 | 因為伺服器擴充資訊有變更，目錄服務繫結必須重新交涉。 |
The directory service binding must be renegotiated due to a change in the server extensions information. |
| 0x2193 | 在停用的交叉參照上不允許的操作。 |
Operation not allowed on a disabled cross ref. |
| 0x2194 | 架構更新失敗: 沒有 msDS-IntId 可用的數值。 |
Schema update failed: No values for msDS-IntId are available. |
| 0x2195 | 架構更新失敗: 重覆的 msDS-INtId。重試這項操作。 |
Schema update failed: Duplicate msDS-INtId. Retry the operation. |
| 0x2196 | 架構刪除失敗: 屬性被用在 rDNAttID。 |
Schema deletion failed: attribute is used in rDNAttID. |
| 0x2197 | 目錄服務無法授權這個要求。 |
The directory service failed to authorize the request. |
| 0x2198 | 目錄服務因為指令碼不正確而無法處理。 |
The Directory Service cannot process the script because it is invalid. |
| 0x2199 | 遠端建立交叉參照操作失敗於 Domain Naming Master FSMO。操作的錯誤是在延伸資料中。 |
The remote create cross reference operation failed on the Domain Naming Master FSMO. The operation's error is in the extended data. |
| 0x219A | 交叉參照在本機以相同名稱使用中。 |
A cross reference is in use locally with the same name. |
| 0x219B | DS 無法繼承用來相互驗證目標伺服器的服務主體名稱 (SPN)，因為伺服器的網域已?樹系中刪除。 |
The DS cannot derive a service principal name (SPN) with which to mutually authenticate the target server because the server's domain has been deleted from the forest. |
| 0x219C | 可寫入的 NC 妨礙這個 DC 降級。 |
Writeable NCs prevent this DC from demoting. |
| 0x219D | 要求的物件具有非唯一識別碼，無法抓取。 |
The requested object has a non-unique identifier and cannot be retrieved. |
| 0x219E | 給予了不足夠的屬性來建立物件，這個物件可能不存在，因為它可能已被刪除且已被當廢棄項目收集。 |
Insufficient attributes were given to create an object. This object may not exist because it may have been deleted and already garbage collected. |
| 0x219F | 基於所要求群組類型上的屬性限制，群組無法轉換。 |
The group cannot be converted due to attribute restrictions on the requested group type. |
| 0x21A0 | 不允許非空的基本應用程式群組的跨網域移動。 |
Cross-domain move of non-empty basic application groups is not allowed. |
| 0x21A1 | 不允許非空的查詢為主應用程式群組的跨網域移動。 |
Cross-domain move of non-empty query based application groups is not allowed. |
| 0x21A2 | 無法確認 FSMO 角色擁有權，因其目錄分割尚未以至少一個複寫協力電腦成功複寫。 |
The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner. |
| 0x21A3 | 眾所熟知物件容器的重新導向的目標容器不能是特別容器。 |
The target container for a redirection of a well known object container cannot already be a special container. |
| 0x21A4 | 目錄服務無法執行要求的操作，因為正在進行網域重新命名操作。 |
The Directory Service cannot perform the requested operation because a domain rename operation is in progress. |
| 0x21A5 | 目錄服務已在要求的分割名稱下偵測到子分割。必須以從上到下的方式建立分割階層。 |
The directory service detected a child partition below the requested partition name. The partition hierarchy must be created in a top down method. |
| 0x21A6 | 因為和這個伺服器複寫的時間已經超過標記存留期，目錄服務無法和這個伺服器複寫。 |
The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime. |
| 0x21A7 | 在系統容器下的物件上，不允許所要求的操作。 |
The requested operation is not allowed on an object under the system container. |
| 0x21A8 | LDAP 伺服器網路傳送佇列已裝滿，因為用戶端處理它的要求結果不夠快。在用戶端進度趕上前，不會再處理任何要求。如果用戶端無法趕上，它將會被中斷連線。 |
The LDAP servers network send queue has filled up because the client is not processing the results of its requests fast enough. No more requests will be processed until the client catches up. If the client does not catch up then it will be disconnected. |
| 0x21A9 | 排定的複寫未執行，因為系統太忙碌而無法在排定的時間內執行這個要求。複寫佇列已超載。請考慮降低協力電腦數目或減少排定複寫的頻率。 |
The scheduled replication did not take place because the system was too busy to execute the request within the schedule window. The replication queue is overloaded. Consider reducing the number of partners or decreasing the scheduled replication frequency. |
| 0x21AA | 此時，無法判斷是否中樞網域控制站上具有分支複寫原則。考慮到會發生複寫延遲，請稍後再試一次。 |
At this time, it cannot be determined if the branch replication policy is available on the hub domain controller. Please retry at a later time to account for replication latencies. |
| 0x21AB | 指定站台的站台設定物件不存在。 |
The site settings object for the specified site does not exist. |
| 0x21AC | 本機帳戶存放區不包含指定帳戶的密碼資料。 |
The local account store does not contain secret material for the specified account. |
| 0x21AD | 在網域中找不到可寫入的網域控制站。 |
Could not find a writable domain controller in the domain. |
| 0x21AE | 網域控制站的伺服器物件不存在。 |
The server object for the domain controller does not exist. |
| 0x21AF | 網域控制站的 NTDS 設定物件不存在。 |
The NTDS Settings object for the domain controller does not exist. |
| 0x21B0 | 要求的搜尋作業不支援 ASQ 搜尋。 |
The requested search operation is not supported for ASQ searches. |
| 0x21B1 | 無法為作業產生需要的稽核事件。 |
A required audit event could not be generated for the operation. |
| 0x21B2 | 屬性的搜尋旗標無效。子樹狀目索引位元組只有在單一值屬性中有效。 |
The search flags for the attribute are invalid. The subtree index bit is valid only on single valued attributes. |
| 0x21B3 | 屬性的搜尋旗標無效。集合索引位元組只有在 Unicode 字串的屬性中有效。 |
The search flags for the attribute are invalid. The tuple index bit is valid only on attributes of Unicode strings. |
| 0x21B4 | 通訊錄巢狀結構太深。無法建立階層表格。 |
The address books are nested too deeply. Failed to build the hierarchy table. |
| 0x21B5 | 指定的 up-to-date-ness 向量已損毀。 |
The specified up-to-date-ness vector is corrupt. |
| 0x21B6 | 複寫秘密的要求被拒絕。 |
The request to replicate secrets is denied. |
| 0x21B7 | 結構描述更新失敗: 已保留 MAPI 識別碼。 |
Schema update failed: The MAPI identifier is reserved. |
| 0x21B8 | 結構描述更新失敗: 沒有可用的 MAPI 識別碼。 |
Schema update failed: There are no MAPI identifiers available. |
| 0x21B9 | 複寫操作失敗，因為遺失本機 krbtgt 物件的必要屬性遺失。 |
The replication operation failed because the required attributes of the local krbtgt object are missing. |
| 0x21BA | 樹系中已經有受信任網域的網域名稱。 |
The domain name of the trusted domain already exists in the forest. |
| 0x21BB | 樹系中已經有受信任網域的一般名稱。 |
The flat name of the trusted domain already exists in the forest. |
| 0x21BC | 使用者主體名稱 (UPN) 不正確。 |
The User Principal Name (UPN) is invalid. |
| 0x21BD | OID 對應的群組不能包含成員。 |
OID mapped groups cannot have members. |
| 0x21BE | 找不到指定的 OID。 |
The specified OID cannot be found. |
| 0x21BF | 複寫操作失敗，因為連結值所參照的目標物件已經回收。 |
The replication operation failed because the target object referred by a link value is recycled. |
| 0x21C0 | 重新導向作業失敗，因為目標物件所在的 NC 與目前網域控制站的網域 NC 不同。 |
The redirect operation failed because the target object is in a NC different from the domain NC of the current domain controller. |
| 0x21C1 | AD LDS 組態集的功能等級無法降低至要求的值。 |
The functional level of the AD LDS configuration set cannot be lowered to the requested value. |
| 0x21C2 | 網域 (或樹系) 的功能等級無法降低至要求的值。 |
The functional level of the domain (or forest) cannot be lowered to the requested value. |
| 0x21C3 | AD LDS 組態集的功能等級無法提升至要求的值，因為有一或多個 ADLDS 執行個體是較低的不相容功能等級。 |
The functional level of the AD LDS configuration set cannot be raised to the requested value, because there exist one or more ADLDS instances that are at a lower incompatible functional level. |
| 0x21C4 | 無法完成加入網域，因為您嘗試加入之網域的 SID 和此電腦的 SID 相同。這是未適當複製之作業系統安裝的徵兆。您應該在此電腦上執行 sysprep，以產生新的電腦 SID。如需詳細資訊，請參閱 http://go.microsoft.com/fwlink/?LinkId=168895。 |
The domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine. This is a symptom of an improperly cloned operating system install. You should run sysprep on this machine in order to generate a new machine SID. Please see http://go.microsoft.com/fwlink/?LinkId=168895 for more information. |
| 0x21C5 | 取消刪除作業失敗，因為正在取消刪除之物件的「SAM 帳戶名稱」或「其他 SAM 帳戶名稱」與現有的即時物件衝突。 |
The undelete operation failed because the Sam Account Name or Additional Sam Account Name of the object being undeleted conflicts with an existing live object. |
| 0x21C6 | 系統沒有管理所指定帳戶的權限，因此無法完成作業。請使用與此帳戶關聯的提供者來重試作業。若這是線上提供者，請使用該提供者的線上網站。 |
The system is not authoritative for the specified account and therefore cannot complete the operation. Please retry the operation using the provider associated with this account. If this is an online provider please use the provider's online site. |
| 0x21C7 | 操作失敗，因為為新增/修改提供的 SPN 值在樹系中不是唯一值。 |
The operation failed because SPN value provided for addition/modification is not unique forest-wide. |
| 0x21C8 | 操作失敗，因為為新增/修改提供的 UPN 值在樹系中不是唯一值。 |
The operation failed because UPN value provided for addition/modification is not unique forest-wide. |
| 0x21C9 | 操作失敗，因為新增/修改參考不存在的連入全樹系信任。 |
The operation failed because the addition/modification referenced an inbound forest-wide trust that is not present. |
| 0x21CA | 找不到指定的連結值，但找到具有該機碼的連結值。 |
The link value specified was not found, but a link value with that key was found. |
| 0x2329 | DNS 伺服器無法解譯格式。 |
DNS server unable to interpret format. |
| 0x232A | DNS 伺服器失敗。 |
DNS server failure. |
| 0x232B | DNS 名稱不存在。 |
DNS name does not exist. |
| 0x232C | 名稱伺服器不支援 DNS 的要求。 |
DNS request not supported by name server. |
| 0x232D | DNS 操作被拒。 |
DNS operation refused. |
| 0x232E | DNS 存在不該存在的名稱。 |
DNS name that ought not exist, does exist. |
| 0x232F | DNS 存在不該存在的 RR 組。 |
DNS RR set that ought not exist, does exist. |
| 0x2330 | DNS 不存在應該存在的 RR 組。 |
DNS RR set that ought to exist, does not exist. |
| 0x2331 | DNS 伺服器不強制需要區域。 |
DNS server not authoritative for zone. |
| 0x2332 | 預先要求的或更新的 DNS 名稱不在區域中。 |
DNS name in update or prereq is not in zone. |
| 0x2338 | DNS 簽章確認失敗。 |
DNS signature failed to verify. |
| 0x2339 | DNS 錯誤機碼。 |
DNS bad key. |
| 0x233A | DNS 簽章有效期已過。 |
DNS signature validity expired. |
| 0x238D | 只有做為區域金鑰主機的 DNS 伺服器可以執行此作業。 |
Only the DNS server acting as the key master for the zone may perform this operation. |
| 0x238E | 不允許在已簽署或擁有簽署金鑰的區域執行此作業。 |
This operation is not allowed on a zone that is signed or has signing keys. |
| 0x238F | NSEC3 與 RSA-SHA-1 演算法不相容。請選擇其他演算法或使用 NSEC。 |
NSEC3 is not compatible with the RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC. |
| 0x2390 | 區域沒有足夠的簽署金鑰。至少必須有一個金鑰簽署金鑰 (KSK) 和至少一個區域簽署金鑰 (ZSK)。 |
The zone does not have enough signing keys. There must be at least one key signing key (KSK) and at least one zone signing key (ZSK). |
| 0x2391 | 不支援指定的演算法。 |
The specified algorithm is not supported. |
| 0x2392 | 不支援指定的金鑰大小。 |
The specified key size is not supported. |
| 0x2393 | DNS 伺服器無法存取區域的一或多個簽署金鑰。在解決此錯誤之前，區域簽署將無法作業。 |
One or more of the signing keys for a zone are not accessible to the DNS server. Zone signing will not be operational until this error is resolved. |
| 0x2394 | 指定的金鑰儲存提供者不支援 DPAPI++ 資料保護。在解決此錯誤之前，區域簽署將無法作業。 |
The specified key storage provider does not support DPAPI++ data protection. Zone signing will not be operational until this error is resolved. |
| 0x2395 | 發生未預期的 DPAPI++ 錯誤。在解決此錯誤之前，區域簽署將無法作業。 |
An unexpected DPAPI++ error was encountered. Zone signing will not be operational until this error is resolved. |
| 0x2396 | 發生未預期的加密錯誤。在解決此錯誤之前，區域簽署可能無法作業。 |
An unexpected crypto error was encountered. Zone signing may not be operational until this error is resolved. |
| 0x2397 | DNS 伺服器發現有不明版本的簽署金鑰。在解決此錯誤之前，區域簽署將無法作業。 |
The DNS server encountered a signing key with an unknown version. Zone signing will not be operational until this error is resolved. |
| 0x2398 | DNS 伺服器無法開啟指定的金鑰服務提供者。 |
The specified key service provider cannot be opened by the DNS server. |
| 0x2399 | DNS 伺服器無法再接受更多含有所指定演算法與此區域之 KSK 旗標值的簽署金鑰。 |
The DNS server cannot accept any more signing keys with the specified algorithm and KSK flag value for this zone. |
| 0x239A | 指定的變換期間無效。 |
The specified rollover period is invalid. |
| 0x239B | 指定的初始變換位移無效。 |
The specified initial rollover offset is invalid. |
| 0x239C | 指定的簽署金鑰已在變換金鑰。 |
The specified signing key is already in process of rolling over keys. |
| 0x239D | 指定的簽署金鑰沒有要撤銷的待命金鑰。 |
The specified signing key does not have a standby key to revoke. |
| 0x239E | 不允許對區域簽署金鑰 (ZSK) 執行此作業。 |
This operation is not allowed on a zone signing key (ZSK). |
| 0x239F | 不允許在作用中簽署金鑰上執行此作業。 |
This operation is not allowed on an active signing key. |
| 0x23A0 | 指定的簽署金鑰已排入佇列等候變換。 |
The specified signing key is already queued for rollover. |
| 0x23A1 | 不允許在未簽署的區域上執行此作業。 |
This operation is not allowed on an unsigned zone. |
| 0x23A2 | 無法完成此作業，因為列示為此區域之目前金鑰主機的 DNS 伺服器已關閉或設定錯誤。請解決此區域之目前金鑰主機的問題，或使用另一部 DNS 伺服器拿取金鑰主機角色。 |
This operation could not be completed because the DNS server listed as the current key master for this zone is down or misconfigured. Resolve the problem on the current key master for this zone or use another DNS server to seize the key master role. |
| 0x23A3 | 指定的簽章有效期間無效。 |
The specified signature validity period is invalid. |
| 0x23A4 | 指定的 NSEC3 反覆運算計數高於區域中使用之金鑰長度下限允許的值。 |
The specified NSEC3 iteration count is higher than allowed by the minimum key length used in the zone. |
| 0x23A5 | 無法完成此作業，因為 DNS 伺服器已設定為停用 DNSSEC 功能。請在 DNS 伺服器上啟用 DNSSEC。 |
This operation could not be completed because the DNS server has been configured with DNSSEC features disabled. Enable DNSSEC on the DNS server. |
| 0x23A6 | 無法完成此作業，因為收到的 XML 資料流空白，或語義無效。 |
This operation could not be completed because the XML stream received is empty or syntactically invalid. |
| 0x23A7 | 此作業已完成，但未新增任何信賴起點，因為收到的所有信賴起點均無效、不受支援、已到期，或不會在 30 天內生效。 |
This operation completed, but no trust anchors were added because all of the trust anchors received were either invalid, unsupported, expired, or would not become valid in less than 30 days. |
| 0x23A8 | 指定的簽署金鑰未在等候父系 DS 更新。 |
The specified signing key is not waiting for parental DS update. |
| 0x23A9 | NSEC3 簽署期間偵測到雜湊衝突。請指定使用者提供的不同 Salt，或使用隨機產生的 Salt，然後嘗試重新簽署該區域。 |
Hash collision detected during NSEC3 signing. Specify a different user-provided salt, or use a randomly generated salt, and attempt to sign the zone again. |
| 0x23AA | NSEC 與 NSEC3-RSA-SHA-1 演算法不相容。請選擇其他演算法或使用 NSEC3。 |
NSEC is not compatible with the NSEC3-RSA-SHA-1 algorithm. Choose a different algorithm or use NSEC3. |
| 0x251D | 沒有找到指定的 DNS 查詢記錄。 |
No records found for given DNS query. |
| 0x251E | 錯誤的 DNS 封包。 |
Bad DNS packet. |
| 0x251F | 無 DNS 封包。 |
No DNS packet. |
| 0x2520 | DNS 錯誤，檢查 rcode。 |
DNS error, check rcode. |
| 0x2521 | 不安全的 DNS 封包。 |
Unsecured DNS packet. |
| 0x2522 | DNS 查詢要求擱置中。 |
DNS query request is pending. |
| 0x254F | 無效的 DNS 類型。 |
Invalid DNS type. |
| 0x2550 | 無效的 IP 位址。 |
Invalid IP address. |
| 0x2551 | 無效的內容。 |
Invalid property. |
| 0x2552 | 稍後再試 DNS 操作。 |
Try DNS operation again later. |
| 0x2553 | 指定的名稱和類型的記錄不具唯一性。 |
Record for given name and type is not unique. |
| 0x2554 | DNS 名稱未遵守 RFC 規格。 |
DNS name does not comply with RFC specifications. |
| 0x2555 | DNS 名稱是一個完全合格的 DNS 名稱。 |
DNS name is a fully-qualified DNS name. |
| 0x2556 | DNS 名稱含有點 (.) (多重標籤)。 |
DNS name is dotted (multi-label). |
| 0x2557 | DNS 名稱是一個單一部分名稱。 |
DNS name is a single-part name. |
| 0x2558 | DNS 名稱包含不正確的字元。 |
DNS name contains an invalid character. |
| 0x2559 | DNS 名稱完全是數字。 |
DNS name is entirely numeric. |
| 0x255A | 操作要求在 DNS 根伺服器上不允許。 |
The operation requested is not permitted on a DNS root server. |
| 0x255B | 無法建立記錄，因為這個部分的 DNS 命名空間已經委派給另外的伺服器。 |
The record could not be created because this part of the DNS namespace has been delegated to another server. |
| 0x255C | DNS 伺服器找不到一組根目錄提示。 |
The DNS server could not find a set of root hints. |
| 0x255D | DNS 伺服器找到根目錄提示，但它們並不對所有的介面卡一致。 |
The DNS server found root hints but they were not consistent across all adapters. |
| 0x255E | 指定的值對此參數來說太小。 |
The specified value is too small for this parameter. |
| 0x255F | 指定的值對此參數來說太大。 |
The specified value is too large for this parameter. |
| 0x2560 | 當 DNS 伺服器在背景載入區域時，不允許進行此作業。請稍後再試。 |
This operation is not allowed while the DNS server is loading zones in the background. Please try again later. |
| 0x2561 | 不允許針對在唯讀 DC 上執行的 DNS 伺服器進行要求的作業。 |
The operation requested is not permitted on against a DNS server running on a read-only DC. |
| 0x2562 | DNAME 記錄下不允許存在任何資料。 |
No data is allowed to exist underneath a DNAME record. |
| 0x2563 | 此操作需要認證委派。 |
This operation requires credentials delegation. |
| 0x2564 | 名稱解析原則表格已損毀。DNS 解析在修復之前都會失敗。請連絡網路管理員。 |
Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. |
| 0x2565 | 不允許移除所有位址。 |
Not allowed to remove all addresses. |
| 0x2581 | DNS 區域不存在。 |
DNS zone does not exist. |
| 0x2582 | DNS 區域資訊無法使用。 |
DNS zone information not available. |
| 0x2583 | 無效的 DNS 區域操作。 |
Invalid operation for DNS zone. |
| 0x2584 | 無效的 DNS 區域設定。 |
Invalid DNS zone configuration. |
| 0x2585 | DNS 區域沒有起始點授權 (SOA) 記錄。 |
DNS zone has no start of authority (SOA) record. |
| 0x2586 | DNS 區域沒有名稱伺服器服務 (NS) 記錄。 |
DNS zone has no Name Server (NS) record. |
| 0x2587 | DNS 區域已被鎖定。 |
DNS zone is locked. |
| 0x2588 | DNS 區域建立失敗。 |
DNS zone creation failed. |
| 0x2589 | DNS 區域已存在。 |
DNS zone already exists. |
| 0x258A | DNS 自動區域已存在。 |
DNS automatic zone already exists. |
| 0x258B | 無效的 DNS 區域類型。 |
Invalid DNS zone type. |
| 0x258C | DNS 輔助區需要主要 IP 位址。 |
Secondary DNS zone requires master IP address. |
| 0x258D | DNS 區域不是次要區域。 |
DNS zone not secondary. |
| 0x258E | 需要次要 IP 位址。 |
Need secondary IP address. |
| 0x258F | WINS 初始化失敗。 |
WINS initialization failed. |
| 0x2590 | 需要 WINS 伺服器。 |
Need WINS servers. |
| 0x2591 | NBTSTAT 初始化呼叫失敗。 |
NBTSTAT initialization call failed. |
| 0x2592 | 無效的刪除起始點授權 (SOA) |
Invalid delete of start of authority (SOA) |
| 0x2593 | 那個名稱已經存在條件性轉送區域。 |
A conditional forwarding zone already exists for that name. |
| 0x2594 | 這個區域必須以一或多個主要 DNS 伺服器 IP 位址設定。 |
This zone must be configured with one or more master DNS server IP addresses. |
| 0x2595 | 無法執行這個操作，因為這個區域已關閉。 |
The operation cannot be performed because this zone is shut down. |
| 0x2596 | 無法執行此操作，因為目前正在簽署該區域。請稍後再試一次。 |
This operation cannot be performed because the zone is currently being signed. Please try again later. |
| 0x25B3 | DNS 主區域需要資料檔案。 |
Primary DNS zone requires datafile. |
| 0x25B4 | 無效的 DNS 區域資料檔案名稱。 |
Invalid datafile name for DNS zone. |
| 0x25B5 | DNS 區域資料檔案開啟失敗。 |
Failed to open datafile for DNS zone. |
| 0x25B6 | DNS 區域資料檔案寫入失敗。 |
Failed to write datafile for DNS zone. |
| 0x25B7 | 讀取 DNS 區域資料檔案時失敗。 |
Failure while reading datafile for DNS zone. |
| 0x25E5 | DNS 記錄不存在。 |
DNS record does not exist. |
| 0x25E6 | DNS 記錄格式錯誤。 |
DNS record format error. |
| 0x25E7 | DNS 中節點建立失敗。 |
Node creation failure in DNS. |
| 0x25E8 | 不明的 DNS 記錄類型。 |
Unknown DNS record type. |
| 0x25E9 | DNS 記錄逾時。 |
DNS record timed out. |
| 0x25EA | 名稱不在 DNS 區域中。 |
Name not in DNS zone. |
| 0x25EB | 偵測到 CNAME 迴路。 |
CNAME loop detected. |
| 0x25EC | 節點是一個 CNAME DNS 記錄。 |
Node is a CNAME DNS record. |
| 0x25ED | 指定的名稱 CNAME 記錄已存在。 |
A CNAME record already exists for given name. |
| 0x25EE | 記錄僅存在於 DNS 根區域。 |
Record only at DNS zone root. |
| 0x25EF | DNS 記錄已存在。 |
DNS record already exists. |
| 0x25F0 | 次要 DNS 區域的資料錯誤。 |
Secondary DNS zone data error. |
| 0x25F1 | 無法建立 DNS 快取資料。 |
Could not create DNS cache data. |
| 0x25F3 | 無法建立指標 (PTR) 記錄。 |
Could not create pointer (PTR) record. |
| 0x25F4 | 解除刪除 DNS 網域。 |
DNS domain was undeleted. |
| 0x25F6 | DNS 區域已存在於目錄服務中。 |
DNS zone already exists in the directory service. |
| 0x25F7 | 目錄服務整合 DNS 區域中的 DNS 伺服器並未建立或讀取開機檔案。 |
DNS server not creating or reading the boot file for the directory service integrated DNS zone. |
| 0x25F8 | 節點是一個 DNAME DNS 記錄。 |
Node is a DNAME DNS record. |
| 0x25F9 | 指定名稱的 DNAME 記錄已存在。 |
A DNAME record already exists for given name. |
| 0x25FA | 偵測到 CNAME 或 DNAME 記錄中有別名迴圈。 |
An alias loop has been detected with either CNAME or DNAME records. |
| 0x2617 | DNS AXFR (區域傳輸) 完成。 |
DNS AXFR (zone transfer) complete. |
| 0x2618 | DNS 區域傳輸失敗。 |
DNS zone transfer failed. |
| 0x2619 | 已新增本機 WINS 伺服器。 |
Added local WINS server. |
| 0x2649 | 安全更新呼叫必須繼續更新要求。 |
Secure update call needs to continue update request. |
| 0x267B | 並未安裝 TCP/IP 網路通訊協定。 |
TCP/IP network protocol not installed. |
| 0x267C | 本機系統並未設定 DNS 伺服器。 |
No DNS servers configured for local system. |
| 0x26AD | 指定的目錄分割不存在。 |
The specified directory partition does not exist. |
| 0x26AE | 指定的目錄分割已經存在。 |
The specified directory partition already exists. |
| 0x26AF | 指定的目錄分割沒有徵募這個 DNS 伺服器。 |
This DNS server is not enlisted in the specified directory partition. |
| 0x26B0 | 指定的目錄分割已經徵募這個 DNS 伺服器。 |
This DNS server is already enlisted in the specified directory partition. |
| 0x26B1 | 目錄分割目前無法使用，請等候數分鐘後再試。 |
The directory partition is not available at this time. Please wait a few minutes and try again. |
| 0x26B2 | 作業失敗，因為無法連線網域命名主機 FSMO 角色。擁有網域命名主機 FSMO 角色的網域控制站已關機、無法服務要求，或不是執行 Windows Server 2003 或更新版本。 |
The operation failed because the domain naming master FSMO role could not be reached. The domain controller holding the domain naming master FSMO role is down or unable to service the request or is not running Windows Server 2003 or later. |
| 0x26B7 | RRL 未啟用。 |
The RRL is not enabled. |
| 0x26B8 | 視窗大小參數無效。它應該大於或等於 1。 |
The window size parameter is invalid. It should be greater than or equal to 1. |
| 0x26B9 | IPv4 首碼長度參數無效。它應該小於或等於 32。 |
The IPv4 prefix length parameter is invalid. It should be less than or equal to 32. |
| 0x26BA | IPv6 首碼長度參數無效。它應該小於或等於 128。 |
The IPv6 prefix length parameter is invalid. It should be less than or equal to 128. |
| 0x26BB | TC Rate 參數無效。它應該小於 10。 |
The TC Rate parameter is invalid. It should be less than 10. |
| 0x26BC | Leak Rate 參數無效。它應該是 0 或介於 2 到 10 之間。 |
The Leak Rate parameter is invalid. It should be either 0, or between 2 and 10. |
| 0x26BD | Leak Rate 或 TC Rate 參數無效。Leak Rate 應該大於 TC Rate。 |
The Leak Rate or TC Rate parameter is invalid. Leak Rate should be greater than TC Rate. |
| 0x26C1 | 虛擬化執行個體已存在。 |
The virtualization instance already exists. |
| 0x26C2 | 虛擬化執行個體不存在。 |
The virtualization instance does not exist. |
| 0x26C3 | 虛擬化樹狀目錄已被鎖定。 |
The virtualization tree is locked. |
| 0x26C4 | 無效的虛擬化執行個體名稱。 |
Invalid virtualization instance name. |
| 0x26C5 | 無法新增、移除或修改預設的虛擬化執行個體。 |
The default virtualization instance cannot be added, removed or modified. |
| 0x26DF | 區域中已經有該領域存在。 |
The scope already exists for the zone. |
| 0x26E0 | 區域中沒有該領域存在。 |
The scope does not exist for the zone. |
| 0x26E1 | 該領域與預設區域領域相同。 |
The scope is the same as the default zone scope. |
| 0x26E2 | 該領域名稱包含無效的字元。 |
The scope name contains invalid characters. |
| 0x26E3 | 區域具有領域時，不允許操作。 |
Operation not allowed when the zone has scopes. |
| 0x26E4 | 無法載入區域範圍。 |
Failed to load zone scope. |
| 0x26E5 | 無法寫入 DNS 區域範圍的資料檔。請確認檔案存在且可供寫入。 |
Failed to write data file for DNS zone scope. Please verify the file exists and is writable. |
| 0x26E7 | 該領域不存在。 |
The scope does not exist. |
| 0x26E8 | 該領域與預設領域相同。 |
The scope is the same as the default scope. |
| 0x26E9 | 該操作在該領域上無效。 |
The operation is invalid on the scope. |
| 0x26EA | 該領域已被鎖定。 |
The scope is locked. |
| 0x26EB | 該領域已存在。 |
The scope already exists. |
| 0x26F3 | DNS 伺服器的此層級 (伺服器層級或區域層級) 已有具有相同名稱的原則存在。 |
A policy with the same name already exists on this level (server level or zone level) on the DNS server. |
| 0x26F4 | DNS 伺服器的此層級 (伺服器層級或區域層級) 沒有具有此名稱的原則存在。 |
No policy with this name exists on this level (server level or zone level) on the DNS server. |
| 0x26F5 | 在原則中提供的準則無效。 |
The criteria provided in the policy are invalid. |
| 0x26F6 | 此原則的至少一個設定無效。 |
At least one of the settings of this policy is invalid. |
| 0x26F7 | 無法刪除該用戶端子網路，因為某個原則正在存取它。 |
The client subnet cannot be deleted while it is being accessed by a policy. |
| 0x26F8 | 用戶端子網路不存在於 DNS 伺服器上。 |
The client subnet does not exist on the DNS server. |
| 0x26F9 | DNS 伺服器上已有具有此名稱的用戶端子網路存在。 |
A client subnet with this name already exists on the DNS server. |
| 0x26FA | 指定的 IP 子網路不存在於用戶端子網路中。 |
The IP subnet specified does not exist in the client subnet. |
| 0x26FB | 要新增的 IP 子網路已存在於用戶端子網路中。 |
The IP subnet that is being added, already exists in the client subnet. |
| 0x26FC | 原則已被鎖定。 |
The policy is locked. |
| 0x26FD | 原則中的領域權數無效。 |
The weight of the scope in the policy is invalid. |
| 0x26FE | DNS 原則名稱無效。 |
The DNS policy name is invalid. |
| 0x26FF | 原則沒有準則。 |
The policy is missing criteria. |
| 0x2700 | 用戶端子網路記錄的名稱無效。 |
The name of the the client subnet record is invalid. |
| 0x2701 | 無效的原則處理順序。 |
Invalid policy processing order. |
| 0x2702 | 尚未為要求範圍資訊的原則提供範圍資訊。 |
The scope information has not been provided for a policy that requires it. |
| 0x2703 | 已經為未要求範圍資訊的原則提供範圍資訊。 |
The scope information has been provided for a policy that does not require it. |
| 0x2704 | 無法刪除伺服器領域，因為它正由 DNS 原則參照。 |
The server scope cannot be deleted because it is referenced by a DNS Policy. |
| 0x2705 | 無法刪除區域領域，因為它正由 DNS 原則參照。 |
The zone scope cannot be deleted because it is referenced by a DNS Policy. |
| 0x2706 | 在原則中提供的用戶端子網路條件無效。 |
The criterion client subnet provided in the policy is invalid. |
| 0x2707 | 在原則中提供的傳輸通訊協定條件無效。 |
The criterion transport protocol provided in the policy is invalid. |
| 0x2708 | 在原則中提供的網路通訊協定條件無效。 |
The criterion network protocol provided in the policy is invalid. |
| 0x2709 | 在原則中提供的介面條件無效。 |
The criterion interface provided in the policy is invalid. |
| 0x270A | 在原則中提供的 FQDN 條件無效。 |
The criterion FQDN provided in the policy is invalid. |
| 0x270B | 在原則中提供的查詢類型條件無效。 |
The criterion query type provided in the policy is invalid. |
| 0x270C | 在原則中提供的當日時間條件無效。 |
The criterion time of day provided in the policy is invalid. |
| 0x00002714 | 中止操作被 WSACancelBlockingCall 呼叫打斷。 |
A blocking operation was interrupted by a call to WSACancelBlockingCall. |
| 0x00002719 | 提供的檔案控制代碼無效。 |
The file handle supplied is not valid. |
| 0x0000271D | 嘗試存取通訊端被拒絕，因為存取權限不足。 |
An attempt was made to access a socket in a way forbidden by its access permissions. |
| 0x0000271E | 嘗試在呼叫中使用指標引數時，系統偵測到無效的指標位址。 |
The system detected an invalid pointer address in attempting to use a pointer argument in a call. |
| 0x00002726 | 提供了一個不正確的引數。 |
An invalid argument was supplied. |
| 0x00002728 | 開啟太多通訊端。 |
Too many open sockets. |
| 0x00002733 | 無法立即完成通訊端操作，而且無法停止。 |
A non-blocking socket operation could not be completed immediately. |
| 0x00002734 | 目前正在終止操作。 |
A blocking operation is currently executing. |
| 0x00002735 | 嘗試啟動一個已在進行中而且不能停止的通訊端操作。 |
An operation was attempted on a non-blocking socket that already had an operation in progress. |
| 0x00002736 | 嘗試操作的對象不是通訊端。 |
An operation was attempted on something that is not a socket. |
| 0x00002737 | 通訊端操作省略了一個必需的位址。 |
A required address was omitted from an operation on a socket. |
| 0x00002738 | 有一個訊息傳送到資料包通訊端，這個訊息超過內部訊息緩衝區或是某些其他網路限制，或是使來接收資料包的緩衝區小於資料包本身。 |
A message sent on a datagram socket was larger than the internal message buffer or some other network limit, or the buffer used to receive a datagram into was smaller than the datagram itself. |
| 0x00002739 | 在通訊端函式呼叫中指定的通訊協定不支援所要求的通訊端類型語法。 |
A protocol was specified in the socket function call that does not support the semantics of the socket type requested. |
| 0x0000273A | 在 getsockopt 或 setsockopt 呼叫中指定了一個不明的，不正確的，或不受支援的參數或等級。 |
An unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call. |
| 0x0000273B | 系統中並未設定所要求的通訊協定，或是無法執行這個通訊協定。 |
The requested protocol has not been configured into the system, or no implementation for it exists. |
| 0x0000273C | 在這個位址家族中不支援指定的通訊端類型。 |
The support for the specified socket type does not exist in this address family. |
| 0x0000273D | 不支援這項物件參照類型的操作。 |
The attempted operation is not supported for the type of object referenced. |
| 0x0000273E | 系統中並未設定所要求的通訊協定家族，或是無法執行這個通訊協定。 |
The protocol family has not been configured into the system or no implementation for it exists. |
| 0x0000273F | 使用了一個與要求的通訊協定不相容的位址。 |
An address incompatible with the requested protocol was used. |
| 0x00002740 | 一次只能用一個通訊端位址 (通訊協定/網路位址/連接埠)。 |
Only one usage of each socket address (protocol/network address/port) is normally permitted. |
| 0x00002741 | 內容中所要求的位址不正確。 |
The requested address is not valid in its context. |
| 0x00002742 | 通訊端操作遇到一個停用的網路。 |
A socket operation encountered a dead network. |
| 0x00002743 | 通訊端操作嘗試連線到一個無法連線的網路。 |
A socket operation was attempted to an unreachable network. |
| 0x00002744 | 連線已經失效，因為操作進行時偵測到一個失敗。 |
The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. |
| 0x00002745 | 連線已被您主機上的軟體中止。 |
An established connection was aborted by the software in your host machine. |
| 0x00002746 | 遠端主機已強制關閉一個現存的連線。 |
An existing connection was forcibly closed by the remote host. |
| 0x00002747 | 因為系統缺乏足夠的緩衝區空間或因為佇列已滿，所以無法在通訊端上執行操作。 |
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. |
| 0x00002748 | 對一個已連線的通訊端發出連線要求。 |
A connect request was made on an already connected socket. |
| 0x00002749 | 不允許傳送或接收資料的要求，因為通訊端並未連線，而且 (在資料包通訊端使用 sendto 呼叫進行傳送時) 並未提供位址。 |
A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied. |
| 0x0000274A | 不允許傳送或接收資料的要求，因為通訊端已經被先前的關機呼叫關閉。 |
A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. |
| 0x0000274B | 有些核心物件的參照太多。 |
Too many references to some kernel object. |
| 0x0000274C | 連線嘗試失敗，因為連線對象有一段時間並未正確回應，或是連線建立失敗，因為連線的主機無法回應。 |
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. |
| 0x0000274D | 無法連線，因為目標電腦拒絕連線。 |
No connection could be made because the target machine actively refused it. |
| 0x0000274E | 無法翻譯名稱。 |
Cannot translate name. |
| 0x0000274F | 名稱元件或名稱太長。 |
Name component or name was too long. |
| 0x00002750 | 通訊端操作失敗，因為目標主機已關機。 |
A socket operation failed because the destination host was down. |
| 0x00002751 | 通訊端操作無法連線到主機。 |
A socket operation was attempted to an unreachable host. |
| 0x00002752 | 無法移除並未清空的目錄。 |
Cannot remove a directory that is not empty. |
| 0x00002753 | Windows Sockets 執行時，與它同時執行的應用程式數目可能有一定的限制。 |
A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously. |
| 0x00002754 | 配額已用完。 |
Ran out of quota. |
| 0x00002755 | 磁碟配額已用完。 |
Ran out of disk quota. |
| 0x00002756 | 檔案控制代碼參照無法使用。 |
File handle reference is no longer available. |
| 0x00002757 | 項目無法在本機使用。 |
Item is not available locally. |
| 0x0000276B | WSAStartup 這時無法執行，因為它用來提供網路服務的主要系統目前無法使用。 |
WSAStartup cannot function at this time because the underlying system it uses to provide network services is currently unavailable. |
| 0x0000276C | 不支援所要求的 Windows Sockets 版本。 |
The Windows Sockets version requested is not supported. |
| 0x0000276D | 可能是應用程式尚未呼叫 WSAStartup，或 WSAStartup 發生失敗。 |
Either the application has not called WSAStartup, or WSAStartup failed. |
| 0x00002775 | WSARecv 或 WSARecvFrom 的傳回結果指出遠端群體已經初始順利關機程序。 |
Returned by WSARecv or WSARecvFrom to indicate the remote party has initiated a graceful shutdown sequence. |
| 0x00002776 | WSALookupServiceNext 沒有其他結果可以傳回。 |
No more results can be returned by WSALookupServiceNext. |
| 0x00002777 | 處理 WSALookupServiceEnd 呼叫時，又收到同樣的呼叫。這個呼叫已被取消。 |
A call to WSALookupServiceEnd was made while this call was still processing. The call has been canceled. |
| 0x00002778 | 程序呼叫表格不正確。 |
The procedure call table is invalid. |
| 0x00002779 | 要求的服務提供者不正確。 |
The requested service provider is invalid. |
| 0x0000277A | 無法載入或初始化所要求的服務提供者。 |
The requested service provider could not be loaded or initialized. |
| 0x0000277B | 系統呼叫失敗。 |
A system call has failed. |
| 0x0000277C | 無法識別此服務。在指定的名稱區中找不到此服務。 |
No such service is known. The service cannot be found in the specified name space. |
| 0x0000277D | 找不到指定的類別。 |
The specified class was not found. |
| 0x00002780 | 資料庫查詢失敗，因為查詢被拒絕。 |
A database query failed because it was actively refused. |
| 0x00002AF9 | 無法識別這台主機。 |
No such host is known. |
| 0x00002AFA | 在主機名稱解析過程中，這通常是暫時性錯誤，它表示本機伺服器並未收到主伺服器的回應。 |
This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. |
| 0x00002AFB | 在搜尋資料庫時發生一個無法恢復的錯誤。 |
A non-recoverable error occurred during a database lookup. |
| 0x00002AFC | 要求的名稱正確，但找不到所要求類型的資料。 |
The requested name is valid, but no data of the requested type was found. |
| 0x00002AFD | 至少到達一個保留區。 |
At least one reserve has arrived. |
| 0x00002AFE | 至少已到達一個路徑。 |
At least one path has arrived. |
| 0x00002AFF | 沒有傳送者。 |
There are no senders. |
| 0x00002B00 | 沒有接收者。 |
There are no receivers. |
| 0x00002B01 | 已經確認保留。 |
Reserve has been confirmed. |
| 0x00002B02 | 資源不足，所以發生錯誤。 |
Error due to lack of resources. |
| 0x00002B03 | 系統管理的拒絕理由 - 認證錯誤。 |
Rejected for administrative reasons - bad credentials. |
| 0x00002B04 | 不明的樣式或樣式有衝突。 |
Unknown or conflicting style. |
| 0x00002B05 | 部分的檔案格式或提供者指定緩衝區有問題。 |
Problem with some part of the filterspec or providerspecific buffer in general. |
| 0x00002B06 | 部分的流量格式有問題。 |
Problem with some part of the flowspec. |
| 0x00002B07 | 一般 QOS 錯誤。 |
General QOS error. |
| 0x00002B08 | 在流量規格中找到不正確或無法識別的服務類型。 |
An invalid or unrecognized service type was found in the flowspec. |
| 0x00002B09 | 在 QOS 結構中找到不正確或不一致的流量規格。 |
An invalid or inconsistent flowspec was found in the QOS structure. |
| 0x00002B0A | 不正確的 QOS 特定提供者緩衝區。 |
Invalid QOS provider-specific buffer. |
| 0x00002B0B | 使用了不正確的 QOS 篩選器類型。 |
An invalid QOS filter style was used. |
| 0x00002B0D | 在 FLOWDESCRIPTOR 指定了錯誤數量的 QOS FILTERSPEC。 |
An incorrect number of QOS FILTERSPECs were specified in the FLOWDESCRIPTOR. |
| 0x00002B0E | 在 QOS 特定提供者緩衝區指定了含有不正確 ObjectLength 欄位的物件。 |
An object with an invalid ObjectLength field was specified in the QOS provider-specific buffer. |
| 0x00002B0F | 在 QOS 結構中指定了數目不正確的流量描述元。 |
An incorrect number of flow descriptors was specified in the QOS structure. |
| 0x00002B10 | 在 QOS 特定提供者緩衝區找到無法識別的物件。 |
An unrecognized object was found in the QOS provider-specific buffer. |
| 0x00002B11 | 在 QOS 特定提供者緩衝區找到不正確的原則物件。 |
An invalid policy object was found in the QOS provider-specific buffer. |
| 0x00002B12 | 在流量描述元清單中找到不正確的 QOS 流量描述元。 |
An invalid QOS flow descriptor was found in the flow descriptor list. |
| 0x00002B13 | 在 QOS 特定提供者緩衝區找到不正確或不一致的流量規格。 |
An invalid or inconsistent flowspec was found in the QOS provider specific buffer. |
| 0x00002B14 | 在 QOS 特定提供者緩衝區找到不正確的 FILTERSPEC。 |
An invalid FILTERSPEC was found in the QOS provider-specific buffer. |
| 0x00002B15 | 在 QOS 特定提供者緩衝區找到不正確的形狀丟棄模式物件。 |
An invalid shape discard mode object was found in the QOS provider specific buffer. |
| 0x00002B16 | 在 QOS 特定提供者緩衝區找到不正確的形式速率物件。 |
An invalid shaping rate object was found in the QOS provider-specific buffer. |
| 0x00002B17 | 在 QOS 特定提供者緩衝區找到保留的原則元素。 |
A reserved policy element was found in the QOS provider-specific buffer. |
| 0x00002B18 | 無法安全地識別這台主機。 |
No such host is known securely. |
| 0x00002B19 | 無法新增以名稱為基礎的 IPSEC 原則。 |
Name based IPSEC policy could not be added. |
| 0x000032C8 | 指定的快速模式原則已經存在。 |
The specified quick mode policy already exists. |
| 0x000032C9 | 找不到指定的快速模式原則。 |
The specified quick mode policy was not found. |
| 0x000032CA | 指定的快速模式原則已在使用中。 |
The specified quick mode policy is being used. |
| 0x000032CB | 指定的主要模式原則已經存在。 |
The specified main mode policy already exists. |
| 0x000032CC | 找不到指定的主要模式原則。 |
The specified main mode policy was not found |
| 0x000032CD | 指定的主要模式原則已在使用中。 |
The specified main mode policy is being used. |
| 0x000032CE | 指定的主要模式篩選器已經存在。 |
The specified main mode filter already exists. |
| 0x000032CF | 找不到指定的主要模式篩選器。 |
The specified main mode filter was not found. |
| 0x000032D0 | 指定的傳輸模式篩選器已經存在。 |
The specified transport mode filter already exists. |
| 0x000032D1 | 指定的傳輸模式篩選器不存在。 |
The specified transport mode filter does not exist. |
| 0x000032D2 | 指定的主要模式驗證清單已存在。 |
The specified main mode authentication list exists. |
| 0x000032D3 | 找不到指定的主要模式驗證清單。 |
The specified main mode authentication list was not found. |
| 0x000032D4 | 指定的主要模式驗證清單已在使用中。 |
The specified main mode authentication list is being used. |
| 0x000032D5 | 找不到指定的預設主要模式原則。 |
The specified default main mode policy was not found. |
| 0x000032D6 | 找不到指定的預設主要模式驗證清單。 |
The specified default main mode authentication list was not found. |
| 0x000032D7 | 找不到指定的預設快速模式原則。 |
The specified default quick mode policy was not found. |
| 0x000032D8 | 指定的通道模式篩選器存在。 |
The specified tunnel mode filter exists. |
| 0x000032D9 | 找不到指定的通道模式篩選器。 |
The specified tunnel mode filter was not found. |
| 0x000032DA | 主要模式篩選器正懸置刪除。 |
The Main Mode filter is pending deletion. |
| 0x000032DB | 傳輸篩選器正懸置刪除。 |
The transport filter is pending deletion. |
| 0x000032DC | 通道篩選器正懸置刪除。 |
The tunnel filter is pending deletion. |
| 0x000032DD | 主要模式原則正懸置刪除。 |
The Main Mode policy is pending deletion. |
| 0x000032DE | 主要模式驗證包裹正懸置刪除。 |
The Main Mode authentication bundle is pending deletion. |
| 0x000032DF | 快速模式原則正懸置刪除。 |
The Quick Mode policy is pending deletion. |
| 0x000032E0 | 成功新增主要模式原則，但並不支援某些要求的提議。 |
The Main Mode policy was successfully added, but some of the requested offers are not supported. |
| 0x000032E1 | 成功新增快速模式原則，但並不支援某些要求的提議。 |
The Quick Mode policy was successfully added, but some of the requested offers are not supported. |
| 0x000035E8 | ERROR_IPSEC_IKE_NEG_STATUS_BEGIN |
ERROR_IPSEC_IKE_NEG_STATUS_BEGIN |
| 0x000035E9 | IKE 驗證認證不可接受 |
IKE authentication credentials are unacceptable |
| 0x000035EA | IKE 安全性屬性不可接受 |
IKE security attributes are unacceptable |
| 0x000035EB | IKE 交涉正在進行中 |
IKE Negotiation in progress |
| 0x000035EC | 一般處理錯誤 |
General processing error |
| 0x000035ED | 交涉逾時 |
Negotiation timed out |
| 0x000035EE | IKE 找不到有效的機器憑證。請連絡您的網路安全性系統管理員，以在適當的憑證存放區中安裝有效的憑證。 |
IKE failed to find valid machine certificate. Contact your Network Security Administrator about installing a valid certificate in the appropriate Certificate Store. |
| 0x000035EF | IKE SA 在建立完成前被對等刪除 |
IKE SA deleted by peer before establishment completed |
| 0x000035F0 | IKE SA 在建立完成前被刪除 |
IKE SA deleted before establishment completed |
| 0x000035F1 | 交涉要求在佇列中等候太久 |
Negotiation request sat in Queue too long |
| 0x000035F5 | 沒有來自對等的回應 |
No response from peer |
| 0x000035F6 | 交涉花太長時間 |
Negotiation took too long |
| 0x000035F8 | 發生不明的錯誤 |
Unknown error occurred |
| 0x000035F9 | 憑證撤銷檢查失敗 |
Certificate Revocation Check failed |
| 0x000035FA | 憑證金鑰使用法無效 |
Invalid certificate key usage |
| 0x000035FB | 憑證類型無效 |
Invalid certificate type |
| 0x000035FC | 因為使用的機器憑證沒有私密金鑰，所以 IKE 交涉失敗。IPsec 憑證需要私密金鑰。請連絡您的網路安全性系統管理員，以具有私密金鑰的憑證來取代。 |
IKE negotiation failed because the machine certificate used does not have a private key. IPsec certificates require a private key. Contact your Network Security administrator about replacing with a certificate that has a private key. |
| 0x000035FD | 偵測到同步重設金鑰。 |
Simultaneous rekeys were detected. |
| 0x000035FE | Diffie-Hellman 計算失敗 |
Failure in Diffie-Hellman computation |
| 0x000035FF | 不知如何處理關鍵內容 |
Don't know how to process critical payload |
| 0x00003600 | 標頭無效 |
Invalid header |
| 0x00003601 | 沒有已設定的原則 |
No policy configured |
| 0x00003602 | 無法確認簽章 |
Failed to verify signature |
| 0x00003603 | 無法使用 Kerberos 進行驗證 |
Failed to authenticate using Kerberos |
| 0x00003604 | 對等的憑證沒有公開金鑰 |
Peer's certificate did not have a public key |
| 0x00003605 | 處理錯誤內容時發生錯誤 |
Error processing error payload |
| 0x00003606 | 處理 SA 內容時發生錯誤 |
Error processing SA payload |
| 0x00003607 | 處理 Proposal 內容時發生錯誤 |
Error processing Proposal payload |
| 0x00003608 | 處理 Transform 內容時發生錯誤 |
Error processing Transform payload |
| 0x00003609 | 處理 KE 內容時發生錯誤 |
Error processing KE payload |
| 0x0000360A | 處理 ID 內容時發生錯誤 |
Error processing ID payload |
| 0x0000360B | 處理 Cert 內容時發生錯誤 |
Error processing Cert payload |
| 0x0000360C | 處理憑證要求內容時發生錯誤 |
Error processing Certificate Request payload |
| 0x0000360D | 處理雜湊內容時發生錯誤 |
Error processing Hash payload |
| 0x0000360E | 處理簽章內容時發生錯誤 |
Error processing Signature payload |
| 0x0000360F | 處理 Nonce 內容時發生錯誤 |
Error processing Nonce payload |
| 0x00003610 | 處理 Notify 內容時發生錯誤 |
Error processing Notify payload |
| 0x00003611 | 處理 Delete 內容時發生錯誤 |
Error processing Delete Payload |
| 0x00003612 | 處理 VendorId 內容時發生錯誤 |
Error processing VendorId payload |
| 0x00003613 | 收到無效的內容 |
Invalid payload received |
| 0x00003614 | Soft SA 已載入 |
Soft SA loaded |
| 0x00003615 | Soft SA 被破壞 |
Soft SA torn down |
| 0x00003616 | 收到無效的 cookie。 |
Invalid cookie received. |
| 0x00003617 | 對等無法傳送有效的電腦憑證 |
Peer failed to send valid machine certificate |
| 0x00003618 | 對等憑證的憑證撤銷檢查失敗 |
Certification Revocation check of peer's certificate failed |
| 0x00003619 | 新原則使採舊原則格式的 SA 失效 |
New policy invalidated SAs formed with old policy |
| 0x0000361A | 沒有可用的主要模式 IKE 原則。 |
There is no available Main Mode IKE policy. |
| 0x0000361B | 無法啟用 TCB 特殊權限。 |
Failed to enabled TCB privilege. |
| 0x0000361C | 無法載入 SECURITY.DLL。 |
Failed to load SECURITY.DLL. |
| 0x0000361D | 無法從 SSPI 取得安全性功能表發送位址。 |
Failed to obtain security function table dispatch address from SSPI. |
| 0x0000361E | 無法查詢 Kerberos 封裝以取得最大權杖大小。 |
Failed to query Kerberos package to obtain max token size. |
| 0x0000361F | 無法取得 Kerberos 伺服器的 ISAKMP/ERROR_IPSEC_IKE 服務認證。Kerberos 驗證功能將無法運作。最可能的造成原因是缺少網域成員資格。如果您的電腦是工作群組成員，這就是正常現象。 |
Failed to obtain Kerberos server credentials for ISAKMP/ERROR_IPSEC_IKE service. Kerberos authentication will not function. The most likely reason for this is lack of domain membership. This is normal if your computer is a member of a workgroup. |
| 0x00003620 | 無法決定 SSPI 主體名稱給 ISAKMP/ERROR_IPSEC_IKE 服務 (QueryCredentialsAttributes)。 |
Failed to determine SSPI principal name for ISAKMP/ERROR_IPSEC_IKE service (QueryCredentialsAttributes). |
| 0x00003621 | 從 IPsec 驅動程式為傳入 SA 取得新的 SPI 時失敗。很可能是因為驅動程式沒有正確的篩選器。請檢查您的原則以確認篩選器。 |
Failed to obtain new SPI for the inbound SA from IPsec driver. The most common cause for this is that the driver does not have the correct filter. Check your policy to verify the filters. |
| 0x00003622 | 指定的篩選器不正確 |
Given filter is invalid |
| 0x00003623 | 記憶體配置失敗。 |
Memory allocation failed. |
| 0x00003624 | 將安全性關聯新增到 IPsec 驅動程式的嘗試失敗。很可能是因為 IKE 交涉花太長時間才完成。如果問題持續發生，請降低發生失敗之電腦的負載。 |
Failed to add Security Association to IPsec Driver. The most common cause for this is if the IKE negotiation took too long to complete. If the problem persists, reduce the load on the faulting machine. |
| 0x00003625 | 不正確的原則 |
Invalid policy |
| 0x00003626 | 不正確的 DOI |
Invalid DOI |
| 0x00003627 | 不正確的狀況 |
Invalid situation |
| 0x00003628 | Diffie-Hellman 失敗 |
Diffie-Hellman failure |
| 0x00003629 | 不正確的 Diffie-Hellman 群組 |
Invalid Diffie-Hellman group |
| 0x0000362A | 加密內容錯誤 |
Error encrypting payload |
| 0x0000362B | 解密內容錯誤 |
Error decrypting payload |
| 0x0000362C | 原則對應錯誤 |
Policy match error |
| 0x0000362D | 未支援的識別碼 |
Unsupported ID |
| 0x0000362E | 雜湊驗證失敗 |
Hash verification failed |
| 0x0000362F | 不正確的雜湊演算法 |
Invalid hash algorithm |
| 0x00003630 | 雜湊大小不正確 |
Invalid hash size |
| 0x00003631 | 錯誤的加密演算法 |
Invalid encryption algorithm |
| 0x00003632 | 錯誤的驗證演算法 |
Invalid authentication algorithm |
| 0x00003633 | 不正確的憑證簽章 |
Invalid certificate signature |
| 0x00003634 | 載入失敗 |
Load failed |
| 0x00003635 | 已藉由 RPC 呼叫刪除 |
Deleted via RPC call |
| 0x00003636 | 建立了臨時狀態以便執行重新初始化。這不是真正的失敗。 |
Temporary state created to perform reinitialization. This is not a real failure. |
| 0x00003637 | 回應程式存留期通知中所收到的存留期的值低於 Windows 2000 所設定的最小值。請在對等電腦上修復原則。 |
The lifetime value received in the Responder Lifetime Notify is below the Windows 2000 configured minimum value. Please fix the policy on the peer machine. |
| 0x00003638 | 收件者無法處理標頭中指定的 IKE 版本。 |
The recipient cannot handle version of IKE specified in the header. |
| 0x00003639 | 憑證的金鑰長度太短，不符合設定的安全性需求。 |
Key length in certificate is too small for configured security requirements. |
| 0x0000363A | 已建立至對等的 MM SA 數目已超過最大值。 |
Max number of established MM SAs to peer exceeded. |
| 0x0000363B | IKE 接收到停用交涉的原則。 |
IKE received a policy that disables negotiation. |
| 0x0000363C | 已到達主要模式的快速模式限制上限。將會啟動新的主要模式。 |
Reached maximum quick mode limit for the main mode. New main mode will be started. |
| 0x0000363D | 主要模式 SA 存留期已到期，或其他模式已傳送主要模式刪除。 |
Main mode SA lifetime expired or peer sent a main mode delete. |
| 0x0000363E | 因為其他模式停止回應，所以主要模式 SA 將繼續為無效。 |
Main mode SA assumed to be invalid because peer stopped responding. |
| 0x0000363F | 憑證無法鏈結到 IPsec 原則中的信任根目錄。 |
Certificate doesn't chain to a trusted root in IPsec policy. |
| 0x00003640 | 已收到非預期的訊息識別碼。 |
Received unexpected message ID. |
| 0x00003641 | 已收到無效的驗證提供。 |
Received invalid authentication offers. |
| 0x00003642 | 已將 DoS Cookie 通知傳送給啟動器。 |
Sent DoS cookie notify to initiator. |
| 0x00003643 | IKE 服務正在關閉。 |
IKE service is shutting down. |
| 0x00003644 | 無法驗證 CGA 位址及憑證間的繫結。 |
Could not verify binding between CGA address and certificate. |
| 0x00003645 | 處理 NatOA 內容時發生錯誤。 |
Error processing NatOA payload. |
| 0x00003646 | 此快速模式的主要模式參數無效。 |
Parameters of the main mode are invalid for this quick mode. |
| 0x00003647 | IPsec 驅動程式已將快速模式 SA 終止。 |
Quick mode SA was expired by IPsec driver. |
| 0x00003648 | 已偵測到太多動態新增的 IKEEXT 篩選器。 |
Too many dynamically added IKEEXT filters were detected. |
| 0x00003649 | ERROR_IPSEC_IKE_NEG_STATUS_END |
ERROR_IPSEC_IKE_NEG_STATUS_END |
| 0x0000364A | NAP 已順利重新驗證，且必須刪除虛設 NAP IKEv2 通道。 |
NAP reauth succeeded and must delete the dummy NAP IKEv2 tunnel. |
| 0x0000364B | 在通道模式中將內部 IP 位址指派給啟動器時發生錯誤。 |
Error in assigning inner IP address to initiator in tunnel mode. |
| 0x0000364C | 所需的設定內容遺失。 |
Require configuration payload missing. |
| 0x0000364D | 以發行連線的安全性主體執行的交涉正在進行中 |
A negotiation running as the security principle who issued the connection is in progress |
| 0x0000364E | 由於 IKEv1/AuthIP 共同存在會抑制檢查，已經刪除 SA。 |
SA was deleted due to IKEv1/AuthIP co-existence suppress check. |
| 0x0000364F | 由於對等 IP 位址速率限制，已丟棄連入 SA 要求。 |
Incoming SA request was dropped due to peer IP address rate limiting. |
| 0x00003650 | 對等不支援 MOBIKE。 |
Peer does not support MOBIKE. |
| 0x00003651 | 未獲授權建立 SA。 |
SA establishment is not authorized. |
| 0x00003652 | 未獲授權建立 SA，因為缺乏足夠強度的 PKINIT 認證。 |
SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. |
| 0x00003653 | 未獲授權建立 SA。您可能需要輸入更新的認證或其他認證 (例如，智慧卡)。 |
SA establishment is not authorized. You may need to enter updated or different credentials such as a smartcard. |
| 0x00003654 | 未獲授權建立 SA，因為缺乏足夠強度的 PKINIT 認證。這可能與 SA 的憑證對帳戶對應失敗相關。 |
SA establishment is not authorized because there is not a sufficiently strong PKINIT-based credential. This might be related to certificate-to-account mapping failure for the SA. |
| 0x00003655 | ERROR_IPSEC_IKE_NEG_STATUS_EXTENDED_END |
ERROR_IPSEC_IKE_NEG_STATUS_EXTENDED_END |
| 0x00003656 | 封包中的 SPI 與有效的 IPsec SA 不相符。 |
The SPI in the packet does not match a valid IPsec SA. |
| 0x00003657 | IPsec SA 收到存留期已到期的封包。 |
Packet was received on an IPsec SA whose lifetime has expired. |
| 0x00003658 | IPsec SA 收到與封包特性不相符的封包。 |
Packet was received on an IPsec SA that does not match the packet characteristics. |
| 0x00003659 | 封包序號重新執行檢查失敗。 |
Packet sequence number replay check failed. |
| 0x0000365A | 封包中的 IPsec 標頭和/或尾端不正確。 |
IPsec header and/or trailer in the packet is invalid. |
| 0x0000365B | IPsec 完整性檢查失敗。 |
IPsec integrity check failed. |
| 0x0000365C | IPsec 已丟棄純文字封包。 |
IPsec dropped a clear text packet. |
| 0x0000365D | IPsec 已在驗證的防火牆模式中丟棄連入 ESP 封包。這是有益的丟棄操作。 |
IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign. |
| 0x0000365E | 由於 DoS 節流，IPsec 已經丟棄封包。 |
IPsec dropped a packet due to DoS throttling. |
| 0x00003665 | IPsec DoS Protection 符合明確封鎖規則。 |
IPsec DoS Protection matched an explicit block rule. |
| 0x00003666 | IPsec DoS Protection 收到不允許的 IPsec 特定多點傳送封包。 |
IPsec DoS Protection received an IPsec specific multicast packet which is not allowed. |
| 0x00003667 | IPsec DoS Protection 收到格式不正確的封包。 |
IPsec DoS Protection received an incorrectly formatted packet. |
| 0x00003668 | IPsec DoS Protection 無法查詢狀態。 |
IPsec DoS Protection failed to look up state. |
| 0x00003669 | IPsec DoS Protection 無法建立狀態，因為已達到原則允許的項目數目上限。 |
IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached. |
| 0x0000366A | IPsec DoS Protection 收到原則不允許之金鑰處理模組的 IPsec 交涉封包。 |
IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy. |
| 0x0000366B | 尚未啟用 IPsec DoS Protection。 |
IPsec DoS Protection has not been enabled. |
| 0x0000366C | IPsec DoS Protection 無法建立每個內部 IP 的速率限制佇列，因為已達到原則允許的佇列數目上限。 |
IPsec DoS Protection failed to create a per internal IP rate limit queue because the maximum number of queues allowed by policy has been reached. |
| 0x000036B0 | 所要求的區段不存在於啟用內容中。 |
The requested section was not present in the activation context. |
| 0x000036B1 | 因為應用程式的並列設定不正確，所以無法啟動。如需詳細資訊，請參閱應用程式事件記錄檔，或使用命令列工具 sxstrace.exe。 |
The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. |
| 0x000036B2 | 應用程式連結資料的格式不正確。 |
The application binding data format is invalid. |
| 0x000036B3 | 參照的組合沒有安裝在您的系統中。 |
The referenced assembly is not installed on your system. |
| 0x000036B4 | 資訊清單檔案的開端沒有必需的標籤和格式資訊。 |
The manifest file does not begin with the required tag and format information. |
| 0x000036B5 | 資訊清單檔案包含一個或以上的語法錯誤。 |
The manifest file contains one or more syntax errors. |
| 0x000036B6 | 應用程式嘗試啟動已停用的啟用內容。 |
The application attempted to activate a disabled activation context. |
| 0x000036B7 | 在所有使用中的啟用內容中都找不到所要求的對應機碼。 |
The requested lookup key was not found in any active activation context. |
| 0x000036B8 | 應用程式必需的元件版本和另一個使用中的元件版本衝突。 |
A component version required by the application conflicts with another component version already active. |
| 0x000036B9 | 要求的啟用內容區段類型與 API 所使用的查詢不相符。 |
The type requested activation context section does not match the query API used. |
| 0x000036BA | 缺乏系統資源，所以必須在目前的執行緒停用孤立啟用。 |
Lack of system resources has required isolated activation to be disabled for the current thread of execution. |
| 0x000036BB | 企圖設定處理程序預設啟用內容的嘗試失敗，原因是處理程序預設啟用內容已經設定了。 |
An attempt to set the process default activation context failed because the process default activation context was already set. |
| 0x000036BC | 無法辨識所指定的編碼群組識別元。 |
The encoding group identifier specified is not recognized. |
| 0x000036BD | 無法辨識所要求的編碼。 |
The encoding requested is not recognized. |
| 0x000036BE | 資訊清單含有不正確 URI 的參照。 |
The manifest contains a reference to an invalid URI. |
| 0x000036BF | 應用程式資訊清單含有未安裝之依存組合的參照 |
The application manifest contains a reference to a dependent assembly which is not installed |
| 0x000036C0 | 應用程式使用的組合資訊清單含有未安裝之依存組合的參照 |
The manifest for an assembly used by the application has a reference to a dependent assembly which is not installed |
| 0x000036C1 | 資訊清單含有不正確的組合識別屬性。 |
The manifest contains an attribute for the assembly identity which is not valid. |
| 0x000036C2 | 資訊清單遺失了組合元素所必需的預設命名空間規格。 |
The manifest is missing the required default namespace specification on the assembly element. |
| 0x000036C3 | 資訊清單有組合元素指定的預設命名空間，但是它的值不是 \"urn:schemas-microsoft-com:asm.v1\"。 |
The manifest has a default namespace specified on the assembly element but its value is not \"urn:schemas-microsoft-com:asm.v1\". |
| 0x000036C4 | 所探查的私密資訊清單讓路徑在不支援的重新分析點交叉。 |
The private manifest probed has crossed a path with an unsupported reparse point. |
| 0x000036C5 | 應用程式資訊清單直接或間接參照到的兩個以上的元件有相同名稱的檔案。 |
Two or more components referenced directly or indirectly by the application manifest have files by the same name. |
| 0x000036C6 | 應用程式資訊清單直接或間接參照到的兩個以上的元件有相同名稱的視窗類別。 |
Two or more components referenced directly or indirectly by the application manifest have window classes with the same name. |
| 0x000036C7 | 應用程式資訊清單直接或間接參照到的兩個以上的元件有相同的 COM 伺服器 CLSID。 |
Two or more components referenced directly or indirectly by the application manifest have the same COM server CLSIDs. |
| 0x000036C8 | 應用程式資訊清單直接或間接參照到的兩個以上的元件有相同 COM 介面 IID 的 Proxy。 |
Two or more components referenced directly or indirectly by the application manifest have proxies for the same COM interface IIDs. |
| 0x000036C9 | 應用程式資訊清單直接或間接參照到的兩個以上的元件有相同的 COM 類型程式庫 TLBID。 |
Two or more components referenced directly or indirectly by the application manifest have the same COM type library TLBIDs. |
| 0x000036CA | 應用程式資訊清單直接或間接參照到的兩個以上的元件有相同的 COM ProgID。 |
Two or more components referenced directly or indirectly by the application manifest have the same COM ProgIDs. |
| 0x000036CB | 應用程式資訊清單直接或間接參照到的兩個以上的元件是同一元件，但不同版本，這是不允許的。 |
Two or more components referenced directly or indirectly by the application manifest are different versions of the same component which is not permitted. |
| 0x000036CC | 元件檔與元件資訊清單中所存在的驗證資訊不相符合。 |
A component's file does not match the verification information present in the component manifest. |
| 0x000036CD | 原則資訊清單包含一個或以上的語法錯誤。 |
The policy manifest contains one or more syntax errors. |
| 0x000036CE | 資訊清單分析錯誤 : 需要字串文字，但是找不到開啟的引號字元。 |
Manifest Parse Error : A string literal was expected, but no opening quote character was found. |
| 0x000036CF | 資訊清單分析錯誤 : 註解使用了不正確的語法。 |
Manifest Parse Error : Incorrect syntax was used in a comment. |
| 0x000036D0 | 資訊清單分析錯誤 : 名稱的起始字元不正確。 |
Manifest Parse Error : A name was started with an invalid character. |
| 0x000036D1 | 資訊清單分析錯誤 : 名稱包含了不正確的字元。 |
Manifest Parse Error : A name contained an invalid character. |
| 0x000036D2 | 資訊清單分析錯誤 : 字串文字包含了不正確的字元。 |
Manifest Parse Error : A string literal contained an invalid character. |
| 0x000036D3 | 資訊清單分析錯誤 : xml 宣告的語法不正確。 |
Manifest Parse Error : Invalid syntax for an xml declaration. |
| 0x000036D4 | 資訊清單分析錯誤 : 文字內容中找到不正確的字元。 |
Manifest Parse Error : An Invalid character was found in text content. |
| 0x000036D5 | 資訊清單分析錯誤 : 遺失了必需的空白區。 |
Manifest Parse Error : Required white space was missing. |
| 0x000036D6 | 資訊清單分析錯誤 : 需要 '' 字元。 |
Manifest Parse Error : The character '' was expected. |
| 0x000036D7 | 資訊清單分析錯誤 : 需要分號字元。 |
Manifest Parse Error : A semi colon character was expected. |
| 0x000036D8 | 資訊清單分析錯誤 : 括號不均衡。 |
Manifest Parse Error : Unbalanced parentheses. |
| 0x000036D9 | 資訊清單分析錯誤 : 內部錯誤。 |
Manifest Parse Error : Internal error. |
| 0x000036DA | 資訊清單分析錯誤 : 這個位置不允許空白區。 |
Manifest Parse Error : Whitespace is not allowed at this location. |
| 0x000036DB | 資訊清單分析錯誤 : 檔案結尾進入了目前編碼的不正確狀態。 |
Manifest Parse Error : End of file reached in invalid state for current encoding. |
| 0x000036DC | 資訊清單分析錯誤 : 遺失了括號。 |
Manifest Parse Error : Missing parenthesis. |
| 0x000036DD | 資訊清單分析錯誤 : 遺失了關閉用的單引號或雙引號字元 (\\' 或 \\\")。 |
Manifest Parse Error : A single or double closing quote character (\\' or \\\") is missing. |
| 0x000036DE | 資訊清單分析錯誤 : 名稱中不允許多重冒號。 |
Manifest Parse Error : Multiple colons are not allowed in a name. |
| 0x000036DF | 資訊清單分析錯誤 : 不正確的十進位字元。 |
Manifest Parse Error : Invalid character for decimal digit. |
| 0x000036E0 | 資訊清單分析錯誤 : 不正確的十六進位字元。 |
Manifest Parse Error : Invalid character for hexadecimal digit. |
| 0x000036E1 | 資訊清單分析錯誤 : 這個平台上不正確的 Unicode 字元值。 |
Manifest Parse Error : Invalid unicode character value for this platform. |
| 0x000036E2 | 資訊清單分析錯誤 : 需要空白區或 '?'。 |
Manifest Parse Error : Expecting whitespace or '?'. |
| 0x000036E3 | 資訊清單分析錯誤 : 這個位置不需要結尾標籤。 |
Manifest Parse Error : End tag was not expected at this location. |
| 0x000036E4 | 資訊清單分析錯誤 : 下列標籤沒有關閉: %1。 |
Manifest Parse Error : The following tags were not closed: %1. |
| 0x000036E5 | 資訊清單分析錯誤 : 屬性重複。 |
Manifest Parse Error : Duplicate attribute. |
| 0x000036E6 | 資訊清單分析錯誤 : XML 文件中只允許一個最上層元素。 |
Manifest Parse Error : Only one top level element is allowed in an XML document. |
| 0x000036E7 | 資訊清單分析錯誤 : 文件的最上層不正確。 |
Manifest Parse Error : Invalid at the top level of the document. |
| 0x000036E8 | 資訊清單分析錯誤 : xml 宣告不正確。 |
Manifest Parse Error : Invalid xml declaration. |
| 0x000036E9 | 資訊清單分析錯誤 : XML 文件必須有一個最上層元素。 |
Manifest Parse Error : XML document must have a top level element. |
| 0x000036EA | 資訊清單分析錯誤 : 意外的檔案結尾。 |
Manifest Parse Error : Unexpected end of file. |
| 0x000036EB | 資訊清單分析錯誤 : 參數項目不能使用在內部子集合的標記宣告中。 |
Manifest Parse Error : Parameter entities cannot be used inside markup declarations in an internal subset. |
| 0x000036EC | 資訊清單分析錯誤 : 未關閉元素。 |
Manifest Parse Error : Element was not closed. |
| 0x000036ED | 資訊清單分析錯誤 : 結尾元素遺失了 '' 字元。 |
Manifest Parse Error : End element was missing the character ''. |
| 0x000036EE | 資訊清單分析錯誤 : 未關閉字串文字。 |
Manifest Parse Error : A string literal was not closed. |
| 0x000036EF | 資訊清單分析錯誤 : 未關閉註解。 |
Manifest Parse Error : A comment was not closed. |
| 0x000036F0 | 資訊清單分析錯誤 : 未關閉宣告。 |
Manifest Parse Error : A declaration was not closed. |
| 0x000036F1 | 資訊清單分析錯誤 : 未關閉 CDATA 區段。 |
Manifest Parse Error : A CDATA section was not closed. |
| 0x000036F2 | 資訊清單分析錯誤 : 命名空間的字首不能夠以保留字串 \"xml\" 起始。 |
Manifest Parse Error : The namespace prefix is not allowed to start with the reserved string \"xml\". |
| 0x000036F3 | 資訊清單分析錯誤 : 系統不支援所指定的編碼。 |
Manifest Parse Error : System does not support the specified encoding. |
| 0x000036F4 | 資訊清單分析錯誤 : 不支援從目前的編碼切換到指定的編碼。 |
Manifest Parse Error : Switch from current encoding to specified encoding not supported. |
| 0x000036F5 | 資訊清單分析錯誤 : 'xml' 是保留名稱，必須全部小寫。 |
Manifest Parse Error : The name 'xml' is reserved and must be lower case. |
| 0x000036F6 | 資訊清單分析錯誤 : 獨立單機的屬性必須有 '是' 或 '否' 值。 |
Manifest Parse Error : The standalone attribute must have the value 'yes' or 'no'. |
| 0x000036F7 | 資訊清單分析錯誤 : 獨立單機的屬性不能夠使用在外部項目。 |
Manifest Parse Error : The standalone attribute cannot be used in external entities. |
| 0x000036F8 | 資訊清單分析錯誤 : 版本號碼不正確。 |
Manifest Parse Error : Invalid version number. |
| 0x000036F9 | 資訊清單分析錯誤 : 屬性及屬性值之間遺失了等號。 |
Manifest Parse Error : Missing equals sign between attribute and attribute value. |
| 0x000036FA | 組合保護錯誤 : 無法復原指定的組合。 |
Assembly Protection Error : Unable to recover the specified assembly. |
| 0x000036FB | 組合保護錯誤 : 組合的公開金鑰太短，因此不准使用。 |
Assembly Protection Error : The public key for an assembly was too short to be allowed. |
| 0x000036FC | 組合保護錯誤 : 組合的類別目錄不正確，或者不符合組合的資訊清單。 |
Assembly Protection Error : The catalog for an assembly is not valid, or does not match the assembly's manifest. |
| 0x000036FD | HRESULT 不能轉譯成對應的 Win32 錯誤碼。 |
An HRESULT could not be translated to a corresponding Win32 error code. |
| 0x000036FE | 組合保護錯誤 : 遺失了組合的類別目錄。 |
Assembly Protection Error : The catalog for an assembly is missing. |
| 0x000036FF | 提供的組合身分遺失一或多個在這個內容中必須有的屬性。 |
The supplied assembly identity is missing one or more attributes which must be present in this context. |
| 0x00003700 | 提供的組合身分有一或多個屬性名稱包含在 XML 名稱中不允許的字元。 |
The supplied assembly identity has one or more attribute names that contain characters not permitted in XML names. |
| 0x00003701 | 找不到參照組合。 |
The referenced assembly could not be found. |
| 0x00003702 | 屬於執行中的執行緒的啟用內容堆疊已毀損。 |
The activation context activation stack for the running thread of execution is corrupt. |
| 0x00003703 | 此處理程序或執行緒的應用程式隔離中繼資料已損毀。 |
The application isolation metadata for this process or thread has become corrupt. |
| 0x00003704 | 正在停用的啟用內容不是最近啟動的那一個。 |
The activation context being deactivated is not the most recently activated one. |
| 0x00003705 | 正在停用的啟用內容在目前的執行緒中未使用。 |
The activation context being deactivated is not active for the current thread of execution. |
| 0x00003706 | 正在停用的啟用內容已經停用了。 |
The activation context being deactivated has already been deactivated. |
| 0x00003707 | 由孤立設備所使用的元件要求中斷程序。 |
A component used by the isolation facility has requested to terminate the process. |
| 0x00003708 | 核心模式元件正在啟用內容中釋放參照。 |
A kernel mode component is releasing a reference on an activation context. |
| 0x00003709 | 無法產生系統預設組合的啟用內容。 |
The activation context of system default assembly could not be generated. |
| 0x0000370A | 識別碼中的屬性值不在合法的範圍內。 |
The value of an attribute in an identity is not within the legal range. |
| 0x0000370B | 識別碼中的屬性名稱不在合法的範圍內。 |
The name of an attribute in an identity is not within the legal range. |
| 0x0000370C | 識別碼的同個屬性包含兩個定義。 |
An identity contains two definitions for the same attribute. |
| 0x0000370D | 識別碼字串的格式錯誤。原因可能是結尾的逗號、超過兩個未命名的屬性、遺失屬性名稱或遺失屬性值所造成。 |
The identity string is malformed. This may be due to a trailing comma, more than two unnamed attributes, missing attribute name or missing attribute value. |
| 0x0000370E | 包含本土化可取代內容的字串格式錯誤。不是貨幣符號 ($) 後面跟的不是左括號，就是找不到另一個貨幣符號或替代項目的右括號。 |
A string containing localized substitutable content was malformed. Either a dollar sign ($) was followed by something other than a left parenthesis or another dollar sign or an substitution's right parenthesis was not found. |
| 0x0000370F | 公開金鑰權杖未對應指定的公開金鑰。 |
The public key token does not correspond to the public key specified. |
| 0x00003710 | 替代字串沒有任何對應項目。 |
A substitution string had no mapping. |
| 0x00003711 | 進行要求前，必須先鎖定元件。 |
The component must be locked before making the request. |
| 0x00003712 | 元件存放區已損毀。 |
The component store has been corrupted. |
| 0x00003713 | 進階安裝程式在安裝或服務期間失敗。 |
An advanced installer failed during setup or servicing. |
| 0x00003714 | XML 宣告的字元編碼不符合文件中使用的編碼。 |
The character encoding in the XML declaration did not match the encoding used in the document. |
| 0x00003715 | 各個資訊清單的識別碼都相同，但是內容不同。 |
The identities of the manifests are identical but their contents are different. |
| 0x00003716 | 元件識別碼不同。 |
The component identities are different. |
| 0x00003717 | 組合不是部署。 |
The assembly is not a deployment. |
| 0x00003718 | 檔案不是組合的一部分。 |
The file is not a part of the assembly. |
| 0x00003719 | 資訊清單的大小超過允許的上限。 |
The size of the manifest exceeds the maximum allowed. |
| 0x0000371A | 設定未登錄。 |
The setting is not registered. |
| 0x0000371B | 一或多個必要的交易成員不存在。 |
One or more required members of the transaction are not present. |
| 0x0000371C | SMI 基本安裝程式在安裝或服務期間失敗。 |
The SMI primitive installer failed during setup or servicing. |
| 0x0000371D | 一般命令可執行檔傳回結果，表示發生失敗。 |
A generic command executable returned a result that indicates failure. |
| 0x0000371E | 元件在其資訊清單遺失檔案驗證資訊。 |
A component is missing file verification information in its manifest. |
| 0x00003A98 | 指定的通道路徑無效。 |
The specified channel path is invalid. |
| 0x00003A99 | 指定的查詢無效。 |
The specified query is invalid. |
| 0x00003A9A | 在資源中找不到發行者中繼資料。 |
The publisher metadata cannot be found in the resource. |
| 0x00003A9B | 在資源中找不到事件定義的範本 (錯誤 = %1)。 |
The template for an event definition cannot be found in the resource (error = %1). |
| 0x00003A9C | 指定的發行者名稱無效。 |
The specified publisher name is invalid. |
| 0x00003A9D | 發行者引發的事件資料與發行者資訊清單中的事件範本定義不相容 |
The event data raised by the publisher is not compatible with the event template definition in the publisher's manifest |
| 0x00003A9F | 找不到指定的通道。請檢查通道組態。 |
The specified channel could not be found. Check channel configuration. |
| 0x00003AA0 | 指定的 xml 文字語式錯誤。如需詳細資訊，請參閱＜延伸的錯誤＞。 |
The specified xml text was not well-formed. See Extended Error for more details. |
| 0x00003AA1 | 呼叫者正嘗試訂閱直接通道，但不允許這個動作。直接通道的事件會直接移到記錄檔，且無法被訂閱。 |
The caller is trying to subscribe to a direct channel which is not allowed. The events for a direct channel go directly to a logfile and cannot be subscribed to. |
| 0x00003AA2 | 組態錯誤。 |
Configuration error. |
| 0x00003AA3 | 查詢結果過期 / 無效。原因可能是在建立查詢結果後，清除記錄檔或記錄檔轉動。使用者應該釋放查詢結果物件並重新發出查詢來管理此程式碼。 |
The query result is stale / invalid. This may be due to the log being cleared or rolling over after the query result was created. Users should handle this code by releasing the query result object and reissuing the query. |
| 0x00003AA4 | 查詢結果目前處於無效的位置中。 |
Query result is currently at an invalid position. |
| 0x00003AA5 | 登錄的 MSXML 不支援驗證。 |
Registered MSXML doesn't support validation. |
| 0x00003AA6 | 如果運算式自我評估為節點組且不是某些其他範圍作業變更的一部分，運算式後面才可以接範圍作業的變更。 |
An expression can only be followed by a change of scope operation if it itself evaluates to a node set and is not already part of some other change of scope operation. |
| 0x00003AA7 | 無法從不代表元素集的術語執行步驟作業。 |
Can't perform a step operation from a term that does not represent an element set. |
| 0x00003AA8 | 二進位檔的左邊引數必須是屬性、節點或變數，而右邊引數必須是常數。 |
Left hand side arguments to binary operators must be either attributes, nodes or variables and right hand side arguments must be constants. |
| 0x00003AA9 | 步驟運算必須包含節點測試，如果是使用述詞，則必須包含用以對前一個節點集識別之節點集中的每個節點，進行測試的代數運算式，如此才能進行評估。 |
A step operation must involve either a node test or, in the case of a predicate, an algebraic expression against which to test each node in the node set identified by the preceeding node set can be evaluated. |
| 0x00003AAA | 目前不支援此資料類型。 |
This data type is currently unsupported. |
| 0x00003AAB | 在位置 %1!d! 發生語法錯誤。 |
A syntax error occurred at position %1!d! |
| 0x00003AAC | 此篩選器的執行不支援此運算子。 |
This operator is unsupported by this implementation of the filter. |
| 0x00003AAD | 發現的權杖不是預期的。 |
The token encountered was unexpected. |
| 0x00003AAE | 要求的作業無法透過啟用的直接通道執行。在執行要求的作業之前，必須先停用通道。 |
The requested operation cannot be performed over an enabled direct channel. The channel must first be disabled before performing the requested operation. |
| 0x00003AAF | 通道屬性 %1!s! 包含不正確的值。該值的類型無效 (不在有效範圍內)，此類型的通道無法更新或不支援該值。 |
Channel property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can't be updated or is not supported by this type of channel. |
| 0x00003AB0 | 發行者屬性 %1!s! 包含不正確的值。該值的類型無效 (不在有效範圍內)，此類型的發行者無法更新或不支援該值。 |
Publisher property %1!s! contains invalid value. The value has invalid type, is outside of valid range, can't be updated or is not supported by this type of publisher. |
| 0x00003AB1 | 通道無法啟動。 |
The channel fails to activate. |
| 0x00003AB2 | Xpath 運算式超過支援的複雜度。請將它簡化或將運算式分開為兩或多個簡單的運算式。 |
The xpath expression exceeded supported complexity. Please symplify it or split it into two or more simple expressions. |
| 0x00003AB3 | 已提供訊息資源，但在字串/訊息表中找不到訊息 |
the message resource is present but the message is not found in the string/message table |
| 0x00003AB4 | 找不到所需訊息的訊息識別碼。 |
The message id for the desired message could not be found. |
| 0x00003AB5 | 找不到插入索引 (%1) 的替代字串。 |
The substitution string for insert index (%1) could not be found. |
| 0x00003AB6 | 找不到參數參照 (%1) 的描述字串。 |
The description string for parameter reference (%1) could not be found. |
| 0x00003AB7 | 已達到替代項目的數目上限。 |
The maximum number of replacements has been reached. |
| 0x00003AB8 | 找不到事件識別碼 (%1) 的事件定義。 |
The event definition could not be found for event id (%1). |
| 0x00003AB9 | 所需訊息的地區設定特定資源不存在。 |
The locale specific resource for the desired message is not present. |
| 0x00003ABA | 資源太舊而無法相容。 |
The resource is too old to be compatible. |
| 0x00003ABB | 資源太新而無法相容。 |
The resource is too new to be compatible. |
| 0x00003ABC | 無法在查詢的索引 %1!d! 開啟通道。 |
The channel at index %1!d! of the query can't be opened. |
| 0x00003ABD | 發行者已被停用，而其資源無法供使用。這通常發生於正在解除安裝或升級發行者的時候。 |
The publisher has been disabled and its resource is not available. This usually occurs when the publisher is in the process of being uninstalled or upgraded. |
| 0x00003ABE | 嘗試建立超出有效範圍的數字類型。 |
Attempted to create a numeric type that is outside of its valid range. |
| 0x00003AE8 | 訂閱無法啟動。 |
The subscription fails to activate. |
| 0x00003AE9 | 訂閱的記錄檔正處於停用的狀態，所以無法用來轉送事件。必須先啟用記錄檔，才能啟動訂閱。 |
The log of the subscription is in disabled state, and can not be used to forward events to. The log must first be enabled before the subscription can be activated. |
| 0x00003AEA | 將本機電腦的事件轉寄給本機本身時，訂閱查詢無法包含訂閱的目標記錄檔。 |
When forwarding events from local machine to itself, the query of the subscription can't contain target log of the subscription. |
| 0x00003AEB | 用以儲存認證的認證存放區已滿。 |
The credential store that is used to save credentials is full. |
| 0x00003AEC | 在認證存放區中找不到此訂閱使用的認證。 |
The credential used by this subscription can't be found in credential store. |
| 0x00003AED | 找不到用於該查詢的使用中通道。 |
No active channel is found for the query. |
| 0x00003AFC | 資源載入器找不到 MUI 檔案。 |
The resource loader failed to find MUI file. |
| 0x00003AFD | 資源載入器無法載入 MUI 檔案，因為該檔案無法通過驗證。 |
The resource loader failed to load MUI file because the file fail to pass validation. |
| 0x00003AFE | RC Manifest 損毀，並含有不需要的資料或不支援的版本，或者遺失必要項目。 |
The RC Manifest is corrupted with garbage data or unsupported version or missing required item. |
| 0x00003AFF | RC Manifest 具有不正確的文化特性名稱。 |
The RC Manifest has invalid culture name. |
| 0x00003B00 | RC Manifest 具有不正確的 ultimatefallback 名稱。 |
The RC Manifest has invalid ultimatefallback name. |
| 0x00003B01 | 資源載入器快取未載入 MUI 項目。 |
The resource loader cache doesn't have loaded MUI entry. |
| 0x00003B02 | 使用者已經停止資源列舉。 |
User stopped resource enumeration. |
| 0x00003B03 | UI 語言安裝失敗。 |
UI language installation failed. |
| 0x00003B04 | 地區設定安裝失敗。 |
Locale installation failed. |
| 0x00003B06 | 資源沒有預設值或中性值。 |
A resource does not have default or neutral value. |
| 0x00003B07 | 無效的 PRI 組態檔。 |
Invalid PRI config file. |
| 0x00003B08 | 檔案類型無效。 |
Invalid file type. |
| 0x00003B09 | 不明的限定詞。 |
Unknown qualifier. |
| 0x00003B0A | 無效的限定詞值。 |
Invalid qualifier value. |
| 0x00003B0B | 找不到候選項目。 |
No Candidate found. |
| 0x00003B0C | ResourceMap 或 NamedResource 的某個項目沒有預設或中性的資源。 |
The ResourceMap or NamedResource has an item that does not have default or neutral resource.. |
| 0x00003B0D | 無效的 ResourceCandidate 類型。 |
Invalid ResourceCandidate type. |
| 0x00003B0E | 重複的資源對應。 |
Duplicate Resource Map. |
| 0x00003B0F | 重複的項目。 |
Duplicate Entry. |
| 0x00003B10 | 無效的資源識別碼。 |
Invalid Resource Identifier. |
| 0x00003B11 | 檔案路徑太長。 |
Filepath too long. |
| 0x00003B12 | 不支援的目錄類型。 |
Unsupported directory type. |
| 0x00003B16 | 無效的 PRI 檔案。 |
Invalid PRI File. |
| 0x00003B17 | 找不到 NamedResource。 |
NamedResource Not Found. |
| 0x00003B1F | 找不到 ResourceMap。 |
ResourceMap Not Found. |
| 0x00003B20 | 不支援的 MRT 設定檔類型。 |
Unsupported MRT profile type. |
| 0x00003B21 | 無效的限定詞運算子。 |
Invalid qualifier operator. |
| 0x00003B22 | 無法判斷限定詞值，或未設定限定詞值。 |
Unable to determine qualifier value or qualifier value has not been set. |
| 0x00003B23 | 已在 PRI 檔案中啟用自動合併。 |
Automerge is enabled in the PRI file. |
| 0x00003B24 | 為套件定義的資源太多。 |
Too many resources defined for package. |
| 0x00003B25 | 資源檔不能用於合併操作。 |
Resource File can not be used for merge operation. |
| 0x00003B26 | Load/UnloadPriFiles 無法用於資源套件。 |
Load/UnloadPriFiles cannot be used with resource packages. |
| 0x00003B27 | 無法在沒有 CoreWindow 的執行緒上建立資源內容。 |
Resource Contexts may not be created on threads that do not have a CoreWindow. |
| 0x00003B28 | 已建立具有不同設定檔的單一子句資源管理員。 |
The singleton Resource Manager with different profile is already created. |
| 0x00003B29 | 系統元件無法執行指定的 API 操作 |
The system component cannot operate given API operation |
| 0x00003B2A | 該資源是非預設資源候選項的直接參照。 |
The resource is a direct reference to a non-default resource candidate. |
| 0x00003B2B | 已重新產生「資源對應」，且查詢字串已無效。 |
Resource Map has been re-generated and the query string is not valid anymore. |
| 0x00003B2C | 要合併的 PRI 檔案具有不相容的版本。 |
The PRI files to be merged have incompatible versions. |
| 0x00003B2D | 要合併的主要 PRI 檔案未包含結構描述。 |
The primary PRI files to be merged does not contain a schema. |
| 0x00003B2E | 無法載入其中一個要合併的 PRI 檔案。 |
Unable to load one of the PRI files to be merged. |
| 0x00003B2F | 無法將其中一個 PRI 檔案新增到已合併的檔案。 |
Unable to add one of the PRI files to the merged file. |
| 0x00003B30 | 無法建立已合併的 PRI 檔案。 |
Unable to create the merged PRI file. |
| 0x00003B31 | 用於 PRI 檔案合併的套件全部都必須來自相同的套件系列。 |
Packages for a PRI file merge must all be from the same package family. |
| 0x00003B32 | 用於 PRI 檔案合併的套件不能包括多個主要套件。 |
Packages for a PRI file merge must not include multiple main packages. |
| 0x00003B33 | 用於 PRI 檔案合併的套件不能包括套件組合套件。 |
Packages for a PRI file merge must not include bundle packages. |
| 0x00003B34 | 用於 PRI 檔案合併的套件必須包括一個主要套件。 |
Packages for a PRI file merge must include one main package. |
| 0x00003B35 | 用於 PRI 檔案合併的套件必須包括至少一個資源套件。 |
Packages for a PRI file merge must include at least one resource package. |
| 0x00003B36 | 所提供的正式合併 PRI 檔案名稱無效。 |
Invalid name supplied for a canonical merged PRI file. |
| 0x00003B60 | 監視器傳回 DDC/CI 功能字串，該字串和 ACCESS.bus 3.0、 DDC/CI 1.1 或 MCCS 2 Revision 1 規格不符。 |
The monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1 or MCCS 2 Revision 1 specification. |
| 0x00003B61 | 監視器的 VCP Version (0xDF) VCP 程式碼傳回不正確的版本值。 |
The monitor's VCP Version (0xDF) VCP code returned an invalid version value. |
| 0x00003B62 | 監視器和其宣告所支援的 MCCS 規格不符。 |
The monitor does not comply with the MCCS specification it claims to support. |
| 0x00003B63 | 監視器的 mccs_ver 功能中的 mccs_ver MCCS 版本和使用 VCP Version (0xDF) VCP 程式碼時監視器所報告的 MCCS 版本不符。 |
The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used. |
| 0x00003B64 | 「監視器組態 API」只能和支援 MCCS 1.0 規格、MCCS 2.0 規格或 MCCS 2.0 Revision 1 規格的監視器一起使用。 |
The Monitor Configuration API only works with monitors that support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification. |
| 0x00003B65 | 發生內部監視器組態 API 錯誤。 |
An internal Monitor Configuration API error occurred. |
| 0x00003B66 | 監視器傳回不正確的監視器技術類型。監視器技術類型範例包括 CRT、電漿與 LCD (TFT)。此錯誤代表監視器違反 MCCS 2.0 或 MCCS 2.0 修訂 1 規格。 |
The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification. |
| 0x00003B67 | SetMonitorColorTemperature 的呼叫者指定了目前監視器不支援的色溫。此錯誤代表監視器違反 MCCS 2.0 或 MCCS 2.0 Revision 1 規格。 |
The caller of SetMonitorColorTemperature specified a color temperature that the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification. |
| 0x00003B92 | 因為多個無法識別的裝置都可能符合識別條件，所以無法識別要求的系統裝置。 |
The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria. |
| 0x00003BC3 | 找不到要求的系統裝置。 |
The requested system device cannot be found. |
| 0x00003BC4 | 未在伺服器上對指定的雜湊版本與雜湊類型啟用雜湊產生。 |
Hash generation for the specified hash version and hash type is not enabled on the server. |
| 0x00003BC5 | 從伺服器要求的雜湊無法使用或不再有效。 |
The hash requested from the server is not available or no longer valid. |
| 0x00003BD9 | 未註冊管理所指定插斷的次要插斷控制器執行個體。 |
The secondary interrupt controller instance that manages the specified interrupt is not registered. |
| 0x00003BDA | GPIO 用戶端驅動程式所提供的資訊無效。 |
The information supplied by the GPIO client driver is invalid. |
| 0x00003BDB | 不支援 GPIO 用戶端驅動程式所指定的版本。 |
The version specified by the GPIO client driver is not supported. |
| 0x00003BDC | GPIO 用戶端驅動程式所提供的註冊封包無效。 |
The registration packet supplied by the GPIO client driver is not valid. |
| 0x00003BDD | 指定的控制代碼不支援要求的作業。 |
The requested operation is not suppported for the specified handle. |
| 0x00003BDE | 要求的連線模式與一或多個所指定 Pin 上的現有模式衝突。 |
The requested connect mode conflicts with an existing mode on one or more of the specified pins. |
| 0x00003BDF | 要求取消遮罩的插斷並未進行遮罩。 |
The interrupt requested to be unmasked is not masked. |
| 0x00003C28 | 無法順利完成要求的執行層級切換。 |
The requested run level switch cannot be completed successfully. |
| 0x00003C29 | 服務的執行層級設定無效。服務的執行層級不能高於其依存服務的執行層級。 |
The service has an invalid run level setting. The run level for a servicemust not be higher than the run level of its dependent services. |
| 0x00003C2A | 因為有一或多個服務將無法在指定的逾時內停止或重新啟動，所以無法順利完成要求的執行層級切換。 |
The requested run level switch cannot be completed successfully sinceone or more services will not stop or restart within the specified timeout. |
| 0x00003C2B | 執行層級切換代理程式未在指定的逾時內回應。 |
A run level switch agent did not respond within the specified timeout. |
| 0x00003C2C | 目前正在進行執行層級切換。 |
A run level switch is currently in progress. |
| 0x00003C2D | 在執行層級切換的服務啟動階段期間，無法啟動一個或多個服務。 |
One or more services failed to start during the service startup phase of a run level switch. |
| 0x00003C8D | 無法立即完成工作停止要求，因為工作需要更多時間才能關閉。 |
The task stop request cannot be completed immediately sincetask needs more time to shutdown. |
| 0x00003CF0 | 無法開啟套件。 |
Package could not be opened. |
| 0x00003CF1 | 找不到套件。 |
Package was not found. |
| 0x00003CF2 | 套件資料無效。 |
Package data is invalid. |
| 0x00003CF3 | 套件無法進行更新、相依性或衝突驗證。 |
Package failed updates, dependency or conflict validation. |
| 0x00003CF4 | 您電腦上沒有足夠的磁碟空間。請釋放一些空間，然後再試一次。 |
There is not enough disk space on your computer. Please free up some space and try again. |
| 0x00003CF5 | 下載產品時發生問題。 |
There was a problem downloading your product. |
| 0x00003CF6 | 無法註冊套件。 |
Package could not be registered. |
| 0x00003CF7 | 無法取消註冊套件。 |
Package could not be unregistered. |
| 0x00003CF8 | 使用者已取消安裝要求。 |
User cancelled the install request. |
| 0x00003CF9 | 安裝失敗。請連絡您的軟體廠商。 |
Install failed. Please contact your software vendor. |
| 0x00003CFA | 移除失敗。請連絡您的軟體廠商。 |
Removal failed. Please contact your software vendor. |
| 0x00003CFB | 已安裝過提供的套件，不允許重新安裝此套件。請參閱 AppXDeployment-Server 事件記錄檔以取得詳細資料。 |
The provided package is already installed, and reinstallation of the package was blocked. Check the AppXDeployment-Server event log for details. |
| 0x00003CFC | 無法啟動應用程式。請嘗試重新安裝應用程式以修正問題。 |
The application cannot be started. Try reinstalling the application to fix the problem. |
| 0x00003CFD | 無法滿足安裝的必要條件。 |
A Prerequisite for an install could not be satisfied. |
| 0x00003CFE | 套件存放庫損毀。 |
The package repository is corrupted. |
| 0x00003CFF | 若要安裝此應用程式，您需要 Windows 開發人員授權或支援側載的系統。 |
To install this application you need either a Windows developer license or a sideloading-enabled system. |
| 0x00003D00 | 應用程式目前正在更新，因此無法啟動。 |
The application cannot be started because it is currently updating. |
| 0x00003D01 | 套件部署操作已由原則封鎖。請連絡您的系統管理員。 |
The package deployment operation is blocked by policy. Please contact your system administrator. |
| 0x00003D02 | 無法安裝套件，因為它修改的資源目前已在使用中。 |
The package could not be installed because resources it modifies are currently in use. |
| 0x00003D03 | 無法修復套件，因為進行修復所需的資料已損毀。 |
The package could not be recovered because necessary data for recovery have been corrupted. |
| 0x00003D04 | 簽章無效。如果要在開發人員模式註冊，AppxSignature.p7x 與 AppxBlockMap.xml 必須有效或不應存在。 |
The signature is invalid. To register in developer mode, AppxSignature.p7x and AppxBlockMap.xml must be valid or should not be present. |
| 0x00003D05 | 刪除套件先前的現有應用程式資料時發生錯誤。 |
An error occurred while deleting the package's previously existing application data. |
| 0x00003D06 | 無法安裝此套件，因為已安裝此套件的更新版本。 |
The package could not be installed because a higher version of this package is already installed. |
| 0x00003D07 | 在系統二進位檔案中偵測到錯誤。請嘗試重新整理電腦以修正該問題。 |
An error in a system binary was detected. Try refreshing the PC to fix the problem. |
| 0x00003D08 | 在系統上偵測到已損毀的 CLR NGEN 二進位檔案。 |
A corrupted CLR NGEN binary was detected on the system. |
| 0x00003D09 | 無法繼續此操作，因為執行修復所需的資料已損毀。 |
The operation could not be resumed because necessary data for recovery have been corrupted. |
| 0x00003D0A | 無法安裝套件，因為 Windows 防火牆服務未執行。請啟用 Windows 防火牆服務，然後再試一次。 |
The package could not be installed because the Windows Firewall service is not running. Enable the Windows Firewall service and try again. |
| 0x00003D0B | 套件移動失敗。 |
Package move failed. |
| 0x00003D0C | 部署操作失敗，因為磁碟區不是空的。 |
The deployment operation failed because the volume is not empty. |
| 0x00003D0D | 部署操作失敗，因為磁碟區已離線。 |
The deployment operation failed because the volume is offline. |
| 0x00003D0E | 部署操作失敗，因為指定的磁碟區已損毀。 |
The deployment operation failed because the specified volume is corrupt. |
| 0x00003D0F | 部署操作失敗，因為必須先註冊指定的應用程式。 |
The deployment operation failed because the specified application needs to be registered first. |
| 0x00003D10 | 部署作業失敗，因為套件以錯誤的處理器架構為目標。 |
The deployment operation failed because the package targets the wrong processor architecture. |
| 0x00003D11 | 您已達到此裝置上允許的開發人員側載套件數目上限。請解除安裝側載的套件，然後再試一次。 |
You have reached the maximum number of developer sideloaded packages allowed on this device. Please uninstall a sideloaded package and try again. |
| 0x00003D12 | 必須有主要 App 套件，才能安裝此選用套件。請先安裝主要套件，然後再試一次。 |
A main app package is required to install this optional package. Install the main package first and try again. |
| 0x00003D13 | 此檔案系統不支援此 App 套件類型 |
This app package type is not supported on this filesystem |
| 0x00003D14 | 完成應用程式串流處理之前，無法執行套件移動作業 |
Package move operation is blocked until the application has finished streaming |
| 0x00003D15 | 主要或另一個選用應用程式套件具有與此選用套件相同的應用程式識別碼。請變更選用套件的應用程式識別碼以避免衝突。 |
A main or another optional app package has the same application ID as this optional package. Change the application ID for the optional package to avoid conflicts. |
| 0x00003D16 | 已暫停此暫存工作階段，以讓其他暫存工作階段排列優先順序。 |
This staging session has been held to allow another staging operation to be prioritized. |
| 0x00003D17 | 由於更新的集合無效，因此相關的集合無法更新。該相關集合內的所有封裝都必須在同一時間更新。 |
A related set cannot be updated because the updated set is invalid. All packages in the related set must be updated at the same time. |
| 0x00003D18 | 內含 FullTrust 進入點的選用套件要求主要套件具備 runFullTrust 功能。 |
An optional package with a FullTrust entry point requires the main package to have the runFullTrust capability. |
| 0x00003D54 | 處理程序沒有套件識別資料。 |
The process has no package identity. |
| 0x00003D55 | 套件執行階段資訊損毀。 |
The package runtime information is corrupted. |
| 0x00003D56 | 套件識別資料損毀。 |
The package identity is corrupted. |
| 0x00003D57 | 處理程序沒有應用程式識別資料。 |
The process has no application identity. |
| 0x00003D58 | 無法讀取一或多個「AppModel 執行階段」群組原則值。請連絡您的系統管理員，並提供您的「AppModel 執行階段」事件記錄檔內容。 |
One or more AppModel Runtime group policy values could not be read. Please contact your system administrator with the contents of your AppModel Runtime event log. |
| 0x00003D59 | 一或多個「AppModel 執行階段」群組原則值無效。請連絡您的系統管理員，並提供您的「AppModel 執行階段」事件記錄檔內容。 |
One or more AppModel Runtime group policy values are invalid. Please contact your system administrator with the contents of your AppModel Runtime event log. |
| 0x00003D5A | 套件目前無法使用。 |
The package is currently not available. |
| 0x00003DB8 | 載入狀態存放區失敗。 |
Loading the state store failed. |
| 0x00003DB9 | 抓取應用程式的狀態版本失敗。 |
Retrieving the state version for the application failed. |
| 0x00003DBA | 設定應用程式的狀態版本失敗。 |
Setting the state version for the application failed. |
| 0x00003DBB | 重設應用程式的結構化狀態失敗。 |
Resetting the structured state of the application failed. |
| 0x00003DBC | 狀態管理員無法開啟容器。 |
State Manager failed to open the container. |
| 0x00003DBD | 狀態管理員無法建立容器。 |
State Manager failed to create the container. |
| 0x00003DBE | 狀態管理員無法刪除容器。 |
State Manager failed to delete the container. |
| 0x00003DBF | 狀態管理員無法讀取設定。 |
State Manager failed to read the setting. |
| 0x00003DC0 | 狀態管理員無法寫入設定。 |
State Manager failed to write the setting. |
| 0x00003DC1 | 狀態管理員無法刪除設定。 |
State Manager failed to delete the setting. |
| 0x00003DC2 | 狀態管理員無法查詢設定。 |
State Manager failed to query the setting. |
| 0x00003DC3 | 狀態管理員無法讀取複合設定。 |
State Manager failed to read the composite setting. |
| 0x00003DC4 | 狀態管理員無法寫入複合設定。 |
State Manager failed to write the composite setting. |
| 0x00003DC5 | 狀態管理員無法列舉容器。 |
State Manager failed to enumerate the containers. |
| 0x00003DC6 | 狀態管理員無法列舉設定。 |
State Manager failed to enumerate the settings. |
| 0x00003DC7 | 狀態管理員複合設定值的大小超過限制。 |
The size of the state manager composite setting value has exceeded the limit. |
| 0x00003DC8 | 狀態管理員設定值的大小超過限制。 |
The size of the state manager setting value has exceeded the limit. |
| 0x00003DC9 | 狀態管理員設定名稱的長度超過限制。 |
The length of the state manager setting name has exceeded the limit. |
| 0x00003DCA | 狀態管理員容器名稱的長度超過限制。 |
The length of the state manager container name has exceeded the limit. |
| 0x00003DE1 | 無法在呼叫者應用程式的應用程式類型上下文中使用此 API。 |
This API cannot be used in the context of the caller's application type. |
| 0x00003DF5 | 此電腦沒有該應用程式或產品的有效授權。 |
This PC does not have a valid license for the application or product. |
| 0x00003DF6 | 已驗證的使用者沒有該應用程式或產品的有效授權。 |
The authenticated user does not have a valid license for the application or product. |
| 0x00003DF7 | 與此授權關聯的商務交易仍尚待驗證。 |
The commerce transaction associated with this license is still pending verification. |
| 0x00003DF8 | 此使用者的授權已被撤銷。 |
The license has been revoked for this user. |
| 0x00030200 | 檔案被轉換成複合檔案格式。 |
The underlying file was converted to compound file format. |
| 0x00030201 | 除非有更多可用的資料，否則存放操作會受阻。 |
The storage operation should block until more data is available. |
| 0x00030202 | 須立即重試存放操作。 |
The storage operation should retry immediately. |
| 0x00030203 | 通知事件接收器並不會影響存放操作。 |
The notified event sink will not influence the storage operation. |
| 0x00030204 | 數個開啟導致無法合併。(已認可成功)。 |
Multiple opens prevent consolidated. (commit succeeded). |
| 0x00030205 | 存放檔案合併失敗。(已認可成功)。 |
Consolidation of the storage file failed. (commit succeeded). |
| 0x00030206 | 合併存放檔案並未適當執行。( 已認可成功 )。 |
Consolidation of the storage file is inappropriate. (commit succeeded). |
| 0x00030207 | 裝置需要重新啟動電源。(認可成功)。 |
The device needs to be power cycled. (commit succeeded). |
| 0x00040000 | 使用登錄資料庫來提供所要求的資訊 |
Use the registry database to provide the requested information |
| 0x00040001 | 成功，但是靜態 |
Success, but static |
| 0x00040002 | Macintosh 剪貼簿格式 |
Macintosh clipboard format |
| 0x00040100 | 產生成功的拖放 |
Successful drop took place |
| 0x00040101 | 取消拖放操作 |
Drag-drop operation canceled |
| 0x00040102 | 使用預設游標 |
Use the default cursor |
| 0x00040130 | 資料有相同的 FORMATETC |
Data has same FORMATETC |
| 0x00040140 | 檢視已凍結 |
View is already frozen |
| 0x00040170 | 不支援 FORMATETC |
FORMATETC not supported |
| 0x00040171 | 相同的快取 |
Same cache |
| 0x00040172 | 有些快取未更新 |
Some cache(s) not updated |
| 0x00040180 | OLE 物件的 verb 無效 |
Invalid verb for OLE object |
| 0x00040181 | Verb 編號有效，但是 verb 目前無法完成 |
Verb number is valid but verb cannot be done now |
| 0x00040182 | 傳送不正確的視窗控制代碼 |
Invalid window handle passed |
| 0x000401A0 | 訊息太長; 某些部分在顯示前必須截斷 |
Message is too long; some of it had to be truncated before displaying |
| 0x000401C0 | 無法將 OLESTREAM 轉換成 IStorage |
Unable to convert OLESTREAM to IStorage |
| 0x000401E2 | Moniker 縮減成自己本身 |
Moniker reduced to itself |
| 0x000401E4 | 共同首碼是這個 moniker |
Common prefix is this moniker |
| 0x000401E5 | 共同首碼是輸入 moniker |
Common prefix is input moniker |
| 0x000401E6 | 共同首碼是這兩個 moniker |
Common prefix is both monikers |
| 0x000401E7 | Moniker 已登錄到執行中的物件表格 |
Moniker is already registered in running object table |
| 0x00040200 | 事件只能啟動某些的訂閱者，並非全部 |
An event was able to invoke some but not all of the subscribers |
| 0x00040202 | 已經傳遞一個事件，但沒有任何的訂閱者 |
An event was delivered but there were no subscribers |
| 0x00040252 | TabletPC 筆跡錯誤碼。字串已被截斷 |
TabletPC inking error code. String was truncated |
| 0x00040253 | TabletPC 筆跡錯誤碼。辨識或訓練已被打斷 |
TabletPC inking error code. Recognition or training was interrupted |
| 0x00040254 | TabletPC 筆跡錯誤碼。沒有辨識器的個人化更新，因為找不到任何訓練資料 |
TabletPC inking error code. No personalization update to the recognizer because no training data found |
| 0x00041300 | 工作已經準備好在它下一個排定的時間執行。 |
The task is ready to run at its next scheduled time. |
| 0x00041301 | 工作正在執行中。 |
The task is currently running. |
| 0x00041302 | 工作將不會在排定的時間執行，因為它已經被停用了。 |
The task will not run at the scheduled times because it has been disabled. |
| 0x00041303 | 工作尚未執行。 |
The task has not yet run. |
| 0x00041304 | 這個工作沒有排程需要執行。 |
There are no more runs scheduled for this task. |
| 0x00041305 | 在排程上執行這個工作所需的一個或以上的內容尚未設定。 |
One or more of the properties that are needed to run this task on a schedule have not been set. |
| 0x00041306 | 上一回執行的工作已經被使用者終止了。 |
The last run of the task was terminated by the user. |
| 0x00041307 | 可能是工作沒有觸發程序或現有的觸發程序已經停用或沒有設定。 |
Either the task has no triggers or the existing triggers are disabled or not set. |
| 0x00041308 | 事件觸發程序沒有設定執行次數。 |
Event triggers don't have set run times. |
| 0x0004131B | 工作已登錄，但並非所有指定的觸發程序都將啟動工作，請檢查工作排程器事件記錄檔了解詳細資訊。 |
The task is registered, but not all specified triggers will start the task, check task scheduler event log for detailed information. |
| 0x0004131C | 工作已登錄，但多數無法啟動。必須啟用該工作主體的批次登入權限。 |
The task is registered, but may fail to start. Batch logon privilege needs to be enabled for the task principal. |
| 0x00041325 | 工作排程器服務已要求執行該工作。 |
The Task Scheduler service has asked the task to run. |
| 0x0004D000 | 指定了一個非同步操作。操作已經開始，但是還不知道結果。 |
An asynchronous operation was specified. The operation has begun, but its outcome is not known yet. |
| 0x0004D001 | XACT_S_DEFECT |
XACT_S_DEFECT |
| 0x0004D002 | 方法呼叫成功，因為交易是唯讀。 |
The method call succeeded because the transaction was read-only. |
| 0x0004D003 | 已經順利中止交易。但是，這是一個經過協調的交易，有部分徵募的資源會徹底中止，因為它們不支援持續中止的語義學 |
The transaction was successfully aborted. However, this is a coordinated transaction, and some number of enlisted resources were aborted outright because they could not support abort-retaining semantics |
| 0x0004D004 | 呼叫期間沒有任何變更，但是接收器需要再一次檢查，看看其他的接收器是否有進一步變更。 |
No changes were made during this call, but the sink wants another chance to look if any other sinks make further changes. |
| 0x0004D005 | 接收器已裝載內容，且準備進行交易。這次呼叫期間，對一個以上的資源作了變更。 |
The sink is content and wishes the transaction to proceed. Changes were made to one or more resources during this call. |
| 0x0004D006 | 接收器已準備好進行交易，但如果其他的事件接收器在緊接這次交易後又作了其他變更，那麼這個接收器需要再一次檢查 |
The sink is for the moment and wishes the transaction to proceed, but if other changes are made following this return by other event sinks then this sink wants another chance to look |
| 0x0004D007 | 已順利中止交易。然而，這個中止是非持續性的。 |
The transaction was successfully aborted. However, the abort was non-retaining. |
| 0x0004D008 | 中止操作已在進行中。 |
An abort operation was already in progress. |
| 0x0004D009 | 資源管理員已經執行了單一階段交易認可。 |
The resource manager has performed a single-phase commit of the transaction. |
| 0x0004D00A | 本機交易未中止。 |
The local transaction has not aborted. |
| 0x0004D010 | 資源管理員已經要求成為這次交易的協調者 (上一次資源管理員)。 |
The resource manager has requested to be the coordinator (last resource manager) for the transaction. |
| 0x00080012 | 並不是所有的要求介面都可使用 |
Not all the requested interfaces were available |
| 0x00080013 | 無法在快取中找到指定的電腦名稱。 |
The specified machine name was not found in the cache. |
| 0x00090312 | 這個功能已成功完成，但必須再被呼叫一次來完成內容 |
The function completed successfully, but must be called again to complete the context |
| 0x00090313 | 這個功能已成功完成，但必須呼叫 CompleteToken |
The function completed successfully, but CompleteToken must be called |
| 0x00090314 | 此功能已成功完成，但必須再呼叫 CompleteToken，此功能才能完成內容 |
The function completed successfully, but both CompleteToken and this function must be called to complete the context |
| 0x00090315 | 登入已經完成，但沒有可供使用的網路授權。登入時用的是本機已知資訊 |
The logon was completed, but no network authority was available. The logon was made using locally known information |
| 0x00090320 | 提供的認證不完整，因此無法確認。可以由內容傳回其他資訊。 |
The credentials supplied were not complete, and could not be verified. Additional information can be returned from the context. |
| 0x00090321 | 必須與對等交涉此內容資料。 |
The context data must be renegotiated with the peer. |
| 0x00090323 | 沒有與此內容相關聯的 LSA 模式內容。 |
There is no LSA mode context associated with this context. |
| 0x0009035C | 必須執行簽章作業，使用者才能執行驗證。 |
A signature operation must be performed before the user can authenticate. |
| 0x00090360 | 接收者拒絕重新交涉要求。 |
The recipient rejected the renegotiation request. |
| 0x00090364 | 傳回的緩衝區只是訊息的一個片段。還有更多片段需要傳回。 |
The returned buffer is only a fragment of the message. More fragments need to be returned. |
| 0x00090366 | 已順利完成該函式，但但必須重新呼叫該函式以完成內容。可以使用提早啟動。 |
The function completed successfully, but must be called again to complete the context. Early start can be used. |
| 0x00090368 | 已呼叫非同步 SSPI 常式，工作正等待完成。 |
An asynchronous SSPI routine has been called and the work is pending completion. |
| 0x00091012 | 受保護的資料需要重新受保護。 |
The protected data needs to be re-protected. |
| 0x001B0000 | 已連結偵錯工具。 |
Debugger was attached. |
| 0x001B0001 | 已上傳報告。 |
Report was uploaded. |
| 0x001B0002 | 已將報告排入佇列。 |
Report was queued. |
| 0x001B0003 | 已停用報告功能。 |
Reporting was disabled. |
| 0x001B0004 | 已暫時停用報告功能。 |
Reporting was temporarily suspended. |
| 0x001B0005 | 未將報告排入佇列，因為正在停用佇列功能。 |
Report was not queued to queueing being disabled. |
| 0x001B0006 | 已上傳報告，但並未將報告封存，因為正在停用封存功能。 |
Report was uploaded, but not archived due to archiving being disabled. |
| 0x001B0007 | 已順利在非同步操作中 spin off 報告功能。 |
Reporting was successfully spun off as an asynchronous operation. |
| 0x001B0008 | 已處理判斷提示。 |
The assertion was handled. |
| 0x001B0009 | 已處理判斷提示，且已將它新增到永久忽略清單。 |
The assertion was handled and added to a permanent ignore list. |
| 0x001B000A | 判斷提示已繼續為未處理。 |
The assertion was resumed as unhandled. |
| 0x001B000B | 已針對報告進行節流處理。 |
Report was throttled. |
| 0x001B000C | 已使用 cab 檔上傳報告。 |
Report was uploaded with cab. |
| 0x001F0001 | 篩選器已完成 IO。 |
The IO was completed by a filter. |
| 0x00261001 | 無法取得監視器描述元。 |
Monitor descriptor could not be obtained. |
| 0x00261002 | 此版本不支援所取得之監視器描述元的格式。 |
Format of the obtained monitor descriptor is not supported by this release. |
| 0x00262307 | 指定的 VidPN 來源/目標上未釘選任何模式。 |
No mode is pinned on the specified VidPN source/target. |
| 0x0026231E | 指定的模式集並未替其中一種模式指定喜好設定。 |
Specified mode set does not specify preference for one of its modes. |
| 0x0026234B | 指定的資料集 (例如模式集、頻率範圍集、描述元集和拓撲等) 空白。 |
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty. |
| 0x0026234C | 指定的資料集 (例如模式集、頻率範圍集、描述元集和拓撲等) 不再包含任何元素。 |
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements. |
| 0x00262351 | 指定的內容格式變更在指定的 VidPN 呈現路徑中並未釘選。 |
Specified content transformation is not pinned on the specified VidPN present path. |
| 0x00263005 | {已傳回 GDI 重新導向表面}已傳回最上層視窗的 GDI 重新導向表面。 |
{GDI redirection surface was returned}GDI redirection surface of the top level window was returned. |
| 0x00263008 | {GDI 重新導向表面位於不同的介面卡上或位於系統記憶體中。請透過 GDI 執行 blt}GDI 重新導向表面位於不同的介面卡上或位於系統記憶體中。請透過 GDI 執行 blt。 |
{GDI redirection surface is either on a different adapter or in system memory. Perform blt via GDI}GDI redirection surface is either on a different adapter or in system memory. Perform blt via GDI. |
| 0x0027000D | 憑證已存在憑證存放區中。 |
A certificate is already present in the cert store. |
| 0x00270258 | 已啟動「市集」而非指定的應用程式，因為應用程式的套件是無效狀態。 |
The Store was launched instead of the specified app because the app's package was in an invalid state. |
| 0x00270259 | 無法啟動此應用程式，但已使用對話方塊處理該錯誤。 |
This app failed to launch, but the error was handled with a dialog. |
| 0x00300100 | 將忽略屬性值。 |
Property value will be ignored. |
| 0x00340001 | 稍後將由 NDIS 狀態表示完成此要求。 |
The request will be completed later by NDIS status indication. |
| 0x00350059 | 裝置具有擱置中的頁面要求，且該要求已被捨棄。 |
The device had pending page requests which were discarded. |
| 0x003C0105 | 無法在此系統上執行疑難排解套件。 |
The troubleshooting pack cannot be executed on this system. |
| 0x003D0000 | 正在以非同步方式完成函式呼叫。 |
The function call is completing asynchronously. |
| 0x003D0001 | 通道已經沒有可用的訊息。 |
There are no more messages available on the channel. |
| 0x00630001 | 已建立圖表資料。 |
The graph data was created. |
| 0x00630002 | 沒有其他事件資料。 |
There is not more event data. |
| 0x00630005 | 無連線能力。 |
No connectivity. |
| 0x00630006 | 已經是成員。 |
Already a member. |
| 0x00632000 | 圖表已連線。 |
The graph is already connect. |
| 0x00636000 | 訂閱已存在。 |
The subscription already exists. |
| 0x00E70001 | 驅動程式已刪除儲存集區。應更新物件快取。 |
The storage pool was deleted by the driver. The object cache should be updated. |
| 0x087A0001 | 使用者無法看見「展示」作業。 |
The Present operation was invisible to the user. |
| 0x087A0002 | 使用者無法看見部分「展示」作業。 |
The Present operation was partially invisible to the user. |
| 0x087A0004 | 驅動程式正在要求 DXGI 執行階段不要使用共用資源來與「桌面視窗管理員」進行通訊。 |
The driver is requesting that the DXGI runtime not use shared resources to communicate with the Desktop Window Manager. |
| 0x087A0005 | 無法看見「展示」作業，因為 Windows 工作階段已切換至另一個桌面 (例如，Ctrl+Alt+Del)。 |
The Present operation was not visible because the Windows session has switched to another desktop (for example, ctrl-alt-del). |
| 0x087A0006 | 無法看見「展示」作業，因為目標監視器已使用於某些其他用途。 |
The Present operation was not visible because the target monitor was being used for some other purpose. |
| 0x087A0007 | 無法看見「展示」作業，因為顯示模式已變更。DXGI 將重新嘗試展示。 |
The Present operation was not visible because the display mode changed. DXGI will have re-attempted the presentation. |
| 0x087A0008 | 無法看見「展示」作業，因為另一個 Direct3D 裝置已在當時嘗試進入全螢幕模式。 |
The Present operation was not visible because another Direct3D device was attempting to take fullscreen mode at the time. |
| 0x087A0009 | swapchain 已變成非閉塞。 |
The swapchain has become unoccluded. |
| 0x087A000A | 介面卡沒有必要資源的存取權，因此無法完成「桌面複製」(Desktop Duplication) Present() 呼叫，必須再次進行 Present() 呼叫 |
The adapter did not have access to the required resources to complete the Desktop Duplication Present() call, the Present() call needs to be made again |
| 0x087A002F | 呈現成功，但呼叫者應該在下次 V-sync 時重新呈現，即使內容沒有變更也一樣。 |
The present succeeded but the caller should present again on the next V-sync, even if there are no changes to the content. |
| 0x4026200A | 指定的緩衝區太小，不足以包含整個要求的資料集。某些資料擴展到緩衝區大小之外。呼叫者必須提供緩衝區大小，如部分填入的緩衝區內容中所指定 (特定介面)。 |
Specified buffer is not big enough to contain entire requested dataset. Partial data populated up to the size of the buffer. Caller needs to provide buffer of size as specified in the partially populated buffer's content (interface specific). |
| 0x40262201 | 略過 DMA 緩衝區所參照的配置準備。 |
Skip preparation of allocations referenced by the DMA buffer. |
| 0x4026242F | 並未確實偵測子裝置的存在。 |
Child device presence was not reliably detected. |
| 0x40262437 | 啟動前置連結配接器已暫時順延。 |
Starting the leadlink adapter has been deferred temporarily. |
| 0x40262439 | 已經為子系在相同的輪詢層級輪詢顯示器介面卡太多次。 |
The display adapter is being polled for children too frequently at the same polling level. |
| 0x4026243A | 介面卡的啟動已暫時順延。 |
Starting the adapter has been deferred temporarily. |
| 0x4026243C | 我們可以依賴驅動程式傳回的子裝置呈現。 |
We can depend on the child device presence returned by the driver. |
| 0x80000001 | 未執行 |
Not implemented |
| 0x80000002 | 記憶體用盡 |
Ran out of memory |
| 0x80000003 | 有一些引數無效 |
One or more arguments are invalid |
| 0x80000004 | 不支援此種介面 |
No such interface supported |
| 0x80000005 | 無效的指標 |
Invalid pointer |
| 0x80000006 | 控制代碼不正確 |
Invalid handle |
| 0x80000007 | 操作已中止 |
Operation aborted |
| 0x80000008 | 無法指出的錯誤 |
Unspecified error |
| 0x80000009 | 發生一般性存取被拒的錯誤 |
General access denied error |
| 0x8000000A | 完成此操作所需的資料仍然無法使用。 |
The data necessary to complete this operation is not yet available. |
| 0x8000000B | 作業嘗試存取有效範圍以外的資料 |
The operation attempted to access data outside the valid range |
| 0x8000000C | 某個同時或交錯式的作業變更了物件狀態，導致此作業無效。 |
A concurrent or interleaved operation changed the state of the object, invalidating this operation. |
| 0x8000000D | 要求的狀態變更無效。 |
An illegal state change was requested. |
| 0x8000000E | 在未預期的時間呼叫了方法。 |
A method was called at an unexpected time. |
| 0x8000000F | 在中繼資料檔案中找不到 Typename 或 Namespace。 |
Typename or Namespace was not found in metadata file. |
| 0x80000010 | 名稱為現有的命名空間，而非 typename。 |
Name is an existing namespace rather than a typename. |
| 0x80000011 | Typename 含有無效格式。 |
Typename has an invalid format. |
| 0x80000012 | 中繼資料檔案無效或損毀。 |
Metadata file is invalid or corrupted. |
| 0x80000013 | 該物件已關閉。 |
The object has been closed. |
| 0x80000014 | 在寫入作業期間，只有一個執行緒可存取該物件。 |
Only one thread may access the object during a write operation. |
| 0x80000015 | 變更通知期間禁止作業。 |
Operation is prohibited during change notification. |
| 0x80000016 | 找不到與此錯誤碼關聯的文字。 |
The text associated with this error code could not be found. |
| 0x80000017 | 字串結尾不是 Null。 |
String not null terminated. |
| 0x80000018 | 在不允許的狀況下指派了委派。 |
A delegate was assigned when not allowed. |
| 0x80000019 | 未正確啟動非同步作業。 |
An async operation was not properly started. |
| 0x8000001A | 應用程式正在結束，無法處理此要求 |
The application is exiting and cannot service this request |
| 0x8000001B | 應用程式檢視正在結束，無法處理此要求 |
The application view is exiting and cannot service this request |
| 0x8000001C | 物件必須支援 IAgileObject 介面 |
The object must support the IAgileObject interface |
| 0x8000001D | 不支援從 MTA 啟用單一執行緒類別 |
Activating a single-threaded class from MTA is not supported |
| 0x8000001E | 已認可此物件。 |
The object has been committed. |
| 0x8000001F | 對 ASTA 的 COM 呼叫被封鎖，因為呼叫鏈結產生自或通過另一個 ASTA。此呼叫模式容易導致鎖死，因此 Apartment 呼叫控制不允許此模式。 |
A COM call to an ASTA was blocked because the call chain originated in or passed through another ASTA. This call pattern is deadlock-prone and disallowed by apartment call control. |
| 0x80004006 | 執行緒本機存放裝置失敗 |
Thread local storage failure |
| 0x80004007 | 無法取得共用記憶體配置器 |
Get shared memory allocator failure |
| 0x80004008 | 無法取得記憶體配置器 |
Get memory allocator failure |
| 0x80004009 | 無法啟動類別快取 |
Unable to initialize class cache |
| 0x8000400A | 無法初始化 RPC 服務 |
Unable to initialize RPC services |
| 0x8000400B | 無法設定執行緒本機存放通道控制 |
Cannot set thread local storage channel control |
| 0x8000400C | 無法配置執行緒本機存放通道控制 |
Could not allocate thread local storage channel control |
| 0x8000400D | 無法接受使用者提供的記憶體配置器 |
The user supplied memory allocator is unacceptable |
| 0x8000400E | OLE 服務 mutex 已存在 |
The OLE service mutex already exists |
| 0x8000400F | OLE 服務檔案對應已存在 |
The OLE service file mapping already exists |
| 0x80004010 | 無法對應 OLE 服務所需的檔案檢視 |
Unable to map view of file for OLE service |
| 0x80004011 | 啟動 OLE 服務的嘗試失敗 |
Failure attempting to launch OLE service |
| 0x80004012 | 當執行單一執行緒時嘗試再次呼叫 CoInitialize |
There was an attempt to call CoInitialize a second time while single threaded |
| 0x80004013 | 有一個必要的遠端啟用不被允許 |
A Remote activation was necessary but was not allowed |
| 0x80004014 | 有一個必要的遠端啟用無法進行，因為提供的伺服器名稱不正確 |
A Remote activation was necessary but the server name provided was invalid |
| 0x80004015 | 這個類別設定的執行方式是安全性識別碼與呼叫者不相同 |
The class is configured to run as a security id different from the caller |
| 0x80004016 | 需要 DDE 視窗的 Ole1 服務已停用 |
Use of Ole1 services requiring DDE windows is disabled |
| 0x80004017 | RunAs 規格必須是 \\ 或是只用 |
A RunAs specification must be \\ or simply |
| 0x80004018 | 伺服器處理程序不能被啟動，路徑名稱可能不正確。 |
The server process could not be started. The pathname may be incorrect. |
| 0x80004019 | 伺服器處理程序可能無法用設定識別來啟動。路徑名稱不正確或無法使用。 |
The server process could not be started as the configured identity. The pathname may be incorrect or unavailable. |
| 0x8000401A | 設定的身分不正確，因此無法啟動伺服器處理。請檢查使用者名稱及密碼。 |
The server process could not be started because the configured identity is incorrect. Check the username and password. |
| 0x8000401B | 不允許這個用戶端啟動這台伺服器。 |
The client is not allowed to launch this server. |
| 0x8000401C | 無法啟動這台伺服器提供的服務。 |
The service providing this server could not be started. |
| 0x8000401D | 這台電腦無法與所提供的伺服器的電腦通訊。 |
This computer was unable to communicate with the computer providing the server. |
| 0x8000401E | 伺服器啟動後沒有回應。 |
The server did not respond after being launched. |
| 0x8000401F | 這台伺服器的登錄資訊不一致或不完整。 |
The registration information for this server is inconsistent or incomplete. |
| 0x80004020 | 介面的登錄資訊不一致或不完整。 |
The registration information for this interface is inconsistent or incomplete. |
| 0x80004021 | 不支援所嘗試的操作。 |
The operation attempted is not supported. |
| 0x80004022 | 必須載入 dll。 |
A dll must be loaded. |
| 0x80004023 | 遇到 Microsoft 軟體安裝程式的錯誤。 |
A Microsoft Software Installer error was encountered. |
| 0x80004024 | 指定的啟用無法依用戶端內容的指定方式發生。 |
The specified activation could not occur in the client context as specified. |
| 0x80004025 | 伺服器上的啟用已暫停。 |
Activations on the server are paused. |
| 0x80004026 | 伺服器上的啟用未暫停。 |
Activations on the server are not paused. |
| 0x80004027 | 包含該元件的元件或應用程式已經停用。 |
The component or application containing the component has been disabled. |
| 0x80004028 | 無法使用通用語言執行階段 |
The common language runtime is not available |
| 0x80004029 | 執行緒集區拒絕了提交的非同步工作。 |
The thread-pool rejected the submitted asynchronous work. |
| 0x8000402A | 伺服器已啟動，但未及時完成初始化。 |
The server started, but did not finish initializing in a timely fashion. |
| 0x8000402B | 無法完成呼叫，因為在 IObjectControl.Activate 內沒有 COM+ 資訊安全內容。 |
Unable to complete the call since there is no COM+ security context inside IObjectControl.Activate. |
| 0x80004030 | 所提供的追蹤器設定不正確 |
The provided tracker configuration is invalid |
| 0x80004031 | 所提供的執行緒集區設定不正確 |
The provided thread pool configuration is invalid |
| 0x80004032 | 所提供的並列設定不正確 |
The provided side-by-side configuration is invalid |
| 0x80004033 | 在安全性交涉期間取得的伺服器主體名稱 (SPN) 格式錯誤。 |
The server principal name (SPN) obtained during security negotiation is malformed. |
| 0x80004034 | 呼叫者無法在 Apartment 關閉之前撤銷每一 Apartment 登錄。 |
The caller failed to revoke a per-apartment registration before apartment shutdown. |
| 0x80004035 | 物件已由虛設常式管理員取消，但仍有外部用戶端。 |
The object has been rundown by the stub manager while there are external clients. |
| 0x8000FFFF | 災難性的失敗 |
Catastrophic failure |
| 0x80010001 | 接收者已拒絕這個呼叫。 |
Call was rejected by callee. |
| 0x80010002 | 呼叫被訊息篩選器取消。 |
Call was canceled by the message filter. |
| 0x80010003 | 呼叫者正在發送一個工作間的 SendMessage 呼叫，因而無法透過 PostMessage 呼叫。 |
The caller is dispatching an intertask SendMessage call and cannot call out via PostMessage. |
| 0x80010004 | 呼叫者正在發送一個非同步呼叫，所以無法代表這個呼叫發出連出的呼叫。 |
The caller is dispatching an asynchronous call and cannot make an outgoing call on behalf of this call. |
| 0x80010005 | 在訊息篩選器裡時不可對外呼叫。 |
It is illegal to call out while inside message filter. |
| 0x80010006 | 這個連線已中斷，或處於假狀態中，無法再使用。其他的連線仍然有效。 |
The connection terminated or is in a bogus state and cannot be used any more. Other connections are still valid. |
| 0x80010007 | 找不到被呼叫者 (伺服器 [不是伺服器應用程式])。所有連線都無效。呼叫可能已執行。 |
The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed. |
| 0x80010008 | 被呼叫者 (伺服器) 在處理呼叫者 (用戶端) 的呼叫時，發現呼叫者不見了。 |
The caller (client) disappeared while the callee (server) was processing a call. |
| 0x80010009 | 附有排列參數資料的資料封包不正確。 |
The data packet with the marshalled parameter data is incorrect. |
| 0x8001000A | 呼叫並未適當地傳送; 訊息佇列已滿，且無法在傳送後清除。 |
The call was not transmitted properly; the message queue was full and was not emptied after yielding. |
| 0x8001000B | 用戶端 (呼叫者) 無法整理參數資料 - 記憶體太低等。 |
The client (caller) cannot marshall the parameter data - low memory, etc. |
| 0x8001000C | 用戶端 (呼叫者) 無法重新整理參數資料 - 記憶體太低等。 |
The client (caller) cannot unmarshall the return data - low memory, etc. |
| 0x8001000D | 伺服器 (被呼叫者) 無法整理傳回的資料 - 記憶體太低等。 |
The server (callee) cannot marshall the return data - low memory, etc. |
| 0x8001000E | 伺服器 (被呼叫者) 無法重新整理參數資料 - 記憶體太低等。 |
The server (callee) cannot unmarshall the parameter data - low memory, etc. |
| 0x8001000F | 接收的資料無效; 可能是伺服器或用戶端資料。 |
Received data is invalid; could be server or client data. |
| 0x80010010 | 某個特定參數無效，無法重新整理。 |
A particular parameter is invalid and cannot be (un)marshalled. |
| 0x80010011 | DDE 對話中，同一通道上沒有第二個傳出呼叫。 |
There is no second outgoing call on same channel in DDE conversation. |
| 0x80010012 | 被呼叫者 (伺服器 [不是伺服器應用程式]) 無法取得或已消失; 所有連接均無效。呼叫未執行。 |
The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call did not execute. |
| 0x80010101 | 無法配置某些需要的資源 (記憶體、事件...) |
Could not allocate some required resource (memory, events, ...) |
| 0x80010102 | 在單一執行緒模式嘗試呼叫數個執行緒。 |
Attempted to make calls on more than one thread in single threaded mode. |
| 0x80010103 | 要求的介面並未登錄在伺服器物件上。 |
The requested interface is not registered on the server object. |
| 0x80010104 | RPC 無法呼叫伺服器，或是無法傳回呼叫伺服器的結果。 |
RPC could not call the server or could not return the results of calling the server. |
| 0x80010105 | 伺服器丟出一個例外。 |
The server threw an exception. |
| 0x80010106 | 執行緒模式設定後就不能再變更它。 |
Cannot change thread mode after it is set. |
| 0x80010107 | 伺服器上沒有這項呼叫方法。 |
The method called does not exist on the server. |
| 0x80010108 | 用戶端中斷了已啟動物件的連線。 |
The object invoked has disconnected from its clients. |
| 0x80010109 | 啟動的物件決定不要立即處理這個呼叫。請稍後重試。 |
The object invoked chose not to process the call now. Try again later. |
| 0x8001010A | 訊息篩選器顯示應用程式正在忙碌中。 |
The message filter indicated that the application is busy. |
| 0x8001010B | 訊息篩選器拒絕這個呼叫。 |
The message filter rejected the call. |
| 0x8001010C | 呼叫控制介面被無效的資料呼叫。 |
A call control interfaces was called with invalid data. |
| 0x8001010D | 因為應用程式正在發送同步輸入呼叫，所以無法建立傳出呼叫。 |
An outgoing call cannot be made since the application is dispatching an input-synchronous call. |
| 0x8001010E | 應用程式所呼叫了整理給不同執行緒的介面。 |
The application called an interface that was marshalled for a different thread. |
| 0x8001010F | 目前的執行緒並未呼叫 CoInitialize。 |
CoInitialize has not been called on the current thread. |
| 0x80010110 | 用戶端與伺服器電腦上的 OLE 版本不相符。 |
The version of OLE on the client and server machines does not match. |
| 0x80010111 | OLE 收到含有無效標頭的封包。 |
OLE received a packet with an invalid header. |
| 0x80010112 | OLE 收到含有無效副檔名的封包。 |
OLE received a packet with an invalid extension. |
| 0x80010113 | 要求的物件或介面不存在。 |
The requested object or interface does not exist. |
| 0x80010114 | 要求的物件不存在。 |
The requested object does not exist. |
| 0x80010115 | OLE 已送出要求，正在等候回覆。 |
OLE has sent a request and is waiting for a reply. |
| 0x80010116 | 在重試要求前，OLE 處於等候狀態。 |
OLE is waiting before retrying a request. |
| 0x80010117 | 呼叫完成後，不可以再存取呼叫內容。 |
Call context cannot be accessed after call completed. |
| 0x80010118 | 不支援未受保護之呼叫模擬。 |
Impersonate on unsecure calls is not supported. |
| 0x80010119 | 整理或重新整理任何介面之前，必須初始安全性。一旦初始設定後就不能再變更。 |
Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized. |
| 0x8001011A | 這台電腦尚未安裝安全性封裝，或使用者未登入，或在用戶端與伺服器之間沒有相容的安全性封裝。 |
No security packages are installed on this machine or the user is not logged on or there are no compatible security packages between the client and server. |
| 0x8001011C | 這項處理不可有遠端呼叫。 |
Remote calls are not allowed for this process. |
| 0x8001011D | 排列的介面資料封包 (OBJREF) 中有無效或不明的格式。 |
The marshaled interface data packet (OBJREF) has an invalid or unknown format. |
| 0x8001011E | 沒有與這個呼叫相關的內容。這常發生在一些自訂排列呼叫及用戶端的呼叫。 |
No context is associated with this call. This happens for some custom marshalled calls and on the client side of the call. |
| 0x80010120 | 沒有需要等候的同步物件。 |
There are no synchronize objects to wait on. |
| 0x80010121 | 伺服器需有完整的主體簽發者鏈結 SSL 主體名稱。 |
Full subject issuer chain SSL principal name expected from the server. |
| 0x80010122 | 主體名稱不是正確的 MSSTD 名稱。 |
Principal name is not a valid MSSTD name. |
| 0x80010123 | 無法模擬 DCOM 用戶端 |
Unable to impersonate DCOM client |
| 0x80010124 | 無法取得伺服器資訊安全內容 |
Unable to obtain server's security context |
| 0x80010125 | 無法開啟目前執行緒的存取權杖 |
Unable to open the access token of the current thread |
| 0x80010126 | 無法從存取權杖中取得使用者資訊 |
Unable to obtain user info from an access token |
| 0x80010127 | 呼叫了 IAccessControl::IsAccessPermitted 的用戶端不是提供給這個方法的受信成員 |
The client who called IAccessControl::IsAccessPermitted was not the trustee provided to the method |
| 0x80010128 | 無法取得用戶端安全性資料組 |
Unable to obtain the client's security blanket |
| 0x80010129 | 無法設定安全性描述元的 ACL 判別 |
Unable to set a discretionary ACL into a security descriptor |
| 0x8001012A | 系統功能 AccessCheck 傳回 false 值 |
The system function, AccessCheck, returned false |
| 0x8001012B | 從 NetAccessDel 或 NetAccessAdd 傳回一個錯誤碼。 |
Either NetAccessDel or NetAccessAdd returned an error code. |
| 0x8001012C | 有一個使用者提供的受信字串無法對應到 \\ 的語法，而且它不是\"*\"字串 |
One of the trustee strings provided by the user did not conform to the \\ syntax and it was not the \"*\" string |
| 0x8001012D | 有一個使用者提供的安全性識別碼不正確 |
One of the security identifiers provided by the user was invalid |
| 0x8001012E | 無法將有萬用字元的信任字串轉換成多位元組的信任字串 |
Unable to convert a wide character trustee string to a multibyte trustee string |
| 0x8001012F | 找不到可對應到使用者所提供的信任字串的安全性識別碼 |
Unable to find a security identifier that corresponds to a trustee string provided by the user |
| 0x80010130 | 系統功能 LookupAccountSID 失敗 |
The system function, LookupAccountSID, failed |
| 0x80010131 | 找不到可對應到使用者所提供的安全性識別碼的信任名稱 |
Unable to find a trustee name that corresponds to a security identifier provided by the user |
| 0x80010132 | 系統功能 LookupAccountName 失敗 |
The system function, LookupAccountName, failed |
| 0x80010133 | 無法設定或重設一個連續控制代碼 |
Unable to set or reset a serialization handle |
| 0x80010134 | 無法取得 Windows 目錄 |
Unable to obtain the Windows directory |
| 0x80010135 | 路徑太長 |
Path too long |
| 0x80010136 | 無法產生一個 uuid。 |
Unable to generate a uuid. |
| 0x80010137 | 無法建立檔案 |
Unable to create file |
| 0x80010138 | 無法關閉連續控制代碼或檔案控制代碼。 |
Unable to close a serialization handle or a file handle. |
| 0x80010139 | ACL 中的 ACE 數字超過系統限制。 |
The number of ACEs in an ACL exceeds the system limit. |
| 0x8001013A | 資料流中並非所有的 DENY_ACCESS ACE 都被安排在 GRANT_ACCESS ACE 之前。 |
Not all the DENY_ACCESS ACEs are arranged in front of the GRANT_ACCESS ACEs in the stream. |
| 0x8001013B | 在資料流中的 ACL 格式版本不受 IAccessControl 執行方式支援 |
The version of ACL format in the stream is not supported by this implementation of IAccessControl |
| 0x8001013C | 無法開啟伺服器處理程序的存取權杖 |
Unable to open the access token of the server process |
| 0x8001013D | 無法由使用者的資料流，將 ACL 解碼 |
Unable to decode the ACL in the stream provided by the user |
| 0x8001013F | COM IAccessControl 物件並未初始化 |
The COM IAccessControl object is not initialized |
| 0x80010140 | Call Cancellation 已停用 |
Call Cancellation is disabled |
| 0x80020003 | 找不到成員。 |
Member not found. |
| 0x80020004 | 找不到參數。 |
Parameter not found. |
| 0x80020005 | 類型不符。 |
Type mismatch. |
| 0x80020006 | 不明的名稱。 |
Unknown name. |
| 0x80020007 | 沒有指名的引數。 |
No named arguments. |
| 0x80020008 | 錯誤的變數類型。 |
Bad variable type. |
| 0x80020009 | 發生例外狀況。 |
Exception occurred. |
| 0x8002000A | 超出目前範圍。 |
Out of present range. |
| 0x8002000C | 不明的語言。 |
Unknown language. |
| 0x8002000D | 記憶體已鎖定。 |
Memory is locked. |
| 0x8002000E | 無效的參數數目。 |
Invalid number of parameters. |
| 0x8002000F | 並非選擇性的參數。 |
Parameter not optional. |
| 0x80020010 | 無效的被呼叫者。 |
Invalid callee. |
| 0x80020011 | 不支援收集。 |
Does not support a collection. |
| 0x80020012 | 除以零。 |
Division by zero. |
| 0x80020013 | 緩衝區太小 |
Buffer too small |
| 0x80028016 | 緩衝區太小。 |
Buffer too small. |
| 0x80028017 | 記錄中的欄位名稱並未定義。 |
Field name not defined in the record. |
| 0x80028018 | 格式太舊或是類型程式庫無效。 |
Old format or invalid type library. |
| 0x8002801C | 存取 OLE 登錄時發生錯誤。 |
Error accessing the OLE registry. |
| 0x8002801D | 程式庫未登錄。 |
Library not registered. |
| 0x80028027 | 連結到不明的類型。 |
Bound to unknown type. |
| 0x80028028 | 合格的名稱未被允許。 |
Qualified name disallowed. |
| 0x80028029 | 先前參照無效，或是參照到未編譯的類型。 |
Invalid forward reference, or reference to uncompiled type. |
| 0x8002802C | 不確定的名稱。 |
Ambiguous name. |
| 0x8002802D | 程式庫中已有此名稱。 |
Name already exists in the library. |
| 0x8002802E | 不明的 LCID。 |
Unknown LCID. |
| 0x8002802F | 指定的 DLL 中未定義功能。 |
Function not defined in specified DLL. |
| 0x800288BD | 模組類型不適用這項操作。 |
Wrong module kind for the operation. |
| 0x800288C5 | 大小不能超過 64K。 |
Size may not exceed 64K. |
| 0x800288C6 | 繼承階層中有重複的識別碼。 |
Duplicate ID in inheritance hierarchy. |
| 0x800288CF | 標準 OLE hmember 中有不正確的繼承深度。 |
Incorrect inheritance depth in standard OLE hmember. |
| 0x80028CA1 | 引數的數目無效。 |
Invalid number of arguments. |
| 0x80028CA2 | I/O 錯誤。 |
I/O Error. |
| 0x80028CA3 | 建立唯一暫存檔時發生錯誤。 |
Error creating unique tmp file. |
| 0x80029C4A | 載入類型程式庫/DLL 時發生錯誤。 |
Error loading type library/DLL. |
| 0x80029C83 | 不一致的內容函數。 |
Inconsistent property functions. |
| 0x80029C84 | 類型/模組間的循環相依性。 |
Circular dependency between types/modules. |
| 0x80030001 | 無法執行要求的操作。 |
Unable to perform requested operation. |
| 0x80030002 | 找不到 %1。 |
%1 could not be found. |
| 0x80030003 | 找不到路徑 %1。 |
The path %1 could not be found. |
| 0x80030004 | 資源不足，無法開啟其他檔案。 |
There are insufficient resources to open another file. |
| 0x80030005 | 拒絕存取。 |
Access Denied. |
| 0x80030006 | 嘗試在無效的物件上執行操作。 |
Attempted an operation on an invalid object. |
| 0x80030008 | 可用記憶體不足，無法完成操作。 |
There is insufficient memory available to complete operation. |
| 0x80030009 | 指標無效的錯誤。 |
Invalid pointer error. |
| 0x80030012 | 沒有其他可傳回的項目。 |
There are no more entries to return. |
| 0x80030013 | 磁碟有防寫保護。 |
Disk is write-protected. |
| 0x80030019 | 執行搜尋操作時發生錯誤。 |
An error occurred during a seek operation. |
| 0x8003001D | 執行寫入操作時發生磁碟錯誤。 |
A disk error occurred during a write operation. |
| 0x8003001E | 執行讀取操作時發生磁碟錯誤。 |
A disk error occurred during a read operation. |
| 0x80030020 | 發生共用違規。 |
A share violation has occurred. |
| 0x80030021 | 發生鎖定違規。 |
A lock violation has occurred. |
| 0x80030050 | %1 已經存在。 |
%1 already exists. |
| 0x80030057 | 發生參數無效的錯誤。 |
Invalid parameter error. |
| 0x80030070 | 磁碟空間不足，無法完成操作。 |
There is insufficient disk space to complete operation. |
| 0x800300F0 | 非簡易內容與簡易內容集之間的不合法寫入。 |
Illegal write of non-simple property to simple property set. |
| 0x800300FA | 存在某個不正常的 API 呼叫。 |
An API call exited abnormally. |
| 0x800300FB | %1 檔案不是正確的複合檔案。 |
The file %1 is not a valid compound file. |
| 0x800300FC | 名稱 %1 不正確。 |
The name %1 is not valid. |
| 0x800300FD | 發生意外的錯誤。 |
An unexpected error occurred. |
| 0x800300FE | 不支援這個函數。 |
That function is not implemented. |
| 0x800300FF | 發生旗標無效的錯誤。 |
Invalid flag error. |
| 0x80030100 | 嘗試使用一個忙碌中的物件。 |
Attempted to use an object that is busy. |
| 0x80030101 | 自從上次確認之後，存放區已經變更。 |
The storage has been changed since the last commit. |
| 0x80030102 | 嘗試使用一個已不存在的物件。 |
Attempted to use an object that has ceased to exist. |
| 0x80030103 | 無法儲存。 |
Can't save. |
| 0x80030104 | %1 這個複合檔案是由不相容版本的存放區所產生的。 |
The compound file %1 was produced with an incompatible version of storage. |
| 0x80030105 | %1 這個複合檔案是由較新版的存放區所產生的。 |
The compound file %1 was produced with a newer version of storage. |
| 0x80030106 | 這項操作需要 Share.exe 或類似程式。 |
Share.exe or equivalent is required for operation. |
| 0x80030107 | 在非檔案基本存放體上呼叫了非法的操作。 |
Illegal operation called on non-file based storage. |
| 0x80030108 | 在現存排列物件上呼叫了非法的操作。 |
Illegal operation called on object with extant marshallings. |
| 0x80030109 | 文件檔已損壞。 |
The docfile has been corrupted. |
| 0x80030110 | OLE32.DLL 已載入於錯誤的位址。 |
OLE32.DLL has been loaded at the wrong address. |
| 0x80030111 | 複合檔案太大，目前的執行方式無法執行 |
The compound file is too large for the current implementation |
| 0x80030112 | 複合檔案並未和 STGM_SIMPLE 旗標一起建立 |
The compound file was not created with the STGM_SIMPLE flag |
| 0x80030201 | 檔案下載異常中止。檔案不完整。 |
The file download was aborted abnormally. The file is incomplete. |
| 0x80030202 | 檔案下載已終止。 |
The file download has been terminated. |
| 0x80030208 | 指定的韌體插槽無效。 |
The specified firmware slot is invalid. |
| 0x80030209 | 指定的韌體映像無效。 |
The specified firmware image is invalid. |
| 0x8003020A | 存放裝置沒有回應。 |
The storage device is unresponsive. |
| 0x80030305 | 一般複製保護錯誤。 |
Generic Copy Protection Error. |
| 0x80030306 | 複製保護錯誤 - DVD CSS 驗證失敗。 |
Copy Protection Error - DVD CSS Authentication failed. |
| 0x80030307 | 複製保護錯誤 - 指定的磁區沒有正確的 CSS 機碼。 |
Copy Protection Error - The given sector does not have a valid CSS key. |
| 0x80030308 | 複製保護錯誤 - 尚未建立 DVD 工作階段金鑰。 |
Copy Protection Error - DVD session key not established. |
| 0x80030309 | 複製保護錯誤 - 讀取失敗，因為磁區已加密。 |
Copy Protection Error - The read failed because the sector is encrypted. |
| 0x8003030A | 複製保護錯誤 - 目前的 DVD 所在區域沒有對應於光碟機的地區設定。 |
Copy Protection Error - The current DVD's region does not correspond to the region setting of the drive. |
| 0x8003030B | 複製保護錯誤 - 光碟機的地區設定可能是永久性的，或者使用者重設的數目已經用完了。 |
Copy Protection Error - The drive's region setting may be permanent or the number of user resets has been exhausted. |
| 0x80040000 | 無效的 OLEVERB 結構 |
Invalid OLEVERB structure |
| 0x80040001 | 無效的指示旗標 |
Invalid advise flags |
| 0x80040002 | 因為關聯的資料已遺失，無法再列舉 |
Can't enumerate any more, because the associated data is missing |
| 0x80040003 | 這項操作不接受指示 |
This implementation doesn't take advises |
| 0x80040004 | 這個連線識別碼沒有連線 |
There is no connection for this connection ID |
| 0x80040005 | 需要執行物件，才能進行這項操作 |
Need to run the object to perform this operation |
| 0x80040006 | 沒有快取可供操作 |
There is no cache to operate on |
| 0x80040007 | 未初始化的物件 |
Uninitialized object |
| 0x80040008 | 連結物件的來源類別已變更 |
Linked object's source class has changed |
| 0x80040009 | 無法取得物件的 moniker |
Not able to get the moniker of the object |
| 0x8004000A | 無法連結到來源 |
Not able to bind to the source |
| 0x8004000B | 物件為靜態; 不允許此項操作 |
Object is static; operation not allowed |
| 0x8004000C | 使用者取消 [無法儲存] 對話方塊 |
User canceled out of save dialog |
| 0x8004000D | 無效的矩形 |
Invalid rectangle |
| 0x8004000E | 對於啟動的 ole2.dll 而言，compobj.dll 的版本已太舊 |
compobj.dll is too old for the ole2.dll initialized |
| 0x8004000F | 不正確的視窗控制代碼 |
Invalid window handle |
| 0x80040010 | 物件並不在任何的就地使用中狀態 |
Object is not in any of the inplace active states |
| 0x80040011 | 無法轉換物件 |
Not able to convert object |
| 0x80040012 | 因為尚未指定物件存放空間，所以無法執行操作 |
Not able to perform the operation because object is not given storage yet |
| 0x80040064 | 無效的 FORMATETC 結構 |
Invalid FORMATETC structure |
| 0x80040065 | 無效的 DVTARGETDEVICE 結構 |
Invalid DVTARGETDEVICE structure |
| 0x80040066 | 無效的 STDGMEDIUM 結構 |
Invalid STDGMEDIUM structure |
| 0x80040067 | 無效的 STATDATA 結構 |
Invalid STATDATA structure |
| 0x80040068 | 無效的 lindex |
Invalid lindex |
| 0x80040069 | 無效的 tymed |
Invalid tymed |
| 0x8004006A | 無效的剪貼簿格式 |
Invalid clipboard format |
| 0x8004006B | 無效的相位 |
Invalid aspect(s) |
| 0x8004006C | DVTARGETDEVICE 結構的 tdSize 參數無效 |
tdSize parameter of the DVTARGETDEVICE structure is invalid |
| 0x8004006D | 物件不支援 IViewObject 介面 |
Object doesn't support IViewObject interface |
| 0x80040100 | 嘗試撤銷一個未登錄的拖放目標 |
Trying to revoke a drop target that has not been registered |
| 0x80040101 | 這個視窗已登錄為拖放目標 |
This window has already been registered as a drop target |
| 0x80040103 | 拖曳操作已在進行中 |
A drag operation is already in progress |
| 0x80040110 | 類別不支援集合，或是類別物件為遠端物件 |
Class does not support aggregation (or class object is remote) |
| 0x80040111 | ClassFactory 無法供應要求的類別 |
ClassFactory cannot supply requested class |
| 0x80040112 | 類別未授權使用 |
Class is not licensed for use |
| 0x80040140 | 繪製檢視錯誤 |
Error drawing view |
| 0x80040150 | 無法從登錄中讀取機碼 |
Could not read key from registry |
| 0x80040151 | 無法在登錄中寫入機碼 |
Could not write key to registry |
| 0x80040152 | 登錄中找不到這個機碼 |
Could not find the key in the registry |
| 0x80040153 | 無效的登錄值 |
Invalid value for registry |
| 0x80040154 | 類別未登錄 |
Class not registered |
| 0x80040155 | 介面未登錄 |
Interface not registered |
| 0x80040156 | 執行緒模型項目不正確 |
Threading model entry is not valid |
| 0x80040157 | 套件中的註冊資訊違反套件特定原則 |
A registration in a package violates package-specific policies |
| 0x80040160 | CATID 不存在 |
CATID does not exist |
| 0x80040161 | 找不到描述 |
Description not found |
| 0x80040164 | Active Directory 的軟體安裝資料中沒有符合條件的封裝。 |
No package in the software installation data in the Active Directory meets this criteria. |
| 0x80040165 | 刪除這個項目將中斷 Active Directory 中軟體安裝資料的參照完整性。 |
Deleting this will break the referential integrity of the software installation data in the Active Directory. |
| 0x80040166 | 無法在 Active Directory 的軟體安裝資料找到 CLSID。 |
The CLSID was not found in the software installation data in the Active Directory. |
| 0x80040167 | Active Directory 的軟體安裝資料已損毀。 |
The software installation data in the Active Directory is corrupt. |
| 0x80040168 | Active Directory 中沒有軟體安裝資料。 |
There is no software installation data in the Active Directory. |
| 0x80040169 | Active Directory 中沒有軟體安裝資料物件。 |
There is no software installation data object in the Active Directory. |
| 0x8004016A | Active Directory 的軟體安裝資料物件已存在。 |
The software installation data object in the Active Directory already exists. |
| 0x8004016B | Active Directory 的軟體安裝資料路徑不正確。 |
The path to the software installation data in the Active Directory is not correct. |
| 0x8004016C | 網路錯誤導致操作插斷。 |
A network error interrupted the operation. |
| 0x8004016D | 這個物件大小超過系統管理員的最大限制。 |
The size of this object exceeds the maximum size set by the Administrator. |
| 0x8004016E | Active Directory 的軟體安裝資料的架構與要求的架構不符。 |
The schema for the software installation data in the Active Directory does not match the required schema. |
| 0x8004016F | Active Directory 的軟體安裝資料發生錯誤。 |
An error occurred in the software installation data in the Active Directory. |
| 0x80040170 | 快取未更新 |
Cache not updated |
| 0x80040180 | OLE 物件沒有 verb |
No verbs for OLE object |
| 0x800401A0 | 無法使用 [復原] |
Undo is not available |
| 0x800401A1 | 工具程式沒有可用空間 |
Space for tools is not available |
| 0x800401C0 | OLESTREAM Get method 失敗 |
OLESTREAM Get method failed |
| 0x800401C1 | OLESTREAM Put method 失敗 |
OLESTREAM Put method failed |
| 0x800401C2 | OLESTREAM 的內容並非正確的格式 |
Contents of the OLESTREAM not in correct format |
| 0x800401C3 | 將點陣圖轉換成 DIB 時，某個 Windows GDI 呼叫發生錯誤 |
There was an error in a Windows GDI call while converting the bitmap to a DIB |
| 0x800401C4 | IStorage 的內容並非正確的格式 |
Contents of the IStorage not in correct format |
| 0x800401C5 | IStorage 的內容遺失某個標準資料流 |
Contents of IStorage is missing one of the standard streams |
| 0x800401C6 | 將 DIB 轉換成點陣圖時，某個 Windows GDI 呼叫發生錯誤。 |
There was an error in a Windows GDI call while converting the DIB to a bitmap. |
| 0x800401D0 | OpenClipboard 失敗 |
OpenClipboard Failed |
| 0x800401D1 | EmptyClipboard 失敗 |
EmptyClipboard Failed |
| 0x800401D2 | SetClipboard 失敗 |
SetClipboard Failed |
| 0x800401D3 | 剪貼簿的資料無效 |
Data on clipboard is invalid |
| 0x800401D4 | CloseClipboard 失敗 |
CloseClipboard Failed |
| 0x800401E0 | Moniker 需要以手動方式連接 |
Moniker needs to be connected manually |
| 0x800401E1 | 操作已超過期限 |
Operation exceeded deadline |
| 0x800401E2 | Moniker 必須是一般性的 |
Moniker needs to be generic |
| 0x800401E3 | 操作無法使用 |
Operation unavailable |
| 0x800401E4 | 無效的語法 |
Invalid syntax |
| 0x800401E5 | 沒有供 moniker 使用的物件 |
No object for moniker |
| 0x800401E6 | 檔案的延伸錯誤 |
Bad extension for file |
| 0x800401E7 | 中繼操作失敗 |
Intermediate operation failed |
| 0x800401E8 | Moniker 不可連結 |
Moniker is not bindable |
| 0x800401E9 | Moniker 並未連結 |
Moniker is not bound |
| 0x800401EA | Moniker 無法開啟檔案 |
Moniker cannot open file |
| 0x800401EB | 需要使用者輸入才能完成操作 |
User input required for operation to succeed |
| 0x800401EC | Moniker 類別沒有倒數 |
Moniker class has no inverse |
| 0x800401ED | Moniker 並未參照到存放庫 |
Moniker does not refer to storage |
| 0x800401EE | 沒有共同首碼 |
No common prefix |
| 0x800401EF | Moniker 無法被列舉 |
Moniker could not be enumerated |
| 0x800401F0 | CoInitialize 尚未被呼叫。 |
CoInitialize has not been called. |
| 0x800401F1 | CoInitialize 已被呼叫。 |
CoInitialize has already been called. |
| 0x800401F2 | 無法判別物件的類別 |
Class of object cannot be determined |
| 0x800401F3 | 無效的類別字串 |
Invalid class string |
| 0x800401F4 | 無效的介面字串 |
Invalid interface string |
| 0x800401F5 | 找不到應用程式 |
Application not found |
| 0x800401F6 | 應用程式無法執行多次 |
Application cannot be run more than once |
| 0x800401F7 | 應用程式中有某個錯誤 |
Some error in application program |
| 0x800401F8 | 類別所需的 DLL 找不到 |
DLL for class not found |
| 0x800401F9 | DLL 中有錯誤 |
Error in the DLL |
| 0x800401FA | 應用程式無法使用這個作業系統或作業系統版本 |
Wrong OS or OS version for application |
| 0x800401FB | 物件未登錄 |
Object is not registered |
| 0x800401FC | 物件已登錄 |
Object is already registered |
| 0x800401FD | 物件未連接到伺服器 |
Object is not connected to server |
| 0x800401FE | 應用程式已啟動，但未登錄類別 |
Application was launched but it didn't register a class factory |
| 0x800401FF | 物件已被釋放 |
Object has been released |
| 0x80040201 | 事件無法啟動任何訂閱者 |
An event was unable to invoke any of the subscribers |
| 0x80040203 | 嘗試評估一個查詢字串時，發生一個語法錯誤 |
A syntax error occurred trying to evaluate a query string |
| 0x80040204 | 查詢字串中使用了不正確的欄位名稱 |
An invalid field name was used in a query string |
| 0x80040205 | 引發一個意外的例外 |
An unexpected exception was raised |
| 0x80040206 | 偵測到一個意外的內部錯誤 |
An unexpected internal error was detected |
| 0x80040207 | 依照每一使用者訂閱的擁有者 SID 不存在 |
The owner SID on a per-user subscription doesn't exist |
| 0x80040208 | 因為一個使用者提供的元件或訂戶而引發一個例外狀況 |
A user-supplied component or subscriber raised an exception |
| 0x80040209 | 介面有太多可從中引發事件的方法 |
An interface has too many methods to fire events from |
| 0x8004020A | 無法存放一個訂閱，因為它的事件類別不存在 |
A subscription cannot be stored unless its event class already exists |
| 0x8004020B | 並非所有要求的物件都可以移除 |
Not all the objects requested could be removed |
| 0x8004020C | 執行這個操作需要有 COM+，但並未安裝 |
COM+ is required for this operation, but is not installed |
| 0x8004020D | 無法修改或刪除不是使用 COM+ 管理 SDK 所加入的物件 |
Cannot modify or delete an object that was not added using the COM+ Admin SDK |
| 0x8004020E | 無法修改或刪除使用 COM+ 管理 SDK 所加入的物件 |
Cannot modify or delete an object that was added using the COM+ Admin SDK |
| 0x8004020F | 此訂閱的事件類別位於無效的分割中 |
The event class for this subscription is in an invalid partition |
| 0x80040210 | PerUser 訂閱的擁有者未登入到所指定的系統 |
The owner of the PerUser subscription is not logged on to the system specified |
| 0x80040212 | TabletPC 筆跡錯誤碼。沒有預設的 Tablet |
TabletPC inking error code. No default tablet |
| 0x80040219 | TabletPC 筆跡錯誤碼。指定的輸入矩形無效 |
TabletPC inking error code. An invalid input rectangle was specified |
| 0x8004021B | TabletPC 筆跡錯誤碼。無法辨識指定的屬性 |
TabletPC inking error code. Unknown property specified |
| 0x80040222 | TabletPC 筆跡錯誤碼。已刪除該筆觸物件 |
TabletPC inking error code. The stroke object was deleted |
| 0x80040223 | TabletPC 筆跡錯誤碼。初始化失敗 |
TabletPC inking error code. Initialization failure |
| 0x80040232 | TabletPC 筆跡錯誤碼。未提供該作業所需的資料 |
TabletPC inking error code. The data required for the operation was not supplied |
| 0x80040233 | TabletPC 筆跡錯誤碼。無效的封包描述 |
TabletPC inking error code. Invalid packet description |
| 0x80040235 | TabletPC 筆跡錯誤碼。未登錄任何手寫辨識器 |
TabletPC inking error code. There are no handwriting recognizers registered |
| 0x80040236 | TabletPC 筆跡錯誤碼。使用者沒有讀取辨識器資訊的必要權限 |
TabletPC inking error code. User does not have the necessary rights to read recognizer information |
| 0x80040237 | TabletPC 筆跡錯誤碼。API 呼叫是以不正確的順序執行 |
TabletPC inking error code. API calls were made in an incorrect order |
| 0x80040238 | TabletPC 筆跡錯誤碼。佇列已滿 |
TabletPC inking error code. Queue is full |
| 0x80040239 | TabletPC 筆跡錯誤碼。呼叫了多次 RtpEnabled |
TabletPC inking error code. RtpEnabled called multiple times |
| 0x8004023A | TabletPC 筆跡錯誤碼。辨識器傳回無效的資料 |
TabletPC inking error code. A recognizer returned invalid data |
| 0x80040241 | TabletPC 筆跡錯誤碼。找不到該屬性，或辨識器不支援該屬性 |
TabletPC inking error code. The property was not found, or supported by the recognizer |
| 0x80041309 | 找不到觸發程序。 |
Trigger not found. |
| 0x8004130A | 一個或多個必須在這個工作上執行的內容尚未設定。 |
One or more of the properties that are needed to run this task have not been set. |
| 0x8004130B | 沒有正在執行的工作例項。 |
There is no running instance of the task. |
| 0x8004130C | 工作排程器服務並未安裝到這部電腦上。 |
The Task Scheduler Service is not installed on this computer. |
| 0x8004130D | 這個工作物件無法開啟。 |
The task object could not be opened. |
| 0x8004130E | 物件可能是無效的工作物件或不是個工作物件。 |
The object is either an invalid task object or is not a task object. |
| 0x8004130F | 找不到指示的工作排程器安全性資料庫帳戶資訊。 |
No account information could be found in the Task Scheduler security database for the task indicated. |
| 0x80041310 | 無法建立指定的帳戶的存在。 |
Unable to establish existence of the account specified. |
| 0x80041311 | 偵測出工作排程器安全性資料庫有損毀; 資料庫已經重設。 |
Corruption was detected in the Task Scheduler security database; the database has been reset. |
| 0x80041312 | 工作排程器安全性服務只有在 Windows NT 上才可供使用。 |
Task Scheduler security services are available only on Windows NT. |
| 0x80041313 | 工作物件版本不受支援或無效。 |
The task object version is either unsupported or invalid. |
| 0x80041314 | 工作已經由不受支援的帳戶設定值和執行時間選項組合設定而成。 |
The task has been configured with an unsupported combination of account settings and run time options. |
| 0x80041315 | 工作排程器服務不在執行中。 |
The Task Scheduler Service is not running. |
| 0x80041316 | 工作 XML 包含未預期的節點。 |
The task XML contains an unexpected node. |
| 0x80041317 | 工作 XML 包含來自未預期命名空間的元素或屬性。 |
The task XML contains an element or attribute from an unexpected namespace. |
| 0x80041318 | 工作 XML 包含格式不正確或超過範圍的值。 |
The task XML contains a value which is incorrectly formatted or out of range. |
| 0x80041319 | 工作 XML 遺失必要元素或屬性。 |
The task XML is missing a required element or attribute. |
| 0x8004131A | 工作 XML 格式不正確。 |
The task XML is malformed. |
| 0x8004131D | 工作 XML 包含太多相同類型的節點。 |
The task XML contains too many nodes of the same type. |
| 0x8004131E | 在觸發程序的結尾界限之後，無法啟動工作。 |
The task cannot be started after the trigger's end boundary. |
| 0x8004131F | 此工作的例項已在執行中。 |
An instance of this task is already running. |
| 0x80041320 | 因為使用者未登入，所以不會執行工作。 |
The task will not run because the user is not logged on. |
| 0x80041321 | 工作映像已損毀或已遭竄改。 |
The task image is corrupt or has been tampered with. |
| 0x80041322 | 無法使用工作排程器服務。 |
The Task Scheduler service is not available. |
| 0x80041323 | 工作排程器服務太過忙碌，無法處理您的要求。請稍後再試。 |
The Task Scheduler service is too busy to handle your request. Please try again later. |
| 0x80041324 | 工作排程器服務已嘗試執行工作，但因為工作定義中的其中一個限制導致工作無法執行。 |
The Task Scheduler service attempted to run the task, but the task did not run due to one of the constraints in the task definition. |
| 0x80041326 | 工作已停用。 |
The task is disabled. |
| 0x80041327 | 該工作內含與舊版 Windows 不相容的內容。 |
The task has properties that are not compatible with previous versions of Windows. |
| 0x80041328 | 工作設定不允許工作依指定啟動。 |
The task settings do not allow the task to start on demand. |
| 0x80041329 | 工作正在使用的屬性組合與排程引擎不相容。 |
The combination of properties that task is using is not compatible with the scheduling engine. |
| 0x80041330 | 工作定義使用了過時的功能。 |
The task definition uses a deprecated feature. |
| 0x8004D000 | 在這次交易中已經徵募了另一個單一階段資源管理員。 |
Another single phase resource manager has already been enlisted in this transaction. |
| 0x8004D001 | 不支援持續性的認可或中止 |
A retaining commit or abort is not supported |
| 0x8004D002 | 無法認可原因不明的交易，因此已經中止交易。 |
The transaction failed to commit for an unknown reason. The transaction was aborted. |
| 0x8004D003 | 無法呼叫這個交易物件的認可，因為呼叫的應用程式並未初始化該交易。 |
Cannot call commit on this transaction object because the calling application did not initiate the transaction. |
| 0x8004D004 | 並未認可，該資源啟發式地中止了。 |
Instead of committing, the resource heuristically aborted. |
| 0x8004D005 | 並未中止，該資源啟發式地認可了。 |
Instead of aborting, the resource heuristically committed. |
| 0x8004D006 | 資源的一部分狀態被認可，但是其餘的被中止。似乎是由於啟發式的決定。 |
Some of the states of the resource were committed while others were aborted, likely because of heuristic decisions. |
| 0x8004D007 | 資源的一部分狀態可能已被認可，但是其餘的可能已中止。似乎是由於啟發式的決定。 |
Some of the states of the resource may have been committed while others may have been aborted, likely because of heuristic decisions. |
| 0x8004D008 | 所要求的孤立層不正確或者不受支援。 |
The requested isolation level is not valid or supported. |
| 0x8004D009 | 交易管理員不支援這個方法的非同步操作。 |
The transaction manager doesn't support an asynchronous operation for this method. |
| 0x8004D00A | 無法在交易中徵募。 |
Unable to enlist in the transaction. |
| 0x8004D00B | 所要求的遍及持續性認可及中止界限的保持孤立語義學並不受這個交易執行方式所支援，或者 isoFlags 不等於零。 |
The requested semantics of retention of isolation across retaining commit and abort boundaries cannot be supported by this transaction implementation, or isoFlags was not equal to zero. |
| 0x8004D00C | 目前沒有資源關聯於這個徵募 |
There is no resource presently associated with this enlistment |
| 0x8004D00D | 交易無法認可，原因是至少有一個資源管理員的寬鬆式同步存取控制失敗。 |
The transaction failed to commit due to the failure of optimistic concurrency control in at least one of the resource managers. |
| 0x8004D00E | 交易已經以暗示或者明確的方式認可或中止了 |
The transaction has already been implicitly or explicitly committed or aborted |
| 0x8004D00F | 指定了不正確的旗標組合 |
An invalid combination of flags was specified |
| 0x8004D010 | 資源管理員識別碼與這項交易或交易管理員沒有關聯。 |
The resource manager id is not associated with this transaction or the transaction manager. |
| 0x8004D011 | 這個方法在錯誤狀態下被呼叫 |
This method was called in the wrong state |
| 0x8004D012 | 指出的工作單元不符合資源管理員所預期的工作單元。 |
The indicated unit of work does not match the unit of work expected by the resource manager. |
| 0x8004D013 | 交易中已經存在有徵募。 |
An enlistment in a transaction already exists. |
| 0x8004D014 | 找不到交易的匯入物件。 |
An import object for the transaction could not be found. |
| 0x8004D015 | 交易 cookie 不正確。 |
The transaction cookie is invalid. |
| 0x8004D016 | 交易狀態尚未確定。可能是通訊失敗，或者是交易管理員或資源管理員已經失敗 |
The transaction status is in doubt. A communication failure occurred, or a transaction manager or resource manager has failed |
| 0x8004D017 | 指定了等候逾時，但等候逾時是不受支援的。 |
A time-out was specified, but time-outs are not supported. |
| 0x8004D018 | 所要求的操作已在進行交易中。 |
The requested operation is already in progress for the transaction. |
| 0x8004D019 | 交易已經中止。 |
The transaction has already been aborted. |
| 0x8004D01A | 交易管理員傳回一個記錄已滿的錯誤。 |
The Transaction Manager returned a log full error. |
| 0x8004D01B | 交易管理員目前無法使用。 |
The Transaction Manager is not available. |
| 0x8004D01C | 與交易管理員已失去連線。 |
A connection with the transaction manager was lost. |
| 0x8004D01D | 與交易管理員建立連線的要求遭到拒絕。 |
A request to establish a connection with the transaction manager was denied. |
| 0x8004D01E | 資源管理員重新徵募以決定交易狀態的等候已經逾時。 |
Resource manager reenlistment to determine transaction status timed out. |
| 0x8004D01F | 這個交易管理員無法與別的 TIP 交易管理員建立連線。 |
This transaction manager failed to establish a connection with another TIP transaction manager. |
| 0x8004D020 | 這個交易管理員與別的 TIP 交易管理員之間遭遇到通訊協定錯誤。 |
This transaction manager encountered a protocol error with another TIP transaction manager. |
| 0x8004D021 | 這個交易管理員無法從別的 TIP 交易管理員傳播交易。 |
This transaction manager could not propagate a transaction from another TIP transaction manager. |
| 0x8004D022 | 目的電腦上的交易管理員無法使用。 |
The Transaction Manager on the destination machine is not available. |
| 0x8004D023 | 交易管理員已經停用了對 TIP 的支援。 |
The Transaction Manager has disabled its support for TIP. |
| 0x8004D024 | 交易管理員已經停用了對遠端/網路交易的支援。 |
The transaction manager has disabled its support for remote/network transactions. |
| 0x8004D025 | 協力電腦交易管理員已經停用了對遠端/網路交易的支援。 |
The partner transaction manager has disabled its support for remote/network transactions. |
| 0x8004D026 | 交易管理員已經停用了對 XA 交易的支援。 |
The transaction manager has disabled its support for XA transactions. |
| 0x8004D027 | MSDTC 無法讀取其設定資訊。 |
MSDTC was unable to read its configuration information. |
| 0x8004D028 | MSDTC 無法載入 DTC Proxy DLL。 |
MSDTC was unable to load the dtc proxy dll. |
| 0x8004D029 | 本機交易已中止。 |
The local transaction has aborted. |
| 0x8004D02A | MSDTC 交易管理員無法將交易推入目的地交易管理員，因為發生通訊問題。可能的原因為: 有防火牆存在且對 MSDTC 處理程序沒有例外狀況、兩部電腦無法依據它們的 NetBIOS 名稱找到彼此，或是其中一個交易管理員未啟用對網路交易的支援。 |
The MSDTC transaction manager was unable to push the transaction to the destination transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. |
| 0x8004D02B | MSDTC 交易管理員無法從來源交易管理員提取交易，因為發生通訊問題。可能的原因為: 有防火牆存在且對於 MSDTC 處理程序沒有例外狀況、兩部電腦無法依據它們的 NetBIOS 名稱找到彼此，或是其中一個交易管理員未啟用對網路交易的支援。 |
The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers. |
| 0x8004D02C | MSDTC 交易管理員已停用對 SNA LU 6.2 交易的支援。 |
The MSDTC transaction manager has disabled its support for SNA LU 6.2 transactions. |
| 0x8004D080 | XACT_E_CLERKNOTFOUND |
XACT_E_CLERKNOTFOUND |
| 0x8004D081 | XACT_E_CLERKEXISTS |
XACT_E_CLERKEXISTS |
| 0x8004D082 | XACT_E_RECOVERYINPROGRESS |
XACT_E_RECOVERYINPROGRESS |
| 0x8004D083 | XACT_E_TRANSACTIONCLOSED |
XACT_E_TRANSACTIONCLOSED |
| 0x8004D084 | XACT_E_INVALIDLSN |
XACT_E_INVALIDLSN |
| 0x8004D085 | XACT_E_REPLAYREQUEST |
XACT_E_REPLAYREQUEST |
| 0x8004D100 | 連線到指定交易協調器的要求被拒絕。 |
The request to connect to the specified transaction coordinator was denied. |
| 0x8004D101 | 已經達到指定交易的徵募數目上限。 |
The maximum number of enlistments for the specified transaction has been reached. |
| 0x8004D102 | 具有相同識別元的資源管理員已經登錄指定的交易協調器。 |
A resource manager with the same identifier is already registered with the specified transaction coordinator. |
| 0x8004D103 | 指定的準備要求不合格，無法進行單一階段最佳化。 |
The prepare request given was not eligible for single phase optimizations. |
| 0x8004D104 | RecoveryComplete 已針對指定的資源管理員呼叫。 |
RecoveryComplete has already been called for the given resource manager. |
| 0x8004D105 | 發出的介面呼叫對於通訊協定的目前狀態而言不正確。 |
The interface call made was incorrect for the current state of the protocol. |
| 0x8004D106 | XA 資源的 xa_open 呼叫失敗。 |
xa_open call failed for the XA resource. |
| 0x8004D107 | XA 資源的 xa_recover 呼叫失敗。 |
xa_recover call failed for the XA resource. |
| 0x8004D108 | 找不到指定的「工作邏輯單元」。 |
The Logical Unit of Work specified cannot be found. |
| 0x8004D109 | 指定的「工作邏輯單元」已存在。 |
The specified Logical Unit of Work already exists. |
| 0x8004D10A | 下層建立失敗。指定的工作邏輯單元未連線。 |
Subordinate creation failed. The specified Logical Unit of Work was not connected. |
| 0x8004D10B | 具有指定識別元的交易已存在。 |
A transaction with the given identifier already exists. |
| 0x8004D10C | 資源正在使用中。 |
The resource is in use. |
| 0x8004D10D | 「LU 修復」程序已關閉。 |
The LU Recovery process is down. |
| 0x8004D10E | 遠端工作階段已遺失。 |
The remote session was lost. |
| 0x8004D10F | 資源目前正在修復。 |
The resource is currently recovering. |
| 0x8004D110 | 驅動修復中有不一致的情形。 |
There was a mismatch in driving recovery. |
| 0x8004D111 | XA 資源發生錯誤。 |
An error occurred with the XA resource. |
| 0x8004E002 | 根交易想要認可，但交易已中止 |
The root transaction wanted to commit, but transaction aborted |
| 0x8004E003 | 您已呼叫 COM+ 元件的方法，但該元件有一個交易且該交易已經中止或即將中止。 |
You made a method call on a COM+ component that has a transaction that has already aborted or in the process of aborting. |
| 0x8004E004 | 沒有 MTS 物件內容 |
There is no MTS object context |
| 0x8004E005 | 元件設定使用同步處理，且這個方法呼叫可能導致發生鎖死。 |
The component is configured to use synchronization and this method call would cause a deadlock to occur. |
| 0x8004E006 | 元件被設定使用同步化處理，並且執行緒在等待內容輸入時已等後逾時 |
The component is configured to use synchronization and a thread has timed out waiting to enter the context. |
| 0x8004E007 | 您已呼叫 COM+ 元件的方法，但該元件有一個交易且該交易已經認可或已經中止。 |
You made a method call on a COM+ component that has a transaction that has already committed or aborted. |
| 0x8004E00C | 尚未設定應用程式所需要的指定角色 |
The specified role was not configured for the application |
| 0x8004E00F | COM+ 無法與 Microsoft Distributed Transaction Coordinator 通訊 |
COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator |
| 0x8004E021 | COM+ 啟用時發生意外的錯誤。 |
An unexpected error occurred during COM+ Activation. |
| 0x8004E022 | COM+ 啟用失敗。請檢查事件記錄檔了解更多資訊 |
COM+ Activation failed. Check the event log for more information |
| 0x8004E023 | COM+ 啟用失敗，因為類別目錄或設定發生錯誤。 |
COM+ Activation failed due to a catalog or configuration error. |
| 0x8004E024 | COM+ 啟用失敗，因為無法在指定的時間內完成啟用。 |
COM+ activation failed because the activation could not be completed in the specified amount of time. |
| 0x8004E025 | COM+ 啟用失敗，因為某個初始化功能失敗。請檢查事件記錄檔了解更多資訊。 |
COM+ Activation failed because an initialization function failed. Check the event log for more information. |
| 0x8004E026 | 要求的操作需要 JIT 在目前的內容中，但它不在 |
The requested operation requires that JIT be in the current context and it is not |
| 0x8004E027 | 要求的操作需要目前的內容有一個交易，但它並沒有 |
The requested operation requires that the current context have a Transaction, and it does not |
| 0x8004E028 | 元件執行緒模型在安裝到一個 COM+ 應用程式後已經改變。請重新安裝元件。 |
The components threading model has changed after install into a COM+ Application. Please re-install component. |
| 0x8004E029 | IIS 本質無法使用。請由 IIS 開始您的工作。 |
IIS intrinsics not available. Start your work with IIS. |
| 0x8004E02A | 企圖寫入 cookie 的嘗試失敗。 |
An attempt to write a cookie failed. |
| 0x8004E02B | 企圖使用資料庫的嘗試產生了一個資料庫特定的錯誤。 |
An attempt to use a database generated a database specific error. |
| 0x8004E02C | 您所建立的 COM+ 元件必須使用物件集區才能工作。 |
The COM+ component you created must use object pooling to work. |
| 0x8004E02D | 您所建立的 COM+ 元件必須使用物件結構才能正確工作。 |
The COM+ component you created must use object construction to work correctly. |
| 0x8004E02E | 這個 COM+ 元件需要同步處理，但卻沒有設定這麼做。 |
The COM+ component requires synchronization, and it is not configured for it. |
| 0x8004E02F | 交易中正在建立的 COM+ 元件的 TxIsolationLevel 內容比 \"根\" 元件的 TxIsolationLevel 還嚴格。建立失敗。 |
The TxIsolation Level property for the COM+ component being created is stronger than the TxIsolationLevel for the \"root\" component for the transaction. The creation failed. |
| 0x8004E030 | 元件已嘗試在叫用 EnterTransactionScopeand ExitTransactionScope 時發出跨內容呼叫。這是不允許的。無法在交易範圍內發出跨內容呼叫。 |
The component attempted to make a cross-context call between invocations of EnterTransactionScopeand ExitTransactionScope. This is not allowed. Cross-context calls cannot be made while inside of a transaction scope. |
| 0x8004E031 | 元件已呼叫 EnterTransactionScope，但並未在傳回前發出對應的 ExitTransactionScope 呼叫。 |
The component made a call to EnterTransactionScope, but did not make a corresponding call to ExitTransactionScope before returning. |
| 0x80072EE1 | 無法再配置其他網際網路控制代碼 |
No more Internet handles can be allocated |
| 0x80072EE2 | 操作逾時 |
The operation timed out |
| 0x80072EE3 | 伺服器傳回延伸資訊 |
The server returned extended information |
| 0x80072EE4 | Microsoft 網際網路擴充功能發生內部錯誤 |
An internal error occurred in the Microsoft Internet extensions |
| 0x80072EE5 | URL 無效 |
The URL is invalid |
| 0x80072EE6 | URL 未使用可辨識的通訊協定 |
The URL does not use a recognized protocol |
| 0x80072EE7 | 無法解析伺服器名稱或位址 |
The server name or address could not be resolved |
| 0x80072EE8 | 找不到具備要求功能的通訊協定 |
A protocol with the required capabilities was not found |
| 0x80072EE9 | 選項無效 |
The option is invalid |
| 0x80072EEA | 選項類型的長度不正確 |
The length is incorrect for the option type |
| 0x80072EEB | 無法設定選項值 |
The option value cannot be set |
| 0x80072EEC | Microsoft 網際網路擴充功能支援已關閉 |
Microsoft Internet Extension support has been shut down |
| 0x80072EED | 不允許該使用者名稱 |
The user name was not allowed |
| 0x80072EEE | 不允許該密碼 |
The password was not allowed |
| 0x80072EEF | 登入要求被拒 |
The login request was denied |
| 0x80072EF0 | 要求的操作無效 |
The requested operation is invalid |
| 0x80072EF1 | 操作已被取消 |
The operation has been canceled |
| 0x80072EF2 | 提供的控制代碼類型不適用於要求的操作 |
The supplied handle is the wrong type for the requested operation |
| 0x80072EF3 | 控制代碼的狀態不適用於要求的操作 |
The handle is in the wrong state for the requested operation |
| 0x80072EF4 | 無法在 Proxy 工作階段上提出要求 |
The request cannot be made on a Proxy session |
| 0x80072EF5 | 找不到登錄值 |
The registry value could not be found |
| 0x80072EF6 | 登錄參數不正確 |
The registry parameter is incorrect |
| 0x80072EF7 | 無法直接存取網際網路 |
Direct Internet access is not available |
| 0x80072EF8 | 未提供內容值 |
No context value was supplied |
| 0x80072EF9 | 未提供狀態回呼 |
No status callback was supplied |
| 0x80072EFA | 尚有未處理的要求 |
There are outstanding requests |
| 0x80072EFB | 資訊格式不正確 |
The information format is incorrect |
| 0x80072EFC | 找不到要求的項目 |
The requested item could not be found |
| 0x80072EFD | 無法建立與伺服器的連線 |
A connection with the server could not be established |
| 0x80072EFE | 伺服器連線異常終止 |
The connection with the server was terminated abnormally |
| 0x80072EFF | 已重設與伺服器的連線 |
The connection with the server was reset |
| 0x80072F00 | 必須重試動作 |
The action must be retried |
| 0x80072F01 | Proxy 要求無效 |
The proxy request is invalid |
| 0x80072F02 | 需要使用者介入才能完成操作 |
User interaction is required to complete the operation |
| 0x80072F04 | 控制代碼已存在 |
The handle already exists |
| 0x80072F05 | 憑證中的日期無效或已過期 |
The date in the certificate is invalid or has expired |
| 0x80072F06 | 憑證中的主機名稱無效或不相符 |
The host name in the certificate is invalid or does not match |
| 0x80072F07 | 重新導向要求將會把不安全連線變更為安全連線 |
A redirect request will change a non-secure to a secure connection |
| 0x80072F08 | 重新導向要求將會把安全連線變更為不安全連線 |
A redirect request will change a secure to a non-secure connection |
| 0x80072F09 | 混合安全與不安全的連線 |
Mixed secure and non-secure connections |
| 0x80072F0A | 正在變更為不安全公佈 |
Changing to non-secure post |
| 0x80072F0B | 正於不安全的連線上公佈資料 |
Data is being posted on a non-secure connection |
| 0x80072F0C | 需要憑證才能完成用戶端驗證 |
A certificate is required to complete client authentication |
| 0x80072F0D | 憑證授權單位無效或不正確 |
The certificate authority is invalid or incorrect |
| 0x80072F0E | 未正確安裝用戶端驗證 |
Client authentication has not been correctly installed |
| 0x80072F0F | Wininet 非同步執行緒中發生錯誤。您可能需要重新啟動 |
An error has occurred in a Wininet asynchronous thread. You may need to restart |
| 0x80072F10 | 通訊協定配置在重新導向操作期間已變更 |
The protocol scheme has changed during a redirect operaiton |
| 0x80072F11 | 有操作正在等待重試 |
There are operations awaiting retry |
| 0x80072F12 | 必須重試操作 |
The operation must be retried |
| 0x80072F13 | 沒有新的快取容器 |
There are no new cache containers |
| 0x80072F14 | 安全性區域檢查指出必須重試操作 |
A security zone check indicates the operation must be retried |
| 0x80072F17 | SSL 憑證包含錯誤。 |
The SSL certificate contains errors. |
| 0x80072F19 | 無法連線至撤銷伺服器，或無法取得明確的回應。 |
It was not possible to connect to the revocation server or a definitive response could not be obtained. |
| 0x80072F76 | 找不到要求的標頭 |
The requested header was not found |
| 0x80072F77 | 伺服器不支援要求的通訊協定層級 |
The server does not support the requested protocol level |
| 0x80072F78 | 伺服器傳回無效或無法辨識的回應 |
The server returned an invalid or unrecognized response |
| 0x80072F79 | 提供的 HTTP 標頭無效 |
The supplied HTTP header is invalid |
| 0x80072F7A | HTTP 標頭的要求無效 |
The request for a HTTP header is invalid |
| 0x80072F7B | HTTP 標頭已存在 |
The HTTP header already exists |
| 0x80072F7C | HTTP 重新導向要求失敗 |
The HTTP redirect request failed |
| 0x80072F7D | 安全通道支援中發生錯誤 |
An error occurred in the secure channel support |
| 0x80072F7E | 無法將檔案寫入到快取 |
The file could not be written to the cache |
| 0x80072F7F | 未正確安裝 TCP/IP 通訊協定 |
The TCP/IP protocol is not installed properly |
| 0x80072F80 | 未重新導向 HTTP 要求 |
The HTTP request was not redirected |
| 0x80072F81 | 來自伺服器的 Cookie 必須經由使用者確認 |
A cookie from the server must be confirmed by the user |
| 0x80072F82 | 來自伺服器的 Cookie 已被拒絕接受 |
A cookie from the server has been declined acceptance |
| 0x80072F83 | 電腦已經與網路中斷連線 |
The computer is disconnected from the network |
| 0x80072F84 | 無法連線到伺服器 |
The server is unreachable |
| 0x80072F85 | 無法連線到 Proxy 伺服器 |
The proxy server is unreachable |
| 0x80072F86 | Proxy 自動設定指令碼發生錯誤 |
The proxy auto-configuration script is in error |
| 0x80072F87 | 無法下載 Proxy 自動設定指令碼檔案 |
Could not download the proxy auto-configuration script file |
| 0x80072F88 | HTTP 重新導向要求必須經由使用者確認 |
The HTTP redirect request must be confirmed by the user |
| 0x80072F89 | 提供的憑證無效 |
The supplied certificate is invalid |
| 0x80072F8A | 提供的憑證已被撤銷 |
The supplied certificate has been revoked |
| 0x80072F8B | 撥號失敗，因為檔案共用為開啟狀態，如果需要安全性檢查，就會要求讓撥號作業失敗 |
The Dialup failed because file sharing was turned on and a failure was requested if security check was needed |
| 0x80072F8C | WinINet API 尚未初始化 |
Initialization of the WinINet API has not occurred |
| 0x80072F8E | 登入失敗，用戶端應向使用者顯示實體內容 |
Login failed and the client should display the entity body to the user |
| 0x80072F8F | 內容解碼失敗 |
Content decoding has failed |
| 0x80080001 | 建立類別物件的嘗試失敗 |
Attempt to create a class object failed |
| 0x80080002 | OLE 服務無法連結物件 |
OLE service could not bind object |
| 0x80080003 | RPC 通訊和 OLE 服務失敗 |
RPC communication failed with OLE service |
| 0x80080004 | 錯誤的物件路徑 |
Bad path to object |
| 0x80080005 | 伺服器執行失敗 |
Server execution failed |
| 0x80080006 | OLE 服務無法與物件伺服器通訊 |
OLE service could not communicate with the object server |
| 0x80080007 | Moniker 路徑無法正常化 |
Moniker path could not be normalized |
| 0x80080008 | OLE 服務與它聯繫時，物件伺服器正在停止 |
Object server is stopping when OLE service contacts it |
| 0x80080009 | 指定不正確的根區塊指標 |
An invalid root block pointer was specified |
| 0x80080010 | 配置鏈結中包含不正確的連結指標 |
An allocation chain contained an invalid link pointer |
| 0x80080011 | 要求的配置值太大 |
The requested allocation size was too large |
| 0x80080015 | 啟用需要 CLSID 機碼下有顯示名稱。 |
The activation requires a display name to be present under the CLSID key. |
| 0x80080016 | 啟用需要應用程式的 RunAs 值是 Activate As Activator。 |
The activation requires that the RunAs value for the application is Activate As Activator. |
| 0x80080017 | 類別未設定為支援 Elevated 啟用。 |
The class is not configured to support Elevated activation. |
| 0x80080200 | Appx 套件處理 API 發生內部錯誤。 |
Appx packaging API has encountered an internal error. |
| 0x80080201 | 檔案不是有效的 Appx 套件，因為其內容為交錯式。 |
The file is not a valid Appx package because its contents are interleaved. |
| 0x80080202 | 檔案不是有效的 Appx 套件，因為它包含 OPC 關係。 |
The file is not a valid Appx package because it contains OPC relationships. |
| 0x80080203 | 檔案不是有效的 Appx 套件，因為它遺漏資訊清單或區塊對應，或遺漏簽章檔案 (當程式碼完整性檔案存在時)。 |
The file is not a valid Appx package because it is missing a manifest or block map, or missing a signature file when the code integrity file is present. |
| 0x80080204 | Appx 套件的資訊清單無效。 |
The Appx package's manifest is invalid. |
| 0x80080205 | Appx 套件的區塊對應無效。 |
The Appx package's block map is invalid. |
| 0x80080206 | 無法讀取 Appx 套件的內容，因為它已損毀。 |
The Appx package's content cannot be read because it is corrupt. |
| 0x80080207 | 所計算的區塊雜湊值與區塊對應中儲存的不相符。 |
The computed hash value of the block does not match the one stored in the block map. |
| 0x80080208 | 要求的位元組範圍在轉譯為區塊的位元組範圍時超過 4GB。 |
The requested byte range is over 4GB when translated to byte range of blocks. |
| 0x80080209 | 用來簽署套件的 SIP_SUBJECTINFO 結構未包含必要資料。 |
The SIP_SUBJECTINFO structure used to sign the package didn't contain the required data. |
| 0x8008020A | 用於將套件加密或解密的 APPX_KEY_INFO 結構包含無效的資料。 |
The APPX_KEY_INFO structure used to encrypt or decrypt the package contains invalid data. |
| 0x8008020B | Appx 套件的內容群組對應表無效。 |
The Appx package's content group map is invalid. |
| 0x80080300 | 背景工作啟用是假性的。 |
The background task activation is spurious. |
| 0x80090001 | UID 錯誤。 |
Bad UID. |
| 0x80090002 | 錯誤的雜湊。 |
Bad Hash. |
| 0x80090003 | 機碼錯誤。 |
Bad Key. |
| 0x80090004 | 長度錯誤。 |
Bad Length. |
| 0x80090005 | 資料錯誤。 |
Bad Data. |
| 0x80090006 | 簽章不正確。 |
Invalid Signature. |
| 0x80090007 | 提供者版本錯誤。 |
Bad Version of provider. |
| 0x80090008 | 指定的演算法無效。 |
Invalid algorithm specified. |
| 0x80090009 | 指定的旗標無效。 |
Invalid flags specified. |
| 0x8009000A | 指定的類型無效。 |
Invalid type specified. |
| 0x8009000B | 機碼用在特定狀態時無效。 |
Key not valid for use in specified state. |
| 0x8009000C | 雜湊用在特定狀態時無效。 |
Hash not valid for use in specified state. |
| 0x8009000D | 機碼不存在。 |
Key does not exist. |
| 0x8009000E | 記憶體不足，無法執行操作。 |
Insufficient memory available for the operation. |
| 0x8009000F | 物件已存在。 |
Object already exists. |
| 0x80090011 | 找不到物件。 |
Object was not found. |
| 0x80090012 | 資料已被加密。 |
Data already encrypted. |
| 0x80090013 | 指定的提供者不正確。 |
Invalid provider specified. |
| 0x80090014 | 指定的提供者類型不正確。 |
Invalid provider type specified. |
| 0x80090015 | 提供者的公開金鑰不正確。 |
Provider's public key is invalid. |
| 0x80090016 | 機碼組不存在 |
Keyset does not exist |
| 0x80090017 | 未定義提供者類型。 |
Provider type not defined. |
| 0x80090018 | 登錄的提供者類型不正確。 |
Provider type as registered is invalid. |
| 0x80090019 | 未定義機碼組。 |
The keyset is not defined. |
| 0x8009001A | 登錄的機碼組不正確。 |
Keyset as registered is invalid. |
| 0x8009001B | 提供者類型與登錄值不符。 |
Provider type does not match registered value. |
| 0x8009001C | 數位簽章檔已損壞。 |
The digital signature file is corrupt. |
| 0x8009001D | 提供者 DLL 無法正確初始設定。 |
Provider DLL failed to initialize correctly. |
| 0x8009001E | 找不到提供者 DLL。 |
Provider DLL could not be found. |
| 0x8009001F | 機碼組參數不正確。 |
The Keyset parameter is invalid. |
| 0x80090021 | 發生基本的錯誤。 |
A base error occurred. |
| 0x80090022 | 提供者無法執行動作，因為內容是隱藏的。 |
Provider could not perform the action since the context was acquired as silent. |
| 0x80090023 | 安全性權杖沒有可用存放空間來新增容器。 |
The security token does not have storage space available for an additional container. |
| 0x80090024 | 這個使用者設定檔是臨時的設定檔。 |
The profile for the user is a temporary profile. |
| 0x80090025 | 關鍵參數無法設定，因為 CSP 使用固定的參數。 |
The key parameters could not be set because the CSP uses fixed parameters. |
| 0x80090026 | 提供的控制代碼不正確。 |
The supplied handle is invalid. |
| 0x80090028 | 提供給函數的緩衝區太小。 |
The buffer supplied to a function was too small. |
| 0x8009002B | 提供的緩衝區不正確地重疊。 |
The supplied buffers overlap incorrectly. |
| 0x8009002C | 無法解密指定的資料。 |
The specified data could not be decrypted. |
| 0x8009002D | 內部一致性檢查失敗。 |
An internal consistency check failed. |
| 0x8009002E | 此操作需要使用者輸入。 |
This operation requires input from the user. |
| 0x8009002F | 密碼編譯提供者不支援 HMAC。 |
The cryptographic provider does not support HMAC. |
| 0x80090030 | 此密碼編譯提供者需要的裝置尚無法使用。 |
The device that is required by this cryptographic provider is not ready for use. |
| 0x80090031 | 已觸發字典攻擊安全防護功能，提供者已略過提供的授權。 |
The dictionary attack mitigation is triggered and the provided authorization was ignored by the provider. |
| 0x80090032 | 所提供資料的驗證無法進行完整性或簽章驗證。 |
The validation of the provided data failed the integrity or signature validation. |
| 0x80090033 | 密碼不正確。 |
Incorrect password. |
| 0x80090034 | 加密失敗。 |
Encryption failed. |
| 0x80090035 | 在此平台上找不到此密碼編譯提供者所需的裝置。 |
The device that is required by this cryptographic provider is not found on this platform. |
| 0x80090036 | 使用者取消這個動作。 |
The action was cancelled by the user. |
| 0x80090037 | 密碼已不再有效，因此需要變更。 |
The password is no longer valid and must be changed. |
| 0x80090038 | 無法從「終端機伺服器」用戶端工作階段完成該作業。 |
The operation cannot be completed from Terminal Server client sessions. |
| 0x80090300 | 記憶體不足，無法完成這個要求 |
Not enough memory is available to complete this request |
| 0x80090301 | 指定的控制代碼不正確 |
The handle specified is invalid |
| 0x80090302 | 不支援要求的功能 |
The function requested is not supported |
| 0x80090303 | 不明或無法達到的指定目標 |
The specified target is unknown or unreachable |
| 0x80090304 | 無法連絡到本機安全性授權單位 |
The Local Security Authority cannot be contacted |
| 0x80090305 | 要求的安全性封裝不存在 |
The requested security package does not exist |
| 0x80090306 | 呼叫者不是需求的認證擁有者 |
The caller is not the owner of the desired credentials |
| 0x80090307 | 安全性封裝初始失敗，無法安裝 |
The security package failed to initialize, and cannot be installed |
| 0x80090308 | 提供給功能的權杖不正確 |
The token supplied to the function is invalid |
| 0x80090309 | 安全性封裝無法整理登入緩衝區，因此登入嘗試失敗 |
The security package is not able to marshall the logon buffer, so the logon attempt has failed |
| 0x8009030A | 安全性封裝不支援依每一訊息的保護品質 |
The per-message Quality of Protection is not supported by the security package |
| 0x8009030B | 資訊安全內容不允許將用戶端模擬化 |
The security context does not allow impersonation of the client |
| 0x8009030C | 登入嘗試失敗 |
The logon attempt failed |
| 0x8009030D | 提供給封裝的認證無法辨識 |
The credentials supplied to the package were not recognized |
| 0x8009030E | 安全性封裝沒有可供使用的認證 |
No credentials are available in the security package |
| 0x8009030F | 供驗證用的訊息或簽章已經被更改 |
The message or signature supplied for verification has been altered |
| 0x80090310 | 供驗證的訊息超出順序 |
The message supplied for verification is out of sequence |
| 0x80090311 | 無法連絡到驗證的授權單位。 |
No authority could be contacted for authentication. |
| 0x80090318 | 提供的訊息不完整。簽章尚未確認。 |
The supplied message is incomplete. The signature was not verified. |
| 0x80090320 | 提供的認證不完整，因此無法確認。無法初始內容。 |
The credentials supplied were not complete, and could not be verified. The context could not be initialized. |
| 0x80090321 | 提供給功能的緩衝區太小。 |
The buffers supplied to a function was too small. |
| 0x80090322 | 目標主體名稱不正確。 |
The target principal name is incorrect. |
| 0x80090324 | 用戶端和伺服器電腦的時鐘不準。 |
The clocks on the client and server machines are skewed. |
| 0x80090325 | 此憑證鏈結是由不受信任的授權單位發出的。 |
The certificate chain was issued by an authority that is not trusted. |
| 0x80090326 | 接收到的訊息超出預期或格式不正確。 |
The message received was unexpected or badly formatted. |
| 0x80090327 | 嘗試處理憑證時發生一個不明的錯誤。 |
An unknown error occurred while processing the certificate. |
| 0x80090328 | 接收到的憑證已經到期。 |
The received certificate has expired. |
| 0x80090329 | 無法加密指定的資料。 |
The specified data could not be encrypted. |
| 0x80090331 | 用戶端和伺服器無法溝通，因為它們沒有公用的演算法。 |
The client and server cannot communicate, because they do not possess a common algorithm. |
| 0x80090332 | 無法建立資訊安全內容，因為要求的服務品質失敗(例如: 相互驗證或委派)。 |
The security context could not be established due to a failure in the requested quality of service (e.g. mutual authentication or delegation). |
| 0x80090333 | 在內容完成之前，其中一個資訊安全內容被刪除了。這屬於登入失敗。 |
A security context was deleted before the context was completed. This is considered a logon failure. |
| 0x80090334 | 用戶端正嘗試交涉一個內容，而伺服器需要的是使用者對使用者，但並未傳送出 TGT 回覆。 |
The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply. |
| 0x80090335 | 無法完成所要求的工作，原因是本機電腦沒有任何 IP 位址。 |
Unable to accomplish the requested task because the local machine does not have any IP addresses. |
| 0x80090336 | 所提供的認證控制代碼與資訊安全內容所關聯的認證不相符合。 |
The supplied credential handle does not match the credential associated with the security context. |
| 0x80090337 | 密碼編譯系統或總和檢查碼功能不正確，原因是所需的函式無法使用。 |
The crypto system or checksum function is invalid because a required function is unavailable. |
| 0x80090338 | 已經超過票證轉介的最大數目。 |
The number of maximum ticket referrals has been exceeded. |
| 0x80090339 | 本機電腦必須是 Kerberos KDC (網域控制站)，而這一部不是。 |
The local machine must be a Kerberos KDC (domain controller) and it is not. |
| 0x8009033A | 安全性交涉中的另一端需要有嚴格的密碼編譯，但是本機電腦上並不支援。 |
The other end of the security negotiation is requires strong crypto but it is not supported on the local machine. |
| 0x8009033B | KDC 的回覆含有一個以上的主體名稱。 |
The KDC reply contained more than one principal name. |
| 0x8009033C | 需要找到 PA 資料，以便提示該使用哪一種類型，但是沒有找到。 |
Expected to find PA data for a hint of what etype to use, but it was not found. |
| 0x8009033D | 用戶端憑證未包含有效的 UPN，或與登入要求中的用戶端名稱不相符。請連絡您的系統管理員。 |
The client certificate does not contain a valid UPN, or does not match the client name in the logon request. Please contact your administrator. |
| 0x8009033E | 需要智慧卡登入，但是沒有這麼做。 |
Smartcard logon is required and was not used. |
| 0x80090340 | 有不正確的要求傳送給 KDC。 |
An invalid request was sent to the KDC. |
| 0x80090341 | KDC 無法為要求的服務產生轉介。 |
The KDC was unable to generate a referral for the service requested. |
| 0x80090342 | KDC 不支援所要求的加密類型。 |
The encryption type requested is not supported by the KDC. |
| 0x80090343 | 有一個不受支援的預先驗證機制被送給 Kerberos 封裝。 |
An unsupported preauthentication mechanism was presented to the Kerberos package. |
| 0x80090345 | 無法完成所要求的操作。電腦必須受信任才能委派，且目前的使用者帳戶必須設定為允許委派。 |
The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. |
| 0x80090346 | 用戶端所提供的 SSPI 通道連結不正確。 |
Client's supplied SSPI channel bindings were incorrect. |
| 0x80090347 | 所收到的憑證對應到多重帳戶。 |
The received certificate was mapped to multiple accounts. |
| 0x80090348 | SEC_E_NO_KERB_KEY |
SEC_E_NO_KERB_KEY |
| 0x80090349 | 要求的使用方式的憑證不正確。 |
The certificate is not valid for the requested usage. |
| 0x80090350 | 系統無法連絡網域控制站以服務驗證要求。請稍後再試一次。 |
The system cannot contact a domain controller to service the authentication request. Please try again later. |
| 0x80090351 | 用於驗證的智慧卡憑證已撤銷。請連絡您的系統管理員。在事件記錄檔中可能有其他的資訊。 |
The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log. |
| 0x80090352 | 處理用於驗證的智慧卡憑證時偵測到不受信任的憑證授權單位。請連絡您的系統管理員。 |
An untrusted certificate authority was detected while processing the smartcard certificate used for authentication. Please contact your system administrator. |
| 0x80090353 | 無法判斷用於驗證的智慧卡憑證的撤銷狀態。請連絡您的系統管理員。 |
The revocation status of the smartcard certificate used for authentication could not be determined. Please contact your system administrator. |
| 0x80090354 | 用於驗證的智慧卡憑證不受信任。請連絡您的系統管理員。 |
The smartcard certificate used for authentication was not trusted. Please contact your system administrator. |
| 0x80090355 | 用於驗證的智慧卡憑證已到期。請連絡您的系統管理員。 |
The smartcard certificate used for authentication has expired. Please contact your system administrator. |
| 0x80090356 | Kerberos 子系統發生錯誤。用於使用者通訊協定要求的服務被用於不支援使用者服務的網域控制站。 |
The Kerberos subsystem encountered an error. A service for user protocol request was made against a domain controller which does not support service for user. |
| 0x80090357 | 這個伺服器嘗試對伺服器領域外面的目標，做 Kerberos 限制委派的要求。這項要求是不受支援的，並且表示在這個伺服器的允許委派清單有錯誤設定。請連絡您的系統管理員。 |
An attempt was made by this server to make a Kerberos constrained delegation request for a target outside of the server's realm. This is not supported, and indicates a misconfiguration on this server's allowed to delegate to list. Please contact your administrator. |
| 0x80090358 | 無法判斷用於智慧卡驗證的網域控制站憑證的撤銷狀態。在系統事件記錄檔中有更多的有關資訊。請連絡您的系統管理員。 |
The revocation status of the domain controller certificate used for smartcard authentication could not be determined. There is additional information in the system event log. Please contact your system administrator. |
| 0x80090359 | 處理用來驗證的網域控制站憑證時，偵測到不受信任的憑證授權單位。系統事件記錄檔中有相關資訊。請連絡您的系統管理員。 |
An untrusted certificate authority was detected while processing the domain controller certificate used for authentication. There is additional information in the system event log. Please contact your system administrator. |
| 0x8009035A | 用於智慧卡登入的網域控制站憑證已到期。請連絡您的系統管理員並隨附系統事件記錄檔的內容。 |
The domain controller certificate used for smartcard logon has expired. Please contact your system administrator with the contents of your system event log. |
| 0x8009035B | 用於智慧卡登入的網域控制站憑證已被撤銷。請連絡您的系統管理員並隨附系統事件記錄檔的內容。 |
The domain controller certificate used for smartcard logon has been revoked. Please contact your system administrator with the contents of your system event log. |
| 0x8009035D | 傳遞給函數的一或多個參數不正確。 |
One or more of the parameters passed to the function was invalid. |
| 0x8009035E | 用戶端原則不允許認證委派至目標伺服器。 |
Client policy does not allow credential delegation to target server. |
| 0x8009035F | 用戶端原則不允許認證委派至目標伺服器 (當使用僅 NLTM 驗證時)。 |
Client policy does not allow credential delegation to target server with NLTM only authentication. |
| 0x80090361 | 所需的資訊安全內容不存在。 |
The required security context does not exist. |
| 0x80090362 | PKU2U 通訊協定嘗試使用關聯的憑證時發生錯誤。 |
The PKU2U protocol encountered an error while attempting to utilize the associated certificates. |
| 0x80090363 | 無法驗證伺服器電腦的身分識別。 |
The identity of the server computer could not be verified. |
| 0x80090365 | 只允許 https 配置。 |
Only https scheme is allowed. |
| 0x80090367 | 用戶端與伺服器之間沒有通用應用程式通訊協定存在。應用程式通訊協定交涉失敗。 |
No common application protocol exists between the client and the server. Application protocol negotiation failed. |
| 0x80090369 | 無法使用此格式的使用者識別碼登入。請嘗試改為使用您的電子郵件地址。 |
You can't sign in with a user ID in this format. Try using your email address instead. |
| 0x80091001 | 進行訊息的密碼編譯操作時遇到錯誤。 |
An error occurred while performing an operation on a cryptographic message. |
| 0x80091002 | 未知的密碼編譯演算法。 |
Unknown cryptographic algorithm. |
| 0x80091003 | 物件識別元格式錯誤。 |
The object identifier is poorly formatted. |
| 0x80091004 | 密碼編譯訊息類型不正確。 |
Invalid cryptographic message type. |
| 0x80091005 | 密碼編譯訊息編碼不正確。 |
Unexpected cryptographic message encoding. |
| 0x80091006 | 密碼編譯訊息包含的認證屬性不正確。 |
The cryptographic message does not contain an expected authenticated attribute. |
| 0x80091007 | 雜湊值不正確。 |
The hash value is not correct. |
| 0x80091008 | 索引值不正確。 |
The index value is not valid. |
| 0x80091009 | 密碼編譯訊息內容已經被解碼。 |
The content of the cryptographic message has already been decrypted. |
| 0x8009100A | 密碼編譯訊息內容尚未被解碼。 |
The content of the cryptographic message has not been decrypted yet. |
| 0x8009100B | 信件訊息沒有指定收件者。 |
The enveloped-data message does not contain the specified recipient. |
| 0x8009100C | 控制類型不正確。 |
Invalid control type. |
| 0x8009100D | 簽發者或序號不正確。 |
Invalid issuer and/or serial number. |
| 0x8009100E | 找不到原始簽署人。 |
Cannot find the original signer. |
| 0x8009100F | 密碼編譯訊息中沒有包含要求的屬性。 |
The cryptographic message does not contain all of the requested attributes. |
| 0x80091010 | 資料流的密碼編譯訊息還沒準備好要傳回資料。 |
The streamed cryptographic message is not ready to return data. |
| 0x80091011 | 資料流密碼編譯訊息需要更多資料才能完成解碼操作。 |
The streamed cryptographic message requires more data to complete the decode operation. |
| 0x80092001 | 輸出資料的指定長度不足。 |
The length specified for the output data was insufficient. |
| 0x80092002 | 編碼或解碼操作時遇到錯誤。 |
An error occurred during encode or decode operation. |
| 0x80092003 | 讀取或寫入檔案時發生錯誤。 |
An error occurred while reading or writing to a file. |
| 0x80092004 | 找不到物件或內容。 |
Cannot find object or property. |
| 0x80092005 | 物件或內容已經存在。 |
The object or property already exists. |
| 0x80092006 | 未指定存放區或物件的提供者。 |
No provider was specified for the store or object. |
| 0x80092007 | 指定的憑證會自動簽署。 |
The specified certificate is self signed. |
| 0x80092008 | 上一個憑證或 CRL 內容已被刪除。 |
The previous certificate or CRL context was deleted. |
| 0x80092009 | 找不到要求的物件。 |
Cannot find the requested object. |
| 0x8009200A | 憑證沒有私密金鑰內容。 |
The certificate does not have a property that references a private key. |
| 0x8009200B | 找不到用來解密的私密金鑰和憑證。 |
Cannot find the certificate and private key for decryption. |
| 0x8009200D | 可能不是密碼編譯訊息或密碼編譯訊息格式不正確。 |
Not a cryptographic message or the cryptographic message is not formatted correctly. |
| 0x8009200E | 簽章的密碼編譯訊息中沒有給指定的簽署人索引使用的簽署人。 |
The signed cryptographic message does not have a signer for the specified signer index. |
| 0x8009200F | 最後截止期限延長，直到有其他的項目釋放或結束。 |
Final closure is pending until additional frees or closes. |
| 0x80092010 | 憑證已經撤銷。 |
The certificate is revoked. |
| 0x80092011 | 找不到用來驗證撤銷的 Dll 或匯出函數。 |
No Dll or exported function was found to verify revocation. |
| 0x80092012 | 撤銷功能無法檢查憑證的撤銷。 |
The revocation function was unable to check revocation for the certificate. |
| 0x80092013 | 因為撤銷伺服器已離線，無法完成撤銷檢查。 |
The revocation function was unable to check revocation because the revocation server was offline. |
| 0x80092014 | 憑證不在撤銷伺服器資料庫中。 |
The certificate is not in the revocation server's database. |
| 0x80092020 | 字串包含一個非數字的字元。 |
The string contains a non-numeric character. |
| 0x80092021 | 字串包含一個無法列印的字元。 |
The string contains a non-printable character. |
| 0x80092022 | 字串包含一個不在 7 位元 ASCII 字集中的字元。 |
The string contains a character not in the 7 bit ASCII character set. |
| 0x80092023 | 字串包含一個不正確的 X500 名稱屬性的代碼，oid，值或分隔字元。 |
The string contains an invalid X500 name attribute key, oid, value or delimiter. |
| 0x80092024 | CERT_NAME_VALUE 的 dwValueType 不是字元所組成的字串。它很可能是一個 CERT_RDN_ENCODED_BLOB 或 CERT_RDN_OCTET_STRING。 |
The dwValueType for the CERT_NAME_VALUE is not one of the character strings. Most likely it is either a CERT_RDN_ENCODED_BLOB or CERT_RDN_OCTET_STRING. |
| 0x80092025 | Put 操作無法繼續。檔案需要重調大小。不過目前已經有一個簽章。您必須完成完整簽章操作。 |
The Put operation cannot continue. The file needs to be resized. However, there is already a signature present. A complete signing operation must be done. |
| 0x80092026 | 密碼編譯操作失敗，因為有本機安全性選項設定。 |
The cryptographic operation failed due to a local security option setting. |
| 0x80092027 | 找不到 DLL 或匯出函數來驗證主體使用。 |
No DLL or exported function was found to verify subject usage. |
| 0x80092028 | 被呼叫的函數無法進行主體使用檢查。 |
The called function was unable to do a usage check on the subject. |
| 0x80092029 | 因為伺服器離線，被呼叫的函數無法完成使用檢查。 |
Since the server was offline, the called function was unable to complete the usage check. |
| 0x8009202A | 在憑證信任清單 (CTL) 中找不到主體。 |
The subject was not found in a Certificate Trust List (CTL). |
| 0x8009202B | 密碼編譯訊息或憑證信任清單的簽署人都不受信任。 |
None of the signers of the cryptographic message or certificate trust list is trusted. |
| 0x8009202C | 公開金鑰的演算法參數遺失了。 |
The public key's algorithm parameters are missing. |
| 0x8009202D | 無法使用具有所指定名稱的物件定位器基礎結構來定位物件。 |
An object could not be located using the object locator infrastructure with the given name. |
| 0x80093000 | OSS 憑證編碼/解碼的錯誤碼基底請到 asn1code.h 參閱 OSS 執行階段錯誤的定義。OSS 錯誤值是 CRYPT_E_OSS_ERROR 的位移值。 |
OSS Certificate encode/decode error code baseSee asn1code.h for a definition of the OSS runtime errors. The OSS error values are offset by CRYPT_E_OSS_ERROR. |
| 0x80093001 | OSS ASN.1 錯誤: 輸出緩衝區太小。 |
OSS ASN.1 Error: Output Buffer is too small. |
| 0x80093002 | OSS ASN.1 錯誤: 有正負的整數被編碼成無正負的整數。 |
OSS ASN.1 Error: Signed integer is encoded as a unsigned integer. |
| 0x80093003 | OSS ASN.1 錯誤: 不明的 ASN.1 資料型態。 |
OSS ASN.1 Error: Unknown ASN.1 data type. |
| 0x80093004 | OSS ASN.1 錯誤: 輸出緩衝區太小，解碼資料已被截斷。 |
OSS ASN.1 Error: Output buffer is too small, the decoded data has been truncated. |
| 0x80093005 | OSS ASN.1 錯誤: 不正確的資料。 |
OSS ASN.1 Error: Invalid data. |
| 0x80093006 | OSS ASN.1 錯誤: 不正確的引數。 |
OSS ASN.1 Error: Invalid argument. |
| 0x80093007 | OSS ASN.1 錯誤: 編碼/解碼版本不相符。 |
OSS ASN.1 Error: Encode/Decode version mismatch. |
| 0x80093008 | OSS ASN.1 錯誤: 記憶體不足。 |
OSS ASN.1 Error: Out of memory. |
| 0x80093009 | OSS ASN.1 錯誤: 編碼/解碼錯誤。 |
OSS ASN.1 Error: Encode/Decode Error. |
| 0x8009300A | OSS ASN.1 錯誤: 內部錯誤。 |
OSS ASN.1 Error: Internal Error. |
| 0x8009300D | OSS ASN.1 錯誤: 不受未支援的 BER indefinite-length 編碼。 |
OSS ASN.1 Error: Unsupported BER indefinite-length encoding. |
| 0x8009300E | OSS ASN.1 錯誤: 存取違規。 |
OSS ASN.1 Error: Access violation. |
| 0x80093013 | OSS ASN.1 錯誤: 多執行緒衝突。 |
OSS ASN.1 Error: Multi-threading conflict. |
| 0x80093017 | OSS ASN.1 錯誤: 編碼/解碼功能未實作。 |
OSS ASN.1 Error: Encode/Decode function not implemented. |
| 0x80093018 | OSS ASN.1 錯誤: 追蹤檔案錯誤。 |
OSS ASN.1 Error: Trace file error. |
| 0x80093019 | OSS ASN.1 錯誤: 函數功能並未執行。 |
OSS ASN.1 Error: Function not implemented. |
| 0x8009301A | OSS ASN.1 錯誤: 程式連結錯誤。 |
OSS ASN.1 Error: Program link error. |
| 0x8009302D | OSS ASN.1 錯誤: 系統資源錯誤。 |
OSS ASN.1 Error: System resource error. |
| 0x80093100 | ASN1 憑證編碼/解碼的錯誤碼基底。ASN1 錯誤值因 CRYPT_E_ASN1_ERROR 而位移。 |
ASN1 Certificate encode/decode error code base. The ASN1 error values are offset by CRYPT_E_ASN1_ERROR. |
| 0x80093101 | ASN1 內部編碼或解碼錯誤。 |
ASN1 internal encode or decode error. |
| 0x80093102 | ASN1 意外的資料結尾。 |
ASN1 unexpected end of data. |
| 0x80093103 | ASN1 損毀的資料。 |
ASN1 corrupted data. |
| 0x80093104 | ASN1 值太大。 |
ASN1 value too large. |
| 0x80093105 | ASN1 強制違規。 |
ASN1 constraint violated. |
| 0x80093106 | ASN1 記憶體不足。 |
ASN1 out of memory. |
| 0x80093107 | ASN1 緩衝區溢位。 |
ASN1 buffer overflow. |
| 0x80093108 | ASN1 函數不支援這個 PDU。 |
ASN1 function not supported for this PDU. |
| 0x80093109 | ASN1 函式呼叫的引數錯誤。 |
ASN1 bad arguments to function call. |
| 0x8009310A | ASN1 錯誤的真實值。 |
ASN1 bad real value. |
| 0x8009310B | ASN1 遇到錯誤的標記值。 |
ASN1 bad tag value met. |
| 0x8009310C | ASN1 錯誤的選擇值。 |
ASN1 bad choice value. |
| 0x8009310D | ASN1 錯誤的編碼規則。 |
ASN1 bad encoding rule. |
| 0x8009310E | ASN1 錯誤的 unicode (UTF8)。 |
ASN1 bad unicode (UTF8). |
| 0x80093133 | ASN1 錯誤的 PDU 類型。 |
ASN1 bad PDU type. |
| 0x80093134 | ASN1 尚未執行。 |
ASN1 not yet implemented. |
| 0x80093201 | ASN1 略過不明的副檔名。 |
ASN1 skipped unknown extension(s). |
| 0x80093202 | ASN1 預期的資料結尾 |
ASN1 end of data expected |
| 0x80094001 | 所要求的主體名稱無效或過長。 |
The request subject name is invalid or too long. |
| 0x80094002 | 要求不存在。 |
The request does not exist. |
| 0x80094003 | 要求的目前狀態不允許這個操作。 |
The request's current status does not allow this operation. |
| 0x80094004 | 所要求的內容值是空的。 |
The requested property value is empty. |
| 0x80094005 | 憑證授權單位的憑證包含不正確的資料。 |
The certification authority's certificate contains invalid data. |
| 0x80094006 | 因為資料庫還原操作，憑證服務已經暫停。 |
Certificate service has been suspended for a database restore operation. |
| 0x80094007 | 此憑證包含經過鎖碼的長度，可能與舊的軟體不相容。 |
The certificate contains an encoded length that is potentially incompatible with older enrollment software. |
| 0x80094008 | 拒絕操作。使用者擁有多重指派的角色，而憑證授權單位是設定為強制角色分隔。 |
The operation is denied. The user has multiple roles assigned and the certification authority is configured to enforce role separation. |
| 0x80094009 | 拒絕操作。只能交由允許為目前要求者管理憑證的憑證管理員來執行。 |
The operation is denied. It can only be performed by a certificate manager that is allowed to manage certificates for the current requester. |
| 0x8009400A | 無法保存私密金鑰。憑證授權單位並未設定為金鑰保存之用。 |
Cannot archive private key. The certification authority is not configured for key archival. |
| 0x8009400B | 無法保存私密金鑰。憑證授權單位無法確認一個或以上的金鑰修復憑證。 |
Cannot archive private key. The certification authority could not verify one or more key recovery certificates. |
| 0x8009400C | 要求的格式不正確。已加密的私密金鑰必須是最外層簽章中具有未驗證的屬性。 |
The request is incorrectly formatted. The encrypted private key must be in an unauthenticated attribute in an outermost signature. |
| 0x8009400D | 至少一個安全性主體必須擁有管理這個 CA 的權限。 |
At least one security principal must have the permission to manage this CA. |
| 0x8009400E | 這個要求含有不正確的更新憑證屬性。 |
The request contains an invalid renewal certificate attribute. |
| 0x8009400F | 嘗試開啟憑證授權單位資料庫工作階段，但是已經有太多個使用中工作階段了。伺服器可能需要設定成允許額外的工作階段。 |
An attempt was made to open a Certification Authority database session, but there are already too many active sessions. The server may need to be configured to allow additional sessions. |
| 0x80094010 | 記憶體參照導致資料調整錯誤。 |
A memory reference caused a data alignment fault. |
| 0x80094011 | 這個憑證授權單位的權限不允許目前的使用者註冊憑證。 |
The permissions on this certification authority do not allow the current user to enroll for certificates. |
| 0x80094012 | 憑證範本上的權限不允許目前的使用者註冊這類型的憑證。 |
The permissions on the certificate template do not allow the current user to enroll for this type of certificate. |
| 0x80094013 | 聯絡的網域控制站不支援簽署的 LDAP 傳輸。請更新網域控制站，或設定憑證服務於 Active Directory 存取使用 SSL。 |
The contacted domain controller cannot support signed LDAP traffic. Update the domain controller or configure Certificate Services to use SSL for Active Directory access. |
| 0x80094014 | 憑證管理員或 CA 系統管理員拒絕要求。 |
The request was denied by a certificate manager or CA administrator. |
| 0x80094015 | 找不到註冊原則伺服器。 |
An enrollment policy server cannot be located. |
| 0x80094016 | 簽章演算法或公開金鑰長度與系統要求的最低強度不符。 |
A signature algorithm or public key length does not meet the system's minimum required strength. |
| 0x80094017 | 無法建立證明金鑰。此電腦或密碼編譯提供者可能不符合支援金鑰證明的硬體需求。 |
Failed to create an attested key. This computer or the cryptographic provider may not meet the hardware requirements to support key attestation. |
| 0x80094018 | 未指定加密憑證。 |
No encryption certificate was specified. |
| 0x80094800 | 這個 CA 不支援要求的憑證範本。 |
The requested certificate template is not supported by this CA. |
| 0x80094801 | 要求中並未包含憑證範本資訊。 |
The request contains no certificate template information. |
| 0x80094802 | 這個要求含有衝突的範本資訊。 |
The request contains conflicting template information. |
| 0x80094803 | 這個要求遺失了必需的主體交替名稱延伸。 |
The request is missing a required Subject Alternate name extension. |
| 0x80094804 | 這個要求遺失了伺服器保存所必需的私密金鑰。 |
The request is missing a required private key for archival by the server. |
| 0x80094805 | 這個要求遺失了必需的 SMIME 功能延伸。 |
The request is missing a required SMIME capabilities extension. |
| 0x80094806 | 要求是代非呼叫者的主體所提出。憑證範本必須設定為要求至少一個簽章來授權要求。 |
The request was made on behalf of a subject other than the caller. The certificate template must be configured to require at least one signature to authorize the request. |
| 0x80094807 | 要求範本的版本比受支援範本的版本還新。 |
The request template version is newer than the supported template version. |
| 0x80094808 | 範本遺失了必需的簽章原則屬性。 |
The template is missing a required signature policy attribute. |
| 0x80094809 | 要求遺失了必需的簽章原則資訊。 |
The request is missing required signature policy information. |
| 0x8009480A | 要求遺失了一個或以上的必需簽章。 |
The request is missing one or more required signatures. |
| 0x8009480B | 有一個或以上的簽章未包含所必需的應用程式或發行原則。要求遺失了一個或以上必須的正確簽章。 |
One or more signatures did not include the required application or issuance policies. The request is missing one or more required valid signatures. |
| 0x8009480C | 要求遺失了一個或以上必需的簽章發行原則。 |
The request is missing one or more required signature issuance policies. |
| 0x8009480D | UPN 無法使用，因此無法加入至主體交替名稱。 |
The UPN is unavailable and cannot be added to the Subject Alternate name. |
| 0x8009480E | Active Directory GUID 無法使用，因此無法加入至主體交替名稱。 |
The Active Directory GUID is unavailable and cannot be added to the Subject Alternate name. |
| 0x8009480F | DNS 名稱無法使用，因此無法加入至主體交替名稱。 |
The DNS name is unavailable and cannot be added to the Subject Alternate name. |
| 0x80094810 | 要求包括了伺服器保存的私密金鑰，但是金鑰保存尚未在指定的憑證範本中啟用。 |
The request includes a private key for archival by the server, but key archival is not enabled for the specified certificate template. |
| 0x80094811 | 公開金鑰沒有達到指定的憑證範本所必需的最小長度。 |
The public key does not meet the minimum size required by the specified certificate template. |
| 0x80094812 | EMail 名稱無法使用且無法加入到主旨或其他主旨名稱。 |
The EMail name is unavailable and cannot be added to the Subject or Subject Alternate name. |
| 0x80094813 | 找不到在這個憑證授權單位上啟用的一或多個憑證範本。 |
One or more certificate templates to be enabled on this certification authority could not be found. |
| 0x80094814 | 憑證範本更新間隔不能長於憑證有效期限。範本應該重新設定或更新 CA 憑證。 |
The certificate template renewal period is longer than the certificate validity period. The template should be reconfigured or the CA certificate renewed. |
| 0x80094815 | 憑證範本需要太多 RA 簽章。只允許一個 RA 簽章。 |
The certificate template requires too many RA signatures. Only one RA signature is allowed. |
| 0x80094816 | 憑證範本必須使用相同的公開金鑰更新，但要求使用了不同的公開金鑰。 |
The certificate template requires renewal with the same public key, but the request uses a different public key. |
| 0x80094817 | 憑證授權單位無法解譯或驗證在要求中提供的簽署金鑰資訊，或該資訊不一致。 |
The certification authority cannot interpret or verify the endorsement key information supplied in the request, or the information is inconsistent. |
| 0x80094818 | 憑證授權單位無法驗證「證明識別金鑰識別碼繫結」。 |
The certification authority cannot validate the Attestation Identity Key Id Binding. |
| 0x80094819 | 憑證授權單位無法驗證私密金鑰證明資料。 |
The certification authority cannot validate the private key attestation data. |
| 0x8009481A | 要求未如憑證範本所定義支援私密金鑰證明。 |
The request does not support private key attestation as defined in the certificate template. |
| 0x8009481B | 要求公開金鑰與私密金鑰證明資料不一致。 |
The request public key is not consistent with the private key attestation data. |
| 0x8009481C | 無法驗證私密金鑰證明挑戰，因為加密憑證已過期，或憑證或金鑰無法使用。 |
The private key attestation challenge cannot be validated because the encryption certificate has expired, or the certificate or key is unavailable. |
| 0x8009481D | 無法驗證證明回應。證明回應是未預期的或不正確。 |
The attestation response could not be validated. It is either unexpected or incorrect. |
| 0x8009481E | 未在要求屬性中偵測到有效的「要求識別碼」，或送出的「要求識別碼」無效。 |
A valid Request ID was not detected in the request attributes, or an invalid one was submitted. |
| 0x80095000 | 這個金鑰不能匯出。 |
The key is not exportable. |
| 0x80095001 | 您必須新增根 CA 憑證到您的本機存放區。 |
You cannot add the root CA certificate into your local store. |
| 0x80095002 | 在回應中找不到金鑰保存雜湊屬性。 |
The key archival hash attribute was not found in the response. |
| 0x80095003 | 在回應中找到意外的金鑰保存雜湊屬性。 |
An unexpected key archival hash attribute was found in the response. |
| 0x80095004 | 要求和回應中的金鑰保存雜湊不相符。 |
There is a key archival hash mismatch between the request and the response. |
| 0x80095005 | 簽署憑證不能包括 SMIME 擴充。 |
Signing certificate cannot include SMIME extension. |
| 0x80096001 | 確認信任時發生了系統層次的錯誤。 |
A system-level error occurred while verifying trust. |
| 0x80096002 | 訊息簽署人的憑證無效或找不到此憑證。 |
The certificate for the signer of the message is invalid or not found. |
| 0x80096003 | 其中一個副署無效。 |
One of the counter signatures was invalid. |
| 0x80096004 | 憑證的簽章無法驗證。 |
The signature of the certificate cannot be verified. |
| 0x80096005 | 時間戳記簽章及/或憑證無法驗證或格式不正確。 |
The timestamp signature and/or certificate could not be verified or is malformed. |
| 0x80096010 | 物件的數位簽章並未驗證。 |
The digital signature of the object did not verify. |
| 0x80096011 | 物件的數位簽章格式錯誤。如需技術詳細資料，請參閱安全布告欄 MS13-098。 |
The digital signature of the object is malformed. For technical detail, see security bulletin MS13-098. |
| 0x80096019 | 看不見憑證的基本限制延伸。 |
A certificate's basic constraint extension has not been observed. |
| 0x8009601E | 憑證不符合或不包含 Authenticode(tm) financial extension。 |
The certificate does not meet or contain the Authenticode(tm) financial extensions. |
| 0x80097001 | 嘗試引用正確範圍外的檔案。 |
Tried to reference a part of the file outside the proper range. |
| 0x80097002 | 無法從檔案中抓取物件。 |
Could not retrieve an object from the file. |
| 0x80097003 | 無法從檔案中找到標題表格。 |
Could not find the head table in the file. |
| 0x80097004 | 標題表格中的幻數不正確。 |
The magic number in the head table is incorrect. |
| 0x80097005 | 表格位移值不正確。 |
The offset table has incorrect values. |
| 0x80097006 | 重複表格標記或標記未按照字母順序。 |
Duplicate table tags or tags out of alphabetical order. |
| 0x80097007 | 表格無法在長字元界線啟動。 |
A table does not start on a long word boundary. |
| 0x80097008 | 第一個表格未出現在表頭資訊後面。 |
First table does not appear after header information. |
| 0x80097009 | 二或三個表格重疊。 |
Two or more tables overlap. |
| 0x8009700A | 表格間有太多 pad 位元組，或 pad 位元組不是 0。 |
Too many pad bytes between tables or pad bytes are not 0. |
| 0x8009700B | 檔案太小無法包含上個表格。 |
File is too small to contain the last table. |
| 0x8009700C | 表格總和檢查碼不正確。 |
A table checksum is incorrect. |
| 0x8009700D | 檔案總和檢查碼不正確。 |
The file checksum is incorrect. |
| 0x80097010 | 這簽章並無原則所需的正確屬性。 |
The signature does not have the correct attributes for the policy. |
| 0x80097011 | 檔案沒通過提示檢查。 |
The file did not pass the hints check. |
| 0x80097012 | 這檔案不是 OpenType 檔案。 |
The file is not an OpenType file. |
| 0x80097013 | 檔案操作失敗 (開啟、對應、讀取、寫入)。 |
Failed on a file operation (open, map, read, write). |
| 0x80097014 | 呼叫 CryptoAPI 函式失敗。 |
A call to a CryptoAPI function failed. |
| 0x80097015 | 檔案內有錯誤的版本號碼。 |
There is a bad version number in the file. |
| 0x80097016 | DSIG 表格的結構不正確。 |
The structure of the DSIG table is incorrect. |
| 0x80097017 | 部分常數表格中有一個檢查失敗。 |
A check failed in a partially constant table. |
| 0x80097018 | 某種結構錯誤。 |
Some kind of structural error. |
| 0x80097019 | 要求的認證需要確認。 |
The requested credential requires confirmation. |
| 0x800B0001 | 不明的信任提供者。 |
Unknown trust provider. |
| 0x800B0002 | 所指定的信任提供者，不支援此信任驗證動作。 |
The trust verification action specified is not supported by the specified trust provider. |
| 0x800B0003 | 所指定的信任提供者不支援或不認得指定給此主體的表單。 |
The form specified for the subject is not one supported or known by the specified trust provider. |
| 0x800B0004 | 所指定的動作不信任此主體。 |
The subject is not trusted for the specified action. |
| 0x800B0005 | ASN.1 編碼處理中有問題，因此發生錯誤。 |
Error due to problem in ASN.1 encoding process. |
| 0x800B0006 | ASN.1 解碼處理中有問題，因此發生錯誤。 |
Error due to problem in ASN.1 decoding process. |
| 0x800B0007 | 讀取或寫入屬性正確的副檔名，反之亦然。 |
Reading / writing Extensions where Attributes are appropriate, and vice versa. |
| 0x800B0008 | 未指定的密碼編譯失敗。 |
Unspecified cryptographic failure. |
| 0x800B0009 | 無法決定資料的大小。 |
The size of the data could not be determined. |
| 0x800B000A | 無法決定大小不明確之資料大小。 |
The size of the indefinite-sized data could not be determined. |
| 0x800B000B | 此物件不能讀取與寫入可自行調整大小的資料。 |
This object does not read and write self-sizing data. |
| 0x800B0100 | 主體中目前沒有任何簽章。 |
No signature was present in the subject. |
| 0x800B0101 | 與目前的系統時鐘或簽署檔案的時間戳記核對時，所需的憑證不在有效日期內。 |
A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. |
| 0x800B0102 | 憑證鏈結的有效期間未正確進行巢狀處理。 |
The validity periods of the certification chain do not nest correctly. |
| 0x800B0103 | 只能做為終端實體的憑證，被做為 CA 憑證，反之亦然。 |
A certificate that can only be used as an end-entity is being used as a CA or vice versa. |
| 0x800B0104 | 已違反憑證鏈結中的路徑長度限制。 |
A path length constraint in the certification chain has been violated. |
| 0x800B0105 | 憑證中包含標示為 '關鍵項目' 的不明副檔名。 |
A certificate contains an unknown extension that is marked 'critical'. |
| 0x800B0106 | 憑證使用的方式與 CA 指定的不符合。 |
A certificate being used for a purpose other than the ones specified by its CA. |
| 0x800B0107 | 事實上指定憑證的父系並未簽發這項子憑證。 |
A parent of a given certificate in fact did not issue that child certificate. |
| 0x800B0108 | 憑證遺失，或某個重要欄位的值是空的，如主體或簽發者名稱。 |
A certificate is missing or has an empty value for an important field, such as a subject or issuer name. |
| 0x800B0109 | 憑證鏈結已處理，但憑證鏈結在根憑證時被終止，因為憑證不受信任提供者信任。 |
A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. |
| 0x800B010A | 憑證鏈結無法建立於受信任的根授權。 |
A certificate chain could not be built to a trusted root authority. |
| 0x800B010B | 一般性的信任失敗。 |
Generic trust failure. |
| 0x800B010C | 憑證已被簽發者宣告撤銷。 |
A certificate was explicitly revoked by its issuer. |
| 0x800B010D | 以測試根目錄結尾的憑證路徑不受目前原則設定值信任。 |
The certification path terminates with the test root which is not trusted with the current policy settings. |
| 0x800B010E | 撤銷處理程序無法繼續 - 憑證無法被檢查。 |
The revocation process could not continue - the certificate(s) could not be checked. |
| 0x800B010F | 憑證的 CN 名稱不符合傳遞值。 |
The certificate's CN name does not match the passed value. |
| 0x800B0111 | 這個憑證被使用者明確標示為不受信任憑證。 |
The certificate was explicitly marked as untrusted by the user. |
| 0x800B0112 | 憑證鏈結處理正確，但其中一個 CA 憑證不受原則提供者信任。 |
A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider. |
| 0x800B0113 | 憑證中有不正確的原則。 |
The certificate has invalid policy. |
| 0x800B0114 | 憑證中有不正確的名稱。該名稱未包括在已許可的清單中、或是已經明確排除在外。 |
The certificate has an invalid name. The name is not included in the permitted list or is explicitly excluded. |
| 0x800C0002 | URL 無效。 |
The URL is invalid. |
| 0x800C0003 | 未建立網際網路工作階段。 |
No Internet session has been established. |
| 0x800C0004 | 無法連線到目標伺服器。 |
Unable to connect to the target server. |
| 0x800C0005 | 系統找不到指定的資源。 |
The system cannot locate the resource specified. |
| 0x800C0006 | 系統找不到指定的物件。 |
The system cannot locate the object specified. |
| 0x800C0007 | 所要求的資源沒有可用的資料。 |
No data is available for the requested resource. |
| 0x800C0008 | 下載指定的資源失敗。 |
The download of the specified resource has failed. |
| 0x800C0009 | 存取這個資源需要驗證。 |
Authentication is required to access this resource. |
| 0x800C000A | 伺服器無法識別所提供的 mime 類型。 |
The server could not recognize the provided mime type. |
| 0x800C000B | 作業等候逾時。 |
The operation was timed out. |
| 0x800C000C | 伺服器無法識別要求或要求無效。 |
The server did not understand the request, or the request was invalid. |
| 0x800C000D | 無法識別指定的通訊協定。 |
The specified protocol is unknown. |
| 0x800C000E | 發生安全性問題。 |
A security problem occurred. |
| 0x800C000F | 系統無法載入必要的資料。 |
The system could not load the persisted data. |
| 0x800C0010 | 無法將物件具現化。 |
Unable to instantiate the object. |
| 0x800C0014 | 發生重新導向問題。 |
A redirection problem occurred. |
| 0x800C0015 | 要求的資源為目錄，而非檔案。 |
The requested resource is a directory, not a file. |
| 0x800C0019 | 存取此資源所需的安全性憑證無效。 |
Security certificate required to access this resource is invalid. |
| 0x800F0000 | 在 INF 中的區段開頭之前遇到非空白行。 |
A non-empty line was encountered in the INF before the start of a section. |
| 0x800F0001 | 在 INF 中的區段名稱標記並未完成，或是它自己不存在行數中。 |
A section name marker in the INF is not complete, or does not exist on a line by itself. |
| 0x800F0002 | 在 INF 區段中遇到超過最大長度的區段名稱。 |
An INF section was encountered whose name exceeds the maximum section name length. |
| 0x800F0003 | INF 語法不正確。 |
The syntax of the INF is invalid. |
| 0x800F0100 | INF 樣式與要求的樣式不同。 |
The style of the INF is different than what was requested. |
| 0x800F0101 | 在 INF 中找不到必需的區段。 |
The required section was not found in the INF. |
| 0x800F0102 | 在 INF 中找不到必需的行。 |
The required line was not found in the INF. |
| 0x800F0103 | 尚未對受安裝這個檔案佇列所影響的檔案做解除安裝備份。 |
The files affected by the installation of this file queue have not been backed up for uninstall. |
| 0x800F0200 | INF 或裝置資訊設定或元素沒有相關聯的安裝類別。 |
The INF or the device information set or element does not have an associated install class. |
| 0x800F0201 | INF、裝置資訊設定或元素不符合指定的安裝類別。 |
The INF or the device information set or element does not match the specified install class. |
| 0x800F0202 | 找到現存的裝置，它是一個用手動安裝的重複裝置。 |
An existing device was found that is a duplicate of the device being manually installed. |
| 0x800F0203 | 沒有為裝置資訊設定或元素選取驅動程式。 |
There is no driver selected for the device information set or element. |
| 0x800F0204 | 要求的裝置登錄機碼不存在。 |
The requested device registry key does not exist. |
| 0x800F0205 | 裝置例項名稱不正確。 |
The device instance name is invalid. |
| 0x800F0206 | 安裝類別不存在或不正確。 |
The install class is not present or is invalid. |
| 0x800F0207 | 無法建立裝置例項，因為它已經存在。 |
The device instance cannot be created because it already exists. |
| 0x800F0208 | 操作無法在尚未登錄的裝置資訊元素上執行。 |
The operation cannot be performed on a device information element that has not been registered. |
| 0x800F0209 | 裝置內容碼不正確。 |
The device property code is invalid. |
| 0x800F020A | 用來建立驅動程式清單中的 INF 不存在。 |
The INF from which a driver list is to be built does not exist. |
| 0x800F020B | 裝置例項不存在於硬體樹狀目錄中。 |
The device instance does not exist in the hardware tree. |
| 0x800F020C | 無法載入代表這個安裝類別的圖示。 |
The icon representing this install class cannot be loaded. |
| 0x800F020D | 類別安裝程式登錄項目不正確。 |
The class installer registry entry is invalid. |
| 0x800F020E | 類別安裝程式已經指出應該為這個安裝要求執行預設動作。 |
The class installer has indicated that the default action should be performed for this installation request. |
| 0x800F020F | 操作不需要任何檔案複製。 |
The operation does not require any files to be copied. |
| 0x800F0210 | 指定的硬體設定檔不存在。 |
The specified hardware profile does not exist. |
| 0x800F0211 | 目前並未替這個裝置資訊組選取裝置資訊元素。 |
There is no device information element currently selected for this device information set. |
| 0x800F0212 | 操作無法執行，因為裝置資訊組已被鎖定。 |
The operation cannot be performed because the device information set is locked. |
| 0x800F0213 | 操作無法執行，因為裝置資訊元素已被鎖定。 |
The operation cannot be performed because the device information element is locked. |
| 0x800F0214 | 指定的路徑未包含可用的裝置 INF。 |
The specified path does not contain any applicable device INFs. |
| 0x800F0215 | 並未替裝置資訊組或元素設定類別安裝程式參數。 |
No class installer parameters have been set for the device information set or element. |
| 0x800F0216 | 操作無法執行，因為檔案佇列已被鎖定。 |
The operation cannot be performed because the file queue is locked. |
| 0x800F0217 | 在這個 INF 中有一個服務安裝區段不正確。 |
A service installation section in this INF is invalid. |
| 0x800F0218 | 這個裝置資訊元素沒有類別驅動程式清單。 |
There is no class driver list for the device information element. |
| 0x800F0219 | 安裝失敗，因為沒有替裝置例項指定一個函數驅動程式。 |
The installation failed because a function driver was not specified for this device instance. |
| 0x800F021A | 目前沒有預設介面裝置指派給這個介面類別。 |
There is presently no default device interface designated for this interface class. |
| 0x800F021B | 操作無法執行，因為裝置介面目前在使用中。 |
The operation cannot be performed because the device interface is currently active. |
| 0x800F021C | 操作無法執行，因為裝置介面已經從系統上移除。 |
The operation cannot be performed because the device interface has been removed from the system. |
| 0x800F021D | 這個 INF 中有一個介面安裝區段不正確。 |
An interface installation section in this INF is invalid. |
| 0x800F021E | 這個介面類別不存在系統中。 |
This interface class does not exist in the system. |
| 0x800F021F | 支援這個介面裝置的參照字串不正確。 |
The reference string supplied for this interface device is invalid. |
| 0x800F0220 | 指定的電腦名稱不符合 UNC 命名協定。 |
The specified machine name does not conform to UNC naming conventions. |
| 0x800F0221 | 發生一般遠端通訊錯誤。 |
A general remote communication error occurred. |
| 0x800F0222 | 選取用來進行遠端通訊的電腦目前無法使用。 |
The machine selected for remote communication is not available at this time. |
| 0x800F0223 | 隨插即用服務在遠端電腦上無法使用。 |
The Plug and Play service is not available on the remote machine. |
| 0x800F0224 | 內容頁提供者登錄項目不正確。 |
The property page provider registry entry is invalid. |
| 0x800F0225 | 要求的裝置介面目前不存在系統上。 |
The requested device interface is not present in the system. |
| 0x800F0226 | 裝置輔助安裝程式在安裝完成後還有額外工作要執行。 |
The device's co-installer has additional work to perform after installation is complete. |
| 0x800F0227 | 裝置輔助安裝程式不正確。 |
The device's co-installer is invalid. |
| 0x800F0228 | 這個裝置沒有相容驅動程式。 |
There are no compatible drivers for this device. |
| 0x800F0229 | 沒有代表這個裝置或裝置類型的圖示。 |
There is no icon that represents this device or device type. |
| 0x800F022A | 這個 INF 中有一個指定的邏輯設定不正確。 |
A logical configuration specified in this INF is invalid. |
| 0x800F022B | 類別安裝程式已拒絕安裝或升級這個裝置的要求。 |
The class installer has denied the request to install or upgrade this device. |
| 0x800F022C | 這個裝置的某個已安裝的篩選器驅動程式不正確。 |
One of the filter drivers installed for this device is invalid. |
| 0x800F022D | 為這個裝置所選取的驅動程式不支援此版本 Windows。 |
The driver selected for this device does not support this version of Windows. |
| 0x800F022E | 為這個裝置所選取的驅動程式不支援 Windows。 |
The driver selected for this device does not support Windows. |
| 0x800F022F | 其他廠商的 INF 並未包含數位簽章資訊。 |
The third-party INF does not contain digital signature information. |
| 0x800F0230 | 使用裝置安裝檔佇列來進行其他平台的數位簽章驗證，這是不正確的嘗試。 |
An invalid attempt was made to use a device installation file queue for verification of digital signatures relative to other platforms. |
| 0x800F0231 | 裝置無法停用。 |
The device cannot be disabled. |
| 0x800F0232 | 無法動態移除這個裝置。 |
The device could not be dynamically removed. |
| 0x800F0233 | 無法複製到指定的目標。 |
Cannot copy to specified target. |
| 0x800F0234 | 驅動程式並不預期在這個平台上工作。 |
Driver is not intended for this platform. |
| 0x800F0235 | 操作不允許在 WOW64 進行。 |
Operation not allowed in WOW64. |
| 0x800F0236 | 涉及未簽署檔案複製的操作已經被還原了，如此便能夠設定系統還原點。 |
The operation involving unsigned file copying was rolled back, so that a system restore point could be set. |
| 0x800F0237 | 以不適當的方式複製 INF 到 Windows INF 目錄。 |
An INF was copied into the Windows INF directory in an improper manner. |
| 0x800F0238 | 安全性設定編輯器 (SCE) API 已在這個內嵌產品上停用。 |
The Security Configuration Editor (SCE) APIs have been disabled on this Embedded product. |
| 0x800F0239 | 發生不明的例外狀況。 |
An unknown exception was encountered. |
| 0x800F023A | 存取隨插即用登錄資料庫時發生問題。 |
A problem was encountered when accessing the Plug and Play registry database. |
| 0x800F023B | 要求的操作在遠端電腦上不支援。 |
The requested operation is not supported for a remote machine. |
| 0x800F023C | 指定的檔案不是一個安裝的 OEM INF。 |
The specified file is not an installed OEM INF. |
| 0x800F023D | 一或多個目前安裝的裝置是使用指定的 INF 安裝。 |
One or more devices are presently installed using the specified INF. |
| 0x800F023E | 要求的裝置安裝操作已太舊作廢。 |
The requested device install operation is obsolete. |
| 0x800F023F | 無法確認檔案，因為它沒有經由 Authenticode(tm) 簽章的相關聯類別目錄。 |
A file could not be verified because it does not have an associated catalog signed via Authenticode(tm). |
| 0x800F0240 | Authenticode(tm) 簽章確認不支援所指定的 INF。 |
Authenticode(tm) signature verification is not supported for the specified INF. |
| 0x800F0241 | INF 是以來自受信任發行者的 Authenticode(tm) 類別目錄所簽章。 |
The INF was signed with an Authenticode(tm) catalog from a trusted publisher. |
| 0x800F0242 | Authenticode(tm) 所簽章類別目錄的發行者尚未被建立為受信任。 |
The publisher of an Authenticode(tm) signed catalog has not yet been established as trusted. |
| 0x800F0243 | Authenticode(tm) 所簽章類別目錄的發行者並未被建立為受信任。 |
The publisher of an Authenticode(tm) signed catalog was not established as trusted. |
| 0x800F0244 | 軟體已經在不同版本 Windows 上測試過符合 Windows Logo 的要求，可能與這個版本不相容。 |
The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version. |
| 0x800F0245 | 檔案可能只能以經由 Authenticode(tm) 簽章的類別目錄來確認。 |
The file may only be validated by a catalog signed via Authenticode(tm). |
| 0x800F0246 | 此裝置的其中一個安裝程式目前無法執行安裝。 |
One of the installers for this device cannot perform the installation at this time. |
| 0x800F0247 | 嘗試將驅動程式新增至存放區時發生問題。 |
A problem was encountered while attempting to add the driver to the store. |
| 0x800F0248 | 系統原則禁止安裝此裝置。請連絡您的系統管理員。 |
The installation of this device is forbidden by system policy. Contact your system administrator. |
| 0x800F0249 | 系統原則禁止安裝此驅動程式。請連絡您的系統管理員。 |
The installation of this driver is forbidden by system policy. Contact your system administrator. |
| 0x800F024A | 指定的 INF 類型對於此操作而言不正確。 |
The specified INF is the wrong type for this operation. |
| 0x800F024B | 指定的類別目錄檔案中沒有該檔案的雜湊。該檔案可能已損毀或被竄改。 |
The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering. |
| 0x800F024C | 嘗試從存放區刪除驅動程式時發生問題。 |
A problem was encountered while attempting to delete the driver from the store. |
| 0x800F0300 | 發生了無法恢復的堆疊溢位。 |
An unrecoverable stack overflow was encountered. |
| 0x800F1000 | 並未偵測出安裝元件。 |
No installed components were detected. |
| 0x80100002 | 已根據 SCardCancel 要求取消動作。 |
The action was cancelled by an SCardCancel request. |
| 0x80100004 | 無法正確解譯所提供的一些參數。 |
One or more of the supplied parameters could not be properly interpreted. |
| 0x80100005 | 登錄中的啟動資訊遺失或不正確。 |
Registry startup information is missing or invalid. |
| 0x80100006 | 記憶體不足，無法完成這個命令。 |
Not enough memory available to complete this command. |
| 0x80100007 | 內部一致性計時器已到期。 |
An internal consistency timer has expired. |
| 0x80100008 | 接收傳回資料的緩衝區太小，無法接收傳回的資料。 |
The data buffer to receive returned data is too small for the returned data. |
| 0x80100009 | 指定的讀卡機名稱無法辨識。 |
The specified reader name is not recognized. |
| 0x8010000A | 已經超過使用者指定的逾時值。 |
The user-specified timeout value has expired. |
| 0x8010000B | 無法存取智慧卡，因為正在處理其他的連線。 |
The smart card cannot be accessed because of other connections outstanding. |
| 0x8010000C | 此操作需要智慧卡，但目前裝置中沒有智慧卡。 |
The operation requires a smart card, but no smart card is currently in the device. |
| 0x8010000D | 指定的智慧卡名稱無法辨識。 |
The specified smart card name is not recognized. |
| 0x8010000E | 系統無法為要求的操作配置媒體。 |
The system could not dispose of the media in the requested manner. |
| 0x8010000F | 要求的通訊協定與目前智慧卡使用的通訊協定不相容。 |
The requested protocols are incompatible with the protocol currently in use with the smart card. |
| 0x80100010 | 讀卡機或智慧卡還未就緒，無法接受命令。 |
The reader or smart card is not ready to accept commands. |
| 0x80100012 | 系統已經將動作取消，可能是系統已關機或登出。 |
The action was cancelled by the system, presumably to log off or shut down. |
| 0x80100013 | 偵測出內部通訊錯誤。 |
An internal communications error has been detected. |
| 0x80100014 | 偵測出內部錯誤，但來源不明。 |
An internal error has been detected, but the source is unknown. |
| 0x80100015 | 從登錄中取得的 ATR 不是正確的 ATR 字串。 |
An ATR obtained from the registry is not a valid ATR string. |
| 0x80100016 | 嘗試結束不存在的交易。 |
An attempt was made to end a non-existent transaction. |
| 0x80100017 | 指定的讀卡機目前無法使用。 |
The specified reader is not currently available for use. |
| 0x80100018 | 操作被中止以允許伺服器應用程式結束。 |
The operation has been aborted to allow the server application to exit. |
| 0x80100019 | PCI 接收緩衝區太小。 |
The PCI Receive buffer was too small. |
| 0x8010001A | 讀卡機驅動程式不符合支援條件。 |
The reader driver does not meet minimal requirements for support. |
| 0x8010001B | 讀卡機驅動程式並未產生唯一性的讀卡機名稱。 |
The reader driver did not produce a unique reader name. |
| 0x8010001C | 智慧卡不符合支援條件。 |
The smart card does not meet minimal requirements for support. |
| 0x8010001D | 智慧卡資源管理員未執行。 |
The Smart Card Resource Manager is not running. |
| 0x8010001E | 智慧卡資源管理員已關閉。 |
The Smart Card Resource Manager has shut down. |
| 0x8010001F | 發生意外的智慧卡錯誤。 |
An unexpected card error has occurred. |
| 0x80100020 | 找不到智慧卡的主要提供者。 |
No Primary Provider can be found for the smart card. |
| 0x80100021 | 不支援要求的物件建立順序。 |
The requested order of object creation is not supported. |
| 0x80100022 | 這個智慧卡不支援要求的功能。 |
This smart card does not support the requested feature. |
| 0x80100023 | 智慧卡中沒有這個識別目錄。 |
The identified directory does not exist in the smart card. |
| 0x80100024 | 智慧卡中沒有這個識別檔案。 |
The identified file does not exist in the smart card. |
| 0x80100025 | 提供的路徑不能代表智慧卡目錄。 |
The supplied path does not represent a smart card directory. |
| 0x80100026 | 提供的路徑不能代表智慧卡檔案。 |
The supplied path does not represent a smart card file. |
| 0x80100027 | 存取這個檔案被拒。 |
Access is denied to this file. |
| 0x80100028 | 智慧卡沒有足夠的記憶體可儲存資訊。 |
The smart card does not have enough memory to store the information. |
| 0x80100029 | 嘗試設定智慧卡檔案物件指標時發生錯誤。 |
There was an error trying to set the smart card file object pointer. |
| 0x8010002A | 提供的 PIN 不正確。 |
The supplied PIN is incorrect. |
| 0x8010002B | 從分層元件傳回一個無法識別的錯誤碼。 |
An unrecognized error code was returned from a layered component. |
| 0x8010002C | 要求的憑證不存在。 |
The requested certificate does not exist. |
| 0x8010002D | 無法取得要求的憑證。 |
The requested certificate could not be obtained. |
| 0x8010002E | 找不到智慧卡讀卡機。 |
Cannot find a smart card reader. |
| 0x8010002F | 偵測出與智慧卡的通訊有錯誤。請重試操作。 |
A communications error with the smart card has been detected. Retry the operation. |
| 0x80100030 | 智慧卡上沒有所要求的金鑰容器。 |
The requested key container does not exist on the smart card. |
| 0x80100031 | 智慧卡資源管理員太忙碌，無法完成此操作。 |
The Smart Card Resource Manager is too busy to complete this operation. |
| 0x80100032 | 智慧卡 PIN 快取已到期。 |
The smart card PIN cache has expired. |
| 0x80100033 | 無法快取智慧卡 PIN。 |
The smart card PIN cannot be cached. |
| 0x80100034 | 智慧卡是唯讀的，無法寫入。 |
The smart card is read only and cannot be written to. |
| 0x80100065 | 讀卡機無法與智慧卡通訊，因為 ATR 設定衝突。 |
The reader cannot communicate with the smart card, due to ATR configuration conflicts. |
| 0x80100066 | 智慧卡並未回應重設操作。 |
The smart card is not responding to a reset. |
| 0x80100067 | 智慧卡的電源已移除，無法進行進一步的通訊。 |
Power has been removed from the smart card, so that further communication is not possible. |
| 0x80100068 | 智慧卡已重設，所以共用的狀態資訊都變成無效。 |
The smart card has been reset, so any shared state information is invalid. |
| 0x80100069 | 智慧卡已移除，無法繼續進行通訊。 |
The smart card has been removed, so that further communication is not possible. |
| 0x8010006A | 因為違反安全性，造成存取被拒。 |
Access was denied because of a security violation. |
| 0x8010006B | 密碼錯誤，無法存取智慧卡。 |
The card cannot be accessed because the wrong PIN was presented. |
| 0x8010006C | 無法存取智慧卡，因為已經到達輸入 PIN 碼的最大次數限制。 |
The card cannot be accessed because the maximum number of PIN entry attempts has been reached. |
| 0x8010006D | 到達智慧卡檔案的結尾。 |
The end of the smart card file has been reached. |
| 0x8010006F | 智慧卡沒有 PIN。 |
No PIN was presented to the smart card. |
| 0x80100070 | 在快取中找不到所要求的項目。 |
The requested item could not be found in the cache. |
| 0x80100071 | 所要求的快取項目太舊，已從快取中刪除。 |
The requested cache item is too old and was deleted from the cache. |
| 0x80100072 | 新的快取項目超出定義給快取的單項大小上限。 |
The new cache item exceeds the maximum per-item size defined for the cache. |
| 0x80110401 | 正在存取一個或多個物件時發生錯誤 - ErrorInfo 集合或許有較多的詳細資料 |
Errors occurred accessing one or more objects - the ErrorInfo collection may have more detail |
| 0x80110402 | 一個或多個物件內容遺失或不正確 |
One or more of the object's properties are missing or invalid |
| 0x80110403 | 類別目錄中找不到物件 |
The object was not found in the catalog |
| 0x80110404 | 已登錄物件 |
The object is already registered |
| 0x80110407 | 寫入應用程式檔案時發生錯誤 |
Error occurred writing to the application file |
| 0x80110408 | 讀取應用程式檔案時發生錯誤 |
Error occurred reading the application file |
| 0x80110409 | 應用程式檔案的版本號碼不正確 |
Invalid version number in application file |
| 0x8011040A | 檔案路徑不正確 |
The file path is invalid |
| 0x8011040B | 已安裝了這個應用程式 |
The application is already installed |
| 0x8011040C | 角色已經存在 |
The role already exists |
| 0x8011040D | 複製檔案時發生錯誤 |
An error occurred copying the file |
| 0x8011040F | 一個或多個使用者不正確 |
One or more users are not valid |
| 0x80110410 | 應用程式中有一個或多個使用者是不正確的 |
One or more users in the application file are not valid |
| 0x80110411 | 元件的 CLSID 遺失或損毀 |
The component's CLSID is missing or corrupt |
| 0x80110412 | 元件的 progID 遺失或損毀 |
The component's progID is missing or corrupt |
| 0x80110413 | 無法為更新要求設定需要的驗證等級 |
Unable to set required authentication level for update request |
| 0x80110414 | 設定在應用程式上的識別或密碼不正確 |
The identity or password set on the application is not valid |
| 0x80110418 | 應用程式檔案 CLSID 或 IID 不符合對應的 DLL |
Application file CLSIDs or IIDs do not match corresponding DLLs |
| 0x80110419 | 介面資訊可能遺失或變更 |
Interface information is either missing or changed |
| 0x8011041A | 元件安裝時 DllRegisterServer 失敗 |
DllRegisterServer failed on component install |
| 0x8011041B | 目前沒有可用的伺服器檔案共用 |
No server file share available |
| 0x8011041D | 無法載入 DLL |
DLL could not be loaded |
| 0x8011041E | 登錄的 TypeLib ID 不正確 |
The registered TypeLib ID is not valid |
| 0x8011041F | 找不到應用程式的安裝目錄 |
Application install directory not found |
| 0x80110423 | 元件登錄時發生錯誤 |
Errors occurred while in the component registrar |
| 0x80110424 | 檔案不存在 |
The file does not exist |
| 0x80110426 | GetClassObject 在 DLL 中失敗 |
GetClassObject failed in the DLL |
| 0x80110427 | DLL 不支援列在 TypeLib 的元件 |
The DLL does not support the components listed in the TypeLib |
| 0x80110428 | 無法載入 TypeLib |
The TypeLib could not be loaded |
| 0x80110429 | 檔案不包含元件或元件資訊 |
The file does not contain components or component information |
| 0x8011042A | 這個物件及其子物件的變更已經停用 |
Changes to this object and its sub-objects have been disabled |
| 0x8011042B | 已停用這個物件的刪除功能 |
The delete function has been disabled for this object |
| 0x8011042C | 伺服器類別目錄版本不受支援 |
The server catalog version is not supported |
| 0x8011042D | 不允許元件移動，因為來源或目的應用程式可能是系統應用程式或因目前的變更而被鎖定 |
The component move was disallowed, because the source or destination application is either a system application or currently locked against changes |
| 0x8011042E | 元件移動失敗，因為目的應用程式已經不存在 |
The component move failed because the destination application no longer exists |
| 0x80110430 | 這個系統無法登錄 TypeLib |
The system was unable to register the TypeLib |
| 0x80110433 | 這個操作不能執行在系統應用程式上 |
This operation cannot be performed on the system application |
| 0x80110434 | 無法使用這個程式中的元件登錄程式參照 |
The component registrar referenced in this file is not available |
| 0x80110435 | 在相同 DLL 中的元件已經安裝 |
A component in the same DLL is already installed |
| 0x80110436 | 服務尚未安裝 |
The service is not installed |
| 0x80110437 | 一個或多個內容設定值不正確或相互衝突 |
One or more property settings are either invalid or in conflict with each other |
| 0x80110438 | 您正嘗試要新增或重新命名的物件已經存在 |
The object you are attempting to add or rename already exists |
| 0x80110439 | 這個元件已經存在 |
The component already exists |
| 0x8011043B | 登錄檔案損毀 |
The registration file is corrupt |
| 0x8011043C | 內容值太大了 |
The property value is too large |
| 0x8011043E | 登錄中未發現物件 |
Object was not found in registry |
| 0x8011043F | 這個物件無法放到集區上 |
This object is not poolable |
| 0x80110446 | 以相同的 GUID 作為新的應用程式識別碼的 CLSID，已經安裝在這台電腦上了 |
A CLSID with the same GUID as the new application ID is already installed on this machine |
| 0x80110447 | 指派給元件、介面或方法的角色不存在於應用程式中 |
A role assigned to a component, interface, or method did not exist in the application |
| 0x80110448 | 您必須有一個元件在應用程式中才能啟動應用程式 |
You must have components in an application in order to start the application |
| 0x80110449 | 這個操作並未在這個平台上啟用 |
This operation is not enabled on this platform |
| 0x8011044A | 應用程式 Proxy 無法匯出 |
Application Proxy is not exportable |
| 0x8011044B | 無法啟動應用程式，因為它可能是程式庫應用程式或應用程式 proxy |
Failed to start application because it is either a library application or an application proxy |
| 0x8011044C | 系統應用程式無法匯出 |
System application is not exportable |
| 0x8011044D | 無法訂閱此元件 (元件可能已經被匯入) |
Cannot subscribe to this component (the component may have been imported) |
| 0x8011044E | 事件類別不可以同時是訂閱元件 |
An event class cannot also be a subscriber component |
| 0x8011044F | 程式庫應用程式與應用程式 proxies 不相容 |
Library applications and application proxies are incompatible |
| 0x80110450 | 此函式只有對基本分割才有效 |
This function is valid for the base partition only |
| 0x80110451 | 無法啟動已經被停用的應用程式 |
You cannot start an application that has been disabled |
| 0x80110457 | 所指定的分割名稱已經在這台電腦上使用了 |
The specified partition name is already in use on this computer |
| 0x80110458 | 所指定的分割名稱無效。請確認該名稱含有至少一個可見的字元 |
The specified partition name is invalid. Check that the name contains at least one visible character |
| 0x80110459 | 無法刪除該分割，因為它是一或多個使用者的預設分割 |
The partition cannot be deleted because it is the default partition for one or more users |
| 0x8011045A | 無法匯出該分割，因為該分割上的一或多個元件有相同的檔案名稱 |
The partition cannot be exported, because one or more components in the partition have the same file name |
| 0x8011045B | 包含一或多個匯入元件的應用程式無法安裝到非基本分割 |
Applications that contain one or more imported components cannot be installed into a non-base partition |
| 0x8011045C | 應用程式名稱不是唯一的且無法解析為應用程式識別碼 |
The application name is not unique and cannot be resolved to an application id |
| 0x8011045D | 分割名稱不是唯一的且無法解析為分割識別碼 |
The partition name is not unique and cannot be resolved to a partition id |
| 0x80110472 | COM+ 登錄資料庫尚未初始化 |
The COM+ registry database has not been initialized |
| 0x80110473 | COM+ 登錄資料庫沒有開啟 |
The COM+ registry database is not open |
| 0x80110474 | COM+ 登錄資料庫偵測到系統錯誤 |
The COM+ registry database detected a system error |
| 0x80110475 | COM+ 登錄資料庫已經在執行中 |
The COM+ registry database is already running |
| 0x80110480 | 這個版本的 COM+ 登錄資料庫無法移轉 |
This version of the COM+ registry database cannot be migrated |
| 0x80110481 | COM+ 登錄資料庫中找不到要移轉的架構版本 |
The schema version to be migrated could not be found in the COM+ registry database |
| 0x80110482 | 二進位檔之間類型不符 |
There was a type mismatch between binaries |
| 0x80110483 | 提供了不明或者不正確類型的二進位檔 |
A binary of unknown or invalid type was provided |
| 0x80110484 | 二進位檔與應用程式之間類型不符 |
There was a type mismatch between a binary and an application |
| 0x80110485 | 這個應用程式無法暫停或繼續 |
The application cannot be paused or resumed |
| 0x80110486 | COM+ 類別目錄伺服器在執行期間丟出一個例外狀況 |
The COM+ Catalog Server threw an exception during execution |
| 0x80110600 | 只有被標示為 \"queued\" 的 COM+ 應用程式才能使用 \"queued\" moniker 來啟動。 |
Only COM+ Applications marked \"queued\" can be invoked using the \"queue\" moniker |
| 0x80110601 | 至少要有一個介面被標示為 \"queued\" 才能建立一個含有 \"queued\" moniker 的佇列元件例項 |
At least one interface must be marked \"queued\" in order to create a queued component instance with the \"queue\" moniker |
| 0x80110602 | 要求的操作需要 MSMQ 但未安裝 |
MSMQ is required for the requested operation and is not installed |
| 0x80110603 | 無法整理不支援 IPersistStream 的介面 |
Unable to marshal an interface that does not support IPersistStream |
| 0x80110604 | 訊息的格式不正確、或者在轉送當中損壞了 |
The message is improperly formatted or was damaged in transit |
| 0x80110605 | 應用程式收到一個未驗證的訊息，而應用程式只接受已驗證的訊息 |
An unauthenticated message was received by an application that accepts only authenticated messages |
| 0x80110606 | 訊息已經重新佇列，或者由不在 \"QC 受信任使用者\" 角色中的使用者移動了 |
The message was requeued or moved by a user not in the \"QC Trusted User\" role |
| 0x80110701 | 無法建立分散式交易協調器類型的重複資源 |
Cannot create a duplicate resource of type Distributed Transaction Coordinator |
| 0x80110808 | 一個插入或更新的物件是不屬於一個正確的父系集合 |
One of the objects being inserted or updated does not belong to a valid parent collection |
| 0x80110809 | 找不到其中一個指定的物件 |
One of the specified objects cannot be found |
| 0x8011080A | 指定的應用程式目前沒有執行 |
The specified application is not currently running |
| 0x8011080B | 指定的分割無效。 |
The partition(s) specified are not valid. |
| 0x8011080D | 無法集區或回收那些執行方式是 NT 服務的 COM+ 應用程式 |
COM+ applications that run as NT service may not be pooled or recycled |
| 0x8011080E | 已經指派了一個或以上的使用者給本機分割集。 |
One or more users are already assigned to a local partition set. |
| 0x8011080F | 無法回收程式庫應用程式。 |
Library applications may not be recycled. |
| 0x80110811 | 無法回收那些執行成 NT 服務的應用程式。 |
Applications running as NT services may not be recycled. |
| 0x80110812 | 已經回收處理程序。 |
The process has already been recycled. |
| 0x80110813 | 無法回收暫停的處理程序。 |
A paused process may not be recycled. |
| 0x80110814 | 程式庫應用程式不可以是 NT 服務。 |
Library applications may not be NT services. |
| 0x80110815 | 提供給複製操作的 ProgID 不正確。該 ProgID 正由另一個登錄的 CLSID 使用中。 |
The ProgID provided to the copy operation is invalid. The ProgID is in use by another registered CLSID. |
| 0x80110816 | 指定為預設的分割並不是分割集的成員。 |
The partition specified as default is not a member of the partition set. |
| 0x80110817 | 無法暫停回收的處理程序。 |
A recycled process may not be paused. |
| 0x80110818 | 拒絕存取指定的分割。 |
Access to the specified partition is denied. |
| 0x80110819 | 只有應用程式檔 (*.MSI 檔) 才能安裝至磁碟分割。 |
Only Application Files (*.MSI files) can be installed into partitions. |
| 0x8011081A | 含有舊版元件的應用程式無法匯出為 1.0 格式。 |
Applications containing one or more legacy components may not be exported to 1.0 format. |
| 0x8011081B | 舊版元件無法存在於非基本分割中。 |
Legacy components may not exist in non-base partitions. |
| 0x8011081C | 無法從系統應用程式、或應用程式 Proxy、或不可變更之應用程式移動 (或複製) 元件 |
A component cannot be moved (or copied) from the System Application, an application proxy or a non-changeable application |
| 0x8011081D | 無法將元件移動 (或複製) 到系統應用程式、或應用程式 Proxy、或不可變更之應用程式 |
A component cannot be moved (or copied) to the System Application, an application proxy or a non-changeable application |
| 0x8011081E | 無法將私密元件移動 (或複製) 到程式庫應用程式或基本分割 |
A private component cannot be moved (or copied) to a library application or to the base partition |
| 0x8011081F | 基本應用程式分割存在於所有的分割集中，因此無法移除。 |
The Base Application Partition exists in all partition sets and cannot be removed. |
| 0x80110820 | 還有，事件類別元件無法產生別名。 |
Alas, Event Class components cannot be aliased. |
| 0x80110821 | 拒絕存取，因為元件是私密的。 |
Access is denied because the component is private. |
| 0x80110822 | 所指定的 SAFER 層級不正確。 |
The specified SAFER level is invalid. |
| 0x80110823 | 所指定的使用者無法寫入系統登錄 |
The specified user cannot write to the system registry |
| 0x80110824 | COM+ 分割目前已停用。 |
COM+ partitions are currently disabled. |
| 0x80190001 | 未預期的 HTTP 狀態碼。 |
Unexpected HTTP status code. |
| 0x80190003 | 未預期的重新導向狀態碼 (3xx)。 |
Unexpected redirection status code (3xx). |
| 0x80190004 | 未預期的用戶端錯誤狀態碼 (4xx)。 |
Unexpected client error status code (4xx). |
| 0x80190005 | 未預期的伺服器錯誤狀態碼 (5xx)。 |
Unexpected server error status code (5xx). |
| 0x8019012C | 多重選擇 (300)。 |
Multiple choices (300). |
| 0x8019012D | 已永久移動 (301)。 |
Moved permanently (301). |
| 0x8019012E | 已找到 (302)。 |
Found (302). |
| 0x8019012F | 檢視其他 (303)。 |
See Other (303). |
| 0x80190130 | 未修改 (304)。 |
Not modified (304). |
| 0x80190131 | 使用 Proxy (305)。 |
Use proxy (305). |
| 0x80190133 | 暫時重新導向 (307)。 |
Temporary redirect (307). |
| 0x80190190 | 錯誤的要求 (400)。 |
Bad request (400). |
| 0x80190191 | 未授權 (401)。 |
Unauthorized (401). |
| 0x80190192 | 要求付款 (402)。 |
Payment required (402). |
| 0x80190193 | 禁止 (403)。 |
Forbidden (403). |
| 0x80190194 | 找不到 (404)。 |
Not found (404). |
| 0x80190195 | 方式不允許 (405)。 |
Method not allowed (405). |
| 0x80190196 | 無法接受 (406)。 |
Not acceptable (406). |
| 0x80190197 | 要求 Proxy 驗證 (407)。 |
Proxy authentication required (407). |
| 0x80190198 | 要求逾時 (408)。 |
Request timeout (408). |
| 0x80190199 | 衝突 (409)。 |
Conflict (409). |
| 0x8019019A | 不存在 (410)。 |
Gone (410). |
| 0x8019019B | 必須有長度 (411)。 |
Length required (411). |
| 0x8019019C | 先決條件失敗 (412)。 |
Precondition failed (412). |
| 0x8019019D | 要求的實體太大 (413)。 |
Request entity too large (413). |
| 0x8019019E | 要求 URI 太長 (414)。 |
Request-URI too long (414). |
| 0x8019019F | 不受支援的媒體類型 (415)。 |
Unsupported media type (415). |
| 0x801901A0 | 無法滿足的要求範圍 (416)。 |
Requested range not satisfiable (416). |
| 0x801901A1 | 預期失敗 (417)。 |
Expectation failed (417). |
| 0x801901F4 | 內部伺服器錯誤 (500)。 |
Internal server error (500). |
| 0x801901F5 | 尚未建置 (501)。 |
Not implemented (501). |
| 0x801901F6 | 錯誤的閘道 (502)。 |
Bad gateway (502). |
| 0x801901F7 | 服務無法使用 (503)。 |
Service unavailable (503). |
| 0x801901F8 | 閘道逾時 (504)。 |
Gateway timeout (504). |
| 0x801901F9 | 版本不受支援 (505)。 |
Version not supported (505). |
| 0x801B8000 | 當機報告功能失敗。 |
Crash reporting failed. |
| 0x801B8001 | 報告產生作業已中止，因為使用者已取消報告產生作業。 |
Report aborted due to user cancelation. |
| 0x801B8002 | 報告產生作業已中止，因為發生網路失敗。 |
Report aborted due to network failure. |
| 0x801B8003 | 報告未初始化。 |
Report not initialized. |
| 0x801B8004 | 已在執行所指定處理程序的報告產生功能。 |
Reporting is already in progress for the specified process. |
| 0x801B8005 | 因為有節流處理而未產生的傾印。 |
Dump not generated due to a throttle. |
| 0x801B8006 | 由於沒有足夠的使用者同意，作業失敗。 |
Operation failed due to insufficient user consent. |
| 0x801B8007 | 由於效能條件，報告已中止。 |
Report aborted due to performance criteria. |
| 0x801F0001 | 篩選未定義此操作的處理常式。 |
A handler was not defined by the filter for this operation. |
| 0x801F0002 | 已針對此物件定義內容。 |
A context is already defined for this object. |
| 0x801F0003 | 非同步要求對於此操作而言不正確。 |
Asynchronous requests are not valid for this operation. |
| 0x801F0004 | 不允許此操作的快速 IO 路徑。 |
Disallow the Fast IO path for this operation. |
| 0x801F0005 | 發出不正確的名稱要求。目前無法抓取要求的名稱。 |
An invalid name request was made. The name requested cannot be retrieved at this time. |
| 0x801F0006 | 目前將此操作指派給背景工作執行緒以進行進一步處理並不安全，因為它可能會導致發生資源鎖死的情況。 |
Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock. |
| 0x801F0007 | 當篩選器嘗試登錄時，篩選器管理員未初始化。請確定篩選器管理員已載入為驅動程式。 |
The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver. |
| 0x801F0008 | 篩選器未就緒，無法連結至磁碟區，因為它尚未完成初始化 (FltStartFiltering 尚未被呼叫)。 |
The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called). |
| 0x801F0009 | 篩選器目前必須清除所有操作特定內容，因為在操作完成之前，內容已被較低階的驅動程式從系統移除。 |
The filter must cleanup any operation specific context at this time because it is being removed from the system before the operation is completed by the lower drivers. |
| 0x801F000A | 篩選器管理員發生無法修復的內部錯誤，因此操作失敗。這通常是因為篩選器從預先操作回呼傳回不正確的值所造成。 |
The Filter Manager had an internal error from which it cannot recover, therefore the operation has been failed. This is usually the result of a filter returning an invalid value from a pre-operation callback. |
| 0x801F000B | 正在刪除針對此動作指定的物件，因此要求的動作目前無法完成。 |
The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time. |
| 0x801F000C | 必須針對此類型的內容使用非分頁集區。 |
Non-paged pool must be used for this type of context. |
| 0x801F000D | 為操作提供了重複的處理常式定義。 |
A duplicate handler definition has been provided for an operation. |
| 0x801F000E | 回呼資料佇列已停用。 |
The callback data queue has been disabled. |
| 0x801F000F | 目前不要將篩選器連結到該磁碟區。 |
Do not attach the filter to the volume at this time. |
| 0x801F0010 | 目前不要將篩選器與該磁碟區中斷連結。 |
Do not detach the filter from the volume at this time. |
| 0x801F0011 | 指定之磁碟區的此高度已有執行個體存在。 |
An instance already exists at this altitude on the volume specified. |
| 0x801F0012 | 指定的磁碟區中已有同名的執行個體存在。 |
An instance already exists with this name on the volume specified. |
| 0x801F0013 | 系統找不到指定的篩選器。 |
The system could not find the filter specified. |
| 0x801F0014 | 系統找不到指定的磁碟區。 |
The system could not find the volume specified. |
| 0x801F0015 | 系統找不到指定的執行個體。 |
The system could not find the instance specified. |
| 0x801F0016 | 找不到指定之要求的已登錄內容配置定義。 |
No registered context allocation definition was found for the given request. |
| 0x801F0017 | 在登錄內容時指定了不正確的參數。 |
An invalid parameter was specified during context registration. |
| 0x801F0018 | 在篩選器管理員的名稱快取中找不到要求的名稱，也無法從檔案系統抓取名稱。 |
The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system. |
| 0x801F0019 | 指定之磁碟區的要求裝置物件不存在。 |
The requested device object does not exist for the given volume. |
| 0x801F001A | 指定的磁碟區已掛接。 |
The specified volume is already mounted. |
| 0x801F001B | 指定的交易內容已徵募到交易中 |
The specified Transaction Context is already enlisted in a transaction |
| 0x801F001C | 特定內容已連結到另一個物件 |
The specifiec context is already attached to another object |
| 0x801F0020 | 沒有任何等候者在等候篩選器對此訊息的回覆。 |
No waiter is present for the filter's reply to this message. |
| 0x801F0023 | filesystem 資料庫資源使用中。目前無法完成註冊。 |
The filesystem database resource is in use. Registration cannot complete at this time. |
| 0x80260001 | {顯示驅動程式停止回應}%hs 顯示驅動程式已停止正常運作。請儲存您的工作資料並重新啟動系統以還原完整的顯示功能。下次您重新開機時，將會顯示對話方塊讓您有機會報告這個問題給 Microsoft。 |
{Display Driver Stopped Responding}The %hs display driver has stopped working normally. Save your work and reboot the system to restore full display functionality.The next time you reboot the machine a dialog will be displayed giving you a chance to report this failure to Microsoft. |
| 0x80263001 | {桌面轉譯緩衝處理已停用}操作無法完成，因為桌面轉譯緩衝處理已停用。 |
{Desktop composition is disabled}The operation could not be completed because desktop composition is disabled. |
| 0x80263002 | {從遠端存取時不支援某些桌面轉譯緩衝處理 API}透過遠端工作階段執行時，不支援此操作。 |
{Some desktop composition APIs are not supported while remoting}The operation is not supported while running in a remote session. |
| 0x80263003 | {沒有可用的 DWM 重新導向表面}DWM 無法提供重新導向表面以完成 DirectX 呈現。 |
{No DWM redirection surface is available}The DWM was unable to provide a redireciton surface to complete the DirectX present. |
| 0x80263004 | {DWM 並未針對指定的視窗將呈現排入佇列} 指定的視窗目前並未使用已排入佇列的呈現。 |
{DWM is not queuing presents for the specified window}The window specified is not currently using queued presents. |
| 0x80263005 | {找不到 LUID 指定的介面卡}DWM 找不到 LUID 指定的介面卡。 |
{The adapter specified by the LUID is not found}DWM can not find the adapter specified by the LUID. |
| 0x80263007 | {無法建立重新導向介面。介面的大小超過此電腦支援的大小}無法建立重新導向介面。介面的大小超過此電腦支援的大小。 |
{Redirection surface can not be created. The size of the surface is larger than what is supported on this machine}Redirection surface can not be created. The size of the surface is larger than what is supported on this machine. |
| 0x80270001 | NAP SoH 封包無效。 |
The NAP SoH packet is invalid. |
| 0x80270002 | NAP 封包遺漏 SoH。 |
An SoH was missing from the NAP packet. |
| 0x80270003 | 實體識別碼和某個已登錄的識別碼衝突。 |
The entity ID conflicts with an already registered id. |
| 0x80270004 | 沒有已快取的 SoH。 |
No cached SoH is present. |
| 0x80270005 | 實體仍繫結至 NAP 系統。 |
The entity is still bound to the NAP system. |
| 0x80270006 | 實體未向 NAP 系統登錄。 |
The entity is not registered with the NAP system. |
| 0x80270007 | 實體未使用 NAP 系統初始化。 |
The entity is not initialized with the NAP system. |
| 0x80270008 | SoH 要求與 SoH 回應中的相互關聯識別碼不相符。 |
The correlation id in the SoH-Request and SoH-Response do not match up. |
| 0x80270009 | 已針對目前不是擱置中的要求指示完成狀態。 |
Completion was indicated on a request that is not currently pending. |
| 0x8027000A | 找不到 NAP 元件的識別碼。 |
The NAP component's id was not found. |
| 0x8027000B | SoH 封包的連線大小上限太小。 |
The maximum size of the connection is too small for an SoH packet. |
| 0x8027000C | NapAgent 服務未執行。 |
The NapAgent service is not running. |
| 0x8027000E | 已使用 NapAgent 服務停用實體。 |
The entity is disabled with the NapAgent service. |
| 0x8027000F | 未設定群組原則。 |
Group Policy is not configured. |
| 0x80270010 | 太多同步呼叫。 |
Too many simultaneous calls. |
| 0x80270011 | SHV 設定已存在。 |
SHV configuration already existed. |
| 0x80270012 | 找不到 SHV 設定。 |
SHV configuration is not found. |
| 0x80270013 | 要求中的 SHV 逾時。 |
SHV timed out on the request. |
| 0x80270220 | 已達到存取清單的項目數上限。您必須先移除項目，才能新增項目。 |
The maximum number of items for the access list has been reached. An item must be removed before another item is added. |
| 0x80270222 | 無法存取家用群組。可能未設定家用群組，或可能發生錯誤。 |
Cannot access Homegroup. Homegroup may not be set up or may have encountered an error. |
| 0x80270250 | 此應用程式無法啟動，因為螢幕解析度低於 1024x768。請選擇較高的螢幕解析度，然後再試一次。 |
This app can't start because the screen resolution is below 1024x768. Choose a higher screen resolution and then try again. |
| 0x80270251 | 無法從提升權限的內容啟用此應用程式。 |
This app can't be activated from an elevated context. |
| 0x80270252 | 當 UAC 停用時，無法啟用此應用程式。 |
This app can't be activated when UAC is disabled. |
| 0x80270253 | 此應用程式無法由內建的 Administrator 啟用。 |
This app can't be activated by the Built-in Administrator. |
| 0x80270254 | 此應用程式不支援指定的協定，或此應用程式尚未安裝。 |
This app does not support the contract specified or is not installed. |
| 0x80270255 | 此應用程式登錄了多個延伸模組，以支援指定的協定。以 AppUserModelId 執行的啟用不明確。 |
This app has mulitple extensions registered to support the specified contract. Activation by AppUserModelId is ambiguous. |
| 0x80270256 | 此應用程式的套件系列安裝了一個以上的套件。這是不支援的做法。 |
This app's package family has more than one package installed. This is not supported. |
| 0x80270257 | 需要應用程式管理員才能啟用應用程式，但應用程式管理員並未執行。 |
The app manager is required to activate applications, but is not running. |
| 0x8027025A | 應用程式未在要求的時間內啟動。 |
The app didn't start in the required time. |
| 0x8027025B | 應用程式未啟動。 |
The app didn't start. |
| 0x8027025C | 此應用程式無法啟動，因為其授權有問題。請稍後再試一次。 |
This app failed to launch because of an issue with its license. Please try again in a moment. |
| 0x8027025D | 此應用程式無法啟動，因為其試用授權已到期。 |
This app failed to launch because its trial license has expired. |
| 0x80270260 | 請選擇位於使用 NTFS 檔案系統格式化之磁碟機上的資料夾。 |
Please choose a folder on a drive that's formatted with the NTFS file system. |
| 0x80270261 | 此位置已被使用。請選擇其他位置。 |
This location is already being used. Please choose a different location. |
| 0x80270262 | 無法為此位置編製索引。請選擇其他位置。 |
This location cannot be indexed. Please choose a different location. |
| 0x80270263 | 抱歉，無法完成該動作，因為該檔案尚未完成上傳。請稍後再試一次。 |
Sorry, the action couldn't be completed because the file hasn't finished uploading. Try again later. |
| 0x80270264 | 抱歉，無法完成該動作。 |
Sorry, the action couldn't be completed. |
| 0x80270265 | 您只能將此內容移動到資料夾。若要將此內容移動到此磁碟機，請選擇或建立資料夾。 |
This content can only be moved to a folder. To move the content to this drive, please choose or create a folder. |
| 0x80280000 | 這是用來將 TPM 硬體錯誤轉換為 win 錯誤的錯誤遮罩。 |
This is an error mask to convert TPM hardware errors to win errors. |
| 0x80280001 | 驗證失敗。 |
Authentication failed. |
| 0x80280002 | PCR、DIR 或其他暫存器的索引不正確。 |
The index to a PCR, DIR or other register is incorrect. |
| 0x80280003 | 一或多個參數錯誤。 |
One or more parameter is bad. |
| 0x80280004 | 操作已順利完成，但稽核操作失敗。 |
An operation completed successfully but the auditing of that operation failed. |
| 0x80280005 | 清除停用旗標已設定，且所有清除操作現在需要實際存取。 |
The clear disable flag is set and all clear operations now require physical access. |
| 0x80280006 | 啟動信賴平台模組 (TPM)。 |
Activate the Trusted Platform Module (TPM). |
| 0x80280007 | 啟用信賴平台模組 (TPM)。 |
Enable the Trusted Platform Module (TPM). |
| 0x80280008 | 目標命令已停用。 |
The target command has been disabled. |
| 0x80280009 | 操作失敗。 |
The operation failed. |
| 0x8028000A | 序數未知或不一致。 |
The ordinal was unknown or inconsistent. |
| 0x8028000B | 安裝擁有者的功能已停用。 |
The ability to install an owner is disabled. |
| 0x8028000C | 無法解譯金鑰控制代碼。 |
The key handle cannot be interpreted. |
| 0x8028000D | 金鑰控制代碼指向無效的金鑰。 |
The key handle points to an invalid key. |
| 0x8028000E | 無法接受的加密配置。 |
Unacceptable encryption scheme. |
| 0x8028000F | 移轉授權失敗。 |
Migration authorization failed. |
| 0x80280010 | 無法解譯 PCR 資訊。 |
PCR information could not be interpreted. |
| 0x80280011 | 沒有空間可以載入金鑰。 |
No room to load key. |
| 0x80280012 | 沒有儲存根金鑰 (SRK) 組。 |
There is no Storage Root Key (SRK) set. |
| 0x80280013 | 已加密的 blob 無效，或是並非由此 TPM 所建立。 |
An encrypted blob is invalid or was not created by this TPM. |
| 0x80280014 | 信賴平台模組 (TPM) 已經有擁有者。 |
The Trusted Platform Module (TPM) already has an owner. |
| 0x80280015 | TPM 的內部資源不足，無法執行要求的動作。 |
The TPM has insufficient internal resources to perform the requested action. |
| 0x80280016 | 隨機字串太短。 |
A random string was too short. |
| 0x80280017 | TPM 的空間不足，無法執行該操作。 |
The TPM does not have the space to perform the operation. |
| 0x80280018 | 具名 PCR 值與目前的 PCR 值不符。 |
The named PCR value does not match the current PCR value. |
| 0x80280019 | 命令之 paramSize 引數的值不正確。 |
The paramSize argument to the command has the incorrect value . |
| 0x8028001A | 沒有現有的 SHA-1 執行緒。 |
There is no existing SHA-1 thread. |
| 0x8028001B | 無法繼續計算，因為現有的 SHA-1 執行緒已發生錯誤。 |
The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error. |
| 0x8028001C | TPM 硬體裝置進行內部自我測試時回報錯誤。請嘗試重新啟動電腦以解決問題。如果問題持續發生，請取得適用於您 TPM 硬體的最新 BIOS 或韌體更新。如需指示，請參閱電腦製造商的文件。 |
The TPM hardware device reported a failure during its internal self test. Try restarting the computer to resolve the problem. If the problem continues, check for the latest BIOS or firmware update for your TPM hardware. Consult the computer manufacturer's documentation for instructions. |
| 0x8028001D | 雙金鑰函數中的第二個金鑰授權失敗。 |
The authorization for the second key in a 2 key function failed authorization. |
| 0x8028001E | 傳送給命令的標記值無效。 |
The tag value sent to for a command is invalid. |
| 0x8028001F | 傳送資訊到 TPM 時發生 IO 錯誤。 |
An IO error occurred transmitting information to the TPM. |
| 0x80280020 | 加密程序有問題。 |
The encryption process had a problem. |
| 0x80280021 | 解密程序未完成。 |
The decryption process did not complete. |
| 0x80280022 | 使用了無效的控制代碼。 |
An invalid handle was used. |
| 0x80280023 | TPM 未安裝簽署金鑰 (EK)。 |
The TPM does not have an Endorsement Key (EK) installed. |
| 0x80280024 | 不允許該金鑰使用方法。 |
The usage of a key is not allowed. |
| 0x80280025 | 不允許送出的實體類型。 |
The submitted entity type is not allowed. |
| 0x80280026 | 相對於 TPM_Init 與後續 TPM_Startup，命令的接收順序錯誤。 |
The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup. |
| 0x80280027 | 已簽章的資料不能包含額外 DER 資訊。 |
Signed data cannot include additional DER information. |
| 0x80280028 | 此 TPM 不支援 TPM_KEY_PARMs 中的金鑰屬性。 |
The key properties in TPM_KEY_PARMs are not supported by this TPM. |
| 0x80280029 | 此金鑰的移轉屬性不正確。 |
The migration properties of this key are incorrect. |
| 0x8028002A | 此金鑰的簽章或加密配置不正確，或在此情況下是不允許的。 |
The signature or encryption scheme for this key is incorrect or not permitted in this situation. |
| 0x8028002B | 資料 (或 blob) 參數的大小錯誤，或與參照的金鑰不一致。 |
The size of the data (or blob) parameter is bad or inconsistent with the referenced key. |
| 0x8028002C | 模式參數錯誤，例如 TPM_GetCapability 的 capArea 或 subCapArea、TPM_PhysicalPresence 的 phsicalPresence 參數，或是 TPM_CreateMigrationBlob 的 migrationType。 |
A mode parameter is bad, such as capArea or subCapArea for TPM_GetCapability, phsicalPresence parameter for TPM_PhysicalPresence, or migrationType for TPM_CreateMigrationBlob. |
| 0x8028002D | physicalPresence 或 physicalPresenceLock 位元的值錯誤。 |
Either the physicalPresence or physicalPresenceLock bits have the wrong value. |
| 0x8028002E | TPM 無法執行此版本的功能。 |
The TPM cannot perform this version of the capability. |
| 0x8028002F | 包裝的傳輸工作階段不允許 TPM。 |
The TPM does not allow for wrapped transport sessions. |
| 0x80280030 | TPM 稽核建構失敗，且其下的命令也傳回錯誤碼。 |
TPM audit construction failed and the underlying command was returning a failure code also. |
| 0x80280031 | TPM 稽核建構失敗，且其下的命令傳回成功資訊。 |
TPM audit construction failed and the underlying command was returning success. |
| 0x80280032 | 嘗試重設沒有可重設屬性的 PCR 暫存器。 |
Attempt to reset a PCR register that does not have the resettable attribute. |
| 0x80280033 | 嘗試重設 PCR 暫存器，它要求位置與位置修飾元不能是命令傳輸的一部分。 |
Attempt to reset a PCR register that requires locality and locality modifier not part of command transport. |
| 0x80280034 | 讓身份識別 blob 看起來不像是人工輸入的樣子。 |
Make identity blob not properly typed. |
| 0x80280035 | 儲存時內容識別的資源類型與實際資源不符。 |
When saving context identified resource type does not match actual resource. |
| 0x80280036 | TPM 正嘗試執行只有在 FIPS 模式才可以使用的命令。 |
The TPM is attempting to execute a command only available when in FIPS mode. |
| 0x80280037 | 命令正嘗試使用無效的系列識別碼。 |
The command is attempting to use an invalid family ID. |
| 0x80280038 | 可用來操縱 NV 存放區的權限無法使用。 |
The permission to manipulate the NV storage is not available. |
| 0x80280039 | 此操作需要已簽章的命令。 |
The operation requires a signed command. |
| 0x8028003A | 載入 NV 金鑰的操作不正確。 |
Wrong operation to load an NV key. |
| 0x8028003B | NV_LoadKey blob 需要擁有者與 blob 授權。 |
NV_LoadKey blob requires both owner and blob authorization. |
| 0x8028003C | NV 區域已鎖定，且無法寫入。 |
The NV area is locked and not writtable. |
| 0x8028003D | 該位置對於所嘗試的操作而言不正確。 |
The locality is incorrect for the attempted operation. |
| 0x8028003E | NV 區域是唯讀的，且無法寫入。 |
The NV area is read only and can't be written to. |
| 0x8028003F | NV 區域沒有防寫保護。 |
There is no protection on the write to the NV area. |
| 0x80280040 | 系列計數值不相符。 |
The family count value does not match. |
| 0x80280041 | NV 區域已被寫入。 |
The NV area has already been written to. |
| 0x80280042 | NV 區域屬性衝突。 |
The NV area attributes conflict. |
| 0x80280043 | 結構標籤與版本無效或不一致。 |
The structure tag and version are invalid or inconsistent. |
| 0x80280044 | 該金鑰是由 TPM 擁有者所控制，且只能由 TPM 擁有者收回。 |
The key is under control of the TPM Owner and can only be evicted by the TPM Owner. |
| 0x80280045 | 計數器控制代碼不正確。 |
The counter handle is incorrect. |
| 0x80280046 | 該寫入動作並未完整寫入該區域。 |
The write is not a complete write of the area. |
| 0x80280047 | 已儲存內容計數的間距太大。 |
The gap between saved context counts is too large. |
| 0x80280048 | 已經超過 NV 寫入次數的上限 (在沒有擁有者的情況下)。 |
The maximum number of NV writes without an owner has been exceeded. |
| 0x80280049 | 未設定運算子 AuthData 值。 |
No operator AuthData value is set. |
| 0x8028004A | 未載入內容指向的資源。 |
The resource pointed to by context is not loaded. |
| 0x8028004B | 委派管理已鎖定。 |
The delegate administration is locked. |
| 0x8028004C | 嘗試管理非委派系列的系列。 |
Attempt to manage a family other then the delegated family. |
| 0x8028004D | 未啟用委派表格管理。 |
Delegation table management not enabled. |
| 0x8028004E | 有命令在專用傳輸工作階段之外執行。 |
There was a command executed outside of an exclusive transport session. |
| 0x8028004F | 嘗試以相關內容方式儲存擁有者收回控制的金鑰。 |
Attempt to context save a owner evict controlled key. |
| 0x80280050 | DAA 命令沒有可用的資源，無法執行命令。 |
The DAA command has no resources availble to execute the command. |
| 0x80280051 | DAA 參數 inputData0 的一致性檢查失敗。 |
The consistency check on DAA parameter inputData0 has failed. |
| 0x80280052 | DAA 參數 inputData1 的一致性檢查失敗。 |
The consistency check on DAA parameter inputData1 has failed. |
| 0x80280053 | DAA_issuerSettings 的一致性檢查失敗。 |
The consistency check on DAA_issuerSettings has failed. |
| 0x80280054 | DAA_tpmSpecific 的一致性檢查失敗。 |
The consistency check on DAA_tpmSpecific has failed. |
| 0x80280055 | 已送出之 DAA 命令所指出之不可部分完成的處理程序不是預期的處理程序。 |
The atomic process indicated by the submitted DAA command is not the expected process. |
| 0x80280056 | 簽發者的有效性檢查發現不一致。 |
The issuer's validity check has detected an inconsistency. |
| 0x80280057 | w 的一致性檢查失敗。 |
The consistency check on w has failed. |
| 0x80280058 | 控制代碼不正確。 |
The handle is incorrect. |
| 0x80280059 | 委派不正確。 |
Delegation is not correct. |
| 0x8028005A | 內容 blob 無效。 |
The context blob is invalid. |
| 0x8028005B | TPM 持有太多內容。 |
Too many contexts held by the TPM. |
| 0x8028005C | 移轉授權單位簽章驗證失敗。 |
Migration authority signature validation failure. |
| 0x8028005D | 移轉目的地未驗證。 |
Migration destination not authenticated. |
| 0x8028005E | 移轉來源不正確。 |
Migration source incorrect. |
| 0x8028005F | 不正確的移轉授權單位。 |
Incorrect migration authority. |
| 0x80280061 | 嘗試撤銷 EK，但 EK 無法撤銷。 |
Attempt to revoke the EK and the EK is not revocable. |
| 0x80280062 | CMK 票證的簽章錯誤。 |
Bad signature of CMK ticket. |
| 0x80280063 | 內容清單中沒有空間，無法存放其他內容。 |
There is no room in the context list for additional contexts. |
| 0x80280400 | 命令已被封鎖。 |
The command was blocked. |
| 0x80280401 | 找不到指定的控制代碼。 |
The specified handle was not found. |
| 0x80280402 | TPM 傳回重複的控制代碼，而且該命令需要重新送出。 |
The TPM returned a duplicate handle and the command needs to be resubmitted. |
| 0x80280403 | 傳輸中的命令已被封鎖。 |
The command within the transport was blocked. |
| 0x80280404 | 傳輸中的命令不受支援。 |
The command within the transport is not supported. |
| 0x80280800 | TPM 正忙於立即回應命令，但該命令可以稍後再重新送出。 |
The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time. |
| 0x80280801 | SelfTestFull 並未執行。 |
SelfTestFull has not been run. |
| 0x80280802 | TPM 目前正在執行完整自我測試。 |
The TPM is currently executing a full selftest. |
| 0x80280803 | TPM 正在防禦字典攻擊，且正處於逾時階段。 |
The TPM is defending against dictionary attacks and is in a time-out period. |
| 0x80284001 | 信賴平台模組支援程式中發生內部錯誤。 |
An internal error has occurred within the Trusted Platform Module support program. |
| 0x80284002 | 一或多個輸入參數錯誤。 |
One or more input parameters is bad. |
| 0x80284003 | 指定的輸出指標錯誤。 |
A specified output pointer is bad. |
| 0x80284004 | 指定的內容控制代碼並非指向正確的內容。 |
The specified context handle does not refer to a valid context. |
| 0x80284005 | 指定的輸出緩衝區太小。 |
A specified output buffer is too small. |
| 0x80284006 | 與 TPM 通訊時發生錯誤。 |
An error occurred while communicating with the TPM. |
| 0x80284007 | 一或多個內容參數不正確。 |
One or more context parameters is invalid. |
| 0x80284008 | TBS 服務並未執行，且無法啟動。 |
The TBS service is not running and could not be started. |
| 0x80284009 | 無法建立新內容，因為已有太多開啟的內容。 |
A new context could not be created because there are too many open contexts. |
| 0x8028400A | 因為開啟的虛擬資源太多，所以無法建立新的虛擬資源。 |
A new virtual resource could not be created because there are too many open virtual resources. |
| 0x8028400B | TBS 服務已啟動，但尚未執行。 |
The TBS service has been started but is not yet running. |
| 0x8028400C | 不支援實體操作介面。 |
The physical presence interface is not supported. |
| 0x8028400D | 命令已取消。 |
The command was canceled. |
| 0x8028400E | 輸入或輸出緩衝區太大。 |
The input or output buffer is too large. |
| 0x8028400F | 在此電腦上電腦上找不到相容的信賴平台模組 (TPM) 安全性裝置。 |
A compatible Trusted Platform Module (TPM) Security Device cannot be found on this computer. |
| 0x80284010 | TBS 服務已停用。 |
The TBS service has been disabled. |
| 0x80284011 | 無法使用 TCG 事件記錄。 |
No TCG event log is available. |
| 0x80284012 | 呼叫者沒有適當的權限可以執行要求的操作。 |
The caller does not have the appropriate rights to perform the requested operation. |
| 0x80284013 | 指定的旗標不允許 TPM 佈建動作。若要成功進行佈建，可能需要數個動作中的其中一項。使 TPM 就緒的 TPM 管理主控台 (tpm.msc) 動作可能會有幫助。如需詳細資訊，請參閱 Win32_Tpm WMI 方法 'Provision' 的文件。(可能需要的動作包括將「TPM 擁有者授權」值匯入到系統中、呼叫 Win32_Tpm WMI 方法以佈建 TPM，以及將 'ForceClear_Allowed' 或 'PhysicalPresencePrompts_Allowed' 指定為 TRUE (如「其他資訊」中指出的值所示)，或是在系統 BIOS 中啟用 TPM)。 |
The TPM provisioning action is not allowed by the specified flags. For provisioning to be successful, one of several actions may be required. The TPM management console (tpm.msc) action to make the TPM Ready may help. For further information, see the documentation for the Win32_Tpm WMI method 'Provision'. (The actions that may be required include importing the TPM Owner Authorization value into the system, calling the Win32_Tpm WMI method for provisioning the TPM and specifying TRUE for either 'ForceClear_Allowed' or 'PhysicalPresencePrompts_Allowed' (as indicated by the value returned in the Additional Information), or enabling the TPM in the system BIOS.) |
| 0x80284014 | 此韌體的「實體操作介面」不支援要求的方法。 |
The Physical Presence Interface of this firmware does not support the requested method. |
| 0x80284015 | 找不到要求的 TPM OwnerAuth 值。 |
The requested TPM OwnerAuth value was not found. |
| 0x80284016 | TPM 佈建未完成。如需完成佈建的詳細資訊，請呼叫 Win32_Tpm WMI 方法以佈建 TPM ('Provision')，並檢查傳回的資訊。 |
The TPM provisioning did not complete. For more information on completing the provisioning, call the Win32_Tpm WMI method for provisioning the TPM ('Provision') and check the returned Information. |
| 0x80290100 | 命令緩衝區並非處於正確的狀態。 |
The command buffer is not in the correct state. |
| 0x80290101 | 命令緩衝區未包含足夠的資料，無法處理要求。 |
The command buffer does not contain enough data to satisfy the request. |
| 0x80290102 | 命令緩衝區無法容納更多資料。 |
The command buffer cannot contain any more data. |
| 0x80290103 | 一或多個輸出參數是 NULL 或不正確。 |
One or more output parameters was NULL or invalid. |
| 0x80290104 | 一或多個輸入參數不正確。 |
One or more input parameters is invalid. |
| 0x80290105 | 記憶體不足，無法滿足要求。 |
Not enough memory was available to satisfy the request. |
| 0x80290106 | 指定的緩衝區太小。 |
The specified buffer was too small. |
| 0x80290107 | 發現內部錯誤。 |
An internal error was detected. |
| 0x80290109 | 指定的授權資訊不正確。 |
The specified authorization information was invalid. |
| 0x8029010A | 指定的內容控制代碼不正確。 |
The specified context handle was not valid. |
| 0x8029010B | 與 TBS 通訊時發生錯誤。 |
An error occurred while communicating with the TBS. |
| 0x8029010C | TPM 傳回意外的結果。 |
The TPM returned an unexpected result. |
| 0x8029010D | 該訊息對於編碼配置而言太大。 |
The message was too large for the encoding scheme. |
| 0x8029010E | 無法識別 blob 中的編碼。 |
The encoding in the blob was not recognized. |
| 0x8029010F | 金鑰大小不正確。 |
The key size is not valid. |
| 0x80290110 | 加密操作失敗。 |
The encryption operation failed. |
| 0x80290111 | 金鑰參數結構不正確 |
The key parameters structure was not valid |
| 0x80290112 | 依據要求提供的資料不像是有效的移轉授權 blob。 |
The requested supplied data does not appear to be a valid migration authorization blob. |
| 0x80290113 | 指定的 PCR 索引不正確 |
The specified PCR index was invalid |
| 0x80290114 | 指定的資料不像是有效的委派 blob。 |
The data given does not appear to be a valid delegate blob. |
| 0x80290115 | 一或多個指定的內容參數不正確。 |
One or more of the specified context parameters was not valid. |
| 0x80290116 | 指定的資料不像是有效的金鑰 blob |
The data given does not appear to be a valid key blob |
| 0x80290117 | 指定的 PCR 資料不正確。 |
The specified PCR data was invalid. |
| 0x80290118 | 擁有者驗證資料的格式不正確。 |
The format of the owner auth data was invalid. |
| 0x80290119 | 產生的隨機數字並未通過 FIPS RNG 檢查。 |
The random number generated did not pass FIPS RNG check. |
| 0x8029011A | TCG 事件記錄檔未包含任何資料。 |
The TCG Event Log does not contain any data. |
| 0x8029011B | TCG 事件記錄檔中的項目不正確。 |
An entry in the TCG Event Log was invalid. |
| 0x8029011C | 找不到 TCG 分隔頁。 |
A TCG Separator was not found. |
| 0x8029011D | TCG 記錄項目的摘要值不符合雜湊資料。 |
A digest value in a TCG Log entry did not match hashed data. |
| 0x8029011E | 目前的 TPM 原則封鎖了要求的作業。請連絡您的系統管理員以尋求協助。 |
The requested operation was blocked by current TPM policy. Please contact your system administrator for assistance. |
| 0x80290201 | 無法清除內容。 |
The context could not be cleaned up. |
| 0x80290202 | 指定的內容控制代碼無效。 |
The specified context handle is invalid. |
| 0x80290203 | 指定的內容參數無效。 |
An invalid context parameter was specified. |
| 0x80290204 | 與 TPM 通訊時發生錯誤 |
An error occurred while communicating with the TPM |
| 0x80290205 | 找不到指定金鑰的項目。 |
No entry with the specified key was found. |
| 0x80290206 | 指定的虛擬控制代碼符合已在使用中的虛擬控制代碼。 |
The specified virtual handle matches a virtual handle already in use. |
| 0x80290207 | 已傳回之控制代碼位置的指標是 NULL 或不正確 |
The pointer to the returned handle location was NULL or invalid |
| 0x80290208 | 一或多個參數不正確 |
One or more parameters is invalid |
| 0x80290209 | RPC 子系統無法初始化。 |
The RPC subsystem could not be initialized. |
| 0x8029020A | TBS 排程器並未執行。 |
The TBS scheduler is not running. |
| 0x8029020C | 記憶體不足，無法滿足要求 |
There was not enough memory to fulfill the request |
| 0x8029020D | 指定的清單是空的，或是重複項目已達清單結尾。 |
The specified list is empty, or the iteration has reached the end of the list. |
| 0x8029020E | 在清單中找不到指定的項目。 |
The specified item was not found in the list. |
| 0x8029020F | TPM 沒有足夠的空間可以載入要求的資源。 |
The TPM does not have enough space to load the requested resource. |
| 0x80290210 | 有太多 TPM 內容正在使用中。 |
There are too many TPM contexts in use. |
| 0x80290211 | TPM 命令失敗。 |
The TPM command failed. |
| 0x80290212 | TBS 無法識別指定的序數。 |
The TBS does not recognize the specified ordinal. |
| 0x80290213 | 要求的資源已無法使用。 |
The requested resource is no longer available. |
| 0x80290214 | 資源類型不相符。 |
The resource type did not match. |
| 0x80290215 | 沒有可解除載入的資源。 |
No resources can be unloaded. |
| 0x80290216 | 沒有任何新項目可新增到雜湊資料表中。 |
No new entries can be added to the hash table. |
| 0x80290217 | 因為開啟的範圍太多，所以無法建立新的 TBS 範圍。 |
A new TBS context could not be created because there are too many open contexts. |
| 0x8029021A | TBS 與在該系統上找到的 TPM 版本不相容。 |
TBS is not compatible with the version of TPM found on the system. |
| 0x80290300 | 嘗試取得 BIOS 對於 Physical Presence 命令的回應時發現一般錯誤。 |
A general error was detected when attempting to acquire the BIOS's response to a Physical Presence command. |
| 0x80290301 | 使用者無法確認 TPM 操作要求。 |
The user failed to confirm the TPM operation request. |
| 0x80290302 | BIOS 失敗導致無法順利執行要求的 TPM 操作 (例如: 不正確的 TPM 操作要求、BIOS 與 TPM 之間的通訊錯誤)。 |
The BIOS failure prevented the successful execution of the requested TPM operation (e.g. invalid TPM operation request, BIOS communication error with the TPM). |
| 0x80290303 | BIOS 不支援實體操作介面。 |
The BIOS does not support the physical presence interface. |
| 0x80290304 | 目前的 BIOS 設定封鎖了實際存在 (Physical Presence) 命令。系統擁有者可以重新設定 BIOS 設定以允許該命令。 |
The Physical Presence command was blocked by current BIOS settings. The system owner may be able to reconfigure the BIOS settings to allow the command. |
| 0x80290400 | 這是用來將「平台密碼編譯提供者」錯誤轉換為 win 錯誤的錯誤遮罩。 |
This is an error mask to convert Platform Crypto Provider errors to win errors. |
| 0x80290401 | 「平台密碼編譯裝置」目前未就緒。它需要完整佈建才能作業。 |
The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational. |
| 0x80290402 | 提供給「平台密碼編譯提供者」的控制代碼無效。 |
The handle provided to the Platform Crypto Provider is invalid. |
| 0x80290403 | 提供給「平台密碼編譯提供者」的參數無效。 |
A parameter provided to the Platform Crypto Provider is invalid. |
| 0x80290404 | 不支援提供給「平台密碼編譯提供者」的旗標。 |
A provided flag to the Platform Crypto Provider is not supported. |
| 0x80290405 | 此「平台密碼編譯提供者」不支援要求的作業。 |
The requested operation is not supported by this Platform Crypto Provider. |
| 0x80290406 | 緩衝區太小，無法包含所有資料。未將資訊寫入至緩衝區。 |
The buffer is too small to contain all data. No information has been written to the buffer. |
| 0x80290407 | 「平台密碼編譯提供者」中發生意外的內部錯誤。 |
An unexpected internal error has occurred in the Platform Crypto Provider. |
| 0x80290408 | 使用提供者物件的授權失敗。 |
The authorization to use a provider object has failed. |
| 0x80290409 | 「平台密碼編譯裝置」已忽略提供者物件的授權，以避免字典攻擊。 |
The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack. |
| 0x8029040A | 找不到參照的原則。 |
The referenced policy was not found. |
| 0x8029040B | 找不到參照的設定檔。 |
The referenced profile was not found. |
| 0x8029040E | 嘗試在不正確的存放裝置父系匯入或載入金鑰。 |
An attempt was made to import or load a key under an incorrect storage parent. |
| 0x8029040F | 未載入 TPM 金鑰。 |
The TPM key is not loaded. |
| 0x80290410 | 尚未產生 TPM 金鑰認證。 |
The TPM key certification has not been generated. |
| 0x80290411 | TPM 金鑰尚未完成。 |
The TPM key is not yet finalized. |
| 0x80290412 | 未設定 TPM 證明挑戰。 |
The TPM attestation challenge is not set. |
| 0x80290413 | TPM PCR 資訊無法使用。 |
The TPM PCR info is not available. |
| 0x80290414 | 已完成 TPM 金鑰。 |
The TPM key is already finalized. |
| 0x80290415 | 不支援 TPM 金鑰使用原則。 |
The TPM key usage policy is not supported. |
| 0x80290416 | TPM 金鑰使用原則無效。 |
The TPM key usage policy is invalid. |
| 0x80290417 | 匯入 TPM 中的軟體金鑰發生問題。 |
There was a problem with the software key being imported into the TPM. |
| 0x80290418 | 未驗證 TPM 金鑰。 |
The TPM key is not authenticated. |
| 0x80290419 | TPM 金鑰不是 AIK。 |
The TPM key is not an AIK. |
| 0x8029041A | TPM 金鑰不是簽署金鑰。 |
The TPM key is not a signing key. |
| 0x8029041B | 已鎖定 TPM。 |
The TPM is locked out. |
| 0x8029041C | 要求的宣告類型不受支援。 |
The claim type requested is not supported. |
| 0x8029041D | TPM 版本不受支援。 |
TPM version is not supported. |
| 0x8029041E | 緩衝區長度不相符。 |
The buffer lengths do not match. |
| 0x80290500 | TPM 相關的網路作業遭封鎖，因為用戶端已啟用 Zero Exhaust 模式。 |
TPM related network operations are blocked as Zero Exhaust mode is enabled on client. |
| 0x802A0001 | 無法建立物件。 |
The object could not be created. |
| 0x802A0002 | 這個物件或擁有它的物件已呼叫關機。 |
Shutdown was already called on this object or the object that owns it. |
| 0x802A0003 | 在這種類型的回呼期間，無法呼叫這個方法。 |
This method cannot be called during this type of callback. |
| 0x802A0004 | 已封裝這個物件，因此不再允許這項變更。 |
This object has been sealed, so this change is no longer allowed. |
| 0x802A0005 | 不曾設定要求的值。 |
The requested value was never set. |
| 0x802A0006 | 無法判斷要求的值。 |
The requested value cannot be determined. |
| 0x802A0007 | 回呼傳回不正確的輸出參數。 |
A callback returned an invalid output parameter. |
| 0x802A0008 | 回呼傳回的是成功碼，而不是 S_OK 或 S_FALSE。 |
A callback returned a success code other than S_OK or S_FALSE. |
| 0x802A0009 | 應該由這個物件擁有的參數，目前是由不同的物件所擁有。 |
A parameter that should be owned by this object is owned by a different object. |
| 0x802A000A | 多個項目符合搜尋條件。 |
More than one item matched the search criteria. |
| 0x802A000B | 發生浮點溢位。 |
A floating-point overflow occurred. |
| 0x802A000C | 這個方法只能從建立物件的執行緒呼叫。 |
This method can only be called from the thread that created the object. |
| 0x802A0101 | 腳本目前已在排程中。 |
The storyboard is currently in the schedule. |
| 0x802A0102 | 腳本未播放。 |
The storyboard is not playing. |
| 0x802A0103 | 開始主要畫面可能出現在結束主要畫面之後。 |
The start keyframe might occur after the end keyframe. |
| 0x802A0104 | 到達開始主要畫面時，可能無法判定結束主要畫面時間。 |
It might not be possible to determine the end keyframe time when the start keyframe is reached. |
| 0x802A0105 | 腳本的兩個重複部分可能重疊。 |
Two repeated portions of a storyboard might overlap. |
| 0x802A0106 | 轉換已經新增至腳本。 |
The transition has already been added to a storyboard. |
| 0x802A0107 | 轉換尚未新增至腳本。 |
The transition has not been added to a storyboard. |
| 0x802A0108 | 這個轉換可能會遮到腳本中另一個轉換的開頭。 |
The transition might eclipse the beginning of another transition in the storyboard. |
| 0x802A0109 | 指定的時間比傳送給上次更新的時間更早。 |
The given time is earlier than the time passed to the last update. |
| 0x802A010A | 這個用戶端已經與計時器連線。 |
This client is already connected to a timer. |
| 0x802A010B | 傳遞的維度無效，或不符合物件的維度。 |
The passed dimension is invalid or does not match the object's dimension. |
| 0x802A010C | 新增的基元在內插運算持續期間或之後開始。 |
The added primitive begins at or beyond the duration of the interpolator. |
| 0x802A0201 | 無法完成該操作，因為正在關閉該視窗。 |
The operation cannot be completed because the window is being closed. |
| 0x80300002 | 找不到資料收集器集合工具。 |
Data Collector Set was not found. |
| 0x80300045 | 無法啟動資料收集器集合工具，因為資料夾數目太多。 |
Unable to start Data Collector Set because there are too many folders. |
| 0x80300070 | 可用磁碟空間不足，無法啟動資料收集器集合工具。 |
Not enough free disk space to start Data Collector Set. |
| 0x803000AA | 資料收集器集合工具或它的其中一個相依性已在使用中。 |
The Data Collector Set or one of its dependencies is already in use. |
| 0x803000B7 | 資料收集器集合工具已存在。 |
Data Collector Set already exists. |
| 0x80300101 | 屬性值衝突。 |
Property value conflict. |
| 0x80300102 | 此資料收集器集合工具的目前組態要求它只能包含一個資料收集器。 |
The current configuration for this Data Collector Set requires that it contain exactly one Data Collector. |
| 0x80300103 | 需要使用者帳戶，才能認可目前的資料收集器集合工具屬性。 |
A user account is required in order to commit the current Data Collector Set properties. |
| 0x80300104 | 資料收集器集合工具並未執行。 |
Data Collector Set is not running. |
| 0x80300105 | 在包含/排除 API 中發現衝突。請勿同時在包含清單與排除清單中指定相同的 API。 |
A conflict was detected in the list of include/exclude APIs. Do not specify the same API in both the include list and the exclude list. |
| 0x80300106 | 您指定的可執行檔路徑指向網路共用或 UNC 路徑。 |
The executable path you have specified refers to a network share or UNC path. |
| 0x80300107 | 您指定的可執行檔路徑已設定為用於 API 追蹤。 |
The executable path you have specified is already configured for API tracing. |
| 0x80300108 | 您指定的可執行檔路徑不存在。請確定指定的路徑正確。 |
The executable path you have specified does not exist. Verify that the specified path is correct. |
| 0x80300109 | 資料收集器已存在。 |
Data Collector already exists. |
| 0x8030010A | 等候資料收集器集合工具的開始通知逾時。 |
The wait for the Data Collector Set start notification has timed out. |
| 0x8030010B | 等候資料收集器開始逾時。 |
The wait for the Data Collector to start has timed out. |
| 0x8030010C | 等候報表產生工具完成逾時。 |
The wait for the report generation tool to finish has timed out. |
| 0x8030010D | 不允許重複項目。 |
Duplicate items are not allowed. |
| 0x8030010E | 指定您要追蹤的可執行檔時，必須指定可執行檔的完整路徑，不能只指定檔案名稱。 |
When specifying the executable that you want to trace, you must specify a full path to the executable and not just a filename. |
| 0x8030010F | 提供的工作階段名稱不正確。 |
The session name provided is invalid. |
| 0x80300110 | 必須啟用事件記錄檔通道 Microsoft-Windows-Diagnosis-PLA/Operational，才能執行此操作。 |
The Event Log channel Microsoft-Windows-Diagnosis-PLA/Operational must be enabled to perform this operation. |
| 0x80300111 | 必須啟用事件記錄檔通道 Microsoft-Windows-TaskScheduler，才能執行此操作。 |
The Event Log channel Microsoft-Windows-TaskScheduler must be enabled to perform this operation. |
| 0x80300112 | 執行規則管理員失敗。 |
The execution of the Rules Manager failed. |
| 0x80300113 | 嘗試壓縮或解壓縮資料時發生錯誤。 |
An error occurred while attempting to compress or extract the data. |
| 0x80310000 | 這個磁碟機已由 BitLocker 磁碟機加密鎖定。您必須至 [控制台] 解除鎖定這個磁碟機。 |
This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel. |
| 0x80310001 | 此磁碟機未加密。 |
This drive is not encrypted. |
| 0x80310002 | BIOS 並未正確與信賴平台模組 (TPM) 通訊。請連絡電腦製造商以取得 BIOS 升級指示。 |
The BIOS did not correctly communicate with the Trusted Platform Module (TPM). Contact the computer manufacturer for BIOS upgrade instructions. |
| 0x80310003 | BIOS 並未正確與主開機記錄 (MBR) 通訊。請連絡電腦製造商以取得 BIOS 升級指示。 |
The BIOS did not correctly communicate with the master boot record (MBR). Contact the computer manufacturer for BIOS upgrade instructions. |
| 0x80310004 | 必要的 TPM 測量遺失。如果您的電腦上有可開機 CD 或 DVD，請移除它並重新啟動電腦，然後再次開啟 BitLocker。如果問題持續發生，請確認主開機記錄是最新的。 |
A required TPM measurement is missing. If there is a bootable CD or DVD in your computer, remove it, restart the computer, and turn on BitLocker again. If the problem persists, ensure the master boot record is up to date. |
| 0x80310005 | 此磁碟機的開機磁區與 BitLocker 磁碟機加密不相容。請使用 Windows 修復環境中的 Bootrec.exe 工具來更新或修復開機管理程式 (BOOTMGR)。 |
The boot sector of this drive is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR). |
| 0x80310006 | 此作業系統的開機管理程式與 BitLocker 磁碟機加密不相容。請使用 Windows 修復環境中的 Bootrec.exe 工具來更新或修復開機管理程式 (BOOTMGR)。 |
The boot manager of this operating system is not compatible with BitLocker Drive Encryption. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot manager (BOOTMGR). |
| 0x80310007 | 至少需要一個安全金鑰保護裝置才能執行此操作。 |
At least one secure key protector is required for this operation to be performed. |
| 0x80310008 | 此磁碟機上沒有啟用 BitLocker 磁碟機加密。請開啟 BitLocker。 |
BitLocker Drive Encryption is not enabled on this drive. Turn on BitLocker. |
| 0x80310009 | BitLocker 磁碟機加密無法執行要求的動作。兩個要求同時發出時，就可能會發生這種情況。請稍候數分鐘，然後再嘗試該動作。 |
BitLocker Drive Encryption cannot perform the requested action. This condition may occur when two requests are issued at the same time. Wait a few moments and then try the action again. |
| 0x8031000A | Active Directory 網域服務樹系未包含必要的屬性與類別以裝載 BitLocker 磁碟機加密或信賴平台模組資訊。請連絡網域系統管理員，確認已安裝所有必要的 BitLocker Active Directory 架構延伸。 |
The Active Directory Domain Services forest does not contain the required attributes and classes to host BitLocker Drive Encryption or Trusted Platform Module information. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed. |
| 0x8031000B | 從 Active Directory 取得的資料類型並非預期的資料類型。BitLocker 修復資訊可能已遺失或損毀。 |
The type of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted. |
| 0x8031000C | 從 Active Directory 取得的資料大小並非預期的資料大小。BitLocker 修復資訊可能已遺失或損毀。 |
The size of the data obtained from Active Directory was not expected. The BitLocker recovery information may be missing or corrupted. |
| 0x8031000D | 從 Active Directory 讀取的屬性中沒有包含任何值。BitLocker 修復資訊可能已遺失或損毀。 |
The attribute read from Active Directory does not contain any values. The BitLocker recovery information may be missing or corrupted. |
| 0x8031000E | 屬性未設定。請確認您用來登入的網域帳戶具有將資訊寫入 Active Directory 物件的能力。 |
The attribute was not set. Verify that you are logged on with a domain account that has the ability to write information to Active Directory objects. |
| 0x8031000F | Active Directory 網域服務中找不到指定的屬性。請連絡網域系統管理員，確認已安裝所有必要的 BitLocker Active Directory 架構延伸。 |
The specified attribute cannot be found in Active Directory Domain Services. Contact your domain administrator to verify that any required BitLocker Active Directory schema extensions have been installed. |
| 0x80310010 | 加密磁碟機的 BitLocker 中繼資料無效。您可以嘗試修復該磁碟機以還原存取權。 |
The BitLocker metadata for the encrypted drive is not valid. You can attempt to repair the drive to restore access. |
| 0x80310011 | 磁碟機無法加密，因為該磁碟機上的可用空間不足。請刪除磁碟機上所有不需要的資料以建立額外的可用空間，然後再試一次。 |
The drive cannot be encrypted because it does not have enough free space. Delete any unnecessary data on the drive to create additional free space and then try again. |
| 0x80310012 | 磁碟機無法加密，因為其中包含系統開機資訊。請分別建立一個做為系統磁碟機的磁碟分割 (包含開機資訊)，以及另一個做為作業系統磁碟機的磁碟分割，然後加密作業系統磁碟機。 |
The drive cannot be encrypted because it contains system boot information. Create a separate partition for use as the system drive that contains the boot information and a second partition for use as the operating system drive and then encrypt the operating system drive. |
| 0x80310013 | 無法加密磁碟機，因為不支援該檔案系統。 |
The drive cannot be encrypted because the file system is not supported. |
| 0x80310014 | 檔案系統大小超過磁碟分割表格中的磁碟分割大小。此磁碟機可能已損毀或遭竄改。若要用於 BitLocker，您必須重新格式化磁碟分割。 |
The file system size is larger than the partition size in the partition table. This drive may be corrupt or may have been tampered with. To use it with BitLocker, you must reformat the partition. |
| 0x80310015 | 此磁碟機無法加密。 |
This drive cannot be encrypted. |
| 0x80310017 | 指定的資料磁碟機未在目前的電腦上設定為自動解除鎖定，因此無法自動解除鎖定。 |
The data drive specified is not set to automatically unlock on the current computer and cannot be unlocked automatically. |
| 0x80310018 | 您必須先初始化信賴平台模組 (TPM)，才能使用 BitLocker 磁碟機加密。 |
You must initialize the Trusted Platform Module (TPM) before you can use BitLocker Drive Encryption. |
| 0x80310019 | 嘗試的操作無法在作業系統磁碟機上執行。 |
The operation attempted cannot be performed on an operating system drive. |
| 0x8031001A | 提供給函數的緩衝區不足以包含傳回的資料。再次執行該函數之前，請先增加緩衝區大小。 |
The buffer supplied to a function was insufficient to contain the returned data. Increase the buffer size before running the function again. |
| 0x8031001B | 轉換磁碟機時發生讀取操作失敗。該磁碟機尚未轉換。請重新啟用 BitLocker。 |
A read operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker. |
| 0x8031001C | 轉換磁碟機時發生寫入操作失敗。該磁碟機尚未轉換。請重新啟用 BitLocker。 |
A write operation failed while converting the drive. The drive was not converted. Please re-enable BitLocker. |
| 0x8031001D | 需要一或多個 BitLocker 金鑰保護裝置。您不能刪除此磁碟機的最後一個金鑰。 |
One or more BitLocker key protectors are required. You cannot delete the last key on this drive. |
| 0x8031001E | BitLocker 磁碟機加密不支援叢集設定。 |
Cluster configurations are not supported by BitLocker Drive Encryption. |
| 0x8031001F | 指定的磁碟機已設定為在目前的電腦上自動解除鎖定。 |
The drive specified is already configured to be automatically unlocked on the current computer. |
| 0x80310020 | 作業系統磁碟機不受 BitLocker 磁碟機加密保護。 |
The operating system drive is not protected by BitLocker Drive Encryption. |
| 0x80310021 | 已在此磁碟機暫停 BitLocker 磁碟機加密。為此磁碟機設定的所有 BitLocker 金鑰保護裝置已有效地停用，該磁碟機將使用未加密 (清除) 金鑰來自動解除鎖定。 |
BitLocker Drive Encryption has been suspended on this drive. All BitLocker key protectors configured for this drive are effectively disabled, and the drive will be automatically unlocked using an unencrypted (clear) key. |
| 0x80310022 | 因為 BitLocker 保護目前已暫停，所以您嘗試鎖定的磁碟機沒有可用來加密的金鑰保護裝置。請重新啟用 BitLocker 以鎖定此磁碟機。 |
The drive you are attempting to lock does not have any key protectors available for encryption because BitLocker protection is currently suspended. Re-enable BitLocker to lock this drive. |
| 0x80310023 | BitLocker 無法使用信賴平台模組 (TPM) 來保護資料磁碟機。TPM 保護只能用於作業系統磁碟機。 |
BitLocker cannot use the Trusted Platform Module (TPM) to protect a data drive. TPM protection can only be used with the operating system drive. |
| 0x80310024 | 加密磁碟機的 BitLocker 中繼資料無法更新，因為它已由另一個處理程序鎖定以進行更新。請重試此處理程序。 |
The BitLocker metadata for the encrypted drive cannot be updated because it was locked for updating by another process. Please try this process again. |
| 0x80310025 | 信賴平台模組 (TPM) 之儲存根金鑰 (SRK) 的授權資料不是零，因而與 BitLocker 不相容。請先初始化 TPM，然後再用於 BitLocker。 |
The authorization data for the storage root key (SRK) of the Trusted Platform Module (TPM) is not zero and is therefore incompatible with BitLocker. Please initialize the TPM before attempting to use it with BitLocker. |
| 0x80310026 | 無法在此大小的磁區上使用磁碟機加密演算法。 |
The drive encryption algorithm cannot be used on this sector size. |
| 0x80310027 | 提供的金鑰無法解除鎖定磁碟機。請確認您提供的金鑰是正確的，然後再試一次。 |
The drive cannot be unlocked with the key provided. Confirm that you have provided the correct key and try again. |
| 0x80310028 | 指定的磁碟機不是作業系統磁碟機。 |
The drive specified is not the operating system drive. |
| 0x80310029 | 與此電腦關聯的固定資料磁碟機和抽取式資料磁碟機停用自動解除鎖定功能後，才能在作業系統磁碟機上關閉 BitLocker 磁碟機加密。 |
BitLocker Drive Encryption cannot be turned off on the operating system drive until the auto unlock feature has been disabled for the fixed data drives and removable data drives associated with this computer. |
| 0x8031002A | 系統磁碟分割開機磁區未執行信賴平台模組 (TPM) 測量。請使用 Windows 修復環境中的 Bootrec.exe 工具來更新或修復開機磁區。 |
The system partition boot sector does not perform Trusted Platform Module (TPM) measurements. Use the Bootrec.exe tool in the Windows Recovery Environment to update or repair the boot sector. |
| 0x8031002B | BitLocker 磁碟機加密作業系統磁碟機必須以 NTFS 檔案系統格式化才能加密。請將磁碟機轉換為 NTFS，然後開啟 BitLocker。 |
BitLocker Drive Encryption operating system drives must be formatted with the NTFS file system in order to be encrypted. Convert the drive to NTFS, and then turn on BitLocker. |
| 0x8031002C | 群組原則設定要求加密磁碟機之前，必須先指定修復密碼。 |
Group Policy settings require that a recovery password be specified before encrypting the drive. |
| 0x8031002D | 先前加密的磁碟機上無法設定磁碟機加密演算法與金鑰。若要以 BitLocker 磁碟機加密來加密此磁碟機，請移除先前的加密，然後開啟 BitLocker。 |
The drive encryption algorithm and key cannot be set on a previously encrypted drive. To encrypt this drive with BitLocker Drive Encryption, remove the previous encryption and then turn on BitLocker. |
| 0x8031002E | BitLocker 磁碟機加密無法加密指定的磁碟機，因為沒有加密金鑰。請新增金鑰保護裝置以加密此磁碟機。 |
BitLocker Drive Encryption cannot encrypt the specified drive because an encryption key is not available. Add a key protector to encrypt this drive. |
| 0x80310030 | BitLocker 磁碟機加密在電腦中偵測到可開機媒體 (CD 或 DVD)。請在設定 BitLocker 之前先移除該媒體，然後重新啟動電腦。 |
BitLocker Drive Encryption detected bootable media (CD or DVD) in the computer. Remove the media and restart the computer before configuring BitLocker. |
| 0x80310031 | 無法新增此金鑰保護裝置。此磁碟機只允許一個此類型的金鑰保護裝置。 |
This key protector cannot be added. Only one key protector of this type is allowed for this drive. |
| 0x80310032 | 找不到修復密碼檔，因為指定了相對路徑。修復密碼必須儲存至完整合格路徑中。路徑中可以使用電腦中設定的環境變數。 |
The recovery password file was not found because a relative path was specified. Recovery passwords must be saved to a fully qualified path. Environment variables configured on the computer can be used in the path. |
| 0x80310033 | 磁碟機上找不到指定的金鑰保護裝置。請嘗試其他的金鑰保護裝置。 |
The specified key protector was not found on the drive. Try another key protector. |
| 0x80310034 | 提供的修復金鑰已損毀，無法用來存取磁碟機。您必須使用其他的修復方法 (例如，修復密碼、資料修復代理或修復金鑰的備份版本) 來修復對該磁碟機的存取。 |
The recovery key provided is corrupt and cannot be used to access the drive. An alternative recovery method, such as recovery password, a data recovery agent, or a backup version of the recovery key must be used to recover access to the drive. |
| 0x80310035 | 提供的修復密碼格式無效。BitLocker 修復密碼為 48 位數。請確認修復密碼的格式正確，然後再試一次。 |
The format of the recovery password provided is invalid. BitLocker recovery passwords are 48 digits. Verify that the recovery password is in the correct format and then try again. |
| 0x80310036 | 隨機數字產生器檢查測試失敗。 |
The random number generator check test failed. |
| 0x80310037 | 要求 FIPS 相容的群組原則設定會防止 BitLocker 磁碟機加密產生或使用本機修復密碼。在 FIPS 相容模式中操作時，BitLocker 修復選項可以是儲存在 USB 磁碟機中的修復金鑰，或是透過資料修復代理來修復。 |
The Group Policy setting requiring FIPS compliance prevents a local recovery password from being generated or used by BitLocker Drive Encryption. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent. |
| 0x80310038 | 要求 FIPS 相容的群組原則設定會防止修復密碼儲存至 Active Directory 中。在 FIPS 相容模式中操作時，BitLocker 修復選項可以是儲存在 USB 磁碟機中的修復金鑰，或是透過資料修復代理來修復。請檢查您的群組原則設定。 |
The Group Policy setting requiring FIPS compliance prevents the recovery password from being saved to Active Directory. When operating in FIPS-compliant mode, BitLocker recovery options can be either a recovery key stored on a USB drive or recovery through a data recovery agent. Check your Group Policy settings configuration. |
| 0x80310039 | 必須將磁碟機完全解密才能完成此操作。 |
The drive must be fully decrypted to complete this operation. |
| 0x8031003A | 指定的金鑰保護裝置無法在此操作中使用。 |
The key protector specified cannot be used for this operation. |
| 0x8031003B | 磁碟機上沒有金鑰保護裝置，無法執行硬體測試。 |
No key protectors exist on the drive to perform the hardware test. |
| 0x8031003C | USB 裝置上找不到 BitLocker 啟動金鑰或修復密碼。請確定使用的是正確的 USB 裝置 (該 USB 裝置已插入電腦的有效 USB 連接埠)，重新啟動電腦，然後再試一次。如果問題仍然存在，請連絡電腦製造商以取得 BIOS 升級指示。 |
The BitLocker startup key or recovery password cannot be found on the USB device. Verify that you have the correct USB device, that the USB device is plugged into the computer on an active USB port, restart the computer, and then try again. If the problem persists, contact the computer manufacturer for BIOS upgrade instructions. |
| 0x8031003D | 提供的 BitLocker 啟動金鑰或修復密碼檔已損毀或不正確。請確定您有正確的啟動金鑰或修復密碼檔，然後再試一次。 |
The BitLocker startup key or recovery password file provided is corrupt or invalid. Verify that you have the correct startup key or recovery password file and try again. |
| 0x8031003E | 無法從啟動金鑰或修復密碼取得 BitLocker 加密金鑰。請確定您有正確的啟動金鑰或修復密碼，然後再試一次。 |
The BitLocker encryption key cannot be obtained from the startup key or recovery password. Verify that you have the correct startup key or recovery password and try again. |
| 0x8031003F | 已停用信賴平台模組 (TPM)。TPM 必須啟用、初始化並具備有效的擁有權，才能與 BitLocker 磁碟機加密搭配使用。 |
The Trusted Platform Module (TPM) is disabled. The TPM must be enabled, initialized, and have valid ownership before it can be used with BitLocker Drive Encryption. |
| 0x80310040 | 無法管理指定磁碟機的 BitLocker 設定，因為此電腦目前以安全模式操作。處於安全模式時，BitLocker 磁碟機加密只能用於修復用途。 |
The BitLocker configuration of the specified drive cannot be managed because this computer is currently operating in Safe Mode. While in Safe Mode, BitLocker Drive Encryption can only be used for recovery purposes. |
| 0x80310041 | 信賴平台模組 (TPM) 無法解除鎖定磁碟機。可能是系統開機資訊在選擇 BitLocker 設定之後變更，或是 PIN 不相符。如果嘗試數次後問題仍未解決，代表可能有硬體或韌體問題。 |
The Trusted Platform Module (TPM) was unable to unlock the drive. Either the system boot information changed after choosing BitLocker settings or the PIN did not match. If the problem persists after several tries, there may be a hardware or firmware problem. |
| 0x80310042 | 無法從信賴平台模組 (TPM) 取得 BitLocker 加密金鑰。 |
The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM). |
| 0x80310043 | 無法從信賴平台模組 (TPM) 與 PIN 取得 BitLocker 加密金鑰。 |
The BitLocker encryption key cannot be obtained from the Trusted Platform Module (TPM) and PIN. |
| 0x80310044 | 自啟用 BitLocker 磁碟機加密以來，已變更開機應用程式。 |
A boot application has changed since BitLocker Drive Encryption was enabled. |
| 0x80310045 | 自啟用 BitLocker 磁碟機加密以來，已變更開機設定資料 (BCD) 設定。 |
The Boot Configuration Data (BCD) settings have changed since BitLocker Drive Encryption was enabled. |
| 0x80310046 | 要求 FIPS 相容的群組原則設定會禁止使用未加密金鑰，這會讓 BitLocker 無法在此磁碟機上暫停。如需詳細資訊，請連絡網域系統管理員。 |
The Group Policy setting requiring FIPS compliance prohibits the use of unencrypted keys, which prevents BitLocker from being suspended on this drive. Please contact your domain administrator for more information. |
| 0x80310047 | BitLocker 磁碟機加密無法加密此磁碟機，因為檔案系統未延伸到磁碟機結尾。請重新分割此磁碟機，然後再試一次。 |
This drive cannot be encrypted by BitLocker Drive Encryption because the file system does not extend to the end of the drive. Repartition this drive and then try again. |
| 0x80310048 | 無法在作業系統磁碟機上啟用 BitLocker 磁碟機加密。請連絡電腦製造商以取得 BIOS 升級指示。 |
BitLocker Drive Encryption cannot be enabled on the operating system drive. Contact the computer manufacturer for BIOS upgrade instructions. |
| 0x80310049 | 此 Windows 版本不包括 BitLocker 磁碟機加密。若要使用 BitLocker 磁碟機加密，請升級您的作業系統。 |
This version of Windows does not include BitLocker Drive Encryption. To use BitLocker Drive Encryption, please upgrade the operating system. |
| 0x8031004A | 無法使用 BitLocker 磁碟機加密，因為重要的 BitLocker 系統檔案遺失或損毀。請使用 Windows 啟動修復來將這些檔案還原到您的電腦。 |
BitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted. Use Windows Startup Repair to restore these files to your computer. |
| 0x8031004B | 當磁碟機正在使用中時，無法鎖定該磁碟機。 |
The drive cannot be locked when the drive is in use. |
| 0x8031004C | 與目前的執行緒關聯的存取權杖不是模擬的權杖。 |
The access token associated with the current thread is not an impersonated token. |
| 0x8031004D | 無法取得 BitLocker 加密金鑰。請確定信賴平台模組 (TPM) 已啟用，而且擁有權已經被取得。如果此電腦沒有 TPM，請確定 USB 磁碟機已經插入並可使用。 |
The BitLocker encryption key cannot be obtained. Verify that the Trusted Platform Module (TPM) is enabled and ownership has been taken. If this computer does not have a TPM, verify that the USB drive is inserted and available. |
| 0x8031004E | 繼續使用 BitLocker 磁碟機加密之前，您必須先重新啟動電腦。 |
You must restart your computer before continuing with BitLocker Drive Encryption. |
| 0x8031004F | 啟用開機偵錯時無法進行磁碟機加密。請使用 bcdedit 命令列工具關閉開機偵錯。 |
Drive encryption cannot occur while boot debugging is enabled. Use the bcdedit command-line tool to turn off boot debugging. |
| 0x80310050 | 未執行任何動作，因為 BitLocker 磁碟機加密目前是原生存取模式。 |
No action was taken as BitLocker Drive Encryption is in raw access mode. |
| 0x80310051 | BitLocker 磁碟機加密無法進入此磁碟機的原生存取模式，因為該磁碟機目前正在使用中。 |
BitLocker Drive Encryption cannot enter raw access mode for this drive because the drive is currently in use. |
| 0x80310052 | 在開機設定資料 (BCD) 中針對 BitLocker 磁碟機加密完整性保護應用程式指定的路徑不正確。請檢查並更正您的 BCD 設定，然後再試一次。 |
The path specified in the Boot Configuration Data (BCD) for a BitLocker Drive Encryption integrity-protected application is incorrect. Please verify and correct your BCD settings and try again. |
| 0x80310053 | 當電腦執行的是安裝前或修復環境時，BitLocker 磁碟機加密只能用於有限的佈建或修復用途。 |
BitLocker Drive Encryption can only be used for limited provisioning or recovery purposes when the computer is running in pre-installation or recovery environments. |
| 0x80310054 | 作業系統磁碟機中沒有自動解除鎖定主要金鑰。 |
The auto-unlock master key was not available from the operating system drive. |
| 0x80310055 | 系統韌體無法在重新啟動電腦時啟用清除系統記憶體。 |
The system firmware failed to enable clearing of system memory when the computer was restarted. |
| 0x80310056 | 無法加密隱藏的磁碟機。 |
The hidden drive cannot be encrypted. |
| 0x80310057 | 已略過 BitLocker 加密金鑰，因為該磁碟機處於暫時狀態。 |
BitLocker encryption keys were ignored because the drive was in a transient state. |
| 0x80310058 | 此磁碟機不允許公開金鑰保護裝置。 |
Public key based protectors are not allowed on this drive. |
| 0x80310059 | BitLocker 磁碟機加密已經在此磁碟機上執行操作。繼續之前，請先完成所有操作。 |
BitLocker Drive Encryption is already performing an operation on this drive. Please complete all operations before continuing. |
| 0x8031005A | 此 Windows 版本不支援 BitLocker 磁碟機加密的此功能。若要啟用此功能，請升級作業系統。 |
This version of Windows does not support this feature of BitLocker Drive Encryption. To use this feature, upgrade the operating system. |
| 0x8031005B | BitLocker 啟動選項的群組原則設定發生衝突，無法套用。如需詳細資訊，請連絡系統管理員。 |
The Group Policy settings for BitLocker startup options are in conflict and cannot be applied. Contact your system administrator for more information. |
| 0x8031005C | 群組原則設定不允許建立修復密碼。 |
Group Policy settings do not permit the creation of a recovery password. |
| 0x8031005D | 群組原則設定要求建立修復密碼。 |
Group Policy settings require the creation of a recovery password. |
| 0x8031005E | 群組原則設定不允許建立修復金鑰。 |
Group Policy settings do not permit the creation of a recovery key. |
| 0x8031005F | 群組原則設定要求建立修復金鑰。 |
Group Policy settings require the creation of a recovery key. |
| 0x80310060 | 群組原則設定不允許在啟動時使用 PIN。請選擇其他 BitLocker 啟動選項。 |
Group Policy settings do not permit the use of a PIN at startup. Please choose a different BitLocker startup option. |
| 0x80310061 | 群組原則設定要求在啟動時使用 PIN。請選擇此 BitLocker 啟動選項。 |
Group Policy settings require the use of a PIN at startup. Please choose this BitLocker startup option. |
| 0x80310062 | 群組原則設定不允許使用啟動金鑰。請選擇其他 BitLocker 啟動選項。 |
Group Policy settings do not permit the use of a startup key. Please choose a different BitLocker startup option. |
| 0x80310063 | 群組原則設定要求使用啟動金鑰。請選擇此 BitLocker 啟動選項。 |
Group Policy settings require the use of a startup key. Please choose this BitLocker startup option. |
| 0x80310064 | 群組原則設定不允許使用啟動金鑰與 PIN。請選擇其他 BitLocker 啟動選項。 |
Group Policy settings do not permit the use of a startup key and PIN. Please choose a different BitLocker startup option. |
| 0x80310065 | 群組原則設定要求使用啟動金鑰與 PIN。請選擇此 BitLocker 啟動選項。 |
Group Policy settings require the use of a startup key and PIN. Please choose this BitLocker startup option. |
| 0x80310066 | 群組原則不允許在啟動時只使用信賴平台模組 (TPM)。請選擇其他 BitLocker 啟動選項。 |
Group policy does not permit the use of TPM-only at startup. Please choose a different BitLocker startup option. |
| 0x80310067 | 群組原則設定要求在啟動時只能使用 TPM。請選擇此 BitLocker 啟動選項。 |
Group Policy settings require the use of TPM-only at startup. Please choose this BitLocker startup option. |
| 0x80310068 | 提供的 PIN 不符合最大或最小長度需求。 |
The PIN provided does not meet minimum or maximum length requirements. |
| 0x80310069 | 目前磁碟機上的 BitLocker 磁碟機加密版本不支援金鑰保護裝置。請升級磁碟機以新增金鑰保護裝置。 |
The key protector is not supported by the version of BitLocker Drive Encryption currently on the drive. Upgrade the drive to add the key protector. |
| 0x8031006A | 群組原則設定不允許建立密碼。 |
Group Policy settings do not permit the creation of a password. |
| 0x8031006B | 群組原則設定要求建立密碼。 |
Group Policy settings require the creation of a password. |
| 0x8031006C | 要求 FIPS 相容的群組原則設定會防止產生或使用密碼。如需詳細資訊，請連絡系統管理員。 |
The Group Policy setting requiring FIPS compliance prevents passwords from being generated or used. Please contact your system administrator for more information. |
| 0x8031006D | 密碼無法新增至作業系統磁碟機。 |
A password cannot be added to the operating system drive. |
| 0x8031006E | 磁碟機上的 BitLocker 物件識別碼 (OID) 不正確或已損毀。請使用 manage-BDE 來重設此磁碟機上的 OID。 |
The BitLocker object identifier (OID) on the drive appears to be invalid or corrupt. Use manage-BDE to reset the OID on this drive. |
| 0x8031006F | 磁碟機太小而無法使用 BitLocker 磁碟機加密予以保護。 |
The drive is too small to be protected using BitLocker Drive Encryption. |
| 0x80310070 | 選取的探索磁碟機類型與磁碟機上的檔案系統不相容。BitLocker To Go 探索磁碟機必須建立於 FAT 格式的磁碟機上。 |
The selected discovery drive type is incompatible with the file system on the drive. BitLocker To Go discovery drives must be created on FAT formatted drives. |
| 0x80310071 | 電腦的群組原則設定不允許選取的探索磁碟機類型。請確定群組原則設定允許建立可與 BitLocker To Go 搭配使用的探索磁碟機。 |
The selected discovery drive type is not allowed by the computer's Group Policy settings. Verify that Group Policy settings allow the creation of discovery drives for use with BitLocker To Go. |
| 0x80310072 | 群組原則設定不允許使用者憑證 (例如，智慧卡) 與 BitLocker 磁碟機加密搭配使用。 |
Group Policy settings do not permit user certificates such as smart cards to be used with BitLocker Drive Encryption. |
| 0x80310073 | 群組原則設定要求您具備可與 BitLocker 磁碟機加密搭配使用的有效使用者憑證 (例如，智慧卡)。 |
Group Policy settings require that you have a valid user certificate, such as a smart card, to be used with BitLocker Drive Encryption. |
| 0x80310074 | 群組原則設定要求您使用可與 BitLocker 磁碟機加密搭配使用的智慧卡金鑰保護裝置。 |
Group Policy settings requires that you use a smart card-based key protector with BitLocker Drive Encryption. |
| 0x80310075 | 群組原則設定不允許受 BitLocker 保護的固定資料磁碟機自動解除鎖定。 |
Group Policy settings do not permit BitLocker-protected fixed data drives to be automatically unlocked. |
| 0x80310076 | 群組原則設定不允許受 BitLocker 保護的抽取式資料磁碟機自動解除鎖定。 |
Group Policy settings do not permit BitLocker-protected removable data drives to be automatically unlocked. |
| 0x80310077 | 群組原則設定不允許您在抽取式資料磁碟機上設定 BitLocker 磁碟機加密。 |
Group Policy settings do not permit you to configure BitLocker Drive Encryption on removable data drives. |
| 0x80310078 | 群組原則設定不允許您在抽取式資料磁碟機上開啟 BitLocker 磁碟機加密。如果您需要開啟 BitLocker，請連絡系統管理員。 |
Group Policy settings do not permit you to turn on BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn on BitLocker. |
| 0x80310079 | 群組原則設定不允許在抽取式資料磁碟機上關閉 BitLocker 磁碟機加密。如果您需要關閉 BitLocker，請連絡系統管理員。 |
Group Policy settings do not permit turning off BitLocker Drive Encryption on removable data drives. Please contact your system administrator if you need to turn off BitLocker. |
| 0x80310080 | 您的密碼不符合最小長度需求。根據預設，密碼的長度至少必須為 8 個字元。請連絡系統管理員以取得組織的密碼長度需求。 |
Your password does not meet minimum password length requirements. By default, passwords must be at least 8 characters in length. Check with your system administrator for the password length requirement in your organization. |
| 0x80310081 | 密碼不符合系統管理員設定的複雜性需求。請嘗試新增大小寫字元、數字和符號。 |
Your password does not meet the complexity requirements set by your system administrator. Try adding upper and lowercase characters, numbers, and symbols. |
| 0x80310082 | 此磁碟機保留給 Windows 系統復原選項使用，因此無法加密。 |
This drive cannot be encrypted because it is reserved for Windows System Recovery Options. |
| 0x80310083 | BitLocker 磁碟機加密無法套用至此磁碟機，因為群組原則設定發生衝突。使用者修復選項停用時，BitLocker 無法設定為自動解除鎖定固定資料磁碟機。如果您要受 BitLocker 保護的固定資料磁碟機在金鑰驗證之後自動解除鎖定，請在啟用 BitLocker 之前，先要求系統管理員解決設定衝突。 |
BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock fixed data drives when user recovery options are disabled. If you want BitLocker-protected fixed data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker. |
| 0x80310084 | BitLocker 磁碟機加密無法套用至此磁碟機，因為群組原則設定發生衝突。使用者修復選項停用時，BitLocker 無法設定為自動解除鎖定抽取式資料磁碟機。如果您要受 BitLocker 保護的抽取式資料磁碟機在金鑰驗證之後自動解除鎖定，請在啟用 BitLocker 之前，先要求系統管理員解決設定衝突。 |
BitLocker Drive Encryption cannot be applied to this drive because of conflicting Group Policy settings. BitLocker cannot be configured to automatically unlock removable data drives when user recovery option are disabled. If you want BitLocker-protected removable data drives to be automatically unlocked after key validation has occurred, please ask your system administrator to resolve the settings conflict before enabling BitLocker. |
| 0x80310085 | 指定憑證的增強金鑰使用方法 (EKU) 屬性不允許該憑證用於 BitLocker 磁碟機加密。BitLocker 不要求憑證須具備 EKU 屬性，但若已設定該屬性，必須將該屬性的物件識別碼 (OID) 設定為符合對 BitLocker 所設定的 OID。 |
The Enhanced Key Usage (EKU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have an EKU attribute, but if one is configured it must be set to an object identifier (OID) that matches the OID configured for BitLocker. |
| 0x80310086 | BitLocker 磁碟機加密因目前的群組原則設定而無法套用至此磁碟機。為磁碟機加密提供的憑證為自我簽署憑證。目前的群組原則設定不允許使用自我簽署憑證。請在嘗試啟用 BitLocker 之前，先從憑證授權單位取得新的憑證。 |
BitLocker Drive Encryption cannot be applied to this drive as currently configured because of Group Policy settings. The certificate you provided for drive encryption is self-signed. Current Group Policy settings do not permit the use of self-signed certificates. Obtain a new certificate from your certification authority before attempting to enable BitLocker. |
| 0x80310087 | BitLocker 加密無法套用至此磁碟機，因為群組原則設定發生衝突。當未受 BitLocker 保護的磁碟機寫入權限遭到拒絕時，不能要求使用 USB 啟動金鑰。請在嘗試啟用 BitLocker 之前，先要求系統管理員解決這些原則衝突。 |
BitLocker Encryption cannot be applied to this drive because of conflicting Group Policy settings. When write access to drives not protected by BitLocker is denied, the use of a USB startup key cannot be required. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker. |
| 0x80310088 | BitLocker 磁碟機加密無法從突然終止的轉換中復原。這可能是因為所有的轉換記錄都已損毀，或該媒體有防寫保護。 |
BitLocker Drive Encryption failed to recover from an abruptly terminated conversion. This could be due to either all conversion logs being corrupted or the media being write-protected. |
| 0x80310089 | 要求的模擬大小太大。 |
The requested virtualization size is too big. |
| 0x80310090 | BitLocker 磁碟機加密無法套用至此磁碟機，因為作業系統磁碟機上修復選項的群組原則設定發生衝突。不允許產生修復密碼時，就不能要求將修復資訊儲存至 Active Directory 網域服務。請在嘗試啟用 BitLocker 之前，先要求系統管理員解決這些原則衝突。 |
BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on operating system drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker. |
| 0x80310091 | BitLocker 磁碟機加密無法套用至此磁碟機，因為固定資料磁碟機上修復選項的群組原則設定發生衝突。不允許產生修復密碼時，就不能要求將修復資訊儲存至 Active Directory 網域服務。請在嘗試啟用 BitLocker 之前，先要求系統管理員解決這些原則衝突。 |
BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on fixed data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker. |
| 0x80310092 | BitLocker 磁碟機加密無法套用至此磁碟機，因為抽取式資料磁碟機上修復選項的群組原則設定發生衝突。不允許產生修復密碼時，就不能要求將修復資訊儲存至 Active Directory 網域服務。請在嘗試啟用 BitLocker 之前，先要求系統管理員解決這些原則衝突。 |
BitLocker Drive Encryption cannot be applied to this drive because there are conflicting Group Policy settings for recovery options on removable data drives. Storing recovery information to Active Directory Domain Services cannot be required when the generation of recovery passwords is not permitted. Please have your system administrator resolve these policy conflicts before attempting to enable BitLocker. |
| 0x80310093 | 指定憑證的金鑰使用方法 (KU) 屬性不允許該憑證用於 BitLocker 磁碟機加密。BitLocker 不要求憑證必須具有 KU 屬性，但若已設定該屬性，則必須設定為金鑰編密或金鑰合約。 |
The Key Usage (KU) attribute of the specified certificate does not permit it to be used for BitLocker Drive Encryption. BitLocker does not require that a certificate have a KU attribute, but if one is configured it must be set to either Key Encipherment or Key Agreement. |
| 0x80310094 | 無法授權與指定憑證關聯的私密金鑰。可能未提供私密金鑰授權，或提供的授權不正確。 |
The private key associated with the specified certificate cannot be authorized. The private key authorization was either not provided or the provided authorization was invalid. |
| 0x80310095 | 必須使用憑證嵌入式管理單元移除資料修復代理憑證。 |
Removal of the data recovery agent certificate must be done using the Certificates snap-in. |
| 0x80310096 | 此磁碟機已使用 Windows Vista 和 Windows Server 2008 隨附的 BitLocker 磁碟機加密版本加密，該版本不支援組織識別元。若要為此磁碟機指定組織識別元，請使用 \"manage-bde -upgrade\" 命令將磁碟機加密升級到最新的版本。 |
This drive was encrypted using the version of BitLocker Drive Encryption included with Windows Vista and Windows Server 2008 which does not support organizational identifiers. To specify organizational identifiers for this drive upgrade the drive encryption to the latest version using the \"manage-bde -upgrade\" command. |
| 0x80310097 | 已在這部電腦上自動解除鎖定磁碟機，因此無法鎖定該磁碟機。請移除自動解除鎖定保護裝置以鎖定這個磁碟機。 |
The drive cannot be locked because it is automatically unlocked on this computer. Remove the automatic unlock protector to lock this drive. |
| 0x80310098 | 您的智慧卡不支援 ECC 智慧卡的預設 BitLocker 金鑰衍生函數 SP800-56A。需要 FIPS 相容的群組原則設定禁止 BitLocker 使用任何其他金鑰衍生函數進行加密。在 FIPS 限制的環境中，您必須使用 FIPS 相容的智慧卡。 |
The default BitLocker Key Derivation Function SP800-56A for ECC smart cards is not supported by your smart card. The Group Policy setting requiring FIPS-compliance prevents BitLocker from using any other key derivation function for encryption. You have to use a FIPS compliant smart card in FIPS restricted environments. |
| 0x80310099 | 無法從信賴平台模組 (TPM) 和增強 PIN 取得 BitLocker 加密金鑰。請嘗試使用僅包含數字的 PIN。 |
The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and enhanced PIN. Try using a PIN containing only numerals. |
| 0x8031009A | 要求的 TPM PIN 包含無效的字元。 |
The requested TPM PIN contains invalid characters. |
| 0x8031009B | 儲存在磁碟機上的管理資訊包含不明類型。如果您使用的是舊版的 Windows，請嘗試從最新的版本存取磁碟機。 |
The management information stored on the drive contained an unknown type. If you are using an old version of Windows, try accessing the drive from the latest version. |
| 0x8031009C | 僅 EFI 系統支援此功能。 |
The feature is only supported on EFI systems. |
| 0x8031009D | 在系統上找到一個以上的「網路金鑰保護裝置」憑證。 |
More than one Network Key Protector certificate has been found on the system. |
| 0x8031009E | 必須使用「憑證」嵌入式管理單元來移除「網路金鑰保護裝置」憑證。 |
Removal of the Network Key Protector certificate must be done using the Certificates snap-in. |
| 0x8031009F | 在「網路金鑰保護裝置」憑證存放區中找到無效的憑證。 |
An invalid certificate has been found in the Network Key Protector certificate store. |
| 0x803100A0 | 此磁碟機未使用 PIN 保護。 |
This drive isn't protected with a PIN. |
| 0x803100A1 | 請輸入目前使用的正確 PIN。 |
Please enter the correct current PIN. |
| 0x803100A2 | 您必須使用系統管理員帳戶登入，才能變更 PIN。請按一下連結，以系統管理員的身分重設 PIN。 |
You must be logged on with an administrator account to change the PIN. Click the link to reset the PIN as an administrator. |
| 0x803100A3 | BitLocker 在太多次失敗的要求之後已停用 PIN 變更。請按一下連結，以系統管理員的身分重設 PIN。 |
BitLocker has disabled PIN changes after too many failed requests. Click the link to reset the PIN as an administrator. |
| 0x803100A4 | 您的系統管理員要求密碼只能包含可列印的 ASCII 字元，包括無重音字母 (A-Z、a-z)、數字 (0-9)、空格、算術符號、常見標點符號、分隔符號以及下列符號: # $ & @ ^ _ ~。 |
Your system administrator requires that passwords contain only printable ASCII characters. This includes unaccented letters (A-Z, a-z), numbers (0-9), space, arithmetic signs, common punctuation, separators, and the following symbols: # $ & @ ^ _ ~ . |
| 0x803100A5 | 「BitLocker 磁碟機加密」只支援在精簡佈建的存放裝置上執行「僅已使用空間」加密。 |
BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage. |
| 0x803100A6 | BitLocker 磁碟機加密不支援抹除精簡佈建的存放裝置上的可用空間。 |
BitLocker Drive Encryption does not support wiping free space on thin provisioned storage. |
| 0x803100A7 | 磁碟機不支援必要的驗證金鑰長度。 |
The required authentication key length is not supported by the drive. |
| 0x803100A8 | 此磁碟機未使用密碼保護。 |
This drive isn't protected with a password. |
| 0x803100A9 | 請輸入目前使用的正確密碼。 |
Please enter the correct current password. |
| 0x803100AA | 密碼不能超過 256 個字元。 |
The password cannot exceed 256 characters. |
| 0x803100AB | 無法新增密碼金鑰保護裝置，因為磁碟機上有 TPM 保護裝置存在。 |
A password key protector cannot be added because a TPM protector exists on the drive. |
| 0x803100AC | 無法新增 TPM 金鑰保護裝置，因為磁碟機上有密碼保護裝置存在。 |
A TPM key protector cannot be added because a password protector exists on the drive. |
| 0x803100AD | 只能從所指定 CSV 磁碟區的協調器節點執行此命令。 |
This command can only be performed from the coordinator node for the specified CSV volume. |
| 0x803100AE | 無法在屬於叢集的磁碟區上執行此命令。 |
This command cannot be performed on a volume when it is part of a cluster. |
| 0x803100AF | 由於群組原則設定，BitLocker 未回復為使用 BitLocker 軟體加密。 |
BitLocker did not revert to using BitLocker software encryption due to group policy configuration. |
| 0x803100B0 | BitLocker 無法管理磁碟機，因為磁碟機的硬體加密功能已在使用中。 |
The drive cannot be managed by BitLocker because the drive's hardware encryption feature is already in use. |
| 0x803100B1 | 群組原則設定不允許使用硬體式加密。 |
Group Policy settings do not allow the use of hardware-based encryption. |
| 0x803100B2 | 指定的磁碟機不支援硬體式加密。 |
The drive specified does not support hardware-based encryption. |
| 0x803100B3 | 無法在磁碟加密或解密期間升級 BitLocker。 |
BitLocker cannot be upgraded during disk encryption or decryption. |
| 0x803100B4 | 使用硬體加密的磁碟區不支援探索磁碟區。 |
Discovery Volumes are not supported for volumes using hardware encryption. |
| 0x803100B5 | 未偵測到開機前鍵盤。使用者可能無法提供必要的輸入以解除鎖定磁碟區。 |
No pre-boot keyboard detected. The user may not be able to provide required input to unlock the volume. |
| 0x803100B6 | 未偵測到開機前鍵盤或 Windows 修復環境。使用者可能無法提供必要的輸入以解除鎖定磁碟區。 |
No pre-boot keyboard or Windows Recovery Environment detected. The user may not be able to provide required input to unlock the volume. |
| 0x803100B7 | 群組原則設定需要建立啟動 PIN，但此裝置上沒有開機前鍵盤。使用者可能無法提供必要的輸入以解除鎖定磁碟區。 |
Group Policy settings require the creation of a startup PIN, but a pre-boot keyboard is not available on this device. The user may not be able to provide required input to unlock the volume. |
| 0x803100B8 | 群組原則設定需要建立修復密碼，但此裝置上沒有開機前鍵盤或 Windows 修復環境。使用者可能無法提供必要的輸入以解除鎖定磁碟區。 |
Group Policy settings require the creation of a recovery password, but neither a pre-boot keyboard nor Windows Recovery Environment is available on this device. The user may not be able to provide required input to unlock the volume. |
| 0x803100B9 | 目前未進行可用空間的抹除作業。 |
Wipe of free space is not currently taking place. |
| 0x803100BA | BitLocker 無法針對平台完整性使用「安全開機」，因為「安全開機」已停用。 |
BitLocker cannot use Secure Boot for platform integrity because Secure Boot has been disabled. |
| 0x803100BB | BitLocker 無法針對平台完整性使用「安全開機」，因為「安全開機」設定不符合 BitLocker 的需求。 |
BitLocker cannot use Secure Boot for platform integrity because the Secure Boot configuration does not meet the requirements for BitLocker. |
| 0x803100BC | 您的電腦不支援 BitLocker 硬體加密。請洽詢您的電腦製造商，以取得韌體更新。 |
Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates. |
| 0x803100BD | 無法在該磁碟區上啟用 BitLocker，因為該磁碟區包含磁碟區陰影複製。在加密該磁碟區之前，請先移除所有磁碟區陰影複製。 |
BitLocker cannot be enabled on the volume because it contains a Volume Shadow Copy. Remove all Volume Shadow Copies before encrypting the volume. |
| 0x803100BE | BitLocker 磁碟機加密無法套用至此磁碟區，因為「增強型開機設定資料」的群組原則設定包含無效的資料。請洽詢您的系統管理員解決這個無效的設定，然後再嘗試啟用 BitLocker。 |
BitLocker Drive Encryption cannot be applied to this drive because the Group Policy setting for Enhanced Boot Configuration Data contains invalid data. Please have your system administrator resolve this invalid configuration before attempting to enable BitLocker. |
| 0x803100BF | 此電腦的韌體不支援硬體加密。 |
This PC's firmware is not capable of supporting hardware encryption. |
| 0x803100C0 | 在多次失敗的要求之後，BitLocker 已停用密碼變更。請按一下連結，以系統管理員的身分重設密碼。 |
BitLocker has disabled password changes after too many failed requests. Click the link to reset the password as an administrator. |
| 0x803100C1 | 您必須以系統管理員帳戶登入，才能變更密碼。請按一下連結，以系統管理員的身分重設密碼。 |
You must be logged on with an administrator account to change the password. Click the link to reset the password as an administrator. |
| 0x803100C2 | BitLocker 無法儲存修復密碼，因為指定的 Microsoft 帳戶已被暫停使用。 |
BitLocker cannot save the recovery password because the specified Microsoft account is Suspended. |
| 0x803100C3 | BitLocker 無法儲存修復密碼，因為指定的 Microsoft 帳戶已被封鎖。 |
BitLocker cannot save the recovery password because the specified Microsoft account is Blocked. |
| 0x803100C4 | 此電腦未佈建為支援裝置加密。為符合裝置加密原則，請在所有磁碟區上啟用 BitLocker。 |
This PC is not provisioned to support device encryption. Please enable BitLocker on all volumes to comply with device encryption policy. |
| 0x803100C5 | 此電腦無法支援裝置加密，因為有未加密的固定式資料磁碟區存在。 |
This PC cannot support device encryption because unencrypted fixed data volumes are present. |
| 0x803100C6 | 此電腦不符合使用裝置加密的硬體需求。 |
This PC does not meet the hardware requirements to support device encryption. |
| 0x803100C7 | 此電腦無法支援裝置加密，因為未正確設定 WinRE。 |
This PC cannot support device encryption because WinRE is not properly configured. |
| 0x803100C8 | 已在磁碟區上啟用保護功能，但該功能已暫停。這可能是因為正在您的系統上套用更新。請重新開機，然後再試一次。 |
Protection is enabled on the volume but has been suspended. This is likely to have happened due to an update being applied to your system. Please try again after a reboot. |
| 0x803100C9 | 此電腦未佈建為支援裝置加密。 |
This PC is not provisioned to support device encryption. |
| 0x803100CA | 由於輸入太多次不正確的密碼，已觸發「裝置鎖定」。 |
Device Lock has been triggered due to too many incorrect password attempts. |
| 0x803100CB | 尚未在該磁碟區上啟用保護功能。啟用保護功能需要連結的帳戶。若您已經有連結的帳戶但看到此錯誤，請參閱事件記錄檔以取得詳細資訊。 |
Protection has not been enabled on the volume. Enabling protection requires a connected account. If you already have a connected account and are seeing this error, please refer to the event log for more information. |
| 0x803100CC | PIN 只能包含 0 到 9 的數字。 |
Your PIN can only contain numbers from 0 to 9. |
| 0x803100CD | BitLocker 無法使用硬體重新執行保護，因為您的電腦上沒有可用的計數器。 |
BitLocker cannot use hardware replay protection because no counter is available on your PC. |
| 0x803100CE | 「裝置鎖定」狀態驗證失敗，因為計數器不符。 |
Device Lockout state validation failed due to counter mismatch. |
| 0x803100CF | 輸入緩衝區太大。 |
The input buffer is too large. |
| 0x803100D0 | 引動過程的目標不支援要求的功能。 |
The target of an invocation does not support requested capability. |
| 0x803100D1 | 裝置加密目前已由此電腦的設定封鎖。 |
Device encryption is currently blocked by this PC's configuration. |
| 0x803100D2 | 此磁碟機已從裝置加密剔除。 |
This drive has been opted out of device encryption. |
| 0x803100D3 | 此磁碟機無法使用裝置加密。 |
Device encryption isn't available for this drive. |
| 0x803100D4 | 此版本的 Windows 不支援 BitLocker 的寫入時加密模式。您可以開啟 BitLocker 但不使用寫入時加密模式。 |
The encrypt on write mode for BitLocker is not supported in this version of Windows. You can turn on BitLocker without using the encrypt on write mode. |
| 0x803100D5 | 群組原則禁止您將此磁碟機類型的修復密碼備份到 Active Directory。如需詳細資訊，請連絡您的系統管理員。 |
Group policy prevents you from backing up your recovery password to Active Directory for this drive type. For more info, contact your system administrator. |
| 0x803100D6 | 正在加密此磁碟機，因此無法關閉裝置加密。請稍後再試一次。 |
Device encryption can't be turned off while this drive is being encrypted. Please try again later. |
| 0x803100D7 | 不支援此動作，因為沒有使用裝置加密自動管理此磁碟機。 |
This action isn't supported because this drive isn't automatically managed with device encryption. |
| 0x803100D8 | 無法在此磁碟機暫停 BitLocker，直到下次重新啟動為止。 |
BitLocker can't be suspended on this drive until the next restart. |
| 0x803100D9 | 「BitLocker 磁碟機加密」原則不允許在受保護的 OS 磁碟區上執行 KSR 作業。 |
BitLocker Drive Encryption policy does not allow KSR operation with protected OS volume. |
| 0x80320001 | 圖說文字不存在。 |
The callout does not exist. |
| 0x80320002 | 篩選器條件不存在。 |
The filter condition does not exist. |
| 0x80320003 | 篩選器不存在。 |
The filter does not exist. |
| 0x80320004 | 圖層不存在。 |
The layer does not exist. |
| 0x80320005 | 提供者不存在。 |
The provider does not exist. |
| 0x80320006 | 提供者內容不存在。 |
The provider context does not exist. |
| 0x80320007 | 子圖層不存在。 |
The sublayer does not exist. |
| 0x80320008 | 物件不存在。 |
The object does not exist. |
| 0x80320009 | 具有該 GUID 或 LUID 的物件已經存在。 |
An object with that GUID or LUID already exists. |
| 0x8032000A | 該物件正由其他物件參照，因此無法刪除。 |
The object is referenced by other objects so cannot be deleted. |
| 0x8032000B | 不允許從動態工作階段中發出呼叫。 |
The call is not allowed from within a dynamic session. |
| 0x8032000C | 該呼叫是從錯誤的工作階段中發出，因此無法完成。 |
The call was made from the wrong session so cannot be completed. |
| 0x8032000D | 該呼叫必須從明確交易發出。 |
The call must be made from within an explicit transaction. |
| 0x8032000E | 從明確交易內不允許呼叫。 |
The call is not allowed from within an explicit transaction. |
| 0x8032000F | 明確交易已被強制取消。 |
The explicit transaction has been forcibly cancelled. |
| 0x80320011 | 從唯讀交易內不允許呼叫。 |
The call is not allowed from within a read-only transaction. |
| 0x80320012 | 等候取得交易鎖定時呼叫逾時。 |
The call timed out while waiting to acquire the transaction lock. |
| 0x80320013 | 網路診斷事件的集合已停用。 |
Collection of network diagnostic events is disabled. |
| 0x80320014 | 指定的層不支援該作業。 |
The operation is not supported by the specified layer. |
| 0x80320015 | 只有核心模式呼叫者可進行呼叫。 |
The call is allowed for kernel-mode callers only. |
| 0x80320016 | 呼叫嘗試關聯兩個具有不相容之存留期的物件。 |
The call tried to associate two objects with incompatible lifetimes. |
| 0x80320017 | 物件為內建，無法刪除。 |
The object is built in so cannot be deleted. |
| 0x80320018 | 已達到核心模式驅動程式呼叫的數目上限。 |
The maximum number of callouts has been reached. |
| 0x80320019 | 因為訊息佇列處於最大容量，所以無法傳送通知。 |
A notification could not be delivered because a message queue is at its maximum capacity. |
| 0x8032001A | 流量參數不符合安全性關聯內容的流量參數。 |
The traffic parameters do not match those for the security association context. |
| 0x8032001B | 目前的安全性關聯狀態不允許呼叫。 |
The call is not allowed for the current security association state. |
| 0x8032001C | 需要的指標為空。 |
A required pointer is null. |
| 0x8032001D | 列舉值無效。 |
An enumerator is not valid. |
| 0x8032001E | 旗標欄位包含無效的值。 |
The flags field contains an invalid value. |
| 0x8032001F | 網路遮罩無效。 |
A network mask is not valid. |
| 0x80320020 | FWP_RANGE 無效。 |
An FWP_RANGE is not valid. |
| 0x80320021 | 時間間隔無效。 |
The time interval is not valid. |
| 0x80320022 | 陣列必須至少包含一個長度為零的元素。 |
An array that must contain at least one element is zero length. |
| 0x80320023 | displayData.name 欄位不可為空。 |
The displayData.name field cannot be null. |
| 0x80320024 | 動作類型不是篩選器允許的其中一個動作類型。 |
The action type is not one of the allowed action types for a filter. |
| 0x80320025 | 篩選器加權無效。 |
The filter weight is not valid. |
| 0x80320026 | 篩選器包含的相符類型與運算元不相容。 |
A filter condition contains a match type that is not compatible with the operands. |
| 0x80320027 | FWP_VALUE 或 FWPM_CONDITION_VALUE 的類型錯誤。 |
An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type. |
| 0x80320028 | 整數值超出允許的範圍。 |
An integer value is outside the allowed range. |
| 0x80320029 | 保留的欄位不是零。 |
A reserved field is non-zero. |
| 0x8032002A | 篩選器無法包含在單一欄位上運作的多個條件。 |
A filter cannot contain multiple conditions operating on a single field. |
| 0x8032002B | 原則無法取得相同的金鑰處理模組超過一次。 |
A policy cannot contain the same keying module more than once. |
| 0x8032002C | 動作類型與層不相容。 |
The action type is not compatible with the layer. |
| 0x8032002D | 動作類型與子層不相容。 |
The action type is not compatible with the sublayer. |
| 0x8032002E | 原始內容或提供者內容與層不相容。 |
The raw context or the provider context is not compatible with the layer. |
| 0x8032002F | 原始內容或提供者內容與圖說文字不相容。 |
The raw context or the provider context is not compatible with the callout. |
| 0x80320030 | 驗證方法與原則類型不相容。 |
The authentication method is not compatible with the policy type. |
| 0x80320031 | Diffie-Hellman 群組與原則類型不相容。 |
The Diffie-Hellman group is not compatible with the policy type. |
| 0x80320032 | IKE 原則無法包含延伸模式原則。 |
An IKE policy cannot contain an Extended Mode policy. |
| 0x80320033 | 列舉範本或訂閱將永遠不會符合任何物件。 |
The enumeration template or subscription will never match any objects. |
| 0x80320034 | 提供者內容類型錯誤。 |
The provider context is of the wrong type. |
| 0x80320036 | 已到達子層的數目上限。 |
The maximum number of sublayers has been reached. |
| 0x80320037 | 圖說文字的通知功能已傳回錯誤。 |
The notification function for a callout returned an error. |
| 0x80320038 | IPsec 驗證轉換無效。 |
The IPsec authentication transform is not valid. |
| 0x80320039 | IPsec 密碼轉換無效。 |
The IPsec cipher transform is not valid. |
| 0x8032003A | IPsec 密碼轉換與原則不相容。 |
The IPsec cipher transform is not compatible with the policy. |
| 0x8032003B | IPsec 轉換類型的組合無效。 |
The combination of IPsec transform types is not valid. |
| 0x8032003C | 原則無法包含相同的驗證方法超過一次。 |
A policy cannot contain the same auth method more than once. |
| 0x8032003D | 通道端點設定無效。 |
A tunnel endpoint configuration is invalid. |
| 0x8032003E | WFP MAC 層未就緒。 |
The WFP MAC Layers are not ready. |
| 0x8032003F | 已註冊可進行金鑰聽寫的金鑰管理員 |
A key manager capable of key dictation is already registered |
| 0x80320040 | 金鑰管理員聽寫到無效的金鑰 |
A key manager dictated invalid keys |
| 0x80320041 | 已停用 BFE IPsec 連線追蹤。 |
The BFE IPsec Connection Tracking is disabled. |
| 0x80320042 | DNS 名稱無效。 |
The DNS name is invalid. |
| 0x80320043 | 因為其他組態設定，所以仍然啟用引擎選項。 |
The engine option is still enabled due to other configuration settings. |
| 0x80320044 | IKEEXT 服務未執行。此服務只會在電腦套用 IPsec 原則時才會執行。 |
The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine. |
| 0x80320104 | 應該丟棄封包，不應該傳送 ICMP。 |
The packet should be dropped, no ICMP should be sent. |
| 0x80340002 | 正在關閉網路介面的繫結。 |
The binding to the network interface is being closed. |
| 0x80340004 | 指定的版本無效。 |
An invalid version was specified. |
| 0x80340005 | 使用的特性表無效。 |
An invalid characteristics table was used. |
| 0x80340006 | 找不到網路介面，或網路介面尚未就緒。 |
Failed to find the network interface or network interface is not ready. |
| 0x80340007 | 無法開啟網路介面。 |
Failed to open the network interface. |
| 0x80340008 | 網路介面發生無法復原的內部錯誤。 |
Network interface has encountered an internal unrecoverable failure. |
| 0x80340009 | 網路介面上的多點傳送清單已滿。 |
The multicast list on the network interface is full. |
| 0x8034000A | 嘗試將重複的多點傳送位址加入清單。 |
An attempt was made to add a duplicate multicast address to the list. |
| 0x8034000B | 嘗試移除從未新增的多點傳送位址。 |
At attempt was made to remove a multicast address that was never added. |
| 0x8034000C | 網路介面中止該要求。 |
Netowork interface aborted the request. |
| 0x8034000D | 因為正在重設網路介面，所以無法處理要求。 |
Network interface can not process the request because it is being reset. |
| 0x8034000F | 嘗試在網路介面上傳送無效的封包。 |
An attempt was made to send an invalid packet on a network interface. |
| 0x80340010 | 指定的要求不是目標裝置所要的正確操作。 |
The specified request is not a valid operation for the target device. |
| 0x80340011 | 網路介面尚未就緒，無法完成此操作。 |
Network interface is not ready to complete this operation. |
| 0x80340014 | 提交給此操作的緩衝區長度無效。 |
The length of the buffer submitted for this operation is not valid. |
| 0x80340015 | 此操作使用的資料無效。 |
The data used for this operation is not valid. |
| 0x80340016 | 提交給此操作的緩衝區長度太短。 |
The length of buffer submitted for this operation is too small. |
| 0x80340017 | 網路介面不支援此 OID (物件識別元) |
Network interface does not support this OID (Object Identifier) |
| 0x80340018 | 網路介面已移除。 |
The network interface has been removed. |
| 0x80340019 | 網路介面不支援此媒體類型。 |
Network interface does not support this media type. |
| 0x8034001A | 嘗試移除其他元件正在使用的權杖環群組位址。 |
An attempt was made to remove a token ring group address that is in use by other components. |
| 0x8034001B | 已嘗試對應不存在的檔案。 |
An attempt was made to map a file that can not be found. |
| 0x8034001C | NDIS 嘗試對應檔案時發生錯誤。 |
An error occurred while NDIS tried to map the file. |
| 0x8034001D | 已嘗試對應已經對應的檔案。 |
An attempt was made to map a file that is alreay mapped. |
| 0x8034001E | 因為另一個元件正在使用該硬體資源，所以嘗試配置該資源失敗。 |
An attempt to allocate a hardware resource failed because the resource is used by another component. |
| 0x8034001F | 因為網路媒體已中斷連線或超出無線存取點範圍，所以 I/O 操作失敗。 |
The I/O operation failed because network media is disconnected or wireless access point is out of range. |
| 0x80340022 | 要求中使用的網路位址無效。 |
The network address used in the request is invalid. |
| 0x8034002A | 已暫停網路介面上的卸載操作。 |
The offload operation on the network interface has been paused. |
| 0x8034002B | 找不到網路介面。 |
Network interface was not found. |
| 0x8034002C | 不支援在結構中指定的修訂編號。 |
The revision number specified in the structure is not supported. |
| 0x8034002D | 指定的連接埠不存在於此網路介面上。 |
The specified port does not exist on this network interface. |
| 0x8034002E | 此網路介面上所指定連接埠的目前狀態不支援要求的操作。 |
The current state of the specified port on this network interface does not support the requested operation. |
| 0x8034002F | 迷你連接埠介面卡電源不足。 |
The miniport adapter is in low power state. |
| 0x80340030 | 此作業需要重新初始化 Miniport 介面卡。 |
This operation requires the miniport adapter to be reinitialized. |
| 0x803400BB | 網路介面不支援此要求。 |
Netword interface does not support this request. |
| 0x80342000 | 無線區域網路介面處於自動設定模式，因此不支援要求的參數變更操作。 |
The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation. |
| 0x80342001 | 無線區域網路介面忙碌中，因此無法執行要求的操作。 |
The wireless local area network interface is busy and can not perform the requested operation. |
| 0x80342002 | 無線區域網路介面的電源已關閉，因此不支援要求的操作。 |
The wireless local area network interface is powered down and doesn't support the requested operation. |
| 0x80342003 | 網路喚醒模式清單已滿。 |
The list of wake on LAN patterns is full. |
| 0x80342004 | 低電源通訊協定卸載清單已滿。 |
The list of low power protocol offloads is full. |
| 0x80342005 | 無線區域網路介面目前無法在指定的通道上啟動 AP。 |
The wireless local area network interface cannot start an AP on the specified channel right now. |
| 0x80342006 | 無線區域網路介面目前無法在指定的頻帶上啟動 AP。 |
The wireless local area network interface cannot start an AP on the specified band right now. |
| 0x80342007 | 無線區域網路介面因為法規因素而無法在此通道上啟動 AP。 |
The wireless local area network interface cannot start an AP on this channel due to regulatory reasons. |
| 0x80342008 | 無線區域網路介面因為法規因素而無法在此頻帶上啟動 AP。 |
The wireless local area network interface cannot start an AP on this band due to regulatory reasons. |
| 0x80370001 | 虛擬機器正以其跨多個 NUMA 節點配置的記憶體執行。除非您的虛擬機器異常緩慢，否則這屬於正常狀況。如果您遇到效能問題，可能需要修改 NUMA 設定。 |
A virtual machine is running with its memory allocated across multiple NUMA nodes. This does not indicate a problem unless the performance of your virtual machine is unusually slow. If you are experiencing performance problems, you may need to modify the NUMA configuration. |
| 0x80380001 | 由於有損壞磁區，所以重新產生操作無法從使用中的網狀磁碟區複製所有資料。 |
The regeneration operation was not able to copy all data from the active plexes due to bad sectors. |
| 0x80380002 | 有一或多個磁碟並未完全移轉至目標封裝。在修正硬體問題後，可能需要重新匯入。 |
One or more disks were not fully migrated to the target pack. They may or may not require reimport after fixing the hardware problems. |
| 0x80390001 | 有些 BCD 項目並未從 BCD 存放區正確匯入。 |
Some BCD entries were not imported correctly from the BCD store. |
| 0x80390003 | 某些 BCD 項目並未與韌體正確同步。 |
Some BCD entries were not synchronized correctly with the firmware. |
| 0x803A0001 | 虛擬化儲存子系統已產生錯誤。 |
The virtualization storage subsystem has generated an error. |
| 0x803C0100 | 操作已取消。 |
The operation was cancelled. |
| 0x803C0101 | 執行 PowerShell 指令碼時發生錯誤。 |
An error occurred when running a PowerShell script. |
| 0x803C0102 | 與 PowerShell 執行階段互動時發生錯誤。 |
An error occurred when interacting with PowerShell runtime. |
| 0x803C0103 | 指令碼診斷管理主機中發生錯誤。 |
An error occurred in the Scripted Diagnostic Managed Host. |
| 0x803C0104 | 疑難排解套件不包含完成驗證所需的檢查器。 |
The troubleshooting pack does not contain a required verifier to complete the verification. |
| 0x803C0106 | 群組原則已停用執行指令的診斷。 |
Scripted diagnostics is disabled by group policy. |
| 0x803C0107 | 疑難排解套件的信任驗證失敗。 |
Trust validation of the troubleshooting pack failed. |
| 0x803C0109 | 不支援此版的疑難排解套件。 |
This version of the troubleshooting pack is not supported. |
| 0x803C010A | 無法載入所需的資源。 |
A required resource cannot be loaded. |
| 0x803C010B | 疑難排解套件已報告根本原因的資訊，但未新增該根本原因。 |
The troubleshooting pack reported information for a root cause without adding the root cause. |
| 0x803D0000 | 輸入的資料不是預期的格式，或者不是預期的值。 |
The input data was not in the expected format or did not have the expected value. |
| 0x803D0001 | 因為先前的錯誤使物件處於錯誤狀態，所以無法完成操作。 |
The operation could not be completed because the object is in a faulted state due to a previous error. |
| 0x803D0002 | 因為操作會導致數字溢位，所以無法完成。 |
The operation could not be completed because it would lead to numeric overflow. |
| 0x803D0003 | 因為物件的目前狀態，所以不允許操作。 |
The operation is not allowed due to the current state of the object. |
| 0x803D0004 | 該操作已經中止。 |
The operation was aborted. |
| 0x803D0005 | 遠端端點拒絕存取。 |
Access was denied by the remote endpoint. |
| 0x803D0006 | 未在指定的時間內完成操作。 |
The operation did not complete within the time allotted. |
| 0x803D0007 | 操作已放棄。 |
The operation was abandoned. |
| 0x803D0008 | 超出配額。 |
A quota was exceeded. |
| 0x803D0009 | 不提供指定語言版本的資訊。 |
The information was not available in the specified language. |
| 0x803D000A | 對接收的資料進行安全性驗證失敗。 |
Security verification was not successful for the received data. |
| 0x803D000B | 位址已在使用中。 |
The address is already being used. |
| 0x803D000C | 位址對這種內容而言無效。 |
The address is not valid for this context. |
| 0x803D000D | 遠端端點不存在或找不到。 |
The remote endpoint does not exist or could not be located. |
| 0x803D000E | 這個位置的遠端端點目前不提供服務。 |
The remote endpoint is not currently in service at this location. |
| 0x803D000F | 遠端端點無法處理要求。 |
The remote endpoint could not process the request. |
| 0x803D0010 | 無法連線到遠端端點。 |
The remote endpoint was not reachable. |
| 0x803D0011 | 遠端端點不支援此項操作。 |
The operation was not supported by the remote endpoint. |
| 0x803D0012 | 由於遠端端點超載，無法處理要求。 |
The remote endpoint is unable to process the request due to being overloaded. |
| 0x803D0013 | 從遠端端點收到包含錯誤的訊息。 |
A message containing a fault was received from the remote endpoint. |
| 0x803D0014 | 已經終止與遠端端點的連線。 |
The connection with the remote endpoint was terminated. |
| 0x803D0015 | HTTP Proxy 伺服器無法處理要求。 |
The HTTP proxy server could not process the request. |
| 0x803D0016 | HTTP Proxy 伺服器拒絕存取。 |
Access was denied by the HTTP proxy server. |
| 0x803D0017 | 這個平台不提供要求的功能。 |
The requested feature is not available on this platform. |
| 0x803D0018 | HTTP Proxy 伺服器需要 HTTP 驗證配置 'basic'。 |
The HTTP proxy server requires HTTP authentication scheme 'basic'. |
| 0x803D0019 | HTTP Proxy 伺服器需要 HTTP 驗證配置 'digest'。 |
The HTTP proxy server requires HTTP authentication scheme 'digest'. |
| 0x803D001A | HTTP Proxy 伺服器需要 HTTP 驗證配置 'NTLM'。 |
The HTTP proxy server requires HTTP authentication scheme 'NTLM'. |
| 0x803D001B | HTTP Proxy 伺服器需要 HTTP 驗證配置 'negotiate'。 |
The HTTP proxy server requires HTTP authentication scheme 'negotiate'. |
| 0x803D001C | 遠端端點需要 HTTP 驗證配置 'basic'。 |
The remote endpoint requires HTTP authentication scheme 'basic'. |
| 0x803D001D | 遠端端點需要 HTTP 驗證配置 'digest'。 |
The remote endpoint requires HTTP authentication scheme 'digest'. |
| 0x803D001E | 遠端端點需要 HTTP 驗證配置 'NTLM'。 |
The remote endpoint requires HTTP authentication scheme 'NTLM'. |
| 0x803D001F | 遠端端點需要 HTTP 驗證配置 'negotiate'。 |
The remote endpoint requires HTTP authentication scheme 'negotiate'. |
| 0x803D0020 | 端點位址 URL 無效。 |
The endpoint address URL is invalid. |
| 0x803D0021 | Windows Web 服務架構發生無法辨識的錯誤。 |
Unrecognized error occurred in the Windows Web Services framework. |
| 0x803D0022 | 伺服器已拒絕安全性權杖，因為它已到期。 |
A security token was rejected by the server because it has expired. |
| 0x803D0023 | Windows Web 服務架構發生安全性作業失敗。 |
A security operation failed in the Windows Web Services framework. |
| 0x803E0100 | 通知通道已關閉。 |
The notification channel has already been closed. |
| 0x803E0101 | 通知通道要求未順利完成。 |
The notification channel request did not complete successfully. |
| 0x803E0102 | 提供的應用程式識別碼無效。 |
The application identifier provided is invalid. |
| 0x803E0103 | 提供之應用程式識別碼的通知通道要求正在進行。 |
A notification channel request for the provided application identifier is in progress. |
| 0x803E0104 | 通道識別碼已繫結至另一個應用程式端點。 |
The channel identifier is already tied to another application endpoint. |
| 0x803E0105 | 通知平台無法使用。 |
The notification platform is unavailable. |
| 0x803E0106 | 通知已公佈。 |
The notification has already been posted. |
| 0x803E0107 | 通知已隱藏。 |
The notification has already been hidden. |
| 0x803E0108 | 通知必須先顯示才能隱藏。 |
The notification cannot be hidden until it has been shown. |
| 0x803E0109 | 雲端通知已關閉。 |
Cloud notifications have been turned off. |
| 0x803E0110 | 應用程式沒有雲端通知功能。 |
The application does not have the cloud notification capability. |
| 0x803E0111 | 設定使得通知無法傳遞。 |
Settings prevent the notification from being delivered. |
| 0x803E0112 | 應用程式功能使得通知無法傳遞。 |
Application capabilities prevent the notification from being delivered. |
| 0x803E0113 | 應用程式沒有網際網路存取能力。 |
The application does not have the internet access capability. |
| 0x803E0114 | 設定使得通知類型無法傳遞。 |
Settings prevent the notification type from being delivered. |
| 0x803E0115 | 通知內容的大小太大。 |
The size of the notification content is too large. |
| 0x803E0116 | 通知標籤的大小太大。 |
The size of the notification tag is too large. |
| 0x803E0117 | 通知平台沒有資源的適當權限。 |
The notification platform doesn't have appropriate privilege on resources. |
| 0x803E0118 | 通知平台發現應用程式已註冊。 |
The notification platform found application is already registered. |
| 0x803E0119 | 應用程式背景工作沒有推播通知功能。 |
The application background task does not have the push notification capability. |
| 0x803E011A | 通知平台無法抓取連線到雲端通知服務所需的驗證認證。 |
The notification platform is unable to retrieve the authentication credentials required to connect to the cloud notification service. |
| 0x803E011B | 通知平台無法連線到雲端通知服務。 |
The notification platform is unable to connect to the cloud notification service. |
| 0x803E011C | 通知平台無法初始化鎖定畫面更新的回呼。 |
The notification platform is unable to initialize a callback for lock screen updates. |
| 0x803E0120 | 排程通知的開發人員識別碼大小太大。 |
The size of the developer id for scheduled notification is too large. |
| 0x803E012A | 通知標籤不是英數字元。 |
The notification tag is not alphanumeric. |
| 0x803E012B | 通知平台收到 2xx 以外的無效 HTTP 狀態碼 (對於輪詢)。 |
The notification platform has received invalid HTTP status code other than 2xx for polling. |
| 0x803E0200 | 通知平台已用盡展示層工作階段。 |
The notification platform has run out of presentation layer sessions. |
| 0x803E0201 | 因為系統在省電模式，通知平台拒絕了影像下載要求。 |
The notification platform rejects image download request due to system in power save mode. |
| 0x803E0202 | 通知平台的快取中沒有要求的影像。 |
The notification platform doesn't have the requested image in its cache. |
| 0x803E0203 | 通知平台無法完成所有要求的影像。 |
The notification platform cannot complete all of requested image. |
| 0x803E0204 | 從通知平台下載的雲端影像無效。 |
A cloud image downloaded from the notification platform is invalid. |
| 0x803E0205 | 所提供做為篩選的通知識別碼與通知平台維護的通知識別碼相符。 |
Notification Id provided as filter is matched with what the notification platform maintains. |
| 0x803E0206 | 通知回呼介面已註冊。 |
Notification callback interface is already registered. |
| 0x803E0207 | 已捨棄快顯通知，而未顯示給使用者。 |
Toast Notification was dropped without being displayed to the user. |
| 0x803E0208 | 通知平台沒有適當的權限可完成該要求。 |
The notification platform does not have the proper privileges to complete the request. |
| 0x803E0209 | 通知群組的大小太大。 |
The size of the notification group is too large. |
| 0x803E020A | 通知群組不是英數字元。 |
The notification group is not alphanumeric. |
| 0x803E020B | 應用程式的雲端通知已因原則設定而停用。 |
Cloud notifications have been disabled for the application due to a policy setting. |
| 0x80400000 | 無法依照非時間先後順序的方式處理輸入資料。 |
Input data cannot be processed in the non-chronological order. |
| 0x80400001 | 無法在回呼或事件處理常式內部執行要求的作業。 |
Requested operation cannot be performed inside the callback or event handler. |
| 0x80400002 | 無法處理輸入，因為正在與其他指標類型互動。 |
Input cannot be processed because there is ongoing interaction with another pointer type. |
| 0x80400003 | 輸入封包中的一或多個欄位無效。 |
One or more fields in the input packet are invalid. |
| 0x80400004 | 框架中的封包不一致。可能是指標識別碼不是唯一的，或是時間戳記、框架識別碼、指標類型或來源裝置不一致。 |
Packets in the frame are inconsistent. Either pointer ids are not unique or there is a discrepancy in timestamps, frame ids, pointer types or source devices. |
| 0x80400005 | 框架的歷程記錄不一致。指標識別碼、類型、來源裝置不符，或框架識別碼不是唯一的，或時間戳記有誤。 |
The history of frames is inconsistent. Pointer ids, types, source devices don't match, or frame ids are not unique, or timestamps are out of order. |
| 0x80400006 | 無法抓取關於輸入裝置的資訊。 |
Failed to retrieve information about the input device. |
| 0x80400007 | 座標系統轉換無法轉換資料。 |
Coordinate system transformation failed to transform the data. |
| 0x80400008 | 內容不受支援，或輸入裝置未正確回報內容。 |
The property is not supported or not reported correctly by the input device. |
| 0x80548201 | 內容未啟用。 |
Context is not activated. |
| 0x80548202 | 插入的 SIM 不正確。 |
Bad SIM is inserted. |
| 0x80548203 | 無法使用要求的資料類別。 |
Requested data class is not avaialable. |
| 0x80548204 | 存取點名稱 (APN) 或存取字串不正確。 |
Access point name (APN) or Access string is incorrect. |
| 0x80548205 | 啟用內容已達上限。 |
Max activated contexts have reached. |
| 0x80548206 | 裝置處於封包中斷連結狀態。 |
Device is in packet detach state. |
| 0x80548207 | 看不見提供者。 |
Provider is not visible. |
| 0x80548208 | 無線電波電源已關閉。 |
Radio is powered off. |
| 0x80548209 | MBN 訂閱未啟用。 |
MBN subscription is not activated. |
| 0x8054820A | 未插入 SIM。 |
SIM is not inserted. |
| 0x8054820B | 語音通話進行中。 |
Voice call in progress. |
| 0x8054820C | 可見的提供者快取不正確。 |
Visible provider cache is invalid. |
| 0x8054820D | 裝置未登錄。 |
Device is not registered. |
| 0x8054820E | 找不到提供者。 |
Providers not found. |
| 0x8054820F | 不支援 PIN。 |
Pin is not supported. |
| 0x80548210 | 需要 PIN。 |
Pin is required. |
| 0x80548211 | PIN 已停用。 |
PIN is disabled. |
| 0x80548212 | 一般失敗。 |
Generic Failure. |
| 0x80548218 | 設定檔不正確。 |
Profile is invalid. |
| 0x80548219 | 預設的設定檔已存在。 |
Default profile exist. |
| 0x80548220 | 不支援 SMS 編碼。 |
SMS encoding is not supported. |
| 0x80548221 | 不支援 SMS 篩選器。 |
SMS filter is not supported. |
| 0x80548222 | 使用的 SMS 記憶體索引不正確。 |
Invalid SMS memory index is used. |
| 0x80548223 | 不支援 SMS 語言。 |
SMS language is not supported. |
| 0x80548224 | 發生 SMS 記憶體失敗。 |
SMS memory failure occurred. |
| 0x80548225 | 發生 SMS 網路逾時。 |
SMS network timeout happened. |
| 0x80548226 | 使用不明的 SMSC 位址。 |
Unknown SMSC address is used. |
| 0x80548227 | 不支援 SMS 格式。 |
SMS format is not supported. |
| 0x80548228 | 不允許 SMS 操作。 |
SMS operation is not allowed. |
| 0x80548229 | 裝置 SMS 記憶體已滿。 |
Device SMS memory is full. |
| 0x80550001 | Windows 無法評估此 EAS 原則，因為這不是由作業系統所管理。 |
Windows cannot evaluate this EAS policy since this is not managed by the operating system. |
| 0x80550002 | 若使用者執行特定動作，則可以讓系統符合此 EAS 原則。 |
The system can be made compliant to this EAS policy if certain actions are performed by the user. |
| 0x80550003 | 系統無法強制執行正在評估的 EAS 原則。 |
The EAS policy being evaluated cannot be enforced by the system. |
| 0x80550004 | 無法評估該使用者的 EAS 密碼原則，因為該使用者使用空白密碼。 |
EAS password policies for the user cannot be evaluated as the user has a blank password. |
| 0x80550005 | 不符合 EAS 密碼到期原則，因為密碼到期間隔小於系統的最小密碼間隔。 |
EAS password expiration policy cannot be satisfied as the password expiration interval is less than the minimum password interval of the system. |
| 0x80550006 | 不允許該使用者變更其密碼。 |
The user is not allowed to change her password. |
| 0x80550007 | 無法評估 EAS 密碼原則，因為一或多個系統管理員帳戶使用空白密碼。 |
EAS password policies cannot be evaluated as one or more admins have blank passwords. |
| 0x80550008 | 不允許一或多個系統管理員變更其密碼。 |
One or more admins are not allowed to change their password. |
| 0x80550009 | 有其他不被允許變更其密碼的標準使用者存在。 |
There are other standard users present who are not allowed to change their password. |
| 0x8055000A | EAS 密碼原則無法由至少一個系統管理員的連結帳戶提供者強制執行。 |
The EAS password policy cannot be enforced by the connected account provider of at least one administrator. |
| 0x8055000B | 至少有一個系統管理員的連結帳戶密碼需要變更，才能符合 EAS 密碼原則的要求。 |
There is at least one administrator whose connected account password needs to be changed for EAS password policy compliance. |
| 0x8055000C | EAS 密碼原則無法由目前使用者的連結帳戶提供者強制執行。 |
The EAS password policy cannot be enforced by the connected account provider of the current user. |
| 0x8055000D | 目前使用者的連結帳戶密碼需要變更，才能符合 EAS 密碼原則的要求。 |
The connected account password of the current user needs to be changed for EAS password policy compliance. |
| 0x80630001 | IPv6 通訊協定尚未安裝。 |
The IPv6 protocol is not installed. |
| 0x80630002 | 元件尚未初始化。 |
The compoment has not been initialized. |
| 0x80630003 | 必要的服務無法啟動。 |
The required service canot be started. |
| 0x80630004 | 未授權 P2P 通訊協定在此 OS 上執行。 |
The P2P protocol is not licensed to run on this OS. |
| 0x80630010 | 圖表控制代碼無效。 |
The graph handle is invalid. |
| 0x80630011 | 圖表資料庫名稱已變更。 |
The graph database name has changed. |
| 0x80630012 | 識別碼相同的圖表已存在。 |
A graph with the same ID already exists. |
| 0x80630013 | 圖表尚未就緒。 |
The graph is not ready. |
| 0x80630014 | 圖表正在關閉。 |
The graph is shutting down. |
| 0x80630015 | 圖表仍在使用中。 |
The graph is still in use. |
| 0x80630016 | 圖表資料庫已損毀。 |
The graph database is corrupt. |
| 0x80630017 | 使用了太多屬性。 |
Too many attributes have been used. |
| 0x80630103 | 找不到連線。 |
The connection can not be found. |
| 0x80630106 | 對等嘗試與自己連線。 |
The peer attempted to connect to itself. |
| 0x80630107 | 對等已在接聽連線。 |
The peer is already listening for connections. |
| 0x80630108 | 找不到節點。 |
The node was not found. |
| 0x80630109 | 連線嘗試失敗。 |
The Connection attempt failed. |
| 0x8063010A | 無法驗證對等連線。 |
The peer connection could not be authenticated. |
| 0x8063010B | 已拒絕連線。 |
The connection was refused. |
| 0x80630201 | 對等名稱分類器太長。 |
The peer name classifier is too long. |
| 0x80630202 | 已建立身分識別數目上限。 |
The maximum number of identities have been created. |
| 0x80630203 | 無法存取金鑰。 |
Unable to access a key. |
| 0x80630204 | 群組已經存在。 |
The group already exists. |
| 0x80630301 | 找不到要求的記錄。 |
The requested record could not be found. |
| 0x80630302 | 存取資料庫被拒。 |
Access to the database was denied. |
| 0x80630303 | 無法初始化資料庫。 |
The Database could not be initialized. |
| 0x80630304 | 記錄太大。 |
The record is too big. |
| 0x80630305 | 資料庫已經存在。 |
The database already exists. |
| 0x80630306 | 找不到資料庫。 |
The database could not be found. |
| 0x80630401 | 找不到身分識別。 |
The identity could not be found. |
| 0x80630501 | 找不到事件控制代碼。 |
The event handle could not be found. |
| 0x80630601 | 無效的搜尋。 |
Invalid search. |
| 0x80630602 | 搜尋屬性無效。 |
The search atributes are invalid. |
| 0x80630701 | 邀請未受信任。 |
The invitiation is not trusted. |
| 0x80630703 | certchain 太長。 |
The certchain is too long. |
| 0x80630706 | 偵測到循環憑證鏈結。 |
A circular cert chain was detected. |
| 0x80630801 | certstore 已損毀。 |
The certstore is corrupted. |
| 0x80631001 | 指定的 PNRP 雲端不存在。 |
The specified PNRP cloud deos not exist. |
| 0x80631005 | 雲端名稱不明確。 |
The cloud name is ambiguous. |
| 0x80632010 | 記錄無效。 |
The record is invlaid. |
| 0x80632020 | 尚未授權。 |
Not authorized. |
| 0x80632021 | 密碼不符合原則需求。 |
The password does not meet policy requirements. |
| 0x80632030 | 記錄驗證已延遲。 |
The record validation has been defered. |
| 0x80632040 | 群組屬性無效。 |
The group properies are invalid. |
| 0x80632050 | 對等名稱無效。 |
The peername is invalid. |
| 0x80632060 | 分類器無效。 |
The classifier is invalid. |
| 0x80632070 | 易記名稱無效。 |
The friendly name is invalid. |
| 0x80632071 | 無效的角色屬性。 |
Invalid role property. |
| 0x80632072 | 無效的分類器屬性。 |
Invalid classifer property. |
| 0x80632080 | 無效的記錄到期日。 |
Invlaid record expiration. |
| 0x80632081 | 無效的認證資訊。 |
Invlaid credential info. |
| 0x80632082 | 無效的認證。 |
Invalid credential. |
| 0x80632083 | 無效的記錄大小。 |
Invalid record size. |
| 0x80632090 | 不支援的版本。 |
Unsupported version. |
| 0x80632091 | 群組尚未就緒。 |
The group is not ready. |
| 0x80632092 | 群組仍在使用中。 |
The group is still in use. |
| 0x80632093 | 群組無效。 |
The group is invalid. |
| 0x80632095 | 沒有成員連線。 |
There are no member connections. |
| 0x80632096 | 無法接聽。 |
Unable to listen. |
| 0x806320A0 | 身分識別不存在。 |
The identity does not exist. |
| 0x806320A1 | 服務無法使用。 |
The service is not availible. |
| 0x80634001 | 對等名稱無法轉換為 DNS pnrp 名稱。 |
The peername could not be converted to a DNS pnrp name. |
| 0x80634002 | 無效的對等主機名稱。 |
Invalid peer host name. |
| 0x80634003 | 找不到更多資料。 |
No more data could be found. |
| 0x80634005 | 現有的對等名稱已登錄。 |
The existing peer name is already registered. |
| 0x80636001 | 找不到連絡人。 |
THe contact could not be found. |
| 0x80637000 | 使用者已取消應用程式邀請要求。 |
The app invite request was cancelled by the user. |
| 0x80637001 | 未收到邀請的回應。 |
No response of the invite was received. |
| 0x80637003 | 使用者尚未登入無伺服器狀態。 |
User is not signed into serverless presence. |
| 0x80637004 | 使用者已拒絕隱私權原則提示。 |
The user declined the privacy policy prompt. |
| 0x80637005 | 發生逾時。 |
A timeout occurred. |
| 0x80637007 | 位址無效。 |
The address is invalid. |
| 0x80637008 | 已停用必要的防火牆例外。 |
A required firewall exception is disabled. |
| 0x80637009 | 防火牆原則已封鎖服務。 |
The service is blocked by a firewall policy. |
| 0x8063700A | 已停用防火牆例外。 |
Firewall exceptions are disabled. |
| 0x8063700B | 使用者已拒絕啟用防火牆例外。 |
The user declined to enable the firewall exceptions. |
| 0x80650001 | 在此伺服器上，指定的屬性控制代碼無效。 |
The attribute handle given was not valid on this server. |
| 0x80650002 | 無法讀取屬性。 |
The attribute cannot be read. |
| 0x80650003 | 無法寫入屬性。 |
The attribute cannot be written. |
| 0x80650004 | 屬性 PDU 無效。 |
The attribute PDU was invalid. |
| 0x80650005 | 需要先驗證屬性，才能讀取或寫入屬性。 |
The attribute requires authentication before it can be read or written. |
| 0x80650006 | 屬性伺服器不支援從用戶端接收的要求。 |
Attribute server does not support the request received from the client. |
| 0x80650007 | 指定的位移超過屬性的結尾。 |
Offset specified was past the end of the attribute. |
| 0x80650008 | 屬性必須先取得授權，才能讀取或寫入屬性。 |
The attribute requires authorization before it can be read or written. |
| 0x80650009 | 排入佇列的準備寫入作業太多。 |
Too many prepare writes have been queued. |
| 0x8065000A | 在指定的屬性控制代碼範圍內找不到屬性。 |
No attribute found within the given attribute handle range. |
| 0x8065000B | 無法使用「讀取 Blob 要求」來讀取或寫入屬性。 |
The attribute cannot be read or written using the Read Blob Request. |
| 0x8065000C | 用於加密此連結的「加密金鑰大小」不足。 |
The Encryption Key Size used for encrypting this link is insufficient. |
| 0x8065000D | 屬性值長度對於該作業而言無效。 |
The attribute value length is invalid for the operation. |
| 0x8065000E | 要求的屬性要求發生不大可能發生的錯誤，因此無法依要求完成。 |
The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested. |
| 0x8065000F | 屬性需要先進行加密，才能讀取或寫入屬性。 |
The attribute requires encryption before it can be read or written. |
| 0x80650010 | 屬性類型不是較高層級指定項所定義的受支援群組屬性。 |
The attribute type is not a supported grouping attribute as defined by a higher layer specification. |
| 0x80650011 | 資源不足，無法完成要求。 |
Insufficient Resources to complete the request. |
| 0x80651000 | 接收到保留範圍內的錯誤。 |
An error that lies in the reserved range has been received. |
| 0x80660001 | PortCl 找不到宣告支援 IMiniportAudioEngineNode 之 Miniport 驅動程式所公開的音訊引擎節點。 |
PortCls could not find an audio engine node exposed by a miniport driver claiming support for IMiniportAudioEngineNode. |
| 0x80660002 | HD Audio Widget 發現未預期的空白連線清單。 |
HD Audio widget encountered an unexpected empty connection list. |
| 0x80660003 | HD Audio Widget 不支援連線清單參數。 |
HD Audio widget does not support the connection list parameter. |
| 0x80660004 | 未順利建立任何 HD Audio 子裝置。 |
No HD Audio subdevices were successfully created. |
| 0x80660005 | 在連結的清單中發現未預期的 NULL 指標。 |
An unexpected NULL pointer was encountered in a linked list. |
| 0x80670001 | 樂觀鎖定失敗。若讀取之後發生變更，將無法更新資料。 |
Optimistic locking failure. Data cannot be updated if it has changed since it was read. |
| 0x80670002 | 至少已進入一次準備的陳述式，但並未執行到完成或已重設。這可能導致忙碌的等候。 |
A prepared statement has been stepped at least once but not run to completion or reset. This may result in busy waits. |
| 0x80670003 | StateRepository 設定無效。 |
The StateRepository configuration is not valid. |
| 0x80670004 | StateRepository 結構描述版本未知。 |
The StateRepository schema version is not known. |
| 0x80670005 | StateRepository 字典無效。 |
A StateRepository dictionary is not valid. |
| 0x80670006 | 要求失敗，因為 StateRepository 正主動地封鎖要求。 |
The request failed because the StateRepository is actively blocking requests. |
| 0x80670007 | 資料庫檔案已被鎖定。將會重試該要求。 |
The database file is locked. The request will be retried. |
| 0x80670008 | 資料庫檔案已被鎖定，因為另一個處理程序正在復原該資料庫。將會重試該要求。 |
The database file is locked because another process is busy recovering the database. The request will be retried. |
| 0x80670009 | 資料庫中的資料表已被鎖定。將會重試該要求。 |
A table in the database is locked. The request will be retried. |
| 0x8067000A | 資料庫的共用快取已由另一個連線鎖定。將會重試該要求。 |
The shared cache for the database is locked by another connection. The request will be retried. |
| 0x8067000B | 需要交易才能執行要求的作業。 |
A transaction is required to perform the request operation. |
| 0x8067000C | 資料庫檔案已被鎖定。要求超過允許的閾值。 |
The database file is locked. The request has exceeded the allowed threshold. |
| 0x8067000D | 資料庫檔案已被鎖定，因為另一個處理程序正忙於還原資料庫。要求超過允許的閾值。 |
The database file is locked because another process is busy recovering the database. The request has exceeded the allowed threshold. |
| 0x8067000E | 資料庫中的資料表已被鎖定。要求超過允許的閾值。 |
A table in the database is locked. The request has exceeded the allowed threshold. |
| 0x8067000F | 資料庫的共用快取已由另一個連線鎖定。要求超過允許的閾值。 |
The shared cache for the database is locked by another connection. The request has exceeded the allowed threshold. |
| 0x80670010 | 正在執行 StateRepository 服務停止事件。 |
The StateRepository service Stop event is in progress. |
| 0x80820001 | 開機檔案太小，無法支援持續快照。 |
The bootfile is too small to support persistent snapshots. |
| 0x80820002 | 此磁碟區上永續性快照的啟動時間超過允許的時間長度。 |
Activation of persistent snapshots on this volume took longer than was allowed. |
| 0x80830001 | 指定的磁碟區不支援儲存層。 |
The specified volume does not support storage tiers. |
| 0x80830002 | 儲存層管理服務偵測到系統正在卸載指定的磁碟區。 |
The Storage Tiers Management service detected that the specified volume is in the process of being dismounted. |
| 0x80830003 | 在磁碟區上找不到指定的儲存層。請確定儲存層名稱是有效的。 |
The specified storage tier could not be found on the volume. Confirm that the storage tier name is valid. |
| 0x80830004 | 指定的檔案識別碼在該磁碟區上無效。 |
The file identifier specified is not valid on the volume. |
| 0x80830005 | 必須在擁有中繼資料磁碟區的叢集節點上呼叫儲存層操作。 |
Storage tier operations must be called on the clustering node that owns the metadata volume. |
| 0x80830006 | 儲存層管理服務已準備好要最佳化所指定磁碟區上的儲存層。 |
The Storage Tiers Management service is already optimizing the storage tiers on the specified volume. |
| 0x80830007 | 要求的物件類型無法指派至儲存層。 |
The requested object type cannot be assigned to a storage tier. |
| 0x80830008 | 要求的檔案未釘選到某一層。 |
The requested file is not pinned to a tier. |
| 0x80830009 | 磁碟區不是分層磁碟區。 |
The volume is not a tiered volume. |
| 0x8083000A | 要求的屬性不存在於指定的檔案或目錄中。 |
The requested attribute is not present on the specified file or directory. |
| 0x80860001 | 驗證目標無效，或未正確設定。 |
Authentication target is invalid or not configured correctly. |
| 0x80860002 | 由於使用者所接受的「使用規定」，您的應用程式無法取得線上識別碼屬性。 |
Your application cannot get the Online Id properties due to the Terms of Use accepted by the user. |
| 0x80860003 | 要求驗證權杖的應用程式已停用或未正確設定。 |
The application requesting authentication tokens is either disabled or incorrectly configured. |
| 0x80860004 | 必須先更新線上識別碼密碼才能登入。 |
Online Id password must be updated before signin. |
| 0x80860005 | 必須先更新線上識別碼帳戶內容才能登入。 |
Online Id account properties must be updated before signin. |
| 0x80860006 | 為協助您保護您的線上識別碼帳戶，您必須重新登入。 |
To help protect your Online Id account you must signin again. |
| 0x80860007 | 已鎖定線上識別碼帳戶，因為嘗試登入次數太多。 |
Online Id account was locked because there have been too many attempts to sign in. |
| 0x80860008 | 線上識別碼帳戶需要家長同意才能繼續。 |
Online Id account requires parental consent before proceeding. |
| 0x80860009 | 尚未驗證線上識別碼登入名稱。必須先完成電子郵件驗證才能登入。 |
Online Id signin name is not yet verified. Email verification is required before signin. |
| 0x8086000A | 我們注意到您的線上識別碼帳戶有不尋常的活動。您需要採取行動，確定沒有其他人使用您的帳戶。 |
We have noticed some unusual activity in your Online Id account. Your action is needed to make sure no one else is using your account. |
| 0x8086000B | 偵測到您的線上識別碼帳戶有某些可疑活動。為協助保護您的安全，我們已暫時封鎖您的帳戶。 |
We detected some suspicious activity with your Online Id account. To help protect you, we've temporarily blocked your account. |
| 0x8086000C | 需要使用者互動以進行驗證。 |
User interaction is required for authentication. |
| 0x8086000D | 使用者已達每個使用者的裝置關聯數目上限。 |
User has reached the maximum device associations per user limit. |
| 0x8086000E | 無法從應用程式登出，因為使用者帳戶已連結。 |
Cannot sign out from the application since the user account is connected. |
| 0x8086000F | 需要使用者認證才能執行此操作。 |
User authentication is required for this operation. |
| 0x80860010 | 我們想確認這是您本人。需要使用者互動以進行驗證。 |
We want to make sure this is you. User interaction is required for authentication. |
| 0x80B00001 | 無法從 ARM 架構裝置建立新處理程序。 |
Could not create new process from ARM architecture device. |
| 0x80B00002 | 無法從 ARM 架構裝置連結到應用程式處理程序。 |
Could not attach to the application process from ARM architecture device. |
| 0x80B00003 | 無法從 ARM 架構裝置連線到 dbgsrv 伺服器。 |
Could not connect to dbgsrv server from ARM architecture device. |
| 0x80B00004 | 無法從 ARM 架構裝置啟動 dbgsrv 伺服器。 |
Could not start dbgsrv server from ARM architecture device. |
| 0x80E70001 | 指定的容錯網域類型或最小/最大容錯網域類型的組合無效。 |
The specified fault domain type or combination of minimum / maximum fault domain type is not valid. |
| 0x80E70002 | 發生「儲存空間」內部錯誤。 |
A Storage Spaces internal error occurred. |
| 0x80E70003 | 指定的恢復類型無效。 |
The specified resiliency type is not valid. |
| 0x80E70004 | 儲存集區不支援實體磁碟的磁區大小。 |
The physical disk's sector size is not supported by the storage pool. |
| 0x80E70006 | 要求的冗餘超出支援的值範圍。 |
The requested redundancy is outside of the supported range of values. |
| 0x80E70007 | 要求的資料複本數目超出支援的值範圍。 |
The number of data copies requested is outside of the supported range of values. |
| 0x80E70008 | ParityLayout 的值超出支援的值範圍。 |
The value for ParityLayout is outside of the supported range of values. |
| 0x80E70009 | 間隔長度的值超出支援的值範圍或不是 2 的次方。 |
The value for interleave length is outside of the supported range of values or is not a power of 2. |
| 0x80E7000A | 指定的欄數超出支援的值範圍。 |
The number of columns specified is outside of the supported range of values. |
| 0x80E7000B | 沒有足夠的實體磁碟可以完成要求的作業。 |
There were not enough physical disks to complete the requested operation. |
| 0x80E7000C | 有延伸的錯誤資訊可用。 |
Extended error information is available. |
| 0x80E7000D | 指定的佈建類型無效。 |
The specified provisioning type is not valid. |
| 0x80E7000E | 配置大小超出支援的值範圍。 |
The allocation size is outside of the supported range of values. |
| 0x80E7000F | 機箱感知不支援此虛擬磁碟。 |
Enclosure awareness is not supported for this virtual disk. |
| 0x80E70010 | 寫入快取大小超出支援的值範圍。 |
The write cache size is outside of the supported range of values. |
| 0x80E70011 | 群組數目的值超出支援的值範圍。 |
The value for number of groups is outside of the supported range of values. |
| 0x80E70012 | 實體磁碟的 OperationalState 對此操作而言無效。 |
The OperationalState of the physical disk is invalid for this operation. |
| 0x83750001 | 不支援的格式。 |
Unsupported format. |
| 0x83750002 | 無效的 XML。 |
Invalid XML. |
| 0x83750003 | 缺少必要的項目。 |
Missing required element. |
| 0x83750004 | 缺少必要的屬性。 |
Missing required attribute. |
| 0x83750005 | 未預期的內容。 |
Unexpected content. |
| 0x83750006 | 資源太大。 |
Resource too large. |
| 0x83750007 | 無效的 JSON 字串。 |
Invalid JSON string. |
| 0x83750008 | 無效的 JSON 數字。 |
Invalid JSON number. |
| 0x83750009 | 找不到 JSON 值。 |
JSON value not found. |
| 0x83760001 | 通訊協定執行的作業無效。 |
Invalid operation performed by the protocol. |
| 0x83760002 | 特定通訊協定作業的資料格式無效。 |
Invalid data format for the specific protocol operation. |
| 0x83760003 | 不支援通訊協定延伸。 |
Protocol extensions are not supported. |
| 0x83760004 | 不支援子通訊協定。 |
Subrotocol is not supported. |
| 0x83760005 | 通訊協定版本不正確。 |
Incorrect protocol version. |
| 0x87AF0001 | SQL 錯誤或遺失資料庫 |
SQL error or missing database |
| 0x87AF0002 | SQLite 中有內部邏輯錯誤 |
Internal logic error in SQLite |
| 0x87AF0003 | 存取權限被拒 |
Access permission denied |
| 0x87AF0004 | 回呼常式已要求中止 |
Callback routine requested an abort |
| 0x87AF0005 | 資料庫檔案已鎖定 |
The database file is locked |
| 0x87AF0006 | 資料庫中有已鎖定的表格 |
A table in the database is locked |
| 0x87AF0007 | malloc() 失敗 |
A malloc() failed |
| 0x87AF0008 | 嘗試寫入唯讀資料庫 |
Attempt to write a readonly database |
| 0x87AF0009 | sqlite3_interrupt() 已終止操作 |
Operation terminated by sqlite3_interrupt() |
| 0x87AF000A | 發生某種磁碟 I/O 錯誤 |
Some kind of disk I/O error occurred |
| 0x87AF000B | 資料庫磁碟映像格式錯誤 |
The database disk image is malformed |
| 0x87AF000C | sqlite3_file_control() 中有不明的 opcode |
Unknown opcode in sqlite3_file_control() |
| 0x87AF000D | 插入失敗，因為資料庫已滿 |
Insertion failed because database is full |
| 0x87AF000E | 無法開啟資料庫檔案 |
Unable to open the database file |
| 0x87AF000F | 資料庫鎖定通訊協定錯誤 |
Database lock protocol error |
| 0x87AF0010 | 資料庫是空的 |
Database is empty |
| 0x87AF0011 | 資料庫結構描述已變更 |
The database schema changed |
| 0x87AF0012 | 字串或 BLOB 超出大小限制 |
String or BLOB exceeds size limit |
| 0x87AF0013 | 因違反限制式而中止 |
Abort due to constraint violation |
| 0x87AF0014 | 資料類型不符 |
Data type mismatch |
| 0x87AF0015 | 程式庫使用方式不正確 |
Library used incorrectly |
| 0x87AF0016 | 使用主機上不支援的 OS 功能 |
Uses OS features not supported on host |
| 0x87AF0017 | 授權被拒 |
Authorization denied |
| 0x87AF0018 | 輔助資料庫格式錯誤 |
Auxiliary database format error |
| 0x87AF0019 | sqlite3_bind 的第 2 個參數超出範圍 |
2nd parameter to sqlite3_bind out of range |
| 0x87AF001A | 開啟的檔案不是資料庫檔案 |
File opened that is not a database file |
| 0x87AF001B | 來自 sqlite3_log() 的通知 |
Notifications from sqlite3_log() |
| 0x87AF001C | 來自 sqlite3_log() 的警告 |
Warnings from sqlite3_log() |
| 0x87AF0064 | sqlite3_step() 有另一列已就緒 |
sqlite3_step() has another row ready |
| 0x87AF0065 | sqlite3_step() 已完成執行 |
sqlite3_step() has finished executing |
| 0x87AF0105 | SQLITE_BUSY_RECOVERY |
SQLITE_BUSY_RECOVERY |
| 0x87AF0106 | SQLITE_LOCKED_SHAREDCACHE |
SQLITE_LOCKED_SHAREDCACHE |
| 0x87AF0108 | SQLITE_READONLY_RECOVERY |
SQLITE_READONLY_RECOVERY |
| 0x87AF010A | SQLITE_IOERR_READ |
SQLITE_IOERR_READ |
| 0x87AF010B | SQLITE_CORRUPT_VTAB |
SQLITE_CORRUPT_VTAB |
| 0x87AF010E | SQLITE_CANTOPEN_NOTEMPDIR |
SQLITE_CANTOPEN_NOTEMPDIR |
| 0x87AF0113 | SQLITE_CONSTRAINT_CHECK |
SQLITE_CONSTRAINT_CHECK |
| 0x87AF011B | SQLITE_NOTICE_RECOVER_WAL |
SQLITE_NOTICE_RECOVER_WAL |
| 0x87AF011C | SQLITE_WARNING_AUTOINDEX |
SQLITE_WARNING_AUTOINDEX |
| 0x87AF0204 | SQLITE_ABORT_ROLLBACK |
SQLITE_ABORT_ROLLBACK |
| 0x87AF0205 | SQLITE_BUSY_SNAPSHOT |
SQLITE_BUSY_SNAPSHOT |
| 0x87AF0208 | SQLITE_READONLY_CANTLOCK |
SQLITE_READONLY_CANTLOCK |
| 0x87AF020A | SQLITE_IOERR_SHORT_READ |
SQLITE_IOERR_SHORT_READ |
| 0x87AF020E | SQLITE_CANTOPEN_ISDIR |
SQLITE_CANTOPEN_ISDIR |
| 0x87AF0213 | SQLITE_CONSTRAINT_COMMITHOOK |
SQLITE_CONSTRAINT_COMMITHOOK |
| 0x87AF021B | SQLITE_NOTICE_RECOVER_ROLLBACK |
SQLITE_NOTICE_RECOVER_ROLLBACK |
| 0x87AF0308 | SQLITE_READONLY_ROLLBACK |
SQLITE_READONLY_ROLLBACK |
| 0x87AF030A | SQLITE_IOERR_WRITE |
SQLITE_IOERR_WRITE |
| 0x87AF030E | SQLITE_CANTOPEN_FULLPATH |
SQLITE_CANTOPEN_FULLPATH |
| 0x87AF0313 | SQLITE_CONSTRAINT_FOREIGNKEY |
SQLITE_CONSTRAINT_FOREIGNKEY |
| 0x87AF0408 | SQLITE_READONLY_DBMOVED |
SQLITE_READONLY_DBMOVED |
| 0x87AF040A | SQLITE_IOERR_FSYNC |
SQLITE_IOERR_FSYNC |
| 0x87AF040E | SQLITE_CANTOPEN_CONVPATH |
SQLITE_CANTOPEN_CONVPATH |
| 0x87AF0413 | SQLITE_CONSTRAINT_FUNCTION |
SQLITE_CONSTRAINT_FUNCTION |
| 0x87AF050A | SQLITE_IOERR_DIR_FSYNC |
SQLITE_IOERR_DIR_FSYNC |
| 0x87AF0513 | SQLITE_CONSTRAINT_NOTNULL |
SQLITE_CONSTRAINT_NOTNULL |
| 0x87AF060A | SQLITE_IOERR_TRUNCATE |
SQLITE_IOERR_TRUNCATE |
| 0x87AF0613 | SQLITE_CONSTRAINT_PRIMARYKEY |
SQLITE_CONSTRAINT_PRIMARYKEY |
| 0x87AF070A | SQLITE_IOERR_FSTAT |
SQLITE_IOERR_FSTAT |
| 0x87AF0713 | SQLITE_CONSTRAINT_TRIGGER |
SQLITE_CONSTRAINT_TRIGGER |
| 0x87AF080A | SQLITE_IOERR_UNLOCK |
SQLITE_IOERR_UNLOCK |
| 0x87AF0813 | SQLITE_CONSTRAINT_UNIQUE |
SQLITE_CONSTRAINT_UNIQUE |
| 0x87AF090A | SQLITE_IOERR_RDLOCK |
SQLITE_IOERR_RDLOCK |
| 0x87AF0913 | SQLITE_CONSTRAINT_VTAB |
SQLITE_CONSTRAINT_VTAB |
| 0x87AF0A0A | SQLITE_IOERR_DELETE |
SQLITE_IOERR_DELETE |
| 0x87AF0A13 | SQLITE_CONSTRAINT_ROWID |
SQLITE_CONSTRAINT_ROWID |
| 0x87AF0B0A | SQLITE_IOERR_BLOCKED |
SQLITE_IOERR_BLOCKED |
| 0x87AF0C0A | SQLITE_IOERR_NOMEM |
SQLITE_IOERR_NOMEM |
| 0x87AF0D0A | SQLITE_IOERR_ACCESS |
SQLITE_IOERR_ACCESS |
| 0x87AF0E0A | SQLITE_IOERR_CHECKRESERVEDLOCK |
SQLITE_IOERR_CHECKRESERVEDLOCK |
| 0x87AF0F0A | SQLITE_IOERR_LOCK |
SQLITE_IOERR_LOCK |
| 0x87AF100A | SQLITE_IOERR_CLOSE |
SQLITE_IOERR_CLOSE |
| 0x87AF110A | SQLITE_IOERR_DIR_CLOSE |
SQLITE_IOERR_DIR_CLOSE |
| 0x87AF120A | SQLITE_IOERR_SHMOPEN |
SQLITE_IOERR_SHMOPEN |
| 0x87AF130A | SQLITE_IOERR_SHMSIZE |
SQLITE_IOERR_SHMSIZE |
| 0x87AF140A | SQLITE_IOERR_SHMLOCK |
SQLITE_IOERR_SHMLOCK |
| 0x87AF150A | SQLITE_IOERR_SHMMAP |
SQLITE_IOERR_SHMMAP |
| 0x87AF160A | SQLITE_IOERR_SEEK |
SQLITE_IOERR_SEEK |
| 0x87AF170A | SQLITE_IOERR_DELETE_NOENT |
SQLITE_IOERR_DELETE_NOENT |
| 0x87AF180A | SQLITE_IOERR_MMAP |
SQLITE_IOERR_MMAP |
| 0x87AF190A | SQLITE_IOERR_GETTEMPPATH |
SQLITE_IOERR_GETTEMPPATH |
| 0x87AF1A02 | SQLITE_IOERR_VNODE |
SQLITE_IOERR_VNODE |
| 0x87AF1A03 | SQLITE_IOERR_AUTH |
SQLITE_IOERR_AUTH |
| 0x87AF1A0A | SQLITE_IOERR_CONVPATH |
SQLITE_IOERR_CONVPATH |
| 0x87C51001 | 已啟動切換 (替代) 追蹤 |
Toggle (alternative) trace started |
| 0x87C51002 | 無法先佔執行中的追蹤: 目前的追蹤具有較高的優先順序 |
Cannot pre-empt running trace: The current trace has a higher priority |
| 0x87C51003 | 一律開啟追蹤並未執行 |
The always-on-trace is not running |
| 0x87C51004 | RunScriptAction 包含無效的指令碼類型 |
RunScriptAction contains an invalid script type |
| 0x87C51005 | 找不到要求的案例定義 |
Requested scenario definition cannot be found |
| 0x87C51006 | 找不到要求的追蹤設定檔 |
Requested trace profile cannot be found |
| 0x87C51007 | 已啟用觸發程序轉寄站 |
Trigger forwarder is already enabled |
| 0x87C51008 | 已停用觸發程序轉寄站 |
Trigger forwarder is already disabled |
| 0x87C51009 | 無法剖析 EventLog XML: 項目格式錯誤 |
Cannot parse EventLog XML: The entry is malformed |
| 0x87C5100A | 節點包含與此用戶端不相容的 schemaversion |
node contains a schemaversion which is not compatible with this client |
| 0x87C5100B | RunScriptAction 已被強制終止指令碼 |
RunScriptAction was forced to terminate a script |
| 0x87C5100C | ToggleTraceWithCustomFilterAction 包含無效的自訂篩選 |
ToggleTraceWithCustomFilterAction contains an invalid custom filter |
| 0x87C5100D | 追蹤並未執行 |
The trace is not running |
| 0x87C5100E | 案例無法呈報: 此案例最近也剛呈報過 |
A scenario failed to escalate: This scenario has escalated too recently |
| 0x87C5100F | 案例無法呈報: 此案例已經在執行呈報 |
A scenario failed to escalate: This scenario is already running an escalation |
| 0x87C51010 | 無法開始追蹤: PerfTrack 元件已經在進行追蹤 |
Cannot start tracing: PerfTrack component is already tracing |
| 0x87C51011 | 案例無法呈報: 此案例已經達到此呈報類型的呈報次數上限 |
A scenario failed to escalate: This scenario has reached max escalations for this escalation type |
| 0x87C51012 | 無法更新轉寄站: 傳遞給函式的轉寄站屬於不同類型 |
Cannot update forwarder: The forwarder passed to the function is of a different type |
| 0x87C51013 | RunScriptAction 無法刻意強制此呈報終止 |
RunScriptAction failed intentionally to force this escalation to terminate |
| 0x87C51014 | 無法初始化 SQM 記錄器 |
Failed to initialize SQM logger |
| 0x87C51015 | 無法初始化 WER 記錄器: 此系統不支援適用於 UTC 的 WER |
Failed to initialize WER logger: This system does not support WER for UTC |
| 0x87C51016 | TraceManager 已嘗試在不初始化追蹤器的情況下採取追蹤動作 |
The TraceManager has attempted to take a tracing action without initializing tracers |
| 0x87C51017 | WinRT 初始化失敗 |
WinRT initialization failed |
| 0x87C51019 | 案例包含永遠無法滿足的無效篩選條件 |
Scenario contains an invalid filter that can never be satisfied |
| 0x87C5101A | RunExeWithArgsAction 已接到強制終止執行中可執行檔的要求 |
RunExeWithArgsAction was forced to terminate a running executable |
| 0x87C5101B | 案例升級失敗，因為沒有足夠的權限 |
Escalation for scenario failed due to insufficient permissions |
| 0x87C5101C | 案例安裝失敗，因為沒有足夠的權限 |
Setup for scenario failed due to insufficient permissions |
| 0x87C5101D | UTC 啟動的處理程序因使用非零的結束代碼而失敗。 |
A process launched by UTC failed with a non-zero exit code. |
| 0x87C5101E | RunExeWithArgs 動作包含未經授權的命令列。 |
A RunExeWithArgs action contains an unauthorized command line. |
| 0x87C5101F | UTC 無法載入情節編輯器 XML。使用編輯器將情節檔案轉換為 DiagTrack XML。 |
UTC cannot load Scenario Editor XML. Convert the scenario file to a DiagTrack XML using the editor. |
| 0x87C51020 | 案例呈報已逾時 |
Escalation for scenario has timed out |
| 0x87C51021 | 案例設定已逾時 |
Setup for scenario has timed out |
| 0x87C51022 | 指定的觸發程序與預期的觸發程序類型不符 |
The given trigger does not match the expected trigger type |
| 0x87C51023 | 找不到要求的觸發程序。 |
Requested trigger cannot be found |
| 0x87C51024 | 電腦上不支援 SIF |
SIF is not supported on the machine |
| 0x87C51025 | 延遲動作已終止 |
The delay action was terminated |
| 0x87C51026 | 未取得裝置票證 |
The device ticket was not obtained |
| 0x87C51027 | 追蹤設定檔需要比可用於追蹤之記憶體還多的記憶體 |
The trace profile needs more memory than is available for tracing |
| 0x87C51028 | API 未順利完成，因此沒有可用的結果 |
The API was not completed successfully so the result is unavailable |
| 0x87C51029 | 要求的 API 在 API 管理員中發生逾時 |
The requested API encountered a timeout in the API manager |
| 0x87C5102A | 同步 API 發生等候失敗 |
The synchronous API encountered a wait failure |
| 0x87C5102B | UTC API 正忙於處理另一個要求 |
The UTC API is busy with another request |
| 0x87C5102C | 執行中的追蹤設定檔沒有足夠的執行階段可滿足提升要求 |
The running trace profile does not have a sufficient runtime to fulfill the escalation request |
| 0x87C5102D | 追蹤設定檔無法啟動，因為它需要專屬性，但另一個優先順序較高的追蹤已在執行 |
The trace profile could not be started because it requires exclusivity and another higher priority trace is already running |
| 0x87C5102E | 未核准 GetFile 升級動作的檔案路徑 |
The file path is not approved for the GetFile escalation action |
| 0x87C5102F | 無法建立要求之升級的升級工作目錄，因為它已存在 |
The escalation working directory for the requested escalation could not be created because it already exists |
| 0x87C51030 | 無法在源自 \"_start\" 狀態的轉換上使用時間觸發程序 |
Time triggers cannot be used on a transition originating from the \"_start\" state |
| 0x87C51031 | 時間觸發程序只能附加到單一轉換 |
Time triggers can only be attached to a single transition |
| 0x87C51032 | 時間觸發程序持續期間必須介於 1 秒鐘到 15 分鐘之間 (含) |
Time trigger duration must fall within an inclusive range of one second and 15 minutes |
| 0x87C51033 | 每個狀態只允許一個時間觸發程序 |
Only one Time Trigger is allowed per state |
| 0x87C51034 | RunExeWithArgs 動作包含目標裝置上不存在的二進位檔案。 |
A RunExeWithArgs action contains a binary which is not present on the targeted device. |
| 0x88010001 | 一或多個固定磁碟區未使用協力廠商加密提供者佈建以支援裝置加密。請使用協力廠商提供者啟用加密以符合原則。 |
One or more fixed volumes are not provisioned with the 3rd party encryption providers to support device encryption. Enable encryption with the 3rd party provider to comply with policy. |
| 0x88010002 | 此電腦未完全加密。有一些固定磁碟區不支援加密。 |
This computer is not fully encrypted. There are fixed volumes present which are not supported for encryption. |
| 0x88010003 | 此電腦不符合硬體需求，無法使用安裝的協力廠商提供者支援裝置加密。 |
This computer does not meet the hardware requirements to support device encryption with the installed 3rd party provider. |
| 0x88010004 | 此電腦不支援裝置加密，因為未設定必須使用裝置鎖定功能。 |
This computer cannot support device encryption because the requisites for the device lock feature are not configured. |
| 0x88010005 | 已在此磁碟區上啟用保護功能，但該功能不是處於作用中狀態。 |
Protection is enabled on this volume but is not in the active state. |
| 0x88010006 | 已安裝協力廠商提供者，但無法啟用加密，因為尚未啟用授權。 |
The 3rd party provider has been installed, but cannot activate encryption beacuse a license has not been activated. |
| 0x88010007 | 作業系統磁碟機不受協力廠商磁碟機加密保護。 |
The operating system drive is not protected by 3rd party drive encryption. |
| 0x88010008 | 呼叫協力廠商磁碟機加密外掛程式時發生意外失敗。 |
Unexpected failure was encountered while calling into the 3rd Party drive encryption plugin. |
| 0x88010009 | 協力廠商磁碟機加密所使用之鎖定中繼資料的輸入緩衝區大小太大。 |
The input buffer size for the lockout metadata used by the 3rd party drive encryption is too large. |
| 0x8802B001 | 檔案大小超過同步引擎支援的大小。 |
The file size is larger than supported by the sync engine. |
| 0x8802B002 | 無法上傳該檔案，因為它不適合使用者可用服務所提供的儲存空間。 |
The file cannot be uploaded because it doesn't fit in the user's available service provided storage space. |
| 0x8802B003 | 檔案名稱包含無效的字元。 |
The file name contains invalid characters. |
| 0x8802B004 | 已達到同步引擎中此資料夾的檔案計數上限。 |
The maximum file count has been reached for this folder in the sync engine. |
| 0x8802B005 | 檔案同步處理已被委派給另一個程式，而且發生問題。 |
The file sync has been delegated to another program and has run into an issue. |
| 0x8802B006 | 由於來自服務的節流處理要求，已延遲同步。 |
Sync has been delayed due to a throttling request from the service. |
| 0x8802C002 | 似乎找不到該檔案。請稍後再試一次。 |
We can't seem to find that file. Please try again later. |
| 0x8802C003 | 您用來登入的帳戶沒有開啟此檔案的權限。 |
The account you're signed in with doesn't have permission to open this file. |
| 0x8802C004 | 連線到該服務時發生問題。請稍後再試一次。 |
There was a problem connecting to the service. Please try again later. |
| 0x8802C005 | 抱歉，下載該檔案時發生問題。 |
Sorry, there was a problem downloading the file. |
| 0x8802C006 | 目前無法下載該檔案。請稍後再試一次。 |
We're having trouble downloading the file right now. Please try again later. |
| 0x8802D001 | 同步引擎沒有存取同步根目錄下之本機資料夾的權限。 |
The sync engine does not have permissions to access a local folder under the sync root. |
| 0x8802D002 | 資料夾名稱包含無效的字元。 |
The folder name contains invalid characters. |
| 0x8802D003 | 您目前的市場不允許執行同步引擎。 |
The sync engine is not allowed to run in your current market. |
| 0x8802D004 | 無法上傳所有檔案與資料夾，因為檔案或資料夾的路徑太長。 |
All files and folders can't be uploaded because a path of a file or folder is too long. |
| 0x8802D005 | 無法同步所有檔案與資料夾，因為檔案或資料夾的路徑會超過本機路徑限制。 |
All file and folders cannot be synchronized because a path of a file or folder would exceed the local path limit. |
| 0x8802D006 | 需要更新才能使用同步引擎。 |
Updates are needed in order to use the sync engine. |
| 0x8802D007 | 同步引擎需要向 Proxy 伺服器驗證。 |
The sync engine needs to authenticate with a proxy server. |
| 0x8802D008 | 設定該帳戶的儲存服務時發生問題。 |
There was a problem setting up the storage services for the account. |
| 0x8802D009 | 無法上傳檔案，因為有不支援的重新分析點。 |
Files can't be uploaded because there's an unsupported reparse point. |
| 0x8802D00A | 該服務已封鎖您的帳戶，因此您無法存取儲存服務。 |
The service has blocked your account from accessing the storage service. |
| 0x8802D00B | 目前無法執行該工作，因為系統正在移除此資料夾。請稍後再試一次。 |
The action can't be performed right now because this folder is being moved. Please try again later. |
| 0x88790001 | 應用程式超過每一 Direct3D 裝置的唯一狀態物件數目上限。到 11.1 為止的功能層級的限制為 4096。 |
The application has exceeded the maximum number of unique state objects per Direct3D device.The limit is 4096 for feature levels up to 11.1. |
| 0x88790002 | 找不到指定的檔案。 |
The specified file was not found. |
| 0x887A0001 | 應用程式進行的呼叫無效。呼叫的參數或某些物件的狀態不正確。啟用 D3D 偵錯層以透過偵測訊息查看詳細資訊。 |
The application made a call that is invalid. Either the parameters of the call or the state of some object was incorrect.Enable the D3D debug layer in order to see details via debug messages. |
| 0x887A0002 | 找不到物件。如果呼叫 IDXGIFactory::EnumAdaptes，則沒有具有指定序號的介面。 |
The object was not found. If calling IDXGIFactory::EnumAdaptes, there is no adapter with the specified ordinal. |
| 0x887A0003 | 呼叫者未提供足夠大的緩衝區。 |
The caller did not supply a sufficiently large buffer. |
| 0x887A0004 | 此系統不支援指定的裝置介面或功能層級。 |
The specified device interface or feature level is not supported on this system. |
| 0x887A0005 | 已暫停 GPU 裝置執行個體。請使用 GetDeviceRemovedReason 來判斷適當的動作。 |
The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. |
| 0x887A0006 | GPU 將不會回應更多命令，最可能的原因是呼叫應用程式傳遞了無效的命令。 |
The GPU will not respond to more commands, most likely because of an invalid command passed by the calling application. |
| 0x887A0007 | GPU 將不會回應更多命令，最可能的原因是某些其他應用程式提交了無效的命令。呼叫應用程式應重新建立裝置後再繼續。 |
The GPU will not respond to more commands, most likely because some other application submitted invalid commands.The calling application should re-create the device and continue. |
| 0x887A000A | 執行呼叫時 GPU 忙碌，而且未執行或排程呼叫。 |
The GPU was busy at the moment when the call was made, and the call was neither executed nor scheduled. |
| 0x887A000B | 某個事件 (例如，電源中斷) 中斷了展示統計資料的收集。任何先前的統計資料應被視為無效。 |
An event (such as power cycle) interrupted the gathering of presentation statistics. Any previous statistics should beconsidered invalid. |
| 0x887A000C | 無法切換至全螢幕模式，因為指定的輸出已在使用中。 |
Fullscreen mode could not be achieved because the specified output was already in use. |
| 0x887A0020 | 內部問題導致驅動程式無法執行指定的作業。驅動程式的狀態可能有問題，應用程式將不會執行。 |
An internal issue prevented the driver from carrying out the specified operation. The driver's state is probably suspect,and the application should not continue. |
| 0x887A0021 | 全域計數器資源已在使用中，因此這個 Direct3D 裝置目前無法使用指定的計數器。 |
A global counter resource was in use, and the specified counter cannot be used by this Direct3D device at this time. |
| 0x887A0022 | 某個資源在呼叫時無法使用，但稍後可能可以使用。 |
A resource is not available at the time of the call, but may become available later. |
| 0x887A0023 | 因為工作階段中斷連線或網路中斷連線，已移除應用程式的遠端裝置。應用程式應呼叫 IDXGIFactory1::IsCurrent 以了解遠端裝置何時可以再次使用。 |
The application's remote device has been removed due to session disconnect or network disconnect.The application should call IDXGIFactory1::IsCurrent to find out when the remote device becomes available again. |
| 0x887A0024 | 裝置已在遠端工作階段期間移除，因為遠端電腦記憶體不足。 |
The device has been removed during a remote session because the remote computer ran out of memory. |
| 0x887A0025 | 進行中的模式變更導致呼叫無法完成。如果稍後嘗試，呼叫可能會成功。 |
An on-going mode change prevented completion of the call. The call may succeed if attempted later. |
| 0x887A0026 | 已放棄機碼式 Mutex。 |
The keyed mutex was abandoned. |
| 0x887A0027 | 逾時值已過，但資源尚無法使用。 |
The timeout value has elapsed and the resource is not yet available. |
| 0x887A0028 | 已關閉輸出複製，因為 Windows 工作階段已結束或已中斷連線。當遠端使用者中斷連線或在本機使用 [切換使用者] 時，就會發生此狀況。 |
The output duplication has been turned off because the Windows session ended or was disconnected.This happens when a remote user disconnects, or when \"switch user\" is used locally. |
| 0x887A0029 | swapchain 內容限定到的 DXGI 輸出 (監視器) 已中斷連線或變更。 |
The DXGI outuput (monitor) to which the swapchain content was restricted, has been disconnected or changed. |
| 0x887A002A | DXGI 無法對 swapchain 提供內容保護。這通常是因為使用的驅動程式太舊或應用程式使用的 swapchain 與內容保護不相容所致。 |
DXGI is unable to provide content protection on the swapchain. This is typically caused by an older driver,or by the application using a swapchain that is incompatible with content protection. |
| 0x887A002B | 應用程式正嘗試使用它沒有必要存取權限的資源。這大多是因為使用唯讀存取權寫入共用資源所導致。 |
The application is trying to use a resource to which it does not have the required access privileges.This is most commonly caused by writing to a shared resource with read-only access. |
| 0x887A002C | 應用程式正嘗試使用已和其他資源關聯的名稱建立共用控制代碼。 |
The application is trying to create a shared handle using a name that is already associated with some other resource. |
| 0x887A002D | 此應用程式要求了某操作，該操作所依賴的 SDK 元件遺失了或不相符。 |
The application requested an operation that depends on an SDK component that is missing or mismatched. |
| 0x887A002E | 應用程式建立的 DXGI 物件已不再是最新的，必須重新建立該物件，才能執行此操作。 |
The DXGI objects that the application has created are no longer current & need to be recreated for this operation to be performed. |
| 0x887A0030 | HW 受保護記憶體不足以供適當的函式使用。 |
Insufficient HW protected memory exits for proper function. |
| 0x887A0031 | 建立此裝置會違反處理程序的動態程式碼原則。 |
Creating this device would violate the process's dynamic code policy. |
| 0x887A0032 | 作業失敗，因為輸出並非由撰寫所控制。 |
The operation failed because the compositor is not in control of the output. |
| 0x887A0033 | 快取已損毀，而且無法開啟或無法重設。 |
The cache is corrupt and either could not be opened or could not be reset. |
| 0x887A0034 | 此項目會導致快取超過其配額。在載入作業上，這可能表示超出記憶體內大小上限。 |
This entry would cause the cache to exceed its quota. On a load operation, this may indicate exceeding the maximum in-memory size. |
| 0x887A0035 | 已發現快取項目，但提供的金鑰不符合項目中儲存的金鑰。 |
A cache entry was found, but the key provided does not match the key stored in the entry. |
| 0x887A0036 | 預期的元素已存在。 |
The desired element already exists. |
| 0x887B0001 | 要求作業時 GPU 忙碌。 |
The GPU was busy when the operation was requested. |
| 0x887B0002 | 驅動程式已拒絕建立此資源。 |
The driver has rejected the creation of this resource. |
| 0x887B0003 | 當應用程式要求存取 GPU 計數器時，GPU 計數器正被另一個處理程序或 d3d 裝置所使用。 |
The GPU counter was in use by another process or d3d device when application requested access to it. |
| 0x887C0003 | 應用程式超過每一 Direct3D 裝置的唯一檢視物件數目上限。到 11.1 為止的功能層級的限制為 2^20。 |
The application has exceeded the maximum number of unique view objects per Direct3D device.The limit is 2^20 for feature levels up to 11.1. |
| 0x887C0004 | 要在延遲的內容上對應的每一命令清單的應用程式的第一個呼叫未使用 D3D11_MAP_WRITE_DISCARD。 |
The application's first call per command list to Map on a deferred context did not use D3D11_MAP_WRITE_DISCARD. |
| 0x887E0001 | 提供的 Blob 與裝置建立所在的配接卡不符。 |
The blob provided does not match the adapter that the device was created on. |
| 0x887E0002 | 提供的 Blob 是針對不同版本的驅動程式所建立，因此必須重新建立。 |
The blob provided was created for a different version of the driver, and must be re-created. |
| 0x88980001 | MILERR_OBJECTBUSY |
MILERR_OBJECTBUSY |
| 0x88980002 | MILERR_INSUFFICIENTBUFFER |
MILERR_INSUFFICIENTBUFFER |
| 0x88980003 | MILERR_WIN32ERROR |
MILERR_WIN32ERROR |
| 0x88980004 | MILERR_SCANNER_FAILED |
MILERR_SCANNER_FAILED |
| 0x88980005 | MILERR_SCREENACCESSDENIED |
MILERR_SCREENACCESSDENIED |
| 0x88980006 | MILERR_DISPLAYSTATEINVALID |
MILERR_DISPLAYSTATEINVALID |
| 0x88980007 | MILERR_NONINVERTIBLEMATRIX |
MILERR_NONINVERTIBLEMATRIX |
| 0x88980008 | MILERR_ZEROVECTOR |
MILERR_ZEROVECTOR |
| 0x88980009 | MILERR_TERMINATED |
MILERR_TERMINATED |
| 0x8898000A | MILERR_BADNUMBER |
MILERR_BADNUMBER |
| 0x88980080 | 發生內部錯誤 (MIL 錯誤)。在已選取組建中，會引發宣告。 |
An internal error (MIL bug) occurred. On checked builds, an assert would be raised. |
| 0x88980084 | 硬體裝置不支援需要轉譯的顯示格式。 |
The display format we need to render is not supported by the hardware device. |
| 0x88980085 | 此方法的呼叫無效。 |
A call to this method is invalid. |
| 0x88980086 | 在已鎖定的物件上嘗試鎖定。 |
Lock attempted on an already locked object. |
| 0x88980087 | 在已解除鎖定的物件上嘗試解除鎖定。 |
Unlock attempted on an unlocked object. |
| 0x88980088 | 沒有可使用此裝置來轉譯文字的演算法 |
No algorithm avaliable to render text with this device |
| 0x88980089 | 字符快取中未包含字符執行轉譯所需的某些字符點陣圖。 |
Some glyph bitmaps, required for glyph run rendering, are not contained in glyph cache. |
| 0x8898008A | 字符快取中的某些字符點陣圖大小超出預期。 |
Some glyph bitmaps in glyph cache are unexpectedly big. |
| 0x8898008B | 撰寫器目前正在忽略已知 Win32 錯誤的標記錯誤。這是為了避免發生錯誤時傳回 S_OK，但仍會在正確的位置回溯堆疊。 |
Marker error for known Win32 errors that are currently being ignored by the compositor. This is to avoid returning S_OK when an error has occurred, but still unwind the stack in the correct location. |
| 0x8898008C | 方針座標未正確排序或包含 NaN。 |
Guideline coordinates are not sorted properly or contain NaNs. |
| 0x8898008D | 此作業沒有可用的 HW 轉譯裝置。 |
No HW rendering device is available for this operation. |
| 0x8898008E | 有無法修復的展示錯誤。呼叫者需要重新建立、重新轉譯整個框架，並嘗試重新展示。這有兩個已知狀況: 1) D3D 驅動程式內部錯誤 2) D3D E_FAIL 2a) 不明的根本原因 b) 當調整大小的速度太快，使 DWM 與 D3D 無法保持同步 |
There has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present.There are two known case for this: 1) D3D Driver Internal error 2) D3D E_FAIL 2a) Unknown root cause b) When resizing too quickly for DWM and D3D stay in sync |
| 0x8898008F | 物件已初始化。 |
The object has already been initialized. |
| 0x88980090 | 物件的大小不符合預期大小。 |
The size of the object does not match the expected size. |
| 0x88980091 | 沒有可用的重新導向介面。 |
No Redirection surface available. |
| 0x88980092 | 不支援遠端處理此內容。 |
Remoting of this content is not supported. |
| 0x88980093 | 不支援「已排入佇列的展示」。 |
Queued Presents are not supported. |
| 0x88980094 | 未在使用「已排入佇列的展示」。 |
Queued Presents are not being used. |
| 0x88980095 | 沒有可用的重新導向介面。呼叫者應重試呼叫。 |
No redirection surface was available. Caller should retry the call. |
| 0x88980096 | 著色器建構失敗，因為它太過複雜。 |
Shader construction failed because it was too complex. |
| 0x88980097 | MROW 嘗試取得讀取鎖定失敗。 |
MROW attempt to get a read lock failed. |
| 0x88980098 | MROW 嘗試更新資料失敗，因為另一個更新尚待處理。 |
MROW attempt to update the data failed because another update was outstanding. |
| 0x88980099 | 著色器編譯失敗。 |
Shader compilation failed. |
| 0x8898009A | 要求的 DX 重新導向介面大小超過紋理大小上限。 |
Requested DX redirection surface size exceeded maximum texture size. |
| 0x8898009B | QueryPerformanceCounter 傳回過去的時間。 |
QueryPerformanceCounter returned a time in the past. |
| 0x8898009D | 主顯示器裝置傳回無效的重新整理的頻率。 |
Primary Display device returned an invalid refresh rate. |
| 0x8898009E | DWM 找不到 LUID 指定的介面卡。 |
DWM can not find the adapter specified by the LUID. |
| 0x8898009F | 不支援要求的點陣圖色彩空間。 |
The requested bitmap color space is not supported. |
| 0x889800A0 | 不支援要求的點陣圖預先過濾狀態。 |
The requested bitmap pre-filtering state is not supported. |
| 0x889800A1 | 存取所指定顯示識別碼的要求點陣圖遭拒。 |
Access is denied to the requested bitmap for the specified display id. |
| 0x88980400 | UCEERR_INVALIDPACKETHEADER |
UCEERR_INVALIDPACKETHEADER |
| 0x88980401 | UCEERR_UNKNOWNPACKET |
UCEERR_UNKNOWNPACKET |
| 0x88980402 | UCEERR_ILLEGALPACKET |
UCEERR_ILLEGALPACKET |
| 0x88980403 | UCEERR_MALFORMEDPACKET |
UCEERR_MALFORMEDPACKET |
| 0x88980404 | UCEERR_ILLEGALHANDLE |
UCEERR_ILLEGALHANDLE |
| 0x88980405 | UCEERR_HANDLELOOKUPFAILED |
UCEERR_HANDLELOOKUPFAILED |
| 0x88980406 | UCEERR_RENDERTHREADFAILURE |
UCEERR_RENDERTHREADFAILURE |
| 0x88980407 | UCEERR_CTXSTACKFRSTTARGETNULL |
UCEERR_CTXSTACKFRSTTARGETNULL |
| 0x88980408 | UCEERR_CONNECTIONIDLOOKUPFAILED |
UCEERR_CONNECTIONIDLOOKUPFAILED |
| 0x88980409 | UCEERR_BLOCKSFULL |
UCEERR_BLOCKSFULL |
| 0x8898040A | UCEERR_MEMORYFAILURE |
UCEERR_MEMORYFAILURE |
| 0x8898040B | UCEERR_PACKETRECORDOUTOFRANGE |
UCEERR_PACKETRECORDOUTOFRANGE |
| 0x8898040C | UCEERR_ILLEGALRECORDTYPE |
UCEERR_ILLEGALRECORDTYPE |
| 0x8898040D | UCEERR_OUTOFHANDLES |
UCEERR_OUTOFHANDLES |
| 0x8898040E | UCEERR_UNCHANGABLE_UPDATE_ATTEMPTED |
UCEERR_UNCHANGABLE_UPDATE_ATTEMPTED |
| 0x8898040F | UCEERR_NO_MULTIPLE_WORKER_THREADS |
UCEERR_NO_MULTIPLE_WORKER_THREADS |
| 0x88980410 | UCEERR_REMOTINGNOTSUPPORTED |
UCEERR_REMOTINGNOTSUPPORTED |
| 0x88980411 | UCEERR_MISSINGENDCOMMAND |
UCEERR_MISSINGENDCOMMAND |
| 0x88980412 | UCEERR_MISSINGBEGINCOMMAND |
UCEERR_MISSINGBEGINCOMMAND |
| 0x88980413 | UCEERR_CHANNELSYNCTIMEDOUT |
UCEERR_CHANNELSYNCTIMEDOUT |
| 0x88980414 | UCEERR_CHANNELSYNCABANDONED |
UCEERR_CHANNELSYNCABANDONED |
| 0x88980415 | UCEERR_UNSUPPORTEDTRANSPORTVERSION |
UCEERR_UNSUPPORTEDTRANSPORTVERSION |
| 0x88980416 | UCEERR_TRANSPORTUNAVAILABLE |
UCEERR_TRANSPORTUNAVAILABLE |
| 0x88980417 | UCEERR_FEEDBACK_UNSUPPORTED |
UCEERR_FEEDBACK_UNSUPPORTED |
| 0x88980418 | UCEERR_COMMANDTRANSPORTDENIED |
UCEERR_COMMANDTRANSPORTDENIED |
| 0x88980419 | UCEERR_GRAPHICSSTREAMUNAVAILABLE |
UCEERR_GRAPHICSSTREAMUNAVAILABLE |
| 0x88980420 | UCEERR_GRAPHICSSTREAMALREADYOPEN |
UCEERR_GRAPHICSSTREAMALREADYOPEN |
| 0x88980421 | UCEERR_TRANSPORTDISCONNECTED |
UCEERR_TRANSPORTDISCONNECTED |
| 0x88980422 | UCEERR_TRANSPORTOVERLOADED |
UCEERR_TRANSPORTOVERLOADED |
| 0x88980423 | UCEERR_PARTITION_ZOMBIED |
UCEERR_PARTITION_ZOMBIED |
| 0x88980500 | MILAVERR_NOCLOCK |
MILAVERR_NOCLOCK |
| 0x88980501 | MILAVERR_NOMEDIATYPE |
MILAVERR_NOMEDIATYPE |
| 0x88980502 | MILAVERR_NOVIDEOMIXER |
MILAVERR_NOVIDEOMIXER |
| 0x88980503 | MILAVERR_NOVIDEOPRESENTER |
MILAVERR_NOVIDEOPRESENTER |
| 0x88980504 | MILAVERR_NOREADYFRAMES |
MILAVERR_NOREADYFRAMES |
| 0x88980505 | MILAVERR_MODULENOTLOADED |
MILAVERR_MODULENOTLOADED |
| 0x88980506 | MILAVERR_WMPFACTORYNOTREGISTERED |
MILAVERR_WMPFACTORYNOTREGISTERED |
| 0x88980507 | MILAVERR_INVALIDWMPVERSION |
MILAVERR_INVALIDWMPVERSION |
| 0x88980508 | MILAVERR_INSUFFICIENTVIDEORESOURCES |
MILAVERR_INSUFFICIENTVIDEORESOURCES |
| 0x88980509 | MILAVERR_VIDEOACCELERATIONNOTAVAILABLE |
MILAVERR_VIDEOACCELERATIONNOTAVAILABLE |
| 0x8898050A | MILAVERR_REQUESTEDTEXTURETOOBIG |
MILAVERR_REQUESTEDTEXTURETOOBIG |
| 0x8898050B | MILAVERR_SEEKFAILED |
MILAVERR_SEEKFAILED |
| 0x8898050C | MILAVERR_UNEXPECTEDWMPFAILURE |
MILAVERR_UNEXPECTEDWMPFAILURE |
| 0x8898050D | MILAVERR_MEDIAPLAYERCLOSED |
MILAVERR_MEDIAPLAYERCLOSED |
| 0x8898050E | MILAVERR_UNKNOWNHARDWAREERROR |
MILAVERR_UNKNOWNHARDWAREERROR |
| 0x8898060E | MILEFFECTSERR_UNKNOWNPROPERTY |
MILEFFECTSERR_UNKNOWNPROPERTY |
| 0x8898060F | MILEFFECTSERR_EFFECTNOTPARTOFGROUP |
MILEFFECTSERR_EFFECTNOTPARTOFGROUP |
| 0x88980610 | MILEFFECTSERR_NOINPUTSOURCEATTACHED |
MILEFFECTSERR_NOINPUTSOURCEATTACHED |
| 0x88980611 | MILEFFECTSERR_CONNECTORNOTCONNECTED |
MILEFFECTSERR_CONNECTORNOTCONNECTED |
| 0x88980612 | MILEFFECTSERR_CONNECTORNOTASSOCIATEDWITHEFFECT |
MILEFFECTSERR_CONNECTORNOTASSOCIATEDWITHEFFECT |
| 0x88980613 | MILEFFECTSERR_RESERVED |
MILEFFECTSERR_RESERVED |
| 0x88980614 | MILEFFECTSERR_CYCLEDETECTED |
MILEFFECTSERR_CYCLEDETECTED |
| 0x88980615 | MILEFFECTSERR_EFFECTINMORETHANONEGRAPH |
MILEFFECTSERR_EFFECTINMORETHANONEGRAPH |
| 0x88980616 | MILEFFECTSERR_EFFECTALREADYINAGRAPH |
MILEFFECTSERR_EFFECTALREADYINAGRAPH |
| 0x88980617 | MILEFFECTSERR_EFFECTHASNOCHILDREN |
MILEFFECTSERR_EFFECTHASNOCHILDREN |
| 0x88980618 | MILEFFECTSERR_ALREADYATTACHEDTOLISTENER |
MILEFFECTSERR_ALREADYATTACHEDTOLISTENER |
| 0x88980619 | MILEFFECTSERR_NOTAFFINETRANSFORM |
MILEFFECTSERR_NOTAFFINETRANSFORM |
| 0x8898061A | MILEFFECTSERR_EMPTYBOUNDS |
MILEFFECTSERR_EMPTYBOUNDS |
| 0x8898061B | MILEFFECTSERR_OUTPUTSIZETOOLARGE |
MILEFFECTSERR_OUTPUTSIZETOOLARGE |
| 0x88980700 | DWMERR_STATE_TRANSITION_FAILED |
DWMERR_STATE_TRANSITION_FAILED |
| 0x88980701 | DWMERR_THEME_FAILED |
DWMERR_THEME_FAILED |
| 0x88980702 | DWMERR_CATASTROPHIC_FAILURE |
DWMERR_CATASTROPHIC_FAILURE |
| 0x88980800 | DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED |
DCOMPOSITION_ERROR_WINDOW_ALREADY_COMPOSED |
| 0x88980801 | DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED |
DCOMPOSITION_ERROR_SURFACE_BEING_RENDERED |
| 0x88980802 | DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED |
DCOMPOSITION_ERROR_SURFACE_NOT_BEING_RENDERED |
| 0x88982F04 | 轉碼器的狀態錯誤。 |
The codec is in the wrong state. |
| 0x88982F05 | 值超出範圍。 |
The value is out of range. |
| 0x88982F07 | 影像格式不明。 |
The image format is unknown. |
| 0x88982F0B | SDK 版本不受支援。 |
The SDK version is unsupported. |
| 0x88982F0C | 元件未初始化。 |
The component is not initialized. |
| 0x88982F0D | 已經有待處理的讀取或寫入鎖定。 |
There is already an outstanding read or write lock. |
| 0x88982F40 | 找不到指定的點陣圖屬性。 |
The specified bitmap property cannot be found. |
| 0x88982F41 | 點陣圖轉碼器不支援點陣圖屬性。 |
The bitmap codec does not support the bitmap property. |
| 0x88982F42 | 點陣圖屬性大小無效。 |
The bitmap property size is invalid. |
| 0x88982F43 | 發生未知的錯誤。 |
An unknown error has occurred. |
| 0x88982F44 | 點陣圖轉碼器不支援縮圖。 |
The bitmap codec does not support a thumbnail. |
| 0x88982F45 | 點陣圖調色盤無法使用。 |
The bitmap palette is unavailable. |
| 0x88982F46 | 要求了太多掃描線。 |
Too many scanlines were requested. |
| 0x88982F49 | 點陣圖界限不符合點陣圖尺寸。 |
The bitmap bounds do not match the bitmap dimensions. |
| 0x88982F50 | 找不到元件。 |
The component cannot be found. |
| 0x88982F51 | 點陣圖大小超出有效範圍。 |
The bitmap size is outside the valid range. |
| 0x88982F52 | 要寫入點陣圖的中繼資料太多。 |
There is too much metadata to be written to the bitmap. |
| 0x88982F60 | 影像無法辨識。 |
The image is unrecognized. |
| 0x88982F61 | 影像標頭無法辨識。 |
The image header is unrecognized. |
| 0x88982F62 | 遺漏點陣圖框架。 |
The bitmap frame is missing. |
| 0x88982F63 | 影像中繼資料標頭無法辨識。 |
The image metadata header is unrecognized. |
| 0x88982F70 | 資料流資料無法辨識。 |
The stream data is unrecognized. |
| 0x88982F71 | 無法寫入資料流。 |
Failed to write to the stream. |
| 0x88982F72 | 無法從資料流讀取。 |
Failed to read from the stream. |
| 0x88982F73 | 資料流無法使用。 |
The stream is not available. |
| 0x88982F80 | 不支援點陣圖像素格式。 |
The bitmap pixel format is unsupported. |
| 0x88982F81 | 不支援作業。 |
The operation is unsupported. |
| 0x88982F8A | 元件註冊無效。 |
The component registration is invalid. |
| 0x88982F8B | 元件初始設定失敗。 |
The component initialization has failed. |
| 0x88982F8C | 配置的緩衝區不足。 |
The buffer allocated is insufficient. |
| 0x88982F8D | 重複的中繼資料已存在。 |
Duplicate metadata is present. |
| 0x88982F8E | 點陣圖屬性類型不是預期值。 |
The bitmap property type is unexpected. |
| 0x88982F8F | 大小不是預期值。 |
The size is unexpected. |
| 0x88982F90 | 屬性查詢無效。 |
The property query is invalid. |
| 0x88982F91 | 中繼資料類型不是預期值。 |
The metadata type is unexpected. |
| 0x88982F92 | 指定的點陣圖屬性只有在根層級才有效。 |
The specified bitmap property is only valid at root level. |
| 0x88982F93 | 查詢字串包含無效的字元。 |
The query string contains an invalid character. |
| 0x88982F94 | Windows 轉碼器收到來自 Win32 系統的錯誤。 |
Windows Codecs received an error from the Win32 system. |
| 0x88982F95 | 要求的詳細資訊層級不存在。 |
The requested level of detail is not present. |
| 0x88982F96 | 掃描索引無效。 |
The scan index is invalid. |
| 0x88985000 | 指示輸入檔案 (例如，字型檔案) 中的錯誤。 |
Indicates an error in an input file such as a font file. |
| 0x88985001 | 指示在 DirectWrite 程式碼中發生的錯誤，該錯誤不應發生，但可以安全復原。 |
Indicates an error originating in DirectWrite code, which is not expected to occur but is safe to recover from. |
| 0x88985002 | 指示指定的字型不存在。 |
Indicates the specified font does not exist. |
| 0x88985003 | 無法開啟字型檔案，因為檔案、目錄、網路位置、磁碟機或其他存放裝置不存在或無法使用。 |
A font file could not be opened because the file, directory, network location, drive, or other storage location does not exist or is unavailable. |
| 0x88985004 | 字型檔案存在，但因為存取被拒、共用違規或類似的錯誤而無法開啟。 |
A font file exists but could not be opened due to access denied, sharing violation, or similar error. |
| 0x88985005 | 字型收集因為系統中的變更而過時。 |
A font collection is obsolete due to changes in the system. |
| 0x88985006 | 指定的介面已註冊。 |
The given interface is already registered. |
| 0x88985007 | 字型快取包含無效的資料。 |
The font cache contains invalid data. |
| 0x88985008 | 字型快取檔案對應至不同的 DirectWrite 版本。 |
A font cache file corresponds to a different version of DirectWrite. |
| 0x88985009 | 此類型的字型不支援該作業。 |
The operation is not supported for this type of font. |
| 0x8898500A | 文字轉譯器介面的版本不相容。 |
The version of the text renderer interface is not compatible. |
| 0x8898500B | 流程方向與閱讀方向衝突。它們必須彼此垂直。 |
The flow direction conflicts with the reading direction. They must be perpendicular to each other. |
| 0x8898500C | 字型或字符繪製順序未包含任何彩色字符。 |
The font or glyph run does not contain any colored glyphs. |
| 0x88990001 | 物件不是正確狀態，因此無法處理該方法。 |
The object was not in the correct state to process the method. |
| 0x88990002 | 物件尚未初始化。 |
The object has not yet been initialized. |
| 0x88990004 | 幾何掃描器無法處理資料。 |
The geometry scanner failed to process the data. |
| 0x88990005 | Direct2D 無法存取螢幕。 |
Direct2D could not access the screen. |
| 0x88990006 | 無法判斷有效的顯示狀態。 |
A valid display state could not be determined. |
| 0x88990007 | 提供的向量為零。 |
The supplied vector is zero. |
| 0x88990008 | 發生內部錯誤 (Direct2D 錯誤)。在已選取的組建中，我們會宣告。應用程式應該關閉 Direct2D 的這個執行個體，而且應該考慮重新啟動其處理程序。 |
An internal error (Direct2D bug) occurred. On checked builds, we would assert. The application should close this instance of Direct2D and should consider restarting its process. |
| 0x88990009 | 硬體裝置不支援需要轉譯的顯示格式 Direct2D。 |
The display format Direct2D needs to render is not supported by the hardware device. |
| 0x8899000B | 沒有可用的硬體轉譯裝置可執行此作業。 |
No hardware rendering device is available for this operation. |
| 0x8899000C | 有可修復的展示錯誤。呼叫者需要重新建立、重新轉譯整個框架，並嘗試重新展示。 |
There has been a presentation error that may be recoverable. The caller needs to recreate, rerender the entire frame, and reattempt present. |
| 0x8899000F | 要求的 DirectX 介面大小超過紋理大小上限。 |
Requested DirectX surface size exceeded maximum texture size. |
| 0x88990010 | 不支援要求的 Direct2D 版本。 |
The requested Direct2D version is not supported. |
| 0x88990011 | 無效的數字。 |
Invalid number. |
| 0x88990012 | 必須從相同的 Factory 執行個體建立一起使用的物件。 |
Objects used together must be created from the same factory instance. |
| 0x88990013 | 圖層資源在任一時間點只能使用一次。 |
A layer resource can only be in use once at any point in time. |
| 0x88990014 | Pop 呼叫不符合對應的 Push 呼叫。 |
The pop call did not match the corresponding push call. |
| 0x88990015 | 資源在錯誤的轉譯目標上呈現。 |
The resource was realized on the wrong render target. |
| 0x88990016 | Push 呼叫的數目與 Pop 呼叫的數目不一致。 |
The push and pop calls were unbalanced. |
| 0x88990017 | 在套用圖層或剪輯矩形時，請嘗試從轉譯目標複製。 |
Attempt to copy from a render target while a layer or clip rect is applied. |
| 0x88990018 | 呼叫的筆刷類型不相容。 |
The brush types are incompatible for the call. |
| 0x88990019 | 發生不明的 win32 失敗。 |
An unknown win32 failure occurred. |
| 0x8899001A | 轉譯目標與 GDI 不相容。 |
The render target is not compatible with GDI. |
| 0x8899001B | 文字用戶端繪圖效果物件的類型錯誤。 |
A text client drawing effect object is of the wrong type. |
| 0x8899001C | 在傳回對應的 DrawText 或 DrawTextLayout 呼叫後，應用程式保有對 IDWriteTextRenderer 介面的參照。IDWriteTextRenderer 執行個體將無效。 |
The application is holding a reference to the IDWriteTextRenderer interface after the corresponding DrawText or DrawTextLayout call has returned. The IDWriteTextRenderer instance will be invalid. |
| 0x8899001D | 要求的大小大於 Direct3D 裝置目前的功能層級保證的支援紋理大小。 |
The requested size is larger than the guaranteed supported texture size at the Direct3D device's current feature level. |
| 0x8899001E | 圖表中有設定錯誤。 |
There was a configuration error in the graph. |
| 0x8899001F | 圖表中有內部設定錯誤。 |
There was a internal configuration error in the graph. |
| 0x88990020 | 圖表中有循環。 |
There was a cycle in the graph. |
| 0x88990021 | 無法使用具有 D2D1_BITMAP_OPTIONS_CANNOT_DRAW 選項的點陣圖繪製。 |
Cannot draw with a bitmap that has the D2D1_BITMAP_OPTIONS_CANNOT_DRAW option. |
| 0x88990022 | 當目標點陣圖有待處理的參照時，作業無法完成。 |
The operation cannot complete while there are outstanding references to the target bitmap. |
| 0x88990023 | 作業失敗，因為原始的目標目前未繫結為目標。 |
The operation failed because the original target is not currently bound as a target. |
| 0x88990024 | 無法將影像設定為目標，因為它是效果或未設定 D2D1_BITMAP_OPTIONS_TARGET 旗標的點陣圖。 |
Cannot set the image as a target because it is either an effect or is a bitmap that does not have the D2D1_BITMAP_OPTIONS_TARGET flag set. |
| 0x88990025 | 無法使用目前繫結為目標點陣圖的點陣圖繪製。 |
Cannot draw with a bitmap that is currently bound as the target bitmap. |
| 0x88990026 | D3D 裝置沒有足夠能力可執行要求的動作。 |
D3D Device does not have sufficient capabilities to perform the requested action. |
| 0x88990027 | 無法使用內容目前的並排顯示設定來轉譯圖表。 |
The graph could not be rendered with the context's current tiling settings. |
| 0x88990028 | 所提供用來取消註冊的 CLSID 未對應至已註冊的效果。 |
The CLSID provided to Unregister did not correspond to a registered effect. |
| 0x88990029 | 指定的內容不存在。 |
The specified property does not exist. |
| 0x8899002A | 指定的子屬性不存在。 |
The specified sub-property does not exist. |
| 0x8899002B | 在列印工作關閉後呼叫了 AddPage 或 Close。 |
AddPage or Close called after print job is already closed. |
| 0x8899002C | 建立列印控制項期間發生錯誤。指示 Direct2D 列印控制項不支援任何套件目標類型 (代表印表機格式)。 |
Error during print control creation. Indicates that none of the package target types (representing printer formats) are supported by Direct2D print control. |
| 0x8899002D | 某個效果嘗試使用含有太多輸入的轉換。 |
An effect attempted to use a transform with too many inputs. |
| 0x8899002E | 解碼或剖析要求的字符影像時發生錯誤。 |
An error was encountered while decoding or parsing the requested glyph image. |
| 0x89010001 | 系統已暫停該操作並執行優先順序較高的操作。您稍後必須繼續該操作。 |
The operation was preempted by a higher priority operation. It must be resumed later. |
| 0x89020001 | 函式無法執行，因為系統已將它刪除或已為它執行記憶體回收。 |
Function could not execute because it was deleted or garbage collected. |
| 0xC0090001 | 所指定的事件目前不在稽核中。 |
The specified event is currently not being audited. |
| 0xC0090002 | SID 篩選操作移除了所有的 SID。 |
The SID filtering operation removed all SIDs. |
| 0xC0090003 | 呼叫應用程式的商務規則指令碼已停用。 |
Business rule scripts are disabled for the calling application. |
| 0xC02605E8 | 因為目前的工作階段正在改變其類型，所以函數失敗。當目前的工作階段正在改變其類型時，不能呼叫這個函數。目前有三種工作階段類型: 主控台、中斷連線及遠端。 |
The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type. There are currently three types of sessions: console, disconnected and remote. |
| 0xC0261003 | 取得之監視器描述元的總和檢查碼無效。 |
Checksum of the obtained monitor descriptor is invalid. |
| 0xC0261004 | 監視器描述元包含的標準時間區塊無效。 |
Monitor descriptor contains an invalid standard timing block. |
| 0xC0261005 | 其中一個 MSMonitorClass WMI 子類別的 WMI 資料區塊登錄失敗。 |
WMI data block registration failed for one of the MSMonitorClass WMI subclasses. |
| 0xC0261006 | 提供的監視器描述元區塊已損毀或不包含監視器的詳細序號。 |
Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number. |
| 0xC0261007 | 提供的監視器描述元區塊已損毀或不包含監視器的使用者易記名稱。 |
Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name. |
| 0xC0261008 | 指定的 (位移、大小) 區域中沒有任何監視器描述元資料。 |
There is no monitor descriptor data at the specified (offset, size) region. |
| 0xC0261009 | 監視器描述元包含的詳細時間區塊無效。 |
Monitor descriptor contains an invalid detailed timing block. |
| 0xC026100A | 監視器描述元包含不正確的製造日期。 |
Monitor descriptor contains invalid manufacture date. |
| 0xC0262000 | 需要獨佔模式擁有權，才能建立不受管理的主要配置。 |
Exclusive mode ownership is needed to create unmanaged primary allocation. |
| 0xC0262001 | 驅動程式需要更多 DMA 緩衝區空間，才能完成要求的作業。 |
The driver needs more DMA buffer space in order to complete the requested operation. |
| 0xC0262002 | 指定的顯示器介面卡控制代碼無效。 |
Specified display adapter handle is invalid. |
| 0xC0262003 | 指定的顯示器介面卡及所有其狀態已重設。 |
Specified display adapter and all of its state has been reset. |
| 0xC0262004 | 驅動程式堆疊與預期的驅動程式模組不符。 |
The driver stack doesn't match the expected driver model. |
| 0xC0262005 | 發生呈現的動作，但是最後卻出現變更的桌面模式 |
Present happened but ended up into the changed desktop mode |
| 0xC0262006 | 因為桌面閉塞，所以無法呈現任何項目 |
Nothing to present due to desktop occlusion |
| 0xC0262007 | 因為拒絕桌面的存取，所以無法呈現 |
Not able to present due to denial of desktop access |
| 0xC0262008 | 無法呈現色彩轉換 |
Not able to present with color convertion |
| 0xC0262009 | 核心驅動程式偵測到和使用者模式驅動程式的版本不符。 |
The kernel driver detected a version mismatch between it and the user mode driver. |
| 0xC026200B | 已停用目前的重新導向 (桌面視窗管理子系統已經關閉)。 |
Present redirection is disabled (desktop windowing management subsystem is off). |
| 0xC026200C | 前一個獨佔 VidPn 來源擁有者已釋出其擁有權 |
Previous exclusive VidPn source owner has released its ownership |
| 0xC026200D | Window DC 無法用於簡報 |
Window DC is not available for presentation |
| 0xC026200E | 已停用無視窗呈現 (桌面視窗管理子系統已經關閉)。 |
Windowless present is disabled (desktop windowing management subsystem is off). |
| 0xC0262100 | 視訊記憶體不足，無法完成作業。 |
Not enough video memory available to complete the operation. |
| 0xC0262101 | 無法探查並鎖定配置的基本記憶體。 |
Couldn't probe and lock the underlying memory of an allocation. |
| 0xC0262102 | 配置目前忙碌中。 |
The allocation is currently busy. |
| 0xC0262103 | 參照的物件已達到參考計數上限，且無法再繼續參照。 |
An object being referenced has reach the maximum reference count already and can't be reference further. |
| 0xC0262104 | 因為某些現存的條件導致問題無法解決。應該稍後再嘗試看還有沒有問題。 |
A problem couldn't be solved due to some currently existing condition. The problem should be tried again later. |
| 0xC0262105 | 因為某些現存的條件導致問題無法解決。應該立即嘗試看還有沒有問題。 |
A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately. |
| 0xC0262106 | 配置無效。 |
The allocation is invalid. |
| 0xC0262107 | 目前沒有任何非拌和光圈可使用。 |
No more unswizzling aperture are currently available. |
| 0xC0262108 | 光圈無法拌和目前的配置。 |
The current allocation can't be unswizzled by an aperture. |
| 0xC0262109 | 因為無法收回釘選的配置，要求失敗。 |
The request failed because a pinned allocation can't be evicted. |
| 0xC0262110 | 無法在配置的目前區段位置中，針對指定作業使用配置。 |
The allocation can't be used from its current segment location for the specified operation. |
| 0xC0262111 | 在目前的命令緩衝區中無法使用封鎖的配置。 |
A locked allocation can't be used in the current command buffer. |
| 0xC0262112 | 參照的配置已永久關閉。 |
The allocation being referenced has been closed permanently. |
| 0xC0262113 | 正在參照的配置執行個體無效。 |
An invalid allocation instance is being referenced. |
| 0xC0262114 | 正在參照的配置控制代碼無效。 |
An invalid allocation handle is being referenced. |
| 0xC0262115 | 正在參照的配置不屬於目前的裝置。 |
The allocation being referenced doesn't belong to the current device. |
| 0xC0262116 | 指定的配置遺失內容。 |
The specified allocation lost its content. |
| 0xC0262200 | 在指定的裝置上偵測到 GPU 例外狀況。將無法排程裝置。 |
GPU exception is detected on the given device. The device is not able to be scheduled. |
| 0xC0262300 | 指定的 VidPN 拓撲無效。 |
Specified VidPN topology is invalid. |
| 0xC0262301 | 指定的 VidPN 拓撲有效，但顯示器介面卡的這個模組不予以支援。 |
Specified VidPN topology is valid but is not supported by this model of the display adapter. |
| 0xC0262302 | 指定的 VidPN 拓撲有效，但因為目前的資源配置，所以此時顯示器介面卡不予以支援。 |
Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources. |
| 0xC0262303 | 指定的 VidPN 控制代碼無效。 |
Specified VidPN handle is invalid. |
| 0xC0262304 | 指定的視訊呈現來源無效。 |
Specified video present source is invalid. |
| 0xC0262305 | 指定的視訊呈現目標無效。 |
Specified video present target is invalid. |
| 0xC0262306 | 不支援指定的 VidPN 樣式 (例如，至少有兩個釘選的模式無法交互運作)。 |
Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional). |
| 0xC0262308 | 指定的 VidPN 來源模式集無效。 |
Specified VidPN source mode set is invalid. |
| 0xC0262309 | 指定的 VidPN 目標模式集無效。 |
Specified VidPN target mode set is invalid. |
| 0xC026230A | 指定的視訊訊號頻率無效。 |
Specified video signal frequency is invalid. |
| 0xC026230B | 指定的視訊訊號作用區無效。 |
Specified video signal active region is invalid. |
| 0xC026230C | 指定的視訊訊號總區域無效。 |
Specified video signal total region is invalid. |
| 0xC0262310 | 指定的視訊呈現來源模式無效。 |
Specified video present source mode is invalid. |
| 0xC0262311 | 指定的視訊呈現目標模式無效。 |
Specified video present target mode is invalid. |
| 0xC0262312 | 釘選的模式必須保留在 VidPN 之交互運作樣式列舉的集合上。 |
Pinned mode must remain in the set on VidPN's cofunctional modality enumeration. |
| 0xC0262313 | 指定的視訊呈現路徑已存在 VidPN 拓撲中。 |
Specified video present path is already in VidPN's topology. |
| 0xC0262314 | 指定的模式已存在於模式集中。 |
Specified mode is already in the mode set. |
| 0xC0262315 | 指定的視訊呈現來源集無效。 |
Specified video present source set is invalid. |
| 0xC0262316 | 指定的視訊呈現目標集無效。 |
Specified video present target set is invalid. |
| 0xC0262317 | 指定的視訊呈現來源已存在視訊呈現來源集中。 |
Specified video present source is already in the video present source set. |
| 0xC0262318 | 指定的視訊呈現目標已存在視訊呈現目標集中。 |
Specified video present target is already in the video present target set. |
| 0xC0262319 | 指定的 VidPN 呈現路徑無效。 |
Specified VidPN present path is invalid. |
| 0xC026231A | 迷你連接埠沒有增強指定 VidPN 拓撲的建議。 |
Miniport has no recommendation for augmentation of the specified VidPN's topology. |
| 0xC026231B | 指定的監視器頻率範圍集無效。 |
Specified monitor frequency range set is invalid. |
| 0xC026231C | 指定的監視器頻率範圍無效。 |
Specified monitor frequency range is invalid. |
| 0xC026231D | 指定的頻率範圍不在指定的監視器頻率範圍集中。 |
Specified frequency range is not in the specified monitor frequency range set. |
| 0xC026231F | 指定的頻率範圍已存在指定的監視器頻率範圍集中。 |
Specified frequency range is already in the specified monitor frequency range set. |
| 0xC0262320 | 指定的模式集已過期。請重新取得新模式集。 |
Specified mode set is stale. Please reacquire the new mode set. |
| 0xC0262321 | 指定的監視器來源模式集無效。 |
Specified monitor source mode set is invalid. |
| 0xC0262322 | 指定的監視器來源模式無效。 |
Specified monitor source mode is invalid. |
| 0xC0262323 | 迷你連接埠針對提供一個可提供目前顯示器介面卡配置的功能性 VidPN 要求沒有任何建議。 |
Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration. |
| 0xC0262324 | 指定模式的識別碼已由集合中的其他模式使用中。 |
ID of the specified mode is already used by another mode in the set. |
| 0xC0262325 | 系統無法判定顯示器介面卡及連接到介面卡之監視器皆支援的模式。 |
System failed to determine a mode that is supported by both the display adapter and the monitor connected to it. |
| 0xC0262326 | 視訊呈現目標的數目必須大於或等於視訊呈現來源的數目。 |
Number of video present targets must be greater than or equal to the number of video present sources. |
| 0xC0262327 | 指定的呈現路徑不在 VidPN 拓撲中。 |
Specified present path is not in VidPN's topology. |
| 0xC0262328 | 顯示卡必須至少具有一個視訊呈現來源。 |
Display adapter must have at least one video present source. |
| 0xC0262329 | 顯示卡必須至少具有一個視訊呈現目標。 |
Display adapter must have at least one video present target. |
| 0xC026232A | 指定的監視器描述元集無效。 |
Specified monitor descriptor set is invalid. |
| 0xC026232B | 指定的監視器描述元無效。 |
Specified monitor descriptor is invalid. |
| 0xC026232C | 指定的描述元不在指定的監視器描述元集中。 |
Specified descriptor is not in the specified monitor descriptor set. |
| 0xC026232D | 指定的描述元已存在指定的監視器描述元集中。 |
Specified descriptor is already in the specified monitor descriptor set. |
| 0xC026232E | 指定監視器描述元的識別碼已由集合中的其他描述元使用中。 |
ID of the specified monitor descriptor is already used by another descriptor in the set. |
| 0xC026232F | 指定的視訊呈現目標子集類型無效。 |
Specified video present target subset type is invalid. |
| 0xC0262330 | 兩個或兩個以上的指定資源不如介面語意定義般的互相關聯。 |
Two or more of the specified resources are not related to each other, as defined by the interface semantics. |
| 0xC0262331 | 指定視訊呈現來源的識別碼已由集合中的其他來源使用中。 |
ID of the specified video present source is already used by another source in the set. |
| 0xC0262332 | 指定視訊呈現目標的識別碼已由集合中的其他目標使用中。 |
ID of the specified video present target is already used by another target in the set. |
| 0xC0262333 | 指定的 VidPN 來源無法使用，因為沒有可用的 VidPN 目標可連接。 |
Specified VidPN source cannot be used because there is no available VidPN target to connect it to. |
| 0xC0262334 | 剛裝的監視器無法與顯示器介面卡產生關聯。 |
Newly arrived monitor could not be associated with a display adapter. |
| 0xC0262335 | 問題顯示器介面卡沒有關聯的 VidPN 管理員。 |
Display adapter in question does not have an associated VidPN manager. |
| 0xC0262336 | 問題顯示器介面卡的 VidPN 管理員沒有作用中的 VidPN。 |
VidPN manager of the display adapter in question does not have an active VidPN. |
| 0xC0262337 | 指定的 VidPN 拓撲已過期。請重新取得新拓撲。 |
Specified VidPN topology is stale. Please reacquire the new topology. |
| 0xC0262338 | 在指定的視訊呈現目標上沒有連接的監視器。 |
There is no monitor connected on the specified video present target. |
| 0xC0262339 | 指定的來源不是指定的 VidPN 拓撲的一部分。 |
Specified source is not part of the specified VidPN's topology. |
| 0xC026233A | 指定的主要表面大小無效。 |
Specified primary surface size is invalid. |
| 0xC026233B | 指定可見區域大小無效。 |
Specified visible region size is invalid. |
| 0xC026233C | 指定的分散大小無效。 |
Specified stride is invalid. |
| 0xC026233D | 指定的像素格式無效。 |
Specified pixel format is invalid. |
| 0xC026233E | 指定的色彩底色無效。 |
Specified color basis is invalid. |
| 0xC026233F | 指定的像素值存取模式無效。 |
Specified pixel value access mode is invalid. |
| 0xC0262340 | 指定的目標不是指定的 VidPN 拓撲的一部分。 |
Specified target is not part of the specified VidPN's topology. |
| 0xC0262341 | 無法取得顯示器模式管理介面。 |
Failed to acquire display mode management interface. |
| 0xC0262342 | 指定的 VidPN 來源已為 DMM 用戶端所擁有，在該用戶端釋放前無法使用。 |
Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it. |
| 0xC0262343 | 指定的 VidPN 為使用中，所以無法存取。 |
Specified VidPN is active and cannot be accessed. |
| 0xC0262344 | 指定的 VidPN 呈現路徑重要性序數無效。 |
Specified VidPN present path importance ordinal is invalid. |
| 0xC0262345 | 指定的 VidPN 呈現路徑內容幾何轉換無效。 |
Specified VidPN present path content geometry transformation is invalid. |
| 0xC0262346 | 相對 VidPN 呈現路徑上不支援指定的內容幾何轉換。 |
Specified content geometry transformation is not supported on the respective VidPN present path. |
| 0xC0262347 | 指定的 Gamma ramp 無效。 |
Specified gamma ramp is invalid. |
| 0xC0262348 | 相對 VidPN 呈現路徑上不支援指定的 Gamma ramp。 |
Specified gamma ramp is not supported on the respective VidPN present path. |
| 0xC0262349 | 相對 VidPN 呈現路徑上不支援多重取樣。 |
Multi-sampling is not supported on the respective VidPN present path. |
| 0xC026234A | 指定的模式不在指定的模式集中。 |
Specified mode is not in the specified mode set. |
| 0xC026234D | 指定的 VidPN 拓撲建議原因無效。 |
Specified VidPN topology recommendation reason is invalid. |
| 0xC026234E | 指定的 VidPN 呈現路徑內容類型無效。 |
Specified VidPN present path content type is invalid. |
| 0xC026234F | 指定的 VidPN 呈現路徑內容保護類型無效。 |
Specified VidPN present path copy protection type is invalid. |
| 0xC0262350 | 在任何時間內，指定 VidPN 來源/目標中都不能存在一個以上的未指派模式集。 |
No more than one unassigned mode set can exist at any given time for a given VidPN source/target. |
| 0xC0262352 | 指定的掃描線排序類型不正確。 |
Specified scanline ordering type is invalid. |
| 0xC0262353 | 指定的 VidPN 不允許拓撲變更。 |
Topology changes are not allowed for the specified VidPN. |
| 0xC0262354 | 已經在指定的拓撲中使用所有可用的重要性序數。 |
All available importance ordinals are already used in specified topology. |
| 0xC0262355 | 指定之主要表面的私密格式屬性和目前的主要表面不同 |
Specified primary surface has a different private format attribute than the current primary surface |
| 0xC0262356 | 指定的模式剪除演算法不正確 |
Specified mode pruning algorithm is invalid |
| 0xC0262357 | 指定的監視器功能來源不正確。 |
Specified monitor capability origin is invalid. |
| 0xC0262358 | 指定的監視器頻率範圍限制不正確。 |
Specified monitor frequency range constraint is invalid. |
| 0xC0262359 | 已經達到呈現路徑的支援數目上限。 |
Maximum supported number of present paths has been reached. |
| 0xC026235A | Miniport 已要求取消指定之 VidPN 的拓撲的指定來源的增強 (augmentation)。 |
Miniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology. |
| 0xC026235B | 無法識別指定的用戶端類型。 |
Specified client type was not recognized. |
| 0xC026235C | 此介面卡上並未設定用戶端 VidPN (例如，此介面卡上未發生由使用者模式起始的模式變更)。 |
Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet). |
| 0xC0262400 | 指定的顯示器介面卡子裝置已具有與其連接的外部裝置。 |
Specified display adapter child device already has an external device connected to it. |
| 0xC0262401 | 指定的顯示器介面卡子裝置不支援報告描述元曝光。 |
Specified display adapter child device does not support descriptor exposure. |
| 0xC0262430 | 顯示器介面卡未連結到任何其他介面卡上。 |
The display adapter is not linked to any other adapters. |
| 0xC0262431 | 尚未列舉連結組態中的主要介面卡。 |
Lead adapter in a linked configuration was not enumerated yet. |
| 0xC0262432 | 尚未列舉連結組態中的某些鏈結介面卡。 |
Some chain adapters in a linked configuration were not enumerated yet. |
| 0xC0262433 | 因為發生無法辨識的失敗，所以連結介面卡的鏈結還無法啟動。 |
The chain of linked adapters is not ready to start because of an unknown failure. |
| 0xC0262434 | 當鏈結連結未啟動時，已嘗試啟動主要連結顯示器介面卡。 |
An attempt was made to start a lead link display adapter when the chain links were not started yet. |
| 0xC0262435 | 當鏈結連結關閉時，已嘗試啟動主要連結顯示器介面卡。 |
An attempt was made to power up a lead link display adapter when the chain links were powered down. |
| 0xC0262436 | 介面卡連結的狀態不一致。不是所有的介面卡都處於預期的 PNP/Power 狀態。 |
The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state. |
| 0xC0262438 | 驅動程式嘗試啟動的與 POST 顯示器介面卡驅動程式嘗試啟動的不同。 |
The driver trying to start is not the same as the driver for the POSTed display adapter. |
| 0xC026243B | 正在嘗試的操作需要顯示器介面卡處於完全非使用中狀態。 |
An operation is being attempted that requires the display adapter to be in a quiescent state. |
| 0xC0262500 | 驅動程式不支援 OPM。 |
The driver does not support OPM. |
| 0xC0262501 | 驅動程式不支援 COPP。 |
The driver does not support COPP. |
| 0xC0262502 | 驅動程式不支援 UAB。 |
The driver does not support UAB. |
| 0xC0262503 | 指定的加密參數無效。 |
The specified encrypted parameters are invalid. |
| 0xC0262505 | 傳遞到此函式的 GDI 顯示器裝置沒有任何使用中的視訊輸出。 |
The GDI display device passed to this function does not have any active video outputs. |
| 0xC026250B | 發生內部錯誤，造成作業失敗。 |
An internal error caused this operation to fail. |
| 0xC026250C | 因為呼叫者傳遞到無效的 OPM 使用者模式控制代碼，所以函數失敗。 |
The function failed because the caller passed in an invalid OPM user mode handle. |
| 0xC026250E | 因為傳遞到函數的憑證緩衝區太小，所以無法傳回憑證。 |
A certificate could not be returned because the certificate buffer passed to the function was too small. |
| 0xC026250F | 無法建立視訊輸出，因為框架緩衝區處於延伸模式。 |
A video output could not be created because the frame buffer is in spanning mode. |
| 0xC0262510 | 無法建立視訊輸出，因為框架緩衝區處於電影模式。 |
A video output could not be created because the frame buffer is in theater mode. |
| 0xC0262511 | 函數失敗，因為顯示卡的硬體功能掃描無法確認圖形硬體。 |
The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware. |
| 0xC0262512 | 傳送到此函數的 HDCP 系統更新訊息未遵守 HDCP 1.1 規格第 5 條的規定。 |
The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification. |
| 0xC0262513 | 視訊輸出無法啟用高頻寬數位內容保護 (DHCP) 系統，因為它不支援 HDCP。 |
The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP. |
| 0xC0262514 | 視訊輸出無法啟用類比複製保護 (ACP)，因為它不支援 ACP。 |
The video output cannot enable Analogue Copy Protection (ACP) because it does not support ACP. |
| 0xC0262515 | 視訊輸出無法啟用內容產生管理系統類比 (CGMS-A) 保護技術，因為它不支援 CGMS-A。 |
The video output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A. |
| 0xC0262516 | IOPMVideoOutput::GetInformation 方法無法傳回所使用的 SRM 版本，因為應用程式從未順利將 SRM 傳送至視訊輸出。 |
The IOPMVideoOutput::GetInformation method cannot return the version of the SRM being used because the application never successfully passed an SRM to the video output. |
| 0xC0262517 | IOPMVideoOutput::Configure 方法無法啟用指定的輸出保護技術，因為輸出的螢幕解析度太高。 |
The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high. |
| 0xC0262518 | IOPMVideoOutput::Configure 方法無法啟用 HDCP，因為顯示器介面卡的 HDCP 硬體已由其他實體輸出使用中。 |
The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs. |
| 0xC026251A | 作業系統已非同步摧毀此 OPM 視訊輸出，因為作業系統的狀態已變更。這個錯誤的發生原因，通常是與此視訊輸出關聯的監視器 PDO 已移除、與此視訊輸出關聯的監視器 PDO 已停止、視訊輸出的工作階段變成非主控台工作階段，或視訊輸出的桌面變成非使用中桌面。 |
The operating system asynchronously destroyed this OPM video output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this video output was removed, the monitor PDO associated with this video output was stopped, the video output's session became a non-console session or the video output's desktop became an inactive desktop. |
| 0xC026251B | 因為工作階段正在變更其類型，所以方法失敗。當工作階段正在變更其類型時，無法呼叫任何 IOPMVideoOutput 方法。目前有三種類型的工作階段: 主控台、已中斷連線及遠端。 |
The method failed because the session is changing its type. No IOPMVideoOutput methods can be called when a session is changing its type. There are currently three types of sessions: console, disconnected and remote. |
| 0xC026251C | IOPMVideoOutput::COPPCompatibleGetInformation、IOPMVideoOutput::GetInformation 或 IOPMVideoOutput::Configure 方法失敗。當呼叫者嘗試使用 COPP 特定命令，而視訊輸出僅含有 OPM 語意時，就會傳回此錯誤。 |
Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use a COPP specific command while the video output has OPM semantics only. |
| 0xC026251D | 如果傳遞的序號並不是所預期的序號，或是傳遞的 OMAC 值不正確，IOPMVideoOutput::GetInformation 及 IOPMVideoOutput::COPPCompatibleGetInformation 方法會傳回此錯誤。 |
The IOPMVideoOutput::GetInformation and IOPMVideoOutput::COPPCompatibleGetInformation methods return this error if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid. |
| 0xC026251E | 因為顯示驅動程式內部發生意外的錯誤，所以方法失敗。 |
The method failed because an unexpected error occurred inside of a display driver. |
| 0xC026251F | IOPMVideoOutput::COPPCompatibleGetInformation、IOPMVideoOutput::GetInformation 或 IOPMVideoOutput::Configure 方法失敗。當呼叫者嘗試使用 COPP 特定命令，而視訊輸出僅含有 COPP 語意時，就會傳回此錯誤。 |
Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use an OPM specific command while the video output has COPP semantics only. |
| 0xC0262520 | 因為顯示驅動程式不支援 OPM_GET_ACP_AND_CGMSA_SIGNALING 及 OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs，所以 IOPMVideoOutput::COPPCompatibleGetInformation 或 IOPMVideoOutput::Configure 方法失敗。 |
The IOPMVideoOutput::COPPCompatibleGetInformation or IOPMVideoOutput::Configure method failed because the display driver does not support the OPM_GET_ACP_AND_CGMSA_SIGNALING and OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs. |
| 0xC0262521 | 如果傳遞的序號並不是所預期的序號，或是傳遞的 OMAC 值不正確，IOPMVideoOutput::Configure 函式會傳回此錯誤碼。 |
The IOPMVideoOutput::Configure function returns this error code if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid. |
| 0xC0262580 | 連接到指定視訊輸出的監視器沒有 I2C 匯流排。 |
The monitor connected to the specified video output does not have an I2C bus. |
| 0xC0262581 | I2C 匯流排上沒有任何裝置具有指定的位址。 |
No device on the I2C bus has the specified address. |
| 0xC0262582 | 傳輸資料給 I2C 匯流排上的裝置時，發生錯誤。 |
An error occurred while transmitting data to the device on the I2C bus. |
| 0xC0262583 | 從 I2C 匯流排上的裝置接收資料時，發生錯誤。 |
An error occurred while receiving data from the device on the I2C bus. |
| 0xC0262584 | 監視器不支援指定的 VCP 程式碼。 |
The monitor does not support the specified VCP code. |
| 0xC0262585 | 從監視器接收到的資料無效。 |
The data received from the monitor is invalid. |
| 0xC0262586 | 函數失敗，因為當作業系統使用 DDC/CI Get Timing Report Timing Message 命令從監視器取得計時報表時，監視器傳回不正確的 Timing Status 位元組。 |
The function failed because a monitor returned an invalid Timing Status byte when the operating system used the DDC/CI Get Timing Report & Timing Message command to get a timing report from a monitor. |
| 0xC0262587 | 監視器傳回 DDC/CI 功能字串，它不符合 ACCESS.bus 3.0、DDC/CI 1.1 或 MCCS 2 修訂 1 規格。 |
The monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification. |
| 0xC0262589 | 因為 DDC/CI 訊息的命令欄位包含不正確的值，操作失敗。 |
An operation failed because a DDC/CI message had an invalid value in its command field. |
| 0xC026258A | 發生此錯誤的原因是 DDC/CI 訊息的長度欄位包含不正確的值。 |
An error occurred because the field length of a DDC/CI message contained an invalid value. |
| 0xC026258B | 發生此錯誤的原因是 DDC/CI 訊息總和檢查碼欄位中的值與訊息的計算總和檢查碼值不符。此錯誤可能表示資料從監視器傳送到電腦時損壞。 |
An error occurred because the checksum field in a DDC/CI message did not match the message's computed checksum value. This error implies that the data was corrupted while it was being transmitted from a monitor to a computer. |
| 0xC026258C | 因為傳遞給函數的監視器控制代碼不正確，所以此函數失敗。 |
This function failed because an invalid monitor handle was passed to it. |
| 0xC026258D | 作業系統已非同步摧毀符合這個控制代碼的監視器，因為作業系統的狀態已變更。這個錯誤的發生原因，通常是與這個控制代碼關聯的監視器 PDO 已移除、與這個控制代碼關聯的監視器 PDO 已停止，或顯示模式已經變更。當視窗傳送 WM_DISPLAYCHANGE 視窗訊息到應用程式時，就會改變顯示模式。 |
The operating system asynchronously destroyed the monitor which corresponds to this handle because the operating system's state changed. This error typically occurs because the monitor PDO associated with this handle was removed, the monitor PDO associated with this handle was stopped, or a display mode change occurred. A display mode change occurs when windows sends a WM_DISPLAYCHANGE windows message to applications. |
| 0xC02625D8 | 連續 VCP 程式碼目前的值大於其最大值。這個錯誤碼表示監視器傳回不正確的值。 |
A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value. |
| 0xC02625DF | SetMonitorColorTemperature() 的呼叫者已傳遞色溫給此函數，但目前的監視器並不支援。此錯誤可能表示監視器違反 MCCS 2.0 或 MCCS 2.0 修訂 1 規格。 |
SetMonitorColorTemperature()'s caller passed a color temperature to it which the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification. |
| 0xC02625E0 | 只有當程式是在本機主控台工作階段使用時，才能使用此功能。若程式是在遠端桌面工作階段或終端機伺服器工作階段中執行，無法使用此功能。 |
This function can only be used if a program is running in the local console session. It cannot be used if the program is running on a remote desktop session or on a terminal server session. |
| 0xC02625E1 | 這個函數找不到符合指定 GDI 顯示裝置名稱的實際 GDI 顯示裝置。 |
This function cannot find an actual GDI display device which corresponds to the specified GDI display device name. |
| 0xC02625E2 | 因為指定的 GDI 顯示器裝置未連結到 Windows 桌面，所以函數失敗。 |
The function failed because the specified GDI display device was not attached to the Windows desktop. |
| 0xC02625E3 | 因為 GDI 鏡像顯示器裝置沒有關聯任何實體的監視器，所以這個函數不支援 GDI 鏡像顯示器裝置。 |
This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them. |
| 0xC02625E4 | 因為有無效的指標參數傳送給它，所以函數失敗。如果指標參數是 NULL、指向不正確的位址、指向核心模式位址，或者未正確對齊，則為無效。 |
The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, points to an invalid address, points to a kernel mode address, or is not correctly aligned. |
| 0xC02625E5 | 因為指定的 GDI 裝置沒有任相關聯的監視器，所以函式失敗。 |
The function failed because the specified GDI device did not have any monitors associated with it. |
| 0xC02625E6 | 傳遞到函數的陣列無法保存函數應該複製到陣列中的所有資料。 |
An array passed to the function cannot hold all of the data that the function must copy into the array. |
| 0xC034100F | 基於本機原則設定，不允許卸載 TCP 連線。 |
The TCP connection is not offloadable because of a local policy setting. |
| 0xC0341012 | Chimney 卸載目標不可卸載 TCP 連線。 |
The TCP connection is not offloadable by the Chimney Offload target. |
| 0xC0341013 | IP 路徑物件未處於可卸載狀態。 |
The IP Path object is not in an offloadable state. |
| 0xC0350002 | Hypervisor 不支援操作，因為不支援指定的 Hypercall 程式碼。 |
The hypervisor does not support the operation because the specified hypercall code is not supported. |
| 0xC0350003 | Hypervisor 不支援操作，因為不支援 Hypercall 輸入登錄的編碼方式。 |
The hypervisor does not support the operation because the encoding for the hypercall input register is not supported. |
| 0xC0350004 | Hypervisor 無法執行作業，因為參數的對齊無效。 |
The hypervisor could not perform the operation because a parameter has an invalid alignment. |
| 0xC0350005 | Hypervisor 無法執行作業，因為指定的參數無效。 |
The hypervisor could not perform the operation because an invalid parameter was specified. |
| 0xC0350006 | 指定物件的存取被拒。 |
Access to the specified object was denied. |
| 0xC0350007 | Hypervisor 無法執行操作，因為該分割正在進入無效狀態或目前處於無效狀態。 |
The hypervisor could not perform the operation because the partition is entering or in an invalid state. |
| 0xC0350008 | 在目前的狀態不允許該操作。 |
The operation is not allowed in the current state. |
| 0xC0350009 | Hypervisor 無法辨識指定的分割屬性。 |
The hypervisor does not recognize the specified partition property. |
| 0xC035000A | 分割屬性的指定值超出範圍或違反不變值。 |
The specified value of a partition property is out of range or violates an invariant. |
| 0xC035000B | Hypervisor 集區中的記憶體不足，無法完成操作。 |
There is not enough memory in the hypervisor pool to complete the operation. |
| 0xC035000C | 分割階層已超過最大的分割深度。 |
The maximum partition depth has been exceeded for the partition hierarchy. |
| 0xC035000D | 具有指定分割識別碼的分割不存在。 |
A partition with the specified partition Id does not exist. |
| 0xC035000E | Hypervisor 無法執行操作，因為指定的 VP 索引不正確。 |
The hypervisor could not perform the operation because the specified VP index is invalid. |
| 0xC0350011 | Hypervisor 無法執行操作，因為指定的連接埠識別碼不正確。 |
The hypervisor could not perform the operation because the specified port identifier is invalid. |
| 0xC0350012 | Hypervisor 無法執行操作，因為指定的連線識別碼不正確。 |
The hypervisor could not perform the operation because the specified connection identifier is invalid. |
| 0xC0350013 | 沒有提供足夠的緩衝區以傳送訊息。 |
Not enough buffers were supplied to send a message. |
| 0xC0350014 | 尚未認可之前的虛擬插斷。 |
The previous virtual interrupt has not been acknowledged. |
| 0xC0350015 | 虛擬處理器不是處於指定作業的正確狀態。 |
A virtual processor is not in the correct state for the indicated operation. |
| 0xC0350016 | 已經認可之前的虛擬插斷。 |
The previous virtual interrupt has already been acknowledged. |
| 0xC0350017 | 所指定分割的狀態不是可執行儲存或還原的有效狀態。 |
The indicated partition is not in a valid state for saving or restoring. |
| 0xC0350018 | Hypervisor 無法完成操作，因為已停用綜合插斷控制器 (SynIC) 的必要功能。 |
The hypervisor could not complete the operation because a required feature of the synthetic interrupt controller (SynIC) was disabled. |
| 0xC0350019 | Hypervisor 無法執行操作，因為物件或值已經在使用中，或是用於不允許完成操作的目的。 |
The hypervisor could not perform the operation because the object or value was either already in use or being used for a purpose that would not permit completing the operation. |
| 0xC035001A | 近接網域資訊不正確。 |
The proximity domain information is invalid. |
| 0xC035001B | 嘗試抓取偵錯資料失敗，因為沒有可用的資料。 |
An attempt to retrieve debugging data failed because none was available. |
| 0xC035001C | 用於偵錯的實體連線從上次操作之後尚未記錄任何接收活動。 |
The physical connection being used for debuggging has not recorded any receive activity since the last operation. |
| 0xC035001D | 資源不足，無法完成操作。 |
There are not enough resources to complete the operation. |
| 0xC035001E | 使用者無法使用 Hypervisor 功能。 |
A hypervisor feature is not available to the user. |
| 0xC0350033 | 指定的緩衝區太小，無法容納要求的資料。 |
The specified buffer was too small to contain all of the requested data. |
| 0xC0350038 | 使用中的網域數目已達平台 I/O 重新對應硬體支援的網域數目上限。沒有其他網域可用，因此無法將此裝置指派到此分割。 |
The maximum number of domains supported by the platform I/O remapping hardware is currently in use. No domains are available to assign this device to this partition. |
| 0xC035003C | 驗證處理器的 CPUID 資料失敗。 |
Validation of CPUID data of the processor failed. |
| 0xC035003D | 驗證處理器的 XSAVE CPUID 資料失敗。 |
Validation of XSAVE CPUID data of the processor failed. |
| 0xC035003E | 處理器未在逾時期間內回應。 |
Processor did not respond within the timeout period. |
| 0xC035003F | BIOS 中已啟用 SMX。 |
SMX has been enabled in the BIOS. |
| 0xC0350041 | Hypervisor 無法執行操作，因為指定的 LP 索引無效。 |
The hypervisor could not perform the operation because the specified LP index is invalid. |
| 0xC0350050 | 提供的登錄值無效。 |
The supplied register value is invalid. |
| 0xC0350051 | 提供的虛擬信任層級不是處於正確的狀態，無法執行要求的作業。 |
The supplied virtual trust level is not in the correct state to perform the requested operation. |
| 0xC0350055 | BIOS 中沒有或未啟用不執行功能 (NX)。 |
No execute feature (NX) is not present or not enabled in the BIOS. |
| 0xC0350057 | 提供的裝置識別碼無效。 |
The supplied device ID is invalid. |
| 0xC0350058 | 目前的裝置狀態不允許此操作。 |
The operation is not allowed in the current device state. |
| 0xC0350060 | 提供的頁面要求指定客體沒有權限執行的記憶體存取。 |
The supplied page request specifies a memory access that the guest does not have permissions to perform. |
| 0xC035006F | 具有所指定 CPU 群組識別碼 的 CPU 群組不存在。 |
A CPU group with the specified CPU group Id does not exist. |
| 0xC0350070 | Hypervisor 無法執行該作業，因為該 CPU 群組正在進入無效狀態或目前處於無效狀態。 |
The hypervisor could not perform the operation because the CPU group is entering or in an invalid state. |
| 0xC0350071 | 要求的作業失敗。 |
The requested operation failed. |
| 0xC0350072 | Hypervisor 無法執行該作業，因為在巢狀虛擬化處於作用中狀態時不允許該作業。 |
The hypervisor could not perform the operation because it is not allowed with nested virtualization active. |
| 0xC0351000 | 這個系統上沒有 Hypervisor。 |
No hypervisor is present on this system. |
| 0xC0370001 | 已經登錄虛擬化基礎結構驅動程式的處理常式。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The handler for the virtualization infrastructure driver is already registered. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370002 | 虛擬化基礎結構驅動程式的處理常式登錄數目超過最大值。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The number of registered handlers for the virtualization infrastructure driver exceeded the maximum. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370003 | 虛擬化基礎結構驅動程式的訊息佇列已滿，無法接受新訊息。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370004 | 虛擬化基礎結構驅動程式的處理常式不存在，無法處理訊息。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
No handler exists to handle the message for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370005 | 虛擬化基礎結構驅動程式的分割名稱或訊息佇列名稱不正確。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The name of the partition or message queue for the virtualization infrastructure driver is invalid. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370006 | 虛擬化基礎結構驅動程式的分割名稱超過最大值。 |
The partition name of the virtualization infrastructure driver exceeds the maximum. |
| 0xC0370007 | 虛擬化基礎結構驅動程式的訊息佇列名稱超過最大值。 |
The message queue name of the virtualization infrastructure driver exceeds the maximum. |
| 0xC0370008 | 無法建立虛擬化基礎結構驅動程式的分割，因為已經有另一個相同名稱的分割。 |
Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists. |
| 0xC0370009 | 虛擬化基礎結構驅動程式發生錯誤。要求的分割不存在。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC037000A | 虛擬化基礎結構驅動程式發生錯誤。找不到要求的分割。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC037000B | 虛擬化基礎結構驅動程式已經有相同名稱的訊息佇列。 |
A message queue with the same name already exists for the virtualization infrastructure driver. |
| 0xC037000C | 虛擬化基礎結構驅動程式的記憶體區塊分頁無法對應，因為已經達到分頁對應限制。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The memory block page for the virtualization infrastructure driver cannot be mapped because the page map limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC037000D | 虛擬化基礎結構驅動程式的記憶體區塊仍在使用中，無法摧毀。 |
The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed. |
| 0xC037000E | 無法解除鎖定客體作業系統記憶體位址的分頁陣列，因為不符合之前的鎖定要求。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
Cannot unlock the page array for the guest operating system memory address because it does not match a previous lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC037000F | 非統一記憶體存取 (NUMA) 節點設定不符合系統 NUMA 拓撲。若要啟動虛擬機器，您需要修改 NUMA 設定。 |
The non-uniform memory access (NUMA) node settings do not match the system NUMA topology. In order to start the virtual machine, you will need to modify the NUMA configuration. |
| 0xC0370010 | 非統一記憶體存取 (NUMA) 節點索引不符合系統 NUMA 拓撲中有效的索引。 |
The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology. |
| 0xC0370011 | 虛擬化基礎結構驅動程式的記憶體區塊已經和訊息佇列關聯。 |
The memory block for the virtualization infrastructure driver is already associated with a message queue. |
| 0xC0370012 | 控制代碼不是虛擬化基礎結構驅動程式有效的記憶體區塊控制代碼。 |
The handle is not a valid memory block handle for the virtualization infrastructure driver. |
| 0xC0370013 | 要求超過虛擬化基礎結構驅動程式的記憶體區塊分頁限制。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The request exceeded the memory block page limit for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370014 | 控制代碼不是虛擬化基礎結構驅動程式有效的訊息佇列控制代碼。 |
The handle is not a valid message queue handle for the virtualization infrastructure driver. |
| 0xC0370015 | 控制代碼不是虛擬化基礎結構驅動程式有效的分頁範圍控制代碼。 |
The handle is not a valid page range handle for the virtualization infrastructure driver. |
| 0xC0370016 | 無法安裝用戶端通知，因為沒有虛擬化基礎結構驅動程式的訊息佇列與記憶體區塊關聯。 |
Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block. |
| 0xC0370017 | 鎖定或對應記憶體區塊分頁的要求失敗，因為已達到虛擬化基礎結構驅動程式記憶體區塊限制。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The request to lock or map a memory block page failed because the virtualization infrastructure driver memory block limit has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370018 | 控制代碼不是虛擬化基礎結構驅動程式有效的父分割對應控制代碼。 |
The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver. |
| 0xC0370019 | 無法在記憶體區塊分頁建立通知，因為正在使用中。 |
Notifications cannot be created on the memory block because it is use. |
| 0xC037001A | 已經關閉虛擬化基礎結構驅動程式的訊息佇列。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC037001B | 無法將虛擬處理器新增到分割，因為已達到最大值。 |
Cannot add a virtual processor to the partition because the maximum has been reached. |
| 0xC037001C | 無法立即停止虛擬處理器，因為有擱置的攔截。 |
Cannot stop the virtual processor immediately because of a pending intercept. |
| 0xC037001D | 虛擬處理器的狀態不正確。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC037001E | 虛擬化基礎結構驅動程式的核心模式用戶端已達到最大數目。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The maximum number of kernel mode clients for the virtualization infrastructure driver has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC037001F | 已經初始化虛擬化基礎結構驅動程式的核心模式介面。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
This kernel mode interface for the virtualization infrastructure driver has already been initialized. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370020 | 無法設定或重設虛擬化基礎結構驅動程式的記憶體區塊屬性超過一次。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
Cannot set or reset the memory block property more than once for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370021 | 此分頁範圍的記憶體對應 I/O 已經不存在。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The memory mapped I/O for this page range no longer exists. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370022 | 鎖定或解除鎖定要求使用的客體作業系統記憶體位址不正確。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The lock or unlock request uses an invalid guest operating system memory address. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370023 | 無法摧毀或重複使用虛擬化基礎結構驅動程式的保留分頁設定。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
Cannot destroy or reuse the reserve page set for the virtualization infrastructure driver because it is in use. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370024 | 虛擬化基礎結構驅動程式的保留分頁設定太小，無法在鎖定要求中使用。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
The reserve page set for the virtualization infrastructure driver is too small to use in the lock request. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370025 | 無法鎖定或對應虛擬化基礎結構驅動程式的記憶體區塊分頁，因為它已經使用保留分頁設定頁鎖定。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
Cannot lock or map the memory block page for the virtualization infrastructure driver because it has already been locked using a reserve page set page. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370026 | 無法建立虛擬化基礎結構驅動程式的記憶體區塊，因為要求的分頁數目超過限制。重新啟動虛擬機器可能可以修復問題。如果問題仍然存在，請嘗試重新啟動實體電腦。 |
Cannot create the memory block for the virtualization infrastructure driver because the requested number of pages exceeded the limit. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer. |
| 0xC0370027 | 無法還原此虛擬機器，因為無法讀取儲存的狀態資料。請刪除儲存的狀態資料然後嘗試啟動虛擬機器。 |
Cannot restore this virtual machine because the saved state data cannot be read. Delete the saved state data and then try to start the virtual machine. |
| 0xC0370028 | 無法還原此虛擬機器，因為無法辨識從儲存的狀態資料讀取的項目。請刪除儲存的狀態資料然後嘗試啟動虛擬機器。 |
Cannot restore this virtual machine because an item read from the saved state data is not recognized. Delete the saved state data and then try to start the virtual machine. |
| 0xC0370029 | 無法將此虛擬機器還原為儲存的狀態，因為 Hypervisor 不相容。請刪除儲存的狀態資料然後嘗試啟動虛擬機器。 |
Cannot restore this virtual machine to the saved state because of hypervisor incompatibility. Delete the saved state data and then try to start the virtual machine. |
| 0xC037002A | 指定的 VTL 沒有存取資源的權限。 |
The specified VTL does not have the permission to access the resource. |
| 0xC0370100 | 運算系統在啟動時意外終止。 |
The compute system unexpectedly terminated while starting. |
| 0xC0370101 | 容器的作業系統與主機的作業系統不相符。 |
The operating system of the container does not match the operating system of the host. |
| 0xC0370102 | 虛擬機器無法啟動，因為未安裝 Hyper-V。 |
A Virtual Machine could not be started because Hyper-V is not installed. |
| 0xC0370103 | 啟動非同步作業的呼叫成功，且作業已在背景執行。 |
The call to start an asynchronous operation succeeded and the operation is performed in the background. |
| 0xC0370104 | 已超過支援的通知回呼數目。 |
The supported number of notification callbacks has been exceeded. |
| 0xC0370105 | 要求的運算系統作業在目前的狀態中無效。 |
The requested compute system operation is not valid in the current state. |
| 0xC0370106 | 運算系統意外地結束。 |
The compute system exited unexpectedly. |
| 0xC0370107 | 運算系統已被強制終止。 |
The compute system was forcefully terminated. |
| 0xC0370108 | 無法建立與裝載「容器」之「虛擬機器」的連線。 |
A connection could not be established with the Virtual Machine hosting the Container. |
| 0xC0370109 | 作業逾時，因為未從裝載「容器」的「虛擬機器」收到回應。 |
The operation timed out because a response was not received from the Virtual Machine hosting the Container. |
| 0xC037010A | 已關閉裝載容器之虛擬機器的連線。 |
The connection with the Virtual Machine hosting the container was closed. |
| 0xC037010B | Hyper-V 運算服務已接收未知的內部訊息。 |
An unknown internal message was received by the Hyper-V Compute Service. |
| 0xC037010C | 不支援 Hyper-V 主機與客體運算服務之間的通訊協定版本。 |
The communication protocol version between the Hyper-V Host and Guest Compute Services is not supported. |
| 0xC037010D | 該 JSON 文件無效。 |
The JSON document is invalid. |
| 0xC037010E | 具有指定識別碼的運算系統不存在。 |
A Compute System with the specified identifier does not exist. |
| 0xC037010F | 具有指定識別碼的運算系統已存在。 |
A Compute System with the specified identifier already exists. |
| 0xC0370110 | 具有所指定識別碼的「運算系統」確實已停止。 |
The Compute System with the specified identifier did already stop. |
| 0xC0370111 | Hyper-V 主機與客體運算服務之間發生通訊協定錯誤。 |
A communication protocol error has occurred between the Hyper-V Host and Guest Compute Service. |
| 0xC0370200 | 找不到具有指定名稱的虛擬交換器。 |
A virtual switch with the given name was not found. |
| 0xC0380001 | 設定資料庫已滿。 |
The configuration database is full. |
| 0xC0380002 | 磁碟上的設定資料已損毀。 |
The configuration data on the disk is corrupted. |
| 0xC0380003 | 磁碟上的設定與記憶體中的設定不同步。 |
The configuration on the disk is not insync with the in-memory configuration. |
| 0xC0380004 | 大部分磁碟無法更新為新的設定。 |
A majority of disks failed to be updated with the new configuration. |
| 0xC0380005 | 該磁碟包含非簡單磁碟區。 |
The disk contains non-simple volumes. |
| 0xC0380006 | 移轉清單中多次指定同一個磁碟。 |
The same disk was specified more than once in the migration list. |
| 0xC0380007 | 磁碟已經是動態磁碟。 |
The disk is already dynamic. |
| 0xC0380008 | 指定的磁碟識別碼無效。指定磁碟識別碼的磁碟並不存在。 |
The specified disk id is invalid. There are no disks with the specified disk id. |
| 0xC0380009 | 指定的磁碟無效。無法在無效的磁碟上完成操作。 |
The specified disk is an invalid disk. Operation cannot complete on an invalid disk. |
| 0xC038000A | 無法移除指定的磁碟，因為它是最後一個磁碟。 |
The specified disk(s) cannot be removed since it is the last remaining voter. |
| 0xC038000B | 指定的磁碟具有無效的磁碟配置。 |
The specified disk has an invalid disk layout. |
| 0xC038000C | 磁碟配置在基本磁碟分割後面包含非基本磁碟分割。這是無效的磁碟配置。 |
The disk layout contains non-basic partitions which appear after basic paritions. This is an invalid disk layout. |
| 0xC038000D | 磁碟配置包含尚未對齊磁柱的磁碟分割。 |
The disk layout contains partitions which are not cylinder aligned. |
| 0xC038000E | 磁碟配置包含小於最小大小的磁碟分割。 |
The disk layout contains partitions which are samller than the minimum size. |
| 0xC038000F | 磁碟配置在邏輯磁碟機之間包含主要磁碟分割。這是無效的磁碟配置。 |
The disk layout contains primary partitions in between logical drives. This is an invalid disk layout. |
| 0xC0380010 | 磁碟配置的支援磁碟分割數目超過上限。 |
The disk layout contains more than the maximum number of supported partitions. |
| 0xC0380011 | 指定的磁碟已遺失。無法對遺失的磁碟完成操作。 |
The specified disk is missing. The operation cannot complete on a missing disk. |
| 0xC0380012 | 指定的磁碟不是空的。 |
The specified disk is not empty. |
| 0xC0380013 | 可用空間不足，無法執行此操作。 |
There is not enough usable space for this operation. |
| 0xC0380014 | 強制重新引導損壞磁區失敗。 |
The force revectoring of bad sectors failed. |
| 0xC0380015 | 指定的磁碟具有無效的磁區大小。 |
The specified disk has an invalid sector size. |
| 0xC0380016 | 指定的磁碟組包含位於磁碟組外部的磁碟區。 |
The specified disk set contains volumes which exist on disks outside of the set. |
| 0xC0380017 | 磁碟區配置中的磁碟可延伸到多個網狀磁碟區成員。 |
A disk in the volume layout provides extents to more than one member of a plex. |
| 0xC0380018 | 磁碟區配置中的磁碟可延伸到多個網狀磁碟區。 |
A disk in the volume layout provides extents to more than one plex. |
| 0xC0380019 | 這個系統不支援動態磁碟。 |
Dynamic disks are not supported on this system. |
| 0xC038001A | 指定的延伸已由其他磁碟區使用中。 |
The specified extent is already used by other volumes. |
| 0xC038001B | 已保留指定的磁碟區，而該磁碟區只能延伸為連續延伸。指定磁碟區中，進行延伸磁碟區的指定延伸並不連續。 |
The specified volume is retained and can only be extended into a contiguous extent. The specified extent to grow the volume is not contiguous with the specified volume. |
| 0xC038001C | 指定的磁碟區延伸不在磁碟的公用區域內。 |
The specified volume extent is not within the public region of the disk. |
| 0xC038001D | 指定磁碟區延伸的磁區沒有對齊。 |
The specifed volume extent is not sector aligned. |
| 0xC038001E | 指定的磁碟分割與 EBR (MBR 磁碟上延伸磁碟分割的第一個磁軌) 重疊。 |
The specified parition overlaps an EBR (the first track of an extended partition on a MBR disks). |
| 0xC038001F | 無法使用指定的延伸長度來建立具有指定長度的磁碟區。 |
The specified extent lengths cannot be used to construct a volume with specified length. |
| 0xC0380020 | 此系統不支援容錯磁碟區。 |
The system does not support fault tolerant volumes. |
| 0xC0380021 | 指定的間隔長度無效。 |
The specified interleave length is invalid. |
| 0xC0380022 | 已註冊的使用者數目已達上限。 |
There is already a maximum number of registered users. |
| 0xC0380023 | 指定的成員已經與其他使用中的成員同步。不需要重新產生。 |
The specified member is already in-sync with the other active members. It does not need to be regenerated. |
| 0xC0380024 | 多次指定同一個成員索引。 |
The same member index was specified more than once. |
| 0xC0380025 | 指定的成員索引大於或等於網狀磁碟區中的成員數目。 |
The specified member index is greater or equal than the number of members in the volume plex. |
| 0xC0380026 | 指定的成員已遺失。無法重新產生。 |
The specified member is missing. It cannot be regenerated. |
| 0xC0380027 | 指定的成員沒有中斷連結。無法取代沒有中斷連結的成員。 |
The specified member is not detached. Cannot replace a member which is not detached. |
| 0xC0380028 | 指定的成員已經重新產生。 |
The specified member is already regenerating. |
| 0xC0380029 | 屬於該封裝的磁碟全部失敗。 |
All disks belonging to the pack failed. |
| 0xC038002A | 目前沒有需要通知的註冊使用者。除非有已註冊的使用者，否則工作號碼並不相關。 |
There are currently no registered users for notifications. The task number is irrelevant unless there are registered users. |
| 0xC038002B | 指定要通知的使用者不存在。無法通知尚未註冊的使用者。 |
The specified notification user does not exist. Failed to unregister user for notifications. |
| 0xC038002C | 已經重設通知。目前使用者的通知無效。請取消註冊再重新註冊以取得通知。 |
The notifications have been reset. Notifications for the current user are invalid. Unregister and re-register for notifications. |
| 0xC038002D | 指定的成員數目無效。 |
The specified number of members is invalid. |
| 0xC038002E | 指定的網狀磁碟區數目無效。 |
The specified number of plexes is invalid. |
| 0xC038002F | 指定的來源與目標封裝相同。 |
The specified source and target packs are identical. |
| 0xC0380030 | 指定的封裝識別碼無效。指定封裝識別碼的封裝並不存在。 |
The specified pack id is invalid. There are no packs with the specified pack id. |
| 0xC0380031 | 指定的封裝無效。無法對無效的封裝完成操作。 |
The specified pack is the invalid pack. The operation cannot complete with the invalid pack. |
| 0xC0380032 | 指定的封裝名稱無效。 |
The specified pack name is invalid. |
| 0xC0380033 | 指定的封裝已離線。 |
The specified pack is offline. |
| 0xC0380034 | 指定的封裝已有狀況良好磁碟的仲裁。 |
The specified pack already has a quorum of healthy disks. |
| 0xC0380035 | 該封裝沒有狀況良好磁碟的仲裁。 |
The pack does not have a quorum of healthy disks. |
| 0xC0380036 | 指定的磁碟具有不支援的磁碟分割樣式。只支援 MBR 與 GPT 磁碟分割樣式。 |
The specified disk has an unsupported partition style. Only MBR and GPT partition styles are supported. |
| 0xC0380037 | 無法更新磁碟的磁碟分割配置。 |
Failed to update the disk's partition layout. |
| 0xC0380038 | 指定的網狀磁碟區已經與其他使用中的網狀磁碟區同步。不需要重新產生。 |
The specified plex is already in-sync with the other active plexes. It does not need to be regenerated. |
| 0xC0380039 | 多次指定同一個網狀磁碟區索引。 |
The same plex index was specified more than once. |
| 0xC038003A | 指定的網狀磁碟區索引大於或等於磁碟區中的網狀磁碟區數目。 |
The specified plex index is greater or equal than the number of plexes in the volume. |
| 0xC038003B | 指定的網狀磁碟區是磁碟區中最後一個使用中的網狀磁碟區。不可以移除此網狀磁碟區，否則將會使磁碟區離線。 |
The specified plex is the last active plex in the volume. The plex cannot be removed or else the volume will go offline. |
| 0xC038003C | 指定的網狀磁碟區已遺失。 |
The specified plex is missing. |
| 0xC038003D | 目前正在重新產生指定的網狀磁碟區。 |
The specified plex is currently regenerating. |
| 0xC038003E | 指定的網狀磁碟區類型無效。 |
The specified plex type is invalid. |
| 0xC038003F | 只有在 RAID-5 網狀磁碟區上才支援此操作。 |
The operation is only supported on RAID-5 plexes. |
| 0xC0380040 | 只有在簡易網狀磁碟區上才支援此操作。 |
The operation is only supported on simple plexes. |
| 0xC0380041 | 並未正確設定 VM_VOLUME_LAYOUT 輸入結構中的 [大小] 欄位。 |
The Size fields in the VM_VOLUME_LAYOUT input structure are incorrectly set. |
| 0xC0380042 | 已經有一個擱置中的通知要求。請等候現有的要求傳回後，再要求發送其他通知。 |
There is already a pending request for notifications. Wait for the existing request to return before requesting for more notifications. |
| 0xC0380043 | 目前正在進行一項交易。 |
There is currently a transaction in process. |
| 0xC0380044 | 磁碟區管理員外部發生意外的配置變更。 |
An unexpected layout change occurred outside of the volume manager. |
| 0xC0380045 | 指定的磁碟區包含遺失的磁碟。 |
The specified volume contains a missing disk. |
| 0xC0380046 | 指定的磁碟區識別碼無效。指定磁碟區識別碼的磁碟區並不存在。 |
The specified volume id is invalid. There are no volumes with the specified volume id. |
| 0xC0380047 | 指定的磁碟區長度無效。 |
The specified volume length is invalid. |
| 0xC0380048 | 指定的磁碟區大小不是磁區大小的倍數。 |
The specified size for the volume is not a multiple of the sector size. |
| 0xC0380049 | 只有在鏡像磁碟區上才支援此操作。 |
The operation is only supported on mirrored volumes. |
| 0xC038004A | 指定的磁碟區沒有保留的磁碟分割。 |
The specified volume does not have a retain partition. |
| 0xC038004B | 指定的磁碟區已離線。 |
The specified volume is offline. |
| 0xC038004C | 指定的磁碟區已有保留的磁碟分割。 |
The specified volume already has a retain partition. |
| 0xC038004D | 指定的延伸數目無效。 |
The specified number of extents is invalid. |
| 0xC038004E | 磁碟區內的所有磁碟必須具有相同的磁區大小。 |
All disks participating to the volume must have the same sector size. |
| 0xC038004F | 開機磁碟發生失敗。 |
The boot disk experienced failures. |
| 0xC0380050 | 封裝的設定已離線。 |
The configuration of the pack is offline. |
| 0xC0380051 | 封裝的設定已上線。 |
The configuration of the pack is online. |
| 0xC0380052 | 指定的封裝不是主要封裝。 |
The specified pack is not the primary pack. |
| 0xC0380053 | 所有磁碟都無法更新為新的記錄檔內容。 |
All disks failed to be updated with the new content of the log. |
| 0xC0380054 | 在網狀磁碟區中指定的磁碟數目無效。 |
The specified number of disks in a plex is invalid. |
| 0xC0380055 | 在網狀磁碟區成員中指定的磁碟數目無效。 |
The specified number of disks in a plex member is invalid. |
| 0xC0380056 | 鏡像磁碟區不支援此操作。 |
The operation is not supported on mirrored volumes. |
| 0xC0380057 | 只有在簡易與合併網狀磁碟區上才支援此操作。 |
The operation is only supported on simple and spanned plexes. |
| 0xC0380058 | 封裝沒有正確的記錄檔。 |
The pack has no valid log copies. |
| 0xC0380059 | 主要封裝已經存在。 |
A primary pack is already present. |
| 0xC038005A | 指定的磁碟數目無效。 |
The specified number of disks is invalid. |
| 0xC038005B | 系統不支援鏡像磁碟區。 |
The system does not support mirrored volumes. |
| 0xC038005C | 系統不支援 RAID-5 磁碟區。 |
The system does not support RAID-5 volumes. |
| 0xC0390002 | 列舉的項目已超過允許的閾值。 |
Entries enumerated have exceeded the allowed threshold. |
| 0xC03A0001 | 虛擬硬碟已損毀。虛擬硬碟的磁碟機頁尾遺失。 |
The virtual hard disk is corrupted. The virtual hard disk drive footer is missing. |
| 0xC03A0002 | 虛擬硬碟已損毀。虛擬硬碟的磁碟機頁尾總和檢查碼與磁碟總和檢查碼不相符。 |
The virtual hard disk is corrupted. The virtual hard disk drive footer checksum does not match the on-disk checksum. |
| 0xC03A0003 | 虛擬硬碟已損毀。虛擬硬碟中的虛擬硬碟磁碟機頁尾已損毀。 |
The virtual hard disk is corrupted. The virtual hard disk drive footer in the virtual hard disk is corrupted. |
| 0xC03A0004 | 系統無法辨識此虛擬硬碟的檔案格式。 |
The system does not recognize the file format of this virtual hard disk. |
| 0xC03A0005 | 該版本不支援此版本的檔案格式。 |
The version does not support this version of the file format. |
| 0xC03A0006 | 虛擬硬碟已損毀。疏鬆標頭的總和檢查碼與磁碟上的總和檢查碼不相符。 |
The virtual hard disk is corrupted. The sparse header checksum does not match the on-disk checksum. |
| 0xC03A0007 | 系統不支援這個版本的虛擬硬碟。不支援這個版本的疏鬆標頭。 |
The system does not support this version of the virtual hard disk.This version of the sparse header is not supported. |
| 0xC03A0008 | 虛擬硬碟已損毀。虛擬硬碟中的疏鬆標頭已損毀。 |
The virtual hard disk is corrupted. The sparse header in the virtual hard disk is corrupt. |
| 0xC03A0009 | 寫入虛擬硬碟失敗，因為系統無法在虛擬硬碟中配置新的區塊。 |
Failed to write to the virtual hard disk failed because the system failed to allocate a new block in the virtual hard disk. |
| 0xC03A000A | 虛擬硬碟已損毀。虛擬硬碟中的區塊配置表已損毀。 |
The virtual hard disk is corrupted. The block allocation table in the virtual hard disk is corrupt. |
| 0xC03A000B | 系統不支援這個版本的虛擬硬碟。區塊大小無效。 |
The system does not support this version of the virtual hard disk. The block size is invalid. |
| 0xC03A000C | 虛擬硬碟已損毀。區塊點陣圖與虛擬硬碟中存在的區塊資料不相符。 |
The virtual hard disk is corrupted. The block bitmap does not match with the block data present in the virtual hard disk. |
| 0xC03A000D | 虛擬硬碟的鏈結已損毀。系統找不到差異磁碟的父虛擬硬碟。 |
The chain of virtual hard disks is broken. The system cannot locate the parent virtual hard disk for the differencing disk. |
| 0xC03A000E | 虛擬硬碟的鏈結已損毀。父虛擬硬碟與差異磁碟的識別元不相符。 |
The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk. |
| 0xC03A000F | 虛擬硬碟的鏈結已損毀。父虛擬硬碟的時間戳記與差異磁碟的時間戳記不相符。 |
The chain of virtual hard disks is corrupted. The time stamp of the parent virtual hard disk does not match the time stamp of the differencing disk. |
| 0xC03A0010 | 無法讀取虛擬硬碟的中繼資料。 |
Failed to read the metadata of the virtual hard disk. |
| 0xC03A0011 | 無法寫入虛擬硬碟的中繼資料。 |
Failed to write to the metadata of the virtual hard disk. |
| 0xC03A0012 | 虛擬硬碟的大小無效。 |
The size of the virtual hard disk is not valid. |
| 0xC03A0013 | 此虛擬硬碟的檔案大小無效。 |
The file size of this virtual hard disk is not valid. |
| 0xC03A0014 | 找不到指定檔案的虛擬磁碟支援提供者。 |
A virtual disk support provider for the specified file was not found. |
| 0xC03A0015 | 指定的磁碟不是虛擬磁碟。 |
The specified disk is not a virtual disk. |
| 0xC03A0016 | 虛擬硬碟的鏈結無法存取。處理程序未獲得差異磁碟之父虛擬硬碟的存取權。 |
The chain of virtual hard disks is inaccessible. The process has not been granted access rights to the parent virtual hard disk for the differencing disk. |
| 0xC03A0017 | 虛擬硬碟的鏈結已損毀。父虛擬硬碟與差異磁碟的虛擬大小不相符。 |
The chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk. |
| 0xC03A0018 | 虛擬硬碟的鏈結已損毀。已指出差異磁碟位於自己的父系鏈結。 |
The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain. |
| 0xC03A0019 | 虛擬硬碟的鏈結無法存取。開啟虛擬磁碟的上一層鏈結時發生錯誤。 |
The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain. |
| 0xC03A001A | 因為虛擬磁碟系統的限制，所以無法完成要求的作業。虛擬硬碟檔案必須未壓縮也未加密，而且不能是疏鬆檔案。 |
The requested operation could not be completed due to a virtual disk system limitation. Virtual hard disk files must be uncompressed and unencrypted and must not be sparse. |
| 0xC03A001B | 無法在此類型的虛擬磁碟中執行要求的操作。 |
The requested operation cannot be performed on a virtual disk of this type. |
| 0xC03A001C | 無法在目前狀態的虛擬磁碟中執行要求的操作。 |
The requested operation cannot be performed on the virtual disk in its current state. |
| 0xC03A001D | 不支援虛擬磁碟所在之實體磁碟的磁區大小。 |
The sector size of the physical disk on which the virtual disk resides is not supported. |
| 0xC03A001E | 此磁碟已由其他擁有者所擁有。 |
The disk is already owned by a different owner. |
| 0xC03A001F | 磁碟必須是離線或唯讀狀態。 |
The disk must be offline or read-only. |
| 0xC03A0020 | 未針對此虛擬磁碟初始化變更追蹤。 |
Change Tracking is not initialized for this virtual disk. |
| 0xC03A0021 | 變更追蹤檔案大小已超出大小上限。 |
Size of change tracking file exceeded the maximum size limit. |
| 0xC03A0022 | VHD 檔案已因壓縮、擴充或離線更新而變更。 |
VHD file is changed due to compaction, expansion, or offline updates. |
| 0xC03A0023 | 虛擬磁碟的變更追蹤狀態無效，因此無法執行此要求。變更追蹤可能已中斷，或已處於要求的狀態。 |
Change Tracking for the virtual disk is not in a valid state to perform this request. Change tracking could be discontinued or already in the requested state. |
| 0xC03A0024 | 虛擬磁碟的變更追蹤檔案狀態無效。 |
Change Tracking file for the virtual disk is not in a valid state. |
| 0xC03A0025 | 無法完成要求的重新調整大小作業，因為該作業可能會截斷虛擬磁碟上的使用者資料。 |
The requested resize operation could not be completed because it might truncate user data residing on the virtual disk. |
| 0xC03A0026 | 無法完成要求的作業，因為無法判斷虛擬磁碟的安全大小下限。這可能是因為磁碟分割表格遺漏或損毀。 |
The requested operation could not be completed because the virtual disk's minimum safe size could not be determined.This may be due to a missing or corrupt partition table. |
| 0xC03A0027 | 無法完成要求的作業，因為虛擬磁碟的大小無法進一步安全地縮小。 |
The requested operation could not be completed because the virtual disk's size cannot be safely reduced further. |
| 0xC03A0028 | 虛擬磁碟檔案中的可用空間不足，無法儲存提供的中繼資料項目。 |
There is not enough space in the virtual disk file for the provided metadata item. |
| 0xC03A0029 | 指定的變更追蹤識別碼無效。 |
The specified change tracking identifier is not valid. |
| 0xC03A002A | 已停用指定之虛擬硬碟的變更追蹤，因此沒有任何可用的變更追蹤資訊。 |
Change tracking is disabled for the specified virtual hard disk, so no change tracking information is available. |
| 0xC03A0030 | 沒有任何可用的變更追蹤資料與指定的變更追蹤識別碼關聯。 |
There is no change tracking data available associated with the specified change tracking identifier. |
| 0xC03B0001 | 已配置該連接埠 |
The port is already allocated |
| 0xC03B0002 | 指定的網路上不支援連接埠對應 |
Port mapping is not supported on the given network |
| 0xC05C0000 | 適當的錯誤碼與感應資料是儲存在伺服器端。 |
The proper error code with sense data was stored on server side. |
| 0xC05CFF00 | 伺服器上沒有要求的錯誤資料。 |
The requested error data is not available on the server. |
| 0xC05CFF01 | Unit Attention 資料可供啟動器查詢。 |
Unit Attention data is available for the initiator to query. |
| 0xC05CFF02 | 裝置的資料功能已變更，導致 Unit Attention 情況。 |
The data capacity of the device has changed, resulting in a Unit Attention condition. |
| 0xC05CFF03 | 先前的操作導致此啟動器的保留被先佔，導致 Unit Attention 情況。 |
A previous operation resulted in this initiator's reservations being preempted, resulting in a Unit Attention condition. |
| 0xC05CFF04 | 先前的操作導致此啟動器的保留被釋放，導致 Unit Attention 情況。 |
A previous operation resulted in this initiator's reservations being released, resulting in a Unit Attention condition. |
| 0xC05CFF05 | 先前的操作導致此啟動器的登錄被先佔，導致 Unit Attention 情況。 |
A previous operation resulted in this initiator's registrations being preempted, resulting in a Unit Attention condition. |
| 0xC05CFF06 | 裝置的資料儲存格式已變更，導致 Unit Attention 情況。 |
The data storage format of the device has changed, resulting in a Unit Attention condition. |
| 0xC05CFF07 | 因為保留衝突，不允許目前的啟動器執行 SCSI 命令。 |
The current initiator is not allowed to perform the SCSI command because of a reservation conflict. |
| 0xC05CFF08 | 只有在固定式或動態 VHDX 格式的虛擬硬碟上才支援多個虛擬機器共用一個虛擬硬碟。 |
Multiple virtual machines sharing a virtual hard disk is supported only on Fixed or Dynamic VHDX format virtual hard disks. |
| 0xC05CFF09 | 伺服器版本不符合所要求的版本。 |
The server version does not match the requested version. |
| 0xC05CFF0A | 無法在虛擬磁碟上執行要求的操作，因為它目前正以共用模式使用中。 |
The requested operation cannot be performed on the virtual disk as it is currently used in shared mode. |
| 0xC05CFF0B | 無效的「共用 VHDX」開啟，因為缺少啟動器識別碼。請檢查相關的「持續可用性」失敗。 |
Invalid Shared VHDX open due to lack of initiator ID. Check for related Continuous Availability failures. |
| 0xC05CFF0C | 要求的操作失敗，因為缺少底層存放裝置檔案。 |
The requested operation failed due to a missing backing storage file. |
| 0xC05D0000 | 無法交涉驗證前完整性雜湊函式。 |
Failed to negotiate a preauthentication integrity hash function. |
| 0xC05D0001 | 目前的叢集功能等級不支援此 SMB 方言。 |
The current cluster functional level does not support this SMB dialect. |
| 0xC0E80000 | 安全性核心無法辨識此命令 |
The command was not recognized by the security core |
| 0xC0EA0001 | 找不到適當的應用程式授權。 |
No applicable app licenses found. |
| 0xC0EA0002 | 找不到用戶端授權平台授權。 |
CLiP license not found. |
| 0xC0EA0003 | 找不到用戶端授權平台裝置授權。 |
CLiP device license not found. |
| 0xC0EA0004 | 用戶端授權平台授權具有無效的簽章。 |
CLiP license has an invalid signature. |
| 0xC0EA0005 | 用戶端授權平台 keyholder 授權無效或遺失。 |
CLiP keyholder license is invalid or missing. |
| 0xC0EA0006 | 用戶端授權平台授權已到期。 |
CLiP license has expired. |
| 0xC0EA0007 | 用戶端授權平台授權是由不明來源所簽署。 |
CLiP license is signed by an unknown source. |
| 0xC0EA0008 | 未簽署 CLiP 授權。 |
CLiP license is not signed. |
| 0xC0EA0009 | 用戶端授權平台授權硬體識別碼超出容忍度。 |
CLiP license hardware ID is out of tolerance. |
| 0xC0EA000A | 用戶端授權平台授權裝置識別碼不符合繫結的裝置授權中的裝置識別碼。 |
CLiP license device ID does not match the device ID in the bound device license. |