October 2018 Update Release Notes for Windows 10 IoT

Article
04/03/2023

Build Number 17763. October 2018

Important

If you're using the October 2018 Update, please use the October Update (with January servicing pack, build 17763.253) release instead. We have found that there are known issues that affect users of the October 2018 Update.

Windows 10 IoT enables development of embedded or dedicated-purpose devices and is the choice for OEMs and developers building Windows solutions for smart devices.

This document provides information that supplements other content and documentation for this release of Windows 10 IoT.

Privacy Statement

The privacy statement for this version of the Windows operating system can be viewed at https://go.microsoft.com/fwlink/?LinkId=521839.

What's New in October 2018 Update

Windows 10 IoT Enterprise & Windows 10 IoT Core

The Windows 10 IoT October 2018 Update will have 10 years of support for both IoT Core and IoT Enterprise.
Azure IoT Edge is a fully managed service that delivers cloud intelligence locally by deploying and running artificial (AI) workloads, Azure services, and custom logic directly on Windows 10 IoT devices.
Windows Machine Learning allows developers to use pretrained machine learning models in their applications. These models are typically trained in the cloud to be evaluated at the edge. Local evaluation on devices running Windows 10 IoT helps mitigate concerns of connectivity, bandwidth, and data privacy.

Windows 10 IoT Core

Windows 10 IoT Core Services subscription is now generally available. This subscription comes with three main benefits including 10 years of OS support, update control with the Device Update Center, and Device Health Attestation (DHA).
To meet growing customer and partner demand for silicon diversity, Microsoft, in close partnership with NXP, have added support for NXP i.MX 6, 7, and 8M series processors to Windows 10 IoT Core.
Qualcomm and Microsoft have created a solution that combines Windows 10 IoT Enterprise with Snapdragon processors to build devices that consume less power, are always connected and wake instantly. Long battery life enables dedicated devices like mobile POS and line-of-business tablets to last a full day of heavy use.
The Windows 10 IoT Core Default App has more features that users can leverage for their own applications, especially when bringing their devices to market. These features include weather, inking capabilities, audio capabilities.
If you are building an open retail device for commercial deployment to a "specific/limited installation" (i.e. factory or retail store) where the end user does the final configuration and you document your customers that they must obtain a certificate for WDP and install it on both WDP and connecting browsers and passwords are changed on WDP, then using WDP in this narrow commercial instance is acceptable. Retail images in this scenario should still not include IOT_TOOLKIT, but should use the IOT_WEBBEXTN package to pull in WDP.
Limpet.exe is now available as an open source project. To make testing easier, we have a non-signed, pre-built version of Limpet.exe available and can be downloaded right from WDP. Learn more about this feature from the Windows Device Portal documentation.
With RS5, developers are now able to flash custom FFUs onto their device using the Dashboard. This can be done with either the DragonBoard 410C or NXP. Learn more and get started here.
Windows 10 IoT Core now uses the same touch keyboard components as the desktop edition of Windows, which allows for features like dictation mode, the entire set of Windows keyboard language layouts, and more. This new update also includes support for emoticons, most input "scopes", and better multi-language support. Learn how to leverage these features here.
Learn how to configure your device to allow to be turned off while not in use and to be turned on when a user touches a screen.
Bluetooth A2DP-SINK is now optionally supported (e.g. Allows playback from remote source such as iPhone to IoT device) and Bluetooth A2DP-SRC is now an optional package (was available by default in the April 2018 Release). You can control Bluetooth A2DP-SRC and A2DP-SINK profile preferences when both profiles are present and when pairing with another device that also supports both.
By design, Windows 10 IoT Core does not display an application frame around an application’s window – in order words, an application is shown as full screen. But with this release, developers have the option of configuring title bars.
Bus tools that allow you to interact with Gpio, I2c, Spi and UART are now available in our samples repository. These tools will run on any edition of Windows including Windows 10 IoT Core and Windows Enterprise.
The Windows.System.Update Namespace API enables calls for interactive control of system updates. This namespace is only available for Windows 10 IoT Core.
If you're looking to use IoT Central as part of a Windows 10 IoT solution, you can now prepare and connect a Windows 10 IoT Core device to your Azure IoT Central application.
The release for the Raspberry Pi 3B+ (the downloadable ISO can be found here) is a technical preview and there is currently no timeline for a release version. For a better evaluation experience and fr any commercial products, please use the Raspberry Pi 3B or other devices with supported Intel, Qualcomm, or NXP SoCs.

IoT Enterprise Manufacturing Guide

A new manufacturing guide for Windows 10 IoT Enterprise is now available.

Improvements in Assigned Access

Windows 10 IoT Enterprise

Kiosks and digital signs are often place in public places where issues are widely seen by people. With built-in status reporting, device management systems are automatically made aware of problems and can issue corrective actions like restarting the device or dispatching a service technician.
Reducing deployment and management costs are key drivers of ROI. Windows 10 IoT Enterprise has improved features for configuring a kiosk experience via a new wizard in the Settings app, managing multi-app kiosks and tailoring the Microsoft Edge browser experience for kiosk devices.
While device builders have great flexibility to configure Assigned Access using provisioning packages, the Settings app, and mobile device management systems, some customers still need more. Using a new set of Assigned Access APIs, developers can now configure Assigned Access programmatically from within their applications.
With the October 2018 release, customers can specify an auto-launch experience as part of the multi-app assigned access configuration so the end user can always have a default primary app experience.
You can control what the user sees from the moment the device is turned on until it's powered off. Starting by showing your logo instead of the Windows logo at boot, or auto-restart apps without error messages after an app crash, a system issue or a power interruption.
You can use the Unified Write Filter (UWF) feature to build a "read-only" device that returns to a known state after a power cycle by keeping disk changes in memory instead of writing them to disk. You can also combine UWF with the Hibernate Once, Resume Many (HORM) feature to resume to a predefined session.

More Management Support