| 0x0 | STATUS_SUCCESS |
STATUS_SUCCESS |
| 0x1 | STATUS_WAIT_1 |
STATUS_WAIT_1 |
| 0x2 | STATUS_WAIT_2 |
STATUS_WAIT_2 |
| 0x3 | STATUS_WAIT_3 |
STATUS_WAIT_3 |
| 0x3F | STATUS_WAIT_63 |
STATUS_WAIT_63 |
| 0x80 | STATUS_ABANDONED_WAIT_0 |
STATUS_ABANDONED_WAIT_0 |
| 0xBF | STATUS_ABANDONED_WAIT_63 |
STATUS_ABANDONED_WAIT_63 |
| 0xC0 | STATUS_USER_APC |
STATUS_USER_APC |
| 0xFF | 要求的動作已由之前的作業完成。 |
The requested action was completed by an earlier operation. |
| 0x100 | STATUS_KERNEL_APC |
STATUS_KERNEL_APC |
| 0x101 | STATUS_ALERTED |
STATUS_ALERTED |
| 0x102 | STATUS_TIMEOUT |
STATUS_TIMEOUT |
| 0x103 | 尚未完成要求的操作。 |
The operation that was requested is pending completion. |
| 0x104 | 因為檔案名稱產生符號連結，所以需由物件管理員執行重新分析的操作。 |
A reparse should be performed by the Object Manager since the name of the file resulted in a symbolic link. |
| 0x105 | 列舉 API 的傳回值表示後續的呼叫尚有更多的資訊。 |
Returned by enumeration APIs to indicate more information is available to successive calls. |
| 0x106 | 表示呼叫者未被指定所有參照的特殊權限或群組。例如，可以允許取消所有的特殊權限而不須知道是否已指定了那一項特殊權限。 |
Indicates not all privileges or groups referenced are assigned to the caller.This allows, for example, all privileges to be disabled without having to know exactly which privileges are assigned. |
| 0x107 | 尚未轉譯某些應該轉譯的資訊。 |
Some of the information to be translated has not been translated. |
| 0x108 | 在 oplock 中斷進行中，完成一項開啟/建立操作。 |
An open/create operation completed while an oplock break is underway. |
| 0x109 | 檔案系統已裝上新的磁碟區。 |
A new volume has been mounted by a file system. |
| 0x10A | 這個成功等級狀態指出異動狀態已存在於登錄子目錄，但異動確認在先前已中止。目前已經完成這個確認。 |
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. |
| 0x10B | 表示因關閉控制代碼而產生的提示變更請求已完成。 |
This indicates that a notify change request has been completed due to closing the handle which made the notify change request. |
| 0x10C | 表示將完成一項提示變更請求且資訊不傳入呼叫者的緩衝區內。呼叫者必須自行由檔案中尋找變更。 |
This indicates that a notify change request is being completed and that the information is not being returned in the caller's buffer.The caller now needs to enumerate the files to find the changes. |
| 0x10D | {沒有配額}本帳戶沒有設定系統配額的限制。 |
{No Quotas}No system quota limits are specifically set for this account. |
| 0x10E | {主要傳輸連線錯誤}以主要傳輸連接遠端伺服器 %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. |
| 0x110 | 分頁錯誤為轉換錯誤。 |
Page fault was a transition fault. |
| 0x111 | 分頁錯誤為請求 0 錯誤。 |
Page fault was a demand zero fault. |
| 0x114 | 讀取次級存放裝置時，分頁檔發生錯誤。 |
Page fault was satisfied by reading from a secondary storage device. |
| 0x115 | 操作時鎖定快取記憶體頁。 |
Cached page was locked during operation. |
| 0x116 | 分頁檔含有損毀傾印資料。 |
Crash dump exists in paging file. |
| 0x117 | 指定的緩衝區中包含所有的 0。 |
Specified buffer contains all zeros. |
| 0x119 | 裝置已經完成 '查詢停止'，而且它的資源需求已變更。 |
The device has succeeded a query-stop and its resource requirements have changed. |
| 0x120 | 轉譯程式已將這些資源轉譯到通用空間，不應該再執行進一步的轉譯。 |
The translator has translated these resources into the global space and no further translations should be performed. |
| 0x121 | 目錄服務只評估本機群組成員，因為它無法連絡通用類別目錄伺服器。 |
The directory service evaluated group memberships locally, as it was unable to contact a global catalog server. |
| 0x122 | 即將終止的處理程序沒有執行緒可供終止。 |
A process being terminated has no threads to terminate. |
| 0x123 | 指定的處理程序不是工作的一部分。 |
The specified process is not part of a job. |
| 0x124 | 指定的處理程序是工作的一部分。 |
The specified process is part of a job. |
| 0x125 | {磁碟區陰影複製服務}系統已準備好休眠。 |
{Volume Shadow Copy Service}The system is now ready for hibernation. |
| 0x126 | 檔案系統或檔案系統篩選器驅動程式已經成功的完成 FsFilter 操作。 |
A file system or file system filter driver has successfully completed an FsFilter operation. |
| 0x127 | 指定的插斷向量已連接。 |
The specified interrupt vector was already connected. |
| 0x128 | 指定的插斷向量仍在連接中。 |
The specified interrupt vector is still connected. |
| 0x129 | 目前的程序是一個複製的程序。 |
The current process is a cloned process. |
| 0x12A | 檔案已經鎖定，且該檔案的所有使用者只能讀取。 |
The file was locked and all users of the file can only read. |
| 0x12B | 檔案已經鎖定，而且至少有一個檔案的使用者可以寫入。 |
The file was locked and at least one user of the file can write. |
| 0x12C | 檔案映像雜湊有效。 |
The file image hash is valid. |
| 0x12D | 檔案類別目錄雜湊有效。 |
The file catalog hash is valid. |
| 0x12E | 檔案雜湊有效並使用強式程式碼完整性。 |
The file hash is valid and uses strong code integrity. |
| 0x12F | IO 範圍中至少有一個部分與映像 (Ghosted) 檔案範圍有交集。 |
At least a portion of IO range intersects with a ghosted file range. |
| 0x202 | 指定的 ResourceManager 對此交易下的資源未進行任何變更或更新。 |
The specified ResourceManager made no changes or updates to the resource under this transaction. |
| 0x210 | 在成功地插入封包之前，指定的信號緩衝區是空的。 |
The specified ring buffer was empty before the packet was successfully inserted. |
| 0x211 | 在成功地移除封包之前，指定的信號緩衝區是滿的。 |
The specified ring buffer was full before the packet was successfully removed. |
| 0x212 | 指定的信號緩衝區已低於其未處理交易的配額。 |
The specified ring buffer has dropped below its quota of outstanding transactions. |
| 0x213 | 在移除目前的封包之後，指定的信號緩衝區現在已變成空的。 |
The specified ring buffer has, with the removal of the current packet, now become empty. |
| 0x214 | 指定的信號緩衝區之前是空的或之前是滿的，這意味著呼叫者應該對反向端點發出信號。 |
The specified ring buffer was either previously empty or previously full which implies that the caller should signal the opposite endpoint. |
| 0x215 | 與此控制代碼關聯的 Oplock 現在已與其他控制代碼相關聯。 |
The oplock that was associated with this handle is now associated with a different handle. |
| 0x216 | 與這個 Oplock 關聯的控制代碼已經關閉。Oplock 現在已經中斷。 |
The handle with which this oplock was associated has been closed. The oplock is now broken. |
| 0x367 | 中止操作，以等候 oplock。 |
An operation is blocked waiting for an oplock. |
| 0x368 | 應該由「物件管理員」從全域根目錄執行重新分析，以逸出容器命名空間。 |
A reparse should be performed by the Object Manager from the global root to escape the container name space. |
| 0x00010001 | 偵錯工具處理了例外 |
Debugger handled exception |
| 0x00010002 | 偵錯工具已經繼續 |
Debugger continued |
| 0x001C0001 | 篩選器已完成 IO。 |
The IO was completed by a filter. |
| 0x00293000 | 遠端 TPM 內容交換未完成。內容應該傳輸到目標並繼續。 |
The remote TPM context exchange is not complete. The context should be transported to the target and continued. |
| 0x00293001 | 遠端 TPM 操作已完成。 |
The remote TPM operation is complete. |
| 0x00350059 | 裝置具有擱置中的頁面要求，且該要求已被捨棄。 |
The device had pending page requests which were discarded. |
| 0x00E70000 | 修復成功。 |
The repair was successful. |
| 0x00E70001 | 已暫停操作。 |
The operation has been paused. |
| 0x00E70002 | 操作完成。 |
The operation is complete. |
| 0x00E70003 | 該作業應該被重新導向到另一個節點。 |
The operation should be redirected to another node. |
| 0x40000000 | {物件已存在}試圖建立一名稱已存在的物件。 |
{Object Exists}An attempt was made to create an object and the object name already existed. |
| 0x40000001 | {暫停執行緒}暫停執行緒時，發生執行緒終止情況。當恢復執行緒時即取消終止。 |
{Thread Suspended}A thread termination occurred while the thread was suspended. The thread was resumed, and termination proceeded. |
| 0x40000002 | {工作組範圍錯誤}嘗試設定超過工作組所允許的最小或最大值範圍。 |
{Working Set Range Error}An attempt was made to set the working set minimum or maximum to values which are outside of the allowable range. |
| 0x40000003 | {映像重配置}無法在映像檔指定的位址對應該映像檔。必須執行本機映像檔修正。 |
{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. |
| 0x40000004 | 這個資訊層級狀態表示某個特定登錄的子目錄交易狀態不存在，且必須建立。 |
This informational level status indicates that a specified registry sub-tree transaction state did not yet exist and had to be created. |
| 0x40000005 | {區段載入}正載入、解除載入一個虛擬 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. |
| 0x40000006 | {本機工作階段金鑰}本機 RPC 連線要求的使用者工作階段金鑰。這個工作階段金鑰傳回一常數值，而且不是這個連線的唯一值。 |
{Local Session Key}A user session key was requested for a local RPC connection. The session key returned is a constant value and not unique to this connection. |
| 0x40000007 | {目前的目錄無效}處理程序無法切換到啟動目前目錄 %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. |
| 0x40000008 | {完成序列 IOCTL}已有其他寫入動作來完成序列埠的 I/O 操作。(IOCTL_SERIAL_XOFF_COUNTER 到達 0。) |
{Serial IOCTL Complete}A serial I/O operation was completed by another write to a serial port.(The IOCTL_SERIAL_XOFF_COUNTER reached zero.) |
| 0x40000009 | {登錄修復}必須使用記錄檔或其他備份檔來修復含有系統登錄資料的檔案。修復成功。 |
{Registry Recovery}One of the files containing the system's Registry data had to be recovered by use of a log or alternate copy. The recovery was successful. |
| 0x4000000A | {複件讀取}為了完成讀取要求，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. |
| 0x4000000B | {複件寫入}為了完成讀取要求，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. |
| 0x4000000C | {序列 IOCTL 傳輸逾時}傳輸等候逾時，序列 I/O 操作完成。(IOCTL_SERIAL_XOFF_COUNTER 未到達 0。) |
{Serial IOCTL Timeout}A serial I/O operation completed because the time-out period expired. (The IOCTL_SERIAL_XOFF_COUNTER had not reached zero.) |
| 0x4000000D | {密碼太複雜}Windows 密碼太複雜無法轉換成 LAN Manager 密碼。傳回的 LAN Manager 密碼是 NULL 字串。 |
{Password Too Complex}The Windows password is too complex to be converted to a LAN Manager password. The LAN Manager password returned is a NULL string. |
| 0x4000000E | {電腦類型不符}映像檔 %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. |
| 0x4000000F | {已接收部分資料}網路已傳輸部分資料至用戶端。稍後再傳輸其餘資料。 |
{Partial Data Received}The network transport returned partial data to its client. The remaining data will be sent later. |
| 0x40000010 | {已接收資料}網路傳輸資料至用戶端並在遠端系統上標記已傳輸。 |
{Expedited Data Received}The network transport returned data to its client that was marked as expedited by the remote system. |
| 0x40000011 | {已接收部分資料}網路已傳輸部分資料至用戶端且在遠端系統上標記該資料。稍後再傳輸其餘資料。 |
{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. |
| 0x40000012 | {TDI 事件完成}TDI 指標已成功完成。 |
{TDI Event Done}The TDI indication has completed successfully. |
| 0x40000013 | {TDI 事件擱置}TDI 指標進入等待狀態。 |
{TDI Event Pending}The TDI indication has entered the pending state. |
| 0x40000014 | 檢查 %wZ 上的檔案系統 |
Checking file system on %wZ |
| 0x40000015 | {嚴重的應用程式結束}%hs |
{Fatal Application Exit}%hs |
| 0x40000016 | 指定的登錄機碼被一個預先定義的控制代碼所參照。 |
The specified registry key is referenced by a predefined handle. |
| 0x40000017 | {解除分頁鎖定}分頁鎖定的保護狀態變更為 [不允許存取] 且從記憶體及程序中解除分頁鎖定。 |
{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. |
| 0x40000018 | %hs |
%hs |
| 0x40000019 | {分頁鎖定}欲鎖定的分頁之一已鎖定。 |
{Page Locked}One of the pages to lock was already locked. |
| 0x4000001A | 應用程式快顯: %1: %2 |
Application popup: %1 : %2 |
| 0x4000001B | STATUS_ALREADY_WIN32 |
STATUS_ALREADY_WIN32 |
| 0x4000001C | 例外狀態碼被 Win32 x86 模擬子系統所使用。 |
Exception status code used by Win32 x86 emulation subsystem. |
| 0x40000023 | {電腦類型不符}映像檔 %hs 正確，但不屬於目前的電腦類型。 |
{Machine Type Mismatch}The image file %hs is valid, but is for a machine type other than the current machine. |
| 0x40000024 | 執行 yield 而沒有可用來執行的執行緒。 |
A yield execution was performed and no thread was available to run. |
| 0x40000025 | 略過計時器 API 的可恢復旗標。 |
The resumable flag to a timer API was ignored. |
| 0x40000026 | 仲裁程式已經將這些資源的仲裁順延到它的父系上 |
The arbiter has deferred arbitration of these resources to its parent |
| 0x40000027 | 裝置 \"%hs\" 已偵測到插槽中有一張 CardBus 介面卡，但系統韌體的設定不允許 CardBus 控制器在 CardBus 模式下執行。這個作業系統目前在這個控制器上只支援 16 位元 (R2) 電腦介面卡。 |
The device \"%hs\" has detected a CardBus card in its slot, but the firmware on this system is not configured to allow the CardBus controller to be run in CardBus mode.The operating system will currently accept only 16-bit (R2) pc-cards on this controller. |
| 0x40000029 | 這個多處理器系統內的 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. |
| 0x4000002A | 系統已進入休眠狀態中。 |
The system was put into hibernation. |
| 0x4000002B | 系統已從休眠狀態復甦繼續。 |
The system was resumed from hibernation. |
| 0x4000002C | Windows 偵測到系統韌體 (BIOS) 已更新 [前版韌體日期 = %2，目前的韌體日期 %3]。 |
Windows has detected that the system firmware (BIOS) was updated [previous firmware date = %2, current firmware date %3]. |
| 0x4000002D | 裝置驅動程式正在漏出鎖定的 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. |
| 0x4000002E | 正在取消的 ALPC 訊息已經從另一端的佇列抓取。 |
The ALPC message being canceled has already been retrieved from the queue on the other side. |
| 0x4000002F | 系統電源狀態正由 %2 轉換為 %3。 |
The system power state is transitioning from %2 to %3. |
| 0x40000030 | 接收作業成功。請檢查 ALPC 完成清單以取得接收到的訊息。 |
The receive operation was successful. Check the ALPC completion list for the received message. |
| 0x40000031 | 系統電源狀態正由 %2 轉換為 %3，但可能會進入 %4。 |
The system power state is transitioning from %2 to %3 but could enter %4. |
| 0x40000032 | 對 %1 的存取是由原則規則 %2 監視。 |
Access to %1 is monitored by policy rule %2. |
| 0x40000033 | 有效的休眠檔案已經失效，且應該將其丟棄。 |
A valid hibernation file has been invalidated and should be abandoned. |
| 0x40000034 | 呼叫應用程式的商務規則指令碼已停用。 |
Business rule scripts are disabled for the calling application. |
| 0x40000035 | 已順利讀取指定的要求資料複本。 |
The specified copy of the requested data was successfully read. |
| 0x40000036 | {映像重新放置}映像並非從所指定映像檔中的位址對應，但仍會在該映像上執行自動修正。 |
{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. |
| 0x40000294 | 系統已經醒機 |
The system has awoken |
| 0x40000370 | 目錄服務關閉中。 |
The Directory Service is shutting down. |
| 0x40000807 | 無法在磁碟區連線時執行磁碟區修復。請排程讓磁碟區離線，以進行修復。 |
The volume repair could not be performed while it is online.Please schedule to take the volume offline so that it can be repaired. |
| 0x4000A144 | 在執行層級切換的服務啟動階段期間，無法啟動一個或多個服務。 |
One or more services failed to start during the service startup phase of a run level switch. |
| 0x40010001 | 偵錯工具稍後將回覆。 |
Debugger will reply later. |
| 0x40010002 | 偵錯工具無法提供控制代碼。 |
Debugger cannot provide handle. |
| 0x40010003 | 偵錯工具已經終止執行緒。 |
Debugger terminated thread. |
| 0x40010004 | 偵錯工具已經終止處理程序。 |
Debugger terminated process. |
| 0x40010005 | 偵錯工具取得控制 C。 |
Debugger got control C. |
| 0x40010006 | 偵錯工具列印出在控制 C 上的例外。 |
Debugger printed exception on control C. |
| 0x40010007 | 偵錯工具收到 RIP 例外。 |
Debugger received RIP exception. |
| 0x40010008 | 偵錯工具收到控制中斷。 |
Debugger received control break. |
| 0x40010009 | 偵錯工具命令通訊例外狀況。 |
Debugger command communication exception. |
| 0x4001000A | 偵錯工具列印出在控制 C 上的例外狀況。 |
Debugger printed exception on control C. |
| 0x40020056 | 已配置一個只在這部電腦有效的 UUID。 |
A UUID that is valid only on this computer has been allocated. |
| 0x400200AF | 在要求緩衝區中，仍有一些資料需要傳送。 |
Some data remains to be sent in the request buffer. |
| 0x400A0004 | 終端機連線的用戶端磁碟對應服務已經連線。 |
The Client Drive Mapping Service Has Connected on Terminal Connection. |
| 0x400A0005 | 終端機連線的用戶端磁碟對應服務已經中斷連線。 |
The Client Drive Mapping Service Has Disconnected on Terminal Connection. |
| 0x4015000D | 核心模式元件正在啟用內容中釋放參照。 |
A kernel mode component is releasing a reference on an activation context. |
| 0x40190001 | 認可交易的嘗試已完成，但交易樹狀目錄的某些部分可能因啟發學習法而沒有認可成功。因此，交易中的部分修改資料可能尚未認可，這會導致交易的不一致。如果可能，請檢查關聯資料的一致性。 |
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. |
| 0x40190034 | 交易資源管理員已經一致。不需要進行修復。 |
The transactional resource manager is already consistent. Recovery is not needed. |
| 0x40190035 | 交易資源管理員已經啟動。 |
The transactional resource manager has already been started. |
| 0x401A000C | 記錄服務遇到沒有重新啟動區域的記錄資料流。 |
Log service encountered a log stream with no restart area. |
| 0x401B00EC | {顯示驅動程式從失敗復原}%hs 顯示驅動程式偵測到失敗並從失敗復原，某些圖形操作可能已失敗。下次您重新開機時，將會呈現一個對話方塊讓您有機會上傳有關這個問題的資料給 Microsoft。 |
{Display Driver Recovered From Failure}The %hs display driver has detected and recovered from a failure. Some graphical operations may have failed. The next time you reboot the machine a dialog will be displayed giving you a chance to upload data about this failure to Microsoft. |
| 0x401E000A | 指定的緩衝區太小，不足以包含整個要求的資料集。某些資料擴展到緩衝區大小之外。呼叫者必須提供部分擴展緩衝區內容中指定的緩衝區大小 (特定介面)。 |
Specified buffer is not big enough to contain entire requested dataset. Partial data populated upto the size of the buffer. Caller needs to provide buffer of size as specified in the partially populated buffer's content (interface specific). |
| 0x401E0201 | 略過 DMA 緩衝區所參照的配置準備。 |
Skip preparation of allocations referenced by the DMA buffer. |
| 0x401E0307 | 指定的 VidPN 來源/目標上未釘選任何模式。 |
No mode is pinned on the specified VidPN source/target. |
| 0x401E031E | 指定的模式集並未替其中一種模式指定喜好設定。 |
Specified mode set does not specify preference for one of its modes. |
| 0x401E034B | 指定的資料集 (例如模式集、頻率範圍集、描述元集和拓撲等) 空白。 |
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty. |
| 0x401E034C | 指定的資料集 (例如模式集、頻率範圍集、描述元集和拓撲等) 不再包含任何元素。 |
Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements. |
| 0x401E0351 | 指定的內容格式變更在指定的 VidPN 呈現路徑中並未釘選。 |
Specified content transformation is not pinned on the specified VidPN present path. |
| 0x401E042F | 並未確實偵測子裝置的存在。 |
Child device presence was not reliably detected. |
| 0x401E0437 | 啟動前置連結配接器已暫時順延。 |
Starting the leadlink adapter has been deferred temporarily. |
| 0x401E0439 | 已經為子系在相同的輪詢層級輪詢顯示器介面卡太多次。 |
The display adapter is being polled for children too frequently at the same polling level. |
| 0x401E043A | 介面卡的啟動已暫時順延。 |
Starting the adapter has been deferred temporarily. |
| 0x401E043C | 我們可以依賴驅動程式傳回的子裝置呈現。 |
We can depend on the child device presence returned by the driver. |
| 0x40230001 | 稍後將由 NDIS 狀態表示完成此要求。 |
The request will be completed later by NDIS status indication. |
| 0x80000001 | {例外}防護分頁例外已存取標記資料結構 (如堆疊或陣列) 結尾的記憶體分頁。 |
{EXCEPTION}Guard Page ExceptionA page of memory that marks the end of a data structure, such as a stack or an array, has been accessed. |
| 0x80000002 | {例外}指定錯誤載入或儲存指令所偵測的資料類型指定錯誤。 |
{EXCEPTION}Alignment FaultA datatype misalignment was detected in a load or store instruction. |
| 0x80000003 | {例外}中斷點已到達中斷點。 |
{EXCEPTION}BreakpointA breakpoint has been reached. |
| 0x80000004 | {例外}單步已完成單步或追蹤操作。 |
{EXCEPTION}Single StepA single step or trace operation has just been completed. |
| 0x80000005 | {緩衝區溢位}資料過大以致於無法載入所指定的緩衝區。 |
{Buffer Overflow}The data was too large to fit into the specified buffer. |
| 0x80000006 | {無其他的檔案}已無其他符合該檔案格式的檔案。 |
{No More Files}No more files were found which match the file specification. |
| 0x80000007 | {核心偵錯工具觸發}由插斷觸發的系統偵錯工具。 |
{Kernel Debugger Awakened}the system debugger was awakened by an interrupt. |
| 0x8000000A | {控制代碼已關閉}依操作要求而自動關閉的物件控制代碼。 |
{Handles Closed}Handles to objects have been automatically closed as a result of the requested operation. |
| 0x8000000B | {非繼承的 ACL}存取控制清單 (ACL) 中不包含可繼承的元件。 |
{Non-Inheritable ACL}An access control list (ACL) contains no components that can be inherited. |
| 0x8000000C | {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. |
| 0x8000000D | {部分複製}因保護衝突無法複製所有請求的位元組。 |
{Partial Copy}Due to protection conflicts not all the requested bytes could be copied. |
| 0x8000000E | {紙張用完了}印表機內沒有紙張了。 |
{Out of Paper}The printer is out of paper. |
| 0x8000000F | {未開啟裝置電源}沒有開啟印表機電源。 |
{Device Power Is Off}The printer power has been turned off. |
| 0x80000010 | {裝置離線}印表機已離線。 |
{Device Offline}The printer has been taken offline. |
| 0x80000011 | {裝置忙碌}裝置使用中。 |
{Device Busy}The device is currently busy. |
| 0x80000012 | {無其他 EAs}無法取得該檔案的其他擴充屬性 (EAs)。 |
{No More EAs}No more extended attributes (EAs) were found for the file. |
| 0x80000013 | {不正確的 EA}指定的擴充屬性 (EA) 名稱中至少包含一個不正確的字元。 |
{Illegal EA}The specified extended attribute (EA) name contains at least one illegal character. |
| 0x80000014 | {不一致的 EA 清單}擴充屬性 (EA) 清單不一致。 |
{Inconsistent EA List}The extended attribute (EA) list is inconsistent. |
| 0x80000015 | {不正確的 EA 旗標}設定不正確的擴充屬性 (EA) 旗標。 |
{Invalid EA Flag}An invalid extended attribute (EA) flag was set. |
| 0x80000016 | {確認磁碟機}媒體已變更而且正在確認中，無法對該裝置執行除了確認操作以外的讀取或寫入動作。 |
{Verifying Disk}The media has changed and a verify operation is in progress so no reads or writes may be performed to the device, except those used in the verify operation. |
| 0x80000017 | {過多的資訊}指定的存取控制清單 (ACL) 中包含過多的資訊。 |
{Too Much Information}The specified access control list (ACL) contained more information than was expected. |
| 0x80000018 | 這個警告等級狀態指出交易狀態已經存在於登錄子目錄，但交易確認動作已中止。確認動作並未完成，也未還原到上一步的操作。(它可能還處在確認狀態)。 |
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). |
| 0x8000001A | {無其他項目}列舉操作中已無其他項目。 |
{No More Entries}No more entries are available from an enumeration operation. |
| 0x8000001B | {發現檔案標記}偵測到一檔案標記。 |
{Filemark Found}A filemark was detected. |
| 0x8000001C | {媒體變更}媒體可能已變更。 |
{Media Changed}The media may have changed. |
| 0x8000001D | {重設 I/O 匯流排}偵測到重設 I/O 匯流排。 |
{I/O Bus Reset}An I/O bus reset was detected. |
| 0x8000001E | {媒體結尾}已達媒體結尾。 |
{End of Media}The end of the media was encountered. |
| 0x8000001F | 偵測到磁帶或磁碟分割區的開頭。 |
Beginning of tape or partition has been detected. |
| 0x80000021 | 已到達磁帶的設定標記。 |
A tape access reached a setmark. |
| 0x80000022 | 已到達磁帶存取時的資料寫入結尾。 |
During a tape access, the end of the data written is reached. |
| 0x80000023 | 重新導向器正在使用中，無法被解除載入。 |
The redirector is in use and cannot be unloaded. |
| 0x80000024 | 伺服器使用中且無法被解除載入。 |
The server is in use and cannot be unloaded. |
| 0x80000025 | 已中斷指定的連線。 |
The specified connection has already been disconnected. |
| 0x80000026 | 已經執行一個長跳躍。 |
A long jump has been executed. |
| 0x80000027 | 清潔卡匣出現在磁帶媒體櫃。 |
A cleaner cartridge is present in the tape library. |
| 0x80000028 | 隨插即用查詢操作沒有成功。 |
The Plug and Play query operation was not successful. |
| 0x80000029 | 框架合併已執行。 |
A frame consolidation has been executed. |
| 0x8000002A | {登錄 Hive 已修復}登錄 hive (檔案):%hs原已毀損，現已修復。某些資料可能已遺失。 |
{Registry Hive Recovered}Registry hive (file):%hswas corrupted and it has been recovered. Some data might have been lost. |
| 0x8000002B | 應用程式嘗試執行來自模組 %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? |
| 0x8000002C | 應用程式正在從模組 %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? |
| 0x8000002D | 到達符號連結後，建立作業已停止。 |
The create operation stopped after reaching a symbolic link. |
| 0x8000002E | 不允許所要求層級的 Oplock。應有可用的較低層級 Oplock。 |
An oplock of the requested level cannot be granted. An oplock of a lower level may be available. |
| 0x8000002F | {無 ACE 條件}指定的存取控制項目 (ACE) 未包含條件。 |
{No ACE Condition}The specified access control entry (ACE) does not contain a condition. |
| 0x80000030 | {支援待確定}正在偵測裝置的命令支援。 |
{Support Being Determined}Device's command support detection is in progress. |
| 0x80000031 | 裝置需要重新啟動電源。 |
The device needs to be power cycled. |
| 0x80000032 | 要求的動作造成未執行任何工作。已執行錯誤樣式清除。 |
The action requested resulted in no work being done. Error-style clean-up has been performed. |
| 0x80000288 | 裝置已經指出必須執行清除動作。 |
The device has indicated that cleaning is necessary. |
| 0x80000289 | 裝置已經指出它的門沒有關。請先將門關閉，再執行進一步的操作。 |
The device has indicated that its door is open. Further operations require it closed and secured. |
| 0x80000803 | Windows 在檔案 \"%hs\" 中發現損毀。現在已修復這個檔案。請檢查檔案中是否有任何資料因為損毀而遺失。 |
Windows discovered a corruption in the file \"%hs\".This file has now been repaired.Please check if any data in the file was lost because of the corruption. |
| 0x8000A127 | 要求取消遮罩的插斷並未進行遮罩。 |
The interrupt requested to be unmasked is not masked. |
| 0x8000CF00 | 雲端檔案屬性 Blob 可能已損毀。磁碟上的總和檢查碼與計算的總和檢查碼不符。 |
The Cloud File property blob is possibly corrupt. The on-disk checksum does not match the computed checksum. |
| 0x8000CF04 | 作業無法完成，因為雲端檔案屬性 Blob 太大。 |
The operation could not be completed because the Cloud File property blob is too large. |
| 0x8000CF05 | 因為會超過「雲端檔案」屬性 Blob 數目上限，所以無法完成作業。 |
The operation could not be completed because the maximum number of Cloud File property blobs would be exceeded. |
| 0x80010001 | 偵錯工具並未處理例外狀況。 |
Debugger did not handle the exception. |
| 0x80130001 | 這個叢集節點已經啟用了。 |
The cluster node is already up. |
| 0x80130002 | 叢集節點已關閉。 |
The cluster node is already down. |
| 0x80130003 | 這個叢集網路已經連線了。 |
The cluster network is already online. |
| 0x80130004 | 這個叢集網路介面已經離線了。 |
The cluster network is already offline. |
| 0x80130005 | 這個叢集節點已是叢集的成員之一。 |
The cluster node is already a member of the cluster. |
| 0x80190009 | 無法將記錄設定為要求的大小。 |
The log could not be set to the requested size. |
| 0x80190029 | 檔案上沒有任何交易中繼資料。 |
There is no transaction metadata on the file. |
| 0x80190031 | 因為檔案中仍有開啟的控制代碼，所以無法復原檔案。 |
The file can't be recovered because there is a handle still open on it. |
| 0x80190041 | 交易中繼資料已存在此檔案中，且無法取代。 |
Transaction metadata is already present on this file and cannot be superseded. |
| 0x80190042 | 因為無法初始化範圍處理常式，所以無法輸入交易範圍。 |
A transaction scope could not be entered because the scope handler has not been initialized. |
| 0x801B00EB | {顯示器驅動程式已停止回應，並且已復原}%hs 顯示器驅動程式已停止正常工作，並且已執行修復。 |
{Display Driver Stopped Responding and recovered}The %hs display driver has stopped working normally. The recovery had been performed. |
| 0x801C0001 | {緩衝區過小}緩衝區過小以致於無法包含項目。無法在緩衝區寫入任何資訊。 |
{Buffer too small}The buffer is too small to contain the entry. No information has been written to the buffer. |
| 0x80210001 | 磁碟區中繼資料讀取或寫入不完整。 |
Volume Metadata read or write is incomplete. |
| 0x80210002 | 已略過 BitLocker 加密金鑰，因為磁碟區處於暫時狀態。 |
BitLocker encryption keys were ignored because the volume was in a transient state. |
| 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. |
| 0x803F0001 | GDI 控制代碼可能已被應用程式洩漏。 |
GDI handles were potentially leaked by the application. |
| 0x80430006 | 此電腦未啟用安全開機。 |
Secure Boot is not enabled on this machine. |
| 0xC0000001 | {操作失敗}要求的操作不成功。 |
{Operation Failed}The requested operation was unsuccessful. |
| 0xC0000002 | {未執行}未執行要求的操作。 |
{Not Implemented}The requested operation is not implemented. |
| 0xC0000003 | {不正確的參數}指定的資訊等級為不正確的指定物件資訊等級。 |
{Invalid Parameter}The specified information class is not a valid information class for the specified object. |
| 0xC0000004 | 指定的資訊記錄長度與請求的資訊等級長度不符合。 |
The specified information record length does not match the length required for the specified information class. |
| 0xC0000005 | 位於 0x%p 的指令參考位於 0x%p 的記憶體。該記憶體不能為 %s。 |
The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s. |
| 0xC0000006 | 0x%p 指令參考的 0x%p 記憶體。因 0x%x 的 I/O 錯誤狀態而無法將請求的資料放入記憶體。 |
The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x. |
| 0xC0000007 | 程序的分頁檔配額已用盡。 |
The pagefile quota for the process has been exhausted. |
| 0xC0000008 | 指定了不正確的 HANDLE。 |
An invalid HANDLE was specified. |
| 0xC0000009 | 呼叫 NtCreateThread 時指定一不正確的起始堆疊。 |
An invalid initial stack was specified in a call to NtCreateThread. |
| 0xC000000A | 呼叫 NtCreateThread 時指定一不正確的起始位址。 |
An invalid initial start address was specified in a call to NtCreateThread. |
| 0xC000000B | 指定不正確的用戶端識別碼。 |
An invalid Client ID was specified. |
| 0xC000000C | 試圖取消或設定具關聯 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. |
| 0xC000000D | 將不正確的參數傳送給服務或功能。 |
An invalid parameter was passed to a service or function. |
| 0xC000000E | 指定的裝置不存在。 |
A device which does not exist was specified. |
| 0xC000000F | {無法找到檔案}檔案 %hs 不存在。 |
{File Not Found}The file %hs does not exist. |
| 0xC0000010 | 指定的要求不是目標裝置所要的正確操作。 |
The specified request is not a valid operation for the target device. |
| 0xC0000011 | 已到達檔案結尾標記。在標記之後已無有效的檔案。 |
The end-of-file marker has been reached. There is no valid data in the file beyond this marker. |
| 0xC0000012 | {錯誤的磁碟區}磁碟機中的磁碟區錯誤。請在磁碟機 %hs 中插入磁碟區 %hs。 |
{Wrong Volume}The wrong volume is in the drive.Please insert volume %hs into drive %hs. |
| 0xC0000013 | {沒有磁片}磁碟機中沒有磁片。請在磁碟機 %hs 中插入磁片。 |
{No Disk}There is no disk in the drive.Please insert a disk into drive %hs. |
| 0xC0000014 | {不明的磁碟格式}磁碟機 %hs 中的磁片尚未格式化。請檢查該磁片，必要時重新格式化。 |
{Unknown Disk Format}The disk in drive %hs is not formatted properly.Please check the disk, and reformat if necessary. |
| 0xC0000015 | {找不到磁區}指定的磁區不存在。 |
{Sector Not Found}The specified sector does not exist. |
| 0xC0000016 | {忙碌中}指定的 I/O 請求封包 (IRP) 因 I/O 操作尚未完成而無法處理。 |
{Still Busy}The specified I/O request packet (IRP) cannot be disposed of because the I/O operation is not complete. |
| 0xC0000017 | {無足夠的配額}沒有足夠的虛擬記憶體或分頁檔配額以完成指定的操作。 |
{Not Enough Quota}Not enough virtual memory or paging file quota is available to complete the specified operation. |
| 0xC0000018 | {位址範圍衝突}指定的位址範圍與位址空間衝突。 |
{Conflicting Address Range}The specified address range conflicts with the address space. |
| 0xC0000019 | 無法檢視未對應的位址範圍。 |
Address range to unmap is not a mapped view. |
| 0xC000001A | 無法釋放虛擬記憶體。 |
Virtual memory cannot be freed. |
| 0xC000001B | 無法偵測指定的區段。 |
Specified section cannot be deleted. |
| 0xC000001C | 在系統服務呼叫中指定一不正確的系統服務。 |
An invalid system service was specified in a system service call. |
| 0xC000001D | {例外}不正確的指令試圖執行一不正確的指令。 |
{EXCEPTION}Illegal InstructionAn attempt was made to execute an illegal instruction. |
| 0xC000001E | {不正確的鎖定順序}試圖執行一不正確的鎖定順序。 |
{Invalid Lock Sequence}An attempt was made to execute an invalid lock sequence. |
| 0xC000001F | {不正確的對應}試圖建立大於區段的區段檢視。 |
{Invalid Mapping}An attempt was made to create a view for a section which is bigger than the section. |
| 0xC0000020 | {損壞的檔案}無法讀取記憶體區段的指定對應檔案屬性。 |
{Bad File}The attributes of the specified mapping file for a section of memory cannot be read. |
| 0xC0000021 | {已接受委託}指定的位址範圍已接受委託。 |
{Already Committed}The specified address range is already committed. |
| 0xC0000022 | {拒絕存取}程序已請求存取一物件，但未被授與存取權。 |
{Access Denied}A process has requested access to an object, but has not been granted those access rights. |
| 0xC0000024 | {錯誤類型}要求操作所需的物件類型與在要求中指定的物件類型不符合。 |
{Wrong Type}There is a mismatch between the type of object required by the requested operation and the type of object that is specified in the request. |
| 0xC0000025 | {例外}無法繼續Windows 無法從例外中繼續。 |
{EXCEPTION}Cannot ContinueWindows cannot continue from this exception. |
| 0xC0000026 | 由例外處理常式傳回一不正確的例外配置。 |
An invalid exception disposition was returned by an exception handler. |
| 0xC0000027 | 解除例外狀況代碼。 |
Unwind exception code. |
| 0xC0000028 | 在解除操作時遇到無效或不正確配置的堆疊。 |
An invalid or unaligned stack was encountered during an unwind operation. |
| 0xC0000029 | 在解除操作時遇到不正確的解除目標。 |
An invalid unwind target was encountered during an unwind operation. |
| 0xC000002A | 試圖解除一個未被鎖定的記憶體分頁鎖定。 |
An attempt was made to unlock a page of memory which was not locked. |
| 0xC000002B | I/O 操作時的裝置同位檢查錯誤。 |
Device parity error on I/O operation. |
| 0xC000002C | 試圖解除未接受委託虛擬記憶體的委託。 |
An attempt was made to decommit uncommitted virtual memory. |
| 0xC000002D | 試圖更改已接受委託的記憶體屬性。 |
An attempt was made to change the attributes on memory that has not been committed. |
| 0xC000002E | 指定給 NtCreatePort 不正確的物件屬性或指定給 NtConnectPort 不正確的連接埠屬性。 |
Invalid Object Attributes specified to NtCreatePort or invalid Port Attributes specified to NtConnectPort |
| 0xC000002F | 傳送給 NtRequestPort 或 NtRequestWaitReplyPort 的訊息長度大於連接埠允許的最大長度。 |
Length of message passed to NtRequestPort or NtRequestWaitReplyPort was longer than the maximum message allowed by the port. |
| 0xC0000030 | 指定的參數組合不正確。 |
An invalid combination of parameters was specified. |
| 0xC0000031 | 試圖將配額限制降到低於目前的使用率。 |
An attempt was made to lower a quota limit below the current usage. |
| 0xC0000032 | {磁碟機損毀}磁碟機的檔案系統結構已損毀且無法使用。請在磁碟區 %hs 上執行 Chkdsk 公用程式。 |
{Corrupt Disk}The file system structure on the disk is corrupt and unusable.Please run the Chkdsk utility on the volume %hs. |
| 0xC0000033 | 物件名稱不正確。 |
Object Name invalid. |
| 0xC0000034 | 物件名稱未找到。 |
Object Name not found. |
| 0xC0000035 | 物件名稱已存在。 |
Object Name already exists. |
| 0xC0000036 | 已設定「請勿打擾」旗標的連接埠嘗試傳送訊息給某個暫停程序中的連接埠。並未喚醒該程序，也未傳遞訊息。 |
A port with the 'do not disturb' flag set attempted to send a message to a port in a suspended process.The process was not woken, and the message was not delivered. |
| 0xC0000037 | 嘗試傳送訊息至已斷線的通訊連接埠。 |
Attempt to send a message to a disconnected communication port. |
| 0xC0000038 | 試圖連結一個已連結至其他裝置的裝置。 |
An attempt was made to attach to a device that was already attached to another device. |
| 0xC0000039 | 物件路徑元件不是目錄物件。 |
Object Path Component was not a directory object. |
| 0xC000003A | {找不到路徑}路徑 %hs 不存在。 |
{Path Not Found}The path %hs does not exist. |
| 0xC000003C | {資料滿溢}發生資料滿溢錯誤。 |
{Data Overrun}A data overrun error occurred. |
| 0xC000003D | {資料延遲}發生資料延遲錯誤。 |
{Data Late}A data late error occurred. |
| 0xC000003E | {資料錯誤}發生資料讀取或寫入錯誤。 |
{Data Error}An error in reading or writing data occurred. |
| 0xC000003F | {錯誤的 CRC}循環冗餘檢查 (CRC) 總和檢查碼發生錯誤。 |
{Bad CRC}A cyclic redundancy check (CRC) checksum error occurred. |
| 0xC0000040 | {區段過長}指定的區段過長以致於無法對應檔案。 |
{Section Too Large}The specified section is too big to map the file. |
| 0xC0000041 | NtConnectPort 請求被拒絕。 |
The NtConnectPort request is refused. |
| 0xC0000042 | 操作所要求的連接埠控制代碼類型不正確。 |
The type of port handle is invalid for the operation requested. |
| 0xC0000043 | 因共用存取旗標不相容無法開啟檔案。 |
A file cannot be opened because the share access flags are incompatible. |
| 0xC0000044 | 配額不足無法完成操作 |
Insufficient quota exists to complete the operation |
| 0xC0000045 | 指定的分頁保護不正確。 |
The specified page protection was not valid. |
| 0xC0000046 | 不是衍生物件擁有者的執行緒試圖釋放該衍生物件。 |
An attempt to release a mutant object was made by a thread that was not the owner of the mutant object. |
| 0xC0000047 | 試圖釋放已超過最大計數的信號。 |
An attempt was made to release a semaphore such that its maximum count would have been exceeded. |
| 0xC0000048 | 嘗試設定處理程序的 DebugPort 或 ExceptionPort，但是程序中已有連接埠，或是嘗試設定檔案的 CompletionPort，但是檔案中已設定連接埠，或是嘗試設定與完成連接埠相關聯的 ALPC 連接埠，但是它已設定。 |
An attempt to set a process's DebugPort or ExceptionPort was made, but a port already exists in the process or an attempt to set a file's CompletionPort made, but a port was already set in the file or an attempt to set an ALPC port's associated completion port was made, but it is already set. |
| 0xC0000049 | 試圖在未對應映像的區段中查詢映像資訊。 |
An attempt was made to query image information on a section which does not map an image. |
| 0xC000004A | 嘗試暫停執行緒，它的暫停計數達最大值。 |
An attempt was made to suspend a thread whose suspend count was at its maximum. |
| 0xC000004B | 試圖存取已開始終止的執行緒。 |
An attempt was made to access a thread that has begun termination. |
| 0xC000004C | 試圖設定不正確的工作組限制值 (如最小值大於最大值)。 |
An attempt was made to set the working set limit to an invalid value (minimum greater than maximum, etc). |
| 0xC000004D | 建立對應檔案的區段不相容於已存在且對應同一檔案的區段。 |
A section was created to map a file which is not compatible to an already existing section which maps the same file. |
| 0xC000004E | 檢視區段指定保護，但這個保護與初始檢視保護不相容。 |
A view to a section specifies a protection which is incompatible with the initial view's protection. |
| 0xC000004F | 因檔案系統不支援 EA，導致操作的 EA 失敗。 |
An operation involving EAs failed because the file system does not support EAs. |
| 0xC0000050 | EA 操作失敗，因為 EA 組太大。 |
An EA operation failed because EA set is too large. |
| 0xC0000051 | EA 操作失敗，因為名稱或 EA 索引不正確。 |
An EA operation failed because the name or EA index is invalid. |
| 0xC0000052 | 要求 EA 的檔案中沒有 EA。 |
The file for which EAs were requested has no EAs. |
| 0xC0000053 | EA 已經損毀且無法讀取。 |
The EA is corrupt and non-readable. |
| 0xC0000054 | 因檔案鎖定衝突，而不允許讀取/寫入的要求。 |
A requested read/write cannot be granted due to a conflicting file lock. |
| 0xC0000055 | 因其他鎖定巳存在，而不允許檔案鎖定的要求。 |
A requested file lock cannot be granted due to other existing locks. |
| 0xC0000056 | 對擱置刪除檔案物件要求一項未關閉的操作。 |
A non close operation has been requested of a file object with a delete pending. |
| 0xC0000057 | 試圖設定檔案的控制屬性。目標檔案系統未支援該屬性。 |
An attempt was made to set the control attribute on a file. This attribute is not supported in the target file system. |
| 0xC0000058 | 表示已遭遇或指定一服務未知的修訂編號。可能超過該服務所知的最近修訂。 |
Indicates a revision number encountered or specified is not one known by the service. It may be a more recent revision than the service is aware of. |
| 0xC0000059 | 標示兩個修正層級不相容。 |
Indicates two revision levels are incompatible. |
| 0xC000005A | 表示某一特定的安全性識別碼可能無法指定為一物件的擁有者。 |
Indicates a particular Security ID may not be assigned as the owner of an object. |
| 0xC000005B | 表示某一特定的安全性識別碼可能無法指定為一物件的主群組。 |
Indicates a particular Security ID may not be assigned as the primary group of an object. |
| 0xC000005C | 嘗試用執行緒對模擬權杖進行操作，這個執行緒目前不是模擬用戶端。 |
An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client. |
| 0xC000005D | 可能無法取消強制群組。 |
A mandatory group may not be disabled. |
| 0xC000005E | 因為您的網域無法使用，所以您無法使用此認證登入。請確定裝置已連線到組織網路後，再試一次。如果您先前使用另一個認證登入此裝置，則可以使用該認證登入。 |
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. |
| 0xC000005F | 指定的登入工作階段不存在。可能已被終止。 |
A specified logon session does not exist. It may already have been terminated. |
| 0xC0000060 | 指定的特殊權限不存在。 |
A specified privilege does not exist. |
| 0xC0000061 | 用戶端沒有這項特殊權限。 |
A required privilege is not held by the client. |
| 0xC0000062 | 提供的名稱並非適當的帳戶名稱形式。 |
The name provided is not a properly formed account name. |
| 0xC0000063 | 指定的帳戶已存在。 |
The specified account already exists. |
| 0xC0000064 | 指定的帳戶不存在。 |
The specified account does not exist. |
| 0xC0000065 | 指定的群組已存在。 |
The specified group already exists. |
| 0xC0000066 | 指定的群組不存在。 |
The specified group does not exist. |
| 0xC0000067 | 指定的使用者帳戶已經在指定的群組帳戶中。也用來表示群組無法刪除，因為它含有一個成員。 |
The specified user account is already in the specified group account. Also used to indicate a group cannot be deleted because it contains a member. |
| 0xC0000068 | 指定的使用者帳戶不是指定群組帳戶的成員。 |
The specified user account is not a member of the specified group account. |
| 0xC0000069 | 指出要求的操作會停用或刪除系統管理帳戶，或造成系統管理帳戶無法登入。不會允許此操作，以免發生無法管理系統的情況。 |
Indicates the requested operation would disable, delete or could prevent logon for an administration account.This is not allowed to prevent creating a situation in which the system cannot be administrated. |
| 0xC000006A | 當試圖更新密碼時，這個傳回狀態表示所提供的目前密碼數值不正確。 |
When trying to update a password, this return status indicates that the value provided as the current password is not correct. |
| 0xC000006B | 當試圖更新密碼時，本傳回狀態表示所提供的新密碼中包含不被允許的值。 |
When trying to update a password, this return status indicates that the value provided for the new password contains values that are not allowed in passwords. |
| 0xC000006C | 當試圖更新密碼時，本狀態表示已違反某些密碼更新原則。例如，密碼不符合長度標準。 |
When trying to update a password, this status indicates that some password update rule has been violated. For example, the password may not meet length criteria. |
| 0xC000006D | 試圖登入不正確。可能是因為不正確的使用者名稱或驗證資訊。 |
The attempted logon is invalid. This is either due to a bad username or authentication information. |
| 0xC000006E | 表示一參考的使用者名稱及驗證資訊不正確，但某些使用者帳戶限制已確認成功 (日期時間限制)。 |
Indicates a referenced user name and authentication information are valid, but some user account restriction has prevented successful authentication (such as time-of-day restrictions). |
| 0xC000006F | 使用者帳戶設有時間限制，不可在此期間內登入。 |
The user account has time restrictions and may not be logged onto at this time. |
| 0xC0000070 | 使用者帳戶設有時間限制，無法從來源工作站登入。 |
The user account is restricted such that it may not be used to log on from the source workstation. |
| 0xC0000071 | 使用者帳戶的密碼已到期。 |
The user account's password has expired. |
| 0xC0000072 | 參考帳戶目前已停用且無法登入。 |
The referenced account is currently disabled and may not be logged on to. |
| 0xC0000073 | 尚未解釋任何該解釋的資訊。 |
None of the information to be translated has been translated. |
| 0xC0000074 | LUID 請求的數量無法以單一配置單位來配置。 |
The number of LUIDs requested may not be allocated with a single allocation. |
| 0xC0000075 | 表示不需要再配置任何的 LUID。 |
Indicates there are no more LUIDs to allocate. |
| 0xC0000076 | 表示特定用途的子授權值不正確。 |
Indicates the sub-authority value is invalid for the particular use. |
| 0xC0000077 | 表示 ACL 結構不正確。 |
Indicates the ACL structure is not valid. |
| 0xC0000078 | 表示 SID 結構不正確。 |
Indicates the SID structure is not valid. |
| 0xC0000079 | 表示 SECURITY_DESCRIPTOR 結構不正確。 |
Indicates the SECURITY_DESCRIPTOR structure is not valid. |
| 0xC000007A | 表示無法在 DLL 中找到指定的程序位址。 |
Indicates the specified procedure address cannot be found in the DLL. |
| 0xC000007B | {映像錯誤}可能是 %hs 並非設計為在 Windows 上執行，或它包含錯誤。請嘗試使用原始安裝媒體再次安裝該程式，或連絡您的系統管理員或軟體廠商以取得支援。錯誤狀態 0x%08lx。 |
{Bad Image}%hs is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0x%08lx. |
| 0xC000007C | 嘗試參照不存在的語法。尤其是參照與不模擬用戶端的執行緒有關的語法。 |
An attempt was made to reference a token that doesn't exist.This is typically done by referencing the token associated with a thread when the thread is not impersonating a client. |
| 0xC000007D | 指出一個嘗試建立繼承的 ACL 或 ACE 不成功。可能原因有幾個。比較可能的原因是因為以不符合 ACE 或 ACL 的 SID 取代了 CreatorId。 |
Indicates that an attempt to build either an inherited ACL or ACE was not successful.This can be caused by a number of things. One of the more probable causes is the replacement of a CreatorId with an SID that didn't fit into the ACE or ACL. |
| 0xC000007E | 無法鎖定在 NtUnlockFile 指定的範圍。 |
The range specified in NtUnlockFile was not locked. |
| 0xC000007F | 操作失敗，因為磁碟空間已滿。若這是精簡佈建的磁碟區，則表示支援此磁碟區的實體存放裝置已耗盡。 |
An operation failed because the disk was full.If this is a thinly provisioned volume the physical storage backing this volume has been exhausted. |
| 0xC0000080 | GUID 配置伺服器此時已停用。 |
The GUID allocation server is [already] disabled at the moment. |
| 0xC0000081 | GUID 配置伺服器此時已啟用。 |
The GUID allocation server is [already] enabled at the moment. |
| 0xC0000082 | 一次從配置伺服器請求太多的 GUID。 |
Too many GUIDs were requested from the allocation server at once. |
| 0xC0000083 | 因 [授權代理程式] 已用盡而無法配置 GUID。 |
The GUIDs could not be allocated because the Authority Agent was exhausted. |
| 0xC0000084 | 提供給識別元的授權值不正確。 |
The value provided was an invalid value for an identifier authority. |
| 0xC0000085 | 指定的識別元授權值中無任何可用的授權代理程式值。 |
There are no more authority agent values available for the given identifier authority value. |
| 0xC0000086 | 指定的磁碟區標籤不正確。 |
An invalid volume label has been specified. |
| 0xC0000087 | 無法延伸對應區段。 |
A mapped section could not be extended. |
| 0xC0000088 | 指定要排清的區段未對應至資料檔案。 |
Specified section to flush does not map a data file. |
| 0xC0000089 | 表示指定的映像檔不包含資源區段。 |
Indicates the specified image file did not contain a resource section. |
| 0xC000008A | 表示在映像檔中找不到指定的資源類型。 |
Indicates the specified resource type cannot be found in the image file. |
| 0xC000008B | 表示在映像檔中找不到指定的資源名稱。 |
Indicates the specified resource name cannot be found in the image file. |
| 0xC000008C | {例外}超出陣列範圍。 |
{EXCEPTION}Array bounds exceeded. |
| 0xC000008D | {例外}浮點運算 denormal 運算元。 |
{EXCEPTION}Floating-point denormal operand. |
| 0xC000008E | {例外}浮點運算除以 0。 |
{EXCEPTION}Floating-point division by zero. |
| 0xC000008F | {例外}浮點運算結果不精確。 |
{EXCEPTION}Floating-point inexact result. |
| 0xC0000090 | {例外}浮點運算操作不正確。 |
{EXCEPTION}Floating-point invalid operation. |
| 0xC0000091 | {例外}浮點溢位。 |
{EXCEPTION}Floating-point overflow. |
| 0xC0000092 | {例外}浮點堆疊檢查。 |
{EXCEPTION}Floating-point stack check. |
| 0xC0000093 | {例外}浮點反向溢位。 |
{EXCEPTION}Floating-point underflow. |
| 0xC0000094 | {例外}整數除以 0。 |
{EXCEPTION}Integer division by zero. |
| 0xC0000095 | {例外}整數溢位。 |
{EXCEPTION}Integer overflow. |
| 0xC0000096 | {例外}特殊權限指令。 |
{EXCEPTION}Privileged instruction. |
| 0xC0000097 | 試圖安裝超過系統支援的分頁檔數。 |
An attempt was made to install more paging files than the system supports. |
| 0xC0000098 | 檔案所在的磁碟區已被外部改變，因此開啟的檔案不再有效。 |
The volume for a file has been externally altered such that the opened file is no longer valid. |
| 0xC0000099 | 當記憶體區塊分配給未來的變更時，例如:用來保留判別存取控制及主要群組帳戶資訊的記憶體配置。成功變更的項目可能會超過記憶體原始分配總數。因為配額可能已經分配到數個擁有物件代碼的處理程序，再變更記憶體大小配置不是一個適當的動作。所以若有一個需要額外記憶體配置的要求，一定會發生失敗，並且 STATUS_ALLOTED_SPACE_EXCEEDED 會傳回錯誤值。 |
When a block of memory is allotted for future updates, such as the memory allocated to hold discretionary access control and primary group information, successive updates may exceed the amount of memory originally allotted.Since quota may already have been charged to several processes which have handles to the object, it is not reasonable to alter the size of the allocated memory.Instead, a request that requires more memory than has been allotted must fail and the STATUS_ALLOTED_SPACE_EXCEEDED error returned. |
| 0xC000009A | 系統資源不足，無法完成 API。 |
Insufficient system resources exist to complete the API. |
| 0xC000009B | 已嘗試開啟 DFS 結束路徑控制檔案。 |
An attempt has been made to open a DFS exit path control file. |
| 0xC000009C | STATUS_DEVICE_DATA_ERROR |
STATUS_DEVICE_DATA_ERROR |
| 0xC000009D | STATUS_DEVICE_NOT_CONNECTED |
STATUS_DEVICE_NOT_CONNECTED |
| 0xC000009E | STATUS_DEVICE_POWER_FAILURE |
STATUS_DEVICE_POWER_FAILURE |
| 0xC000009F | 當起始位址不是區域的起始位址，且已指定 0 的區域大小時，將無法釋放虛擬記憶體。 |
Virtual memory cannot be freed as base address is not the base of the region and a region size of zero was specified. |
| 0xC00000A0 | 試圖釋放未配置的虛擬記憶體。 |
An attempt was made to free virtual memory which is not allocated. |
| 0xC00000A1 | 工作組大小不足，無法允許要求的分頁鎖定。 |
The working set is not big enough to allow the requested pages to be locked. |
| 0xC00000A2 | {寫入保護錯誤}因磁片有防寫保護而無法寫入該磁片。請將磁碟機 %hs 中的磁碟區 %hs 之防寫保護移除。 |
{Write Protect Error}The disk cannot be written to because it is write protected. Please remove the write protection from the volume %hs in drive %hs. |
| 0xC00000A3 | {磁碟機未備妥}磁碟機未備妥; 可能未關上磁碟門。請檢查磁碟機 %hs 並確定已插入磁片及關上磁碟機門。 |
{Drive Not Ready}The drive is not ready for use; its door may be open. Please check drive %hs and make sure that a disk is inserted and that the drive door is closed. |
| 0xC00000A4 | 指定的屬性不正確，或與整個群組的屬性不相容。 |
The specified attributes are invalid, or incompatible with the attributes for the group as a whole. |
| 0xC00000A5 | 指定的模擬層級不正確。同時也表示未提供所請求的模擬層級。 |
A specified impersonation level is invalid.Also used to indicate a required impersonation level was not provided. |
| 0xC00000A6 | 試圖開啟一匿名層權杖。匿名層權杖可能無法開啟。 |
An attempt was made to open an Anonymous level token.Anonymous tokens may not be opened. |
| 0xC00000A7 | 要求的確認資訊類別不正確。 |
The validation information class requested was invalid. |
| 0xC00000A8 | 權杖物件類型無法與其用途相配合。 |
The type of a token object is inappropriate for its attempted use. |
| 0xC00000AA | 試圖在未配置的位址上執行指令，且主機系統不支援未配置的指令參考。 |
An attempt was made to execute an instruction at an unaligned address and the host system does not support unaligned instruction references. |
| 0xC00000AB | 已達到具名管道例項計數的最大值。 |
The maximum named pipe instance count has been reached. |
| 0xC00000AC | 在聽候狀態下找不到具名管道例項。 |
An instance of a named pipe cannot be found in the listening state. |
| 0xC00000AD | 具名管道不在連線或關閉狀態。 |
The named pipe is not in the connected or closing state. |
| 0xC00000AE | 指定的管道設定要完成操作，但目前已有 I/O 操作在佇列中，所以無法將它變更為佇列操作。 |
The specified pipe is set to complete operations and there are current I/O operations queued so it cannot be changed to queue operations. |
| 0xC00000AF | 指定的控制代碼並未開啟給伺服器端的具名管道。 |
The specified handle is not open to the server end of the named pipe. |
| 0xC00000B0 | 指定的具名管道處於中斷連線狀態。 |
The specified named pipe is in the disconnected state. |
| 0xC00000B1 | 指定的具名管道處於關閉狀態。 |
The specified named pipe is in the closing state. |
| 0xC00000B2 | 指定的具名管道處於連線狀態。 |
The specified named pipe is in the connected state. |
| 0xC00000B3 | 指定的具名管道處於聽候狀態。 |
The specified named pipe is in the listening state. |
| 0xC00000B4 | 指定的具名管道不在訊息模式。 |
The specified named pipe is not in message mode. |
| 0xC00000B5 | {裝置等候逾時}在 %hs 指定的 I/O 操作無法在等候逾時之前完成操作。 |
{Device Timeout}The specified I/O operation on %hs was not completed before the time-out period expired. |
| 0xC00000B6 | 指定的檔案已被另一個處理程序關閉。 |
The specified file has been closed by another process. |
| 0xC00000B7 | 未啟動分析。 |
Profiling not started. |
| 0xC00000B8 | 未停止分析。 |
Profiling not stopped. |
| 0xC00000B9 | 傳遞出的 ACL 並未包含所需的最少資訊。 |
The passed ACL did not contain the minimum required information. |
| 0xC00000BA | 指定的目標檔案是個目錄，但呼叫者指定其為目錄之外的任何目標。 |
The file that was specified as a target is a directory and the caller specified that it could be anything but a directory. |
| 0xC00000BB | 不支援這個要求。 |
The request is not supported. |
| 0xC00000BC | 遠端電腦不在聽候狀態。 |
This remote computer is not listening. |
| 0xC00000BD | 網路上有重複的名稱。 |
A duplicate name exists on the network. |
| 0xC00000BE | 無法找到網路路徑。 |
The network path cannot be located. |
| 0xC00000BF | 網路忙碌中。 |
The network is busy. |
| 0xC00000C0 | 裝置不存在。 |
This device does not exist. |
| 0xC00000C1 | 已達網路 BIOS 命令限制。 |
The network BIOS command limit has been reached. |
| 0xC00000C2 | 發生 I/O 介面卡硬體錯誤。 |
An I/O adapter hardware error has occurred. |
| 0xC00000C3 | 網路回應不正確。 |
The network responded incorrectly. |
| 0xC00000C4 | 發生意外的網路錯誤。 |
An unexpected network error occurred. |
| 0xC00000C5 | 遠端介面卡不相容。 |
The remote adapter is not compatible. |
| 0xC00000C6 | 印表機佇列已滿。 |
The printer queue is full. |
| 0xC00000C7 | 無法在伺服器上取得儲存等待列印檔案的空間。 |
Space to store the file waiting to be printed is not available on the server. |
| 0xC00000C8 | 已取消要求列印的檔案。 |
The requested print file has been canceled. |
| 0xC00000C9 | 網路名稱已刪除。 |
The network name was deleted. |
| 0xC00000CA | 網路存取被拒。 |
Network access is denied. |
| 0xC00000CB | {不正確的網路資源類型}指定的裝置類型 (如 LPT) 與遠端資源上的實際裝置類型衝突。 |
{Incorrect Network Resource Type}The specified device type (LPT, for example) conflicts with the actual device type on the remote resource. |
| 0xC00000CC | {無法取得網路名稱}無法在遠端伺服器上找到共用名稱。 |
{Network Name Not Found}The specified share name cannot be found on the remote server. |
| 0xC00000CD | 超過本機電腦網路介面卡的名稱限制。 |
The name limit for the local computer network adapter card was exceeded. |
| 0xC00000CE | 超過網路 BIOS 工作階段限制。 |
The network BIOS session limit was exceeded. |
| 0xC00000CF | 已暫停檔案共用。 |
File sharing has been temporarily paused. |
| 0xC00000D0 | 目前已無法再連線到這台遠端電腦，因為已達到電腦的連線數目極限。 |
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. |
| 0xC00000D1 | 已暫停印表機或磁碟重新導向。 |
Print or disk redirection is temporarily paused. |
| 0xC00000D2 | 發生網路資料錯誤。 |
A network data fault occurred. |
| 0xC00000D3 | 使用中分析物件的數量已到達最大值且無法啟動任一物件。 |
The number of active profiling objects is at the maximum and no more may be started. |
| 0xC00000D4 | {不正確的磁碟區}重新命名要求的目標檔案位於與重新命名要求之來源不同的裝置。 |
{Incorrect Volume}The target file of a rename request is located on a different device than the source of the rename request. |
| 0xC00000D5 | 指定的檔案已重新命名，因此無法修改。 |
The file specified has been renamed and thus cannot be modified. |
| 0xC00000D6 | {網路請求等候逾時}因已到達要求的等候逾時間隔而切斷遠端伺服器的工作階段。 |
{Network Request Timeout}The session with a remote server has been disconnected because the time-out interval for a request has expired. |
| 0xC00000D7 | 表示試圖在沒有設定安全性關聯的物件上執行操作。 |
Indicates an attempt was made to operate on the security of an object that does not have security associated with it. |
| 0xC00000D8 | 用來表示 I/O 沒有區塊化時，就無法繼續操作。 |
Used to indicate that an operation cannot continue without blocking for I/O. |
| 0xC00000D9 | 用以表示已執行空管道中的讀取操作。 |
Used to indicate that a read operation was done on an empty pipe. |
| 0xC00000DA | 無法從網域控制站讀取設定資訊，可能是電腦無法使用，或是存取被拒絕。 |
Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied. |
| 0xC00000DB | 表示有一執行緒試圖依預設值終止其本身 (以 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. |
| 0xC00000DC | 表示 Sam 伺服器處於執行操作的錯誤狀態。 |
Indicates the Sam Server was in the wrong state to perform the desired operation. |
| 0xC00000DD | 表示網域處於執行操作的錯誤狀態。 |
Indicates the Domain was in the wrong state to perform the desired operation. |
| 0xC00000DE | 這項操作只能在網域的網域主控站上執行。 |
This operation is only allowed for the Primary Domain Controller of the domain. |
| 0xC00000DF | 指定的網域不存在。 |
The specified Domain did not exist. |
| 0xC00000E0 | 指定的網域已存在。 |
The specified Domain already exists. |
| 0xC00000E1 | 嘗試超出此版本的每一伺服器的網域數目限制。 |
An attempt was made to exceed the limit on the number of domains per server for this release. |
| 0xC00000E2 | 當 oplock 要求被拒絕時傳回錯誤的狀態。 |
Error status returned when oplock request is denied. |
| 0xC00000E3 | 當檔案系統接收不正確的 oplock 聲言時，傳回錯誤的狀態。 |
Error status returned when an invalid oplock acknowledgment is received by a file system. |
| 0xC00000E4 | 這個錯誤表示要求的操作無法完成，原因是嚴重的媒體失效或磁碟上的資料架構損毀。 |
This error indicates that the requested operation cannot be completed due to a catastrophic media failure or on-disk data structure corruption. |
| 0xC00000E5 | 發生內部錯誤。 |
An internal error occurred. |
| 0xC00000E6 | 表示包含在存取遮罩中的一般存取類型已經對應到非一般存取類型了。 |
Indicates generic access types were contained in an access mask which should already be mapped to non-generic access types. |
| 0xC00000E7 | 表示不須設定安全性描述元的特定格式 (絕對或自我相對)。 |
Indicates a security descriptor is not in the necessary format (absolute or self-relative). |
| 0xC00000E8 | 在「預期」的時間點上存取使用者緩衝區失敗。當呼叫者不接受其篩選器中的 STATUS_ACCESS_VIOLATION 時即定義本代碼。 |
An access to a user buffer failed at an \"expected\" point in time. This code is defined since the caller does not want to accept STATUS_ACCESS_VIOLATION in its filter. |
| 0xC00000E9 | 如果傳回的 I/O 錯誤值不是定義在標準 FsRtl 篩選器中，它會被轉換成下列保證在篩選器中的錯誤值。在這個狀況下，資訊會遺失，但篩選器可以正確處理意外狀況。 |
If an I/O error is returned which is not defined in the standard FsRtl filter, it is converted to the following error which is guaranteed to be in the filter. In this case information is lost, however, the filter correctly handles the exception. |
| 0xC00000EA | 如果傳回的 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. |
| 0xC00000ED | 這項要求動作只能用在登入程序。所呼叫的程序並未登錄為登入程序。 |
The requested action is restricted for use by logon processes only. The calling process has not registered as a logon process. |
| 0xC00000EE | 嘗試啟動新的工作階段管理員，或以一個正在使用的識別碼啟動 LSA 登入工作階段。 |
An attempt has been made to start a new session manager or LSA logon session with an ID that is already in use. |
| 0xC00000EF | 不正確的參數傳遞給服務或函數，作為第一個引數。 |
An invalid parameter was passed to a service or function as the first argument. |
| 0xC00000F0 | 不正確的參數傳遞給服務或函數，作為第二個引數。 |
An invalid parameter was passed to a service or function as the second argument. |
| 0xC00000F1 | 不正確的參數傳遞給服務或函數，作為第三個引數。 |
An invalid parameter was passed to a service or function as the third argument. |
| 0xC00000F2 | 不正確的參數傳遞給服務或函數，作為第四個引數。 |
An invalid parameter was passed to a service or function as the fourth argument. |
| 0xC00000F3 | 不正確的參數傳遞給服務或函數，作為第五個引數。 |
An invalid parameter was passed to a service or function as the fifth argument. |
| 0xC00000F4 | 不正確的參數傳遞給服務或函數，作為第六個引數。 |
An invalid parameter was passed to a service or function as the sixth argument. |
| 0xC00000F5 | 不正確的參數傳遞給服務或函數，作為第七個引數。 |
An invalid parameter was passed to a service or function as the seventh argument. |
| 0xC00000F6 | 不正確的參數傳遞給服務或函數，作為第八個引數。 |
An invalid parameter was passed to a service or function as the eighth argument. |
| 0xC00000F7 | 不正確的參數傳遞給服務或函數，作為第九個引數。 |
An invalid parameter was passed to a service or function as the ninth argument. |
| 0xC00000F8 | 不正確的參數傳遞給服務或函數，作為第十個引數。 |
An invalid parameter was passed to a service or function as the tenth argument. |
| 0xC00000F9 | 不正確的參數傳遞給服務或函數，作為第十一個引數。 |
An invalid parameter was passed to a service or function as the eleventh argument. |
| 0xC00000FA | 不正確的參數傳遞給服務或函數，作為第十二個引數。 |
An invalid parameter was passed to a service or function as the twelfth argument. |
| 0xC00000FB | 試圖存取一網路檔案，但網路軟體尚未啟動。 |
An attempt was made to access a network file, but the network software was not yet started. |
| 0xC00000FC | 試圖啟動一重新導向器，但它已啟動。 |
An attempt was made to start the redirector, but the redirector has already been started. |
| 0xC00000FD | 無法建立新的堆疊防護分頁。 |
A new guard page for the stack cannot be created. |
| 0xC00000FE | 指定的驗證封裝不明。 |
A specified authentication package is unknown. |
| 0xC00000FF | 在釋放操作時遇到形式錯誤的功能表格。 |
A malformed function table was encountered during an unwind operation. |
| 0xC0000100 | 表示無法在指定的環境區塊中找到指定的環境變數名稱。 |
Indicates the specified environment variable name was not found in the specified environment block. |
| 0xC0000101 | 這表示要刪除的目錄不是空的。 |
Indicates that the directory trying to be deleted is not empty. |
| 0xC0000102 | {毀損檔案}檔案或目錄 %hs 已毀損且無法讀取。請執行 Chkdsk 公用程式。 |
{Corrupt File}The file or directory %hs is corrupt and unreadable.Please run the Chkdsk utility. |
| 0xC0000103 | 要求的開啟檔案不是一個目錄。 |
A requested opened file is not a directory. |
| 0xC0000104 | 登入工作階段跟要求操作的狀態不一致。 |
The logon session is not in a state that is consistent with the requested operation. |
| 0xC0000105 | 發生內部 LSA 錯誤。驗證封裝要求建立登入工作階段，但指定的是現存的登入工作階段識別碼。 |
An internal LSA error has occurred. An authentication package has requested the creation of a Logon Session but the ID of an already existing Logon Session has been specified. |
| 0xC0000106 | 指定的名稱字串過長。 |
A specified name string is too long for its intended use. |
| 0xC0000107 | 使用者試圖強迫關閉已重新導向磁碟機上的檔案，但該磁碟機上仍有開啟的檔案，且使用者並未指定一足夠的關閉層級。 |
The user attempted to force close the files on a redirected drive, but there were opened files on the drive, and the user did not specify a sufficient level of force. |
| 0xC0000108 | 使用者試圖強迫關閉已重新導向磁碟機上的檔案，但該磁碟機上仍有開啟的目錄，且使用者並未指定一足夠的關閉層級。 |
The user attempted to force close the files on a redirected drive, but there were opened directories on the drive, and the user did not specify a sufficient level of force. |
| 0xC0000109 | RtlFindMessage 無法在訊息表資源中配置要求的訊息識別碼。 |
RtlFindMessage could not locate the requested message ID in the message table resource. |
| 0xC000010A | 嘗試存取現有的處理程序。 |
An attempt was made to access an exiting process. |
| 0xC000010B | 表示已提供不正確的值給要求的登入類型。 |
Indicates an invalid value has been provided for the LogonType requested. |
| 0xC000010C | 嘗試將保護設定指派給檔案系統的檔案或目錄，有一個可能由檔案系統所儲存的 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. |
| 0xC000010D | 表示嘗試以一尚未讀取的具名管道來執行模擬。 |
Indicates that an attempt has been made to impersonate via a named pipe that has not yet been read from. |
| 0xC000010E | 表示已載入指定的映像。 |
Indicates that the specified image is already loaded. |
| 0xC000010F | STATUS_ABIOS_NOT_PRESENT |
STATUS_ABIOS_NOT_PRESENT |
| 0xC0000110 | STATUS_ABIOS_LID_NOT_EXIST |
STATUS_ABIOS_LID_NOT_EXIST |
| 0xC0000111 | STATUS_ABIOS_LID_ALREADY_OWNED |
STATUS_ABIOS_LID_ALREADY_OWNED |
| 0xC0000112 | STATUS_ABIOS_NOT_LID_OWNER |
STATUS_ABIOS_NOT_LID_OWNER |
| 0xC0000113 | STATUS_ABIOS_INVALID_COMMAND |
STATUS_ABIOS_INVALID_COMMAND |
| 0xC0000114 | STATUS_ABIOS_INVALID_LID |
STATUS_ABIOS_INVALID_LID |
| 0xC0000115 | STATUS_ABIOS_SELECTOR_NOT_AVAILABLE |
STATUS_ABIOS_SELECTOR_NOT_AVAILABLE |
| 0xC0000116 | STATUS_ABIOS_INVALID_SELECTOR |
STATUS_ABIOS_INVALID_SELECTOR |
| 0xC0000117 | 表示嘗試變更一個沒有 LDT 處理程序的 LDT 大小。 |
Indicates that an attempt was made to change the size of the LDT for a process that has no LDT. |
| 0xC0000118 | 表示嘗試藉由設定 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. |
| 0xC0000119 | 這表示 LDT 資訊的啟動值不是選擇器大小的整數倍數。 |
Indicates that the starting value for the LDT information was not an integral multiple of the selector size. |
| 0xC000011A | 這表示使用者在試著設定 LDT 描述元時，提供不正確的描述元。 |
Indicates that the user supplied an invalid descriptor when trying to set up Ldt descriptors. |
| 0xC000011B | 指定的映像檔沒有正確的格式。它以 NE 格式出現。 |
The specified image file did not have the correct format. It appears to be NE format. |
| 0xC000011C | 指出登錄子目錄異動狀態與要求的操作不相容。例如，要求以進行中的異動來啟動新異動，或是要求套用到一個目前不在執行中的異動。 |
Indicates that the transaction state of a registry sub-tree is incompatible with the requested operation. For example, a request has been made to start a new transaction with one already in progress, or a request has been made to apply a transaction when one is not currently in progress. |
| 0xC000011D | 指出登錄異動確認動作已經發生錯誤。資料庫已處在一個不明，但可能不一致的狀態。登錄異動狀態為 COMMITTING。 |
Indicates an error has occurred during a registry transaction commit. The database has been left in an unknown, but probably inconsistent, state. The state of the registry transaction is left as COMMITTING. |
| 0xC000011E | 試圖將大小為 0 的檔案與最大大小指定為 0 來對應。 |
An attempt was made to map a file of size zero with the maximum size specified as zero. |
| 0xC000011F | 在遠端伺服器開啟過多的檔案。本項錯誤僅可由遠端磁碟機上的 Windows 重新導向器傳回。 |
Too many files are opened on a remote server.This error should only be returned by the Windows redirector on a remote drive. |
| 0xC0000120 | I/O 請求已取消。 |
The I/O request was canceled. |
| 0xC0000121 | 試圖移除一無法刪除的檔案或目錄。 |
An attempt has been made to remove a file or directory that cannot be deleted. |
| 0xC0000122 | 表示指定的遠端電腦名稱語法錯誤。 |
Indicates a name specified as a remote computer name is syntactically invalid. |
| 0xC0000123 | 在刪除檔案之後執行對該檔案除關閉以外的 I/O 請求，僅適用於未以 NtClose 關閉最後控制代碼的請求。 |
An I/O request other than close was performed on a file after it has been deleted, which can only happen to a request which did not complete before the last handle was closed via NtClose. |
| 0xC0000124 | 這表示試著在內建的 (特殊) SAM 帳戶上進行操作，而這帳戶與內建的帳戶不相容。例如，內建帳戶無法刪除。 |
Indicates an operation has been attempted on a built-in (special) SAM account which is incompatible with built-in accounts. For example, built-in accounts cannot be deleted. |
| 0xC0000125 | 可能無法在指定群組上執行要求的操作，因為它是內建特殊群組。 |
The operation requested may not be performed on the specified group because it is a built-in special group. |
| 0xC0000126 | 指定的使用者可能無法執行所要求的操作，因為它是內建特殊使用者。 |
The operation requested may not be performed on the specified user because it is a built-in special user. |
| 0xC0000127 | 這表示無法從群組中移除成員，因為該群組目前是此成員的主要群組。 |
Indicates a member cannot be removed from a group because the group is currently the member's primary group. |
| 0xC0000128 | 試圖以已關閉的檔案物件執行除關閉及其他特殊操作以外的 I/O 要求。 |
An I/O request other than close and several other special case operations was attempted using a file object that had already been closed. |
| 0xC0000129 | 表示想執行要求動作的程序中執行緒太多。例如，您只能在程序沒有執行緒或只有一個執行緒時指定主要權杖。 |
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. |
| 0xC000012A | 試圖在特定的程序中執行緒，但所指定的執行緒不在指定的程序中。 |
An attempt was made to operate on a thread within a specific process, but the thread specified is not in the process specified. |
| 0xC000012B | 試圖將權杖建立成主要權杖，但此權杖已在使用中。程序內一次只能有一個主要權杖。 |
An attempt was made to establish a token for use as a primary token but the token is already in use. A token can only be the primary token of one process at a time. |
| 0xC000012C | 超過分頁檔配額。 |
Page file quota was exceeded. |
| 0xC000012D | {虛擬記憶體用完}您的系統虛擬記憶體很低。要確保 Windows 正確執行，請增加您虛擬記憶體分頁檔的大小。需要其他資訊，請參考 [說明]。 |
{Out of Virtual Memory}Your system is low on virtual memory. To ensure that Windows runs properly, increase the size of your virtual memory paging file. For more information, see Help. |
| 0xC000012E | 指定的映像檔案格式不正確，可能為 LE 格式。 |
The specified image file did not have the correct format, it appears to be LE format. |
| 0xC000012F | 指定的映像檔案格式不正確，沒有初始 MZ。 |
The specified image file did not have the correct format, it did not have an initial MZ. |
| 0xC0000130 | 指定的映像檔案格式不正確，MZ 檔頭沒有適當的 e_lfarlc。 |
The specified image file did not have the correct format, it did not have a proper e_lfarlc in the MZ header. |
| 0xC0000131 | 指定的映像檔案格式不正確，它可能是 16 位元的 Windows 映像。 |
The specified image file did not have the correct format, it appears to be a 16-bit Windows image. |
| 0xC0000132 | 因在網域中執行的其他 Netlogon 服務與指定的角色衝突而無法啟動 Netlogon 服務。 |
The Netlogon service cannot start because another Netlogon service running in the domain conflicts with the specified role. |
| 0xC0000133 | 網域主控站的時間與備份網域控制站或成員伺服器上的時間相差太大。 |
The time at the Primary Domain Controller is different than the time at the Backup Domain Controller or member server by too large an amount. |
| 0xC0000134 | 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. |
| 0xC0000135 | 程式碼執行無法繼續，因為找不到 %hs。重新安裝程式或許可以修正此問題。 |
The code execution cannot proceed because %hs was not found. Reinstalling the program may fix this problem. |
| 0xC0000136 | 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. |
| 0xC0000137 | {特殊權限失敗}無法更改程序的 I/O 使用權限。 |
{Privilege Failed}The I/O permissions for the process could not be changed. |
| 0xC0000138 | {找不到 Ordinal}序數 %ld 無法在動態連結程式庫 %hs 上找到。 |
{Ordinal Not Found}The ordinal %ld could not be located in the dynamic link library %hs. |
| 0xC0000139 | {無法找到輸入點}無法找到程序輸入點 %hs (在動態連結程式庫 %hs)。 |
{Entry Point Not Found}The procedure entry point %hs could not be located in the dynamic link library %hs. |
| 0xC000013A | {使用 CTRL+C 結束應用程式}使用 CTRL+C 終止應用程式。 |
{Application Exit by CTRL+C}The application terminated as a result of a CTRL+C. |
| 0xC000013B | {關閉虛擬網路}您的電腦網路傳輸已關閉網路連線。原因可能為無法處理的 I/O 要求。 |
{Virtual Circuit Closed}The network transport on your computer has closed a network connection. There may or may not be I/O requests outstanding. |
| 0xC000013C | {關閉虛擬網路}遠端電腦的網路傳輸已關閉網路連線。原因可能為無法處理的 I/O 要求。 |
{Virtual Circuit Closed}The network transport on a remote computer has closed a network connection. There may or may not be I/O requests outstanding. |
| 0xC000013D | {遠端電腦資源不足}遠端電腦資源不足以完成網路要求。例如，遠端電腦可能沒有足夠的可用記憶體，無法完成這次要求。 |
{Insufficient Resources on Remote Computer}The remote computer has insufficient resources to complete the network request. For instance, there may not be enough memory available on the remote computer to carry out the request at this time. |
| 0xC000013E | {關閉虛擬網路}遠端電腦上的既有連線 (虛擬網路) 已中斷。可能是遠端電腦的網路軟體協定或網路硬體發生錯誤。 |
{Virtual Circuit Closed}An existing connection (virtual circuit) has been broken at the remote computer. There is probably something wrong with the network software protocol or the network hardware on the remote computer. |
| 0xC000013F | {關閉虛擬網路}遠端電腦的網路傳輸已關閉網路連線，因為遠端電腦的等候逾時過長。 |
{Virtual Circuit Closed}The network transport on your computer has closed a network connection because it had to wait too long for a response from the remote computer. |
| 0xC0000140 | 指定給傳輸的連線控制代碼不正確。 |
The connection handle given to the transport was invalid. |
| 0xC0000141 | 指定給傳輸位址的控制代碼不正確。 |
The address handle given to the transport was invalid. |
| 0xC0000142 | {DLL 初始化失敗}動態連結程式庫 %hs 初始失敗。程序異常終止。 |
{DLL Initialization Failed}Initialization of the dynamic link library %hs failed. The process is terminating abnormally. |
| 0xC0000143 | {系統檔案遺失}必要的系統檔案 %hs 損毀或遺失。 |
{Missing System File}The required system file %hs is bad or missing. |
| 0xC0000144 | {應用程式錯誤}應用程式發生例外狀況 %s (0x%08lx) 於位置 0x%p。 |
{Application Error}The exception %s (0x%08lx) occurred in the application at location 0x%p. |
| 0xC0000145 | {應用程式錯誤}應用程式無法正確啟動 (0x%lx)。請按一下 [確定] 關閉應用程式。 |
{Application Error}The application was unable to start correctly (0x%lx). Click OK to close the application. |
| 0xC0000146 | {無法建立分頁檔}建立分頁檔 %hs 失敗 (%lx)。而要求的檔案大小為 %ld。 |
{Unable to Create Paging File}The creation of the paging file %hs failed (%lx). The requested size was %ld. |
| 0xC0000147 | {未指定分頁檔}未在系統設定中指定分頁檔。 |
{No Paging File Specified}No paging file was specified in the system configuration. |
| 0xC0000148 | {不正確的系統呼叫層級}傳送一不正確的層級給指定的系統呼叫。 |
{Incorrect System Call Level}An invalid level was passed into the specified system call. |
| 0xC0000149 | {區域網路管理員伺服器的密碼不正確}您指定一不正確的 LAN Manager 2.x 或 MS-NET 伺服器密碼。 |
{Incorrect Password to LAN Manager Server}You specified an incorrect password to a LAN Manager 2.x or MS-NET server. |
| 0xC000014A | {例外}真實模式的應用程式發出浮點運算指令，而浮點運算硬體不存在。 |
{EXCEPTION}A real-mode application issued a floating-point instruction and floating-point hardware is not present. |
| 0xC000014B | 管道操作 I/O 失敗，因為管道的另一端已關閉。 |
The pipe operation has failed because the other end of the pipe has been closed. |
| 0xC000014C | {登錄損毀}包含登錄資料的檔案結構已損毀，或其中的檔案映像已損毀，或因為有其他複製檔案或記錄檔缺少或損毀，所以檔案無法修復。 |
{The Registry Is Corrupt}The structure of one of the files that contains Registry data is corrupt, or the image of the file in memory is corrupt, or the file could not be recovered because the alternate copy or log was absent or corrupt. |
| 0xC000014D | 根據登錄所進行的 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. |
| 0xC000014E | 這個事件配對同步處理操作必須使用指定執行緒的用戶端/伺服器事件配對物件來執行，但沒有事件配對物件與該執行緒關聯。 |
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. |
| 0xC000014F | 本磁碟區不包含已確認的檔案系統。請確定所有請求的檔案系統驅動程式已載入，且本磁碟區未損毀。 |
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 corrupt. |
| 0xC0000150 | 序列裝置並未成功初始。序列驅動程式將解除載入。 |
No serial device was successfully initialized. The serial driver will unload. |
| 0xC0000151 | 指定的本機群組不存在。 |
The specified local group does not exist. |
| 0xC0000152 | 指定的帳戶名稱不是群組的成員。 |
The specified account name is not a member of the group. |
| 0xC0000153 | 指定的帳戶名稱已是群組的成員。 |
The specified account name is already a member of the group. |
| 0xC0000154 | 指定的本機群組已存在。 |
The specified local group already exists. |
| 0xC0000155 | 請求的登入類型 (如互動式、網路使用者、服務使用者) 不為目的系統的本機安全性原則所允許。請詢問系統管理員以取得必須的登入類型允許。 |
A requested type of logon (e.g., Interactive, Network, Service) is not granted by the target system's local security policy.Please ask the system administrator to grant the necessary form of logon. |
| 0xC0000156 | 超過單一系統所能儲存的最大秘密數。秘密的長度及數量限制須依照美國國務院的出口管制。 |
The maximum number of secrets that may be stored in a single system has been exceeded. The length and number of secrets is limited to satisfy United States State Department export restrictions. |
| 0xC0000157 | 秘密的長度超過允許的最大長度。秘密的長度及數量限制，須依照美國國務院的出口管制。 |
The length of a secret exceeds the maximum length allowed. The length and number of secrets is limited to satisfy United States State Department export restrictions. |
| 0xC0000158 | 本機安全性授權 (LSA) 資料庫包含內部的不一致。 |
The Local Security Authority (LSA) database contains an internal inconsistency. |
| 0xC0000159 | 要求的操作無法於全螢幕模式下執行。 |
The requested operation cannot be performed in fullscreen mode. |
| 0xC000015A | 在登入嘗試過程中，使用者的資訊安全內容累積太多安全性識別碼。這是一個相當不尋常的狀況。請從一些通用或本機群組中移除使用者，來減少安全性識別碼的數目，以便併入資訊安全內容中。 |
During a logon attempt, the user's security context accumulated too many security IDs. This is a very unusual situation. Remove the user from some global or local groups to reduce the number of security ids to incorporate into the security context. |
| 0xC000015B | 使用者要求一種不被許可的登入類型 (例如，互動或網路)。系統管理員可控制何人可以用互動式登入，及經由網路登入。 |
A user has requested a type of logon (e.g., interactive or network) that has not been granted. An administrator has control over who may logon interactively and through the network. |
| 0xC000015C | 系統試圖在登錄中載入或還原檔案，而指定的檔案不是登錄檔的格式。 |
The system has attempted to load or restore a file into the registry, and the specified file is not in the format of a registry file. |
| 0xC000015D | 試圖更改安全性帳戶管理員中的使用者密碼而未提供必須的 Windows 交互編碼密碼。 |
An attempt was made to change a user password in the security account manager without providing the necessary Windows cross-encrypted password. |
| 0xC000015E | Windows Server 的組態不正確。 |
A Windows Server has an incorrect configuration. |
| 0xC000015F | 試圖以裝置控制直接存取容錯磁碟機的第二資訊備份，而該備份未存在於系統中。 |
An attempt was made to explicitly access the secondary copy of information via a device control to the Fault Tolerance driver and the secondary copy is not present in the system. |
| 0xC0000160 | 組態登錄節點顯示一磁碟機服務項目類型不正確且未包含必須的項目值。 |
A configuration registry node representing a driver service entry was ill-formed and did not contain required value entries. |
| 0xC0000161 | 遭遇不正確的字元。多位元組字元集必須包含一前導位元組且無結尾位元組。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. |
| 0xC0000162 | 在多位元組的目的字碼頁中，沒有這個 Unicode 字元可以對應到的字元。 |
No mapping for the Unicode character exists in the target multi-byte code page. |
| 0xC0000163 | 本 Unicode 字元未定義在系統安裝的 Unicode 字元集。 |
The Unicode character is not defined in the Unicode character set installed on the system. |
| 0xC0000164 | 無法在磁片中建立分頁檔。 |
The paging file cannot be created on a floppy diskette. |
| 0xC0000165 | {軟式磁碟機錯誤}存取軟式磁碟機時無法找到識別碼位址標記。 |
{Floppy Disk Error}While accessing a floppy disk, an ID address mark was not found. |
| 0xC0000166 | {磁碟片錯誤}存取磁碟片時，磁區識別碼的磁軌位址失敗且不同於控制卡上所記錄的磁軌位址。 |
{Floppy Disk Error}While accessing a floppy disk, the track address from the sector ID field was found to be different than the track address maintained by the controller. |
| 0xC0000167 | {磁碟片錯誤}軟碟機控制器報告一軟式磁碟機驅動程式無法識別的錯誤。 |
{Floppy Disk Error}The floppy disk controller reported an error that is not recognized by the floppy disk driver. |
| 0xC0000168 | {磁碟片錯誤}存取磁碟片時，控制器經由其暫存器傳回不一致的結果。 |
{Floppy Disk Error}While accessing a floppy-disk, the controller returned inconsistent results via its registers. |
| 0xC0000169 | {硬式磁碟機錯誤}存取硬式磁碟機時，重新校準操作失敗，重試後仍舊失敗。 |
{Hard Disk Error}While accessing the hard disk, a recalibrate operation failed, even after retries. |
| 0xC000016A | {硬式磁碟機錯誤}存取硬式磁碟機時，磁碟操作重試失敗。 |
{Hard Disk Error}While accessing the hard disk, a disk operation failed even after retries. |
| 0xC000016B | {硬碟錯誤}存取硬磁時，重設磁碟控制卡失敗。 |
{Hard Disk Error}While accessing the hard disk, a disk controller reset was needed, but even that failed. |
| 0xC000016C | 嘗試開啟裝置，這個裝置與其他裝置共用一個 IRQ。至少有一個其他裝置使用已開啟的 IRQ。有兩個同時開啟的裝置共用一個 IRQ，而且只能透過插斷執行工作，它們不支援特別給裝置使用的匯流排類型。 |
An attempt was made to open a device that was sharing an IRQ with other devices.At least one other device that uses that IRQ was already opened.Two concurrent opens of devices that share an IRQ and only work via interrupts is not supported for the particular bus type that the devices use. |
| 0xC000016D | {FT 損壞}屬於一部分容錯磁碟區的磁碟機無法存取。 |
{FT Orphaning}A disk that is part of a fault-tolerant volume can no longer be accessed. |
| 0xC000016E | 系統 BIOS 無法將系統插斷連接到裝置，或裝置連接的匯流排。 |
The system bios failed to connect a system interrupt to the device or bus for which the device is connected. |
| 0xC0000172 | 無法分割磁帶。 |
Tape could not be partitioned. |
| 0xC0000173 | 當存取多重組合磁碟分割的新磁帶時，目前的區塊大小錯誤。 |
When accessing a new tape of a multivolume partition, the current blocksize is incorrect. |
| 0xC0000174 | 載入磁帶時，找不到磁帶磁碟分割資訊。 |
Tape partition information could not be found when loading a tape. |
| 0xC0000175 | 試圖鎖定退出媒體機制失敗。 |
Attempt to lock the eject media mechanism fails. |
| 0xC0000176 | 解除載入媒體失敗。 |
Unload media fails. |
| 0xC0000177 | 已偵測到磁帶的實體結尾。 |
Physical end of tape was detected. |
| 0xC0000178 | {沒有媒體}磁碟機中沒有媒體。請在磁碟機 %hs 中插入媒體。 |
{No Media}There is no media in the drive. Please insert media into drive %hs. |
| 0xC000017A | 無法將成員加入本機群組或從本機群組移除，因為成員不存在。 |
A member could not be added to or removed from the local group because the member does not exist. |
| 0xC000017B | 無法將新成員加入到本機群組中，因為成員的帳戶類型錯誤。 |
A new member could not be added to a local group because the member has the wrong account type. |
| 0xC000017C | 試圖在已標記為刪除的登錄機碼上執行無效的操作。 |
Illegal operation attempted on a registry key which has been marked for deletion. |
| 0xC000017D | 系統無法在登錄的記錄檔中配置必要的空間。 |
System could not allocate required space in a registry log. |
| 0xC000017E | 指定過多的 Sid。 |
Too many Sids have been specified. |
| 0xC000017F | 嘗試變更安全性帳戶管理員中的使用者密碼，但未提供必須的 LM 交互編碼密碼。 |
An attempt was made to change a user password in the security account manager without providing the necessary LM cross-encrypted password. |
| 0xC0000180 | 嘗試在一個已經有子機碼或數值的登錄機碼中建立符號連結。 |
An attempt was made to create a symbolic link in a registry key that already has subkeys or values. |
| 0xC0000181 | 嘗試在變動父系機碼下建立穩定子機碼。 |
An attempt was made to create a Stable subkey under a Volatile parent key. |
| 0xC0000182 | I/O 裝置的設定不正確或驅動程式配置不正確的設定參數。 |
The I/O device is configured incorrectly or the configuration parameters to the driver are incorrect. |
| 0xC0000183 | 於兩項驅動程式或一項 I/O 驅動程式間偵測到錯誤。 |
An error was detected between two drivers or within an I/O driver. |
| 0xC0000184 | 裝置未處於執行要求的有效狀態中。 |
The device is not in a valid state to perform this request. |
| 0xC0000185 | I/O 裝置報告一項 I/O 錯誤。 |
The I/O device reported an I/O error. |
| 0xC0000186 | 於驅動程式與裝置間偵測到錯誤。 |
A protocol error was detected between the driver and the device. |
| 0xC0000188 | 記錄檔案的空間不足，無法支援這項操作。 |
Log file space is insufficient to support this operation. |
| 0xC0000189 | 嘗試在卸載後的磁碟區執行寫入操作。 |
A write operation was attempted to a volume after it was dismounted. |
| 0xC000018A | 工作站在本機的 LSA 資料庫中沒有主要網域的信任秘密。 |
The workstation does not have a trust secret for the primary domain in the local LSA database. |
| 0xC000018B | Windows Server 上的 SAM 資料庫沒有此工作站信任關係的電腦帳戶。 |
The SAM database on the Windows Server does not have a computer account for this workstation trust relationship. |
| 0xC000018C | 因主要網域與受信任網域間的信任關係失敗而導致請求失敗。 |
The logon request failed because the trust relationship between the primary domain and the trusted domain failed. |
| 0xC000018D | 因工作站與主要網域間的信任關係失敗而導致請求失敗。 |
The logon request failed because the trust relationship between this workstation and the primary domain failed. |
| 0xC000018E | 事件記錄檔已經損毀。 |
The Eventlog log file is corrupt. |
| 0xC000018F | 無法開啟事件記錄檔。事件記錄檔服務未啟動。 |
No Eventlog log file could be opened. The Eventlog service did not start. |
| 0xC0000190 | 網路登入失敗。可能是因為無法聯繫驗證單位。 |
The network logon failed. This may be because the validation authority can't be reached. |
| 0xC0000191 | 嘗試取得一超過最大計數值的 semaphor。 |
An attempt was made to acquire a mutant such that its maximum count would have been exceeded. |
| 0xC0000192 | 嘗試登入，但尚未啟動 netlogon 服務。 |
An attempt was made to logon, but the netlogon service was not started. |
| 0xC0000193 | 使用者帳戶已到期。 |
The user's account has expired. |
| 0xC0000194 | {例外}可能的鎖死狀態。 |
{EXCEPTION}Possible deadlock condition. |
| 0xC0000195 | 不允許使用多於一個使用者名稱的相同使用者有多個連線到一個伺服器或共用資源。中斷所有之前到伺服器或共用資源的連線，然後再試。 |
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. |
| 0xC0000196 | 嘗試建立網路伺服器的工作階段，但已對該伺服器建立過多的工作階段。 |
An attempt was made to establish a session to a network server, but there are already too many sessions established to that server. |
| 0xC0000197 | 記錄檔案在讀取間已變更。 |
The log file has changed between reads. |
| 0xC0000198 | 使用的帳戶是網域間的信任帳戶。請使用您的通用使用者帳戶或本機使用者帳戶來存取此伺服器。 |
The account used is an Interdomain Trust account. Use your global user account or local user account to access this server. |
| 0xC0000199 | 使用的帳戶是電腦帳戶。請使用您的通用使用者帳戶或本機使用者帳戶來存取此伺服器。 |
The account used is a Computer Account. Use your global user account or local user account to access this server. |
| 0xC000019A | 使用的帳戶是伺服器信任帳戶。請使用您的通用使用者帳戶或本機使用者帳戶來存取此伺服器。 |
The account used is an Server Trust account. Use your global user account or local user account to access this server. |
| 0xC000019B | 指定網域的名稱或 SID 與該網域的信任資訊不一致。 |
The name or SID of the domain specified is inconsistent with the trust information for that domain. |
| 0xC000019C | 因為一個必要但尚未載入的檔案系統驅動程式，所以存取磁碟區。 |
A volume has been accessed for which a file system driver is required that has not yet been loaded. |
| 0xC000019D | 表示指定的映像已載入為 DLL。 |
Indicates that the specified image is already loaded as a DLL. |
| 0xC000019E | 由於全域登錄設定，可能不會變更這個磁碟區上的簡短名稱設定。 |
Short name settings may not be changed on this volume due to the global registry setting. |
| 0xC000019F | 未在這個磁碟區上啟用簡短名稱。 |
Short names are not enabled on this volume. |
| 0xC00001A0 | 所指定磁碟區的安全性資料流處於不一致狀態。請在磁碟區上執行 CHKDSK。 |
The security stream for the given volume is in an inconsistent state.Please run CHKDSK on the volume. |
| 0xC00001A1 | 無法處理要求的檔案鎖定操作，因為位元組範圍無效。 |
A requested file lock operation cannot be processed due to an invalid byte range. |
| 0xC00001A2 | {無效的 ACE 條件}指定的存取控制項目 (ACE) 包含無效的條件。 |
{Invalid ACE Condition}The specified access control entry (ACE) contains an invalid condition. |
| 0xC00001A3 | 支援映像類型所需的子系統不存在。 |
The subsystem needed to support the image type is not present. |
| 0xC00001A4 | {ACE 條件不正確}指定的檔案已經有相關的通知 GUID。 |
{Invalid ACE Condition}The specified file already has a notification GUID associated with it. |
| 0xC00001A5 | 偵測到無效的例外處理常式。 |
An invalid exception handler routine has been detected. |
| 0xC00001A6 | 指定給權杖的權限重複。 |
Duplicate privileges were specified for the token. |
| 0xC00001A7 | 不允許對檔案系統內部檔案執行要求的動作。 |
Requested action not allowed on a file system internal file. |
| 0xC00001A8 | 需要修復檔案系統的某個部分。 |
A portion of the file system requires repair. |
| 0xC00001A9 | 系統未啟用配額支援。 |
Quota support is not enabled on the system. |
| 0xC00001AA | 作業失敗，因為應用程式不是應用程式套件的一部分。 |
The operation failed because the application is not part of an application package. |
| 0xC00001AB | 已經在進行檔案中繼資料最佳化。 |
File metadata optimization is already in progress. |
| 0xC00001AC | 物件不相同。 |
The objects are not identical. |
| 0xC00001AD | 處理程序已終止，因為它無法配置額外的記憶體。 |
The process has terminated because it could not allocate additional memory. |
| 0xC00001AE | 處理程序不是工作的一部分。 |
The process is not part of a job. |
| 0xC00001AF | 指定的 CPU 設定識別碼無效。 |
The specified CPU Set IDs are invalid. |
| 0xC0000201 | 因為不符合網路開啟限制，所以遠端開啟失敗。 |
A remote open failed because the network open restrictions were not satisfied. |
| 0xC0000202 | 沒有提供使用者工作階段金鑰給指定的登入工作階段。 |
There is no user session key for the specified logon session. |
| 0xC0000203 | 已刪除遠端使用者工作階段。 |
The remote user session has been deleted. |
| 0xC0000204 | 表示在映像檔中找不到指定的資源語言識別碼。 |
Indicates the specified resource language ID cannot be found in theimage file. |
| 0xC0000205 | 伺服器資源不足無法完成要求。 |
Insufficient server resources exist to complete the request. |
| 0xC0000206 | 指定操作的緩衝區大小不正確。 |
The size of the buffer is invalid for the specified operation. |
| 0xC0000207 | 傳輸拒絕所指定的不正確網路位址。 |
The transport rejected the network address specified as invalid. |
| 0xC0000208 | 傳輸因不正確的萬用字元而拒絕所指定的網路位址。 |
The transport rejected the network address specified due to an invalid use of a wildcard. |
| 0xC0000209 | 因已使用所有的可用位址而無法開啟傳輸位址。 |
The transport address could not be opened because all the available addresses are in use. |
| 0xC000020A | 無法開啟已存在的傳輸位址。 |
The transport address could not be opened because it already exists. |
| 0xC000020B | 已關閉傳輸位址。 |
The transport address is now closed. |
| 0xC000020C | 傳輸連線已中斷。 |
The transport connection is now disconnected. |
| 0xC000020D | 已重設傳輸連線。 |
The transport connection has been reset. |
| 0xC000020E | 傳輸無法動態取得任何的節點。 |
The transport cannot dynamically acquire any more nodes. |
| 0xC000020F | 傳輸中止一擱置的異動。 |
The transport aborted a pending transaction. |
| 0xC0000210 | 傳輸已超過要求的回應等待時間。 |
The transport timed out a request waiting for a response. |
| 0xC0000211 | 傳輸並沒有接收到釋出的擱置回應。 |
The transport did not receive a release for a pending response. |
| 0xC0000212 | 傳輸未找到符合特定記號的異動。 |
The transport did not find a transaction matching the specific token. |
| 0xC0000213 | 傳輸先前已回應一異動要求。 |
The transport had previously responded to a transaction request. |
| 0xC0000214 | 傳輸無法識別指定的異動要求識別元。 |
The transport does not recognized the transaction request identifier specified. |
| 0xC0000215 | 傳輸無法識別指定的異動要求類型。 |
The transport does not recognize the transaction request type specified. |
| 0xC0000216 | 傳輸只能處理在工作階段中的伺服器端所指定的要求。 |
The transport can only process the specified request on the server side of a session. |
| 0xC0000217 | 傳輸只能處理在工作階段中的用戶端所指定的要求。 |
The transport can only process the specified request on the client side of a session. |
| 0xC0000218 | {登錄檔案失敗}登錄無法載入 hive 檔案:%hs或它的記錄檔或替代資料。檔案可能已經損毀、不存在或是無法寫入。 |
{Registry File Failure}The registry cannot load the hive (file):%hsor its log or alternate.It is corrupt, absent, or not writable. |
| 0xC0000219 | {意外錯誤 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. |
| 0xC000021A | {致命的系統錯誤}%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. |
| 0xC000021B | {無法接受資料}TDI 用戶端無法在指示的時間內處理接收的資料。 |
{Data Not Accepted}The TDI client could not handle the data received during an indication. |
| 0xC000021C | {無法抓取瀏覽伺服器清單}無法取得目前工作群組的伺服器清單。 |
{Unable to Retrieve Browser Server List}The list of servers for this workgroup is not currently available. |
| 0xC000021D | NTVDM 遭遇硬體錯誤。 |
NTVDM encountered a hard error. |
| 0xC000021E | {取消逾時值}驅動程式 %hs 無法在指定的時間內完成一已取消的 I/O 請求。 |
{Cancel Timeout}The driver %hs failed to complete a cancelled I/O request in the allotted time. |
| 0xC000021F | {回應訊息不符}嘗試回應一 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. |
| 0xC0000220 | {對應的檢視配置不正確}嘗試對應一檔案的檢視，但所指定的起始位址或檔案的偏移位址無法配置適當的間距。 |
{Mapped View Alignment Incorrect}An attempt was made to map a view of a file, but either the specified base address or the offset into the file were not aligned on the proper allocation granularity. |
| 0xC0000221 | {映像總和檢查碼不符}映像 %hs 可能已損毀。標題的總和檢查碼與所計算的總和檢查碼不符。 |
{Bad Image Checksum}The image %hs is possibly corrupt. The header checksum does not match the computed checksum. |
| 0xC0000222 | {延遲寫入失敗}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. |
| 0xC0000223 | 傳送給在用戶端/伺服器共用記憶體視窗中的伺服器參數不正確。共用記憶體視窗中可能放入過多的資料。 |
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. |
| 0xC0000224 | 登入之前必須先變更使用者的密碼。 |
The user's password must be changed before signing in. |
| 0xC0000225 | 找不到物件。 |
The object was not found. |
| 0xC0000226 | 這個資料流不是一個微小的資料流。 |
The stream is not a tiny stream. |
| 0xC0000227 | 交易還原失敗。 |
A transaction recover failed. |
| 0xC0000228 | 本要求必須由堆疊溢位代碼處理。 |
The request must be handled by the stack overflow code. |
| 0xC0000229 | 一致性檢查失敗。 |
A consistency check failed. |
| 0xC000022A | 索引中已有識別碼，所以嘗試在索引中插入識別碼時失敗。 |
The attempt to insert the ID in the index failed because the ID is already in the index. |
| 0xC000022B | 物件已有識別碼，所以嘗試設定該物件的識別碼時失敗。 |
The attempt to set the object's ID failed because the object already has an ID. |
| 0xC000022C | 內部 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. |
| 0xC000022D | 必須重試要求。 |
The request needs to be retried. |
| 0xC000022E | 嘗試尋找物件時，在磁碟區上找到符合識別碼的物件，但是它已經超出操作所使用的控制代碼領域。 |
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. |
| 0xC000022F | bucket 陣列必須增加。請在執行此工作後重新嘗試交易。 |
The bucket array must be grown. Retry transaction after doing so. |
| 0xC0000230 | 指定的內容組不存在於物件中。 |
The property set specified does not exist on the object. |
| 0xC0000231 | 使用者/核心排列緩衝區已經溢位。 |
The user/kernel marshalling buffer has overflowed. |
| 0xC0000232 | 提供的不同架構包含不正確的資料。 |
The supplied variant structure contains invalid data. |
| 0xC0000233 | 找不到這個網域的網域控制站。 |
Could not find a domain controller for this domain. |
| 0xC0000234 | 使用者帳戶已自動鎖定，因為不正確的登入次數過多，或密碼變更嘗試過多。 |
The user account has been automatically locked because too many invalid logon attempts or password change attempts have been requested. |
| 0xC0000235 | 由控制代碼所呼叫的 NtClose 已使用 NtSetInformationObject 以防止關閉。 |
NtClose was called on a handle that was protected from close via NtSetInformationObject. |
| 0xC0000236 | 遠端系統拒絕傳輸連線。 |
The transport connection attempt was refused by the remote system. |
| 0xC0000237 | 傳輸連線已順利關閉。 |
The transport connection was gracefully closed. |
| 0xC0000238 | 傳輸端點已有與其關聯的位址。 |
The transport endpoint already has an address associated with it. |
| 0xC0000239 | 尚未與傳輸端點產生關聯的位址。 |
An address has not yet been associated with the transport endpoint. |
| 0xC000023A | 嘗試在不存在的傳輸連線上執行一項操作。 |
An operation was attempted on a nonexistent transport connection. |
| 0xC000023B | 嘗試在使用中的傳輸連線上執行不正確的操作。 |
An invalid operation was attempted on an active transport connection. |
| 0xC000023C | 傳輸無法到達遠端網路。 |
The remote network is not reachable by the transport. |
| 0xC000023D | 傳輸無法到達遠端系統。 |
The remote system is not reachable by the transport. |
| 0xC000023E | 遠端系統不支援傳輸通訊協定。 |
The remote system does not support the transport protocol. |
| 0xC000023F | 在遠端系統的傳輸目的地連接埠上未執行任何服務。 |
No service is operating at the destination port of the transport on the remote system. |
| 0xC0000240 | 要求已經中止。 |
The request was aborted. |
| 0xC0000241 | 本機系統已中止傳輸連線。 |
The transport connection was aborted by the local system. |
| 0xC0000242 | 指定的緩衝區中包含錯誤類型的資料。 |
The specified buffer contains ill-formed data. |
| 0xC0000243 | 要求的操作無法在具有使用者對應區段開啟的檔案上執行。 |
The requested operation cannot be performed on a file with a user mapped section open. |
| 0xC0000244 | {稽核失敗}嘗試產生安全性稽核時發生失敗。 |
{Audit Failed}An attempt to generate a security audit failed. |
| 0xC0000245 | 目前的程序未設定計時器解析度。 |
The timer resolution was not previously set by the current process. |
| 0xC0000246 | 已達這個帳戶的最大連線數目，所以無法連接伺服器。 |
A connection to the server could not be made because the limit on the number of concurrent connections for this account has been reached. |
| 0xC0000247 | 嘗試在這個帳戶未被授權的時間內登入。 |
Attempting to login during an unauthorized time of day for this account. |
| 0xC0000248 | 這個帳戶並未得到從這個工作站登入的授權。 |
The account is not authorized to login from this station. |
| 0xC0000249 | {UP/MP 映像不相符}映像 %hs 為使用於單一處理器系統而做修改，不過您正在多個處理器的電腦上執行它。請重新安裝映像檔案。 |
{UP/MP Image Mismatch}The image %hs has been modified for use on a uniprocessor system, but you are running it on a multiprocessor machine.Please reinstall the image file. |
| 0xC0000250 | 帳戶資訊不足，無法讓您登入。 |
There is insufficient account information to log you on. |
| 0xC0000251 | {不正確的 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. |
| 0xC0000252 | {不正確的服務回呼進入點}%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. |
| 0xC0000253 | 伺服器接收到訊息，但是並未傳送回函。 |
The server received the messages but did not send a reply. |
| 0xC0000254 | 有一個 IP 位址與網路上的另一個系統衝突。 |
There is an IP address conflict with another system on the network |
| 0xC0000256 | {登錄檔空間不足}登錄檔內准許系統部分使用的空間已經達到最大值，將會略過其他的存放要求。 |
{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. |
| 0xC0000257 | 聯繫的伺服器不支援 DFS 命名空間中的指示部分。 |
The contacted server does not support the indicated part of the DFS namespace. |
| 0xC0000258 | 沒有使用中的回撥功能時，回撥系統服務就無法執行。 |
A callback return system service cannot be executed when no callback is active. |
| 0xC0000259 | 正在存取的服務有連線數目的限制。這時候已經無法讓他人連線，原因是已經到了可容許的連線數目上限。 |
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. |
| 0xC000025A | 提供的密碼太短，不符合使用者帳戶的原則要求。請輸入較長的密碼。 |
The password provided is too short to meet the policy of your user account. Please choose a longer password. |
| 0xC000025B | 您的使用者帳戶原則不允許太頻繁的密碼變更。這個是為了防止使用者所變更的密碼與上一個太相似，有被破解的潛在危險。如果您覺得您的密碼已經被盜用，請連絡您的系統管理員立即指定一個新密碼給你。 |
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. |
| 0xC000025C | 變更的密碼過去曾經用過。您的使用者帳戶原則不允許您這樣做，請選還沒有用過的密碼。 |
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. |
| 0xC000025E | 您想載入先前的裝置驅動程式，但是這個裝置例項已經被停用了。 |
You have attempted to load a legacy device driver while its device instance had been disabled. |
| 0xC000025F | 不支援指定的壓縮格式。 |
The specified compression format is unsupported. |
| 0xC0000260 | 指定的硬體設定檔組態不正確。 |
The specified hardware profile configuration is invalid. |
| 0xC0000261 | 指定的隨插即用登錄裝置路徑不正確。 |
The specified Plug and Play registry device path is invalid. |
| 0xC0000262 | {找不到驅動程式登入點}%hs 裝置驅動程式找不到序數 %ld 於驅動程式 %hs 中。 |
{Driver Entry Point Not Found}The %hs device driver could not locate the ordinal %ld in driver %hs. |
| 0xC0000263 | {找不到驅動程式登入點}%hs 裝置驅動程式找不到登入點 %hs 於驅動程式 %hs 中。 |
{Driver Entry Point Not Found}The %hs device driver could not locate the entry point %hs in driver %hs. |
| 0xC0000264 | {應用程式錯誤}應用程式嘗試釋放不是自已的資源。請按一下 [確定] 終止應用程式。 |
{Application Error}The application attempted to release a resource it did not own. Click OK to terminate the application. |
| 0xC0000265 | 嘗試建立比檔案系統所支援還多的檔案連結。 |
An attempt was made to create more links on a file than the file system supports. |
| 0xC0000266 | 指定的配額清單內部與其描述元不一致。 |
The specified quota list is internally inconsistent with its descriptor. |
| 0xC0000267 | 指定的檔案已被移到離線的存放區中。 |
The specified file has been relocated to offline storage. |
| 0xC0000268 | {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. |
| 0xC0000269 | {系統 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. |
| 0xC000026A | {違反產品使用權}系統已偵測到有人竄改您的登錄產品類型。這違反了您的軟體使用權。擅自竄改產品類型是不被充許的。 |
{License Violation}The system has detected tampering with your registered product type. This is a violation of your software license. Tampering with product type is not permitted. |
| 0xC000026B | {DLL 初始化失敗}應用程式無法初始，因為視窗工作站正在關機。 |
{DLL Initialization Failed}The application failed to initialize because the window station is shutting down. |
| 0xC000026C | {無法載入裝置驅動程式}%hs 裝置驅動程式無法載入。錯誤狀態為 0x%x |
{Unable to Load Device Driver}%hs device driver could not be loaded.Error Status was 0x%x |
| 0xC000026D | DFS 在連線的伺服器上無法使用。 |
DFS is unavailable on the contacted server. |
| 0xC000026E | 嘗試在磁碟區卸載後，執行操作。 |
An operation was attempted to a volume after it was dismounted. |
| 0xC000026F | Win32 x86 模擬子系統中，發生內部錯誤。 |
An internal error occurred in the Win32 x86 emulation subsystem. |
| 0xC0000270 | Win32 x86 模擬子系統浮點堆疊檢查。 |
Win32 x86 emulation subsystem Floating-point stack check. |
| 0xC0000271 | 確認處理程序需要繼續下一步。 |
The validation process needs to continue on to the next step. |
| 0xC0000272 | 在索引中找不到符合指定機碼的項目。 |
There was no match for the specified key in the index. |
| 0xC0000273 | 找不到目前索引列舉的項目。 |
There are no more matches for the current index enumeration. |
| 0xC0000275 | NTFS 檔案或目錄不是重新分析點。 |
The NTFS file or directory is not a reparse point. |
| 0xC0000276 | 通過的 Windows I/O 重新分析標記不正確，這個指標是給 NTFS 重新分析點的。 |
The Windows I/O reparse tag passed for the NTFS reparse point is invalid. |
| 0xC0000277 | Windows I/O 重新分析標記與目前在 NTFS 的重新分析點不符合。 |
The Windows I/O reparse tag does not match the one present in the NTFS reparse point. |
| 0xC0000278 | 通過的 NTFS 重新分析點的使用者資料不正確。 |
The user data passed for the NTFS reparse point is invalid. |
| 0xC0000279 | 在需要處理 IO 標記時，這個 IO 標記的分層檔案系統驅動程式並未處理它。 |
The layered file system driver for this IO tag did not handle it when needed. |
| 0xC000027A | 提供的密碼太長，不符合您的使用者帳戶原則。請選擇較短的密碼。 |
The password provided is too long to meet the policy of your user account. Please choose a shorter password. |
| 0xC000027B | 發生應用程式內部例外狀況。 |
An application-internal exception has occurred. |
| 0xC0000280 | 雖然起始檔案名稱正確，但無法解析 NTFS 符號連結。 |
The NTFS symbolic link could not be resolved even though the initial file name is valid. |
| 0xC0000281 | NTFS 目錄是一個重新分析點。 |
The NTFS directory is a reparse point. |
| 0xC0000282 | 範圍無法加入範圍清單，因為發生衝突。 |
The range could not be added to the range list because of a conflict. |
| 0xC0000283 | 指定的媒體變更來源元素中並未包含媒體。 |
The specified medium changer source element contains no media. |
| 0xC0000284 | 指定的媒體變更目的元素已經包含媒體。 |
The specified medium changer destination element already contains media. |
| 0xC0000285 | 指定的媒體變更元素不存在。 |
The specified medium changer element does not exist. |
| 0xC0000286 | 指定的元素包含在一個已經不存在的雜誌中。 |
The specified element is contained within a magazine that is no longer present. |
| 0xC0000287 | 裝置需要重新初始化，因為硬體發生錯誤。 |
The device requires reinitialization due to hardware errors. |
| 0xC000028A | 檔案加密嘗試失敗。 |
The file encryption attempt failed. |
| 0xC000028B | 檔案解密嘗試失敗。 |
The file decryption attempt failed. |
| 0xC000028C | 在範圍清單中找不到指定的範圍。 |
The specified range could not be found in the range list. |
| 0xC000028D | 這個系統中沒有加密修復的原則設定。 |
There is no encryption recovery policy configured for this system. |
| 0xC000028E | 必要的加密驅動程式並未載入系統中。 |
The required encryption driver is not loaded for this system. |
| 0xC000028F | 檔案加密所使用的加密驅動程式，與目前載入的加密驅動程式不同。 |
The file was encrypted with a different encryption driver than is currently loaded. |
| 0xC0000290 | 沒有為使用者定義 EFS 金鑰。 |
There are no EFS keys defined for the user. |
| 0xC0000291 | 指定的檔案並未加密。 |
The specified file is not encrypted. |
| 0xC0000292 | 指定的檔案不是定義的 EFS 匯出格式。 |
The specified file is not in the defined EFS export format. |
| 0xC0000293 | 指定的檔案已加密，而且使用者沒有能力解密。 |
The specified file is encrypted and the user does not have the ability to decrypt it. |
| 0xC0000295 | 無法辨識傳來的 guid 是否為有效的 WMI 資料提供者。 |
The guid passed was not recognized as valid by a WMI data provider. |
| 0xC0000296 | 無法辨識傳來的例項名稱是否為有效的 WMI 資料提供者。 |
The instance name passed was not recognized as valid by a WMI data provider. |
| 0xC0000297 | 無法辨識傳來的資料項目識別碼是否為有效的 WMI 資料提供者。 |
The data item id passed was not recognized as valid by a WMI data provider. |
| 0xC0000298 | 無法完成 WMI 要求，應該重試一次。 |
The WMI request could not be completed and should be retried. |
| 0xC0000299 | 原則物件已共用，而且可以只能在根目錄修改 |
The policy object is shared and can only be modified at the root |
| 0xC000029A | 原則物件不存在，它應該存在才對 |
The policy object does not exist when it should |
| 0xC000029B | 要求的原則資訊只存在於 Ds |
The requested policy information only lives in the Ds |
| 0xC000029C | 磁碟區必須升級以啟用這個功能 |
The volume must be upgraded to enable this feature |
| 0xC000029D | 遠端存放服務此時無法操作。 |
The remote storage service is not operational at this time. |
| 0xC000029E | 遠端存放服務遇到媒體錯誤。 |
The remote storage service encountered a media error. |
| 0xC000029F | 追蹤 (工作站) 服務並未執行。 |
The tracking (workstation) service is not running. |
| 0xC00002A0 | 正在 SID 之下執行伺服器處理程序，這不是用戶端要求的 SID。 |
The server process is running under a SID different than that required by client. |
| 0xC00002A1 | 指定的目錄服務屬性或服務值不存在。 |
The specified directory service attribute or value does not exist. |
| 0xC00002A2 | 目錄服務中所指定的屬性語法不正確。 |
The attribute syntax specified to the directory service is invalid. |
| 0xC00002A3 | 目錄服務中所指定的屬性類型並未定義。 |
The attribute type specified to the directory service is not defined. |
| 0xC00002A4 | 指定的目錄服務屬性或服務值已存在。 |
The specified directory service attribute or value already exists. |
| 0xC00002A5 | 目錄服務忙碌中。 |
The directory service is busy. |
| 0xC00002A6 | 無法使用目錄服務。 |
The directory service is not available. |
| 0xC00002A7 | 目錄服務無法配置相關的識別元。 |
The directory service was unable to allocate a relative identifier. |
| 0xC00002A8 | 目錄服務已用盡所有相關的識別元。 |
The directory service has exhausted the pool of relative identifiers. |
| 0xC00002A9 | 要求的操作無法執行，因為目錄服務不是該操作的主要類型。 |
The requested operation could not be performed because the directory service is not the master for that type of operation. |
| 0xC00002AA | 目錄服務無法將配置了相關識別元的子系統初始化。 |
The directory service was unable to initialize the subsystem that allocates relative identifiers. |
| 0xC00002AB | 要求的操作不符合一個或多個與物件類別相關的限制。 |
The requested operation did not satisfy one or more constraints associated with the class of the object. |
| 0xC00002AC | 目錄服務只有在分葉物件中才能執行要求的操作。 |
The directory service can perform the requested operation only on a leaf object. |
| 0xC00002AD | 目錄服務無法在物件的 Relatively Defined Name (RDN) 屬性上執行要求的操作。 |
The directory service cannot perform the requested operation on the Relatively Defined Name (RDN) attribute of an object. |
| 0xC00002AE | 目錄服務偵測出曾嘗試修改物件的物件類別。 |
The directory service detected an attempt to modify the object class of an object. |
| 0xC00002AF | 執行跨網域移動操作時發生錯誤。 |
An error occurred while performing a cross domain move operation. |
| 0xC00002B0 | 無法連絡通用類別目錄伺服器。 |
Unable to Contact the Global Catalog Server. |
| 0xC00002B1 | 要求的操作需要目錄服務，但是沒有可用的目錄服務。 |
The requested operation requires a directory service, and none was available. |
| 0xC00002B2 | 無法設定重新分析屬性，因為它和一個現存的屬性不相容。 |
The reparse attribute cannot be set as it is incompatible with an existing attribute. |
| 0xC00002B3 | 無法啟用標記為 [只可用來拒絕] 的群組。 |
A group marked use for deny only cannot be enabled. |
| 0xC00002B4 | {EXCEPTION}多重浮點指標錯誤。 |
{EXCEPTION}Multiple floating point faults. |
| 0xC00002B5 | {EXCEPTION}多重浮點指標陷阱。 |
{EXCEPTION}Multiple floating point traps. |
| 0xC00002B6 | 裝置已移除。 |
The device has been removed. |
| 0xC00002B7 | 正在刪除磁碟區變更日誌。 |
The volume change journal is being deleted. |
| 0xC00002B8 | 磁碟區變更日誌不在使用中。 |
The volume change journal is not active. |
| 0xC00002B9 | 不支援要求的介面。 |
The requested interface is not supported. |
| 0xC00002BA | 目錄服務偵測到配置相對識別碼的子系統已停用。當系統判斷大部分的相對識別碼 (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. |
| 0xC00002C1 | 已經超過目錄服務的資源限制。 |
A directory service resource limit has been exceeded. |
| 0xC00002C2 | {系統待命失敗} 驅動程式 %hs 無法支援待命模式。更新此驅動程式或許可以讓系統轉換成待命模式。 |
{System Standby Failed}The driver %hs does not support standby mode. Updating this driver may allow the system to go to standby mode. |
| 0xC00002C3 | 相互驗證失敗。網域控制站的伺服器密碼已過期。 |
Mutual Authentication failed. The server's password is out of date at the domain controller. |
| 0xC00002C4 | 系統檔案 %1 損毀，並且已經被取代。 |
The system file %1 has become corrupt and has been replaced. |
| 0xC00002C5 | {例外}對齊錯誤在載入或存放指令中偵測出資料類型對齊錯誤。 |
{EXCEPTION}Alignment ErrorA datatype misalignment error was detected in a load or store instruction. |
| 0xC00002C6 | WMI 資料項目或資料區塊是唯讀屬性。 |
The WMI data item or data block is read only. |
| 0xC00002C7 | 無法變更 WMI 資料項目或資料區塊。 |
The WMI data item or data block could not be changed. |
| 0xC00002C8 | {虛擬記憶體最小值太低}您的系統執行的虛擬記憶體太低。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. |
| 0xC00002C9 | {例外}登錄 NaT 消耗錯誤。NaT 數值消耗在一個非理論式的指示上。 |
{EXCEPTION}Register NaT consumption faults.A NaT value is consumed on a non speculative instruction. |
| 0xC00002CA | 媒體變更器傳輸元素包含一個導致操作失敗的媒體。 |
The medium changer's transport element contains media, which is causing the operation to fail. |
| 0xC00002CB | 安全性帳戶管理員初始化失敗，因為發生下列錯誤:%hs錯誤狀態: 0x%x。請將系統關機，並重新開機成目錄服務還原模式，然後檢查事件記錄檔，以取得詳細資訊。 |
Security Accounts Manager initialization failed because of the following error:%hsError Status: 0x%x.Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information. |
| 0xC00002CC | 這操作只有在和伺服器連線時才能獲得支援。 |
This operation is supported only when you are connected to the server. |
| 0xC00002CD | 只有系統管理員才能修改系統管理群組的成員資格清單。 |
Only an administrator can modify the membership list of an administrative group. |
| 0xC00002CE | 裝置已經移除，列舉必須重新開始。 |
A device was removed so enumeration must be restarted. |
| 0xC00002CF | 日誌項目已從日誌中刪除。 |
The journal entry has been deleted from the journal. |
| 0xC00002D0 | 無法變更網域控制站帳戶的主要群組識別碼。 |
Cannot change the primary group ID of a domain controller account. |
| 0xC00002D1 | {嚴重的系統錯誤}系統映像 %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. |
| 0xC00002D2 | 沒有重新開機的話，裝置將不會啟動。 |
Device will not start without a reboot. |
| 0xC00002D3 | 目前裝置的電源狀態無法支援這個要求。 |
Current device power state cannot support this request. |
| 0xC00002D4 | 指定的群組類型不正確。 |
The specified group type is invalid. |
| 0xC00002D5 | 混合網域中不可存在安全性已啟用的通用群組。 |
In mixed domain no nesting of global group if group is security enabled. |
| 0xC00002D6 | 在混合網域中，如果群組的安全性已啟用，則無法將本機群組與其他本機群組放在一起。 |
In mixed domain, cannot nest local groups with other local groups, if the group is security enabled. |
| 0xC00002D7 | 本機群組不可以是通用群組的成員。 |
A global group cannot have a local group as a member. |
| 0xC00002D8 | 萬用群組不可以是通用群組的成員。 |
A global group cannot have a universal group as a member. |
| 0xC00002D9 | 本機群組不可以是萬用群組的成員。 |
A universal group cannot have a local group as a member. |
| 0xC00002DA | 通用群組不可以有跨網域成員。 |
A global group cannot have a cross domain member. |
| 0xC00002DB | 本機群組不可以有另一個跨網域的本機群組作為成員。 |
A local group cannot have another cross domain local group as a member. |
| 0xC00002DC | 無法變成安全性停用群組，因為它在此群組中已有主要成員。 |
Cannot change to security disabled group because of having primary members in this group. |
| 0xC00002DD | 資料區塊或方法不支援 WMI 操作。 |
The WMI operation is not supported by the data block or method. |
| 0xC00002DE | 電源不足，無法完成要求的操作。 |
There is not enough power to complete the requested operation. |
| 0xC00002DF | 安全性帳戶管理員需要取得開機密碼。 |
Security Account Manager needs to get the boot password. |
| 0xC00002E0 | 安全性帳戶管理員需要從磁片取得開機識別碼。 |
Security Account Manager needs to get the boot key from floppy disk. |
| 0xC00002E1 | 目錄服務無法啟動。 |
Directory Service cannot start. |
| 0xC00002E2 | 目錄服務無法啟動，因為發生下列錯誤:%hs錯誤狀態: 0x%x。請將系統關機，並重新開機成目錄服務還原模式，然後檢查事件記錄檔，以取得詳細資訊。 |
Directory Services could not start because of the following error:%hsError Status: 0x%x.Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information. |
| 0xC00002E3 | 安全性帳戶管理員初始化失敗，因為發生下列錯誤:%hs錯誤狀態: 0x%x。請按一下 [確定] 將系統關機，並重新開機成安全模式，然後檢查事件記錄檔，以取得詳細資訊。 |
Security Accounts Manager initialization failed because of the following error:%hsError Status: 0x%x.Please click OK to shutdown this system and reboot into Safe Mode, check the event log for more detailed information. |
| 0xC00002E4 | 要求的操作只能在通用類別目錄伺服器上執行。 |
The requested operation can be performed only on a global catalog server. |
| 0xC00002E5 | 本機群組只能是同樣網域的其他本機群組的成員。 |
A local group can only be a member of other local groups in the same domain. |
| 0xC00002E6 | 外部安全性主體不可以是萬用群組的成員。 |
Foreign security principals cannot be members of universal groups. |
| 0xC00002E7 | 您的電腦無法加入網域。因為您已經超過這個網域所允許建立的電腦帳戶上限。請連絡您的系統管理員，重設或提高這個限制。 |
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. |
| 0xC00002E8 | STATUS_MULTIPLE_FAULT_VIOLATION |
STATUS_MULTIPLE_FAULT_VIOLATION |
| 0xC00002E9 | 無法在目前的網域中執行這個操作。 |
This operation cannot be performed on the current domain. |
| 0xC00002EA | 無法建立目錄或檔案。 |
The directory or file cannot be created. |
| 0xC00002EB | 系統正處於關機程序中。 |
The system is in the process of shutting down. |
| 0xC00002EC | 無法啟動目錄服務，這是由於以下錯誤:%hs錯誤狀態: 0x%x。請按一下 [確定] 將系統關機。您可以使用修復主控台進一步診斷系統。 |
Directory Services could not start because of the following error:%hsError Status: 0x%x.Please click OK to shutdown the system. You can use the recovery console to diagnose the system further. |
| 0xC00002ED | 無法初始化安全性帳戶管理員，這是由於以下錯誤:%hs錯誤狀態: 0x%x。請按一下 [確定] 將系統關機。您可以使用修復主控台進一步診斷系統。 |
Security Accounts Manager initialization failed because of the following error:%hsError Status: 0x%x.Please click OK to shutdown the system. You can use the recovery console to diagnose the system further. |
| 0xC00002EE | 在內容完成之前，其中一個資訊安全內容被刪除了。這屬於登入失敗。 |
A security context was deleted before the context was completed. This is considered a logon failure. |
| 0xC00002EF | 用戶端正嘗試交涉一個內容，而伺服器需要的是使用者對使用者，但並未傳送出 TGT 回覆。 |
The client is trying to negotiate a context and the server requires user-to-user but didn't send a TGT reply. |
| 0xC00002F0 | 檔案中找不到物件識別碼。 |
An object ID was not found in the file. |
| 0xC00002F1 | 無法完成所要求的工作，原因是本機電腦沒有任何 IP 位址。 |
Unable to accomplish the requested task because the local machine does not have any IP addresses. |
| 0xC00002F2 | 所提供的認證控制代碼與資訊安全內容所關聯的認證不相符合。 |
The supplied credential handle does not match the credential associated with the security context. |
| 0xC00002F3 | 密碼編譯系統或總和檢查碼功能不正確，原因是所需的函式無法使用。 |
The crypto system or checksum function is invalid because a required function is unavailable. |
| 0xC00002F4 | 已經超過票證轉介的最大數目。 |
The number of maximum ticket referrals has been exceeded. |
| 0xC00002F5 | 本機電腦必須是 Kerberos KDC (網域控制站)，而這一部不是。 |
The local machine must be a Kerberos KDC (domain controller) and it is not. |
| 0xC00002F6 | 安全性交涉中的另一端需要有嚴格的密碼編譯，但是本機電腦上並不支援。 |
The other end of the security negotiation is requires strong crypto but it is not supported on the local machine. |
| 0xC00002F7 | KDC 的回覆含有一個以上的主體名稱。 |
The KDC reply contained more than one principal name. |
| 0xC00002F8 | 需要找到 PA 資料，以便提示該使用哪一種類型，但是沒有找到。 |
Expected to find PA data for a hint of what etype to use, but it was not found. |
| 0xC00002F9 | 用戶端憑證未包含有效的 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. |
| 0xC00002FA | 需要智慧卡登入，但是沒有這麼做。 |
Smartcard logon is required and was not used. |
| 0xC00002FB | 有不正確的要求傳送給 KDC。 |
An invalid request was sent to the KDC. |
| 0xC00002FC | KDC 無法為要求的服務產生轉介。 |
The KDC was unable to generate a referral for the service requested. |
| 0xC00002FD | KDC 不支援所要求的加密類型。 |
The encryption type requested is not supported by the KDC. |
| 0xC00002FE | 系統關機進行中。 |
A system shutdown is in progress. |
| 0xC00002FF | 伺服器電腦正在關機。 |
The server machine is shutting down. |
| 0xC0000300 | 這項操作在執行 Windows Server 2003 for Small Business Server 的電腦上不支援 |
This operation is not supported on a computer running Windows Server 2003 for Small Business Server |
| 0xC0000301 | WMI GUID 已經無法再使用了 |
The WMI GUID is no longer available |
| 0xC0000302 | 已經停用 WMI GUID 的收集或事件。 |
Collection or events for the WMI GUID is already disabled. |
| 0xC0000303 | 已經啟用 WMI GUID 的收集或事件。 |
Collection or events for the WMI GUID is already enabled. |
| 0xC0000304 | 磁碟區中的主檔案表格太過分散，以致無法完成這項操作。 |
The Master File Table on the volume is too fragmented to complete this operation. |
| 0xC0000305 | 複製保護失敗。 |
Copy protection failure. |
| 0xC0000306 | 複製保護錯誤 - DVD CSS 驗證失敗。 |
Copy protection error - DVD CSS Authentication failed. |
| 0xC0000307 | 複製保護錯誤 - 指定的磁區未包含有效的金鑰。 |
Copy protection error - The given sector does not contain a valid key. |
| 0xC0000308 | 複製保護錯誤 - 尚未建立 DVD 工作階段金鑰。 |
Copy protection error - DVD session key not established. |
| 0xC0000309 | 複製保護錯誤 - 讀取失敗，因為磁區已加密。 |
Copy protection error - The read failed because the sector is encrypted. |
| 0xC000030A | 複製保護錯誤 - 指定的 DVD 地區沒有對應於光碟機的地區設定。 |
Copy protection error - The given DVD's region does not correspond to theregion setting of the drive. |
| 0xC000030B | 複製保護錯誤 - 光碟機的地區設定可能是永久性的。 |
Copy protection error - The drive's region setting may be permanent. |
| 0xC000030C | EAS 原則要求使用者必須先變更密碼，才能執行此作業。 |
EAS policy requires that the user change their password before this operation can be performed. |
| 0xC000030D | 系統管理員已限制登入。若要登入，請確定您的裝置已連線到網際網路，並要求您的系統管理員先登入。 |
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. |
| 0xC0000320 | 在登入期間，Kerberos 通訊協定在確認 KDC 憑證時發生錯誤。在系統事件記錄檔中會有詳細資訊。 |
The Kerberos protocol encountered an error while validating the KDC certificate during logon. There is more information in the system event log. |
| 0xC0000321 | Kerberos 通訊協定嘗試使用智慧卡子系統時發生錯誤。 |
The Kerberos protocol encountered an error while attempting to utilize the smartcard subsystem. |
| 0xC0000322 | 目標伺服器沒有可接受的 Kerberos 認證。 |
The target server does not have acceptable Kerberos credentials. |
| 0xC0000350 | 傳送已經判定遠端系統是關閉的。 |
The transport determined that the remote system is down. |
| 0xC0000351 | 有一個不受支援的預先驗證機制被送給 Kerberos 封裝。 |
An unsupported preauthentication mechanism was presented to the Kerberos package. |
| 0xC0000352 | 使用於來源檔的加密演算法比目的檔所使用的需要更大的金鑰緩衝區。 |
The encryption algorithm used on the source file needs a bigger key buffer than the one used on the destination file. |
| 0xC0000353 | 嘗試移除處理程序的 DebugPort，但是該處理程序尚未與連接埠關聯。 |
An attempt to remove a process's DebugPort was made, but a port was not already associated with the process. |
| 0xC0000354 | 偵錯工具停用中: 啟動 Windows 時可能未啟用核心偵錯。 |
Debugger Inactive: Windows may have been started without kernel debugging enabled. |
| 0xC0000355 | 這個版本的 Windows 與目錄樹系、網域或網域控制站的行為版本不相容。 |
This version of Windows is not compatible with the behavior version of directory forest, domain or domain controller. |
| 0xC0000356 | 所指定的事件目前不在稽核中。 |
The specified event is currently not being audited. |
| 0xC0000357 | 電腦帳戶是在 NT4 以前的作業系統上所建立。需要重新建立該帳戶。 |
The machine account was created pre-NT4. The account needs to be recreated. |
| 0xC0000358 | 帳戶群組不能將萬用群組視為成員。 |
A account group cannot have a universal group as a member. |
| 0xC0000359 | 所指定的映像檔格式不正確，它是 32 位元的 Windows 映像。 |
The specified image file did not have the correct format, it appears to be a 32-bit Windows image. |
| 0xC000035A | 所指定的映像檔格式不正確，它是 64 位元的 Windows 映像。 |
The specified image file did not have the correct format, it appears to be a 64-bit Windows image. |
| 0xC000035B | 用戶端所提供的 SSPI 通道連結不正確。 |
Client's supplied SSPI channel bindings were incorrect. |
| 0xC000035C | 用戶端工作階段已經到期。用戶端必須重新驗證，才能夠繼續存取遠端資源。 |
The client's session has expired, so the client must reauthenticate to continue accessing the remote resources. |
| 0xC000035D | AppHelp 對話已取消，因此防止了應用程式的啟動。 |
AppHelp dialog canceled thus preventing the application from starting. |
| 0xC000035E | SID 篩選操作移除了所有的 SID。 |
The SID filtering operation removed all SIDs. |
| 0xC000035F | 驅動程式沒有載入，原因是系統以安全模式開機。 |
The driver was not loaded because the system is booting into safe mode. |
| 0xC0000361 | 系統管理員依照預設的軟體限制原則層級，已經限制了對 %1 的存取。 |
Access to %1 has been restricted by your Administrator by the default software restriction policy level. |
| 0xC0000362 | 系統管理員依照放置於路徑 %3 的原則規則 %2 的位置，已經限制了對 %1 的存取 |
Access to %1 has been restricted by your Administrator by location with policy rule %2 placed on path %3 |
| 0xC0000363 | 系統管理員依照軟體發行者原則，已經限制了對 %1 的存取。 |
Access to %1 has been restricted by your Administrator by software publisher policy. |
| 0xC0000364 | 系統管理員依照原則規則 %2，已經限制了對 %1 的存取。 |
Access to %1 has been restricted by your Administrator by policy rule %2. |
| 0xC0000365 | 驅動程式沒有載入，原因是初始化呼叫失敗。 |
The driver was not loaded because it failed its initialization call. |
| 0xC0000366 | \"%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. |
| 0xC0000368 | 建立的操作失敗，原因是名稱中含有至少一個掛接點，該掛接點解析成磁碟區，而所指定的裝置物件沒有連結到這個磁碟區。 |
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. |
| 0xC0000369 | 裝置物件參數不是正確的裝置物件、或者沒有連結到檔案名稱所指定的磁碟區。 |
The device object parameter is either not a valid device object or is not attached to the volume specified by the file name. |
| 0xC000036A | 發生電腦檢查錯誤，其他資訊請檢查系統事件記錄檔。 |
A Machine Check Error has occurred. Please check the system eventlog for additional information. |
| 0xC000036B | 驅動程式 %2 已被防止載入 |
Driver %2 has been blocked from loading. |
| 0xC000036D | 處理驅動程式資料庫時發生錯誤 [%2]。 |
There was error [%2] processing the driver database. |
| 0xC000036E | 系統儲存檔大小已超出它的限制。 |
System hive size has exceeded its limit. |
| 0xC000036F | 動態連結程式庫 (DLL) 參照了既不是 DLL 也不是程序的可執行檔的模組。 |
A dynamic link library (DLL) referenced a module that was neither a DLL nor the process's executable image. |
| 0xC0000371 | 本機帳戶存放區不包含指定帳戶的密碼資料。 |
The local account store does not contain secret material for the specified account. |
| 0xC0000373 | 系統無法配置足夠的記憶體來執行堆疊參數。 |
The system was not able to allocate enough memory to perform a stack switch. |
| 0xC0000374 | 堆積已損毀。 |
A heap has been corrupted. |
| 0xC0000380 | 不正確的 PIN 呈現給智慧卡 |
An incorrect PIN was presented to the smart card |
| 0xC0000381 | 這個智慧卡已被中止 |
The smart card is blocked |
| 0xC0000382 | 沒有呈現 PIN 給智慧卡 |
No PIN was presented to the smart card |
| 0xC0000383 | 沒有可用的智慧卡 |
No smart card available |
| 0xC0000384 | 要求的金鑰容器不存在於智慧卡上 |
The requested key container does not exist on the smart card |
| 0xC0000385 | 要求的憑證不存在於智慧卡上 |
The requested certificate does not exist on the smart card |
| 0xC0000386 | 要求的索引鍵集不存在 |
The requested keyset does not exist |
| 0xC0000387 | 偵測出與智慧卡的通訊有錯誤。 |
A communication error with the smart card has been detected. |
| 0xC0000388 | 系統無法連絡網域控制站以提供驗證要求。請稍後再試一次。 |
The system cannot contact a domain controller to service the authentication request. Please try again later. |
| 0xC0000389 | 用於驗證的智慧卡憑證已撤銷。請連絡您的系統管理員。在事件記錄檔中可能有其他的資訊。 |
The smartcard certificate used for authentication has been revoked. Please contact your system administrator. There may be additional information in the event log. |
| 0xC000038A | 處理用於驗證的憑證時偵測到不受信任的憑證授權單位。 |
An untrusted certificate authority was detected while processing the certificate used for authentication. |
| 0xC000038B | 無法判斷用於驗證的憑證的撤銷狀態。 |
The revocation status of the certificate used for authentication could not be determined. |
| 0xC000038C | 用於驗證的用戶端憑證不受信任。 |
The client certificate used for authentication was not trusted. |
| 0xC000038D | 用於驗證的智慧卡憑證已到期。請連絡您的系統管理員。 |
The smartcard certificate used for authentication has expired. Pleasecontact your system administrator. |
| 0xC000038E | 無法載入驅動程式，因為前版的驅動程式仍在記憶體中。 |
The driver could not be loaded because a previous version of the driver is still in memory. |
| 0xC000038F | 智慧卡提供者無法執行動作，因為內容是隱藏的。 |
The smartcard provider could not perform the action since the context was acquired as silent. |
| 0xC0000401 | 已超過目前使用者委派的信任建立配額。 |
The current user's delegated trust creation quota has been exceeded. |
| 0xC0000402 | 已超過委派的信任建立配額總額。 |
The total delegated trust creation quota has been exceeded. |
| 0xC0000403 | 已超過目前使用者委派的信任刪除配額。 |
The current user's delegated trust deletion quota has been exceeded. |
| 0xC0000404 | 要求的名稱已以唯一識別碼存在。 |
The requested name already exists as a unique identifier. |
| 0xC0000405 | 要求的物件具有非唯一識別碼，無法抓取。 |
The requested object has a non-unique identifier and cannot be retrieved. |
| 0xC0000406 | 基於所要求群組類型上的屬性限制，群組無法轉換。 |
The group cannot be converted due to attribute restrictions on the requested group type. |
| 0xC0000407 | {磁碟區陰影複製服務}請稍候，磁碟區陰影複製服務正在準備磁碟區 %hs 休眠。 |
{Volume Shadow Copy Service}Please wait while the Volume Shadow Copy Service prepares volume %hs for hibernation. |
| 0xC0000408 | 要求 Kerberos 子通訊協定 User2User。 |
Kerberos sub-protocol User2User is required. |
| 0xC0000409 | 系統偵測到這個應用程式中堆疊為主緩衝區的滿溢，這個滿溢有可能讓心懷不軌的使用者取得這個電腦的控制。 |
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. |
| 0xC000040A | 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. |
| 0xC000040B | 這個伺服器嘗試對伺服器領域外面的目標，做 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. |
| 0xC000040C | 無法判斷用於驗證之網域控制站憑證的撤銷狀態。在系統事件記錄檔中有更多的有關資訊。 |
The revocation status of the domain controller certificate used for authentication could not be determined. There is additional information in the system event log. |
| 0xC000040D | 處理用來驗證的網域控制站憑證時，偵測到不受信任的憑證授權單位。系統事件記錄檔中有相關資訊。請連絡您的系統管理員。 |
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. |
| 0xC000040E | 用於登入的網域控制站憑證已到期。在系統事件記錄檔中有更多的有關資訊。 |
The domain controller certificate used for logon has expired. There is additional information in the system event log. |
| 0xC000040F | 用於登入的網域控制站憑證已被撤銷。在系統事件記錄檔中有更多的有關資訊。 |
The domain controller certificate used for logon has been revoked. There is additional information in the system event log. |
| 0xC0000410 | 呈現在其中一個參數中的資料超出功能函數可以運作。 |
Data present in one of the parameters is more than the function can operate on. |
| 0xC0000411 | 系統休眠失敗 (錯誤碼為 %hs)。在系統重新啟動前，休眠將被停用。 |
The system has failed to hibernate (The error code is %hs). Hibernation will be disabled until the system is restarted. |
| 0xC0000412 | 延遲載入 .dll，或於延遲載入的 .dll 中取得功能函數位址的嘗試失敗。 |
An attempt to delay-load a .dll or get a function address in a delay-loaded .dll failed. |
| 0xC0000413 | 登入失敗: 您要登入的電腦受到驗證防火牆的保護。指定的帳戶不允許驗證到電腦。 |
Logon Failure: The machine you are logging onto is protected by an authentication firewall. The specified account is not allowed to authenticate to the machine. |
| 0xC0000414 | %hs 是一個 16 位元應用程式。您沒有許可可執行 16 位元應用程式。請向您的系統管理員查詢您的許可。 |
%hs is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system administrator. |
| 0xC0000415 | {顯示驅動程式停止回應}%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. |
| 0xC0000416 | 桌面堆積在配置工作階段記憶體時發生錯誤。在系統事件記錄檔中會有詳細資訊。 |
The Desktop heap encountered an error while allocating session memory. There is more information in the system event log. |
| 0xC0000417 | 傳遞到 C 執行階段函數的參數無效。 |
An invalid parameter was passed to a C runtime function. |
| 0xC0000418 | 驗證失敗，因為 NTLM 已封鎖。 |
The authentication failed since NTLM was blocked. |
| 0xC0000419 | 目的地樹系中已經有來源物件的 SID。 |
The source object's SID already exists in destination forest. |
| 0xC000041A | 樹系中已經有受信任網域的網域名稱。 |
The domain name of the trusted domain already exists in the forest. |
| 0xC000041B | 樹系中已經有受信任網域的一般名稱。 |
The flat name of the trusted domain already exists in the forest. |
| 0xC000041C | 使用者主體名稱 (UPN) 不正確。 |
The User Principal Name (UPN) is invalid. |
| 0xC000041D | 在使用者回撥時，發生未處理的例外狀況。 |
An unhandled exception was encountered during a user callback. |
| 0xC0000420 | 發生宣告失敗。 |
An assertion failure has occurred. |
| 0xC0000421 | 應用程式驗證器已在目前的處理程序中找到錯誤。 |
Application verifier has found an error in the current process. |
| 0xC0000423 | 使用者模式回呼發生例外，且應該移除核心回呼框架。 |
An exception has occurred in a user mode callback and the kernel callback frame should be removed. |
| 0xC0000424 | %2 已被防止載入，原因是其與此系統不相容。請連絡您的軟體廠商，以取得相容的驅動程式版本。 |
%2 has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver. |
| 0xC0000425 | 嘗試在已解除載入的登錄機碼上執行無效的操作。 |
Illegal operation attempted on a registry key which has already been unloaded. |
| 0xC0000426 | 已停用此磁碟區的壓縮。 |
Compression is disabled for this volume. |
| 0xC0000427 | 因為檔案系統限制，所以無法完成要求的作業。 |
The requested operation could not be completed due to a file system limitation |
| 0xC0000428 | 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. |
| 0xC0000429 | 執行方式無法執行要求。 |
The implementation is not capable of performing the request. |
| 0xC000042A | 考量其他作業後，要求的作業有誤。 |
The requested operation is out of order with respect to other operations. |
| 0xC000042B | 作業嘗試超過執行定義的限制。 |
An operation attempted to exceed an implementation-defined limit. |
| 0xC000042C | 要求的作業需要提升的權限。 |
The requested operation requires elevation. |
| 0xC000042D | 所需的資訊安全內容不存在。 |
The required security context does not exist. |
| 0xC000042F | PKU2U 通訊協定嘗試使用關聯的憑證時發生錯誤。 |
The PKU2U protocol encountered an error while attempting to utilize the associated certificates. |
| 0xC0000432 | 作業嘗試超出有效的檔案資料長度。 |
The operation was attempted beyond the valid data length of the file. |
| 0xC0000433 | 嘗試的寫入作業發生範圍內的一些部分已在寫入中。 |
The attempted write operation encountered a write already in progress for some portion of the range. |
| 0xC0000434 | 因為分頁錯誤對應在處理錯誤的過程中有所變更，所以必須重試作業。 |
The page fault mappings changed in the middle of processing a fault so the operation must be retried. |
| 0xC0000435 | 從記憶體清除此檔案的嘗試無法清除部分或所有記憶體中的資料。 |
The attempt to purge this file from memory failed to purge some or all the data from memory. |
| 0xC0000440 | 要求的認證需要確認。 |
The requested credential requires confirmation. |
| 0xC0000441 | 遠端伺服器已將無效的回應傳送給以用戶端加密開啟的檔案。 |
The remote server sent an invalid response for a file being opened with Client Side Encryption. |
| 0xC0000442 | 遠端伺服器雖然聲稱支援用戶端加密，但其實不支援。 |
Client Side Encryption is not supported by the remote server even though it claims to support it. |
| 0xC0000443 | 檔案已加密，且應在用戶端加密模式下開啟。 |
File is encrypted and should be opened in Client Side Encryption mode. |
| 0xC0000444 | 已建立新的加密檔案，且需要提供 $EFS。 |
A new encrypted file is being created and a $EFS needs to be provided. |
| 0xC0000445 | SMB 用戶端在非 CSE 檔案上要求 CSE FSCTL。 |
The SMB client requested a CSE FSCTL on a non-CSE file. |
| 0xC0000446 | 指出可能無法將特定的安全性識別碼指派為物件的標籤。 |
Indicates a particular Security ID may not be assigned as the label of an object. |
| 0xC0000450 | 主控此裝置驅動程式的處理程序已終止。 |
The process hosting the driver for this device has terminated. |
| 0xC0000451 | 因為多個無法識別的裝置都可能符合識別條件，所以無法識別要求的系統裝置。 |
The requested system device cannot be identified due to multiple indistinguishable devices potentially matching the identification criteria. |
| 0xC0000452 | 找不到要求的系統裝置。 |
The requested system device cannot be found. |
| 0xC0000453 | 這個開機應用程式必須重新啟動。 |
This boot application must be restarted. |
| 0xC0000454 | NVRAM 資源不足，無法完成 API。可能需要重新開機。 |
Insufficient NVRAM resources exist to complete the API. A reboot might be required. |
| 0xC0000455 | 指定的工作階段無效。 |
The specified session is invalid. |
| 0xC0000456 | 指定的執行緒已在工作階段中。 |
The specified thread is already in a session. |
| 0xC0000457 | 指定的執行緒不在工作階段中。 |
The specified thread is not in a session. |
| 0xC0000458 | 指定的權重無效。 |
The specified weight is invalid. |
| 0xC0000459 | 作業已暫停。 |
The operation was paused. |
| 0xC0000460 | 無法處理所指定作業的範圍。 |
No ranges for the specified operation were able to be processed. |
| 0xC0000461 | 此磁碟的實體資源已用完。 |
The physical resources of this disk have been exhausted. |
| 0xC0000462 | 無法啟動應用程式。請嘗試重新安裝應用程式以修正問題。 |
The application cannot be started. Try reinstalling the application to fix the problem. |
| 0xC0000463 | {裝置功能不受支援}裝置不支援命令功能。 |
{Device Feature Not Supported}The device does not support the command feature. |
| 0xC0000464 | {無法連線到來源/目的地裝置}無法連線到裝置。 |
{Source/Destination device unreachable}The device is unreachable. |
| 0xC0000465 | {Proxy 資料權杖無效}代表資料的權杖無效。 |
{Invalid Proxy Data Token}The token representing the data is invalid. |
| 0xC0000466 | 檔案伺服器暫時無法使用。 |
The file server is temporarily unavailable. |
| 0xC0000467 | 檔案暫時無法使用。 |
The file is temporarily unavailable. |
| 0xC0000468 | {裝置資源不足}目標裝置的資源不足，無法完成作業。 |
{Device Insufficient Resources}The target device has insufficient resources to complete the operation. |
| 0xC0000469 | 應用程式目前正在更新，因此無法啟動。 |
The application cannot be started because it is currently updating. |
| 0xC000046A | 無法讀取指定的要求資料複本。 |
The specified copy of the requested data could not be read. |
| 0xC000046B | 無法將指定的資料寫入到任一複本。 |
The specified data could not be written to any of the copies. |
| 0xC000046C | 此裝置上的一或多份資料複本未同步。完成資料完整性掃描之前，無法執行寫入。 |
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. |
| 0xC000046D | 此物件未受任何外部提供者支援。 |
This object is not externally backed by any provider. |
| 0xC000046E | 無法識別該外部支援提供者。 |
The external backing provider is not recognized. |
| 0xC000046F | 壓縮此物件並不會節省空間。 |
Compressing this object would not save space. |
| 0xC0000470 | 發生資料完整性總和檢查碼錯誤。檔案資料流中的資料損毀。 |
A data integrity checksum error occurred. Data in the file stream is corrupt. |
| 0xC0000471 | 嘗試在相同作業中同時修改 KERNEL 與一般擴充屬性 (EA)。 |
An attempt was made to modify both a KERNEL and normal Extended Attribute (EA) in the same operation. |
| 0xC0000472 | {LogicalBlockProvisioningReadZero 不受支援}目標裝置不支援讀取已修剪/未對應區塊傳回的零。 |
{LogicalBlockProvisioningReadZero Not Supported}The target device does not support read returning zeros from trimmed/unmapped blocks. |
| 0xC0000473 | {超過區段描述元數目上限}命令指定的描述元數目超過裝置支援的上限。 |
{Maximum Segment Descriptors Exceeded}The command specified a number of descriptors that exceeded the maximum supported by the device. |
| 0xC0000474 | {對齊違規}命令指定的資料位移未對齊裝置的資料粒度/對齊。 |
{Alignment Violation}The command specified a data offset that does not align to the device's granularity/alignment. |
| 0xC0000475 | {參數清單中的欄位無效}命令指定的欄位在其參數清單中無效。 |
{Invalid Field In Parameter List}The command specified an invalid field in its parameter list. |
| 0xC0000476 | {操作進行中}目前已在該裝置上進行操作。 |
{Operation In Progress}An operation is currently in progress with the device. |
| 0xC0000477 | {無效的 I_T Nexus}嘗試透過無效的路徑傳送命令給目標裝置。 |
{Invalid I_T Nexus}An attempt was made to send down the command via an invalid path to the target device. |
| 0xC0000478 | 指定的檔案已停用清除 (Scrub)。 |
Scrub is disabled on the specified file. |
| 0xC0000479 | 存放裝置未提供備援。 |
The storage device does not provide redundancy. |
| 0xC000047A | 駐留檔案不支援作業。 |
An operation is not supported on a resident file. |
| 0xC000047B | 壓縮檔案不支援作業。 |
An operation is not supported on a compressed file. |
| 0xC000047C | 目錄不支援作業。 |
An operation is not supported on a directory. |
| 0xC000047D | {IO 作業逾時}指定的 I/O 作業無法在預期的時間週期內完成。 |
{IO Operation Timeout}The specified I/O operation failed to complete within the expected time period. |
| 0xC000047E | 在系統二進位檔案中偵測到錯誤。請嘗試重新整理電腦以修正該問題。 |
An error in a system binary was detected. Try refreshing the PC to fix the problem. |
| 0xC000047F | 在系統上偵測到已損毀的 CLR NGEN 二進位檔案。 |
A corrupted CLR NGEN binary was detected on the system. |
| 0xC0000480 | 該共用暫時無法使用， |
The share is temporarily unavailable. |
| 0xC0000481 | 找不到目標 dll，因為並未裝載 apiset %hs。 |
The target dll was not found because the apiset %hs is not hosted. |
| 0xC0000482 | API 集合擴充包含屬於不存在之 API 集合的主機。 |
The API set extension contains a host for a non-existent API set. |
| 0xC0000483 | 要求失敗，因為發生嚴重的裝置硬體錯誤。 |
The request failed due to a fatal device hardware error. |
| 0xC0000484 | 指定的韌體插槽無效。 |
The specified firmware slot is invalid. |
| 0xC0000485 | 指定的韌體映像無效。 |
The specified firmware image is invalid. |
| 0xC0000486 | 要求失敗，因為存放裝置拓撲識別碼不符。 |
The request failed due to a storage topology ID mismatch. |
| 0xC0000487 | 指定的 Windows 映像 (WIM) 未標示為可開機。 |
The specified Windows Image (WIM) is not marked as bootable. |
| 0xC0000488 | 操作已由家長監護封鎖。 |
The operation was blocked by parental controls. |
| 0xC0000489 | 部署操作失敗，因為必須先註冊指定的應用程式。 |
The deployment operation failed because the specified application needs to be registered first. |
| 0xC000048A | 由於仍在執行配額操作，因此要求的操作失敗。 |
The requested operation failed due to quota operation is still in progress. |
| 0xC000048B | 回呼函式必須以內嵌方式叫用。 |
The callback function must be invoked inline. |
| 0xC000048C | 正在參考的檔案系統區塊已達到參考計數上限，因此無法再繼續參考。 |
A file system block being referenced has already reached the maximum reference count and can't be referenced any further. |
| 0xC000048D | 要求的作業失敗，因為檔案資料流已標示為不允許寫入。 |
The requested operation failed because the file stream is marked to disallow writes. |
| 0xC000048E | 「Windows 資訊保護」原則不允許存取此網路資源。 |
Windows Information Protection policy does not allow access to this network resource. |
| 0xC000048F | 要求的作業失敗，並顯示架構特定的失敗碼。 |
The requested operation failed with an architecture-specific failure code. |
| 0xC0000490 | 沒有相容的驅動程式可供此裝置使用。 |
There are no compatible drivers available for this device. |
| 0xC0000491 | 在系統上找不到指定的驅動程式套件。 |
The specified driver package cannot be found on the system. |
| 0xC0000492 | 驅動程式套件找不到必要的驅動程式設定。 |
The driver package cannot find a required driver configuration. |
| 0xC0000493 | 驅動程式設定不完整，無法搭配此裝置使用。。 |
The driver configuration is incomplete for use with this device. |
| 0xC0000494 | 裝置需要含有功能驅動程式的驅動程式設定。 |
The device requires a driver configuration with a function driver. |
| 0xC0000495 | 裝置目前擱置中以等待進一步設定。 |
The device is pending further configuration. |
| 0xC0000496 | 裝置提示名稱緩衝區太小，無法接收剩餘的名稱。 |
The device hint name buffer is too small to receive the remaining name. |
| 0xC0000497 | 套件目前無法使用。 |
The package is currently not available. |
| 0xC0000499 | 裝置處於維護模式。 |
The device is in maintenance mode. |
| 0xC000049A | DAX 磁碟區上不支援此作業。 |
This operation is not supported on a DAX volume. |
| 0xC000049B | 磁碟區上的可用空間太過分散，因此無法完成此作業。 |
The free space on the volume is too fragmented to complete this operation. |
| 0xC000049C | 磁碟區具有作用中 DAX 對應。 |
The volume has active DAX mappings. |
| 0xC000049D | 處理程序建立作業已被封鎖。 |
The process creation has been blocked. |
| 0xC000049E | 該存放裝置已遺失資料或持續性。 |
The storage device has lost data or persistence. |
| 0xC000049F | 當 CFG 已啟用時，無法設定驅動程式檢查器揮發性設定。 |
Driver Verifier Volatile settings cannot be set when CFG is enabled. |
| 0xC0000500 | 指定的工作名稱無效。 |
The specified task name is invalid. |
| 0xC0000501 | 指定的工作索引無效。 |
The specified task index is invalid. |
| 0xC0000502 | 指定的執行緒已加入工作。 |
The specified thread is already joining a task. |
| 0xC0000503 | 已要求回呼略過原始碼。 |
A callback has requested to bypass native code. |
| 0xC0000504 | 目標電腦未定義指定的集中存取原則。 |
The Central Access Policy specified is not defined on the target machine. |
| 0xC0000505 | 從 Active Directory 取得的集中存取原則無效。 |
The Central Access Policy obtained from Active Directory is invalid. |
| 0xC0000506 | 無法完成要求的作業，因為指定的處理程序不是 GUI 處理程序。 |
Unable to finish the requested operation because the specified process is not a GUI process. |
| 0xC0000507 | 裝置既沒有回應也無法安全地移除。 |
The device is not responding and cannot be safely removed. |
| 0xC0000508 | 指定的工作已經有指派給它的容器。 |
The specified Job already has a container assigned to it. |
| 0xC0000509 | 指定的工作並沒有被指派容器。 |
The specified Job does not have a container assigned to it. |
| 0xC000050A | 裝置沒有回應。 |
The device is unresponsive. |
| 0xC000050B | 物件管理員在抓取物件時發現重新分析點。 |
The object manager encountered a reparse point while retrieving an object. |
| 0xC000050C | 要求的屬性不存在於指定的檔案或目錄中。 |
The requested attribute is not present on the specified file or directory. |
| 0xC000050D | 此磁碟區不是分層磁碟區。 |
This volume is not a tiered volume. |
| 0xC000050E | 這個檔案目前與不同的串流識別碼相關聯。 |
This file is currently associated with a different stream id. |
| 0xC000050F | 因為指定的工作具有子系，所以無法完成要求的作業。 |
The requested operation could not be completed because the specified job has children. |
| 0xC0000510 | 已初始化過指定的物件。 |
The specified object has already been initialized. |
| 0xC0000602 | {立即失敗例外狀況}發生立即失敗例外狀況。將不啟動例外處理常式，並將立即終止處理程序。 |
{Fail Fast Exception}A fail fast exception occurred. Exception handlers will not be invoked and the process will be terminated immediately. |
| 0xC0000603 | Windows 無法驗證此檔案的數位簽章。這個檔案的簽署憑證已經撤銷。 |
Windows cannot verify the digital signature for this file. The signing certificate for this file has been revoked. |
| 0xC0000604 | 因為程序禁止動態程式碼產生，已禁止操作。 |
The operation was blocked as the process prohibits dynamic code generation. |
| 0xC0000605 | Windows 無法驗證此檔案的數位簽章。此檔案的簽署憑證已過期。 |
Windows cannot verify the digital signature for this file. The signing certificate for this file has expired. |
| 0xC0000606 | 已封鎖指定映像檔的載入，因為它未啟用處理程序所需的功能: 控制流程防護。 |
The specified image file was blocked from loading because it does not enable a feature required by the process: Control Flow Guard. |
| 0xC0000607 | 已封鎖指定映像檔的載入，因為它未啟用處理程序所需的功能: 傳回流程防護。 |
The specified image file was blocked from loading because it does not enable a feature required by the process: Return Flow Guard. |
| 0xC0000608 | 「傳回流程防護」受限區域發生無效記憶體存取。 |
An invalid memory access occurred to a Return Flow Guard restricted region. |
| 0xC0000609 | 附加的處理程序的「傳回流程防護」受限區域發生無效記憶體存取。 |
An invalid memory access occurred to a Return Flow Guard restricted region from an attached process. |
| 0xC000060A | 執行緒內容已限為處理程序使用，因此無法更新。 |
The thread context could not be updated because this has been restricted for the process. |
| 0xC000060B | 嘗試存取另一個磁碟分割的私密檔案/區段遭拒。 |
An attempt to access another partition's private file/section was rejected. |
| 0xC000060C | 此處理程序附加到另一個處理程序時觸發了對「傳回流程防護」受限區域的無效記憶體存取。 |
This process triggered an invalid memory access to a Return Flow Guard restricted region while attached to another process. |
| 0xC0000700 | ALPC 連接埠已關閉。 |
The ALPC port is closed. |
| 0xC0000701 | 要求的 ALPC 訊息已經無法使用。 |
The ALPC message requested is no longer available. |
| 0xC0000702 | 提供的 ALPC 訊息無效。 |
The ALPC message supplied is invalid. |
| 0xC0000703 | ALPC 訊息已取消。 |
The ALPC message has been canceled. |
| 0xC0000704 | 無效的遞迴發送嘗試。 |
Invalid recursive dispatch attempt. |
| 0xC0000705 | 同步要求中沒有提供任何接收緩衝區。 |
No receive buffer has been supplied in a synchrounus request. |
| 0xC0000706 | 連線連接埠用於無效的環境中。 |
The connection port is used in an invalid context. |
| 0xC0000707 | ALPC 連接埠不接受新的要求訊息。 |
The ALPC port does not accept new request messages. |
| 0xC0000708 | 要求的資源已在使用中。 |
The resource requested is already in use. |
| 0xC0000709 | 硬體已報告無法修正的記憶體錯誤。 |
The hardware has reported an uncorrectable memory error. |
| 0xC000070A | 傳回狀態 0x%08x，在控制代碼 0x%x 上等待 0x%p，於等候者 0x%p 中。 |
Status 0x%08x was returned, waiting on handle 0x%x for wait 0x%p, in waiter 0x%p. |
| 0xC000070B | 回呼 0x%p(0x%p) 後，對 SetEvent(0x%p) 的完成呼叫失敗，狀態為 0x%08x。 |
After a callback to 0x%p(0x%p), a completion call to SetEvent(0x%p) failed with status 0x%08x. |
| 0xC000070C | 回呼 0x%p(0x%p) 後，對 ReleaseSemaphore(0x%p, %d) 的完成呼叫失敗，狀態為 0x%08x。 |
After a callback to 0x%p(0x%p), a completion call to ReleaseSemaphore(0x%p, %d) failed with status 0x%08x. |
| 0xC000070D | 回呼 0x%p(0x%p) 後，對 ReleaseMutex(%p) 的完成呼叫失敗，狀態為 0x%08x。 |
After a callback to 0x%p(0x%p), a completion call to ReleaseMutex(%p) failed with status 0x%08x. |
| 0xC000070E | 回呼 0x%p(0x%p) 後，對 FreeLibrary(%p) 的完成呼叫失敗，狀態為 0x%08x。 |
After a callback to 0x%p(0x%p), an completion call to FreeLibrary(%p) failed with status 0x%08x. |
| 0xC000070F | 當執行緒將對 0x%p(0x%p) 的回呼張貼至執行緒集區 0x%p 時，該執行緒集區已釋放。 |
The threadpool 0x%p was released while a thread was posting a callback to 0x%p(0x%p) to it. |
| 0xC0000710 | 回呼 0x%p(0x%p) 後，執行緒集區背景工作執行緒正在模擬用戶端。這是未預期的狀況，代表回呼遺失還原模擬的呼叫。 |
A threadpool worker thread is impersonating a client, after a callback to 0x%p(0x%p).This is unexpected, indicating that the callback is missing a call to revert the impersonation. |
| 0xC0000711 | 執行 APC 後，執行緒集區背景工作執行緒正在模擬用戶端。這是未預期的狀況，代表 APC 遺失還原模擬的呼叫。 |
A threadpool worker thread is impersonating a client, after executing an APC.This is unexpected, indicating that the APC is missing a call to revert the impersonation. |
| 0xC0000712 | 目標處理程序或目標執行緒包含的處理程序是受保護的處理程序。 |
Either the target process, or the target thread's containing process, is a protected process. |
| 0xC0000713 | 因為 MCA，執行緒正在中斷與 MCA EXCEPTION 的連線。 |
A Thread is getting dispatched with MCA EXCEPTION because of MCA. |
| 0xC0000714 | 用戶端憑證帳戶對應不是唯一的。 |
The client certificate account mapping is not unique. |
| 0xC0000715 | 因為符號連結的類型已停用，所以無法遵循符號連結。 |
The symbolic link cannot be followed because its type is disabled. |
| 0xC0000716 | 表示指定的字串對 IDN 正規化而言無效。 |
Indicates that the specified string is not valid for IDN normalization. |
| 0xC0000718 | 提供的回呼已登錄。 |
The provided callback is already registered. |
| 0xC0000719 | 提供的內容與目標不相符。 |
The provided context did not match the target. |
| 0xC000071A | 指定的連接埠已經有完成清單。 |
The specified port already has a completion list. |
| 0xC000071B | 執行緒集區背景工作執行緒進入執行緒基本優先順序 0x%x 的回呼，並在優先順序 0x%x 離開。這是未預期的狀況，代表回呼錯過還原優先順序。 |
A threadpool worker thread enter a callback at thread base priority 0x%x and exited at priority 0x%x.This is unexpected, indicating that the callback missed restoring the priority. |
| 0xC000071C | 這項操作指定不正確的執行緒，控制代碼 %p。可能是指定了執行緒集區背景工作執行緒。 |
An invalid thread, handle %p, is specified for this operation. Possibly, a threadpool worker thread was specified. |
| 0xC000071D | 執行緒集區背景工作執行緒進入回呼，留下交易狀態。這是未預期的狀況，代表回呼錯過清除交易。 |
A threadpool worker thread enter a callback, which left transaction state.This is unexpected, indicating that the callback missed clearing the transaction. |
| 0xC000071E | 執行緒集區背景工作執行緒進入回呼，留下保留的載入器鎖定。這是未預期的狀況，代表回呼錯過釋放鎖定。 |
A threadpool worker thread enter a callback, which left the loader lock held.This is unexpected, indicating that the callback missed releasing the lock. |
| 0xC000071F | 執行緒集區背景工作執行緒進入回呼，留下偏好的語言設定。這是未預期的狀況，代表回呼錯過清除它們。 |
A threadpool worker thread enter a callback, which left with preferred languages set.This is unexpected, indicating that the callback missed clearing them. |
| 0xC0000720 | 執行緒集區背景工作執行緒進入回呼，留下背景優先順序設定。這是未預期的狀況，代表回呼錯過還原原本的優先順序。 |
A threadpool worker thread enter a callback, which left with background priorities set.This is unexpected, indicating that the callback missed restoring the original priorities. |
| 0xC0000721 | 執行緒集區背景工作執行緒進入在執行緒親和性 %p 的回呼，並在執行緒相關性 %p 離開。這是未預期的狀況，代表回呼錯過還原優先順序。 |
A threadpool worker thread enter a callback at thread affinity %p and exited at affinity %p.This is unexpected, indicating that the callback missed restoring the priority. |
| 0xC0000722 | 呼叫者已超過可在單一本機程序呼叫中傳輸的控制代碼數目上限。 |
The caller has exceeded the maximum number of handles that may be transmitted ina single local procedure call. |
| 0xC0000800 | 嘗試的作業需要啟用自我修復的功能。 |
The attempted operation required self healing to be enabled. |
| 0xC0000801 | 目錄服務無法執行要求的操作，因為正在進行網域重新命名操作。 |
The Directory Service cannot perform the requested operation because a domain rename operation is in progress. |
| 0xC0000802 | 要求的檔案操作失敗，因為已超過儲存配額。若要釋出磁碟空間，請將檔案移動到其他位置或刪除不必要的檔案。如需詳細資訊，請連絡您的系統管理員。 |
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. |
| 0xC0000804 | 要求的檔案操作失敗，因為存放原則已封鎖該檔案類型。如需詳細資訊，請連絡您的系統管理員。 |
The requested file operation failed because the storage policy blocks that type of file. For more information, contact your system administrator. |
| 0xC0000805 | 無法完成此操作，因為磁碟上的叢集已損壞。 |
The operation could not be completed due to bad clusters on disk. |
| 0xC0000806 | 操作無法完成，因為磁碟區不乾淨。請執行 chkdsk 然後再試一次。 |
The operation could not be completed because the volume is dirty. Please run chkdsk and try again. |
| 0xC0000808 | 磁碟區修復失敗。 |
The volume repair was not successful. |
| 0xC0000809 | 其中一個磁碟區損毀記錄檔已滿。將不會記錄之後偵測到的損毀。 |
One of the volume corruption logs is full. Further corruptions that may be detected won't be logged. |
| 0xC000080A | 其中一個磁碟區損毀記錄檔內部損毀，需要重建。磁碟區可能包含未偵測的損毀，因此必須進行掃描。 |
One of the volume corruption logs is internally corrupted and needs to be recreated. The volume may contain undetected corruptions and must be scanned. |
| 0xC000080B | 無法在其中一個磁碟區損毀記錄檔上進行操作。 |
One of the volume corruption logs is unavailable for being operated on. |
| 0xC000080C | 已刪除其中一個磁碟區損毀記錄檔，但其中仍然有損毀記錄。磁碟區包含已偵測的損毀，因此必須進行掃描。 |
One of the volume corruption logs was deleted while still having corruption records in them. The volume contains detected corruptions and must be scanned. |
| 0xC000080D | chkdsk 已清除其中一個磁碟區損毀記錄檔，因此不再包含實際的損毀。 |
One of the volume corruption logs was cleared by chkdsk and no longer contains real corruptions. |
| 0xC000080E | 孤立檔案存在於磁碟區上，但因為無法再於復原目錄中建立新名稱，所以無法進行復原。必須從復原目錄中移動檔案。 |
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. |
| 0xC000080F | 無法完成作業，因為「主動式掃描器」的執行個體目前正在執行。 |
The operation could not be completed because an instance of Proactive Scanner is currently running. |
| 0xC0000810 | 無法完成加密檔案的讀取或寫入操作，因為尚未開啟該檔案進行資料存取。 |
The read or write operation to an encrypted file could not be completed because the file has not been opened for data access. |
| 0xC0000811 | 其中一個磁碟區損毀記錄檔來自於較新版本的 Windows，而且包含損毀記錄。系統會將該記錄檔清空並重設為目前的版本，磁碟區健康情況狀態也將會據此更新。 |
One of the volume corruption logs comes from a newer version of Windows and contains corruption records. The log will be emptied and reset to the current version, and the volume health state will be updated accordingly. |
| 0xC0000901 | 此檔案已由其他使用者取出或封鎖編輯。 |
This file is checked out or locked for editing by another user. |
| 0xC0000902 | 儲存變更前必須取出檔案。 |
The file must be checked out before saving changes. |
| 0xC0000903 | 儲存或抓取的檔案類型已封鎖。 |
The file type being saved or retrieved has been blocked. |
| 0xC0000904 | 檔案大小超過允許的限制，無法儲存。 |
The file size exceeds the limit allowed and cannot be saved. |
| 0xC0000905 | 拒絕存取。在此位置開啟檔案前，您必須先瀏覽到網站並選取自動登入的選項。 |
Access Denied. Before opening files in this location, you must first browse to the web site and select the option to login automatically. |
| 0xC0000906 | 因為檔案包含病毒或潛在的垃圾軟體，所以作業未順利完成。 |
Operation did not complete successfully because the file contains a virus or potentially unwanted software. |
| 0xC0000907 | 這個檔案包含病毒或潛在的垃圾軟體，因此無法開啟。有鑑於病毒或潛在的垃圾軟體的本質，檔案已從此位置中移除。 |
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. |
| 0xC0000908 | 此裝置所需的資源與 MCFG 表格互相衝突。 |
The resources required for this device conflict with the MCFG table. |
| 0xC0000909 | 無法順利完成操作，因為該操作會造成 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. |
| 0xC000090A | 金鑰錯誤。 |
Bad key. |
| 0xC000090B | 資料錯誤。 |
Bad data. |
| 0xC000090C | 金鑰不存在。 |
Key does not exist. |
| 0xC0000910 | 已撤銷對所指定檔案控制代碼的存取權。 |
Access to the specified file handle has been revoked. |
| 0xC0009898 | WOW 宣告錯誤。 |
WOW Assertion Error. |
| 0xC000A000 | 密碼編譯簽章無效。 |
The cryptographic signature is invalid. |
| 0xC000A001 | 密碼編譯提供者不支援 HMAC。 |
The cryptographic provider does not support HMAC. |
| 0xC000A002 | 已計算的驗證標記不符合輸入驗證標記。 |
The computed authentication tag did not match the input authentication tag. |
| 0xC000A003 | 要求的狀態轉換無效，因此無法執行。 |
The requested state transition is invalid and cannot be performed. |
| 0xC000A004 | 提供的核心資訊版本無效。 |
The supplied kernel information version is invalid. |
| 0xC000A005 | 提供的 PEP 資訊版本無效。 |
The supplied PEP information version is invalid. |
| 0xC000A006 | 已撤銷對所指定控制代碼的存取權。 |
Access to the specified handle has been revoked. |
| 0xC000A007 | 該檔案作業將導致檔案結尾出現在不存在的範圍之外。 |
The file operation will result in the end of file being on a ghosted range. |
| 0xC000A010 | IPSEC 佇列溢位。 |
The IPSEC queue overflowed. |
| 0xC000A011 | 鄰居搜索佇列溢位。 |
The neighbor discovery queue overflowed. |
| 0xC000A012 | 收到超過 ICMP 躍點限制錯誤。 |
An ICMP hop limit exceeded error was received. |
| 0xC000A013 | 本機電腦上未安裝通訊協定。 |
The protocol is not installed on the local machine. |
| 0xC000A014 | 在網路快速路徑上已拒絕操作或資料。 |
An operation or data has been rejected while on the network fast path. |
| 0xC000A080 | {延遲寫入失敗}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. |
| 0xC000A081 | {延遲寫入失敗}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. |
| 0xC000A082 | {延遲寫入失敗}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. |
| 0xC000A083 | Windows 無法剖析要求的 XML 資料。 |
Windows was unable to parse the requested XML data. |
| 0xC000A084 | 處理 XML 數位簽章時發生錯誤。 |
An error was encountered while processing an XML digital signature. |
| 0xC000A085 | 表示呼叫者以錯誤的路由區間進行連線要求。 |
Indicates that the caller made the connection request in the wrong routing compartment. |
| 0xC000A086 | 表示嘗試連線到遠端主機時發生 AuthIP 失敗。 |
Indicates that there was an AuthIP failure when attempting to connect to the remote host. |
| 0xC000A087 | OID 對應的群組不能包含成員。 |
OID mapped groups cannot have members. |
| 0xC000A088 | 找不到指定的 OID。 |
The specified OID cannot be found. |
| 0xC000A089 | 系統沒有管理所指定帳戶的權限，因此無法完成作業。請使用與此帳戶關聯的提供者來重試作業。若這是線上提供者，請使用該提供者的線上網站。 |
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. |
| 0xC000A100 | 未在伺服器上對指定的版本與雜湊類型啟用雜湊產生。 |
Hash generation for the specified version and hash type is not enabled on server. |
| 0xC000A101 | 雜湊要求不存在，或不具有目前的最新檔案內容。 |
The hash requests is not present or not up to date with the current file contents. |
| 0xC000A121 | 未註冊管理所指定插斷的次要插斷控制器執行個體。 |
The secondary interrupt controller instance that manages the specified interrupt is not registered. |
| 0xC000A122 | GPIO 用戶端驅動程式所提供的資訊無效。 |
The information supplied by the GPIO client driver is invalid. |
| 0xC000A123 | 不支援 GPIO 用戶端驅動程式所指定的版本。 |
The version specified by the GPIO client driver is not supported. |
| 0xC000A124 | GPIO 用戶端驅動程式所提供的註冊封包無效。 |
The registration packet supplied by the GPIO client driver is not valid. |
| 0xC000A125 | 指定的控制代碼不支援要求的作業。 |
The requested operation is not suppported for the specified handle. |
| 0xC000A126 | 要求的連線模式與一或多個所指定 Pin 上的現有模式衝突。 |
The requested connect mode conflicts with an existing mode on one or more of the specified pins. |
| 0xC000A141 | 因為一或多個服務拒絕停止或重新啟動，所以無法順利完成要求的執行層級切換。 |
The requested run level switch cannot be completed successfully sinceone or more services refused to stop or restart. |
| 0xC000A142 | 服務的執行層級設定無效。服務的執行層級不能高於其依存服務的執行層級。 |
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. |
| 0xC000A143 | 因為有一或多個服務將無法在指定的逾時內停止或重新啟動，所以無法順利完成要求的執行層級切換。 |
The requested run level switch cannot be completed successfully sinceone or more services will not stop or restart within the specified timeout. |
| 0xC000A145 | 執行層級切換代理程式未在指定的逾時內回應。 |
A run level switch agent did not respond within the specified timeout. |
| 0xC000A146 | 目前正在進行執行層級切換。 |
A run level switch is currently in progress. |
| 0xC000A200 | 此作業只有在應用程式容器的內容中才有效。 |
This operation is only valid in the context of an app container. |
| 0xC000A201 | 在應用程式容器的內容中不支援此功能。 |
This functionality is not supported in the context of an app container. |
| 0xC000A202 | 提供的 SID 長度不是有效的應用程式容器 SID 長度。 |
The length of the SID supplied is not a valid length for app container SIDs. |
| 0xC000A203 | 存取具有較低特殊權限之應用程式的指定資源被拒。 |
Access to the specified resource has been denied for a less privileged app container. |
| 0xC000A281 | 找不到快速快取資料。 |
Fast Cache data not found. |
| 0xC000A282 | 快速快取資料已到期。 |
Fast Cache data expired. |
| 0xC000A283 | 快速快取資料損毀。 |
Fast Cache data corrupt. |
| 0xC000A284 | 快速快取資料已超出其大小上限，因此無法更新。 |
Fast Cache data has exceeded its max size and cannot be updated. |
| 0xC000A285 | 快速快取已重設授權狀態，因此需要重新開機才能更新。 |
Fast Cache has been ReArmed and requires a reboot until it can be updated. |
| 0xC000A2A1 | 篩選器不支援複製卸載讀取操作。 |
The copy offload read operation is not supported by a filter. |
| 0xC000A2A2 | 篩選器不支援複製卸載寫入操作。 |
The copy offload write operation is not supported by a filter. |
| 0xC000A2A3 | 檔案不支援複製卸載讀取操作。 |
The copy offload read operation is not supported for the file. |
| 0xC000A2A4 | 檔案不支援複製卸載寫入操作。 |
The copy offload write operation is not supported for the file. |
| 0xC000CE01 | 支援檔案系統虛擬化的提供者暫時無法使用。 |
The provider that supports file system virtualization is temporarily unavailable. |
| 0xC000CE02 | 檔案系統虛擬化的中繼資料已損毀且無法讀取。 |
The metadata for file system virtualization is corrupt and unreadable. |
| 0xC000CE03 | 支援檔案系統虛擬化的提供者太忙，因此無法完成此作業。 |
The provider that supports file system virtualization is too busy to complete this operation. |
| 0xC000CE04 | 支援檔案系統虛擬化的提供者未知。 |
The provider that supports file system virtualization is unknown. |
| 0xC000CF00 | 雲端檔案提供者是未知的。 |
The Cloud File provider is unknown. |
| 0xC000CF01 | 雲端檔案提供者未執行。 |
The Cloud File provider is not running. |
| 0xC000CF02 | 雲端檔案中繼資料已損毀且無法讀取。 |
The Cloud File metadata is corrupt and unreadable. |
| 0xC000CF03 | 因為「雲端檔案」中繼資料太大，所以無法完成作業。 |
The operation could not be completed because the Cloud File metadata is too large. |
| 0xC000CF06 | 因為不支援「雲端檔案」中繼資料版本，所以無法完成作業。 |
The operation could not be completed because the Cloud File metadata version is not supported. |
| 0xC000CF07 | 因為檔案不是「雲端檔案」，所以無法完成作業。 |
The operation could not be completed because the file is not a Cloud File. |
| 0xC000CF08 | 因為「雲端檔案」不同步，所以無法完成作業。 |
The operation could not be completed because the Cloud File is not in sync. |
| 0xC0010001 | 偵錯工具無法執行狀態變更。 |
Debugger did not perform a state change. |
| 0xC0010002 | 偵錯工具發現應用程式不在閒置中。 |
Debugger has found the application is not idle. |
| 0xC0020001 | 字串繫結無效。 |
The string binding is invalid. |
| 0xC0020002 | 連結控制代碼類型不正確。 |
The binding handle is not the correct type. |
| 0xC0020003 | 連結控制代碼不正確。 |
The binding handle is invalid. |
| 0xC0020004 | 不支援 RPC 通訊協定順序。 |
The RPC protocol sequence is not supported. |
| 0xC0020005 | RPC 通訊協定順序不正確。 |
The RPC protocol sequence is invalid. |
| 0xC0020006 | 不正確的 UUID 字串。 |
The string UUID is invalid. |
| 0xC0020007 | 端點格式不正確。 |
The endpoint format is invalid. |
| 0xC0020008 | 網路位址不正確。 |
The network address is invalid. |
| 0xC0020009 | 找不到端點。 |
No endpoint was found. |
| 0xC002000A | 逾時值不正確。 |
The timeout value is invalid. |
| 0xC002000B | 無法找到物件 UUID。 |
The object UUID was not found. |
| 0xC002000C | 物件 UUID 已登記。 |
The object UUID has already been registered. |
| 0xC002000D | 類型 UUID 已登記。 |
The type UUID has already been registered. |
| 0xC002000E | RPC 伺服器已在聽候。 |
The RPC server is already listening. |
| 0xC002000F | 未登錄任何通訊協定順序。 |
No protocol sequences have been registered. |
| 0xC0020010 | RPC 伺服器不在聽候。 |
The RPC server is not listening. |
| 0xC0020011 | 管理員類型不明。 |
The manager type is unknown. |
| 0xC0020012 | 不明的介面。 |
The interface is unknown. |
| 0xC0020013 | 沒有任何連結。 |
There are no bindings. |
| 0xC0020014 | 無任何通訊協定順序。 |
There are no protocol sequences. |
| 0xC0020015 | 無法建立端點。 |
The endpoint cannot be created. |
| 0xC0020016 | 資源不足無法完成此操作。 |
Not enough resources are available to complete this operation. |
| 0xC0020017 | RPC 伺服器無法使用。 |
The RPC server is unavailable. |
| 0xC0020018 | RPC 伺服器忙線中，無法完成此操作。 |
The RPC server is too busy to complete this operation. |
| 0xC0020019 | 網路選項無效。 |
The network options are invalid. |
| 0xC002001A | 這個執行緒沒有使用中的遠端程序呼叫。 |
There are no remote procedure calls active on this thread. |
| 0xC002001B | 遠端程序呼叫失敗。 |
The remote procedure call failed. |
| 0xC002001C | 遠端程序呼叫失敗且未執行。 |
The remote procedure call failed and did not execute. |
| 0xC002001D | 產生 RPC 協定錯誤。 |
An RPC protocol error occurred. |
| 0xC002001F | RPC 伺服器不支援傳輸語法。 |
The transfer syntax is not supported by the RPC server. |
| 0xC0020021 | 不支援 UUID 類型。 |
The type UUID is not supported. |
| 0xC0020022 | 標記不正確。 |
The tag is invalid. |
| 0xC0020023 | 陣列界限不正確。 |
The array bounds are invalid. |
| 0xC0020024 | 連結不包含項目名稱。 |
The binding does not contain an entry name. |
| 0xC0020025 | 名稱語法不正確。 |
The name syntax is invalid. |
| 0xC0020026 | 不支援名稱語法。 |
The name syntax is not supported. |
| 0xC0020028 | 無法取得網路位址以建立 UUID。 |
No network address is available to use to construct a UUID. |
| 0xC0020029 | 端點是一個複製項。 |
The endpoint is a duplicate. |
| 0xC002002A | 驗證類型不明。 |
The authentication type is unknown. |
| 0xC002002B | 呼叫的最大極限太小。 |
The maximum number of calls is too small. |
| 0xC002002C | 字串太長。 |
The string is too long. |
| 0xC002002D | 找不到 RPC 通訊協定順序。 |
The RPC protocol sequence was not found. |
| 0xC002002E | 程序數字超出範圍。 |
The procedure number is out of range. |
| 0xC002002F | 連結不包含任何驗證資訊。 |
The binding does not contain any authentication information. |
| 0xC0020030 | 驗證服務不明。 |
The authentication service is unknown. |
| 0xC0020031 | 驗證層級不明。 |
The authentication level is unknown. |
| 0xC0020032 | 資訊安全內容不正確。 |
The security context is invalid. |
| 0xC0020033 | 不明的授權服務。 |
The authorization service is unknown. |
| 0xC0020034 | 項目不正確。 |
The entry is invalid. |
| 0xC0020035 | 無法執行這項操作。 |
The operation cannot be performed. |
| 0xC0020036 | 端點對應表中無更多可用的端點。 |
There are no more endpoints available from the endpoint mapper. |
| 0xC0020037 | 未匯出任何介面。 |
No interfaces have been exported. |
| 0xC0020038 | 項目名稱不完整。 |
The entry name is incomplete. |
| 0xC0020039 | 版本選項無效。 |
The version option is invalid. |
| 0xC002003A | 不再有成員。 |
There are no more members. |
| 0xC002003B | 沒有項目可供解除匯出。 |
There is nothing to unexport. |
| 0xC002003C | 找不到介面。 |
The interface was not found. |
| 0xC002003D | 項目已存在。 |
The entry already exists. |
| 0xC002003E | 找不到項目。 |
The entry is not found. |
| 0xC002003F | 沒有可用的名稱服務。 |
The name service is unavailable. |
| 0xC0020040 | 網路位址家族無效。 |
The network address family is invalid. |
| 0xC0020041 | 不支援要求的操作。 |
The requested operation is not supported. |
| 0xC0020042 | 無可用的資訊安全內容以允許模擬。 |
No security context is available to allow impersonation. |
| 0xC0020043 | RPC 發生內部錯誤。 |
An internal error occurred in RPC. |
| 0xC0020044 | RPC 伺服器嘗試執行除以 0 的動作。 |
The RPC server attempted an integer divide by zero. |
| 0xC0020045 | RPC 伺服器中發生位址錯誤。 |
An addressing error occurred in the RPC server. |
| 0xC0020046 | RPC 伺服器上的浮點運算操作產生除以 0 的動作。 |
A floating point operation at the RPC server caused a divide by zero. |
| 0xC0020047 | RPC 伺服器產生浮點運算反向溢位。 |
A floating point underflow occurred at the RPC server. |
| 0xC0020048 | RPC 伺服器產生浮點溢位。 |
A floating point overflow occurred at the RPC server. |
| 0xC0020049 | 執行緒的遠端程序呼叫已在進行中。 |
A remote procedure call is already in progress for this thread. |
| 0xC002004A | 不再有連結。 |
There are no more bindings. |
| 0xC002004B | 找不到群組成員。 |
The group member was not found. |
| 0xC002004C | 無法建立端點對應資料庫項目。 |
The endpoint mapper database entry could not be created. |
| 0xC002004D | 物件 UUID 是空的 UUID。 |
The object UUID is the nil UUID. |
| 0xC002004F | 未登錄任何介面。 |
No interfaces have been registered. |
| 0xC0020050 | 遠端程序呼叫已取消。 |
The remote procedure call was cancelled. |
| 0xC0020051 | 連結控制代碼不包含所有需要的資訊。 |
The binding handle does not contain all required information. |
| 0xC0020052 | 遠端程序呼叫發生通訊失敗。 |
A communications failure occurred during a remote procedure call. |
| 0xC0020053 | 不支援請求的驗證層級。 |
The requested authentication level is not supported. |
| 0xC0020054 | 未登錄任何主體名稱。 |
No principal name registered. |
| 0xC0020055 | 指定的錯誤不是正確的 Windows RPC 錯誤碼。 |
The error specified is not a valid Windows RPC error code. |
| 0xC0020057 | 發生安全性封裝特定錯誤。 |
A security package specific error occurred. |
| 0xC0020058 | 執行緒未取消。 |
Thread is not cancelled. |
| 0xC0020062 | 不正確的非同步遠端程序呼叫控制代碼。 |
Invalid asynchronous remote procedure call handle. |
| 0xC0020063 | 這個操作的非同步 RPC 呼叫控制代碼不正確。 |
Invalid asynchronous RPC call handle for this operation. |
| 0xC0020064 | 拒絕存取 HTTP Proxy。 |
Access to the HTTP proxy is denied. |
| 0xC0020065 | HTTP Proxy 伺服器已拒絕連線，因為 Cookie 驗證失敗。 |
HTTP proxy server rejected the connection because the cookie authentication failed. |
| 0xC0030001 | 可用於自動處理連結的 RPC 伺服器清單已用盡。 |
The list of RPC servers available for auto-handle binding has been exhausted. |
| 0xC0030002 | 無法開啟由 DCERPCCHARTRANS 指定的檔案。 |
The file designated by DCERPCCHARTRANS cannot be opened. |
| 0xC0030003 | 包含字元轉譯表格的檔案少於 512 個位元組。 |
The file containing the character translation table has fewer than 512 bytes. |
| 0xC0030004 | 將 NULL 內容控制代碼以 [in] 參數傳送。 |
A null context handle is passed as an [in] parameter. |
| 0xC0030005 | 該內容控制代碼不符合已知的內容控制代碼。 |
The context handle does not match any known context handles. |
| 0xC0030006 | 內容控制代碼在呼叫時已被變更。 |
The context handle changed during a call. |
| 0xC0030007 | 傳遞到遠端程序呼叫的連結控制代碼不相符。 |
The binding handles passed to a remote procedure call do not match. |
| 0xC0030008 | 虛設常式無法取得呼叫控制代碼。 |
The stub is unable to get the call handle. |
| 0xC0030009 | NULL 參考指標被傳遞到虛設常式。 |
A null reference pointer was passed to the stub. |
| 0xC003000A | 列舉值超出範圍。 |
The enumeration value is out of range. |
| 0xC003000B | 位元組計數太小。 |
The byte count is too small. |
| 0xC003000C | 虛設常式接收到損壞的資料。 |
The stub received bad data. |
| 0xC0030059 | 不正確的編碼/解碼控制代碼操作。 |
Invalid operation on the encoding/decoding handle. |
| 0xC003005A | 序列化封裝的版本不相容。 |
Incompatible version of the serializing package. |
| 0xC003005B | RPC 虛設常式的版本不相容。 |
Incompatible version of the RPC stub. |
| 0xC003005C | RPC 管道物件不正確或已損毀。 |
The RPC pipe object is invalid or corrupted. |
| 0xC003005D | 在 RPC 管道物件上的操作嘗試不正確。 |
An invalid operation was attempted on an RPC pipe object. |
| 0xC003005E | 未支援的 RPC 管道版本。 |
Unsupported RPC pipe version. |
| 0xC003005F | RPC 管道物件已經關閉。 |
The RPC pipe object has already been closed. |
| 0xC0030060 | 在 RPC 呼叫完成之前全部的管道都已處理完成。 |
The RPC call completed before all pipes were processed. |
| 0xC0030061 | 沒有其他來自 RPC 管道的可用資料。 |
No more data is available from the RPC pipe. |
| 0xC0040035 | 系統 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. |
| 0xC0040036 | 某個轉譯器無法轉譯資源。 |
A translator failed to translate resources. |
| 0xC0040037 | 某個 IRQ 轉譯器無法轉譯資源。 |
A IRQ translator failed to translate resources. |
| 0xC0040038 | 驅動程式 %2 為子裝置 (%3) 傳回無效的識別碼。 |
Driver %2 returned invalid ID for a child device (%3). |
| 0xC0040039 | 重新發出指定的操作做為快取的 IO 操作 |
Reissue the given operation as a cached IO operation |
| 0xC00A0001 | 工作階段名稱 %1 不正確。 |
Session name %1 is invalid. |
| 0xC00A0002 | 通訊協定驅動程式 %1 不正確。 |
The protocol driver %1 is invalid. |
| 0xC00A0003 | 在系統路徑找不到通訊協定驅動程式 %1。 |
The protocol driver %1 was not found in the system path. |
| 0xC00A0006 | 終端機連線有一個擱置中的關閉操作。 |
A close operation is pending on the Terminal Connection. |
| 0xC00A0007 | 沒有可用的輸出緩衝區。 |
There are no free output buffers available. |
| 0xC00A0008 | 找不到 MODEM.INF 檔案。 |
The MODEM.INF file was not found. |
| 0xC00A0009 | MODEM.INF 中找不到數據機 (%1)。 |
The modem (%1) was not found in MODEM.INF. |
| 0xC00A000A | 數據機不接受傳送給它的命令。請檢查設定的數據機名稱是否與連結的數據機相符。 |
The modem did not accept the command sent to it.Verify the configured modem name matches the attached modem. |
| 0xC00A000B | 數據機沒有回應傳送給它的命令。請檢查數據機的電纜是否已正確接妥，電源是否已開啟。 |
The modem did not respond to the command sent to it.Verify the modem is properly cabled and powered on. |
| 0xC00A000C | 載波偵測失敗。或是因為斷線，所以載波遺失。 |
Carrier detect has failed or carrier has been dropped due to disconnect. |
| 0xC00A000D | 要求的時間內沒有偵測出撥號音。請檢查電話電纜是否已正確連接，且它是否能正常運作。 |
Dial tone not detected within required time.Verify phone cable is properly attached and functional. |
| 0xC00A000E | 回撥時偵測到遠端站台的忙線信號。 |
Busy signal detected at remote site on callback. |
| 0xC00A000F | 回撥時偵測出遠端站台的聲音。 |
Voice detected at remote site on callback. |
| 0xC00A0010 | 傳輸驅動程式錯誤 |
Transport driver error |
| 0xC00A0012 | 您所使用的用戶端並未被授權來使用這個系統。您的登入要求已被拒絕。 |
The client you are using is not licensed to use this system. Your logon request is denied. |
| 0xC00A0013 | 這系統已達到它授權登入的容許限制。請稍後再試。 |
The system has reached its licensed logon limit.Please try again later. |
| 0xC00A0014 | 系統授權已逾期。您的登入要求被拒。 |
The system license has expired. Your logon request is denied. |
| 0xC00A0015 | 找不到指定的工作階段。 |
The specified session cannot be found. |
| 0xC00A0016 | 指定的工作階段名稱已在使用中。 |
The specified session name is already in use. |
| 0xC00A0017 | 目前嘗試的工作無法完成，因為遠端桌面服務目前忙碌中。請稍後再試一次。其他使用者應該仍然可以登入。 |
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. |
| 0xC00A0018 | 嘗試連線到視訊模式不受目前用戶端支援的工作階段。 |
An attempt has been made to connect to a session whose video mode is not supported by the current client. |
| 0xC00A0022 | 應用程式嘗試啟用 DOS 圖形模式。DOS 圖形模式不受支援。 |
The application attempted to enable DOS graphics mode.DOS graphics mode is not supported. |
| 0xC00A0024 | 要求的操作只能在系統主控台上執行。這經常是驅動程式或系統 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. |
| 0xC00A0026 | 用戶端無法回應伺服器連線訊息。 |
The client failed to respond to the server connect message. |
| 0xC00A0027 | 不支援中斷主控台工作階段。 |
Disconnecting the console session is not supported. |
| 0xC00A0028 | 不支援將中斷的工作階段重新連線到主控台。 |
Reconnecting a disconnected session to the console is not supported. |
| 0xC00A002A | 拒絕在另一個工作階段遠端控制的要求。 |
The request to control another session remotely was denied. |
| 0xC00A002B | 已經要求處理程序進行工作階段存取，但尚未授與存取權。 |
A process has requested access to a session, but has not been granted those access rights. |
| 0xC00A002E | 終端機連線驅動程式 %1 不正確。 |
The Terminal Connection driver %1 is invalid. |
| 0xC00A002F | 在系統路徑中找不到終端機連線驅動程式 %1。 |
The Terminal Connection driver %1 was not found in the system path. |
| 0xC00A0030 | 無法由遠端控制要求的工作階段。這可能是因為這個工作階段已中斷連線，或目前沒使用者登入。您不能從系統主控台遠端控制工作階段。您也不能遠端控制您目前的工作階段。 |
The requested session cannot be controlled remotely.You cannot control your own session, a session that is trying to control your session,a session that has no user logged on, nor control other sessions from the console. |
| 0xC00A0031 | 要求的工作階段並非設定成允許遠端控制。 |
The requested session is not configured to allow remote control. |
| 0xC00A0032 | RDP 通訊協定元件 %2 偵測出通訊協定資料流中有錯誤，已經中斷用戶端連線。 |
The RDP protocol component %2 detected an error in the protocol stream and has disconnected the client. |
| 0xC00A0033 | 您想要建立終端機伺服器的連線要求被拒。這個複製的終端機用戶端沒有您的終端機伺服器用戶端授權號碼。請和您的系統管理員連絡以獲得有效的終端機伺服器用戶端授權號碼。請按 [確定] 繼續。 |
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 Client.Please call your system administrator for help in entering a valid, unique license number for this Terminal Server Client.Click OK to continue. |
| 0xC00A0034 | 您想要建立終端機伺服器的連線要求被拒。您的終端機伺服器用戶端授權號碼目前正被其他使用者使用。請和您的系統管理員連絡以獲得有效的終端機伺服器用戶端授權號碼。請按 [確定] 繼續。 |
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 new copy of the Terminal Server Client with a valid, unique license number.Click OK to continue. |
| 0xC00A0035 | 主控台的遠端控制已終止，原因是顯示模式已經變更。在遠端控制工作階段中變更顯示模式是不受支援的。 |
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. |
| 0xC00A0036 | 無法終止遠端控制，因為所指定的工作階段目前不受遠端控制。 |
Remote control could not be terminated because the specified session is not currently being remotely controlled. |
| 0xC00A0037 | 您的互動登入特殊權限已停用。請連絡您的系統管理員。 |
Your interactive logon privilege has been disabled.Please contact your system administrator. |
| 0xC00A0038 | 終端機伺服器安全性階層已偵測到通訊協定資料流中的錯誤，並已中斷用戶端的連線。用戶端 IP: %2。 |
The Terminal Server security layer detected an error in the protocol stream and has disconnected the client.Client IP: %2. |
| 0xC00A0039 | 目標工作階段與目前的工作階段不相容。 |
The target session is incompatible with the current session. |
| 0xC00A003A | 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. |
| 0xC00B0001 | 資源載入器找不到 MUI 檔案。 |
The resource loader failed to find MUI file. |
| 0xC00B0002 | 資源載入器無法載入 MUI 檔案，因為該檔案無法通過驗證。 |
The resource loader failed to load MUI file because the file fail to pass validation. |
| 0xC00B0003 | RC Manifest 損毀，並含有不需要的資料或不支援的版本，或者遺失必要項目。 |
The RC Manifest is corrupted with garbage data or unsupported version or missing required item. |
| 0xC00B0004 | RC Manifest 具有不正確的文化特性名稱。 |
The RC Manifest has invalid culture name. |
| 0xC00B0005 | RC Manifest 具有不正確的 ultimatefallback 名稱。 |
The RC Manifest has invalid ultimatefallback name. |
| 0xC00B0006 | 資源載入器快取未載入 MUI 項目。 |
The resource loader cache doesn't have loaded MUI entry. |
| 0xC00B0007 | 使用者已經停止資源列舉。 |
User stopped resource enumeration. |
| 0xC0130001 | 這個叢集節點不正確。 |
The cluster node is not valid. |
| 0xC0130002 | 這個叢集節點已經存在了。 |
The cluster node already exists. |
| 0xC0130003 | 某個節點正在加入叢集中。 |
A node is in the process of joining the cluster. |
| 0xC0130004 | 這個叢集節點找不到。 |
The cluster node was not found. |
| 0xC0130005 | 找不到這個叢集的本機節點資訊。 |
The cluster local node information was not found. |
| 0xC0130006 | 這個叢集網路已經存在了。 |
The cluster network already exists. |
| 0xC0130007 | 找不到這個叢集網路。 |
The cluster network was not found. |
| 0xC0130008 | 這個叢集網路介面已經存在了。 |
The cluster network interface already exists. |
| 0xC0130009 | 找不到這個叢集網路介面。 |
The cluster network interface was not found. |
| 0xC013000A | 這個叢集要求不適用於這個物件。 |
The cluster request is not valid for this object. |
| 0xC013000B | 這個叢集網路提供者不正確。 |
The cluster network provider is not valid. |
| 0xC013000D | 無法連線到叢集節點。 |
The cluster node is not reachable. |
| 0xC013000E | 這個叢集節點不是叢集的成員之一。 |
The cluster node is not a member of the cluster. |
| 0xC013000F | 目前沒有叢集加入操作在進行中。 |
A cluster join operation is not in progress. |
| 0xC0130010 | 這個叢集網路不正確。 |
The cluster network is not valid. |
| 0xC0130011 | 沒有可用的網路介面卡。 |
No network adapters are available. |
| 0xC0130012 | 這個叢集節點已啟動。 |
The cluster node is up. |
| 0xC0130013 | 這個叢集節點已經暫停。 |
The cluster node is paused. |
| 0xC0130014 | 這個叢集節點並未暫停。 |
The cluster node is not paused. |
| 0xC0130015 | 沒有可用的叢集資訊安全內容。 |
No cluster security context is available. |
| 0xC0130016 | 這個叢集網路不是設定為內部叢集通訊之用。 |
The cluster network is not configured for internal cluster communication. |
| 0xC0130017 | 叢集節點已受污染。 |
The cluster node has been poisoned. |
| 0xC0130018 | 路徑不屬於叢集共用磁碟區。 |
The path does not belong to a cluster shared volume. |
| 0xC0130019 | 叢集共用磁碟區不是掛接在本機。 |
The cluster shared volume is not locally mounted. |
| 0xC0130020 | 因為正在讀取 oplock 中斷，所以作業失敗。 |
The operation has failed because read oplock break is in progress. |
| 0xC0130021 | 作業失敗。CSVFS 必須暫停並重新整理資訊。 |
The operation has failed. CSVFS has to pause and refresh information. |
| 0xC0130022 | 作業失敗。CSVFS 不允許在重新導向模式封鎖 I/O。 |
The operation has failed. CSVFS does not allow block i/o in redirected mode. |
| 0xC0130023 | 作業失敗。CSVFS 不是重新導向模式。 |
The operation has failed. CSVFS is not in redirected mode. |
| 0xC0130024 | CSVFS 正在將該操作判定為失敗，因為它處於正在清空狀態。 |
CSVFS is failing operation because it is in draining state. |
| 0xC0130025 | 操作已經失敗，因為正在建立快照。 |
The operation has failed because snapshot creation is in progress. |
| 0xC0130026 | 操作已在下層檔案系統完成，但 CSV 正在將它判定為失敗，因為它處於正在清空狀態。 |
The operation has succeeded on the down level file system, but CSV is failing it because it is in draining state. |
| 0xC0130027 | 協調節點上的 Volsnap 傳回錯誤，指出此磁碟區上沒有任何快照。 |
Volsnap on the coordinating node returned an error indicating that there is no snapshots on this volume. |
| 0xC0130028 | 操作失敗，因為 CSV 磁碟區無法在此檔案物件上指定的時間內復原。 |
The operation has failed because CSV volume was not able to recover in time specified on this file object. |
| 0xC0130029 | 作業失敗，因為 CSV 已將此檔案物件判定為無效。 |
The operation has failed because CSV has invalidated this file object. |
| 0xC0130030 | 只有 CSV 協調器節點上才支援此作業。 |
This operation is supported only on the CSV coordinator node. |
| 0xC0130031 | 叢集 CAM 偵測到有人正嘗試回覆票證。 |
Cluster CAM has detected that somone is trying to reply ticket. |
| 0xC0140001 | 嘗試執行無效的 AML opcode |
An attempt was made to run an invalid AML opcode |
| 0xC0140002 | AML 直譯器堆疊已溢位 |
The AML Interpreter Stack has overflowed |
| 0xC0140003 | 發生不一致的狀態 |
An inconsistent state has occurred |
| 0xC0140004 | 嘗試存取在其界線外的陣列 |
An attempt was made to access an array outside of its bounds |
| 0xC0140005 | 未指定所需的引數 |
A required argument was not specified |
| 0xC0140006 | 發生嚴重的錯誤 |
A fatal error has occurred |
| 0xC0140007 | 指定了不正確的 SuperName |
An invalid SuperName was specified |
| 0xC0140008 | 指定了不正確的引數類型 |
An argument with an incorrect type was specified |
| 0xC0140009 | 指定了不正確的物件類型 |
An object with an incorrect type was specified |
| 0xC014000A | 指定了不正確的目標類型 |
A target with an incorrect type was specified |
| 0xC014000B | 指定了不正確的引數個數 |
An incorrect number of arguments were specified |
| 0xC014000C | 位址無法轉譯 |
An address failed to translate |
| 0xC014000D | 指定了不正確的事件類型 |
An incorrect event type was specified |
| 0xC014000E | 目標的處理常式已存在 |
A handler for the target already exists |
| 0xC014000F | 指定了不正確的目標資料 |
Invalid data for the target was specified |
| 0xC0140010 | 指定了不正確的目標區域 |
An invalid region for the target was specified |
| 0xC0140011 | 嘗試存取定義範圍外的欄位 |
An attempt was made to access a field outside of the defined range |
| 0xC0140012 | 無法獲得全域性系統鎖定 |
The Global system lock could not be acquired |
| 0xC0140013 | 嘗試將 ACPI 子系統重新初始化 |
An attempt was made to reinitialize the ACPI subsystem |
| 0xC0140014 | ACPI 子系統尚未初始化 |
The ACPI subsystem has not been initialized |
| 0xC0140015 | 指定了不正確的 mutex |
An incorrect mutex was specified |
| 0xC0140016 | mutex 目前沒有被擁有 |
The mutex is not currently owned |
| 0xC0140017 | 非擁有者的處理程序嘗試存取 mutex |
An attempt was made to access the mutex by a process that was not the owner |
| 0xC0140018 | 當存取 Region Space 時發生錯誤 |
An error occurred during an access to Region Space |
| 0xC0140019 | 嘗試使用不正確的表格 |
An attempt was made to use an incorrect table |
| 0xC0140020 | ACPI 事件的登錄失敗 |
The registration of an ACPI event failed |
| 0xC0140021 | 有一個 ACPI 電源物件無法轉移狀態 |
An ACPI Power Object failed to transition state |
| 0xC0150001 | 所要求的區段不存在於啟用內容中。 |
The requested section is not present in the activation context. |
| 0xC0150002 | Windows 無法處理應用程式連結資訊。請參照系統事件記錄檔以取得進一步資訊。 |
Windows was not able to process the application binding information.Please refer to your System Event Log for further information. |
| 0xC0150003 | 應用程式連結資料的格式不正確。 |
The application binding data format is invalid. |
| 0xC0150004 | 參照的組合沒有安裝在您的系統中。 |
The referenced assembly is not installed on your system. |
| 0xC0150005 | 資訊清單檔案的開端沒有必需的標籤和格式資訊。 |
The manifest file does not begin with the required tag and format information. |
| 0xC0150006 | 資訊清單檔案包含一個或以上的語法錯誤。 |
The manifest file contains one or more syntax errors. |
| 0xC0150007 | 應用程式嘗試啟動已停用的啟用內容。 |
The application attempted to activate a disabled activation context. |
| 0xC0150008 | 在所有使用中的啟用內容中都找不到所要求的對應機碼。 |
The requested lookup key was not found in any active activation context. |
| 0xC0150009 | 應用程式必需的元件版本和另一個使用中的元件版本衝突。 |
A component version required by the application conflicts with another component version already active. |
| 0xC015000A | 要求的啟用內容區段類型與 API 所使用的查詢不相符。 |
The type requested activation context section does not match the query API used. |
| 0xC015000B | 缺乏系統資源，所以必須在目前的執行緒停用孤立啟用。 |
Lack of system resources has required isolated activation to be disabled for the current thread of execution. |
| 0xC015000C | 找不到參照組合。 |
The referenced assembly could not be found. |
| 0xC015000E | 企圖設定處理程序預設啟用內容的嘗試失敗，原因是處理程序預設啟用內容已經設定了。 |
An attempt to set the process default activation context failed because the process default activation context was already set. |
| 0xC015000F | 正在停用的啟用內容不是最近啟動的那一個。 |
The activation context being deactivated is not the most recently activated one. |
| 0xC0150010 | 正在停用的啟用內容在目前的執行緒中未使用。 |
The activation context being deactivated is not active for the current thread of execution. |
| 0xC0150011 | 正在停用的啟用內容已經停用了。 |
The activation context being deactivated has already been deactivated. |
| 0xC0150012 | 無法產生系統預設組合的啟用內容。 |
The activation context of system default assembly could not be generated. |
| 0xC0150013 | 由孤立設備所使用的元件要求中斷程序。 |
A component used by the isolation facility has requested to terminate the process. |
| 0xC0150014 | 屬於執行中的執行緒的啟用內容堆疊已毀損。 |
The activation context activation stack for the running thread of execution is corrupt. |
| 0xC0150015 | 此處理程序或執行緒的應用程式隔離中繼資料已損毀。 |
The application isolation metadata for this process or thread has become corrupt. |
| 0xC0150016 | 識別碼中的屬性值不在合法的範圍內。 |
The value of an attribute in an identity is not within the legal range. |
| 0xC0150017 | 識別碼中的屬性名稱不在合法的範圍內。 |
The name of an attribute in an identity is not within the legal range. |
| 0xC0150018 | 識別碼的同個屬性包含兩個定義。 |
An identity contains two definitions for the same attribute. |
| 0xC0150019 | 識別碼字串的格式錯誤。原因可能是結尾的逗號、超過兩個未命名的屬性、遺失屬性名稱或遺失屬性值所造成。 |
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. |
| 0xC015001A | 元件存放區已損毀。 |
The component store has been corrupted. |
| 0xC015001B | 元件檔與元件資訊清單中所存在的驗證資訊不相符合。 |
A component's file does not match the verification information present in the component manifest. |
| 0xC015001C | 各個資訊清單的識別碼都相同，但是內容不同。 |
The identities of the manifests are identical but their contents are different. |
| 0xC015001D | 元件識別碼不同。 |
The component identities are different. |
| 0xC015001E | 組合不是部署。 |
The assembly is not a deployment. |
| 0xC015001F | 檔案不是組合的一部分。 |
The file is not a part of the assembly. |
| 0xC0150020 | 進階安裝程式在安裝或服務期間失敗。 |
An advanced installer failed during setup or servicing. |
| 0xC0150021 | XML 宣告的字元編碼不符合文件中使用的編碼。 |
The character encoding in the XML declaration did not match the encoding used in the document. |
| 0xC0150022 | 資訊清單的大小超過允許的上限。 |
The size of the manifest exceeds the maximum allowed. |
| 0xC0150023 | 設定未登錄。 |
The setting is not registered. |
| 0xC0150024 | 一或多個必要的交易成員不存在。 |
One or more required members of the transaction are not present. |
| 0xC0150025 | SMI 基本安裝程式在安裝或服務期間失敗。 |
The SMI primitive installer failed during setup or servicing. |
| 0xC0150026 | 一般命令可執行檔傳回結果，表示發生失敗。 |
A generic command executable returned a result that indicates failure. |
| 0xC0150027 | 元件在其資訊清單遺失檔案驗證資訊。 |
A component is missing file verification information in its manifest. |
| 0xC0190001 | 函數嘗試使用的名稱，已保留給其他交易使用。 |
The function attempted to use a name that is reserved for use by another transaction. |
| 0xC0190002 | 與此作業相關的交易控制代碼無效。 |
The transaction handle associated with this operation is not valid. |
| 0xC0190003 | 在交易的內容中已進行要求的動作，但是交易不再作用。 |
The requested operation was made in the context of a transaction that is no longer active. |
| 0xC0190004 | 無法順利初始化交易管理員。不支援交易的作業。 |
The Transaction Manager was unable to be successfully initialized. Transacted operations are not supported. |
| 0xC0190005 | 未啟動指定資源管理員內的交易支援，或因為錯誤而關閉。 |
Transaction support within the specified resource manager is not started or was shut down due to an error. |
| 0xC0190006 | RM 的中繼資料已損毀。RM 將無法運作。 |
The metadata of the RM has been corrupted. The RM will not function. |
| 0xC0190007 | 資源管理員已嘗試準備其未順利加入的交易。 |
The resource manager has attempted to prepare a transaction that it has not successfully joined. |
| 0xC0190008 | 指定的目錄未包含檔案系統資源管理員。 |
The specified directory does not contain a file system resource manager. |
| 0xC019000A | 遠端伺服器或共用不支援交易的檔案作業。 |
The remote server or share does not support transacted file operations. |
| 0xC019000B | 要求的檔案系統資源管理員記錄大小無效。 |
The requested log size for the file system resource manager is invalid. |
| 0xC019000C | 遠端伺服器已傳送不符的版本號碼或 Fid 給以交易開啟的檔案。 |
The remote server sent mismatching version number or Fid for a file opened with transactions. |
| 0xC019000F | RM 嘗試登錄的通訊協定已存在。 |
The RM tried to register a protocol that already exists. |
| 0xC0190010 | 傳播交易的嘗試失敗。 |
The attempt to propagate the Transaction failed. |
| 0xC0190011 | 要求的傳播通訊協定未登錄為 CRM。 |
The requested propagation protocol was not registered as a CRM. |
| 0xC0190012 | 交易物件已具有上層登記，而呼叫者嘗試的作業可能建立新的上層。只會允許一個上層登記。 |
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 allowed. |
| 0xC0190013 | 交易物件處於目前狀態時，要求的作業無效。 |
The requested operation is not valid on the Transaction object in its current state. |
| 0xC0190014 | 呼叫者已呼叫回應 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. |
| 0xC0190015 | 因為交易已取消，所以要執行要求的作業已經太晚。 |
It is too late to perform the requested operation, since the Transaction has already been aborted. |
| 0xC0190016 | 因為交易已認可，所以要執行要求的作業已經太晚。 |
It is too late to perform the requested operation, since the Transaction has already been committed. |
| 0xC0190017 | 傳遞到 NtPushTransaction 或 NtPullTransaction 之緩衝區的格式無效。 |
The buffer passed in to NtPushTransaction or NtPullTransaction is not in a valid format. |
| 0xC0190018 | 與執行緒關聯的目前交易內容不是交易物件的有效控制代碼。 |
The current transaction context associated with the thread is not a valid handle to a transaction object. |
| 0xC0190019 | 嘗試在交易資源管理員的記錄檔中建立空間失敗。已在事件記錄檔中記錄失敗狀態。 |
An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log. |
| 0xC0190021 | 對應到控制代碼的物件 (檔案、資料流、連結) 已被交易儲存點復原刪除。 |
The object (file, stream, link) corresponding to the handle has been deleted by a transaction savepoint rollback. |
| 0xC0190022 | 找不到此開啟之交易檔案的指定檔案迷你版本。 |
The specified file miniversion was not found for this transacted file open. |
| 0xC0190023 | 找到指定的檔案迷你版本，但已失效。可能是因為交易儲存點復原而造成。 |
The specified file miniversion was found but has been invalidated. Most likely cause is a transaction savepoint rollback. |
| 0xC0190024 | 只能在建立迷你版本的交易內容中開啟迷你版本。 |
A miniversion may only be opened in the context of the transaction that created it. |
| 0xC0190025 | 無法使用修改存取來開啟迷你版本。 |
It is not possible to open a miniversion with modify access. |
| 0xC0190026 | 無法再為此資料流建立任何的迷你版本。 |
It is not possible to create any more miniversions for this stream. |
| 0xC0190028 | 交易已讓控制代碼失效。最可能的原因是當交易結束或回復到儲存點時，檔案或開啟的控制代碼上存在記憶體對應。 |
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. |
| 0xC0190030 | 記錄資料已毀損。 |
The log data is corrupt. |
| 0xC0190032 | 因為負責交易結果的資源管理員已中斷連線，所以無法取得交易結果。 |
The transaction outcome is unavailable because the resource manager responsible for it has disconnected. |
| 0xC0190033 | 因為問題徵募不是上層徵募，所以拒絕要求。 |
The request was rejected because the enlistment in question is not a superior enlistment. |
| 0xC0190036 | 無法以交易開啟檔案，因為檔案的識別碼依賴未解決交易的結果。 |
The file cannot be opened transactionally, because its identity depends on the outcome of an unresolved transaction. |
| 0xC0190037 | 因為其他交易依賴這個屬性不會改變的事實，所以無法執行作業。 |
The operation cannot be performed because another transaction is depending on the fact that this property will not change. |
| 0xC0190038 | 作業將牽涉到單一檔案及兩個交易資源管理員，因此不允許作業。 |
The operation would involve a single file with two transactional resource managers and is therefore not allowed. |
| 0xC0190039 | $Txf 目錄必須為空，這個作業才能成功。 |
The $Txf directory must be empty for this operation to succeed. |
| 0xC019003A | 作業會讓交易資源管理員處於不一致的狀態，因此不允許作業。 |
The operation would leave a transactional resource manager in an inconsistent state and is therefore not allowed. |
| 0xC019003B | 因為交易管理員沒有記錄檔，所以無法完成作業。 |
The operation could not be completed because the transaction manager does not have a log. |
| 0xC019003C | 因為已經執行之前排程的復原，或排程的復原已進入佇列等候執行，所以無法排程復原。 |
A rollback could not be scheduled because a previously scheduled rollback has already executed or been queued for execution. |
| 0xC019003D | 檔案或目錄 %hs 上的交易中繼資料屬性已損毀且無法讀取。 |
The transactional metadata attribute on the file or directory %hs is corrupt and unreadable. |
| 0xC019003E | 因為交易為使用中，所以無法完成加密作業。 |
The encryption operation could not be completed because a transaction is active. |
| 0xC019003F | 不允許在交易中開啟此物件。 |
This object is not allowed to be opened in a transaction. |
| 0xC0190040 | 不支援在交易下記憶體對應 (建立對應區段) 遠端檔案。 |
Memory mapping (creating a mapped section) a remote file under a transaction is not supported. |
| 0xC0190043 | 需要升級才能讓資源管理員徵募，但交易已設定為不允許升級。 |
Promotion was required in order to allow the resource manager to enlist, but the transaction was set to disallow it. |
| 0xC0190044 | 已在未解決的交易中開啟此檔案以進行修改，且只可由交易讀取器開啟來執行。 |
This file is open for modification in an unresolved transaction and may be opened for execute only by a transacted reader. |
| 0xC0190045 | 因為交易之前未被凍結，所以已略過取消凍結交易的要求。 |
The request to thaw frozen transactions was ignored because transactions had not previously been frozen. |
| 0xC0190046 | 因為正在進行凍結，所以無法取消凍結交易。 |
Transactions cannot be frozen because a freeze is already in progress. |
| 0xC0190047 | 目標磁碟區不是快照磁碟區。只有在掛接為快照的磁碟區上，此作業才有效。 |
The target volume is not a snapshot volume. This operation is only valid on a volume mounted as a snapshot. |
| 0xC0190048 | 因為檔案在交易上開啟，所以儲存點作業失敗。不允許這項動作。 |
The savepoint operation failed because files are open on the transaction. This is not permitted. |
| 0xC0190049 | 因為交易正在檔案上作用，所以無法完成鬆散作業。 |
The sparse operation could not be completed because a transaction is active on the file. |
| 0xC019004A | 建立 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. |
| 0xC019004B | 已在區段物件上嘗試 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. |
| 0xC019004C | 因為發生暫時性的狀況 (例如資源不足)，所以交易資源管理員目前無法接受交易工作。 |
The transactional resource manager cannot currently accept transacted work due to a transient condition such as low resources. |
| 0xC019004D | 交易資源管理員有太多無法中止的待處理交易。交易資源管理員已關閉。 |
The transactional resource manager had too many tranactions outstanding that could not be aborted. The transactional resource manger has been shut down. |
| 0xC019004E | 因為找不到指定的交易，所以無法開啟該交易。 |
The specified Transaction was unable to be opened, because it was not found. |
| 0xC019004F | 因為找不到指定的 ResourceManager，所以無法開啟該 ResourceManager。 |
The specified ResourceManager was unable to be opened, because it was not found. |
| 0xC0190050 | 因為找不到指定的 Enlistment，所以無法開啟該 Enlistment。 |
The specified Enlistment was unable to be opened, because it was not found. |
| 0xC0190051 | 因為找不到指定的 TransactionManager，所以無法開啟該 TransactionManager。 |
The specified TransactionManager was unable to be opened, because it was not found. |
| 0xC0190052 | 無法建立或開啟指定的物件，因為物件關聯的 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. |
| 0xC0190053 | 指定的 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. |
| 0xC0190054 | 無法完成呼叫以在此 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. |
| 0xC0190055 | 關聯的交易管理員或資源管理員已關閉，因此控制代碼已無效。 |
Because the associated transaction manager or resource manager has been closed, the handle is no longer valid. |
| 0xC0190056 | 無法完成壓縮操作，因為該檔案上有作用中的交易。 |
The compression operation could not be completed because a transaction is active on the file. |
| 0xC0190057 | 無法在這個上層徵募執行指定的操作，因為徵募不是以 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. |
| 0xC0190058 | 無法執行指定的操作，因為記錄的記錄太長。發生這個狀況的原因有二: 這個交易的徵募太多，或是代表這些徵募記錄的組合 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. |
| 0xC0190059 | 無法完成連結追蹤操作，因為交易是使用中狀態。 |
The link tracking operation could not be completed because a transaction is active. |
| 0xC019005A | 無法在交易中執行此操作。 |
This operation cannot be performed in a transaction. |
| 0xC019005B | 核心交易管理員已中止或放棄交易，因為它已封鎖轉送程序。 |
The kernel transaction manager had to abort or forget the transaction because it blocked forward progress. |
| 0xC019005C | 提供的 TransactionManager 識別碼與 TransactionManager 記錄檔中所記錄的識別碼不相符。 |
The TransactionManager identity that was supplied did not match the one recorded in the TransactionManager's log file. |
| 0xC019005D | 無法繼續此快照操作，因為無法凍結處於目前狀態的交易資源管理員。請再試一次。 |
This snapshot operation cannot continue because a transactional resource manager cannot be frozen in its current state. Please try again. |
| 0xC019005E | 無法使用指定的 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. |
| 0xC019005F | 這個交易沒有上層徵募。 |
The transaction does not have a superior enlistment. |
| 0xC0190060 | 控制代碼與其交易已不再正確地關聯。它可能在交易資源管理員中開啟，隨後被強制重新啟動。請關閉該控制代碼，然後開啟新的控制代碼。 |
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. |
| 0xC0190061 | 無法執行指定的操作，因為交易中未徵募資源管理員。 |
The specified operation could not be performed because the resource manager is not enlisted in the transaction. |
| 0xC01A0001 | 記錄服務發現無效的記錄磁區。 |
Log service found an invalid log sector. |
| 0xC01A0002 | 記錄服務遇到具有無效區塊同位檢查的記錄磁區。 |
Log service encountered a log sector with invalid block parity. |
| 0xC01A0003 | 記錄服務遇到重新對應的記錄磁區。 |
Log service encountered a remapped log sector. |
| 0xC01A0004 | 記錄服務遇到部分或未完成的記錄區塊。 |
Log service encountered a partial or incomplete log block. |
| 0xC01A0005 | 記錄服務遇到嘗試存取使用中記錄範圍外的資料。 |
Log service encountered an attempt access data outside the active log range. |
| 0xC01A0006 | 記錄服務使用者記錄排列緩衝區已耗盡。 |
Log service user log marshalling buffers are exhausted. |
| 0xC01A0007 | 記錄服務遇到從具有無效讀取內容之排列區域讀取的嘗試。 |
Log service encountered an attempt read from a marshalling area with an invalid read context. |
| 0xC01A0008 | 記錄服務遇到無效的記錄重新啟動區域。 |
Log service encountered an invalid log restart area. |
| 0xC01A0009 | 記錄服務遇到無效的記錄區塊版本。 |
Log service encountered an invalid log block version. |
| 0xC01A000A | 記錄服務遇到無效的記錄區塊。 |
Log service encountered an invalid log block. |
| 0xC01A000B | 記錄服務遇到讀取具有無效讀取模式的嘗試。 |
Log service encountered an attempt to read the log with an invalid read mode. |
| 0xC01A000D | 記錄服務遇到毀損的中繼資料檔案。 |
Log service encountered a corrupted metadata file. |
| 0xC01A000E | 記錄服務遇到的中繼資料檔案無法由記錄檔案系統建立。 |
Log service encountered a metadata file that could not be created by the log file system. |
| 0xC01A000F | 記錄服務遇到資料不一致的中繼資料檔案。 |
Log service encountered a metadata file with inconsistent data. |
| 0xC01A0010 | 記錄服務遇到錯誤配置或放置保留空間的嘗試。 |
Log service encountered an attempt to erroneously allocate or dispose reservation space. |
| 0xC01A0011 | 記錄服務無法刪除記錄檔或檔案系統容器。 |
Log service cannot delete log file or file system container. |
| 0xC01A0012 | 記錄服務已達到配置給記錄檔的可允許容器上限。 |
Log service has reached the maximum allowable containers allocated to a log file. |
| 0xC01A0013 | 記錄服務已嘗試超過記錄開頭向後讀取或寫入。 |
Log service has attempted to read or write backwards past the start of the log. |
| 0xC01A0014 | 因為相同類型的原則已存在，所以無法安裝記錄原則。 |
Log policy could not be installed because a policy of the same type is already present. |
| 0xC01A0015 | 問題記錄原則此時未依要求安裝。 |
Log policy in question was not installed at the time of the request. |
| 0xC01A0016 | 記錄上安裝的原則集無效。 |
The installed set of policies on the log is invalid. |
| 0xC01A0017 | 問題記錄上的原則導致作業無法完成。 |
A policy on the log in question prevented the operation from completing. |
| 0xC01A0018 | 因為記錄空間已由封存結尾所釘選，所以無法收回。 |
Log space cannot be reclaimed because the log is pinned by the archive tail. |
| 0xC01A0019 | 記錄不是記錄檔中的記錄。 |
Log record is not a record in the log file. |
| 0xC01A001A | 保留的記錄數或保留記錄數的調整無效。 |
Number of reserved log records or the adjustment of the number of reserved log records is invalid. |
| 0xC01A001B | 保留的記錄空間或記錄空間的調整無效。 |
Reserved log space or the adjustment of the log space is invalid. |
| 0xC01A001C | 新的或現有封存結尾或作用中記錄的基底無效。 |
A new or existing archive tail or base of the active log is invalid. |
| 0xC01A001D | 記錄空間已耗盡。 |
Log space is exhausted. |
| 0xC01A001E | 記錄為多工，不允許直接寫入實體記錄。 |
Log is multiplexed, no direct writes to the physical log is allowed. |
| 0xC01A001F | 因為記錄是固定記錄，所以作業失敗。 |
The operation failed because the log is a dedicated log. |
| 0xC01A0020 | 作業需要封存內容。 |
The operation requires an archive context. |
| 0xC01A0021 | 記錄封存進行中。 |
Log archival is in progress. |
| 0xC01A0022 | 作業需要非暫時的記錄，但記錄為暫時。 |
The operation requires a non-ephemeral log, but the log is ephemeral. |
| 0xC01A0023 | 記錄必須至少有兩個容器，才能供讀取或寫入。 |
The log must have at least two containers before it can be read from or written to. |
| 0xC01A0024 | 記錄用戶端已在資料流上登錄。 |
A log client has already registered on the stream. |
| 0xC01A0025 | 記錄用戶端未在資料流上登錄。 |
A log client has not been registered on the stream. |
| 0xC01A0026 | 已發出要求來處理記錄已滿的狀況。 |
A request has already been made to handle the log full condition. |
| 0xC01A0027 | 記錄服務嘗試從記錄容器讀取時發生錯誤。 |
Log service encountered an error when attempting to read from a log container. |
| 0xC01A0028 | 記錄服務嘗試寫入記錄容器時發生錯誤。 |
Log service encountered an error when attempting to write to a log container. |
| 0xC01A0029 | 記錄服務嘗試開啟記錄容器時發生錯誤。 |
Log service encountered an error when attempting open a log container. |
| 0xC01A002A | 記錄服務嘗試進行要求的動作時，遇到無效的容器狀態。 |
Log service encountered an invalid container state when attempting a requested action. |
| 0xC01A002B | 記錄服務狀態錯誤，無法執行要求的動作。 |
Log service is not in the correct state to perform a requested action. |
| 0xC01A002C | 因為記錄空間已釘選，所以無法收回記錄空間。 |
Log space cannot be reclaimed because the log is pinned. |
| 0xC01A002D | 記錄中繼資料清除失敗。 |
Log metadata flush failed. |
| 0xC01A002E | 記錄上的安全性及其容器不一致。 |
Security on the log and its containers is inconsistent. |
| 0xC01A002F | 記錄已附加到記錄檔或保留項目有所變更，但無法清除記錄檔。 |
Records were appended to the log or reservation changes were made, but the log could not be flushed. |
| 0xC01A0030 | 保留項目耗用了大部分的記錄檔空間，所以已釘選記錄檔。請釋放一些保留的記錄以釋出空間。 |
The log is pinned due to reservation consuming most of the log space. Free some reserved records to make space available. |
| 0xC01B00EA | {顯示驅動程式停止回應}%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 upload data about this failure to Microsoft. |
| 0xC01C0001 | 篩選未定義此操作的處理常式。 |
A handler was not defined by the filter for this operation. |
| 0xC01C0002 | 已針對此物件定義內容。 |
A context is already defined for this object. |
| 0xC01C0003 | 非同步要求對於此操作而言不正確。 |
Asynchronous requests are not valid for this operation. |
| 0xC01C0004 | 篩選器管理員使用內部錯誤碼來判斷是否應強制 fastio 作業關閉 IRP 路徑。迷你篩選器不應傳回這個值。 |
Internal error code used by the filter manager to determine if a fastio operation should be forced down the IRP path. Mini-filters should never return this value. |
| 0xC01C0005 | 發出不正確的名稱要求。目前無法抓取要求的名稱。 |
An invalid name request was made. The name requested cannot be retrieved at this time. |
| 0xC01C0006 | 目前將此操作指派給背景工作執行緒以進行進一步處理並不安全，因為它可能會導致發生資源鎖死的情況。 |
Posting this operation to a worker thread for further processing is not safe at this time because it could lead to a system deadlock. |
| 0xC01C0007 | 當篩選器嘗試登錄時，篩選器管理員未初始化。請確定篩選器管理員已載入為驅動程式。 |
The Filter Manager was not initialized when a filter tried to register. Make sure that the Filter Manager is getting loaded as a driver. |
| 0xC01C0008 | 篩選器未就緒，無法連結至磁碟區，因為它尚未完成初始化 (FltStartFiltering 尚未被呼叫)。 |
The filter is not ready for attachment to volumes because it has not finished initializing (FltStartFiltering has not been called). |
| 0xC01C0009 | 篩選器目前必須清除所有操作特定內容，因為在操作完成之前，內容已被較低階的驅動程式從系統移除。 |
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. |
| 0xC01C000A | 篩選器管理員發生無法修復的內部錯誤，因此操作失敗。這通常是因為篩選器從預先操作回呼傳回不正確的值所造成。 |
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. |
| 0xC01C000B | 正在刪除針對此動作指定的物件，因此要求的動作目前無法完成。 |
The object specified for this action is in the process of being deleted, therefore the action requested cannot be completed at this time. |
| 0xC01C000C | 必須針對此類型的內容使用非分頁集區。 |
Non-paged pool must be used for this type of context. |
| 0xC01C000D | 為操作提供了重複的處理常式定義。 |
A duplicate handler definition has been provided for an operation. |
| 0xC01C000E | 回呼資料佇列已停用。 |
The callback data queue has been disabled. |
| 0xC01C000F | 目前不要將篩選器連結到該磁碟區。 |
Do not attach the filter to the volume at this time. |
| 0xC01C0010 | 目前不要將篩選器與該磁碟區中斷連結。 |
Do not detach the filter from the volume at this time. |
| 0xC01C0011 | 指定之磁碟區的此高度已有執行個體存在。 |
An instance already exists at this altitude on the volume specified. |
| 0xC01C0012 | 指定的磁碟區中已有同名的執行個體存在。 |
An instance already exists with this name on the volume specified. |
| 0xC01C0013 | 系統找不到指定的篩選器。 |
The system could not find the filter specified. |
| 0xC01C0014 | 系統找不到指定的磁碟區。 |
The system could not find the volume specified. |
| 0xC01C0015 | 系統找不到指定的執行個體。 |
The system could not find the instance specified. |
| 0xC01C0016 | 找不到指定之要求的已登錄內容配置定義。 |
No registered context allocation definition was found for the given request. |
| 0xC01C0017 | 在登錄內容時指定了不正確的參數。 |
An invalid parameter was specified during context registration. |
| 0xC01C0018 | 在篩選器管理員的名稱快取中找不到要求的名稱，也無法從檔案系統抓取名稱。 |
The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system. |
| 0xC01C0019 | 指定之磁碟區的要求裝置物件不存在。 |
The requested device object does not exist for the given volume. |
| 0xC01C001A | 指定的磁碟區已掛接。 |
The specified volume is already mounted. |
| 0xC01C001B | 指定的交易內容已徵募到交易中 |
The specified Transaction Context is already enlisted in a transaction |
| 0xC01C001C | 特定內容已連結到另一個物件 |
The specifiec context is already attached to another object |
| 0xC01C0020 | 沒有任何等候者在等候篩選器對此訊息的回覆。 |
No waiter is present for the filter's reply to this message. |
| 0xC01C0023 | filesystem 資料庫資源使用中。目前無法完成註冊。 |
The filesystem database resource is in use. Registration cannot complete at this time. |
| 0xC01D0001 | 無法取得監視器描述元。 |
Monitor descriptor could not be obtained. |
| 0xC01D0002 | 此版本不支援所取得之監視器描述元的格式。 |
Format of the obtained monitor descriptor is not supported by this release. |
| 0xC01D0003 | 取得之監視器描述元的總和檢查碼無效。 |
Checksum of the obtained monitor descriptor is invalid. |
| 0xC01D0004 | 監視器描述元包含的標準時間區塊無效。 |
Monitor descriptor contains an invalid standard timing block. |
| 0xC01D0005 | 其中一個 MSMonitorClass WMI 子類別的 WMI 資料區塊登錄失敗。 |
WMI data block registration failed for one of the MSMonitorClass WMI subclasses. |
| 0xC01D0006 | 提供的監視器描述元區塊已損毀或不包含監視器的詳細序號。 |
Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number. |
| 0xC01D0007 | 提供的監視器描述元區塊已損毀或不包含監視器的使用者易記名稱。 |
Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name. |
| 0xC01D0008 | 指定的 (位移、大小) 區域中沒有任何監視器描述元資料。 |
There is no monitor descriptor data at the specified (offset, size) region. |
| 0xC01D0009 | 監視器描述元包含的詳細時間區塊無效。 |
Monitor descriptor contains an invalid detailed timing block. |
| 0xC01D000A | 監視器描述元包含不正確的製造日期。 |
Monitor descriptor contains invalid manufacture date. |
| 0xC01E0000 | 需要獨佔模式擁有權，才能建立不受管理的主要配置。 |
Exclusive mode ownership is needed to create unmanaged primary allocation. |
| 0xC01E0001 | 驅動程式需要更多 DMA 緩衝區空間，才能完成要求的作業。 |
The driver needs more DMA buffer space in order to complete the requested operation. |
| 0xC01E0002 | 指定的顯示器介面卡控制代碼無效。 |
Specified display adapter handle is invalid. |
| 0xC01E0003 | 指定的顯示器介面卡及所有其狀態已重設。 |
Specified display adapter and all of its state has been reset. |
| 0xC01E0004 | 驅動程式堆疊與預期的驅動程式模組不符。 |
The driver stack doesn't match the expected driver model. |
| 0xC01E0005 | 發生呈現的動作，但是最後卻出現變更的桌面模式 |
Present happened but ended up into the changed desktop mode |
| 0xC01E0006 | 因為桌面閉塞，所以無法呈現任何項目 |
Nothing to present due to desktop occlusion |
| 0xC01E0007 | 因為拒絕桌面的存取，所以無法呈現 |
Not able to present due to denial of desktop access |
| 0xC01E0008 | 無法呈現色彩轉換 |
Not able to present with color convertion |
| 0xC01E0009 | 核心驅動程式偵測到和使用者模式驅動程式的版本不符。 |
The kernel driver detected a version mismatch between it and the user mode driver. |
| 0xC01E000B | 已停用目前的重新導向 (桌面視窗管理子系統已經關閉)。 |
Present redirection is disabled (desktop windowing management subsystem is off). |
| 0xC01E000C | 前一個獨佔 VidPn 來源擁有者已釋出其擁有權 |
Previous exclusive VidPn source owner has released its ownership |
| 0xC01E000D | Window DC 無法用於簡報 |
Window DC is not available for presentation |
| 0xC01E000E | 已停用無視窗呈現 (桌面視窗管理子系統已經關閉)。 |
Windowless present is disabled (desktop windowing management subsystem is off). |
| 0xC01E0100 | 視訊記憶體不足，無法完成作業。 |
Not enough video memory available to complete the operation. |
| 0xC01E0101 | 無法探查並鎖定配置的基本記憶體。 |
Couldn't probe and lock the underlying memory of an allocation. |
| 0xC01E0102 | 配置目前忙碌中。 |
The allocation is currently busy. |
| 0xC01E0103 | 參照的物件已達到參考計數上限，且無法再繼續參照。 |
An object being referenced has already reached the maximum reference count and can't be referenced any further. |
| 0xC01E0104 | 因為某些現存的條件導致問題無法解決。應該稍後再嘗試看還有沒有問題。 |
A problem couldn't be solved due to some currently existing condition. The problem should be tried again later. |
| 0xC01E0105 | 因為某些現存的條件導致問題無法解決。應該立即嘗試看還有沒有問題。 |
A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately. |
| 0xC01E0106 | 配置無效。 |
The allocation is invalid. |
| 0xC01E0107 | 目前沒有任何非拌和光圈可使用。 |
No more unswizzling aperture are currently available. |
| 0xC01E0108 | 光圈無法拌和目前的配置。 |
The current allocation can't be unswizzled by an aperture. |
| 0xC01E0109 | 因為無法收回已釘選的配置，要求失敗。 |
The request failed because a pinned allocation can't be evicted. |
| 0xC01E0110 | 無法在配置的目前區段位置中，針對指定作業使用配置。 |
The allocation can't be used from its current segment location for the specified operation. |
| 0xC01E0111 | 在目前的命令緩衝區中無法使用封鎖的配置。 |
A locked allocation can't be used in the current command buffer. |
| 0xC01E0112 | 參照的配置已永久關閉。 |
The allocation being referenced has been closed permanently. |
| 0xC01E0113 | 正在參照的配置執行個體無效。 |
An invalid allocation instance is being referenced. |
| 0xC01E0114 | 正在參照的配置控制代碼無效。 |
An invalid allocation handle is being referenced. |
| 0xC01E0115 | 正在參照的配置不屬於目前的裝置。 |
The allocation being referenced doesn't belong to the current device. |
| 0xC01E0116 | 指定的配置遺失內容。 |
The specified allocation lost its content. |
| 0xC01E0200 | 在指定的裝置上偵測到 GPU 例外狀況。將無法排程裝置。 |
GPU exception is detected on the given device. The device is not able to be scheduled. |
| 0xC01E0300 | 指定的 VidPN 拓撲無效。 |
Specified VidPN topology is invalid. |
| 0xC01E0301 | 指定的 VidPN 拓撲有效，但顯示器介面卡的這個模組不予以支援。 |
Specified VidPN topology is valid but is not supported by this model of the display adapter. |
| 0xC01E0302 | 指定的 VidPN 拓撲有效，但因為目前的資源配置，所以此時顯示器介面卡不予以支援。 |
Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources. |
| 0xC01E0303 | 指定的 VidPN 控制代碼無效。 |
Specified VidPN handle is invalid. |
| 0xC01E0304 | 指定的視訊呈現來源無效。 |
Specified video present source is invalid. |
| 0xC01E0305 | 指定的視訊呈現目標無效。 |
Specified video present target is invalid. |
| 0xC01E0306 | 不支援指定的 VidPN 樣式 (例如，至少有兩個釘選的模式無法交互運作)。 |
Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional). |
| 0xC01E0308 | 指定的 VidPN 來源模式集無效。 |
Specified VidPN source mode set is invalid. |
| 0xC01E0309 | 指定的 VidPN 目標模式集無效。 |
Specified VidPN target mode set is invalid. |
| 0xC01E030A | 指定的視訊訊號頻率無效。 |
Specified video signal frequency is invalid. |
| 0xC01E030B | 指定的視訊訊號作用區無效。 |
Specified video signal active region is invalid. |
| 0xC01E030C | 指定的視訊訊號總區域無效。 |
Specified video signal total region is invalid. |
| 0xC01E0310 | 指定的視訊呈現來源模式無效。 |
Specified video present source mode is invalid. |
| 0xC01E0311 | 指定的視訊呈現目標模式無效。 |
Specified video present target mode is invalid. |
| 0xC01E0312 | 已釘選的模式必須保留在 VidPN 之交互運作樣式列舉的集合上。 |
Pinned mode must remain in the set on VidPN's cofunctional modality enumeration. |
| 0xC01E0313 | 指定的視訊呈現路徑已存在 VidPN 拓撲中。 |
Specified video present path is already in VidPN's topology. |
| 0xC01E0314 | 指定的模式已存在於模式集中。 |
Specified mode is already in the mode set. |
| 0xC01E0315 | 指定的視訊呈現來源集無效。 |
Specified video present source set is invalid. |
| 0xC01E0316 | 指定的視訊呈現目標集無效。 |
Specified video present target set is invalid. |
| 0xC01E0317 | 指定的視訊呈現來源已存在視訊呈現來源集中。 |
Specified video present source is already in the video present source set. |
| 0xC01E0318 | 指定的視訊呈現目標已存在視訊呈現目標集中。 |
Specified video present target is already in the video present target set. |
| 0xC01E0319 | 指定的 VidPN 呈現路徑無效。 |
Specified VidPN present path is invalid. |
| 0xC01E031A | 迷你連接埠沒有增強指定 VidPN 拓撲的建議。 |
Miniport has no recommendation for augmentation of the specified VidPN's topology. |
| 0xC01E031B | 指定的監視器頻率範圍集無效。 |
Specified monitor frequency range set is invalid. |
| 0xC01E031C | 指定的監視器頻率範圍無效。 |
Specified monitor frequency range is invalid. |
| 0xC01E031D | 指定的頻率範圍不在指定的監視器頻率範圍集中。 |
Specified frequency range is not in the specified monitor frequency range set. |
| 0xC01E031F | 指定的頻率範圍已存在指定的監視器頻率範圍集中。 |
Specified frequency range is already in the specified monitor frequency range set. |
| 0xC01E0320 | 指定的模式集已過期。請重新取得新模式集。 |
Specified mode set is stale. Please reacquire the new mode set. |
| 0xC01E0321 | 指定的監視器來源模式集無效。 |
Specified monitor source mode set is invalid. |
| 0xC01E0322 | 指定的監視器來源模式無效。 |
Specified monitor source mode is invalid. |
| 0xC01E0323 | 迷你連接埠針對提供一個可提供目前顯示器介面卡配置的功能性 VidPN 要求沒有任何建議。 |
Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration. |
| 0xC01E0324 | 指定模式的識別碼已由集合中的其他模式使用中。 |
ID of the specified mode is already used by another mode in the set. |
| 0xC01E0325 | 系統無法判定顯示器介面卡及連接到介面卡之監視器皆支援的模式。 |
System failed to determine a mode that is supported by both the display adapter and the monitor connected to it. |
| 0xC01E0326 | 視訊呈現目標的數目必須大於或等於視訊呈現來源的數目。 |
Number of video present targets must be greater than or equal to the number of video present sources. |
| 0xC01E0327 | 指定的呈現路徑不在 VidPN 拓撲中。 |
Specified present path is not in VidPN's topology. |
| 0xC01E0328 | 顯示卡必須至少具有一個視訊呈現來源。 |
Display adapter must have at least one video present source. |
| 0xC01E0329 | 顯示卡必須至少具有一個視訊呈現目標。 |
Display adapter must have at least one video present target. |
| 0xC01E032A | 指定的監視器描述元集無效。 |
Specified monitor descriptor set is invalid. |
| 0xC01E032B | 指定的監視器描述元無效。 |
Specified monitor descriptor is invalid. |
| 0xC01E032C | 指定的描述元不在指定的監視器描述元集中。 |
Specified descriptor is not in the specified monitor descriptor set. |
| 0xC01E032D | 指定的描述元已存在指定的監視器描述元集中。 |
Specified descriptor is already in the specified monitor descriptor set. |
| 0xC01E032E | 指定監視器描述元的識別碼已由集合中的其他描述元使用中。 |
ID of the specified monitor descriptor is already used by another descriptor in the set. |
| 0xC01E032F | 指定的視訊呈現目標子集類型無效。 |
Specified video present target subset type is invalid. |
| 0xC01E0330 | 兩個或兩個以上的指定資源不如介面語意定義般的互相關聯。 |
Two or more of the specified resources are not related to each other, as defined by the interface semantics. |
| 0xC01E0331 | 指定視訊呈現來源的識別碼已由集合中的其他來源使用中。 |
ID of the specified video present source is already used by another source in the set. |
| 0xC01E0332 | 指定視訊呈現目標的識別碼已由集合中的其他目標使用中。 |
ID of the specified video present target is already used by another target in the set. |
| 0xC01E0333 | 指定的 VidPN 來源無法使用，因為沒有可用的 VidPN 目標可連接。 |
Specified VidPN source cannot be used because there is no available VidPN target to connect it to. |
| 0xC01E0334 | 剛裝的監視器無法與顯示器介面卡產生關聯。 |
Newly arrived monitor could not be associated with a display adapter. |
| 0xC01E0335 | 問題顯示器介面卡沒有關聯的 VidPN 管理員。 |
Display adapter in question does not have an associated VidPN manager. |
| 0xC01E0336 | 問題顯示器介面卡的 VidPN 管理員沒有作用中的 VidPN。 |
VidPN manager of the display adapter in question does not have an active VidPN. |
| 0xC01E0337 | 指定的 VidPN 拓撲已過期。請重新取得新拓撲。 |
Specified VidPN topology is stale. Please reacquire the new topology. |
| 0xC01E0338 | 在指定的視訊呈現目標上沒有連接的監視器。 |
There is no monitor connected on the specified video present target. |
| 0xC01E0339 | 指定的來源不是指定的 VidPN 拓撲的一部分。 |
Specified source is not part of the specified VidPN's topology. |
| 0xC01E033A | 指定的主要表面大小無效。 |
Specified primary surface size is invalid. |
| 0xC01E033B | 指定可見區域大小無效。 |
Specified visible region size is invalid. |
| 0xC01E033C | 指定的分散大小無效。 |
Specified stride is invalid. |
| 0xC01E033D | 指定的像素格式無效。 |
Specified pixel format is invalid. |
| 0xC01E033E | 指定的色彩底色無效。 |
Specified color basis is invalid. |
| 0xC01E033F | 指定的像素值存取模式無效。 |
Specified pixel value access mode is invalid. |
| 0xC01E0340 | 指定的目標不是指定的 VidPN 拓撲的一部分。 |
Specified target is not part of the specified VidPN's topology. |
| 0xC01E0341 | 無法取得顯示器模式管理介面。 |
Failed to acquire display mode management interface. |
| 0xC01E0342 | 指定的 VidPN 來源已為 DMM 用戶端所擁有，在該用戶端釋放前無法使用。 |
Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it. |
| 0xC01E0343 | 指定的 VidPN 為使用中，所以無法存取。 |
Specified VidPN is active and cannot be accessed. |
| 0xC01E0344 | 指定的 VidPN 呈現路徑重要性序數無效。 |
Specified VidPN present path importance ordinal is invalid. |
| 0xC01E0345 | 指定的 VidPN 呈現路徑內容幾何轉換無效。 |
Specified VidPN present path content geometry transformation is invalid. |
| 0xC01E0346 | 相對 VidPN 呈現路徑上不支援指定的內容幾何轉換。 |
Specified content geometry transformation is not supported on the respective VidPN present path. |
| 0xC01E0347 | 指定的 Gamma ramp 無效。 |
Specified gamma ramp is invalid. |
| 0xC01E0348 | 相對 VidPN 呈現路徑上不支援指定的 Gamma ramp。 |
Specified gamma ramp is not supported on the respective VidPN present path. |
| 0xC01E0349 | 相對 VidPN 呈現路徑上不支援多重取樣。 |
Multi-sampling is not supported on the respective VidPN present path. |
| 0xC01E034A | 指定的模式不在指定的模式集中。 |
Specified mode is not in the specified mode set. |
| 0xC01E034D | 指定的 VidPN 拓撲建議原因無效。 |
Specified VidPN topology recommendation reason is invalid. |
| 0xC01E034E | 指定的 VidPN 呈現路徑內容類型無效。 |
Specified VidPN present path content type is invalid. |
| 0xC01E034F | 指定的 VidPN 呈現路徑內容保護類型無效。 |
Specified VidPN present path copy protection type is invalid. |
| 0xC01E0350 | 在任何時間內，指定 VidPN 來源/目標中都不能存在一個以上的未指派模式集。 |
No more than one unassigned mode set can exist at any given time for a given VidPN source/target. |
| 0xC01E0352 | 指定的掃描線排序類型不正確。 |
Specified scanline ordering type is invalid. |
| 0xC01E0353 | 指定的 VidPN 不允許拓撲變更。 |
Topology changes are not allowed for the specified VidPN. |
| 0xC01E0354 | 已經在指定的拓撲中使用所有可用的重要性序數。 |
All available importance ordinals are already used in specified topology. |
| 0xC01E0355 | 指定之主要表面的私密格式屬性和目前的主要表面不同 |
Specified primary surface has a different private format attribute than the current primary surface |
| 0xC01E0356 | 指定的模式剪除演算法不正確 |
Specified mode pruning algorithm is invalid |
| 0xC01E0357 | 指定的監視器功能來源不正確。 |
Specified monitor capability origin is invalid. |
| 0xC01E0358 | 指定的監視器頻率範圍限制不正確。 |
Specified monitor frequency range constraint is invalid. |
| 0xC01E0359 | 已經達到呈現路徑的支援數目上限。 |
Maximum supported number of present paths has been reached. |
| 0xC01E035A | Miniport 已要求取消指定之 VidPN 的拓撲的指定來源的增強 (augmentation)。 |
Miniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology. |
| 0xC01E035B | 無法識別指定的用戶端類型。 |
Specified client type was not recognized. |
| 0xC01E035C | 此介面卡上並未設定用戶端 VidPN (例如，此介面卡上未發生由使用者模式起始的模式變更)。 |
Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet). |
| 0xC01E0400 | 指定的顯示器介面卡子裝置已具有與其連接的外部裝置。 |
Specified display adapter child device already has an external device connected to it. |
| 0xC01E0401 | 指定的顯示器介面卡子裝置不支援報告描述元曝光。 |
Specified display adapter child device does not support descriptor exposure. |
| 0xC01E0430 | 顯示器介面卡未連結到任何其他介面卡上。 |
The display adapter is not linked to any other adapters. |
| 0xC01E0431 | 尚未列舉連結組態中的主要介面卡。 |
Lead adapter in a linked configuration was not enumerated yet. |
| 0xC01E0432 | 尚未列舉連結組態中的某些鏈結介面卡。 |
Some chain adapters in a linked configuration were not enumerated yet. |
| 0xC01E0433 | 因為發生無法辨識的失敗，所以連結介面卡的鏈結還無法啟動。 |
The chain of linked adapters is not ready to start because of an unknown failure. |
| 0xC01E0434 | 當鏈結連結未啟動時，已嘗試啟動主要連結顯示器介面卡。 |
An attempt was made to start a lead link display adapter when the chain links were not started yet. |
| 0xC01E0435 | 當鏈結連結關閉時，已嘗試啟動主要連結顯示器介面卡。 |
An attempt was made to power up a lead link display adapter when the chain links were powered down. |
| 0xC01E0436 | 介面卡連結的狀態不一致。不是所有的介面卡都處於預期的 PNP/Power 狀態。 |
The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state. |
| 0xC01E0438 | 驅動程式嘗試啟動的與 POST 顯示器介面卡驅動程式嘗試啟動的不同。 |
The driver trying to start is not the same as the driver for the POSTed display adapter. |
| 0xC01E043B | 正在嘗試的操作需要顯示器介面卡處於完全非使用中狀態。 |
An operation is being attempted that requires the display adapter to be in a quiescent state. |
| 0xC01E0500 | 驅動程式不支援 OPM。 |
The driver does not support OPM. |
| 0xC01E0501 | 驅動程式不支援 COPP。 |
The driver does not support COPP. |
| 0xC01E0502 | 驅動程式不支援 UAB。 |
The driver does not support UAB. |
| 0xC01E0503 | 指定的加密參數無效。 |
The specified encrypted parameters are invalid. |
| 0xC01E0505 | 傳遞到此函數的 GDI 顯示器裝置沒有任何作用中受保護的輸出。 |
The GDI display device passed to this function does not have any active protected outputs. |
| 0xC01E050B | 發生內部錯誤，造成作業失敗。 |
An internal error caused an operation to fail. |
| 0xC01E050C | 因為呼叫者傳遞到無效的 OPM 使用者模式控制代碼，所以函數失敗。 |
The function failed because the caller passed in an invalid OPM user mode handle. |
| 0xC01E050E | 因為傳遞到函數的憑證緩衝區太小，所以無法傳回憑證。 |
A certificate could not be returned because the certificate buffer passed to the function was too small. |
| 0xC01E050F | DxgkDdiOpmCreateProtectedOutput 函式無法建立受保護的輸出，因為視訊呈現目標處於跨螢幕模式。 |
The DxgkDdiOpmCreateProtectedOutput function could not create a protected output because the Video Present Target is in spanning mode. |
| 0xC01E0510 | DxgkDdiOpmCreateProtectedOutput 函式無法建立受保護的輸出，因為視訊呈現目標處於劇院模式。 |
The DxgkDdiOpmCreateProtectedOutput function could not create a protected output because the Video Present Target is in theater mode. |
| 0xC01E0511 | 函數失敗，因為顯示卡的硬體功能掃描無法確認圖形硬體。 |
The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware. |
| 0xC01E0512 | 傳送到此函數的 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. |
| 0xC01E0513 | 受保護的輸出無法啟用高頻寬數位內容保護 High-bandwidth Digital Content Protection (HDCP) 系統，因為它不支援 HDCP。 |
The protected output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP. |
| 0xC01E0514 | 受保護的輸出無法啟用類比複製保護 Analogue Copy Protection (ACP)，因為它不支援 ACP。 |
The protected output cannot enable Analogue Copy Protection (ACP) because it does not support ACP. |
| 0xC01E0515 | 受保護的輸出無法啟用內容產生管理系統類比 Content Generation Management System Analogue (CGMS-A) 保護技術，因為它不支援 CGMS-A。 |
The protected output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A. |
| 0xC01E0516 | DxgkDdiOPMGetInformation 函數無法傳回使用之 SRM 的版本，因為應用程式從未順利傳送 SRM 到受保護的輸出。 |
The DxgkDdiOPMGetInformation function cannot return the version of the SRM being used because the application never successfully passed an SRM to the protected output. |
| 0xC01E0517 | DxgkDdiOPMConfigureProtectedOutput 函數無法啟用指定的輸出保護技術，因為輸出的螢幕解析度太高。 |
The DxgkDdiOPMConfigureProtectedOutput function cannot enable the specified output protection technology because the output's screen resolution is too high. |
| 0xC01E0518 | DxgkDdiOPMConfigureProtectedOutput 函數無法啟用 HDCP，因為顯示器介面卡的 HDCP 硬體已經由其他實體輸出所使用。 |
The DxgkDdiOPMConfigureProtectedOutput function cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs. |
| 0xC01E051A | 因為作業系統狀態已經變更，所以作業系統已非同步地摧毀這個 OPM 受保護的輸出。這個錯誤發生的原因通常是這個受保護輸出關聯的監視器 PDO 已經移除、這個受保護輸出關聯的監視器 PDO 已經停止、或受保護輸出的工作階段已經成為非主控台工作階段。 |
The operating system asynchronously destroyed this OPM protected output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this protected output was removed, the monitor PDO associated with this protected output was stopped, or the protected output's session became a non-console session. |
| 0xC01E051C | DxgkDdiOPMGetCOPPCompatibleInformation、DxgkDdiOPMGetInformation 或 DxgkDdiOPMConfigureProtectedOutput 函數失敗。當呼叫者嘗試使用 COPP 特定命令，而受保護的輸出僅含有 OPM 語意時，就會傳回此錯誤。 |
Either the DxgkDdiOPMGetCOPPCompatibleInformation, DxgkDdiOPMGetInformation, or DxgkDdiOPMConfigureProtectedOutput function failed. This error is returned when the caller tries to use a COPP specific command while the protected output has OPM semantics only. |
| 0xC01E051D | 如果傳遞的序號不是預期中的序號或是傳遞的 OMAC 數值不正確，DxgkDdiOPMGetInformation 與 DxgkDdiOPMGetCOPPCompatibleInformation 函數會傳回這個錯誤碼。 |
The DxgkDdiOPMGetInformation and DxgkDdiOPMGetCOPPCompatibleInformation functions return this error code if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid. |
| 0xC01E051E | 在顯示驅動程式內發生的意外的錯誤導致函數失敗。 |
The function failed because an unexpected error occurred inside of a display driver. |
| 0xC01E0520 | 如果顯示驅動程式不支援 DXGKMDT_OPM_GET_ACP_AND_CGMSA_SIGNALING 與 DXGKMDT_OPM_SET_ACP_AND_CGMSA_SIGNALING GUID，DxgkDdiOPMGetCOPPCompatibleInformation 與 DxgkDdiOPMConfigureProtectedOutput 函數會傳回這個錯誤。 |
The DxgkDdiOPMGetCOPPCompatibleInformation and DxgkDdiOPMConfigureProtectedOutput functions return this error if the display driver does not support the DXGKMDT_OPM_GET_ACP_AND_CGMSA_SIGNALING and DXGKMDT_OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs. |
| 0xC01E0521 | 如果傳遞的序號不是預期中的序號或是傳遞的 OMAC 數值不正確，DxgkDdiOPMConfigureProtectedOutput 函數會傳回這個錯誤碼。 |
The DxgkDdiOPMConfigureProtectedOutput 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. |
| 0xC01E0580 | 連接到指定視訊輸出的監視器沒有 I2C 匯流排。 |
The monitor connected to the specified video output does not have an I2C bus. |
| 0xC01E0581 | I2C 匯流排上沒有任何裝置具有指定的位址。 |
No device on the I2C bus has the specified address. |
| 0xC01E0582 | 傳輸資料給 I2C 匯流排上的裝置時，發生錯誤。 |
An error occurred while transmitting data to the device on the I2C bus. |
| 0xC01E0583 | 從 I2C 匯流排上的裝置接收資料時，發生錯誤。 |
An error occurred while receiving data from the device on the I2C bus. |
| 0xC01E0584 | 監視器不支援指定的 VCP 程式碼。 |
The monitor does not support the specified VCP code. |
| 0xC01E0585 | 從監視器接收到的資料無效。 |
The data received from the monitor is invalid. |
| 0xC01E0586 | 函數失敗，因為當作業系統使用 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. |
| 0xC01E0587 | 監視器回傳不符合 ACCESS.bus 3.0、DDC/CI 1.1 或 MCCS 2 修訂 1 規格的 DDC/CI 功能字串。 |
A 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. |
| 0xC01E0589 | 因為 DDC/CI 訊息的命令欄位包含不正確的值，操作失敗。 |
An operation failed because a DDC/CI message had an invalid value in its command field. |
| 0xC01E058A | 發生此錯誤的原因是 DDC/CI 訊息的長度欄位包含不正確的值。 |
An error occurred because the field length of a DDC/CI message contained an invalid value. |
| 0xC01E058B | 發生此錯誤的原因是 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. |
| 0xC01E058C | 因為傳遞給函數的監視器控制代碼不正確，所以此函數失敗。 |
This function failed because an invalid monitor handle was passed to it. |
| 0xC01E058D | 作業系統已非同步摧毀符合這個控制代碼的監視器，因為作業系統的狀態已變更。這個錯誤的發生原因，通常是與這個控制代碼關聯的監視器 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. |
| 0xC01E05E0 | 只有當程式是在本機主控台工作階段使用時，才能使用此功能。若程式是在遠端桌面工作階段或終端機伺服器工作階段中執行，無法使用此功能。 |
This function can only be used if a program is running in the local console session. It cannot be used if a program is running on a remote desktop session or on a terminal server session. |
| 0xC01E05E1 | 這個函數找不到符合指定 GDI 顯示裝置名稱的實際 GDI 顯示裝置。 |
This function cannot find an actual GDI display device which corresponds to the specified GDI display device name. |
| 0xC01E05E2 | 因為指定的 GDI 顯示器裝置未連結到 Windows 桌面，所以函數失敗。 |
The function failed because the specified GDI display device was not attached to the Windows desktop. |
| 0xC01E05E3 | 因為 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. |
| 0xC01E05E4 | 因為有無效的指標參數傳送給它，所以函數失敗。如果指標參數是 NULL 則為無效，它會指向無效的位址、核心模式位址，或者未正確配置它。 |
The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, it points to an invalid address, it points to a kernel mode address or it is not correctly aligned. |
| 0xC01E05E5 | 因為傳遞到函數的 GDI 裝置沒有與其關聯的任何監視器，所以這個函數失敗。 |
This function failed because the GDI device passed to it did not have any monitors associated with it. |
| 0xC01E05E6 | 傳遞到函數的陣列無法保存函數應該複製到陣列中的所有資料。 |
An array passed to the function cannot hold all of the data that the function must copy into the array. |
| 0xC01E05E8 | 因為目前的工作階段正在改變其類型，所以函數失敗。當目前的工作階段正在改變其類型時，不能呼叫這個函數。目前有三種工作階段類型: 主控台、中斷連線及遠端。 |
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. |
| 0xC0210000 | 此磁碟區已由 BitLocker 磁碟機加密鎖定。 |
This volume is locked by BitLocker Drive Encryption. |
| 0xC0210001 | 磁碟區並未加密，且沒有可用的金鑰。 |
The volume is not encrypted, no key is available. |
| 0xC0210002 | 加密磁碟區的控制區塊不正確。 |
The control block for the encrypted volume is not valid. |
| 0xC0210003 | 磁碟區無法加密，因為該磁碟區上的可用空間不足。 |
The volume cannot be encrypted because it does not have enough free space. |
| 0xC0210004 | 無法加密磁碟區，因為檔案系統不支援。 |
The volume cannot be encrypted because the file system is not supported. |
| 0xC0210005 | 檔案系統大小超過磁碟分割表格中的磁碟分割大小。 |
The file system size is larger than the partition size in the partition table. |
| 0xC0210006 | 檔案系統並未延伸到磁碟區結尾。 |
The file system does not extend to the end of the volume. |
| 0xC0210007 | 如果磁碟區已裝載檔案系統，就無法執行此操作。 |
This operation cannot be performed while a file system is mounted on the volume. |
| 0xC0210008 | BitLocker 磁碟機加密未包含在此 Windows 版本中。 |
BitLocker Drive Encryption is not included with this version of Windows. |
| 0xC0210009 | 要求的動作無法在目前的磁碟區狀態下執行。 |
Requested action not allowed in the current volume state. |
| 0xC021000A | 提供的資料格式不正確。 |
Data supplied is malformed. |
| 0xC021000B | 磁碟區未繫結到系統。 |
The volume is not bound to the system. |
| 0xC021000C | 磁碟區不是資料磁碟區。 |
That volume is not a data volume. |
| 0xC021000D | 轉換磁碟區時發生讀取操作失敗。 |
A read operation failed while converting the volume. |
| 0xC021000E | 轉換磁碟區時發生寫入操作失敗。 |
A write operation failed while converting the volume. |
| 0xC021000F | 加密磁碟區的控制區塊已由另一個執行緒更新。請再試一次。 |
The control block for the encrypted volume was updated by another thread. Try again. |
| 0xC0210010 | 加密演算法不支援該磁碟區的磁區大小。 |
The encryption algorithm does not support the sector size of that volume. |
| 0xC0210011 | BitLocker 修復驗證失敗。 |
BitLocker recovery authentication failed. |
| 0xC0210012 | 該磁碟區不是作業系統磁碟區。 |
That volume is not the OS volume. |
| 0xC0210013 | 無法從外部媒體讀取 BitLocker 啟動金鑰或修復密碼。 |
The BitLocker startup key or recovery password could not be read from external media. |
| 0xC0210014 | BitLocker 啟動金鑰或修復密碼檔已損毀或不正確。 |
The BitLocker startup key or recovery password file is corrupt or invalid. |
| 0xC0210015 | 無法從啟動金鑰或修復密碼取得 BitLocker 加密金鑰。 |
The BitLocker encryption key could not be obtained from the startup key or recovery password. |
| 0xC0210016 | 已停用信賴平台模組 (TPM)。 |
The Trusted Platform Module (TPM) is disabled. |
| 0xC0210017 | 信賴平台模組 (TPM) 儲存根金鑰 (SRK) 的授權資料不是零。 |
The authorization data for the Storage Root Key (SRK) of the Trusted Platform Module (TPM) is not zero. |
| 0xC0210018 | 系統開機資訊已變更，或信賴平台模組 (TPM) 已鎖定 BitLocker 加密金鑰的存取權 (直到電腦重新啟動)。 |
The system boot information changed or the Trusted Platform Module (TPM) locked out access to BitLocker encryption keys until the computer is restarted. |
| 0xC0210019 | 無法從信賴平台模組 (TPM) 取得 BitLocker 加密金鑰。 |
The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM). |
| 0xC021001A | 無法從信賴平台模組 (TPM) 與 PIN 取得 BitLocker 加密金鑰。 |
The BitLocker encryption key could not be obtained from the Trusted Platform Module (TPM) and PIN. |
| 0xC021001B | 開機應用程式雜湊與開啟 BitLocker 時所運算的雜湊不相符。 |
A boot application hash does not match the hash computed when BitLocker was turned on. |
| 0xC021001C | 啟用 BitLocker 後，不支援開機設定資料 (BCD) 設定或該資料已發生變更。 |
The Boot Configuration Data (BCD) settings are not supported or have changed since BitLocker was enabled. |
| 0xC021001D | 已啟用開機偵錯。請執行 bcdedit 將它關閉。 |
Boot debugging is enabled. Run bcdedit to turn it off. |
| 0xC021001E | 無法取得 BitLocker 加密金鑰。 |
The BitLocker encryption key could not be obtained. |
| 0xC021001F | 中繼資料磁碟區域指標不正確。 |
The metadata disk region pointer is incorrect. |
| 0xC0210020 | 中繼資料的備份副本已過期。 |
The backup copy of the metadata is out of date. |
| 0xC0210021 | 因為需要重新啟動系統，因此未採取任何動作。 |
No action was taken as a system reboot is required. |
| 0xC0210022 | 未執行任何動作，因為 BitLocker 磁碟機加密目前是原生存取模式。 |
No action was taken as BitLocker Drive Encryption is in RAW access mode. |
| 0xC0210023 | BitLocker 磁碟機加密無法針對此磁碟區進入原生存取模式。 |
BitLocker Drive Encryption cannot enter raw access mode for this volume. |
| 0xC0210024 | 作業系統磁碟區沒有自動解除鎖定主要金鑰。請使用 BitLocker WMI 介面來重試操作。 |
The auto-unlock master key was not available from the operating system volume. Retry the operation using the BitLocker WMI interface. |
| 0xC0210025 | 系統韌體無法在重新開機時清除系統記憶體。 |
The system firmware failed to enable clearing of system memory on reboot. |
| 0xC0210026 | 此版 Windows 未包含這個 BitLocker 磁碟機加密功能。 |
This feature of BitLocker Drive Encryption is not included with this version of Windows. |
| 0xC0210027 | 群組原則不允許關閉漫遊資料磁碟區上的 BitLocker 磁碟機加密。 |
Group policy does not permit turning off BitLocker Drive Encryption on roaming data volumes. |
| 0xC0210028 | Bitlocker 磁碟機加密無法從中止的轉換復原。這可能是因為所有轉換記錄損毀，或媒體有寫入保護。 |
Bitlocker Drive Encryption failed to recover from aborted conversion. This could be due to either all conversion logs being corrupted or the media being write-protected. |
| 0xC0210029 | 要求的模擬大小太大。 |
The requested virtualization size is too big. |
| 0xC021002A | 儲存在磁碟機上的管理資訊包含不明類型。如果您使用的是舊版的 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. |
| 0xC0210030 | 磁碟機太小而無法使用 BitLocker 磁碟機加密予以保護。 |
The drive is too small to be protected using BitLocker Drive Encryption. |
| 0xC0210031 | 無法從信賴平台模組 (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. |
| 0xC0210032 | 「BitLocker 磁碟機加密」只支援在精簡佈建的存放裝置上執行「僅已使用空間」加密。 |
BitLocker Drive Encryption only supports Used Space Only encryption on thin provisioned storage. |
| 0xC0210033 | BitLocker 磁碟機加密不支援抹除精簡佈建的存放裝置上的可用空間。 |
BitLocker Drive Encryption does not support wiping free space on thin provisioned storage. |
| 0xC0210034 | 只能從所指定 CSV 磁碟區的協調器節點執行此命令。 |
This command can only be performed from the coordinator node for the specified CSV volume. |
| 0xC0210035 | 無法在屬於叢集的磁碟區上執行此命令。 |
This command cannot be performed on a volume when it is part of a cluster. |
| 0xC0210036 | 無法在磁碟加密或解密期間升級 BitLocker。 |
BitLocker cannot be upgraded during disk encryption or decryption. |
| 0xC0210037 | 目前未進行可用空間的抹除作業。 |
Wipe of free space is not currently taking place. |
| 0xC0210038 | 您的電腦不支援 BitLocker 硬體加密。請洽詢您的電腦製造商，以取得韌體更新。 |
Your computer doesn't support BitLocker hardware-based encryption. Check with your computer manufacturer for firmware updates. |
| 0xC0210039 | 已停用安全開機。必須重新啟用安全開機，或必須暫停 BitLocker，Windows 才能正常啟動。 |
Secure Boot has been disabled. Either Secure Boot must be re-enabled, or BitLocker must be suspended for Windows to start normally. |
| 0xC021003A | 安全開機原則意外變更。 |
Secure Boot policy has unexpectedly changed. |
| 0xC021003B | 由於輸入太多次不正確的密碼，已觸發「裝置鎖定」。 |
Device Lock has been triggered due to too many incorrect password attempts. |
| 0xC021003C | 因為磁碟區延伸超過其原始大小，已禁止移除裝置加密。 |
Device encryption removal is blocked due to volume being extended beyond its original size. |
| 0xC021003D | 不支援此動作，因為沒有使用裝置加密自動管理此磁碟機。 |
This action isn't supported because this drive isn't automatically managed with device encryption. |
| 0xC021003E | 已在此磁碟機暫停「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. |
| 0xC021003F | 無法在此磁碟機暫停 BitLocker，直到下次重新啟動為止。 |
BitLocker can't be suspended on this drive until the next restart. |
| 0xC0210040 | 「BitLocker 磁碟機加密」原則不允許在受保護的 OS 磁碟區上執行 KSR 作業。 |
BitLocker Drive Encryption policy does not allow KSR operation with protected OS volume. |
| 0xC0220001 | 圖說文字不存在。 |
The callout does not exist. |
| 0xC0220002 | 篩選器條件不存在。 |
The filter condition does not exist. |
| 0xC0220003 | 篩選器不存在。 |
The filter does not exist. |
| 0xC0220004 | 圖層不存在。 |
The layer does not exist. |
| 0xC0220005 | 提供者不存在。 |
The provider does not exist. |
| 0xC0220006 | 提供者內容不存在。 |
The provider context does not exist. |
| 0xC0220007 | 子圖層不存在。 |
The sublayer does not exist. |
| 0xC0220008 | 物件不存在。 |
The object does not exist. |
| 0xC0220009 | 具有該 GUID 或 LUID 的物件已經存在。 |
An object with that GUID or LUID already exists. |
| 0xC022000A | 該物件正由其他物件參照，因此無法刪除。 |
The object is referenced by other objects so cannot be deleted. |
| 0xC022000B | 不允許從動態工作階段中發出呼叫。 |
The call is not allowed from within a dynamic session. |
| 0xC022000C | 該呼叫是從錯誤的工作階段中發出，因此無法完成。 |
The call was made from the wrong session so cannot be completed. |
| 0xC022000D | 該呼叫必須從明確交易發出。 |
The call must be made from within an explicit transaction. |
| 0xC022000E | 從明確交易內不允許呼叫。 |
The call is not allowed from within an explicit transaction. |
| 0xC022000F | 明確交易已被強制取消。 |
The explicit transaction has been forcibly cancelled. |
| 0xC0220010 | 工作階段已被取消。 |
The session has been cancelled. |
| 0xC0220011 | 從唯讀交易內不允許呼叫。 |
The call is not allowed from within a read-only transaction. |
| 0xC0220012 | 等候取得交易鎖定時呼叫逾時。 |
The call timed out while waiting to acquire the transaction lock. |
| 0xC0220013 | 網路診斷事件的集合已停用。 |
Collection of network diagnostic events is disabled. |
| 0xC0220014 | 指定的層不支援該作業。 |
The operation is not supported by the specified layer. |
| 0xC0220015 | 只有核心模式呼叫者可進行呼叫。 |
The call is allowed for kernel-mode callers only. |
| 0xC0220016 | 呼叫嘗試關聯兩個具有不相容之存留期的物件。 |
The call tried to associate two objects with incompatible lifetimes. |
| 0xC0220017 | 物件為內建，無法刪除。 |
The object is built in so cannot be deleted. |
| 0xC0220018 | 已達到核心模式驅動程式呼叫的數目上限。 |
The maximum number of callouts has been reached. |
| 0xC0220019 | 因為訊息佇列處於最大容量，所以無法傳送通知。 |
A notification could not be delivered because a message queue is at its maximum capacity. |
| 0xC022001A | 流量參數不符合安全性關聯內容的流量參數。 |
The traffic parameters do not match those for the security association context. |
| 0xC022001B | 目前的安全性關聯狀態不允許呼叫。 |
The call is not allowed for the current security association state. |
| 0xC022001C | 需要的指標為空。 |
A required pointer is null. |
| 0xC022001D | 列舉值無效。 |
An enumerator is not valid. |
| 0xC022001E | 旗標欄位包含無效的值。 |
The flags field contains an invalid value. |
| 0xC022001F | 網路遮罩無效。 |
A network mask is not valid. |
| 0xC0220020 | FWP_RANGE 無效。 |
An FWP_RANGE is not valid. |
| 0xC0220021 | 時間間隔無效。 |
The time interval is not valid. |
| 0xC0220022 | 陣列必須至少包含一個長度為零的元素。 |
An array that must contain at least one element is zero length. |
| 0xC0220023 | displayData.name 欄位不可為空。 |
The displayData.name field cannot be null. |
| 0xC0220024 | 動作類型不是篩選器允許的其中一個動作類型。 |
The action type is not one of the allowed action types for a filter. |
| 0xC0220025 | 篩選器加權無效。 |
The filter weight is not valid. |
| 0xC0220026 | 篩選器包含的相符類型與運算元不相容。 |
A filter condition contains a match type that is not compatible with the operands. |
| 0xC0220027 | FWP_VALUE 或 FWPM_CONDITION_VALUE 的類型錯誤。 |
An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type. |
| 0xC0220028 | 整數值超出允許的範圍。 |
An integer value is outside the allowed range. |
| 0xC0220029 | 保留的欄位不是零。 |
A reserved field is non-zero. |
| 0xC022002A | 篩選器無法包含在單一欄位上運作的多個條件。 |
A filter cannot contain multiple conditions operating on a single field. |
| 0xC022002B | 原則無法取得相同的金鑰處理模組超過一次。 |
A policy cannot contain the same keying module more than once. |
| 0xC022002C | 動作類型與層不相容。 |
The action type is not compatible with the layer. |
| 0xC022002D | 動作類型與子層不相容。 |
The action type is not compatible with the sublayer. |
| 0xC022002E | 原始內容或提供者內容與層不相容。 |
The raw context or the provider context is not compatible with the layer. |
| 0xC022002F | 原始內容或提供者內容與圖說文字不相容。 |
The raw context or the provider context is not compatible with the callout. |
| 0xC0220030 | 驗證方法與原則類型不相容。 |
The authentication method is not compatible with the policy type. |
| 0xC0220031 | Diffie-Hellman 群組與原則類型不相容。 |
The Diffie-Hellman group is not compatible with the policy type. |
| 0xC0220032 | IKE 原則無法包含延伸模式原則。 |
An IKE policy cannot contain an Extended Mode policy. |
| 0xC0220033 | 列舉範本或訂閱將永遠不會符合任何物件。 |
The enumeration template or subscription will never match any objects. |
| 0xC0220034 | 提供者內容類型錯誤。 |
The provider context is of the wrong type. |
| 0xC0220035 | 參數錯誤。 |
The parameter is incorrect. |
| 0xC0220036 | 已到達子層的數目上限。 |
The maximum number of sublayers has been reached. |
| 0xC0220037 | 圖說文字的通知功能已傳回錯誤。 |
The notification function for a callout returned an error. |
| 0xC0220038 | IPsec 驗證轉換無效。 |
The IPsec authentication transform is not valid. |
| 0xC0220039 | IPsec 密碼轉換無效。 |
The IPsec cipher transform is not valid. |
| 0xC022003A | IPsec 密碼轉換與原則不相容。 |
The IPsec cipher transform is not compatible with the policy. |
| 0xC022003B | IPsec 轉換類型的組合無效。 |
The combination of IPsec transform types is not valid. |
| 0xC022003C | 原則無法包含相同的驗證方法超過一次。 |
A policy cannot contain the same auth method more than once. |
| 0xC022003D | 通道端點設定無效。 |
A tunnel endpoint configuration is invalid. |
| 0xC022003E | WFP MAC 層未就緒。 |
The WFP MAC Layers are not ready. |
| 0xC022003F | 已註冊可進行金鑰聽寫的金鑰管理員 |
A key manager capable of key dictation is already registered |
| 0xC0220040 | 金鑰管理員聽寫到無效的金鑰 |
A key manager dictated invalid keys |
| 0xC0220041 | 已停用 BFE IPsec 連線追蹤。 |
The BFE IPsec Connection Tracking is disabled. |
| 0xC0220042 | DNS 名稱無效。 |
The DNS name is invalid. |
| 0xC0220043 | 因為其他組態設定，所以仍然啟用引擎選項。 |
The engine option is still enabled due to other configuration settings. |
| 0xC0220044 | IKEEXT 服務未執行。此服務只會在電腦套用 IPsec 原則時才會執行。 |
The IKEEXT service is not running. This service only runs when there is IPsec policy applied to the machine. |
| 0xC0220100 | TCP/IP 堆疊未就緒。 |
The TCP/IP stack is not ready. |
| 0xC0220101 | 插入控制代碼已由其他執行緒關閉。 |
The injection handle is being closed by another thread. |
| 0xC0220102 | 插入控制代碼已過期。 |
The injection handle is stale. |
| 0xC0220103 | 該分類無法暫停。 |
The classify cannot be pended. |
| 0xC0220104 | 應該丟棄封包，不應該傳送 ICMP。 |
The packet should be dropped, no ICMP should be sent. |
| 0xC0230002 | 正在關閉網路介面的繫結。 |
The binding to the network interface is being closed. |
| 0xC0230004 | 指定的版本無效。 |
An invalid version was specified. |
| 0xC0230005 | 使用的特性表無效。 |
An invalid characteristics table was used. |
| 0xC0230006 | 找不到網路介面，或網路介面尚未就緒。 |
Failed to find the network interface or network interface is not ready. |
| 0xC0230007 | 無法開啟網路介面。 |
Failed to open the network interface. |
| 0xC0230008 | 網路介面發生無法復原的內部錯誤。 |
Network interface has encountered an internal unrecoverable failure. |
| 0xC0230009 | 網路介面上的多點傳送清單已滿。 |
The multicast list on the network interface is full. |
| 0xC023000A | 嘗試將重複的多點傳送位址加入清單。 |
An attempt was made to add a duplicate multicast address to the list. |
| 0xC023000B | 嘗試移除從未新增的多點傳送位址。 |
At attempt was made to remove a multicast address that was never added. |
| 0xC023000C | 網路介面中止該要求。 |
Netowork interface aborted the request. |
| 0xC023000D | 因為正在重設網路介面，所以無法處理要求。 |
Network interface can not process the request because it is being reset. |
| 0xC023000F | 嘗試在網路介面上傳送無效的封包。 |
An attempt was made to send an invalid packet on a network interface. |
| 0xC0230011 | 網路介面尚未就緒，無法完成此操作。 |
Network interface is not ready to complete this operation. |
| 0xC0230014 | 提交給此操作的緩衝區長度無效。 |
The length of the buffer submitted for this operation is not valid. |
| 0xC0230015 | 此操作使用的資料無效。 |
The data used for this operation is not valid. |
| 0xC0230016 | 提交給此操作的緩衝區長度太短。 |
The length of buffer submitted for this operation is too small. |
| 0xC0230017 | 網路介面不支援此 OID (物件識別元) |
Network interface does not support this OID (Object Identifier) |
| 0xC0230018 | 網路介面已移除。 |
The network interface has been removed. |
| 0xC0230019 | 網路介面不支援此媒體類型。 |
Network interface does not support this media type. |
| 0xC023001A | 嘗試移除其他元件正在使用的權杖環群組位址。 |
An attempt was made to remove a token ring group address that is in use by other components. |
| 0xC023001B | 已嘗試對應不存在的檔案。 |
An attempt was made to map a file that can not be found. |
| 0xC023001C | NDIS 嘗試對應檔案時發生錯誤。 |
An error occurred while NDIS tried to map the file. |
| 0xC023001D | 已嘗試對應已經對應的檔案。 |
An attempt was made to map a file that is alreay mapped. |
| 0xC023001E | 因為另一個元件正在使用該硬體資源，所以嘗試配置該資源失敗。 |
An attempt to allocate a hardware resource failed because the resource is used by another component. |
| 0xC023001F | 因為網路媒體已中斷連線或超出無線存取點範圍，所以 I/O 操作失敗。 |
The I/O operation failed because network media is disconnected or wireless access point is out of range. |
| 0xC0230022 | 要求中使用的網路位址無效。 |
The network address used in the request is invalid. |
| 0xC023002A | 已暫停網路介面上的卸載操作。 |
The offload operation on the network interface has been paused. |
| 0xC023002B | 找不到網路介面。 |
Network interface was not found. |
| 0xC023002C | 不支援在結構中指定的修訂編號。 |
The revision number specified in the structure is not supported. |
| 0xC023002D | 指定的連接埠不存在於此網路介面上。 |
The specified port does not exist on this network interface. |
| 0xC023002E | 此網路介面上所指定連接埠的目前狀態不支援要求的操作。 |
The current state of the specified port on this network interface does not support the requested operation. |
| 0xC023002F | Miniport Adapter 處於電源不足狀態。 |
The miniport adapter is in lower power state. |
| 0xC0230030 | 此作業需要重新初始化 Miniport 介面卡。 |
This operation requires the miniport adapter to be reinitialized. |
| 0xC02300BB | 網路介面不支援此要求。 |
Netword interface does not support this request. |
| 0xC023100F | 基於本機原則設定，不允許卸載 TCP 連線。 |
The TCP connection is not offloadable because of a local policy setting. |
| 0xC0231012 | Chimney 卸載目標不可卸載 TCP 連線。 |
The TCP connection is not offloadable by the Chimney offload target. |
| 0xC0231013 | IP 路徑物件未處於可卸載狀態。 |
The IP Path object is not in an offloadable state. |
| 0xC0232000 | 無線區域網路介面處於自動設定模式，因此不支援要求的參數變更操作。 |
The wireless local area network interface is in auto configuration mode and doesn't support the requested parameter change operation. |
| 0xC0232001 | 無線區域網路介面忙碌中，因此無法執行要求的操作。 |
The wireless local area network interface is busy and can not perform the requested operation. |
| 0xC0232002 | 無線區域網路介面的電源已關閉，因此不支援要求的操作。 |
The wireless local area network interface is powered down and doesn't support the requested operation. |
| 0xC0232003 | 網路喚醒模式清單已滿。 |
The list of wake on LAN patterns is full. |
| 0xC0232004 | 低電源通訊協定卸載清單已滿。 |
The list of low power protocol offloads is full. |
| 0xC0232005 | 無線區域網路介面目前無法在指定的通道上啟動 AP。 |
The wireless local area network interface cannot start an AP on the specified channel right now. |
| 0xC0232006 | 無線區域網路介面目前無法在指定的頻帶上啟動 AP。 |
The wireless local area network interface cannot start an AP on the specified band right now. |
| 0xC0232007 | 無線區域網路介面因為法規因素而無法在此通道上啟動 AP。 |
The wireless local area network interface cannot start an AP on this channel due to regulatory reasons. |
| 0xC0232008 | 無線區域網路介面因為法規因素而無法在此頻帶上啟動 AP。 |
The wireless local area network interface cannot start an AP on this band due to regulatory reasons. |
| 0xC0290000 | 這是用來將 TPM 硬體錯誤轉換為 win 錯誤的錯誤遮罩。 |
This is an error mask to convert TPM hardware errors to win errors. |
| 0xC0290001 | 驗證失敗。 |
Authentication failed. |
| 0xC0290002 | PCR、DIR 或其他暫存器的索引不正確。 |
The index to a PCR, DIR or other register is incorrect. |
| 0xC0290003 | 一或多個參數錯誤。 |
One or more parameter is bad. |
| 0xC0290004 | 操作已順利完成，但稽核操作失敗。 |
An operation completed successfully but the auditing of that operation failed. |
| 0xC0290005 | 清除停用旗標已設定，且所有清除操作現在需要實際存取。 |
The clear disable flag is set and all clear operations now require physical access. |
| 0xC0290006 | 啟動信賴平台模組 (TPM)。 |
Activate the Trusted Platform Module (TPM). |
| 0xC0290007 | 啟用信賴平台模組 (TPM)。 |
Enable the Trusted Platform Module (TPM). |
| 0xC0290008 | 目標命令已停用。 |
The target command has been disabled. |
| 0xC0290009 | 操作失敗。 |
The operation failed. |
| 0xC029000A | 序數未知或不一致。 |
The ordinal was unknown or inconsistent. |
| 0xC029000B | 安裝擁有者的功能已停用。 |
The ability to install an owner is disabled. |
| 0xC029000C | 無法解譯金鑰控制代碼。 |
The key handle cannot be interpreted. |
| 0xC029000D | 金鑰控制代碼指向無效的金鑰。 |
The key handle points to an invalid key. |
| 0xC029000E | 無法接受的加密配置。 |
Unacceptable encryption scheme. |
| 0xC029000F | 移轉授權失敗。 |
Migration authorization failed. |
| 0xC0290010 | 無法解譯 PCR 資訊。 |
PCR information could not be interpreted. |
| 0xC0290011 | 沒有空間可以載入金鑰。 |
No room to load key. |
| 0xC0290012 | 沒有儲存根金鑰 (SRK) 組。 |
There is no Storage Root Key (SRK) set. |
| 0xC0290013 | 已加密的 blob 無效，或是並非由此 TPM 所建立。 |
An encrypted blob is invalid or was not created by this TPM. |
| 0xC0290014 | 信賴平台模組 (TPM) 已經有擁有者。 |
The Trusted Platform Module (TPM) already has an owner. |
| 0xC0290015 | TPM 的內部資源不足，無法執行要求的動作。 |
The TPM has insufficient internal resources to perform the requested action. |
| 0xC0290016 | 隨機字串太短。 |
A random string was too short. |
| 0xC0290017 | TPM 的空間不足，無法執行該操作。 |
The TPM does not have the space to perform the operation. |
| 0xC0290018 | 具名 PCR 值與目前的 PCR 值不符。 |
The named PCR value does not match the current PCR value. |
| 0xC0290019 | 命令之 paramSize 引數的值不正確。 |
The paramSize argument to the command has the incorrect value . |
| 0xC029001A | 沒有現有的 SHA-1 執行緒。 |
There is no existing SHA-1 thread. |
| 0xC029001B | 無法繼續計算，因為現有的 SHA-1 執行緒已發生錯誤。 |
The calculation is unable to proceed because the existing SHA-1 thread has already encountered an error. |
| 0xC029001C | TPM 硬體裝置進行內部自我測試時回報錯誤。請嘗試重新啟動電腦以解決問題。如果問題持續發生，您可能需要更換 TPM 硬體或主機板。 |
The TPM hardware device reported a failure during its internal self test. Try restarting the computer to resolve the problem. If the problem continues, you might need to replace your TPM hardware or motherboard. |
| 0xC029001D | 雙金鑰函數中的第二個金鑰授權失敗。 |
The authorization for the second key in a 2 key function failed authorization. |
| 0xC029001E | 傳送給命令的標記值無效。 |
The tag value sent to for a command is invalid. |
| 0xC029001F | 傳送資訊到 TPM 時發生 IO 錯誤。 |
An IO error occurred transmitting information to the TPM. |
| 0xC0290020 | 加密程序有問題。 |
The encryption process had a problem. |
| 0xC0290021 | 解密程序未完成。 |
The decryption process did not complete. |
| 0xC0290022 | 使用了無效的控制代碼。 |
An invalid handle was used. |
| 0xC0290023 | TPM 未安裝簽署金鑰 (EK)。 |
The TPM does not have an Endorsement Key (EK) installed. |
| 0xC0290024 | 不允許該金鑰使用方法。 |
The usage of a key is not allowed. |
| 0xC0290025 | 不允許送出的實體類型。 |
The submitted entity type is not allowed. |
| 0xC0290026 | 相對於 TPM_Init 與後續 TPM_Startup，命令的接收順序錯誤。 |
The command was received in the wrong sequence relative to TPM_Init and a subsequent TPM_Startup. |
| 0xC0290027 | 已簽署的資料不能包含額外 DER 資訊。 |
Signed data cannot include additional DER information. |
| 0xC0290028 | 此 TPM 不支援 TPM_KEY_PARMs 中的金鑰屬性。 |
The key properties in TPM_KEY_PARMs are not supported by this TPM. |
| 0xC0290029 | 此金鑰的移轉屬性不正確。 |
The migration properties of this key are incorrect. |
| 0xC029002A | 此金鑰的簽章或加密配置不正確，或在此情況下是不允許的。 |
The signature or encryption scheme for this key is incorrect or not permitted in this situation. |
| 0xC029002B | 資料 (或 blob) 參數的大小錯誤，或與參照的金鑰不一致。 |
The size of the data (or blob) parameter is bad or inconsistent with the referenced key. |
| 0xC029002C | 模式參數錯誤，例如 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. |
| 0xC029002D | physicalPresence 或 physicalPresenceLock 位元的值錯誤。 |
Either the physicalPresence or physicalPresenceLock bits have the wrong value. |
| 0xC029002E | TPM 無法執行此版本的功能。 |
The TPM cannot perform this version of the capability. |
| 0xC029002F | 包裝的傳輸工作階段不允許 TPM。 |
The TPM does not allow for wrapped transport sessions. |
| 0xC0290030 | TPM 稽核建構失敗，且其下的命令也傳回錯誤碼。 |
TPM audit construction failed and the underlying command was returning a failure code also. |
| 0xC0290031 | TPM 稽核建構失敗，且其下的命令傳回成功資訊。 |
TPM audit construction failed and the underlying command was returning success. |
| 0xC0290032 | 嘗試重設沒有可重設屬性的 PCR 暫存器。 |
Attempt to reset a PCR register that does not have the resettable attribute. |
| 0xC0290033 | 嘗試重設 PCR 暫存器，它要求位置與位置修飾元不能是命令傳輸的一部分。 |
Attempt to reset a PCR register that requires locality and locality modifier not part of command transport. |
| 0xC0290034 | 讓身份識別 blob 看起來不像是人工輸入的樣子。 |
Make identity blob not properly typed. |
| 0xC0290035 | 儲存時內容識別的資源類型與實際資源不符。 |
When saving context identified resource type does not match actual resource. |
| 0xC0290036 | TPM 正嘗試執行只有在 FIPS 模式才可以使用的命令。 |
The TPM is attempting to execute a command only available when in FIPS mode. |
| 0xC0290037 | 命令正嘗試使用無效的系列識別碼。 |
The command is attempting to use an invalid family ID. |
| 0xC0290038 | 可用來操縱 NV 存放區的權限無法使用。 |
The permission to manipulate the NV storage is not available. |
| 0xC0290039 | 此操作需要已簽署的命令。 |
The operation requires a signed command. |
| 0xC029003A | 載入 NV 金鑰的操作不正確。 |
Wrong operation to load an NV key. |
| 0xC029003B | NV_LoadKey blob 需要擁有者與 blob 授權。 |
NV_LoadKey blob requires both owner and blob authorization. |
| 0xC029003C | NV 區域已鎖定，且無法寫入。 |
The NV area is locked and not writtable. |
| 0xC029003D | 該位置對於所嘗試的操作而言不正確。 |
The locality is incorrect for the attempted operation. |
| 0xC029003E | NV 區域是唯讀的，且無法寫入。 |
The NV area is read only and can't be written to. |
| 0xC029003F | NV 區域沒有防寫保護。 |
There is no protection on the write to the NV area. |
| 0xC0290040 | 系列計數值不相符。 |
The family count value does not match. |
| 0xC0290041 | NV 區域已被寫入。 |
The NV area has already been written to. |
| 0xC0290042 | NV 區域屬性衝突。 |
The NV area attributes conflict. |
| 0xC0290043 | 結構標籤與版本無效或不一致。 |
The structure tag and version are invalid or inconsistent. |
| 0xC0290044 | 該金鑰是由 TPM 擁有者所控制，且只能由 TPM 擁有者收回。 |
The key is under control of the TPM Owner and can only be evicted by the TPM Owner. |
| 0xC0290045 | 計數器控制代碼不正確。 |
The counter handle is incorrect. |
| 0xC0290046 | 該寫入動作並未完整寫入該區域。 |
The write is not a complete write of the area. |
| 0xC0290047 | 已儲存內容計數的間距太大。 |
The gap between saved context counts is too large. |
| 0xC0290048 | 已經超過 NV 寫入次數的上限 (在沒有擁有者的情況下)。 |
The maximum number of NV writes without an owner has been exceeded. |
| 0xC0290049 | 未設定運算子 AuthData 值。 |
No operator AuthData value is set. |
| 0xC029004A | 未載入內容指向的資源。 |
The resource pointed to by context is not loaded. |
| 0xC029004B | 委派管理已鎖定。 |
The delegate administration is locked. |
| 0xC029004C | 嘗試管理非委派系列的系列。 |
Attempt to manage a family other then the delegated family. |
| 0xC029004D | 未啟用委派表格管理。 |
Delegation table management not enabled. |
| 0xC029004E | 有命令在專用傳輸工作階段之外執行。 |
There was a command executed outside of an exclusive transport session. |
| 0xC029004F | 嘗試以相關內容方式儲存擁有者收回控制的金鑰。 |
Attempt to context save a owner evict controlled key. |
| 0xC0290050 | DAA 命令沒有可用的資源，無法執行命令。 |
The DAA command has no resources availble to execute the command. |
| 0xC0290051 | DAA 參數 inputData0 的一致性檢查失敗。 |
The consistency check on DAA parameter inputData0 has failed. |
| 0xC0290052 | DAA 參數 inputData1 的一致性檢查失敗。 |
The consistency check on DAA parameter inputData1 has failed. |
| 0xC0290053 | DAA_issuerSettings 的一致性檢查失敗。 |
The consistency check on DAA_issuerSettings has failed. |
| 0xC0290054 | DAA_tpmSpecific 的一致性檢查失敗。 |
The consistency check on DAA_tpmSpecific has failed. |
| 0xC0290055 | 已送出之 DAA 命令所指出之不可部分完成的處理程序不是預期的處理程序。 |
The atomic process indicated by the submitted DAA command is not the expected process. |
| 0xC0290056 | 簽發者的有效性檢查發現不一致。 |
The issuer's validity check has detected an inconsistency. |
| 0xC0290057 | w 的一致性檢查失敗。 |
The consistency check on w has failed. |
| 0xC0290058 | 控制代碼不正確。 |
The handle is incorrect. |
| 0xC0290059 | 委派不正確。 |
Delegation is not correct. |
| 0xC029005A | 內容 blob 無效。 |
The context blob is invalid. |
| 0xC029005B | TPM 持有太多內容。 |
Too many contexts held by the TPM. |
| 0xC029005C | 移轉授權單位簽章驗證失敗。 |
Migration authority signature validation failure. |
| 0xC029005D | 移轉目的地未驗證。 |
Migration destination not authenticated. |
| 0xC029005E | 移轉來源不正確。 |
Migration source incorrect. |
| 0xC029005F | 不正確的移轉授權單位。 |
Incorrect migration authority. |
| 0xC0290061 | 嘗試撤銷 EK，但 EK 無法撤銷。 |
Attempt to revoke the EK and the EK is not revocable. |
| 0xC0290062 | CMK 票證的簽章錯誤。 |
Bad signature of CMK ticket. |
| 0xC0290063 | 內容清單中沒有空間，無法存放其他內容。 |
There is no room in the context list for additional contexts. |
| 0xC0290400 | 命令已被封鎖。 |
The command was blocked. |
| 0xC0290401 | 找不到指定的控制代碼。 |
The specified handle was not found. |
| 0xC0290402 | TPM 傳回重複的控制代碼，而且該命令需要重新送出。 |
The TPM returned a duplicate handle and the command needs to be resubmitted. |
| 0xC0290403 | 傳輸中的命令已被封鎖。 |
The command within the transport was blocked. |
| 0xC0290404 | 傳輸中的命令不受支援。 |
The command within the transport is not supported. |
| 0xC0290800 | TPM 正忙於立即回應命令，但該命令可以稍後再重新送出。 |
The TPM is too busy to respond to the command immediately, but the command could be resubmitted at a later time. |
| 0xC0290801 | SelfTestFull 並未執行。 |
SelfTestFull has not been run. |
| 0xC0290802 | TPM 目前正在執行完整自我測試。 |
The TPM is currently executing a full selftest. |
| 0xC0290803 | TPM 正在防禦字典攻擊，且正處於逾時階段。 |
The TPM is defending against dictionary attacks and is in a time-out period. |
| 0xC0291001 | 命令已取消。 |
The command was cancelled. |
| 0xC0291002 | 無法建立新的 TMP 內容，因為已有太多開啟的內容。 |
A new TPM context could not be created because there are too many open contexts. |
| 0xC0291003 | TPM 驅動程式與系統上找到的 TPM 版本不相容。 |
TPM driver is not compatible with the version of TPM found on the system. |
| 0xC0291004 | 呼叫者沒有適當的權限可以執行要求的操作。 |
The caller does not have the appropriate rights to perform the requested operation. |
| 0xC0291006 | 此韌體的「實體操作介面」不支援要求的方法。 |
The Physical Presence Interface of this firmware does not support the requested method. |
| 0xC0292000 | 這是用來將「平台密碼編譯提供者」錯誤轉換為 win 錯誤的錯誤遮罩。 |
This is an error mask to convert Platform Crypto Provider errors to win errors. |
| 0xC0292001 | 「平台密碼編譯裝置」目前未就緒。它需要完整佈建，才能作業。 |
The Platform Crypto Device is currently not ready. It needs to be fully provisioned to be operational. |
| 0xC0292002 | 提供給「平台密碼編譯提供者」的控制代碼無效。 |
The handle provided to the Platform Crypto Provider is invalid. |
| 0xC0292003 | 提供給「平台密碼編譯提供者」的參數無效。 |
A parameter provided to the Platform Crypto Provider is invalid. |
| 0xC0292004 | 不支援提供給「平台密碼編譯提供者」的旗標。 |
A provided flag to the Platform Crypto Provider is not supported. |
| 0xC0292005 | 此「平台密碼編譯提供者」不支援要求的作業。 |
The requested operation is not supported by this Platform Crypto Provider. |
| 0xC0292006 | 緩衝區太小，無法包含所有資料。未將資訊寫入至緩衝區。 |
The buffer is too small to contain all data. No information has been written to the buffer. |
| 0xC0292007 | 「平台密碼編譯提供者」中發生意外的內部錯誤。 |
An unexpected internal error has occurred in the Platform Crypto Provider. |
| 0xC0292008 | 使用提供者物件的授權失敗。 |
The authorization to use a provider object has failed. |
| 0xC0292009 | 「平台密碼編譯裝置」已忽略提供者物件的授權，以避免字典攻擊。 |
The Platform Crypto Device has ignored the authorization for the provider object, to mitigate against a dictionary attack. |
| 0xC029200A | 找不到參照的原則。 |
The referenced policy was not found. |
| 0xC029200B | 找不到參照的設定檔。 |
The referenced profile was not found. |
| 0xC029200D | 找不到「平台密碼編譯裝置」。將不會送出需要「平台密碼編譯裝置」的操作。 |
A Platform Crypto Device was not found. Operations that require a Platform Crypto Device will not be submitted. |
| 0xC029200E | 嘗試在不正確的存放裝置父系匯入或載入金鑰。 |
An attempt was made to import or load a key under an incorrect storage parent. |
| 0xC029200F | 未載入 TPM 金鑰。 |
The TPM key is not loaded. |
| 0xC0292010 | 尚未產生 TPM 金鑰認證。 |
The TPM key certification has not been generated. |
| 0xC0292011 | TPM 金鑰尚未完成。 |
The TPM key is not yet finalized. |
| 0xC0292012 | 未設定 TPM 證明挑戰。 |
The TPM attestation challenge is not set. |
| 0xC0292013 | TPM 金鑰未繫結到 PCR 資訊。 |
The TPM key is not bound to PCR info. |
| 0xC0292014 | 已完成 TPM 金鑰。 |
The TPM key is already finalized. |
| 0xC0292015 | 不支援 TPM 金鑰使用原則。 |
The TPM key usage policy is not supported. |
| 0xC0292016 | TPM 金鑰使用原則無效。 |
The TPM key usage policy is invalid. |
| 0xC0292017 | 匯入 TPM 中的軟體金鑰發生問題。 |
There was a problem with the software key being imported into the TPM. |
| 0xC0292018 | 未驗證 TPM 金鑰。 |
The TPM key is not authenticated. |
| 0xC0292019 | TPM 金鑰不是 AIK。 |
The TPM key is not an AIK. |
| 0xC029201A | TPM 金鑰不是簽署金鑰。 |
The TPM key is not a signing key. |
| 0xC029201B | 已鎖定 TPM。 |
The TPM is locked out. |
| 0xC029201C | 要求的宣告類型不受支援。 |
The claim type requested is not supported. |
| 0xC029201D | 目前的 TPM 版本不受支援。 |
The current TPM version is not supported. |
| 0xC029201E | 緩衝區長度不相符。 |
The buffer lengths do not match. |
| 0xC0293002 | 沒有與此執行個體關聯的結果存在。 |
No result associated with this instance exists. |
| 0xC0293003 | TPM 傳回不完整的 PCR 結果。這可能是因為不支援的選取範圍集。請嘗試使用不同的選取範圍集再次讀取。 |
The TPM returned incomplete PCR results. This maybe due to an unsupported selection set. Attempt the read again with a different selection set. |
| 0xC0293004 | rTPM 內容已損毀。rTPM 操作必須重新啟動。 |
The rTPM context has been corrupted. The rTPM operation must be restarted. |
| 0xC0293005 | rTPM 目標不支援所指定 TPM 命令的遠端處理。 |
The rTPM target does not support remote processing of the specified TPM command. |
| 0xC0294000 | TPM 相關的網路作業遭封鎖，因為用戶端已啟用 Zero Exhaust 模式。 |
TPM related network operations are blocked as Zero Exhaust mode is enabled on client. |
| 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 debugging 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. |
| 0xC0360001 | 封包中的 SPI 與有效的 IPsec SA 不相符。 |
The SPI in the packet does not match a valid IPsec SA. |
| 0xC0360002 | IPsec SA 收到存留期已到期的封包。 |
Packet was received on an IPsec SA whose lifetime has expired. |
| 0xC0360003 | IPsec SA 收到與封包特性不相符的封包。 |
Packet was received on an IPsec SA that does not match the packet characteristics. |
| 0xC0360004 | 封包序號重新執行檢查失敗。 |
Packet sequence number replay check failed. |
| 0xC0360005 | 封包中的 IPsec 標頭和/或尾端不正確。 |
IPsec header and/or trailer in the packet is invalid. |
| 0xC0360006 | IPsec 完整性檢查失敗。 |
IPsec integrity check failed. |
| 0xC0360007 | IPsec 已丟棄純文字封包。 |
IPsec dropped a clear text packet. |
| 0xC0360008 | IPsec 已在驗證的防火牆模式中丟棄連入 ESP 封包。這是有益的丟棄操作。 |
IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign. |
| 0xC0360009 | 由於 DoS 節流，IPsec 已經丟棄封包。 |
IPsec dropped a packet due to DoS throttling. |
| 0xC0368000 | IPsec DoS Protection 符合明確封鎖規則。 |
IPsec DoS Protection matched an explicit block rule. |
| 0xC0368001 | IPsec DoS Protection 收到不允許的 IPsec 特定多點傳送封包。 |
IPsec DoS Protection received an IPsec specific multicast packet which is not allowed. |
| 0xC0368002 | IPsec DoS Protection 收到格式不正確的封包。 |
IPsec DoS Protection received an incorrectly formatted packet. |
| 0xC0368003 | IPsec DoS Protection 無法查詢狀態。 |
IPsec DoS Protection failed to look up state. |
| 0xC0368004 | IPsec DoS Protection 無法建立狀態，因為已達到原則允許的項目數目上限。 |
IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached. |
| 0xC0368005 | IPsec DoS Protection 收到原則不允許之金鑰處理模組的 IPsec 交涉封包。 |
IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy. |
| 0xC0368006 | 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. |
| 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. |
| 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. |
| 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. |
| 0xC03A0031 | 要求的大小調整操作可能會截斷虛擬磁碟上的使用者資料。 |
The requested resize operation might truncate user data residing on the virtual disk. |
| 0xC03A0032 | 無法判斷虛擬磁碟的最低安全大小。這可能是因為缺少磁碟分割表格或磁碟分割表格損毀。 |
The minimum safe size of the virtual disk could not be determined. This may be due to a missing or corrupt partition table. |
| 0xC03A0033 | 無法進一步安全地縮減虛擬磁碟大小。 |
The size of the virtual disk cannot be safely reduced further. |
| 0xC0400001 | 「繼續金鑰篩選」找不到針對該作業提供的繼續金鑰。 |
The Resume Key Filter could not find the resume key supplied for the operation. |
| 0xC0400002 | 「繼續金鑰篩選」找到符合提供給控制代碼之繼續金鑰的現有繼續金鑰。 |
The Resume Key Filter found an existing resume key that matches the one supplied for the handle. |
| 0xC0400003 | 附加至控制代碼的「繼續金鑰篩選」資料 blob 已滿。已沒有可用的空間。 |
The Resume Key Filter data blob attached to the handle is full. No more space is available. |
| 0xC0400004 | 「繼續金鑰篩選」控制代碼存放區已滿。無法再接受繼續控制代碼。 |
The Resume Key Filter handle store is full. No more resume handles can be accepted. |
| 0xC0400005 | 因為檔案已被暫時封鎖，無法再擱置該檔案上的現有繼續執行作業，所以「繼續金鑰篩選」讓該作業失敗。 |
The Resume Key Filter failed the operation because the file is temporarily blocked pending the resume of existing handles on the file. |
| 0xC0400006 | 「繼續金鑰篩選」找到符合在使用中/開啟狀態的控制代碼上提供的現有繼續金鑰。該作業需要非使用中/關閉狀態的控制代碼。 |
The Resume Key Filter found an existing resume key that matches the one supplied on a handle that's active/open. The operation requires an inactive/closed handle. |
| 0xC0410001 | RDBSS 必須重新啟動此作業。 |
The operation must be restarted by RDBSS. |
| 0xC0410002 | 必須繼續處理作業。 |
The operation must continue processing. |
| 0xC0410003 | 必須將該操作發佈到執行緒，以便在被動 IRQL 重試。 |
The operation must be posted to a thread to be retried at passive IRQL. |
| 0xC0420001 | 在此伺服器上，指定的屬性控制代碼無效。 |
The attribute handle given was not valid on this server. |
| 0xC0420002 | 無法讀取屬性。 |
The attribute cannot be read. |
| 0xC0420003 | 無法寫入屬性。 |
The attribute cannot be written. |
| 0xC0420004 | 屬性 PDU 無效。 |
The attribute PDU was invalid. |
| 0xC0420005 | 需要先驗證屬性，才能讀取或寫入屬性。 |
The attribute requires authentication before it can be read or written. |
| 0xC0420006 | 屬性伺服器不支援從用戶端接收的要求。 |
Attribute server does not support the request received from the client. |
| 0xC0420007 | 指定的位移超過屬性的結尾。 |
Offset specified was past the end of the attribute. |
| 0xC0420008 | 屬性必須先取得授權，才能讀取或寫入屬性。 |
The attribute requires authorization before it can be read or written. |
| 0xC0420009 | 排入佇列的準備寫入作業太多。 |
Too many prepare writes have been queued. |
| 0xC042000A | 在指定的屬性控制代碼範圍內找不到屬性。 |
No attribute found within the given attribute handle range. |
| 0xC042000B | 無法使用「讀取 Blob 要求」來讀取或寫入屬性。 |
The attribute cannot be read or written using the Read Blob Request. |
| 0xC042000C | 用於加密此連結的「加密金鑰大小」不足。 |
The Encryption Key Size used for encrypting this link is insufficient. |
| 0xC042000D | 屬性值長度對於該作業而言無效。 |
The attribute value length is invalid for the operation. |
| 0xC042000E | 要求的屬性要求發生不大可能發生的錯誤，因此無法依要求完成。 |
The attribute request that was requested has encountered an error that was unlikely, and therefore could not be completed as requested. |
| 0xC042000F | 屬性需要先進行加密，才能讀取或寫入屬性。 |
The attribute requires encryption before it can be read or written. |
| 0xC0420010 | 屬性類型不是較高層級指定項所定義的受支援群組屬性。 |
The attribute type is not a supported grouping attribute as defined by a higher layer specification. |
| 0xC0420011 | 資源不足，無法完成要求。 |
Insufficient Resources to complete the request. |
| 0xC0421000 | 接收到保留範圍內的錯誤。 |
An error that lies in the reserved range has been received. |
| 0xC0430001 | 安全開機偵測到已嘗試復原保護的資料。 |
Secure Boot detected that rollback of protected data has been attempted. |
| 0xC0430002 | 值受安全開機原則保護，因此無法修改或刪除。 |
The value is protected by Secure Boot policy and cannot be modified or deleted. |
| 0xC0430003 | 安全開機原則無效。 |
The Secure Boot policy is invalid. |
| 0xC0430004 | 新安全開機原則的更新清單中未包含目前的發行者。 |
A new Secure Boot policy did not contain the current publisher on its update list. |
| 0xC0430005 | 安全開機原則未簽署，或者是由非信任的簽署人所簽署。 |
The Secure Boot policy is either not signed or is signed by a non-trusted signer. |
| 0xC0430007 | 安全開機需要某些檔案與驅動程式未被其他檔案或驅動程式取代。 |
Secure Boot requires that certain files and drivers are not replaced by other files or drivers. |
| 0xC0430008 | 此電腦上的安全開機增補原則檔案未獲授權。 |
The Secure Boot Supplemental Policy file was not authorized on this machine. |
| 0xC0430009 | 無法識別此裝置上的「增補原則」。 |
The Supplemntal Policy is not recognized on this device. |
| 0xC043000A | 在安全開機原則中找不到 Antirollback 版本。 |
The Antirollback version was not found in the Secure Boot Policy. |
| 0xC043000B | 在安全開機原則中指定的平台識別碼不符合此裝置上的平台識別碼。 |
The Platform ID specified in the Secure Boot policy does not match the Platform ID on this device. |
| 0xC043000C | 安全開機原則檔案具有比此裝置舊的 Antirollback 版本。 |
The Secure Boot policy file has an older Antirollback Version than this device. |
| 0xC043000D | 安全開機原則檔案不符合已升級的舊版原則。 |
The Secure Boot policy file does not match the upgraded legacy policy. |
| 0xC043000E | 「安全開機」原則檔案為必要項目，但找不到該檔案。 |
The Secure Boot policy file is required but could not be found. |
| 0xC043000F | 增補「安全開機」原則檔案無法載入為基礎「安全開機」原則。 |
Supplemental Secure Boot policy file can not be loaded as a base Secure Boot policy. |
| 0xC0430010 | 基礎「安全開機」原則檔案無法載入為增補「安全開機」原則。 |
Base Secure Boot policy file can not be loaded as a Supplemental Secure Boot policy. |
| 0xC0440001 | PortCl 找不到宣告支援 IMiniportAudioEngineNode 之 Miniport 驅動程式所公開的音訊引擎節點。 |
PortCls could not find an audio engine node exposed by a miniport driver claiming support for IMiniportAudioEngineNode. |
| 0xC0440002 | HD Audio Widget 發現未預期的空白連線清單。 |
HD Audio widget encountered an unexpected empty connection list. |
| 0xC0440003 | HD Audio Widget 不支援連線清單參數。 |
HD Audio widget does not support the connection list parameter. |
| 0xC0440004 | 未順利建立任何 HD Audio 子裝置。 |
No HD Audio subdevices were successfully created. |
| 0xC0440005 | 在連結的清單中發現未預期的 NULL 指標。 |
An unexpected NULL pointer was encountered in a linked list. |
| 0xC0450000 | 虛擬安全模式 (VSM) 未初始化。Hypervisor 或 VSM 可能不存在或未啟用。 |
Virtual Secure Mode (VSM) is not initialized. The hypervisor or VSM may not be present or enabled. |
| 0xC0450001 | Hypervisor 並沒有在保護 DMA，因為 BIOS 中的 IOMMU 不存在或未啟用。 |
The hypervisor is not protecting DMA because an IOMMU is not present or not enabled in the BIOS. |
| 0xC0500003 | 開機檔案太小，無法支援持續快照。 |
The bootfile is too small to support persistent snapshots. |
| 0xC0500004 | 此磁碟區上永續性快照的啟動時間超過允許的時間長度。 |
Activation of persistent snapshots on this volume took longer than was allowed. |
| 0xC0510001 | 系統已暫停該操作並執行優先順序較高的操作。您稍後必須繼續該操作。 |
The operation was preempted by a higher priority operation. It must be resumed later. |
| 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 data is available for the initiator to query. |
| 0xC05CFF02 | 裝置的資料功能已變更，導致「單位注意」情況。 |
The data capacity of the device has changed, resulting in a Unit Attention condition. |
| 0xC05CFF03 | 先前的操作導致此啟動器的保留被先佔，導致「單位注意」情況。 |
A previous operation resulted in this initiator's reservations being preempted, resulting in a Unit Attention condition. |
| 0xC05CFF04 | 先前的操作導致此啟動器的保留被釋放，導致「單位注意」情況。 |
A previous operation resulted in this initiator's reservations being released, resulting in a Unit Attention condition. |
| 0xC05CFF05 | 先前的操作導致此啟動器的登錄被先佔，導致「單位注意」情況。 |
A previous operation resulted in this initiator's registrations being preempted, resulting in a Unit Attention condition. |
| 0xC05CFF06 | 裝置的資料儲存格式已變更，導致「單位注意」情況。 |
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. |
| 0xC05D0002 | 您無法存取此共用資料夾，因為您組織的安全性原則已封鎖未經驗證的來賓存取。這些原則可協助保護您的電腦，讓您免於網路上不安全或惡意的裝置。 |
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. |
| 0xC0E70001 | 指定的容錯網域類型或最小/最大容錯網域類型的組合無效。 |
The specified fault domain type or combination of minimum / maximum fault domain type is not valid. |
| 0xC0E70003 | 指定的恢復類型無效。 |
The specified resiliency type is not valid. |
| 0xC0E70004 | 儲存集區不支援實體磁碟的磁區大小。 |
The sector size of the physical disk is not supported by the storage pool. |
| 0xC0E70006 | 容錯的值超出支援的值範圍。 |
The value for fault tolerance is outside of the supported range of values. |
| 0xC0E70007 | 要求的資料複本數目超出支援的值範圍。 |
The number of data copies requested is outside of the supported range of values. |
| 0xC0E70009 | 間隔長度的值超出支援的值範圍或不是 2 的次方。 |
The value for interleave length is outside of the supported range of values or is not a power of 2. |
| 0xC0E7000A | 指定的欄數超出支援的值範圍。 |
The number of columns specified is outside of the supported range of values. |
| 0xC0E7000B | 沒有足夠的實體磁碟可以完成要求的作業。 |
There were not enough physical disks to complete the requested operation. |
| 0xC0E7000C | 有延伸的錯誤資訊可用。 |
Extended error information is available. |
| 0xC0E7000D | 指定的佈建類型無效。 |
The specified provisioning type is not valid. |
| 0xC0E7000E | 配置大小超出支援的值範圍。 |
The allocation size is outside of the supported range of values. |
| 0xC0E7000F | 機箱感知不支援此虛擬磁碟。 |
Enclosure awareness is not supported for this virtual disk. |
| 0xC0E70010 | 寫入快取大小超出支援的值範圍。 |
The write cache size is outside of the supported range of values. |
| 0xC0E70011 | 群組數目的值超出支援的值範圍。 |
The value for number of groups is outside of the supported range of values. |
| 0xC0E70012 | 實體磁碟的 OperationalState 對此操作而言無效。 |
The OperationalState of the physical disk is invalid for this operation. |
| 0xC0E70013 | 需要更新欄狀態。 |
A column's state needs to be updated. |
| 0xC0E70014 | 需要配置區塊。 |
An extent needs to be allocated. |
| 0xC0E70015 | 不支援此中繼資料版本。 |
The metadata version is unsupported. |
| 0xC0E70016 | 中繼資料讀取損毀。 |
The metadata read was corrupt. |
| 0xC0E70017 | DRT 已滿。 |
The DRT is full. |
| 0xC0E70018 | 發現不一致。 |
An inconsistency was found. |
| 0xC0E70019 | 記錄檔尚未就緒。 |
The log is not ready. |
| 0xC0E7001A | 沒有可用的良好資料複本。 |
No good copy of data was available. |
| 0xC0E7001B | 磁碟機尚未就緒。 |
The drive is not ready. |
| 0xC0E7001C | 此磁碟機上的資料已過時。 |
The data on this drive is stale. |
| 0xC0E7001D | 此磁碟機上的資料已遺失。 |
The data on this drive has been lost. |
| 0xC0E80000 | 安全性核心無法辨識此命令 |
The command was not recognized by the security core |
| 0xC0E90001 | 「系統完整性」偵測到已嘗試回復原則。 |
System Integrity detected that policy rollback has been attempted. |
| 0xC0E90002 | 違反「系統完整性」原則。 |
System Integrity policy has been violated. |
| 0xC0E90003 | 「系統完整性」原則無效。 |
The System Integrity policy is invalid. |
| 0xC0E90004 | 「系統完整性」原則未經簽署或不是由信任的簽署人簽署。 |
The System Integrity policy is either not signed or is signed by a non-trusted signer. |
| 0xC0EA0001 | 找不到適當的應用程式授權。 |
No applicable app licenses found. |
| 0xC0EA0002 | 找不到用戶端授權平台授權。 |
CLiP license not found. |
| 0xC0EA0003 | 找不到用戶端授權平台裝置授權。 |
CLiP device license not found. |
| 0xC0EA0004 | 用戶端授權平台 (CLiP) 授權具有無效的簽章。 |
CLiP license has an invalid signature. |
| 0xC0EA0005 | 用戶端授權平台 (CLiP) keyholder 授權無效或遺失。 |
CLiP keyholder license is invalid or missing. |
| 0xC0EA0006 | 用戶端授權平台 (CLiP) 授權已到期。 |
CLiP license has expired. |
| 0xC0EA0007 | 用戶端授權平台 (CLiP) 授權是由不明來源所簽署。 |
CLiP license is signed by an unknown source. |
| 0xC0EA0008 | 未簽署用戶端授權平台 (CLiP) 授權。 |
CLiP license is not signed. |
| 0xC0EA0009 | 用戶端授權平台 (CLiP) 授權硬體識別碼超出容忍度。 |
CLiP license hardware ID is out of tolerance. |
| 0xC0EA000A | 用戶端授權平台授權裝置識別碼不符合繫結的裝置授權中的裝置識別碼。 |
CLiP license device ID does not match the device ID in the bound device license. |
| 0xC0EB0001 | 此電腦上的平台資訊清單檔案未獲授權。 |
The Platform Manifest file was not authorized on this machine. |
| 0xC0EB0002 | 平台資訊清單檔案無效。 |
The Platform Manifest file was not valid. |
| 0xC0EB0003 | 此平台上的該檔案未獲授權，因為在平台資訊清單中找不到項目。 |
The file is not authorized on this platform because an entry was not found in the Platform Manifest. |
| 0xC0EB0004 | 此平台上的該類別目錄未獲授權，因為在平台資訊清單中找不到項目。 |
The catalog is not authorized on this platform because an entry was not found in the Platform Manifest. |
| 0xC0EB0005 | 此平台上的該檔案未獲授權，因為在內嵌簽章中找不到二進位識別碼。 |
The file is not authorized on this platform because a Binary ID was not found in the embedded signature. |
| 0xC0EB0006 | 此系統上沒有作用中平台資訊清單存在。 |
No active Platform Manifest exists on this system. |
| 0xC0EB0007 | 平台資訊清單檔案未正確簽署。 |
The Platform Manifest file was not properly signed. |