In the long arc of computing's evolution toward integrated intelligence, NVIDIA has opened a door for developers this week — releasing preview drivers and a new CUDA toolkit that invite programmers to begin preparing for RTX Spark, a single-chip system fusing CPU, GPU, and memory into one AI-native architecture arriving this fall. The gesture is as much philosophical as technical: rather than waiting for hardware to exist before software catches up, NVIDIA is asking the developer community to meet the future halfway, porting applications to Windows on Arm64 while the machines themselves are st
NVIDIA Releases First RTX Spark Developer Drivers Ahead of Fall Launch
Better to find out now than in October when the hardware launches.
So NVIDIA is releasing drivers for hardware that doesn't ship until fall. Why not wait until the hardware is actually available?
Because developers need months to port applications. If NVIDIA waited until fall to release drivers, apps wouldn't be ready until winter or later. By releasing preview drivers now, developers can start identifying incompatibilities and rewriting code while the hardware is still in engineering.
But the preview has known issues—PyTorch workflows are causing system instability, and CUDA transfers are slow. How much can developers actually accomplish if the tools are this rough?
That's the point of a preview. It's not production-ready. Developers are expected to work around these issues or wait for fixes. The company is being transparent about what's broken.
What about developers who don't have access to a Surface RTX Dev Box? Can they still prepare?
Yes. CUDA 13.4 supports cross-compilation, so you can build Arm64 applications from an x86_64 machine without the actual hardware. You won't be able to test on real RTX Spark hardware yet, but you can get your code to compile and run on Windows Arm64 systems.
That's a significant caveat. Cross-compilation catches some problems, but not all. Performance issues, driver-specific bugs, and hardware-specific quirks won't show up until you're running on actual RTX Spark machines.
Absolutely. That's why NVIDIA's roadmap includes a final validation step once RTX Spark hardware ships. The preview is about getting ahead of the obvious porting work, not about full testing.
What happens if a developer discovers their application can't run on Arm64 at all?
That's what the preview is for. Better to find out now than in October when the hardware launches. If there are blockers, developers have time to either fix them or plan workarounds.
And if they can't fix them? If a critical dependency doesn't support Arm64?
Then they're stuck until that dependency is ported, or they find an alternative. NVIDIA can't solve that problem for them, but at least they know it now.
Il Polso
- NVIDIA's RTX Spark — a single chip combining Grace CPU, Blackwell GPU, and 128GB of unified memory — is set to land in laptops and Mini PCs this fall, and the race to have software ready is now officially on.
- Developer preview driver 616.00 targets the fanless Microsoft Surface RTX Dev Box, giving programmers their first hands-on foothold with the platform months before consumer hardware ships.
- CUDA 13.4 introduces Windows on Arm preview support, enabling both native Arm64 development and cross-compilation from existing x86_64 machines — a critical unlock for the broader developer ecosystem.
- Known issues create real friction: pageable memory transfers underperform, display blanking during installation can alarm users, and PyTorch CI/CD workflows risk triggering GPU timeouts and system instability — all under active investigation.
- NVIDIA is urging developers to audit dependencies, choose between full Arm64 porting or the hybrid Arm64EC path, and validate workflows now so applications are production-ready the moment RTX Spark hardware reaches customers.
In the long arc of computing's evolution toward integrated intelligence, NVIDIA has opened a door for developers this week — releasing preview drivers and a new CUDA toolkit that invite programmers to begin preparing for RTX Spark, a single-chip system fusing CPU, GPU, and memory into one AI-native architecture arriving this fall. The gesture is as much philosophical as technical: rather than waiting for hardware to exist before software catches up, NVIDIA is asking the developer community to meet the future halfway, porting applications to Windows on Arm64 while the machines themselves are still being finished. It is a familiar rhythm in technology — the scaffold going up before the building is complete — and the known friction in this preview only confirms that the work of preparation is genuinely underway.
NVIDIA took a meaningful step this week toward making its RTX Spark platform real, releasing developer preview driver 616.00 alongside CUDA 13.4 — tools designed to give programmers months of runway before the hardware itself arrives. RTX Spark is an ambitious single-chip design, weaving together NVIDIA's Grace CPU architecture, a Blackwell GPU, and 128 gigabytes of unified memory on one piece of silicon built expressly for AI workloads. It's headed to laptops and compact desktops this fall, and NVIDIA clearly wants developers ready when it does.
The preview driver is aimed at the Microsoft Surface RTX Dev Box, a fanless machine purpose-built for early platform work. The more consequential release, however, is CUDA 13.4, which introduces Windows on Arm preview support for the first time. Developers can now build natively on Arm64 systems or cross-compile Arm64 applications from conventional x86_64 machines — meaning the porting work can begin without waiting for RTX Spark hardware to be in hand.
NVIDIA has laid out a deliberate preparation roadmap: audit code and dependencies for Arm64 compatibility, choose between a full port or the hybrid Arm64EC approach, test on available Windows on Arm systems, and validate everything again once production hardware ships. It's a months-long process, and the company is asking developers to start now.
The preview carries expected rough edges. Pageable memory CUDA transfers are underperforming — page-locked memory is the current workaround. Display output goes dark for roughly two minutes during driver installation, which looks alarming but is normal. More seriously, PyTorch CI/CD workflows can trigger GPU timeouts and system instability, an issue NVIDIA says is under active investigation. Nsight Copilot remains unavailable on Windows Arm64 for now.
None of these are fatal to the preview's purpose. NVIDIA has already shown RTX Spark systems publicly at Computex 2026, and early impressions of AI and creative workload performance have been encouraging. Leaked benchmarks from engineering samples are circulating, but NVIDIA is cautioning against drawing conclusions from them — retail systems will tell a different story. The real measure comes this fall, when production hardware ships and the months of preparation either pay off or reveal what still needs work.
NVIDIA is moving its RTX Spark platform closer to reality. The company released the first developer preview drivers this week—version 616.00—giving programmers their first real chance to prepare applications for hardware that won't ship until fall. The RTX Spark itself is a single-chip system combining NVIDIA's Grace CPU architecture, a Blackwell GPU, and 128 gigabytes of memory, all wired together on one piece of silicon designed specifically for AI workloads. It's coming to laptops and compact desktop machines, and NVIDIA is now making sure developers don't get caught flat-footed when those machines arrive.
The preview driver targets the Microsoft Surface RTX Dev Box, a fanless machine built explicitly for developers who want to start working with the platform before it reaches consumers. Alongside the driver release, CUDA 13.4—NVIDIA's toolkit for GPU programming—now includes what the company calls "Windows on Arm" preview support. This is the piece that matters most for the developer community. The toolkit enables two critical workflows: native development directly on Windows Arm64 systems, and cross-compilation, which lets programmers build Arm64 applications from existing x86_64 machines without needing the actual hardware yet.
The timing is deliberate. NVIDIA is essentially asking developers to start now. Review your code and your dependencies for Arm64 compatibility. Decide whether you're porting your application wholesale to Arm64 or using a hybrid approach called Arm64EC. Build and test on Windows on Arm systems if you can access them. Validate that your NVIDIA and CUDA software paths work as expected. Test installation, updates, functionality, and performance. Then, when RTX Spark hardware becomes available in the fall, validate everything one final time on the actual device. It's a methodical roadmap, and it assumes developers will take months to prepare.
But the preview is not without friction. NVIDIA documented several known issues that developers need to understand. CUDA transfers using pageable memory—the default kind—are delivering lower performance than expected. The workaround is to use page-locked memory instead, allocated through specific CUDA functions. During driver installation, the display may go blank for roughly two minutes; the company warns users not to restart or power off the system during this window, even though it looks like something has gone wrong. More concerning is a possible system instability when running PyTorch CI/CD workflows, which can trigger GPU timeouts and cause unexpected restarts or unresponsiveness. NVIDIA says this is under investigation. Nsight Copilot, a development tool, is also disabled in this preview and not available on Windows Arm64 yet.
These are the kinds of rough edges you expect in a developer preview. They're not showstoppers—they're signals that the platform is still being refined. NVIDIA has already shown RTX Spark systems at Computex 2026, and the company reported seeing impressive performance in AI applications, content creation tools, and games. This is NVIDIA's first serious push into the laptop and AI PC market with its own integrated system, and early impressions suggest the hardware is capable. But benchmarks from engineering samples have leaked online, and NVIDIA is explicitly cautioning against reading too much into them. Those numbers don't reflect what retail systems will actually deliver. The real test comes in the fall, when RTX Spark machines ship to customers and developers can measure performance on production hardware. Until then, the work is preparation—getting code ready, dependencies sorted, and workflows validated so that when the hardware arrives, applications are waiting.
Citazioni salienti
Developers can start porting their applications to Windows on Arm on an existing development system and identify incompatible dependencies before RTX Spark hardware arrives— NVIDIA