PPK could not be recognized

RE: PPK could not be recognized

Kyle Wang — Thu, 11 Sep 2025 08:09:16 GMT

16:04:02.031

Initialising the bundled nrfutil device

16:04:21.543

Successfully installed nrfutil device version: 2.10.2

16:04:24.239

Using the bundled core version for nrfutil device: 8.0.0

16:04:25.045

Using nrfutil-device version: 2.10.2

16:04:25.045

Using nrf-device-lib version: 0.17.71

16:04:25.045

Using nrf-probe version: 0.38.0

16:04:25.045

Using JLink version: JLink_V8.18

16:04:26.296

Getting serial port options from the persistent store for C9FCEFCA6DB1.pc-nrfconnect-ppk

16:04:26.297

Device connected with the serial number C9FCEFCA6DB1

16:05:08.299

Selecting device with the serial number C9FCEFCA6DB1

16:05:11.135

Selected device with the serial number C9FCEFCA6DB1

16:05:13.489

Connected to the device with the serial number C9FCEFCA6DB1 and family: Unknown

16:05:13.773

PPK started

16:05:13.773

PPK opened

16:05:20.009

DUT ON

Today I install PPK2 in my old win10 PC and update it in old PC, then install PPK2 in my new PC, it works well now, happy to see it.

RE: PPK could not be recognized

Benjamin — Tue, 09 Sep 2025 10:22:17 GMT

I'm glad to hear that!

RE: PPK could not be recognized

Tiny.zeng — Tue, 09 Sep 2025 03:35:43 GMT

sorry, actuallly the error log does not affect the PPK recognition, now the ppk can be recognized , thanks！！！

RE: PPK could not be recognized

Tiny.zeng — Tue, 09 Sep 2025 03:30:34 GMT

yes, i have downloaded the file from https://files.nordicsemi.com/artifactory/swtools/external/nrfutil/packages/nrfutil/nrfutil-x86_64-pc-windows-msvc-8.0.0.tar.gz directly in the web browser?, but the problem still exist,

2025-09-09T03:24:13.094Z INFO Initialising nrfutil module: device
2025-09-09T03:24:13.129Z DEBUG Application data folder: C:\Users\yan.ceng\AppData\Roaming\nrfconnect\pc-nrfconnect-ppk
2025-09-09T03:24:13.188Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-09T03:24:13.188Z DEBUG App pc-nrfconnect-ppk v4.0.0 (official)
2025-09-09T03:24:13.188Z DEBUG App path: C:\Users\yan.ceng\.nrfconnect-apps\node_modules\pc-nrfconnect-ppk
2025-09-09T03:24:13.188Z DEBUG nRFConnect 5.0.0, required by the app is (>=4.4.1)
2025-09-09T03:24:13.188Z DEBUG nRFConnect path: C:\Users\yan.ceng\AppData\Local\Programs\nrfconnect\resources\app.asar
2025-09-09T03:24:13.188Z DEBUG HomeDir: C:\Users\yan.ceng
2025-09-09T03:24:13.188Z DEBUG TmpDir: C:\Users\yan.ceng\AppData\Local\Temp
2025-09-09T03:24:14.693Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-09T03:25:42.020Z ERROR Error: Failed with exit code 1.
Could not update package registry

