Skip to content
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

why AdGuard E-Mail promote 7.20.0 update when even critical bug is reported? #5378

Open
3 tasks done
hong620 opened this issue Feb 27, 2025 · 6 comments
Open
3 tasks done
Assignees

Comments

@hong620
Copy link

hong620 commented Feb 27, 2025

Please answer the following questions for yourself before submitting a question.

  • I am running the latest version
  • I checked the knowledge base and found no answer
  • I checked to make sure that this issue has not already been filed

Ask a question

  1. why push the malfunctioning build that has critical bug reported during beta?

  2. why push the build and release without real world field tests?

  3. why AdGuard promotion e-mail send 7.20.0 update promotion even in critical bug already reported and on-going few days back?

  4. why even 7.20.0 version didn't rollback from update servers to avoid more victims?

  5. even in a simple automated test builds, fairly can check the AdGuard and AdGuard Browser Assistant totally not working on Firefox Specific, how could this pass the internal tests?

  6. since russian sanction and war, AdGuard Forum was totally discontinued, in this kind serious situations tons of customers exposed to tons of trackers in windows desktop and custom filter data loses, 'forum not exist' itself could be more legally serious issues?

  7. there's any way to recover or rollback the user's data and setting?
    seems there's no temporal backup file system in adguard itself.
    some peoples might be consider this as 'intended attack to use specific commerical solution customers'

@KolbasovAnton
Copy link

@hong620 Greetings! We apologize for the inconvenience caused, using this version of the application and following the instructions you will be able to restore all the lost settings.

  1. Open File Explorer and navigate to the path %programdata%/adguard/backups

  2. Find the backup zip file associated with the 7.19 version. It will be named something like adguard_settings_7.19.... Save this file somewhere.

  3. Uninstall AdGuard, but make sure to keep your settings (don’t check the box Delete settings).

  4. Go back to File Explorer and navigate to %programdata%/adguard. Delete the FLM folder and the adguard.db file.

  5. From the zip file you saved in step 2, extract the adguard.db file and copy it to the %programdata%/adguard folder.

  6. Finally, install version 7.20.1. Your settings should be restored.

Please, let us know, if any of your issues are still reproducing.

@majo-z
Copy link

majo-z commented Feb 28, 2025

  1. Find the backup zip file associated with the 7.19 version - I have no zip file in the backups folder, there is only user_S-1-5-21-3114501870-1540493806-398104678-1001.config file.

  2. ... Delete the FLM folder - There is no FLM folder, only these folders and files: Backups, Core, Crashes, DnsFilters, Flags, HostManifests, Logs, SSL, Temp, and adguard.db.

@KolbasovAnton
Copy link

@majo-z Hello. You updated from 7.19 to 7.20, or which specific version are You currently using?
The absence of the archive with previouses version database means that You install the current version "from scratch".

@majo-z
Copy link

majo-z commented Feb 28, 2025

@KolbasovAnton Hello, I exported 7.19 settings before the 7.20 update. I have experienced all sorts of problems after the 7.20 update (user rules list gone, extensions gone, many filters disabled, etc.). Because the 7.20 version also failed to import my previously exported settings, I uninstalled it (checked the 'Delete settings' box), installed back the 7.19 version and successfully imported the settings. So I am currently using 7.19 version.

@KolbasovAnton
Copy link

@majo-z Ok! Now You can update to 7.20.1 version without doubts, this bug was fixed.

@majo-z
Copy link

majo-z commented Feb 28, 2025

@KolbasovAnton I can confirm the 7.20.1 version is working fine. I haven't noticed the version in the AdGuard program has changed from 7.20 to 7.20.1 overnight. Thanks for your help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants
@hong620 @majo-z @adguard-bot @Aydinv13 @KolbasovAnton and others