4.72 FAQ-1202 Internal Python packages that are installed by one user account fails for another account. What should I do?

Last Update: 11/23/2025

If you installed Origin with All users accessible and later run Origin and installed a Python package (e.g. numpy) under Windows user account A, this package should be used for all Windows user accounts.

For those upgraded from Origin 2023b/2024/2024b to Origin 2025 or later,

If you failed to run the installed Python packages by another user account, and received error message like following:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\ProgramData\OriginLab\101b\PyPackage\Py3\originpro\__init__.py", line 9, in <module>
    from .config import *
  File "C:\ProgramData\OriginLab\101b\PyPackage\Py3\originpro\config.py", line 61, in <module>
    np.float64: po.DF_DOUBLE,
    ^^^^^^^^^^
AttributeError: module 'numpy' has no attribute 'float64'

To fix this problem:

Start Origin. Select menu Window: Command Window, and run the following Labtalk script in the Command Window:
```
pip freeze > d:\packages.txt;  //you can change the path as desired
```
Find and open the created packages.txt with any text editor (e.g. Notepad). Remove 3 lines containing originpro, jedi, and parso. Re-save the file.
Run following Labtalk script to remove all installed python packages.
```
pip uninstall *;
```
Run following Labtalk script to re-install all packages.
```
pip install -r d:\packages.txt;
```
Run following Labtalk script to update originpro.
```
pip install originpro --upgrade;
```
Once done, restart Origin and try again your python scripts. It should be working fine now.

Keywords:python, package, numpy, different account, log in account, user profile, permission