CPUID, the French software house behind two of the most-downloaded hardware utilities on Windows, pushed out new ARM64 builds of CPU-Z and HWMonitor on October 6, 2026. The update, tagged version 1.06 for both tools, exists for one reason: NVIDIA’s RTX Spark platform is about to ship, and right now almost nothing on the market can read what’s actually inside it. For the overclockers, system builders, and reviewers who treat CPU-Z as a baseline sanity check before any benchmark run, that gap just closed a day or two ahead of schedule.
According to CPUID’s own news post, NVIDIA is about to release its RTX Spark superchip equipped with a 20-core MediaTek ARM SoC (codenamed “Grace”) and a 6,144-core RTX GPU codenamed “Backwell,” running Windows 11 on ARM64. That single sentence explains why a monitoring-tool update became a story in its own right: RTX Spark isn’t a conventional x86 desktop chip, and conventional x86 tooling doesn’t automatically know how to talk to it.
What Changed in CPU-Z and HWMonitor 1.06
CPUID split the update across its two flagship utilities, and each one solves a different half of the problem. CPU-Z 1.06 for ARM64 improves the detection of the new chip, while HWMonitor 1.06 adds a complete telemetry for the CPU and the GPU, as described in the company’s own changelog. In plain terms, CPU-Z now recognizes the RTX Spark silicon well enough to report its core layout and clocks correctly instead of guessing or falling back to a generic ARM identifier, and HWMonitor can now pull live temperature, voltage, and clock-speed readings from both the SoC and the integrated GPU.
That distinction matters more than it sounds. Detection and monitoring are two separate engineering problems. A tool can “see” a chip’s name and model number without being able to read its sensors, and it can poll sensors without correctly labeling what generated the reading. CPUID’s release notes treat the two as linked but distinct line items, which lines up with how the company has historically rolled out support for new platforms: identification first, then telemetry, shipped together when the timing allows it.
Both builds appeared as direct downloads on CPUID’s site the same day, listed as “Version 1.06 for windows ARM64 – Improved support of NVIDIA RTX Spark” for CPU-Z and “Version 1.06 for windows ARM64 – NVIDIA RTX Spark telemetry (System, CPU and GPU)” for HWMonitor. Readers tracking the broader launch timeline can see how this fits into NVIDIA’s own rollout in shattered.io’s earlier report on RTX Spark shipping to six PC makers.
What Is NVIDIA RTX Spark, Exactly?
RTX Spark is NVIDIA’s superchip platform pairing a 20-core MediaTek ARM SoC with a 6,144-core RTX GPU, running the ARM64 build of Windows 11 rather than the x86 version most PC buyers know. CPUID’s news post is explicit that the GPU carries the internal codename “Backwell” and the SoC carries the codename “Grace,” though it’s worth flagging that CPUID’s own description does not establish those codenames as the final, official marketing terms NVIDIA will use at retail. Reports have pointed to October 2026 as the expected window for the first RTX Spark machines to reach buyers, which is exactly why a monitoring-tool update landed this week instead of next month.
What isn’t confirmed yet is just as important as what is. The exact consumer launch date, final retail pricing, and specific product configurations for RTX Spark machines haven’t been clearly nailed down in public reporting as of this week. Readers should treat any specific price point they see elsewhere with caution until an OEM or NVIDIA itself confirms it. For context on how previous NVIDIA “Spark” branding played out, shattered.io covered the related DGX Spark price split between its 64GB and 128GB configurations, a separate but adjacent product line that shares the Spark name.
Why a Monitoring Tool Update Is Actually News
It’s easy to dismiss a point release of a free diagnostic utility as a footnote. In practice, CPU-Z and HWMonitor function as unofficial industry infrastructure. Reviewers screenshot CPU-Z’s validation tab in nearly every CPU review published since the early 2000s. Builders run HWMonitor in the background during stress tests to catch thermal throttling before it shows up as a benchmark dip. System integrators use both tools to confirm that a machine shipped with the silicon a customer actually paid for.
None of that works on a chip the software doesn’t recognize. Before this update, anyone running early RTX Spark hardware with CPU-Z or HWMonitor would likely have seen incomplete or generic readings, if the tools ran at all, because ARM64 builds of Windows software require separate compilation and testing from their x86 counterparts. That’s a real engineering cost for CPUID to carry for a platform that, as of this week, has not yet sold a single unit at retail.
The timing also says something about how NVIDIA is managing its launch partners. Software vendors don’t usually get early silicon access for free, and TweakTown’s coverage of the update notes that it landed “ahead of release,” which strongly implies NVIDIA, MediaTek, or an OEM partner shared early access rather than CPUID reverse-engineering a retail unit after the fact. Shattered.io’s prior coverage of AMD’s claimed 500,000 agentic PCs shipped before RTX Spark even launched gives a sense of how competitive the pre-launch positioning around this category has already become.
The Developer Behind the Build
Franck Delattre, identified in reporting as the author of CPU-Z and HWMonitor, reportedly used remote access to an ASUS P16 system while developing the RTX Spark support. That detail, drawn from independent reporting rather than CPUID’s own announcement, points to a one-person or small-team operation building platform support without a retail unit physically on a desk in France. Remote development against pre-release hardware is common in the Windows tooling world, but it also means the update ships with less real-world validation than CPUID would normally prefer, which is one reason the company frames this release as an “improvement” to detection rather than a claim of complete support.
CPU-Z and HWMonitor 1.06: The Technical Snapshot
| Item | Detail |
|---|---|
| Developer | CPUID |
| CPU-Z ARM64 version | 1.06 |
| HWMonitor ARM64 version | 1.06 |
| CPU-Z change | Improved detection of the RTX Spark platform |
| HWMonitor change | Full telemetry for CPU and GPU sensors |
| Target platform | NVIDIA RTX Spark (Windows 11 ARM64) |
| Availability | Direct download from CPUID, October 6, 2026 |
| Development note | Built with reported remote access to an ASUS P16 system |
RTX Spark Specs: What’s Confirmed vs. Still Open
| Spec | Status |
|---|---|
| SoC core count | 20-core MediaTek ARM chip, per CPUID |
| GPU core count | 6,144-core RTX GPU, per CPUID |
| SoC codename | “Grace,” per CPUID (not confirmed as final branding) |
| GPU codename | “Backwell,” per CPUID (not confirmed as final branding) |
| Operating system | Windows 11 on ARM64 |
| Expected launch window | October 2026, per multiple reports |
| Confirmed retail price | Not established in available reporting |
| Confirmed OEM lineup | Not established in available reporting |
Market Impact: Why Tooling Readiness Matters for a Launch
NVIDIA’s push into ARM64 Windows hardware runs into a problem that x86 launches rarely face: the software ecosystem has to catch up chip by chip. On a new Intel or AMD desktop CPU, most diagnostic and benchmarking tools already understand the x86 instruction set and need only minor updates to add a new model ID. ARM64 is a different architecture entirely. Every monitoring tool, every benchmark suite, and every driver utility has to be separately compiled, tested, and in some cases substantially rewritten to run natively rather than through emulation.
That makes early tooling support a genuine signal of launch health. A platform that reviewers can’t fully measure on day one tends to generate softer, less confident coverage, because benchmark numbers without reliable thermal and clock-speed context are harder to trust. CPUID shipping working ARM64 builds before RTX Spark hardware reaches the public buys NVIDIA and its partners cleaner, more credible first-look coverage when review units start landing. It’s the same dynamic that played out around the broader agentic-PC category, which shattered.io covered in detail in its report on AMD’s Gorgon Halo benchmarks aimed squarely at RTX Spark.
There’s a second, quieter market effect here too. CPUID is a small, independent company, and platform-specific updates like this one are effectively free marketing validation for NVIDIA. When an established, trusted diagnostic tool adds explicit support for a new chip ahead of its retail debut, it signals to the enthusiast and reviewer community that the platform is real, imminent, and worth tracking, rather than vaporware. That kind of organic third-party confirmation is difficult for a hardware vendor to manufacture through its own marketing.
Competitive Landscape: Who Else Needs to Catch Up
CPU-Z and HWMonitor are far from the only tools builders lean on, and it’s an open question whether rivals such as AIDA64 or HWiNFO already have matching ARM64 builds ready for RTX Spark, or whether they’re still working on it. Public reporting reviewed for this story doesn’t confirm either way, and vendors in this space don’t always announce platform support with the same visibility CPUID gave this update. What is clear is that CPUID moved early enough to have a working build in hand before retail units exist, which puts pressure on competing utilities to match that timeline or risk looking behind on a platform that reviewers will be testing within weeks.
The broader competitive backdrop also includes the chipmakers themselves. Intel and AMD have spent much of 2026 defending their share of the AI-PC and agentic-PC categories against ARM-based entrants, and NVIDIA’s RTX Spark sits at the center of that fight because it combines a non-x86 CPU with a genuinely high-end GPU rather than the modest integrated graphics typical of earlier ARM Windows laptops. Shattered.io’s coverage of Surface Laptop Ultra’s RTX Spark-class specs, including a 6,144-core GPU figure that matches CPUID’s own number, shows how consistently that core count is showing up across independent reporting, which adds confidence to the figure even without a single unified NVIDIA press release confirming it outright.
Historical Context: CPU-Z’s Long Track Record With New Platforms
CPUID has been through this cycle before. CPU-Z has added support for new CPU architectures and socket types for roughly two decades, and HWMonitor followed a similar pattern as sensor hardware diversified across motherboard vendors. The company’s current validation framework, CPU-Z Validator V3, rolled out earlier in 2026 as a redesign aimed at overclockers and power users, according to CPUID’s own news page, showing the company has been actively modernizing its core tools well before RTX Spark became a factor.
What makes the RTX Spark case notable in that history isn’t the update itself, it’s the architecture shift underneath it. Most of CPU-Z’s platform-support work over the years has stayed within x86, covering new Intel and AMD generations as they launched. A full ARM64 build, tracking a combined CPU-and-GPU superchip rather than a conventional discrete-socket design, is a meaningfully different kind of engineering problem than CPUID has solved repeatedly in the past. Readers interested in how Windows-on-ARM hardware has been narrowing the gap with x86 can see related ground covered in shattered.io’s report on RTX 5090 thermal issues on the x86 side, a reminder that even mature, well-understood platforms still produce monitoring and thermal surprises that software has to keep pace with.
What the Verified Record Says, in the Words of the People Who Shipped It
CPUID’s own announcement lays out the reasoning plainly: “NVIDIA is about to release its RTX Spark superchip equipped with a 20-core MediaTek ARM Soc (codenamed ‘Grace’) and a 6144-core RTX GPU codenamed ‘Backwell’, running Windows 11 on ARM64,” the company wrote on its official news page. CPUID followed that with a direct explanation of the engineering split between the two tools: “CPU-Z 1.06 for ARM64 improves the detection of the new chip, while HWMonitor 1.06 adds a complete telemetry for the CPU and the GPU, as you can see in the screenshots below,” per the same CPUID announcement.
The company’s own product pages echo that split in changelog form. CPU-Z’s release notes read, “Version 1.06 for windows ARM64 – Improved support of NVIDIA RTX Spark,” according to CPUID’s CPU-Z ARM64 download page. HWMonitor’s changelog is just as direct: “Version 1.06 for windows ARM64 – NVIDIA RTX Spark telemetry (System, CPU and GPU),” per CPUID’s HWMonitor ARM64 download page.
Outside coverage framed the release in similarly concrete terms. “CPU-Z and HWMonitor have received a new update that adds monitoring support for NVIDIA’s upcoming RTX Spark SoCs that are debuting tomorrow,” TweakTown reported in its coverage of the release, a framing that places the retail debut just one day behind the software update itself.
Predictions: Where This Goes Next
- Expect other diagnostic and benchmarking vendors, including AIDA64 and HWiNFO, to announce or quietly ship their own ARM64 RTX Spark builds within the next few weeks as retail hardware starts reaching reviewers.
- CPUID will likely follow 1.06 with incremental patches (1.07 and beyond) once real retail RTX Spark units generate bug reports that remote pre-release access couldn’t catch.
- Watch for NVIDIA or an OEM partner to confirm or walk back the “Grace” and “Backwell” codenames once official marketing materials for RTX Spark go live, since CPUID’s phrasing leaves that branding unconfirmed.
- If RTX Spark’s October 2026 launch window holds, the first independent reviews using these updated tools should appear within days of retail availability, giving the public its first fully instrumented look at the platform’s real clocks and thermals rather than NVIDIA’s own marketing figures.
- Expect continued competitive messaging from AMD and Intel around their own ARM and agentic-PC offerings as RTX Spark’s launch window closes in, following the pattern already visible in their pre-launch benchmark claims.
What Builders and Reviewers Should Do Right Now
Anyone planning to review, benchmark, or simply validate an RTX Spark system at launch should update to CPU-Z ARM64 1.06 and HWMonitor ARM64 1.06 before touching the hardware. Running an older build risks either a failed launch on the ARM64 chip or, worse, silently incomplete sensor data that could misrepresent thermal headroom during a review. Because the update ships as a direct download rather than through an auto-updater for most users, it’s worth manually checking CPUID’s site rather than assuming an existing install will refresh itself.
It’s also worth treating any RTX Spark readings from this initial 1.06 release with a reasonable amount of caution. Software built against remote, pre-release hardware access, as this update reportedly was, tends to improve quickly once wider public testing surfaces edge cases the developer couldn’t see in advance. Cross-checking HWMonitor’s numbers against a second tool, once one becomes available, remains good practice until the ARM64 tooling ecosystem around RTX Spark matures.
Frequently Asked Questions
What did CPUID actually update on October 6, 2026?
CPUID released CPU-Z ARM64 version 1.06 and HWMonitor ARM64 version 1.06. CPU-Z’s update improves detection of the NVIDIA RTX Spark platform, while HWMonitor’s update adds full CPU and GPU telemetry for the same chip.
What is NVIDIA RTX Spark?
RTX Spark is a superchip platform combining a 20-core MediaTek ARM SoC, described by CPUID with the codename “Grace,” and a 6,144-core RTX GPU, described with the codename “Backwell,” running Windows 11 on ARM64. Reports point to an October 2026 launch window, though exact pricing and final product lineups haven’t been clearly confirmed yet.
Are “Grace” and “Backwell” the official names for RTX Spark’s chips?
CPUID’s announcement uses those codenames, but that single source doesn’t establish them as NVIDIA’s final, official product branding. Treat them as working codenames until NVIDIA or an OEM partner confirms otherwise.
Where can I download CPU-Z and HWMonitor ARM64 1.06?
Both builds are available as direct downloads from CPUID’s official site, listed separately on the CPU-Z ARM64 and HWMonitor ARM64 product pages.
Do I need these updates if I’m not buying an RTX Spark machine?
No. The 1.06 changes are specific to RTX Spark detection and telemetry. Users on standard x86 systems don’t need this update for their existing hardware.
Who developed the RTX Spark support in CPU-Z and HWMonitor?
Franck Delattre, identified in reporting as the author of both tools, reportedly built the support using remote access to an ASUS P16 system ahead of RTX Spark’s public launch.
Will other monitoring tools like AIDA64 or HWiNFO add RTX Spark support too?
That’s likely but not yet confirmed in public reporting. ARM64 support generally requires separate development work from each vendor, so timing can vary tool by tool.
When will retail RTX Spark systems actually ship?
Multiple reports point to October 2026 as the expected window, with some coverage suggesting the retail debut followed the CPU-Z and HWMonitor update by about a day. An exact, universally confirmed date for all configurations hasn’t been established.
