2015/09/06 15:23:37
Canopus
cowboydan
I had this problem since the install of Windows 10. The workaround that I use is:
Go to Control Panel
             /System and Security
                      /Administrative Tools
                              /Services
                                   /Pace
                                       Right click (or dubbel click) and RUN Pace.
In the service  menu, Pace is in Automatic mode but is not running.



That seemed to work for a while. But having the service "PACE License Services" kept in Automatic mode while starting it manually made my system really unstable and unable to boot about half of the times. And the remaining times Windows 10 refused to shut down. I had to use the Big Blue Button on my workstation each time in order to end the misery.
 
So I finally got a lead in a KVR Forum thread, rebuilt my iLok license database, and additionally realized that I had to change the "Startup type" for this service from Automatic to Manual. This last step was crucial.
 
The drawback is of course that I will have to start this service manually each time I boot the system, but at least I can use my iLok dependent plug-ins in Cakewalk running Windows 10 while not having my system freezing up. I sure hope Microsoft and/or PACE is made aware of this problem and that they will come up with a permanent solution real soon.
 
This worked for me, but I'm seriously considering going back to Windows 7. Follow my steps at your own peril.
 
What a way to spend the better part of a Sunday.
 
EDIT:
I think I've found a better solution that actually solves the problem without the additional headache of having to manually start the "PACE License Services" after each reboot. Changing the default start type from "Automatic" not to "Manual" but to "Automatic (Delayed Start)" makes Windows wait for two minutes before it actually tries to start the service. And somehow this seems to solve the problem. I've tested this with three consecutive reboots and it works as far as I can see every time.
 
2015/09/06 15:34:21
cclarry
Canopus
cowboydan
I had this problem since the install of Windows 10. The workaround that I use is:
Go to Control Panel
             /System and Security
                      /Administrative Tools
                              /Services
                                   /Pace
                                       Right click (or dubbel click) and RUN Pace.
In the service  menu, Pace is in Automatic mode but is not running.



That seemed to work for a while. But having the service "PACE License Services" kept in Automatic mode while starting it manually made my system really unstable and unable to boot about half of the times. And the remaining times Windows 10 refused to shut down. I had to use the Big Blue Button on my workstation each time in order to end the misery.
 
So I finally got a lead in a KVR Forum thread, rebuilt my iLok license database, and additionally realized that I had to change the "Startup type" for this service from Automatic to Manual. This last step was crucial.
 
The drawback is of course that I will have to start this service manually each time I boot the system, but at least I can use my iLok dependent plug-ins in Cakewalk running Windows 10 while not having my system freezing up. I sure hope Microsoft and/or PACE is made aware of this problem and that they will come up with a permanent solution real soon.
 
This worked for me, but I'm seriously considering going back to Windows 7. Follow my steps at your own peril.
 
What a way to spend the better part of a Sunday.
 



I've been running Win 10 since the very first preview and iLok gave me no problems...

It wasn't until I installed the Latest Preview Build 10532 that the problem occurred.
Rolling back to the previous build solved the iLok problem, but killed my AudioDirector 5
program, which is supposed to be (and was) Win 10 compatible BEFORE the update and reversion.

Now it won't open at all.. but everything else seems to be fine...
2015/09/06 15:59:20
kitekrazy1
Was this a Windows Update or an Insider Build update?
2015/09/06 16:57:43
cclarry
kitekrazy1
Was this a Windows Update or an Insider Build update?



Insider Build Update
2015/09/06 22:24:28
kitekrazy1
cclarry
kitekrazy1
Was this a Windows Update or an Insider Build update?



Insider Build Update




 I stopped those. The last one was bad for me.  I have networked drives and shared folders and it totally mess those up. It would ask for a password when I tried to access folders from another machine. Turn off password protected sharing was enabled and that build broke that.  One of the first things I use to disable was system restore. Not any more.
12
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account