pinguinotuerto
Wouldn't it be easier to just roll SONAR back to the version that was working until you're done with this big project? Never a good idea to update in the middle of a big project. Especially if things are working well.

This was my first reaction, too. But the OP's project is long-term, and he's probably unwilling to forego multiple SONAR bug fixes and enhancements for years to come.

bitflipper
 
Although audible differences between versions seems unlikely, the only way to know with certainty would be a null test.

that's probably a good idea to test for yourself and also to convince the customer that it is the same - assuming it works ;-)
 
upgrade to later WAVES plugs, open old project & bounce, if identical keep (make new backup), if not roll back to usable version and stay there...

bitflipper

pinguinotuerto
Wouldn't it be easier to just roll SONAR back to the version that was working until you're done with this big project? Never a good idea to update in the middle of a big project. Especially if things are working well.

This was my first reaction, too. But the OP's project is long-term, and he's probably unwilling to forego multiple SONAR bug fixes and enhancements for years to come.

I see! Makes sense. My experience with Waves' tech support so far has been very positive. Give them a call. Hold times are short and they'll probably be able to help you figure it out.

As someone who provides tech support in my day job, and has done so for 35 years, I guarantee the first thing Waves Support will suggest is updating the plugins. Step #1 is always to bring the software up-to-date and see if the problem is still reproducible. It's unlikely they'd be able to reproduce Thomas' exact setup anyway, and even if they could, they're not likely to pursue it if it doesn't apply to the current revision.
 
Unfortunately, the OP's situation is highly unusual. Not unique, but unusual.
 
When I did O/S support back in the day, I had a nuclear power plant that was so far out of rev there were only a couple guys in the office who were knowledgeable about their software. Newer, younger guys (like me) would tell them to upgrade. But the plant was under strict NRC regulations that made it extremely difficult and time-consuming to upgrade any software, requiring them to stay on a known stable version for years and years. It was, after all, a nuclear power plant! If it ain't broke, don't touch it. 
 
For them, the answer was the same as it may have to be for Thomas: they froze those machines in time and never updated ANYTHING. At least until a piece of hardware broke down that was no longer manufactured. One solution for the OP would be to set aside a computer that's dedicated to this one project, and NEVER update it.

Would it be possible from the anniversary Windows 10 update which has disabled many other plugins?
 

Thank you.
Anniversary Windows 10 update was not the problem. When I rollback to 2016.08 the plugins V9.18 work.
 
My customer says NO CHANGE of versions. After this large digitization project (National library) the customer wants to have ONE computer with ONE version of plugins for 2 years. If something needs to be reworked later. This computer is simply retained. This computer can only have ONE version of plugins that where used over the whole project for over 3 years.
So I will roll back with one computer to 2016.08 and buy a new computer. So the customer can keep this computer with his licences.