Complete uninstall of jamovi - Make it "it's alive" again...
Posted: Thu Oct 10, 2024 6:20 pm
Hello,
One of my student had a functional jamovi version 2.6.2 and after some analysis, the dreaded message "this analysis has terminated, likely due to hitting a resource limit" appeared. Then it remained even when using basic descriptive functions. We tried following some suggestions here https://github.com/jamovi/jamovi/issues/1515 with no success. We tried uninstalling jamovi, reinstalling it, upgrading to a newer version, uninstalling all modules, reinstalling jamovi, still getting the same infamous message, even when using a new data file from scratch.
So my question is: in what folders is jamovi installed ? In Windows, is everything stored here? C:\Program Files\jamovi 2.6.2.0
or are some dependencies stored elsewhere ?
My reasoning is that by deleting everything manually, we will make it work again. There seems to be a file that is not automatically deleted by Windows when the program in uninstalled and that file is creating a problem even when the application is reinstalled.
Regards,
Michael
One of my student had a functional jamovi version 2.6.2 and after some analysis, the dreaded message "this analysis has terminated, likely due to hitting a resource limit" appeared. Then it remained even when using basic descriptive functions. We tried following some suggestions here https://github.com/jamovi/jamovi/issues/1515 with no success. We tried uninstalling jamovi, reinstalling it, upgrading to a newer version, uninstalling all modules, reinstalling jamovi, still getting the same infamous message, even when using a new data file from scratch.
So my question is: in what folders is jamovi installed ? In Windows, is everything stored here? C:\Program Files\jamovi 2.6.2.0
or are some dependencies stored elsewhere ?
My reasoning is that by deleting everything manually, we will make it work again. There seems to be a file that is not automatically deleted by Windows when the program in uninstalled and that file is creating a problem even when the application is reinstalled.
Regards,
Michael