This document provides late-breaking or other information that supplements the documentation included with the Windows 10 IoT Core.
Thank you for downloading Windows 10 IoT Core. Windows 10 IoT Core is the version of Windows 10 intended for development of embedded or dedicated purpose devices and the choice for the Maker community. This package contains the bits and tools needed to install Windows 10 IoT Core on the MinnowBoard Max based on Intel® Atom E38xx series SoC (also referred to as MBM board), the Raspberry PI2 based on the ARM Cortex-A7 based SoC (also referred to as the RPI) and the DragonBoard 410c based on the QualComm Snapdragon™ 400 series processor (also referred to as the Dragon).
You can review linked terms by pasting the forward link into your browser window.
Windows 10 IoT Core Public Release
Support for servicing updates
Serial support on Raspberry Pi for TX and RX pins
Support for Realtek Wi-Fi chipsets (RTL8188EU & RTL8192EU)
High performance GPIO driver option with > 100x improvement
Support for the QualComm DragonBoard
Updated features for Windows Device Portal
Secure boot has been enabled
Third party pure python libraries can be run on IoT core
PWM and ADC chips have been enabled
Updated base OS build
The default administrator user name and password are hard coded in the Windows 10 IoT Core image. This is a security risk for the device, and it should not be exposed to an open internet connection until the password has been changed.
The MinnowBoard Max will not boot unless the firmware is version .082 or later. The minimum recommended version of the firmware is “MinnowBoard MAX 0.83 32-Bit”. Firmware updates can be downloaded from http://go.microsoft.com/fwlink/?LinkId=708613.
The Windows 10 IoT Core image included in this drop supports the peripherals that are exposed on the MinnowBoard MAX board. Subsequently, Intel® will provide support of the full feature set of the Baytrail processors including the Intel Celeron™ Processors J1900/N2930/N2807 and Intel Atom™ Processors E38XX.
On the DragonBoard, a shutdown command will not power off the board. The system will restart. Please power off the board by disconnecting the power.
Windows 10 UWP projects created with Visual Studio RC are not compatible with the current Visual Studio release. Users should create a new blank UWP project or Background Application (IoT) project and copy their source code into the new project.
Windows 10 IoT Core is still being ported to the Raspberry PI. The video driver for the Raspberry PI is still under development, and its performance has not yet been optimized. Animated user elements, such as XAML based drop down menus in particular, may display poorly.
With this release of Windows 10 IoT Core for the Raspberry Pi 2, support for camera peripheral devices is limited. The PiCam device directly connected to the onboard camera bus is not currently supported, as it requires GPU services that are not currently available on the Raspberry Pi because the DirectX driver has not been implemented. Modern USB webcams produce data streams that are very demanding on the USB Host controller. Even when used with low resolution settings webcams will require additional USB fine tuning and specialized control logic. We are planning to support a number of USB cameras in the near future and will publish specific information on supported devices as soon as possible.
Hardware volume controls for USB microphones and speakers which depend on Windows system to change system volume are currently not supported on Windows 10 IoT Core.
On the Raspberry Pi2 the GPIO pin 0 and GPIO pin 1 were available to user mode applications in the April Insider Preview release of version of Windows 10 IoT Core, but are no longer available. Attempting to open these pins with Windows::Devices::Gpio::GpioController::OpenPin() will return HRESULT_FROM_WIN32(ERROR_NOT_FOUND). GPIO pins 0 and 1 are reserved on the Raspberry Pi by the HAT specification (https://github.com/raspberrypi/hats) and are under control of VC firmware. For compliance with this specification, these pins should be left unconnected.
Windows Device Portal may stop working after a day of continuous uptime. (5458435) WORKAROUND: Restart the device.
Setting the orientation to “Portrait” may not be honored in a Universal App (3039042) WORKAROUND: None
On Raspberry Pi and Dragonboard, switching from a non-default drive mode to a different non-default drive mode may produce a glitch on the GPIO pin. (3890679) WORKAROUND: Set drive mode once at the beginning of the application.
The Default startup app may conflict with itself when it is also deployed from Visual Studio (4266059). WORKAROUND: Change the default startup app to an application other than that you wish to deploy.
BackgroundMediaPlayer.MessageReceivedFromForeground may crash. (2199869) WORKAROUND: The following line of code may crash: “BackgroundMediaPlayer.MessageReceivedFromForeground += OnMessageReceivedFromForeground;”. To prevent the crash, add this code so that it is executed first “var player = BackgroundMediaPlayer.Current;”
Data breakpoints have been disabled on the Raspberry Pi2 (4266252). WORKAROUND: None at this time
The Azure Active Directory Authentication Library may not work on Windows 10 IoT Core (4266261). WORKAROUND: Do not use the Azure Active Directory Authentication Library.
A MediaEncodingProfile.CreateWma( Windows.Media.MediaProperties. AudioEncodingQuality.Auto) method call may fail on the Raspberry Pi 2 with the error message No suitable transform was found to encode or decode the content. (Exception from HRESULT: 0xC00D5212). (4510128) WORKAROUND: None.
More.com!PAGER::DisplayString may return INVALID_POINTER_READ exception. (1552523) WORKAROUND: None.
When deploying a Node.JS project BackgroundTaskHost.exe may fail with an error.(4873190) WORKAROUND: None.
On Dragonboard, GPIO/I2C/SPI/UART stop working when COM1 or COM2 is enabled for kernel debugging. (4710796) WORKAROUND: Use USB debug transport.
The Dragonboard BSP has drivers for the headset jack and microphone jack, but it doesn’t have either of these jacks on board. (4791855) WORKAROUND: USB headsets cannot be used without manually disabling these devices
The SPI on the Dragonboard will ignore the requested speed and always run at 4.8 Mhz. (5055938) WORKAROUND: None.
If an application or background task enter a bad state the device may blue screen instead of allowing an opportunity to connect through an SSH session and reconfigure the device. (5098713) WORKAROUND: None.
A conflict may result if a webcam and a USB audio adapter or headset are connected to a Raspberry Pi2 at the same time. (5383535) WORKAROUND: Use an analog headset plugged into the onboard audio jack of the Raspberry Pi2.
If the device name is set to a value longer than 15 characters, it may cause a boot failure. If this occurs the device will need to be reflashed to recover. (5474244) WORKAROUND: Do not use a device name that is longer than 15 characters.
SerialDevice.FromIdAsync() may return a NULL value when trying to open Silicon Labs USB-Serial adapters. (5385500) WORKAROUND: Run iotstartup headless remove ZWaveHeadlessAdapterApp and reboot.
On MinnowBoardMax, the SPI driver will generate malformed bus traffic for FullDuplex and TransferSequential transfers at clock speeds less than 250kHz. (3076149) WORKAROUND: Use clock speeds of 250kHz or greater.
On MinnowBoardMax, Silicon Labs based USB-Serial converters (USB\VID_10C4&PID_EA60) will fail to load with error 31. (5307602) WORKAROUND: Ensure the device is unplugged, then run: reg add "HKEY_LOCAL_MACHINE\system\controlset001\enum\usb\VID_10C4&PID_EA60\0001\Device Parameters" /v PortName /t REG_SZ /d COM3
On MinnowBoardMax, a NULL value may be returned by SerialDevice::FromIdAsync() when devices are connected to the top USB port on MinnowBoardMax (2175837) WORKAROUND: Update to firmware version 0.83 or later from Intel’s website: http://firmware.intel.com/projects/minnowboard-max.
Run devcon status FTDIBUS\* and note the device instance path of your device.
C:\Data>devcon status ftdibus\*
Name: USB Serial Port
Driver is running.
1 matching device(s) found.
Create a file named ftdi-fix.reg with the following contents, where <device instance path> is replaced with the device instance path determined in the previous step.
Copy ftdi-fix.reg to your device and run reg import ftdi-fix.reg to apply the registry keys.
Unplug and replug the FTDI device.
WiFi Direct limitations on IoTCore
The IoTCore device has to be the connecting device – it will not work as the advertising device with another device initiating the connection.
Advanced pairing must be used. The sample app demonstrates how to use the advanced pairing API’s to pair the devices prior to connecting.
Not all wireless adapters support WiFi direct. We have tested and validated that the “Realtek RTL8188EU Wireless Lan 802.11n USB 2.0 Network adapter” works, but other adapters may not be supported.
3. Not all wireless adapters support WiFi direct. We have tested and validated that the “Realtek RTL8188EU Wireless Lan 802.11n USB 2.0 Network adapter” works, but other adapters may not be supported.
Workaround for audio and direct memory mapped drivers
After the direct memory mapped drivers have been enabled, run: