That's it, you have a bootable drive! NO special magic needed. Then take contents of C:\WinPE_amd64\media and copy them to your formatted flash drive. Then open “Deployment and Imaging Tools Environment” and type in copype amd64 C:\WinPE_amd64Īmd64 can be replaced with x86 or ARM as needed. Take a flashdrive and format it as FAT32 (NTFS should work too). To do that, download Windows Deployment Kit and tick Windows PE. Then you need to create a bootable flashdrive that runs Windows PE. Save them somewhere safe, we will need them later. Export-WindowsDriver -Online -Destination C:\driversBackup
Use PowerShell to export drivers from your device while it’s running “normal” Windows.
You need to get 32 bit drivers for 32 bit Windows IoT, and 64 bit drivers for 64 bit IoT. Export Driversįirst see what kind of device you are running. Some guys mention that they managed to get Windows IoT to work on I3 and I7 CPUs and even get the GPU to work. A Cherry Trail (Atom® x5-Z8300) Intel Compute Stick is one example of such device. A device with unsupported processor would still boot up, but GPU acceleration won’t work, and some peripherals won’t work either. Cherry Trail Intel Atom processors are not supported. Currently Microsoft only provides 32 bit image of Windows IoT for Minnowboard Max, and if you wish to test it on another machine, you have to build an image yourself, the process is described in Windows IoT Core Build your own image section.Ĭurrently Intel provides board support packages for Atom BayTrail and Atom Apollo Lake processors. This is not the case with “normal” operating systems- they would boot either way. A 32 bit UEFI will boot 32 bit Windows IoT, and 64 bit UEFI can only boot 64 bit Windows IoT. Windows IoT core will boot on most UEFI systems. The Goal is to find a few off-the-shelf devices that work well and bring together everything needed for an average dev can get them working immediately. The only way to find out which ones are compatible is to test them. Many off-the-shelf devices are compatible with Windows IoT, but it uses a more restricted driver model.
How to Test a device with Windows IoT Background Provide fully built images for each device.Provide x86 and 圆4 apollo lake Images for quick testing of devices, so everyone doesn’t have to download 50 metric tons of stuff just to test their device.Document which devices work and which don’t.However, I was enlightened by a stranger on Reddit - you can run Windwos IoT Core pretty much on any computer! Microsoft just does not bother explaining it properly! Goals You might protest that off -the shelf devices don’t have GPIOs, but one can use a microcontroller over USB.įor a long time I was lamenting the fact that there are only 3 supported boards on the official website. Bigger devices, this can be both good an bad.
If you go to Android AOSP route, that’s not an issue, but it’s also a lot more work. Unlike a Kiosk app, there is no system UI sitting around that needs to be locked down.