Windows Embedded Blog articles

Older Windows Embedded Compact content is being retired

Christine Ahonen — Wed, 30 Mar 2022 17:46:04 GMT

Beginning September 30, 2022, Microsoft is updating the content on the Device Partner Center (DPC) and the Microsoft Download Center (DLC) for the Windows Embedded Compact and Windows Embedded CE products. Please note that the following content will be retired:

All content for Windows CE 5.0
All content for Windows Embedded CE 6.0
All content for Windows Embedded Compact 7 prior to June 2017 update (M03-2018)
All content for Windows Embedded Compact 2013 prior to June 2021

Recommended actions:

To be compliant with SHA256, customers using Windows Embedded Compact 2013 should update to the June 2021 update or later, with the most recent being the December 2021 update.

If you wish to continue to have access to the updates that are being discontinued, it is recommended that you download the updates and store them in a secure location for use as needed after the updates have been removed.

If you have any concerns about this change, please leave your questions and comments below.

Windows Thin PC ending support on October 12, 2021

Christine Ahonen — Wed, 01 Sep 2021 22:01:24 GMT

A reminder that Windows Thin PC will end support on October 12, 2021.

For organizations still maintaining Windows Thin PC, Microsoft recommends that you consider moving to a newer remote desktop client. Enterprise organizations needing information on upgrading should contact the original equipment manufacturer (OEM) or Microsoft Authorized Distributor.

OEMs needing additional information should contact their Microsoft sales representative or distributor. For information about the Windows lifecycle, please see the Windows Lifecycle FAQ.

Windows Embedded Standard 7 end of support: October 13, 2020

Christine Ahonen — Tue, 10 Nov 2020 23:22:09 GMT

Windows Embedded Standard 7 reached end of support on October 13, 2020. As devices running Windows Embedded Standard 7 will no longer receive updates of any kind from Microsoft,

we recommend migrating any remaining devices to Windows 10 IoT as quickly as possible.

If you were unable to complete your migration in time, Microsoft offers the Extended Security Update (ESU) program as a last resort. This paid program will ensure that your devices receive critical and important security updates for a maximum of three years after the end of support date, which in the case of Windows Embedded Standard 7, would be October 10, 2023.

Extended Security Updates for embedded devices, including Windows Embedded Standard 7, are only available from OEMs. Other products currently supported by the ESU program include SQL Server 2008 R2 for Embedded Systems, Windows Server 2008 R2 for Embedded Systems, and Windows 7 for Embedded Systems. For more information, see the Extended Security Updates FAQ.

Additional resources

For more information on end of support dates for Windows and other Microsoft products, see the following resources:

Final IE10 updates for Windows Server 2012 and Windows Embedded 8 Standard

Christine Ahonen — Thu, 30 Jan 2020 00:06:44 GMT

The final updates for Internet Explorer 10 will be published on Tuesday, February 11, 2020. After that date, all updates, paid assisted support options, and technical content updates for Internet Explorer 10 will be discontinued.

If you are running Windows Server 2012 and Windows Embedded 8 Standard—and still using Internet Explorer 10—please note that, in February of 2020, we will change the Internet Explorer 11 standalone update from an Optional Update to a Recommended Update. For customers using Windows Update, this means that the update will be available in the Important section of Windows Update instead of Optional. If you use WSUS, the Update Type will now be displayed as Recommended.

For more details, see Reminder: IE10 end of support for Windows Server 2012 and Windows Embedded 8 Standard.

Support update for Windows Embedded 8.1 Handheld and Windows Embedded Handheld 6.5

Christine Ahonen — Wed, 28 Aug 2019 04:01:42 GMT

Microsoft would like to remind the community that support for Windows Embedded 8.1 Handheld ended July 9, 2019 and that support for Windows Embedded Handheld 6.5 will end on January 14, 2020.

If your organization is still maintaining these platforms and has additional questions, please contact your account team.

For information about the Windows Embedded support lifecycle, please see the Windows lifecycle FAQ.

Support update for Windows Embedded Standard 2009 and Windows Embedded POSReady 2009

Christine Ahonen — Tue, 29 Jan 2019 23:53:22 GMT

Microsoft would like to remind the community that support for Windows Embedded Standard 2009 ended January 10, 2019 and that support for Windows Embedded POSReady 2009 will end on April 9, 2019.

For customers still maintaining these platforms, Microsoft recommends that you consider moving to Windows 10 IoT Enterprise or Windows 10 Pro. If you are an Enterprise Customer and need information on upgrading, please contact your Original Equipment Manufacturer (OEM) or Microsoft Authorized Distributor. If you are an OEM and need additional information, please contact your Microsoft sales representative or Distributor.

For information about the Windows Embedded support lifecycle, please see the Windows lifecycle FAQ.

IE11 coming to Windows Embedded 8 Standard!

Christine Ahonen — Thu, 29 Aug 2019 17:26:32 GMT

Updated 8/29/2019:

Users of Windows Server 2012 and Windows Embedded 8 Standard can now get Internet Explorer 11 (IE11) by scanning Windows Update and Windows Server Update Services (WSUS) for KB4492872, or by downloading the update from the Microsoft Update Catalog. As noted below, this will appear as “Internet Explorer 11 for Windows Server 2012 for x64 based systems,” “Internet Explorer 11 for Windows Embedded 8 Standard for x64 based systems," or "Internet Explorer 11 for Windows Embedded 8 Standard for x86 based systems.” A “Cumulative Security Update for Internet Explorer 11” applicable to Windows Server 2012 and Windows Embedded 8 Standard will continue to be published as a monthly standalone update in the Microsoft Update Catalog, Windows Update, and WSUS, and will not be included as part of a Monthly Quality Rollup in 2019.

As a reminder, the last security updates for Internet Explorer 10 (IE10) will be published in January 2020, after which IE11 will be the only supported version of Internet Explorer for Windows Server 2012 and Windows Embedded 8 Standard.

Updated 4/16/2019:

Windows Server 2012 and Windows Embedded 8 Standard customers can now begin using Internet Explorer 11 (IE11) in their test environments or pilot rings by downloading “Internet Explorer 11 for Windows Server 2012 for x64 based systems,” “Internet Explorer 11 for Windows Embedded 8 Standard for x64 based systems," or "Internet Explorer 11 for Windows Embedded 8 Standard for x86 based systems” from the Microsoft Update Catalog.

In addition, to help you remain secure on IE11, we will publish a “Cumulative Security Update for Internet Explorer 11” that will be applicable to Windows Server 2012 and Windows Embedded 8 Standard, starting May 2019. This update will be available from the Microsoft Update Catalog, Windows Update, and Windows Server Update Services (WSUS); and will not be included as part of a Monthly Quality Rollup in 2019.

For more information, including guidance related to language packs, see KB4492872.

Microsoft is consolidating its browser strategy around IE11. Learn more about opportunities to pilot it on Windows Embedded 8 Standard!

Change to the Windows Embedded Developer Update

Christine Ahonen — Tue, 13 Nov 2018 21:04:53 GMT

Currently, Windows Embedded Standard 7 SP1 (WES7 SP1) and Windows Embedded 8 Standard (WE8S) customers use the Windows Embedded Developer Update (WEDU) tool to update WES7 SP1 distribution shares (DS) and WE8S catalogs. Since October 2016, Microsoft stopped releasing individual updates for WES7 SP1 and WE8S. Instead, cumulative rollup updates are released every month for WES7 SP1 and WE8S.

End of WEDU publication of WES7 SP1 and WE8S updates

Starting in November 2018, no monthly, cumulative rollup updates for WES7SP1 and WE8S will be published to WEDU. We advise our customers to get the Security Monthly Quality Rollup updates from the Microsoft Update Catalog. To update the WES7 SP1 distribution shares and WE8S catalogs, use the Import feature of the Image Configuration Editor (ICE) tool (see the instructions below).

Update WES7 SP1 distribution shares and WE8S catalogs using ICE

Below are the instructions for making future updates to WES7 SP1 distribution shares and WE8S catalogs using the ICE tool.

Important WEDU will still continue to offer all the WES7 SP1 and WE8S updates released through October 2018.

Update WES7 SP1 distribution shares using ICE

Find the latest WES7 SP1 Security Monthly Quality rollup update in the Microsoft Update Catalog

Go to https://www.catalog.update.microsoft.com.
In the Search box, type Security Monthly Quality Rollup for Windows Embedded Standard 7 and select the Search button (see Figure 1)
From the list of results, identify the latest security, monthly quality rollup update for WES7 SP1 by looking at the year and month information in the title of the updates. For example, the update titled, “2018-10 Security Monthly Quality Rollup for Windows Embedded Standard 7 for x86-based Systems (KB4462923)” corresponds to the rollup update released in October 2018 for the x86 architecture.
Download and save the latest WES7 SP1 Security Monthly Quality rollup update (see Figure 2).

Import the latest WES7 SP1 Security Monthly Quality rollup update to a WES7 SP1 distribution share using ICE

Open the WES7 SP1 ICE tool and select a WES7 SP1 distribution share.
After selecting the distribution share, select File > Import > Import Package(s)…. Then, select the update package downloaded in Step 4 of Find the latest WES7 SP1 Security Monthly Quality rollup update in the Microsoft Update Catalog (see Figure 3).

Once the import operation completes successfully, the latest WES7 SP1 Security Monthly Quality Rollup update is added to the WES7 SP1 distribution share (see Figure 4).

Update WE8S catalogs using ICE

Find the latest WE8S Security Monthly Quality rollup update in the Microsoft Update Catalog

Go to https://www.catalog.update.microsoft.com.
In the Search box, type Security Monthly Quality Rollup for Windows Embedded 8 Standard and select the Search button (see Figure 5).
From the list of results, identify the latest security, monthly quality rollup update for WE8S by looking at the year and month information in the title of the updates. For example, the update titled, “2018-10 Security Monthly Quality Rollup for Windows Embedded 8 Standard for x86-based Systems (KB4462929)” corresponds to the rollup update released in October 2018 for the x86 architecture.
Download and save the latest WE8S Security Monthly Quality rollup update (see Figure 6).

Import the latest WE8S Security Monthly Quality rollup update to the WE8S catalog using ICE

Open the WE8S ICE tool and select a WE8S catalog.
After selecting the WE8S catalog, select File > Import > Import Module(s)…. Then, select the update package downloaded in Step 4 of Find the latest WE8S Security Monthly Quality rollup update in the Microsoft Update Catalog (see Figure 7).

Once the import operation completes successfully, the latest WE8S Security Monthly Quality Rollup update is added to the WE8S catalog (see Figure 8).

Announcing support for TLS 1.1 and TLS 1.2 in Windows Embedded Standard 2009 and Windows Embedded PO

Christine Ahonen — Tue, 13 Nov 2018 19:27:20 GMT

[This blog post was originally published on October 10, 2017 on MSDN.]

As a follow-up to our announcement regarding TLS 1.2 support at Microsoft, we are announcing that support for TLS1.1/TLS 1.2 on Windows Embedded POSReady 2009 and Windows Embedded Standard 2009 will be available for download as of October 17th, 2017. We're offering this support in recognition that our customers have a strong demand for support for these newer protocols in their environment.

For more information on where to get this update please see the complete blog post at https://cloudblogs.microsoft.com/microsoftsecure/2017/10/05/announcing-support-for-tls-1-1-and-tls-1-2-in-xp-posready-2009/

Improve Windows Update Performance for New Windows Embedded Image Deployments

Christine Ahonen — Tue, 13 Nov 2018 19:26:10 GMT

[This blog post was originally published on May 24, 2017 on MSDN.]

Occasionally, the Windows Update (WU) process can take significantly longer than expected for new image deployments on Windows Embedded Standard 7 SP1, POSReady7, and ThinPC. To help speed up this process, you need to install three specific KB packages, and you must stop the Windows Update service before each installation. The packages are:

Here are the steps:

Open an administrator command prompt. Click the Start menu, right-click Command Prompt, and then click Run as Administrator.
Stop the Windows Update service using the net stop wuauserv
After the service stops, immediately install a KB package. This will automatically restart the WU service.
Repeat steps 2 and 3 until all three packages listed above are installed.
Close the Command Prompt window, and run Windows Update from within Control Panel to check for any additional updates.

Windows Embedded OS Down-Level Servicing Model FAQ

Christine Ahonen — Tue, 13 Nov 2018 19:24:53 GMT

[This blog post was originally published on May 23, 2017 on MSDN.]

We have created this FAQ below to better support our partners seeking embedded-specific details around the down-level OS servicing changes for Windows 7 SP1, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2. Please note that questions 4-8 apply broadly to non-embedded scenarios.

Q1. For embedded partners who don’t have assigned account managers, how can servicing changes be communicated before wide spread announcements?
A1. Since we are following the Windows update model customers who do not have an account manager may review the https://blogs.technet.microsoft.com/windowsitpro blog for updates.

Q2. How can offline embedded machines access or download Monthly Rollups?
A2. The same way that they consume updates offline today. The only difference is that they only have to download one update instead of many.

Q3. How will offline embedded machines (often mission critical) be serviced if a Monthly Rollup causes an issue?
A3. We expect MUC offline scenarios to have advanced testing in-house before being released to devices. As such, we don’t anticipate many situations where a rollback is necessary if compatibility checks have already been done on test systems. If a Monthly Rollup happens to cause an offline issue, the customer will need to report the issue to CSS. If a fix is issued, then it would be included in the next relevant update.

Q4. How can machines with size limitations download Monthly Rollups?
A4. We understand that some machines have size limitations. While either the Security Only Update OR the Monthly Rollup is necessary to be covered for critical security fixes for a given month, we recommend installing the Monthly Rollup because each update will only download the new delta fixes (for customers using Windows Update, or WSUS with “express installation files” support enabled). In addition, with new Monthly Rollups superseding those from previous months, disk cleanup will remove the older installed and superseded Monthly Rollups after a certain amount of time (see below Questions for further details). In comparison, the Security Only updates (which are not superseded by the subsequent Security Only update) will continue to reside on disk and not be replaced if any binaries are in multiple updates, which consumes greater space over time. Please note that removal of superseded updates happens automatically on Windows versions equal to or newer than Windows 8. For Windows 7, the user can apply the Task Scheduler to create a recurring task to run the disk cleanup tool.

Starting February 2017, the Security Only update does not include updates for Internet Explorer. With this separation, the Security Only update package size is significantly reduced.

Q5. Can customers skip or uninstall Monthly Rollups?
A5. Customers can choose to not install a given Monthly Rollup, and can uninstall the Monthly Rollup as well. If multiple Monthly Rollups are installed and present on disk, then uninstalling the latest Monthly Rollup would “revert” to the state of the older Monthly Rollup. If no older Monthly Rollups are installed on disk, then uninstalling the latest Monthly Rollup would “revert” to a state with none of the Monthly Rollups present. See below for further details on how older Monthly Rollups can be removed from disk.

Q6. What is the Monthly Rollup disk cleanup process?
A6. Since each new Monthly Rollup supersedes the previous one, disk cleanup will automatically take care of removing older Monthly Rollups from disk over time. On Windows 8 and later versions, a cleanup task will run regularly during the next maintenance window that identifies all installed updates that have been superseded by another installed update. Once 30 days have passed since a particular update has been marked superseded by this cleanup task, that update will be removed from disk on the next task run. The same behavior will apply for the Monthly Rollups, where an older Monthly Rollup will remain on disk for approximately 30 days (may vary by a few days based on maintenance windows) after a newer / superseding Monthly Rollup is installed. Note that once an older Monthly Rollup is removed from disk, it will no longer be a state to “revert” to if uninstalling a newer Monthly Rollup.

Below is an example of this cleanup and uninstallation timing:

