topic Secure Provision Tool 25.12 failed to run after installation in MCUXpresso Secure Provisioning Tool

Secure Provision Tool 25.12 failed to run after installation

nxf51434 — Fri, 13 Mar 2026 06:47:17 GMT

Following is the log :Traceback (most recent call last):
File "pyi_rth_pkgres.py", line 177, in <module>
File "pyi_rth_pkgres.py", line 44, in _pyi_rthook
File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
File "pyimod02_importers.py", line 457, in exec_module
File "pkg_resources\__init__.py", line 90, in <module>
File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
File "<frozen importlib._bootstrap>", line 1331, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 935, in _load_unlocked
File "pyimod02_importers.py", line 457, in exec_module
File "setuptools\_vendor\jaraco\text\__init__.py", line 231, in <module>
File "pathlib.py", line 1028, in read_text
File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xee in position 6: invalid continuation byte
[PYI-30324:ERROR] Failed to execute script 'pyi_rth_pkgres' due to unhandled exception!

What caused it?

Re: Secure Provision Tool 25.12 failed to run after installation

marek-trmac — Fri, 13 Mar 2026 07:39:40 GMT

Hi,

can you check if the following file was installed and can you attach the file to the chat?

"c:\nxp\SEC_Provi_25.12\bin\_internal\setuptools\_vendor\jaraco\text\Lorem ipsum.txt"

Based on the stack trace it seems the file is broken.

Can you confirm you are running the tool on Windows 11?

Can you provide info about language and region configuration of your OS (Start > Settings > Time & language > Language & region)?

Re: Secure Provision Tool 25.12 failed to run after installation

nxf51434 — Fri, 13 Mar 2026 07:57:47 GMT

Based on your indication, the issue caused by the encryption software installed on the local computer. After adding the application to the whitelist, the problem was resolved.