One Step Update Not Working (Windows) [Edited]

Contacted Quicken about the problem 'stalling' during OSU and Cloud Sync before seeing this last response. Each activity was taking over 20 minutes to complete, was accompanied by the Quicken window blacking out and sometimes OSU and Scync would not complete. Further, during these 'stalls' CPU usage would hover around 10 to 12% CPU utilization (up from the normal 0.5% for Quicken). Not sure what this means and only noticed it because of the processor fan roaring for minutes on end.

After going through many steps (including employing old back up from prior to problem), the first tech was convinced that the difficulty centered on my 'back up' programs interfering with Quicken. Despite those programs being in place for years without a problem I went through and shut them down. That encounter was about an hour on the phone and did not result in any detectable difference in the OSU and Sync issues.

The second phone call to Quicken support for the stalling issue was about 2 hours long. Back up was disabled since the first call. Multiple avenues were approached including validating the file, shutting down Synch, and shutting down updates on individual accounts. Notably, during the error check process the report indicated that thee were some problem with transactions were from over 10 years ago and the report indicated that they were from "1900". These transactions were allowed to be 'cleared' by the program. Ultimately, OSU and Sync were relatively improved; OSU now typically takes 5 minutes and Cloud Sync takes another 5 minutes when the program is closing. Both activities are accompanied by periodic blacking out of the Quicken window and a big jump in CPU usage for most of the process.

Quicken has been, for the most part, a great tool for many years. The organization and updating with multiple institutions typically took less than a minute. However, this new norm of 10 minutes or so a day which equates to (60 hours per year) of watching updating circles spin and 'processing' messages blink is unacceptable. Further, such a situation makes me concerned about the accuracy of the updates. If this situation can not be corrected to the prior level function for Quicken then it may be time to let Quicken go.

BTW, I am running Version R38.3, Build 27.1.38.30 on a Windows 11 machine. I am not experiencing any problems with any other program on my machine and updates to Windows and malware programs are checked daily. Willing to follow the Mondo patch suggestion above but it was not suggested at the time by the Quicken techs. Any suggestions would be appreciated.