This has now been confirmed by the iLok devs. They are working on a fix.
Those of you who have not had an issue, it’s because you’re not using any plugin that used the very latest toolkit when built.
Plus a number of other coincidences.
Cheers all.
4 Likes
@Phil_Pendlebury Are you in contact with PACE or any host or plugin developer about this? I have a couple of bug tickets running, but I doubt that anyone will push the information when the fix is available. I haven’t even received any confirmation that this is a PACE issue. If you hear anything about a fix version being released, it would be perect if you could inform this thread.
1 Like
Yes, I am and yes of course I will.
2 Likes
Hey Phil, how lovely to hear from you and fanx for the info. I think in my case it was the “perfect storm” with various updates and housekeeping all arriving at the same time. With the help of the good folks on here i have nailed it and have enjoyed a “drama free” week.
Are you still out in the dust, or back in Blighty?
1 Like
Glad you got it sorted Glenn, the perfect storm, indeed those days happen eh…
Yes, still in the land of sand. 
1 Like
It’s an easy to resolve issue in terms of rebuilding the plugins with the older toolkit which I did last week as a workaround, and I gather a proper fix will be coming along as well. It only presented for me when installing the .40 DAW updates.
3 Likes
I haven’t updated .40 due to major bugs when using Atmos. This isn’t a problem that happens only in the .40 versions, it’s happening in .32 as well and I suspect pretty much every Steinberg software using the vstscanner and vstscanner master, including Dorico where I first noticed this.
2 Likes