How NSP gets its updates
NSP, the software for Haltech Nexus ECUs and devices, has a built-in updater. When you press Check for Updates, it contacts Haltech's cloud servers and pulls down the newest software, device firmware and base maps once Haltech has finished testing them. That saves you hunting for files or calling support to find out what's current.
The connection is encrypted with TLS (Transport Layer Security), the same technology that protects banking and shopping websites. Encryption does two jobs here: it stops anyone tampering with the files on their way to your computer, and it proves that what you receive really came from the update server. That matters when the file is firmware for the computer running your engine.
What the updater needs
The update servers currently require TLS 1.2. Expect that to move to TLS 1.3 at some point. Encryption standards get retired as attacks against them become practical. SSL 2.0 was abandoned for that reason, and TLS 1.1 support ended in 2020. Any service that takes security seriously follows those changes, so the minimum your computer needs will keep rising over time.
Which Windows versions can connect?
Every version listed here can still do TLS 1.0, which no longer helps. What matters is the newer versions:
| Windows version | TLS 1.2 (needed now) | TLS 1.3 (likely needed later) | Build required |
|---|---|---|---|
| XP | No | No | SP3, build 2600 |
| Vista | No | No | SP2, build 6002 |
| 7 | Yes, fully updated only | No | SP1, build 7601 |
| 8 | Yes | No | Build 9200 |
| 8.1 | Yes | No | Build 9600 |
| 10 | Yes | Yes | Version 1903, build 18362 or newer |
| 11 | Yes | Yes | 21H2 or newer |
Reading the table from a tuner's point of view:
- XP and Vista can't reach the update servers at all.
- Windows 7 can, but only with Service Pack 1 and every later update installed. Even then, TLS 1.2 is as far as it will ever go, because Microsoft ended support for it. When the servers move to TLS 1.3, Windows 7 will be locked out.
- Windows 8 and 8.1 work today but have the same TLS 1.3 ceiling.
- Windows 10 (1903 or newer) and Windows 11 support everything the updater needs now and in the foreseeable future.
What it looks like when TLS is the problem
A computer that can't make a TLS 1.2 connection doesn't show an obvious error. Check for Updates simply reports "No updates available". That's why this catches people out: it looks like good news.
If you suspect this is happening, compare the NSP version you're running with the one we or Haltech list as current. If yours is older and the updater still says you're up to date, the connection is the likely cause.
Your options
- Update Windows. On Windows 7, install SP1 and all updates. Better still, move to Windows 10 or 11.
- Use a newer laptop for updates. Plenty of shops keep an old laptop in the car for logging. That's fine, as long as updates happen on a machine that can connect.
- Source the files manually. Firmware and software can be downloaded on another computer and brought across. Our downloads page is a good place to start, and we can send you what you need if you get in touch.
Keep your tuning laptop on a supported version of Windows. It's not only about the updater. Newer NSP releases, USB drivers and the rest of your toolkit all assume a current operating system.
FAQ
Does this affect my ECU while driving?
No. TLS only matters when your computer talks to the update servers. The ECU and your tune aren't affected.
Can I still tune with NSP on Windows 7?
The TLS limit only affects the updater, since going online with the ECU doesn't use the update servers. Whether a given NSP release still installs on Windows 7 is a separate question, so plan to move to Windows 10 or 11 anyway. For more on working in NSP, see table data manipulation or browse the knowledge base.
