The device (%1) will not be used for a ReadyBoost cache because it is mounted read-only. This is usually caused by one of the following reasons: * Write-protected devices/media * BitLocker group policy settings prohibit write access to non-encrypted removable devices
The device (%1) will not be used for a ReadyBoost cache because a ReadyBoost cache already exists (on device %2) and only ...
The device (%1) will not be used for a ReadyBoost cache because it contains a configuration file which explicitly prohibits ...
The device (%1) will not be used for a ReadyBoost cache because it does not exhibit uniform performance across the device. ...
The device (%1) will not be used for a ReadyBoost cache because it does not have enough free space. Free Space %2 MB, required ...
The device (%1) will not be used for a ReadyBoost cache because it is mounted read-only. This is usually caused by one of ...
The device (%1) will not be used for a ReadyBoost cache because it is not attached to a supported interface. For USB devices, ...
The device (%1) will not be used for a ReadyBoost cache because it is not formatted with FAT, FAT32, or NTFS. Current Format:%2 ...
The device (%1) will not be used for a ReadyBoost cache because it is remote, read-only, virtual, or otherwise unsupported. ...
The device (%1) will not be used for a ReadyBoost cache because the device is too small. Size: %2 MB. Minimum Size: %3 MB ...