# Windows 10 ARM

**URL:** <https://forums.developer.nvidia.com/t/windows-10-arm/69050>\
**Category:** Jetson TX2\
**Created:** [January 3, 2019, 8:18pm UTC](https://forums.developer.nvidia.com/t/windows-10-arm/69050 "2019-01-03T20:18:28Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![joey.spiker](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/joey.spiker/32/17011_2.png) [@joey.spiker](https://forums.developer.nvidia.com/u/joey.spiker)\
**Post date:** [January 3, 2019, 8:18pm UTC](https://forums.developer.nvidia.com/t/windows-10-arm/69050/1 "2019-01-03T20:18:28Z")

</div>

> **[Windows on Arm documentation](https://learn.microsoft.com/en-us/windows/arm/)**
>
> Learn more about running Windows on PCs powered by Arm processors. Find guidance on how to build Windows apps for Arm64 devices or iteratively update your existing Windows app to take advantage of Arm64 native capabilities.

Please dear god, I’ve been trying to make this work for weeks. Someone on here with more embedded, uboot, knowledge MUST know how to make this happen. If not lets work as a community to make it a reality.

---

<div class="post-metadata">

**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\
**Post date:** [January 4, 2019, 1:47pm UTC](https://forums.developer.nvidia.com/t/windows-10-arm/69050/2 "2019-01-04T13:47:16Z")

</div>

You should know that the GPU driver itself is for an integrated GPU (iGPU), not PCIe (dGPU). This means that none of the published desktop PC drivers will work, even if the driver is arm64 (and they are not). Compounding the problem is that the driver is a binary format driver in Linux ELF format intended to be embedded in a particular X11 server ABI. So if for some reason you get this booting Windows, you will have no access to CUDA and the GPU. Unless you are interested in giving up CUDA and GPU hardware acceleration you’ll end up disappointed.

---

<div class="post-metadata">

**Author:** ![joey.spiker](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/joey.spiker/32/17011_2.png) [@joey.spiker](https://forums.developer.nvidia.com/u/joey.spiker)\
**Post date:** [January 4, 2019, 5:14pm UTC](https://forums.developer.nvidia.com/t/windows-10-arm/69050/3 "2019-01-04T17:14:44Z")

</div>

They have details on recompiling drivers for arm – do you happen to know where I could find this Linux ELF binary format driver’s source code?

---

<div class="post-metadata">

**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\
**Post date:** [January 4, 2019, 6:49pm UTC](https://forums.developer.nvidia.com/t/windows-10-arm/69050/4 "2019-01-04T18:49:49Z")

</div>

If you download the R28.2.1 driver package, the “apply\_binaries.sh” script unpacks some of the NVIDIA-specific driver files onto the sample rootfs. If you simply run “sudo ./apply\_binaries.sh” from the L4T directory without first unpacking the sample rootfs you will get all of those files, and just those files. It would be one of the ones in the “rootfs/usr/lib/aarch64/” directory.

Do beware this is in binary only format. NVIDIA does not publish the source code of its GPU drivers, and this driver is specifically bound the iGPU and is a Linux file format which is unknown to Windows. There is no chance of getting source code (perhaps if you were a large OEM under non-disclosure you could).

---

<div class="post-metadata">

**Author:** ![joey.spiker](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/joey.spiker/32/17011_2.png) [@joey.spiker](https://forums.developer.nvidia.com/u/joey.spiker)\
**Post date:** [January 4, 2019, 6:53pm UTC](https://forums.developer.nvidia.com/t/windows-10-arm/69050/5 "2019-01-04T18:53:47Z")

</div>

Appreciate it, I’ll attempt to decompile it, i’m sure its optimized, etc… but i’ll give it hell and see what happens.

---

<div class="post-metadata">

**Author:** ![linuxdev](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/linuxdev/32/10243_2.png) [@linuxdev](https://forums.developer.nvidia.com/u/linuxdev)\
**Post date:** [January 4, 2019, 7:13pm UTC](https://forums.developer.nvidia.com/t/windows-10-arm/69050/6 "2019-01-04T19:13:47Z")

</div>

Well…that’s probably against the EULA. Even so, realize that the driver binds using the X11 protocol interface…it is essentially a plugin to the X server. Windows doesn’t use X, so even then there is some serious work ahead.

---

<div class="post-metadata">

**Author:** ![joel.reindel](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/joel.reindel/32/11737_2.png) [@joel.reindel](https://forums.developer.nvidia.com/u/joel.reindel)\
**Post date:** [April 10, 2019, 11:52pm UTC](https://forums.developer.nvidia.com/t/windows-10-arm/69050/7 "2019-04-10T23:52:36Z")

</div>

Hey Joey,

While I don’t personally have much on an interest in getting Windows 10 running on the Jetson TX2 I am interested in what ever came of this.

Did you give up on this, or did you get somewhere?
