Redirecting you to Developer Center... Click here if you are not automatically redirected.

Release Notes for Windows 10 IoT Core

Insider Preview Build Number 10556.0

© 2015 Microsoft Corporation. All rights reserved

This document provides late-breaking or other information that supplements the documentation included with the Windows 10 IoT Core Insider Preview.

Thank you for downloading Windows 10 IoT Core Insider Preview. 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) and the Raspberry PI2 based on the ARM Cortex-A7 based SoC (also referred to as the RPI).

Privacy Statement

The privacy statement for this version of the Windows operating system can be viewed here:

You can review the privacy statement by pasting the forward link into your browser window.

What’s New

  • Windows 10 IoT Core Insider Preview October 15 Release
    • Serial support on Raspberry Pi for TX and RX pins
    • High performance GPIO driver option with > 100x improvement
    • Arduino Wiring Project System for Visual Studio
    • Updated base OS build
    • Bug Fixes

Release Notes

Devices running IoT Core may be extremely slow to boot up on the first boot when using some 8GB class 10 SD cards. Slow boot times may be over 15 minutes. Subsequent boots will be much quicker on the affected cards.

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 with builds of Windows 10 IoT Core which are later than 10240 unless the firmware is version .082 or later. The minimum recommended version of the firmware is “MinnowBoard MAX 0.82 32-Bit”. Firmware updates can be downloaded from

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.

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.

Some USB keyboards and mice may not work on the Raspberry PI2. Use a different keyboard or mouse. A list of validated peripheral devices can be found on the documentation at

On the Raspberry Pi2 the GPIO pin 0 and GPIO pin 1 were available to user mode applications in the April 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 and are under control of VC firmware. For compliance with this specification, these pins should be left unconnected.

Known Issues

  • 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.
  • GetNetworkUsageAsync may throw a System.UnauthorizedAccessException (1972129). WORKAROUND: None.
  • 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.
  • The IoT Core Default Application may display two different IP addresses for the same adapter where one is a stale address. (3303771). WORKAROUND: None.
  • 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:
  • Data breakpoints have been disabled on the Raspberry Pi2 (4266252). WORKAROUND: Data breakpoints will be enabled in a future release.
  • 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.
  •!PAGER::DisplayString may return INVALID_POINTER_READ exception. (1552523) WORKAROUND: None.
  • The time may not sync on devices running IoT Core. (4444681) Manually update the time or programmatically force a time sync.
  • 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, FTDI USB-Serial adapters will ignore the requested baud rate and will use 3.8Mhz. (5348073) WORKAROUND: Workaround for FTDI devices on x86
  • WiFi direct is partially supported on IoT Core using the WinRT WiFi direct APIs. For more details see WiFi Direct limitations on IoTCore.
  • On Raspberry Pi, audio via the 3.5mm jack stops working when the direct memory mapped drivers are enabled. (6678121) WORKAROUND: See Workaround for audio and direct memory mapped drivers.

Workaround for FTDI devices on x86

  1. Plug in the FTDI device to your MBM.
  2. 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.
  3. 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.
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\system\controlset001\enum\<device instance path>\Device Parameters]
  1. Copy ftdi-fix.reg to your device and run reg import ftdi-fix.reg to apply the registry keys.
  2. Unplug and replug the FTDI device.

WiFi Direct limitations on IoTCore

  1. The IoTCore device has to be the connecting device – it will not work as the advertising device with another device initiating the connection.
  2. Advanced pairing must be used. The sample app demonstrates how to use the advanced pairing API’s to pair the devices prior to connecting.
  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:

reg add HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DeviceIds\ACPI\BCM2844 /v dmap.inf /t REG_BINARY /d 02ff0100
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\enum\ACPI\bcm2844\0 /v ConfigFlags /t REG_DWORD /d 0x20
devcon restart acpi\bcm2844

Verify that the driver for the PWM device node is BCM2836 PWM Controller:

C:\Data>devcon status acpi\bcm2844
    Name: BCM2836 PWM Controller
    Driver is running.
1 matching device(s) found.