Failed to start cache / to convert this volume to a level-2 storage volume!

[Kalex]

Hey there, I'm currently in the trial period and also recently migrated from Legacy/BIOS with Win10 on a SSD to UEFI with Win10 on a M.2 PCIe SSD.
PrimoCache worked just fine before, but since the migration it has become unable to create any kind of Cache, no matter if I'm trying to create an L1- or L2-Cache.

If I try to create an L1-Cache, I get the following error message, no matter of what Block Size I choose. (I have 24 GByte RAM available which hasn't changed in the migration process.)

Code: Select all

Failed to start cache!
This is usually caused by insufficient system resources. You may choose a larger value for the Block Size and then try again. [0x0000026E]

If I try to create an L2-Cache, I get this error message when trying to create it on an SSD (tested with GPT and MBR):

Code: Select all

Failed to convert this volume to a level-2 storage volume! [0x0000026E]

...and this one when trying to create it on an USB3-Flash Drive (MBR):

Code: Select all

Failed to convert this volume to a level-2 storage volume! [0x00000000]

Is PrimoCache unable to work in UEFI-Mode or whats causing this issue?

[Support]

PrimoCache supports both Legacy BIOS and UEFI. Could you try the following steps?
1. Uninstalling PrimoCache,
2. Reboot the computer,
3. Install PrimoCache again.
If you still have the problem, I'm afraid the issue might be related to Windows migration. Was it a clean Windows install when you do the migration?

[Kalex]

I already tried this yesterday with no success.

It wasn't a clean&fresh Windows installation, I cloned my system partition over to an GPT-formated M.2, manually created an efi-partition with diskpart and it's bootloader with bcdedit, changed the BIOS-Setting to clean (as in CSM-free) UEFI and booted into Windows just fine.
Everything works, including other roughly comparable tools like ImDisk RamDisk, except for PrimoCache.
Hope we can somehow fix this.

[Support]

After a review of this issue we find that it might be caused by the trial expiration. We have sent you an extended trial license by email. You may check if this will fix the problem or not.

[Kalex]

This sadly made it worse, now it's telling me whenever I start the tool:

Code: Select all

The trial period for this product has expired!

What I've tried to fix this:
- just entering the key, doing a restart as asked by PrimoCache.
- uninstalling, restarting, installing, restarting, enter the key, restarting.

Now whatever I seem to try, it keeps telling me the trial period has expired.
According to the PrimoCache Setup File I downloaded and installed it on 9th July, if that helps.

[Support]

Could you check your Windows system time? Is it in correct date and time?

[Kalex]

Yes it is. Currently 11:37 AM, 26th July 2019.

[Support]

Sorry for the late reply. We was checking this issue and updated the license. A new email has been sent to you. Please check.

[Kalex]

Sorry to inform you, but none of that worked either.
I keep getting the error message on program startup that "the trial
period for this product has expired!" and "Trial period has expired.
Activate PrimoCache to continue using it." in the "About"-Dialog, no matter if I'm activating
it via the trial license information or using the license key file you sent me.
Something appears to be awkwardly weird with the application.

I also tried to uninstall it again, tried to manually search for any
remnant files and any remnants in the registry, before I then
re-installed PrimoCache but nothing changed.

[Support]

Could you please check if there are any scripts running at shutdown/logoff phase? Below are steps to check this.
1. Open GPE by entering "gpedit.msc" (no quotes) into the Run dialog (Win+R).
2. In the left panel, select "Windows Settings" under "Computer Configuration."
3. Double-click "Scripts (Startup/Shutdown)" in the right panel.
4. Double-click "Startup" and "Shutdown", and check if there are any scripts.
5. In the left panel, select "Windows Settings" under "User Configuration."
6. Double-click "Scripts (Logon/Logoff)" in the right panel.
7. Double-click "Logon" and "Logoff", and check if there are any scripts.