Caused by:
0: failed to fetch `github.com/.../nrfutil-package-index`
1: failed to send request: 操作超时
; class=Os (2).
2025-09-09T03:25:42.020Z ERROR Error while updated nrfutil core
2025-09-09T03:25:42.042Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-09T03:25:42.042Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-09T03:25:42.052Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-09T03:25:42.177Z INFO Using nrfutil-device core version: 7.7.1
2025-09-09T03:25:43.247Z INFO Device Connected SN:000601022398
2025-09-09T03:25:43.248Z INFO Getting serialport options from persistent store 000601022398.pc-nrfconnect-ppk
2025-09-09T03:25:43.249Z DEBUG Sending event "ppk: device connected"
2025-09-09T03:25:43.249Z INFO Device Connected SN:EB3C6961A90F
2025-09-09T03:25:43.250Z INFO Getting serialport options from persistent store EB3C6961A90F.pc-nrfconnect-ppk
2025-09-09T03:25:43.251Z DEBUG Sending event "ppk: device connected"
2025-09-09T03:25:43.251Z INFO Device Connected SN:null
2025-09-09T03:25:43.252Z DEBUG Sending event "ppk: device connected"
2025-09-09T03:25:43.529Z INFO Using nrfutil-device version: 2.1.1
2025-09-09T03:25:43.529Z INFO Using nrf-device-lib version: 0.17.5
2025-09-09T03:25:43.529Z INFO Using nrfjprog DLL version: 10.24.0
2025-09-09T03:25:43.529Z INFO Using JLink version: JLink_V8.18
2025-09-09T03:25:43.529Z WARN Installed JLink version does not match the expected version (JLink_V7.94e)

RE: PPK could not be recognized

Benjamin — Mon, 08 Sep 2025 07:24:31 GMT

Are your computer able to download the file from https://files.nordicsemi.com/artifactory/swtools/external/nrfutil/packages/nrfutil/nrfutil-x86_64-pc-windows-msvc-8.0.0.tar.gz directly in the web browser?

RE: PPK could not be recognized

Kyle Wang — Mon, 08 Sep 2025 06:37:54 GMT

I manually installed nrfutil and update to latest version, but PPK2 still could not be recognized.

RE: PPK could not be recognized

Tiny.zeng — Mon, 08 Sep 2025 06:34:01 GMT

and I saw the PPKdevice show DFU Trigger in the device manager .

RE: PPK could not be recognized

Tiny.zeng — Mon, 08 Sep 2025 06:20:24 GMT

hi，I am facing a similar problem. and I can confirm my network is operational, The log is as follows：

2025-09-08T02:15:56.211Z INFO Initialising nrfutil module: device
2025-09-08T02:15:56.253Z DEBUG Application data folder: C:\Users\yan.ceng\AppData\Roaming\nrfconnect\pc-nrfconnect-ppk
2025-09-08T02:15:56.312Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-08T02:15:56.313Z DEBUG App pc-nrfconnect-ppk v4.0.0 (official)
2025-09-08T02:15:56.313Z DEBUG App path: C:\Users\yan.ceng\.nrfconnect-apps\node_modules\pc-nrfconnect-ppk
2025-09-08T02:15:56.313Z DEBUG nRFConnect 5.0.0, required by the app is (>=4.4.1)
2025-09-08T02:15:56.313Z DEBUG nRFConnect path: C:\Users\yan.ceng\AppData\Local\Programs\nrfconnect\resources\app.asar
2025-09-08T02:15:56.313Z DEBUG HomeDir: C:\Users\yan.ceng
2025-09-08T02:15:56.313Z DEBUG TmpDir: C:\Users\yan.ceng\AppData\Local\Temp
2025-09-08T02:15:57.659Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-08T02:17:41.374Z ERROR Error: Failed with exit code 1.
Failed to install nrfutil

Caused by:
0: Could not download package
1: failed to download from `developer.nordicsemi.com/.../nrfutil-x86_64-pc-windows-msvc-7.11.1.tar.gz`
2: failed to get 200 response from `developer.nordicsemi.com/.../nrfutil-x86_64-pc-windows-msvc-7.11.1.tar.gz`, got 404.
2025-09-08T02:17:41.374Z ERROR Error while updated nrfutil core
2025-09-08T02:17:41.388Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-08T02:17:41.388Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-08T02:17:41.395Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-08T02:18:03.422Z ERROR Error: Failed with exit code 1.
Failed to bootstrap core functionality before executing command.

Failed to download bootstrap tarball using config:

files.nordicsemi.com/.../
bootstrap.json

See the details below for further information on the error.

