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

[BUG] Config is lost when updating with the prompt #486

Closed
Moustachauve opened this issue May 2, 2021 · 5 comments
Closed

[BUG] Config is lost when updating with the prompt #486

Moustachauve opened this issue May 2, 2021 · 5 comments
Labels
question Question asked. resolved Problem resolved or will be resolved in next version.

Comments

@Moustachauve
Copy link

When starting NH Quickminer and seeing the prompt asking if we want to update to the newest version, saying yes will reset the current config and will not make a backup of it, so all configs and overclocks are lost

@Moustachauve Moustachauve added the bug Something isn't working label May 2, 2021
@nicehashdev
Copy link
Contributor

Please, check your AV. This must be issue with your AV deleting some NHQM files.

@nicehashdev nicehashdev added question Question asked. resolved Problem resolved or will be resolved in next version. and removed bug Something isn't working labels May 4, 2021
@Moustachauve
Copy link
Author

Moustachauve commented May 4, 2021

@nicehashdev My antivirus (windows defender, default on windows 10) has the NHQM folder whitelisted. This was my first time updating using the prompt as I usually update manually by overwriting my files from the zip (and being careful not to override the command.json file)

I reproduced this on both my computers running NHQM

@nicehashdev
Copy link
Contributor

Unfortunately, due to bugs in Defender, this is not enough. You have to explicitly allow in Defender to let all NHQM files through.

@Moustachauve
Copy link
Author

@nicehashdev like so?
image

If yes, then it was already done

@nicehashdev
Copy link
Contributor

This is exclusion list which is usually not enough. You need to explicitly allow it when defender asks you for it. Read more here: #204

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Question asked. resolved Problem resolved or will be resolved in next version.
Projects
None yet
Development

No branches or pull requests

2 participants