I recently broke my EMU PCM card. I installed a Steinberg midi device. It appears that all of my projects that were saved as .cwp files are looking for the previous EMU hardware. I had to go through every project and change the hardware device in each track and re-save to get them to work. All of the projects that are still .mid or .wrk are fine. I find this a bit odd but not surprising. There is no way to contact support on this matter so I am asking here. Have I missed something? Could there have been a global way of handling this issue? Everything is working after two days of editing but wow what a job. Thanks in advance.

A quick bump for you,
You might be able to use Windows file association located in Control panel.
Find the .EXT and change it once.
I've never heard of the EMU doing this before but I did have a program change my file extensions once and it was a huge cluster struck.
I opted the easy way out and reformatted my HD and reinstalled Windows. Mine was a bit different because it was all kinds of extensions. if its simply one or two, try File acc.

The issue is that SONAR stores I/O port names in the project file based on the way drivers are named and numbered in Windows, and cannot map old ports to new ones automatically. I ran into the same issue when my E-MU 1820m died and I switched to MOTU MIDI and audio interfaces.
 
Unfortunately, there is no other way of fixing this other than modifying and re-saving each project file with the new I/O assignments.
 
I'm not sure why the Bakers have never changed this to use 'friendly' I/O names which could be made to match for different interfaces. There must be some significant architectural obstacle.

Before Windows 10, Windows midi device management was awful. I'm not sure this one can be blamed on Sonar though it sure sounds annoying.

Thanks for the replies. It's just a pain that I will have to live with.