-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
119.0.6045.214 AVX breaks passwords and more #38
Comments
@MaggotHATE Yeah.... That's what can happen when you upgrade or downgrade 10 versions. There's no way to fix it AFAIK. Chromium only guarantees user profile backwards/forwards compatibility up to two major versions. I knew this could happen, but it didn't cross my mind because I did all my testing in Windows 7/8.1 Virtual Machines, instead of my real Win7 installation (where I have passwords saved and would have noticed it) Updated the release with info concerning this. |
@Alex313031 So, what can I do to have a chance of updating safely in such case? Or am I stuck on 109? Does |
@MaggotHATE I would reccomend just deleting all passwords and re-log into your sites, or start with a fresh profile on M122 (latest release), and re-login to your sites there. You could back up your bookmarks. |
@Alex313031 Well, thanks for answering! Guess it's time to get more used to Bitwarden - with how things are going I'll have to move to Ubuntu anyway. It was a good run on win8/8.1, time to move on. |
System Details
Problem
Updating from 109.0.5414.173 to 119.0.6045.214 (AVX, always zips) broke my passwords, making them into gibberish. When I tried rolling back to 109.0.5414.173 (replaced back "chrome_proxy.exe", "initial_preferences", "thor_ver" and "thorium.exe", "109.0.5414.173" folder is in BIN too), it broke the entire browser and my userdata (- 2 months of...everything, I guess?). Now I have to use my ~old userdata backup and 109.0.5414.173.
Additional Notes
I expected this release to be experimental, of course, but not that destructive.
The text was updated successfully, but these errors were encountered: