Updating Your Windows Embedded Standard 8 Devices

Posted By J.T. Kimbell
Program Manager

When thinking about the newest features or the things that may excite you about the next Windows Embedded release, servicing may not be the first thing that comes to mind. However, as many of you know, servicing and managing your devices comprises a huge part of their lifecycle and cost. We realize this as well in the Windows Embedded team and strive to make the servicing and update experience as simple as possible for Windows Embedded Standard 8. In many ways, this means making the experience as close as possible to the Windows 8 servicing experience.

Changes to Windows Update Experience

In Windows Embedded Standard 7, all updates to Windows were applicable to Windows Embedded, but only security updates appeared through Windows Update. Additionally, those security updates were packaged separately from the Windows security updates. As such, they would appear in the IT administrator’s consoles separately as “Security Update for Windows 7” and “Security Update for Windows Embedded Standard 7” even though they contained the same payload.

For Windows Embedded 8, all update types will be available through Windows Update (with the exception of service packs) and these will be packaged together with the updates release for Windows 8, meaning less clutter in the IT admin’s console. To learn more about the nine different update types, please see the appendix below.

Also, several changes have been made to Windows 8 that will also improve the Windows Update experience for Embedded customers. As described in this blog post on the Building Windows 8 blog, there will be less disruptive reboots due to Windows Updates, which is being achieved in a handful of ways:

1. Updates will only cause a reboot when security updates are downloaded during the 2^nd week of each month, regardless of when these other updates that require a reboot were downloaded
2. Required update notifications will no longer appear as a popup or “toast”, but instead the notification will appear on the logon screen
3. The computer will not restart if there’s the potential to lose data

Windows Updates available for CTP2

Also related to those improvements is the new Automatic Maintenance functionality. This allows system maintenance and updates to happen intelligently when the PC is not in use. This improves the user experience on the device and also reduces power consumption. For example, all activities that are part of Automatic Maintenance will stop within 2 seconds of user activity on the system. Automatic maintenance can run in two different modes:

1. Fully Automatic Mode
   1. Intelligently schedules during PC idle-time and at scheduled times
   2. All activity is non-interactive and executes silently
   3. PC automatically resumes from sleep to do this maintenance. For some systems (like laptop), this only happens if it’s on AC power.
2. User Initiated Mode
   1. Can be configured for exactly when to run
   2. Can view status of Automatic maintenance and stop if needed

To learn how to create or add a task to Automatic Maintenance, please see this link for XML and this for C code.

Service Packs

If there are any service packs for Windows 8, there will also be a service pack released for Windows Embedded Standard 8 at the same time. There are three differences between the Windows service pack and the one that’s release for Embedded:

1. The Embedded service pack will not be released through Windows Update and must be downloaded through other release channels, such as the Embedded Communications Extranet (ECE), Microsoft OEM Online (MOO), or the Download Center
2. The Embedded service pack will contain some Embedded-specific content in addition to the updated Windows 8 components
3. There will be two types of service packs release for Embedded
   1. One to service the runtime of images in the field
   2. One to update the toolkit and catalog

Reducing Image Bloat

In Windows Embedded Standard 7, many customers have noticed that their device footprint will increase over time. This is a result of servicing files remaining on the system after installation, previous updates remaining on the system, and from unused system files. In Windows 8, customers will be able to combat this with scavenging of the contents of the Windows side-by-side store. This can be done via the Disk Cleanup Utility or by running the following DISM command:

Dism /online /Cleanup-Image /StartComponentCleanup

Servicing the Catalog

For Windows Embedded Standard 8, Windows Embedded Developer Update (WEDU) is the best way for developers to keep their toolkit up-to-date and ensure all devices they create are secure and robust. By using WEDU, developers can include the latest Windows updates in their toolkit, download updates to modules and the catalog, and receive updates to the toolkit.

Windows Embedded Developer Update is a single application through which user can find the latest updates for Windows Embedded development environments.  By utilizing the Microsoft Update service, Windows Embedded Developer Update provides an easy and reliable way to update the distribution shares, catalogs on your computer and across the network.

Key features of WEDU for Windows Embedded developers:

• Auto scan automatically notifies whenever there are available updates
• Simple update selection and download
• Control over which environments to update
• History of updates and ability to hide optional updates
• Supports both Windows Embedded Standard 7 and 8

Appendix