Get the tools needed to customize Windows IoT Core
Here's the hardware you'll need to create OEM images using the Windows 10 IoT Core (IoT Core) ADK Add-Ons:
PCs and devices
Technician PC: This is the PC you will be building your images on. A dedicated PC is recommended for this. This PC should have at least 15 GB of free space for installing the software and for modifying IoT Core images.
We recommend either Windows 10 or Windows 8.1 with the latest updates. The minimum requirement is Windows 7 SP1, though this may require additional tools or workarounds for tasks such as mounting .ISO images.
IoT device: A test device or board that represents all of the devices in a single model line.
For our labs, you'll need a Raspberry Pi 3. For a list of support devices, see SoCs and Custom Boards.
An HDMI cable, and a monitor or TV with a dedicated HDMI input. We'll use this to verify that the image is loaded and that our sample apps are running.
- A MicroSD card. Note that this is dependent on the device you are using. Some devices require a microSD card while others have onboard storage. For these labs, we ill use a microSD card. If your technician PC doesn't include a microSD slot, you may also need an adapter.Learn more about existing supported storage options.
Here's the software you'll need to create OEM images using the Windows 10 IoT Core (IoT Core) ADK Add-Ons:
Install the following tools on your technician PC
- Windows Assessment and Deployment Kit (Windows ADK) for Windows 10, version 1089 - Including at least the Deployment Tools and Imaging and Configuration Designer (ICD) features, shown below. You'll use these tools to create images and provision packages.
NOTE - The version of ADK and the version of IoT Core Packages used must match.
Windows PE add-on for the ADK for Windows 10, version 1809 -
optional, required only if you are adding recovery mechanism.
Windows Driver Kit (WDK) -
optional, required only if you are compiling drivers from source code.
Windows 10 IoT Core Packages - The .iso package adds the IoT Core packages and feature manifests used to create IoT Core images. By default, these packages are installed to C:\Program Files (x86)\Windows Kits\10\MSPackages\Retail. Install one or more of the IoT Core packages, depending on the architecutre you are building an image for (Arm, Arm64, x86, x64).
IoT Core ADK Add-Ons - Click Clone or Download > Download ZIP, and extract it to a folder on the technician PC (for example, C:\IoT-ADK-AddonKit). This kit includes the sample scripts and base structures you'll use to create your image. To learn about the contents, see What's in the Windows ADK IoT Core Add-ons).
The Raspberry Pi BSP. Since this lab uses a Raspberry Pi, you'll need to download the Raspberry Pi BSP. If you're working with a device other than Raspberry Pi, visit the Windows 10 IoT Core BSP page to download other BSPs.
If you are buliding a Retail image, you will need to get a code-signing certificate. For kernel driver signing, a Standard Code signing certificate is sufficient. You will require an EV cert to access the Device Update Center in the Hardware Dev Center portal.
Starting Windows 10 IoT Core version 1809 November 10, 2020 update(17763.1577), OEM kernel driver signing is supported. With this, the code signing certificate does not require to be chained to cross-signed root. The Cross-signed root certificates are SHA1 and will be supported till their expiry dates. This expiry does not impact the already signed drivers in the image and impacts signing of new drivers after the expiry date. OEM signing requires secure boot and device guard features to be enabled for both retail and test images. See IoT-ADK-AddonKit 17763-v7 branch for the tooling updates and sample certificates.
We recommend that you purchase your code signing certificate from a Certificate Authority listed from the link above. Building Windows 10 IoT Core retail image or image with Secure Boot enabled requires that all kernel drivers (including all drivers in the BSP that's included in the retail image) are signed with a code signing certificate with Cross Signed root. See Cross-Certificates for Kernel Model Code Signing and the FAQ section "Cross-Signing and SHA-256 Certificates" in code-signing certificate.
As an example, if you chooes to purchase through Digicert, you must choose the "Microsoft Kernel-Mode Code" option in the Platform section:
Other helpful software:
A text editor such as Notepad++. You can also use the Notepad tool, though for some files, you won't see the line breaks unless you open each file as a UTF-8 file.
A compression program such as 7-Zip, which can uncompress Windows app packages.
Visual Studio 2017, used to create an app in Lab 1b: Add an app to your image.
An app built for IoT Core. Our samples use the IoT Core Default app, though you can use your own.
A driver built for IoT Core. Our samples use the GPIO KMDF demo driver, though you can use your own.