Thanks for this and all of your other points. On this one, maybe I am wrong about fileimage.dat. I was sure it was associated with CPM, but I honestly can't even recall why. At any rate, some combination of restarting the service and/or moving fileimage.dat worked for me. Thought I understood why, but maybe this somehow resets the key you mention.Thanks for the information. There are times where due to CPM not working, I've uninstalled and then reinstalled it, which has meant CPM has lost its database of installations. Now I know what file to backup. However, I have worked out how to reinstall CPM without losing anything. I run the installer again and then delete the CPMRestartCheck registry key.
One minute. I think now that you mention it, I do move fileimage.dat and then uninstall CPM. Then I reinstall CPM and turn off the service, replace fileimage.dat, and restart the service. I really should take notes when I do these things. At any rate, gonna commit all your info to a notepad now, so thx again.
@roger_m...is the 2.0 beta installer you use available someplace safe? I found it on some Russian or Latvian etc. download sites, but I don't want to install from an unknown site on a clean W10 installation. Can't seem to get .1.2.x to install on W10 Pro, even booting with the driver signatures unmonitored. CPM installer run as admin for W7 compatibility asks me to reboot and try again, which again fails...Do this at your own risk, as CPM can cause issues in rare cases. I'm using the beta of v2 of CPM.
Thanks for this. Think the issue with CPM is that Comodo let the driver expire. Don't know why, but they punted CPM for some unknown reason. It really works though...If you have it working without Test Mode enabled without disabling driver signature enforcement at each boot then this already means they sign their drivers