Caused by:
0: HTTP request to "">files.nordicsemi.com/.../nrfutil-x86_64-pc-windows-msvc-8.0.0.tar.gz" failed
1: error sending request for url (files.nordicsemi.com/.../nrfutil-x86_64-pc-windows-msvc-8.0.0.tar.gz)
2: client error (Connect)
3: tcp connect error: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 (os error 10060)
4: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 (os error 10060).
2025-09-08T02:18:03.443Z ERROR Error: Failed to bootstrap core functionality before executing command.

Failed to download bootstrap tarball using config:

files.nordicsemi.com/.../
bootstrap.json

See the details below for further information on the error.

Caused by:
0: HTTP request to "">files.nordicsemi.com/.../nrfutil-x86_64-pc-windows-msvc-8.0.0.tar.gz" failed
1: error sending request for url (files.nordicsemi.com/.../nrfutil-x86_64-pc-windows-msvc-8.0.0.tar.gz)
2: client error (Connect)
3: tcp connect error:
2025-09-08T02:18:03.443Z ERROR 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 (os error 10060)
4: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 (os error 10060)

2025-09-08T02:18:03.447Z ERROR Error: Failed with exit code 1.
2025-09-08T02:18:03.493Z ERROR Error: Failed with exit code 1.
Failed to bootstrap core functionality before executing command.

Failed to download bootstrap tarball using config:

files.nordicsemi.com/.../
bootstrap.json

See the details below for further information on the error.

RE: PPK could not be recognized

Kyle Wang — Mon, 08 Sep 2025 00:02:12 GMT

yes，100% updated.

RE: PPK could not be recognized

Benjamin — Fri, 05 Sep 2025 09:05:21 GMT

Thanks for the log. Have you installed nRF Util on your computer?

RE: PPK could not be recognized

Kyle Wang — Fri, 05 Sep 2025 07:51:20 GMT

2025-09-05T07:48:45.014Z INFO Initialising the bundled nrfutil device
2025-09-05T07:48:45.018Z DEBUG Application data folder: C:\Users\E879623\AppData\Roaming\nrfconnect\pc-nrfconnect-ppk
2025-09-05T07:48:45.697Z DEBUG App pc-nrfconnect-ppk v4.3.1 (official)
2025-09-05T07:48:45.697Z DEBUG App path: C:\Users\E879623\.nrfconnect-apps\node_modules\pc-nrfconnect-ppk
2025-09-05T07:48:45.697Z DEBUG nRFConnect 5.2.0, required by the app is (>=5.2.0)
2025-09-05T07:48:45.697Z DEBUG nRFConnect path: C:\Users\E879623\AppData\Local\Programs\nrfconnect\resources\app.asar
2025-09-05T07:48:45.697Z DEBUG HomeDir: C:\Users\EXXXXXX
2025-09-05T07:48:45.697Z DEBUG TmpDir: C:\Users\EXXXXXX\AppData\Local\Temp
2025-09-05T07:48:45.709Z DEBUG Sending event "ppk: running nrfutil device"
2025-09-05T07:48:52.482Z ERROR Error: Failed with exit code 1.
Failed to bootstrap core functionality before executing command.

Failed to extract bootstrap tarball

C:\Users\EXXXXXX\AppData\Roaming\nrfconnect\nrfutil-
sandboxes\8.0.0\device\2.10.2\bootstrap\nrfutil-core-install-Bikdru\nrfutil-
x86_64-pc-windows-msvc-8.0.0.tar.gz

downloaded from

files.nordicsemi.com/.../
nrfutil/nrfutil-x86_64-pc-windows-msvc-8.0.0.tar.gz

See the details below for further information on the error.

Caused by:
invalid gzip header

RE: PPK could not be recognized

Benjamin — Fri, 05 Sep 2025 07:45:42 GMT

Could you share the log file?

RE: PPK could not be recognized

Kyle Wang — Fri, 05 Sep 2025 00:12:34 GMT

My old PC is Win10, PPK2 works well, my new PC installed Win11 version 23H2， PPK2 could not works, always shows "The system cannot find the path specified. (os error 3)"

RE: PPK could not be recognized

Benjamin — Thu, 04 Sep 2025 14:09:43 GMT

Hi,
Have you tried on a different computer?

Best regards,
Benjamin