Statistical information stays after a fast startup/shutdown cycle in Win 10 Topic is solved

[caqde]

PrimoCache version: 2.00
Cache Settings: Read/Write 4.5GB L1/250GB L2
Windows OS: Windows 10
Hardware Information (CPU/Motherboard/Memory/Harddisks):
Description: In Windows 10 if you shutdown the system with fast startup enabled (DEFAULT action for Windows 10) Primocache will start with the last sessions Statistical Data intact

Basically if you shut your system down and turn it back on using Windows 10 and never reset your statistical data will continue growing to infinity with the way things work as they are now unless a user modifies the Default shutdown method or has a system that can't hibernate (In which case fast startup is automatically disabled)

[Support]

Actually this is not a bug. It is by design. With fast startup enabled, Windows enters hybrid shutdown mode, somewhat like hibernate does. And the cache contents are also conserved. So the statistical data is also kept.
In future versions, we'll add options to allow users release the cache (to reduce shutdown time) and other related information data, thus making it like a shutdown.
Thanks.

[caqde]

Actually this is not a bug. It is by design. With fast startup enabled, Windows enters hybrid shutdown mode, somewhat like hibernate does. And the cache contents are also conserved. So the statistical data is also kept.
In future versions, we'll add options to allow users release the cache (to reduce shutdown time) and other related information data, thus making it like a shutdown.
Thanks.

Given that most users would not know about this. In their eyes the rolling over of the statistical data would be seen as an unwanted feature or bug. Especially given that fast startup is a default and not an option that would need to be selected by the user. Although personally I would prefer that the statistical data would not roll over so I can see how much of an effect the L2 and L1 cache have on fast startup. It is good to know that you will eventually give us the option to change this behavior.

[Support]

Well, this issue has been fixed in version 2.2.0.
Thank you all!