updates change the sounds of the instruments in my saved musescore files

I am a great fan of musescore - it has changed my life. Having said that, with each recent update (I just downloaded the latest 3.0.1.5807 update for example) - it annoys me to find that when I open a saved musescore file - for example with a cello, or a clarinet - the sound fonts I had carefully selected and deliberately saved with the previous version are now changed! And that is whether I "reset the position of all elements" or not, as the opening pop up window in the new version recommends. This is totally frustrating. (Hey I realize the creators of Musescore are saints and benefactors of mankind, but I'm just saying) I am really glad that installing the Musescore 3 didn't overwrite my Musescore 2.3.2 because if I open the same file there the cello font I selected still sounds wonderful. In the new Musescore I now have to try and refind the original cello font - and that's also a problem. There are at least two cello sound fonts and both are called simply 'cello'. But I find it and ok. It's annoying but apparently solvable.
But now I open up a piece with a Bb Clarinet and first in playback there is just silence - then I see in the Mixer panel the Clarinet is set to Yamaha Grand Piano!!?? If I open the same file in 2.3.2 the instrument is Woodwinds- Clarinet Solo. What's happening???? What is this all about? I open up the 'patch' search (which in the previous version was called more obviously 'sound') and whereas in 2.3.2 you could see how far down you were in the list, with the new version you are scrolling blind. And whereas my Woodwinds - Clarinet Solo was at the bottom in 2.3.2 in the new version I have no idea where it is. It appears that there are two "Clarinets" and neither is as beautiful as my original one. I'm not sure I understand what is going on here. My Sound font sources are apparently the same but the sounds they generate aren't???
At this point I think I will probably continue to use the older version which I am very comfortable with. At least until this gets fixed... This doesn't alter my admiration for the Musescore Creators!