ISCL causing RazerChroma Freyja Haptic to stop working

[x8009]

For this time it worked fine, but since Razer Chroma 4.0.062 version instead 4.0.600 if ISCL start at boot the device won't vibrate, I never had that. only after not letting ISCL running at boot and chroma starts normally it would work like it should.
I don't know what has changed on 4.0.600 but they did fix something with turning it off and on issue where it wouldn't vibrate after. they have process called POWERTOOLS that keeps running with Razer Elevation Service that keeps it admin premission so it won't ask every sec checking if the haptic still running keeping it alive or checking if it's needed. maybe ISCL causing it to stop working? because I tried to reinstall CHROMA and nothing worked until just closing ISCL disabling autorun and everything worked and still working after. I tested it 10 times. ISCL not working everything works fine. I even tried newest version 1.4.4.4 something and still I had 1.4.0

[Wagnard]

For this time it worked fine, but since Razer Chroma 4.0.062 version instead 4.0.600 if ISCL start at boot the device won't vibrate, I never had that. only after not letting ISCL running at boot and chroma starts normally it would work like it should.
I don't know what has changed on 4.0.600 but they did fix something with turning it off and on issue where it wouldn't vibrate after. they have process called POWERTOOLS that keeps running with Razer Elevation Service that keeps it admin premission so it won't ask every sec checking if the haptic still running keeping it alive or checking if it's needed. maybe ISCL causing it to stop working? because I tried to reinstall CHROMA and nothing worked until just closing ISCL disabling autorun and everything worked and still working after. I tested it 10 times. ISCL not working everything works fine. I even tried newest version 1.4.4.4 something and still I had 1.4.0

If you start it manually instead ? does it work ?

[jamesadkins]

ISCL changes CPU standby/priority behavior, and with the newer Chroma versions it might be interfering with how the haptics service stays active at startup.
Since everything works when ISCL is disabled at boot, a few things to try:
Start ISCL after Razer Chroma has fully loaded
Run ISCL without aggressive standby clearing (or lower its frequency)
Make sure both apps run with consistent privileges (both admin or both not)
Looks like a timing/service interaction issue introduced in 4.0.600 rather than a hardware problem.

[immaterialpolicy]

With the more recent Chroma versions, ISCL may be interfering with the haptics service's ability to remain active at startup by altering CPU standby/priority behavior.