Ticket UUID: | 840eb0b51cab92baffda34d54abac5d0a9a40787 | |||
Title: | [unconfirmed] Lost accounts (decryption error) if ripcord isn't cleanly shut down | |||
Status: | Open | Type: | Bug | |
Severity: | Minor | Priority: | Low | |
Subsystem: | General | Resolution: | Open | |
Last Modified: | 2021-06-03 23:35:41 | |||
Version Found In: | 0.4.26,0.4.28 | |||
silverbacknet — 2020-08-28 16:47:37 Message box:
I can reliably reproduce the error by rebooting without manually shutting down Ripcord first. It's not too hard to re-authorize, but it does get annoying when I've been updating drivers that require a reboot. | ||||
cancel — 2020-08-28 19:15:15 Do you have some kind of enterprise management or provisioning software installed on your PC? Or some special anti-virus? It looks like something is tampering the Windows Credential Store. | ||||
silverbacknet — 2020-08-29 08:46:37 Aside from Windows Defender, nothing like that, though there's a lot of software in general. I'll try to run some captures and see if I can record anything weird. Now that I know it's in Credential Store, I can try to narrow it down. | ||||
GreenReaper — 2021-05-11 19:29:59 I got this on Windows 10 for both Discord and Slack when restarting after today's cumulative update. When restarting the app it continued to trigger until I set an account in the relevant services. I don't think I explicitly closed Ripcord when restarting. Maybe it needs to hold up the reboot while it shuts down and syncs data to disk? There is an option for that. Or perhaps it was something to do with the update? I did also install an update to Windows Admin Center yesterday. It needed to add a user certificate. My bet would still be related to the reboot, as my netbook's CPU is very slow and the default time given is not that long (and this after a heavy update which might make the old SSD slow to respond as well). | ||||
cancel — 2021-06-03 23:35:41 I really think it's something else tampering with the credential store. It's pretty unlikely that shutting down without first quitting causes this, because Ripcord normally doesn't write to either the credential store or your account file except when you're changing it, so there's usually no incomplete write operation that could get interrupted by an unexpected restart. I've tried this multiple times on my own computers and it never happens for me. (In fact, that's normally what I do: I just shut down my computer without first quitting Ripcord.) |