[@benasp] agreed, windows already uses spare RAM as local drive vcache so what is the real world benefit of this apart from a UI showing cache hits and misses which is not shown by windows on its cache… Is it worth the risk of instability installing a 3rd party driver for the 3rd party cache… Also part of the function of a cache like this is to reduce writes to write limited SSD drives but this offers the chance to use SSD drives as caches for conventional electro-mechanical hard drives… which negates the write life saving of write cacheing SSD’s ideally what we want is write cacheing with no write through certain folders like the various TEMP folders and maybe the events log folder root. It is unclear how this cache works in tandem with windows own vcache system or does it disable the windows vcache mechanism… too many unknowns to be able to make an intelligent informed decision on this product… Although installing it onto my 32bit Vista based server with 8G RAM in the patched system to allow windows to use it all… getting QILING fast cache to cache the C: system conventional drive with a 4.28G cache setup the physical system drive has now managed for the first time to enter power saving standby mode due to inactivity… obviously it does not stay in standby mode as the cache hit rate is only 55.83% but that is a noticeable reduction in drive activity, I am not convinced it would be wise to put it on my win10 or above machines as yet.