-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Online v2.7.1 release doesn't open, offline v2.7.0 release does #1998
Comments
It is working fine if you download the 2.7.0 exe file from GitHub and install it. |
I assure you, we have not placed a virus inside of the GPT4All distribution binaries. But if you don't believe me, you can build it from source. You should add an exception for the |
I have never accused you for placing virus. It's just the newer version is not working. Even if i turn off the windows defender it is not working. The chat ui dosent open. I will wait for next version to start using it again. Thank you. |
From the title it sure sounded like it.
If Windows Defender quarantined some part of GPT4All, it won't function anymore. You should completely uninstall it (and remove |
I'm having this same issue and will need to rollback to 2.7.0 as well. Models unable to run in 2.7.1 |
It worked. |
I'm not sure if there was an update or I followed some different set of steps, but I actually finally got 2.7.1 to work by sideloading the model into the .cache/gpt4all folder and then uninstalling and reinstalling 2.7.1. When it opened, the mistral model worked and now downloading other models appears to be working as well. Thank you for your help! |
Bug Report
I upgraded the app from 2.70 to 2.71, and first Windows Defender gave me a virus notification and removed some files and then the app stopped working.
Steps to Reproduce
Upgrade from 2.70 to 2.71 using in app upgrade option on windows 11
Expected Behavior
Nothing works. The chat UI doesn't start and the issue persists even after reinstalling until I downgraded to 2.7.0.
Your Environment
The text was updated successfully, but these errors were encountered: