Quick update. I had hoped that the problem would disappear with the installation of v3.5, but no luck. I have noticed though that the problem only occurs with one of my camera bodies. Of course, it is the body I use 95% of the time. I do not understand why it would be the camera body though since the problem is relatively new and I have been using that camera body for several years. So whatever has changed is also effecting images that have been in the catalog since v2.2.
Still hoping that someone out there will have seen and solve this problem.