Build Number 14393. August 2016
© 2016 Microsoft Corporation. All rights reserved
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).
The privacy statement for this version of the Windows operating system can be viewed here: http://go.microsoft.com/fwlink/?LinkId=506737
You can review linked terms by pasting the forward link into your browser window.
When using the SoftAP clients will not be able to access content exposed by UAP apps. To expose UAP applications via SoftAP the following changes must be made from the console on the device:
reg add hklm\system\currentcontrolset\services\mpssvc\parameters /v IoTInboundLoopbackPolicy /t REG_DWORD /d 1
checknetisolation loopbackexempt -a -n=
For example: checknetisolation loopbackexempt -a -n=IoTOnboardingTask-uwp_1w720vyc4ccym Reboot
There is a Sensor Driver Conflict in the provided FFUs. The Remote Sensor Framework installs drivers for Compass, Magnetometer, Accelerometer and Gyro. The UWP APIs for accessing these from an application assume just 1 is installed. If you are developing a driver for a physically attached device, the remote driver on the Microsoft provided FFUs will conflict. Resolution: The conflicting driver can be removed by connecting to the device via SSH or Powershell and using the tool devcon.exe to remove the remote sensor driver by typing “devcon.exe remove @”ROOT\REMOTESENSORDRIVER*”. The remote sensor driver does not affect OEM created FFUs.
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 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.
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.
Video playback performance on the Raspberry Pi platform has not been optimized. Animated user elements including XAML-based dropdown menus may exhibit less than optimal performance.
Camera support on Raspberry Pi is limited to USB cameras only. Cameras with high data streams may exceed the capabilities of the USB host controller. Consider lower resolutions or lower frame rates to reduce the data stream.
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 IoT Core. Use a different keyboard or mouse. A list of validated peripheral devices can be found on the [documentation here]((/content/en-US/Docs/HardwareCompatList).
Setting the orientation to “Portrait” may not be honored in a Universal App
Attempting to add references to AllJoyn adapter projects may result in errors when using specific SDK versions. To resolve these errors, change Visual Studio’s target platform to match the current SDK version, then reload the project.
Raspberry Pi 2 supports the serial transport for communication through the PL011 UART. This is set by default in kernel debugging scenarios. An application or device driver can use the PL011 UART to send and receive data with the PL011 device driver turning off the debugger using the following command:
bcdedit /set debug off
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. 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. WORKAROUND: Change the default startup app to an application other than that you wish to deploy.
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;”
No workaround at this time
The Azure Active Directory Authentication Library does not work on Windows 10 IoT Core.
The GPIO/I2C/SPI/UART drivers will be disabled when connecting to the DragonBoard with windbg.
The Dragonboard BSP has drivers for the headset jack and microphone jack, but it doesn’t have either of these jacks on board.
The SPI on the Dragonboard will ignore the requested speed and always run at 4.8 Mhz.
IoT Core’s shell infrastructure monitors APPX-type applications running on the device for crashes, and restarts those applications when crashes occur. If the restarted applications continue to crash, the shell will employ a __failfast – a system critical process that causes a bugcheck and reboot in an attempt to recover. Comparable logic and handling is used to background tasks and foreground applications in a headed configuration. Crash handing and retry logic is captured below:
Software\Microsoft\Windows NT\CurrentVersion\Winlogon\IoTShellExtension\CBTConfig (or ForegroundAppConfig for headed) Qword:"FailureResetIntervalMs" – length of time app has to run successfully to reset failures seen to 0. – default is 0x00000000000493E0 == 5 minutes Qword:"BaseRetryDelayMs" -- wait time coefficient. Default is 0xa. Dword:"MaxFailureCount". Default is 10 DWord:"FallbackExponentNumerator", default is 31. Dword:"FallbackExponentDenominator", default is 20 Fallback_exponent = FallbackExponentNumerator / FallbackExponentDenominator; // default is 1.55 When app crash is detected: if time_since_last_crash > failureresetinterval then crashes_seen = 1 else ++crashes_seen; if crashes_seen > MaxFailureCount then __failfast; else delay = (dword) ((float)BaseRetryDelayMs * (crashes_seen ** Fallback_exponent)) wait for delay and relaunch app
On Raspberry Pi, audio via the 3.5mm jack stops working when the direct memory mapped drivers are enabled.
WORKAROUND: 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 ACPI\BCM2844\0 Name: BCM2836 PWM Controller Driver is running. 1 matching device(s) found.
If time sync is failing or timing out this may be due to unreachable or a distant time server, the following can be done to add additional or local time servers.
w32tm /config /syncfromflags:manual /manualpeerlist:"0.windows.time.com 1.pool.ntp.org 2.something else, ..."
The FTP Server no longer runs by default at start-up
To run once: Login with SSH\PS and run this command to start FTP: start ftpd.exe
To run on every boot Users should create a scheduler task:
Login with SSH\PS and create a scheduler task:
schtasks /create /tn “IoTFTPD” /tr ftpd.exe /ru system /sc onstart Schtasks /run /tn “IoTFTPD”