Windows 8
- d!. Save this numerical recovery password in a secure location away from your computer: %2!s! To prevent data loss, save ...
- D0_AoAcWake: NDIS is requesting that the device return to the operational power state because the device has indicated a ...
- D0_D3DCancel: NDIS is requesting that the device return to the operational power state because the D3-on-disconnect has been ...
- D0_D3DResume: NDIS is requesting that the device return to the operational power state because NDIS needed to interact with ...
- D0_D3DWake: NDIS is requesting that the device return to the operational power state because the NIC has indicated a wake ...
- D0_NicActive: NDIS is requesting device working power state due for maintaining connectivity during Connected Standby or ...
- DA MULTISITE: Site %4 is selected based on probing. Previously, TCP/IP sorting selected site %1 with metric %2 for address ...
- Data cannot be logged locally on the system. WSRM is unable to connect to Windows Internal Database. Please verify if Windows ...
- Data cannot be logged on the remote system. WSRM is unable to connect to Windows Internal Database. Please verify if Windows ...
- Data cannot be written to the output configuration file. This error is obsolete and should no longer be reported. Call Microsoft ...
- Data Center Bridging (DCB) is a suite of IEEE standards that are used to enhance Ethernet local area networks by providing ...
- Data Deduplication cancelled job type "%1" on volume "%2". Memory resource is running low on the machine or in the job. %3 ...
- Data Deduplication cannot run the job on volume %1 because the dedup store version compatiblity check failed with error %2. ...
- Data Deduplication corruption log "%1" has reached maximum allowed size "%2". No more corruptions will be reported until ...
- Data Deduplication corruption log "%1" has reached maximum allowed size "%2". Please run scrubbing job to process corruption ...
- Data Deduplication could not access global configuration since the cluster service is not running. Please start the cluster ...
- Data Deduplication could not create thread to poll for task scheduler stop message due to error %1. Task(s) may not stop ...
- Data Deduplication could not create window to receive task scheduler stop message due to error %1. Task(s) may not stop after ...
- Data Deduplication could not use BCrypt provider '%1' for hash algorithm %2 due to an error in operation %3. Reverting to ...
- Data Deduplication detected a container cannot be compacted or updated because it has reached the maximum generation. %1 ...
- Data Deduplication detected a corruption on file "%1" at offset ("%2"). If this condition persists then please restore the ...
- Data Deduplication detected a new container could not be created in a chunk store because it ran out of available container ...
- Data Deduplication detected an insecure internal folder. To secure the folder, reinstall deduplication on the volume again. ...
- Data Deduplication detected job type "%1" on volume "%2" page fault rate has lowered to desirable level. The rate is %3 page ...
- Data Deduplication detected job type "%1" on volume "%2" page fault rate is high. The rate is %3 page faults per second. ...
- Data Deduplication encountered a corrupted metadata file. To correct the problem, schedule or manually run a Garbage Collection ...
- Data Deduplication encountered an error while attempting to resume processing. Please consult the event log parameters for ...
- Data Deduplication encountered an unexpected error during volume scan of volumes mounted at "%1" ("%2"). To find out more ...
- Data deduplication encountered an unexpected error. Check the Data Deduplication Operational event log for more information. ...
- Data Deduplication encountered checksum (CRC) mismatch error while accessing a file in chunk store. Please run scrubbing ...
- Data Deduplication encountered chunk %1 with corrupted header while updating container. The corrupted chunk is replicated ...
- Data Deduplication encountered chunk %1 with transient header corruption while updating container. The corrupted chunk is ...
- Data Deduplication encountered corrupted chunk %1 while updating container. Corrupted data that cannot be repaired will be ...
- Data Deduplication encountered corrupted chunk container %1 while performing full garbage collection. The corrupted chunk ...
- Data Deduplication encountered corruption while accessing a file in chunk store. Please run scrubbing job for diagnosis and ...
- Data Deduplication encountered failure while reconciling chunk store on volume "%1". The error code was %2. Reconciliation ...
- Data Deduplication failed to dedup file "%1" with file ID %2 due to non-fatal error %3 %4. Note: You can retrieve the file ...
- Data Deduplication failed to initialize oplock as the file appears to be missing. File ID: %1 File name: "%2" Error: %3 %4 ...
- Data Deduplication full garbage collection could not achieve maximum space reclamation because delete logs for data container ...
- Data Deduplication full garbage collection phase 1 (cleaning file related metadata) on volume "%1" failed with error: %2. ...
- Data Deduplication full garbage collection phase 1 on volume "%1" encountered an error %2 while processing file %3. Phase ...
- Data deduplication Garbage Collection did not complete successfully for over a month. As a result, data deduplication cannot ...
- Data Deduplication Garbage Collection encountered a delete log entry with an invalid stream map signature for stream map ...
- Data Deduplication has detected a corrupt corruption metadata file on the store at %1. Please run deep scrubbing on the volume. ...
- Data Deduplication has disabled the volume %1 because it has discovered too many corruptions. Please run deep scrubbing on ...
- Data Deduplication has disabled the volume %1 because there are missing or corrupt containers. Please run deep scrubbing ...
- Data Deduplication has failed to load a corrupted metadata file %1 due to error %2. Deleting the file and continuing. %3 ...
- Data Deduplication has failed to load corruption metadata file on the store at %1 due to error %2. Please run deep scrubbing ...
- Data Deduplication has failed to process corruption metadata file %1 due to error %2. Please run deep scrubbing on the volume. ...
- Data Deduplication is using a strong cryptographic hash to detect duplicate chunks. In most situations, this level of verification ...
- Data Deduplication may not achieve maximum space savings as space freed up by deleted or modified files will not be reclaimed ...
- Data Deduplication may not have sufficient time to process data on the volume, leading to less space savings than expected. ...
- Data Deduplication saves disk space by storing a single copy of identical data on the volume. Specify the age of files to ...
- Data Deduplication service detected a corrupted item (%11 - %13, %8, %9, %10, %12) in Deduplication Chunk Store on volume ...
- Data Deduplication service detected a corrupted item (%6, %7, %8, %9) in Deduplication Chunk Store on volume %4. See the ...
- Data Deduplication service detected fixable corruption in "%5%6%7". Please run scrubbing job in read-write mode to fix this ...
- Data Deduplication service detected potential data loss (%9) in "%6" due to sharing reparse data with file "%8". See the ...
- Data Deduplication service encountered error while cleaning up corruption logs on volume %3. The error was %4. Some corruptions ...
- Data Deduplication service encountered error while detecting corruptions in chunk store on volume %3. The error was %4. The ...
- Data Deduplication service encountered error while determining corrupted user files on volume %3. The error was %4. Some ...
- Data Deduplication service encountered error while loading corruption logs on volume %3. The error was %4. The job continues. ...
- Data Deduplication service encountered error while loading hotspots mapping from chunk store on volume %3. The error was ...
- Data Deduplication service encountered error while repairing corruptions on volume %3. The error was %4. The repair is unsuccessful. ...
- Data Deduplication service encountered error while scaning dedup user files on volume %3. The error was %4. Some user file ...
- Data Deduplication service encountered too many errors while processing file on volume %3. The threshold was %4. Some user ...
- Data Deduplication service found %4 corruption(s) on volume %3. %5 corruption(s) are fixed. %6 user file(s) are corrupted. ...
- Data Deduplication service found %4 corruption(s) on volume %3. %6 user file(s) are corrupted. %7 user file(s) are fixable. ...
- Data Deduplication service has finished scrubbing on volume %3. It did not find any corruption since the last scrubbing. ...
- Data Deduplication was unable to access a file or volume. Details: %1 The volume may be inaccessible for I/O operations or ...
- Data Deduplication was unable to access the following file or volume: "%1". This file or volume might be locked by another ...
- Data Deduplication was unable to access volumes mounted at "%1" ("%2"). Make sure that dismount or format operations do not ...
- Data Deduplication was unable to create or access the shadow copy for volumes mounted at "%1" ("%2"). Possible causes include ...
- Data Deduplication was unable to save one of the configuration stores on volume "%1" due to a disk-full error: If the disk ...
- Data Execution Prevention helps protect against damage from viruses or other threats. Some programs might not run correctly ...
- Data Flush Pages/sec is the number of pages the file system cache has flushed to disk as a result of a request to flush or ...