November 2016 Monthly Rollup is installed on 11/8/2016
December 2016 Monthly Rollup is installed on 12/13/2016
- On the next scheduled run of the cleanup task (assume this happens to run on 12/14/2016), the November 2016 Monthly Rollup is marked as superseded.
January 2017 Monthly Rollup is installed on 1/10/2017
- On the next scheduled run of the cleanup task (assume this happens to run on 1/11/2017), the December 2016 Monthly Rollup is marked as superseded.
- On 1/13/2017, the November 2016 Monthly Rollup will have been marked superseded for 30 days
- On the next scheduled run of the cleanup task, November 2016 Monthly Rollup will be removed from disk.
- The January 2017 and December 2016 Monthly Rollups are still present and installed on the PC, meaning that you can still â€œrevertâ€ to the December 2016 Monthly Rollup state if uninstalling the January 2017 Monthly Rollup. The November 2016 Monthly Rollup is no longer available as an installed state to "revert"

Note that for Windows 7, this cleanup task does not run automatically. Task Scheduler could be utilized to create a recurring task to run cleanup – otherwise this will not automatically occur. In addition, a user-initiated Windows Update Cleanup using the disk cleanup tool can also be used to remove superseded updates, but please note that this would immediately remove any superseded updates and not follow the 30 day process used by the cleanup task (in Windows 8 and later versions).

Q7. What is the guidance around re-applying Monthly Rollups after enabling Optional Components?
A7. When Windows installs an update, all serviced content is staged for installation, including updates for Optional Components (such as Features and Roles in Server Manager). When an Optional Component is later enabled, the component servicing model will apply the highest available version of the component, which is the latest serviced version. Therefore, Optional Components will be up-to-date based on previously installed updates once they are enabled. Note that this assumes the staged content has not been corrupted, missing, etc., in which case Windows Update would be required to download the repair content. In summary, enabling Optional Components will apply them in the latest serviced state without needing to re-apply the update. Features that are installed via other means (like Features on Demand, apps downloaded outside of Optional Components, etc.) would likely need Windows Update to re-apply the update.

Q8. How can customers assess their optimal update strategy?
A8. Please review “Update strategy choices” on this blog post.

Recommended System File Checker Usage for Windows Embedded Systems

Christine Ahonen — Tue, 13 Nov 2018 19:22:11 GMT

[This blog post was originally published on June 15, 2016 on MSDN.]

System File Checker (SFC) is a built-in command-line utility you can use to find and repair missing and corrupted files. The tool is available on all Windows platforms, including all the supported embedded systems.

There are several options (switches) you can use with SFC, however, this post will only discuss the following:

/scanfile

/verifyfile

/verifyonly

/scannow

The /scannow option is not recommended because it may return false positives for corruption*. Instead, we recommend that you use sfc /scanfile, sfc /verifyfile, or sfc /verifyonly. With these options, you’ll need to provide the full path to the file you want to check.

*Use of /scannow may also indicate that corrupted files have been fixed. However, subsequent scans will still show these files as corrupted.

Microsoft .NET Framework Versions supported by Windows Embedded Products

Christine Ahonen — Wed, 30 Mar 2022 18:14:43 GMT

[This blog post was originally published on August 10, 2015 on MSDN.]

***Updated 10/12/2021 updated support table to reflect current levels of support***

***Updated - Added Microsoft .NET Framework 4.7 Support***

This communication details the .NET Framework versions supported by the Windows Embedded Products after June 2017. Read on for further details.

Details

The following table specifies the Microsoft support plans for all Microsoft .NET Framework versions after June 2017. We will update this blog when our support plan changes, so check this page regularly for the latest support details.

	.NET Framework version
	3.5 SP1	4.5.2	4.6	4.7	4.8
Windows Embedded Standard 7	Y	Y	Y	Y	Y
Windows Embedded POSReady 7	Y	Y	Y	Y	Y
Windows Embedded 8 Standard	Y		Y	Y	Y
Windows Embedded Standard 8.1 Pro	Y	Y	Y	Y	Y
Windows Embedded 8.1 Industry	Y	Y	Y	Y	Y

Y=Supported

Note that the following products are not listed because they have moved out of extended support:
- Windows Embedded Point of Service
- Windows XP Embedded
- Windows Embedded 8 Industry
- Windows Embedded POSReady 2009
- Windows Embedded Standard 2009
For information about general Windows support for the .NET Framework and any restrictions, visit the .NET blog website.