Issue still exists after allowing file mysqld.exe on both public and private networks. Is there another step that needs completed? When is the fixed update expected to be released?

Yes, we are still seeing issues. Please see KB article 102392 for instructions.

I'm having this issue with files on Sage Drive. If I do the instructions in the article, my file on Sage drive will sit there forever without a way to delete it. I've already got that issue with past files stuck in Sage Drive. Do you have a better solution for Sage Drive users?

Do you have 2020.1 installed yet?

Try this:  Close Sage 50, reopen, and uncheck the option for auto backups when t converts. 

Yes, I have the 2020.1 version installed and unfortunately it still loops around and around. No way to open the file again.

I don't know why it worked, or if this was a fluke, but I created a new company in Sage 2020.1 (all four or my true company files were stuck in this loop) and then once I had Sage 50 in version 2020.1 opened with a company (this fake test company) I was able to click File>Sage Drive>Download a Shared Company and then choose one of my real companies. The same prompt asking me to update the file to the newest version appeared so I UNchecked auto create backup and let the system go through updating my file and the company opened for me, updated and no loop! Repeated for all four companies and it worked with all. Again, could be a fluke that this worked after creating a fake company file, but at least I can complete payroll this week!

But it's worth sharing, which I will. Thanks.

I did, and the reply was "The fake company would not have done anything. If they would have closed out and tried to open the file again and uncheck the box the conversion would have worked as well.

 I have tested this on my own machine and with the auto backup checked it will keep looping and only way to get out of it is close and reopen the file." But thanks for sharing.

Eventually I needed the file so I used an older computer and opened the file under Sage 2020.0. At that point I took the file off Sage Drive and then converted it to 2020.1. That worked, but then I had to put it back on the drive so my clients could access their data again. 

Eventually I needed the file so I used an older computer and opened the file under Sage 2020.0. At that point I took the file off Sage Drive and then converted it to 2020.1. That worked, but then I had to put it back on the drive so my clients could access their data again.