Data Deduplication detected a new container could not be created in a chunk store because it ran out of available container Id. %1
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 ...