Pro Tools 12.5 suddenly unable to initalize the yamaha steinberg USB ASIO & stops responding on close

[event2020]

Pro Tools 12.5
Windows 10
Steinberg UR22 C

After around 8 months of working perfectly (rock solid) after a fresh install on a new machine Pro Tools all of a sudden gives the error "could not initalize the yamaha steinberg USB ASIO" and then goes unresponsive. The only way I can make it close is to use Ctrl Alt Delete > task manager > end process. This happens regardless of existing PT session or new session.

I have spent 3 solid days including VERY late nights trying to fix this - I have searched extensively on google and read every post and forum thread I can find including Avid's and not one suggest has worked.

I have tried so many things that I can not remember them all: open Pro Tools, create a new session using the bit rate/sample size my UR22C is set to then restart Pro Tools to reset, reinstall of my UR22C and Yamaha USB drivers, complete uninstall of pro tools incl manual deletion of left behind hidden folders and upteen registry keys followed by a fresh install of pro tools.

I know it is not the UR22C because as soon as I had to kill the PT process in task manager I opened my Cubase Pro 11 with a fairly high track and plugin count and it did not even break a sweat. Same goes for Studio One 5, Sound Forge Pro, RX 8 and any other app that needs the UR22C.

I tested my 22C with the above programs straight after each time Pro Tools threw the error so I am 100% confident the issue is Pro Tools.

My DAW is more than well spec'd for Pro Tools on Windows and is NOT connect to the net apart from licence downloads and auth. Windows update is fully disabled and I am 100% confident nothing has been downloaded by update without me knowing about it.

Avids own forum is next to useless and I see a lot of people are experiencing this issue with PTs albiet with varying sound interfaces. All Avid suggest is what I have already tried.

I am at my wits end and this is the last thing I need to be dealing with when I have client deadlines looming. I am on the verge of loosing it which is unlike me but thats how wound up I am. Three days trying to fix something that should not be happening with little to no help from Avid.

If anyone can help, I would be so grateful.

[antic604]

Have you tried using a generic ASIO4All driver? Can you borrow a different audio interface from someone and test that? I know you said the UR22C - I'm assuming with factory drivers - works just fine in other DAWs, but that'd at least give you some time to wrap up current client work and move to another, more reliable DAW...

[event2020]

Hi antic604 Thank you for your reply.

Yes I have tried both the generic ASIO that comes with PTs and ASIO4All but sadly they have the same result in Pro Tools.

Sadly due to where I live I do not know anyone who has a different interface I can burrow.

My work requires that I use PTs so I need to find a solution.

[Cancel Culture Club]

after a fresh install on a new machine Pro Tools all of a sudden gives the error

This part concerns me, not exactly sure how Protools 12.5 operates on Windows 10, but a simple check, did you reregister your new computer for Protools on Avid's site?

I'm not sure how their copy protection works these days, it's been years.