"Finishing Steam cloud sync" - It stays forever.

[Guizunga]

As soon as I accept Steam's update and restart, it pops this window saying: "Finishing Steam cloud sync". And it stays forever. How to proceed?

[ginomsi]

I have the same problem

[Jaunty]

I'm encountering the same thing. There is slightly different behaviour based on how the Steam app is being closed. The behaviours are:

> When simply exiting steam,
>> a window appears with "Finishing Steam cloud sync" appears with the buttons "Exit Now" (disabled, eventually becomes enabled) and "Cancel". The sync will never resolve,

> When selecting "Update and Restart" from an update notification,
>> a window appears with "Finishing Steam cloud sync" appears with the buttons "Exit Now" (disabled, DOES NOT become enabled) and "Cancel". The sync will never resolve and I must hit cancel.

> When logging out of steam account via "Change Account",
>> a window appears with "Finishing Steam cloud sync" appears with the buttons "Exit Now" (disabled, DOES NOT become enabled) and "Cancel". The sync will never resolve and I must hit cancel. Same as Update/Restart.

Details & Notes
- Settings > Account > Steam Beta participation: Steam Beta Update
- Settings > Cloud > "Enable Steam Cloud [...]" can be enabled OR disabled, THE ISSUE OCCURS WITH 100% REPRODUCTION REGARDLESS OF CLOUD ENABLED/DISABLED
- This issue is encountered 100% of the time when performing any action that would close or log out of the application (exiting, updating, or logging out of steam).

Workaround(s)
- Steam can be closed via task manager.
- To exit steam, wait for the "Exit Now" button to become enabled and press it.
- To apply updates to steam, close steam using one of the above workarounds and start it again manually. Updates will be detected and applied during the boot. Note that even after all updates as of the date of this post the issue has 100% reproduction.
- To log out of steam select "Change Account" and then close Steam using one of the above workarounds. You will be prompted to log in on next boot. The issue will still reproduce itself after a log-out log-in.

Please let me know if this issue can be resolved through any actions taken client-side.

[Yes-Man]

Same here.

[Big]

Same problem :c

[Jaunty]

As of this writing, I no longer encounter this error. Not sure what changed (upate or actions taken on my side)