MagnusDB's Posts

Well, well, What can I say... After we noticed that renaming Anaconda3 directory and naming it back again (after the packaging ​proccess) made it work properly for the user, we experimentally try to... See more...
Well, well, What can I say... After we noticed that renaming Anaconda3 directory and naming it back again (after the packaging ​proccess) made it work properly for the user, we experimentally try to do the same procedure while capturing the package and .... voilà... it worked. In other words, after installing Anaconda3 for all users and installing some libraries for python while packaging, we just renamed "C:/Anaconda3" directory as "C:/Anaconda3abc" (it took some time) and then renamed it back to "C:/Anaconda3". For some reason it was enough to make Anaconda work properlly for the final user.
Thank you for your reply Micheal. We have not tested yet your suggestion, but hermanc01 command did not work for us. The same problem persisted. Nevertheless, something interesting occured in some te... See more...
Thank you for your reply Micheal. We have not tested yet your suggestion, but hermanc01 command did not work for us. The same problem persisted. Nevertheless, something interesting occured in some tests. After the capture, when we renamed the Anaconda directory to any other name and then renamed it back to the original name the software works perfectly. We noticed that in the first time, it tooks a couple of minutes to complete (probably copying files from C:\SnapVolumesTemp\MountPoints\{...}\{...}\Anaconda3 to the user space) , but when renaming back to the original name, it tooks less than one second (no physical copy required). Hence, we think maybe Anaconda3 is keeping some wrong references when inside the SnapVolumesTemp. Let's see if we can find out a solution based on your suggestion.
I have a similar issue with Anaconda3 packaging. I'm using the default instalation directory (C:\ProgramData\Anaconda3) in an instalation for all users. The CLI based application is able to run the A... See more...
I have a similar issue with Anaconda3 packaging. I'm using the default instalation directory (C:\ProgramData\Anaconda3) in an instalation for all users. The CLI based application is able to run the Anaconda prompt, but the anaconda-navigator won't open. Running through CMD I got the error in the attached image. I also got some weird errors when importing numpy and matplotlib packages. The errors says: 'File "C:\ProgramData\Anaconda3\lib\site-packages\numpy\__ini__.py, line 126, in <module> from numpy.__config__ import show as show_config ModuleNotFoundError: No module name 'numpy.__config__' And in the end, it follows: "ImportError: Error importing numpy: you should not try to import numpy from its source directory; please exit the numpy source tree, and relaunch your python interpreter from there." It might be important to highligh that only anaconda3 was installed (conda version 4.10.1 and python version 3.8.8) during the packaging process, i.e. no pyqt or other libs were installed before or after anaconda3 installation, which could cause some incompatibilities and problems. I will try the suggested command and check if it solves the problem "Anaconda3[version].exe" /InstallationType=AllUsers /AddToPath=0 /RegisterPython=0 /S /D=C:\Anaconda3