• Windows Embedded Compact 13
• Windows Compact Embedded
• Windows Embedded Compact 7 Download
• Windows Embedded Compact 2013 Update
• Windows Embedded Compact 2013 Queen Tree Pictures

Windows Embedded Compact 2013:::: Is this page helpful? Any additional feedback? Install Windows Embedded Compact 7 RDP RemoteFX Update (same DVD as step 2) 4. Install Windows Embedded Compact 7 Update 3 from another DVD. Go to 'Program And Feature' and find Windows Embedded Silverlight Tools and update it to version 7 (I think, you don't have any choice between versions anyway).

Originally published: July 26, 2016
Updated: October 14, 2020

Please go here to search for your product's lifecycle.

On this page:

Windows - General

What is the Lifecycle Policy for Windows?

Windows 10 Semi-Annual Channel and Windows Server Semi-Annual Channel are governed by the Modern Policy. Other Windows products are governed by the Fixed Lifecycle Policy. Search for the product lifecycle for your specific Windows product and its corresponding Lifecycle Policy and end-of-support dates.

What is the difference between a Windows quality update and a Windows feature update?

A Windows quality update is an incremental update to Windows products that includes bug fixes and security issue resolutions but includes no new features.

A Windows feature update is an update that contains new features. A feature update also includes all previous quality updates, as applicable.

Go here for more information on these terms.

If I obtained Windows when I purchased a new device, who provides support?

If you have a valid Windows license, you are eligible for support from Microsoft, subject to the Microsoft Lifecycle Policy and the support terms and conditions that were in place at the time of purchase. If you acquired your Windows operating system through the Microsoft Volume Licensing program or from an Original Equipment Manufacturer (OEM), Microsoft offers access to a wealth of online self-help support content in addition to paid technical help offerings. If you acquired your Windows operating system through an OEM, you may also contact your OEM for more information about the support offerings for Windows operating systems from that OEM.

Can I use prior versions of Windows on a device running a newer version?

To use prior versions of Windows on devices currently running a newer version, it is possible for customers to obtain a license for downgrade rights. These downgrade rights will vary depending on whether the software was acquired via Volume Licensing, Original Equipment Manufacturer (OEM), or Full Packaged Product (FPP). To learn more about these rights, review the downgrade rights licensing brief. Prior versions of Windows, including Windows 8.1, have limited support when running on new processors and chipsets from manufacturers like Intel, AMD, NVidia, and Qualcomm. For more information, please see Microsoft Lifecycle Policy. A device may not be able to run prior versions of Windows if the device hardware is incompatible, lacks current drivers, or is otherwise outside of the original equipment manufacturer’s (OEM) support period.

When a Windows operating system (OS) reaches the end of its lifecycle or is no longer supported, does that mean new programs will not run on that OS?

Once a Microsoft operating system (OS) reaches the end of support, customers will no longer receive security updates. The OS may still work with programs and hardware after the sale or support of the operating system has been discontinued. However, the possibility increases that new programs and hardware will not be performant on an older OS. This frequently occurs because the manufacturers of new hardware and software make product-design decisions that take advantage of the increased functionality and features in newer operating systems. These manufacturers may decide to discontinue support of their products on older operating systems as appropriate.

Windows 10

What is the servicing timeline for a version (feature update) of Windows 10?

New versions of Windows 10 (also called feature updates) will be released twice a year for Windows 10 via the Semi-Annual Channel. Customers should always install the latest version before the current version reaches end of servicing to remain supported by Microsoft.

As of September 6, 2018, we have evolved our servicing timeline for customers who need more time to test and deploy Windows 10 feature updates. Supported versions will be serviced via monthly quality updates.

¹Home edition does not support the deferral of feature updates and will therefore typically receive a new version of Windows 10 prior to the end-of-servicing date shown.

What are the requirements for servicing and updating Windows 10 Semi-Annual Channels?

To receive monthly quality updates, customers must be on a supported version of Windows 10. Go here for support dates.

Windows 10 quality updates are cumulative, with each update built upon the quality updates preceding it.

What are my installation options for Windows updates?

Windows Embedded Compact 13

It is highly recommended that customers install the latest feature update to stay up to date with the latest security updates, as well as to continue receiving future feature updates, with less impact on IT processes and infrastructure.

To help reduce the burden on network bandwidth, Microsoft designed two different update types: Full and Express¹.

If needed, customers may defer semi-annual Feature Updates via Settings > Windows Update > Advanced options or via an organization's device management policies.

On devices that do not defer the installation of feature updates, the subsequent Semi-Annual Channel version of Windows 10 may be automatically offered and installed prior to the end date. Update deferral is not available for all versions of Windows 10². Please see Windows as a Service (WaaS) for information on release channels and the Windows 10 release information page for additional update details.

Not all features in a feature update will be available on all devices. Similarly, a device may not be able to receive updates if the device hardware is incompatible, lacks current drivers, lacks sufficient storage space, or is otherwise outside the original equipment manufacturer’s (OEM) support period. For more information on compatibility, review the Windows 10 System Requirements as well as the Windows Processor Requirements.

Update availability may vary by country, region, network connectivity, mobile operator (e.g., for cellular-capable devices), or hardware capabilities (including, e.g., free disk space).

¹As of April 9th, 2019 Delta Updates are no longer be available. To learn more, go here.

²Windows 10 Home does not support the deferral of feature updates and will therefore typically receive a new version of Windows 10 prior to the end-of-service date shown.

What happened to the End of Mainstream Support date for Windows 10 listings on the Lifecycle Product Search page?

In the Windows as a Service (WaaS) model, the concept of Mainstream Support does not apply to Semi-Annual Channels, as each Semi-Annual Channel will be serviced (receive monthly quality updates) for a limited time. Customers are required to move to a supported version (feature update) to continue to receive monthly quality updates with security and non-security fixes.

What are the requirements for servicing and updating the Windows 10 Long-Term Servicing Channel (LTSC)?

The Long-Term Servicing Channel (LTSC) is designed to be used only for specialized devices - for example, those that control medical equipment or automated teller machines (ATMs).

To receive monthly quality updates, customers must be on a supported version of Windows 10. Go here for support dates.

See Overview of Windows as a Service (WaaS) for more information on release channels and the Windows 10 release info page for additional update details.

Windows Server

What are the requirements for servicing and updating Windows Server 2016 (LTSC) and Windows Server (Semi-Annual Channel)?

To receive monthly quality updates, customers must be on a supported version of Windows Server. Go here for support dates.

Updates are cumulative, with each update built upon the updates that preceded it.

What is the Lifecycle Policy for Windows Server Update Services (WSUS)?

Previously a standalone product, Windows Server Update Services (WSUS) became a component of the Windows Server operating system beginning with Windows Server 2012. A component is defined as a set of files or features that are included with a Microsoft product, whether it is shipped with the product, included in a product service pack or update, or later made available as a web download for the product. As a component, WSUS follows the Lifecycle Policy for the product on which it is installed – Windows Server (the parent product).

Windows 8.1

What is the Lifecycle Policy for Windows 8.1?

Windows 8.1 reached the end of Mainstream Support on January 9, 2018, and will reach end of Extended Support on January 10, 2023. With the general availability of Windows 8.1, customers on Windows 8 had until January 12, 2016, to move to Windows 8.1 to remain supported.

Why were Windows 8 customers required to move to Windows 8.1 two years after the general availability?

Historically, Microsoft has taken a similar support approach related to service packs. The place where we dwell 3rd edition pdf download. When a Windows service pack is released, Microsoft provides customers 24 months of support for the prior service pack or original release. Unlike service packs that are typically a collection of fixes, Windows 8.1 has new features and enhancements, and was designed to give customers the ability to deploy this update similar to service packs. Therefore we are applying the service pack policy to Windows 8.1.

Windows 8.1 does not change any hardware requirements compared with Windows 8 and existing Windows Store apps will work with Windows 8.1. Business customers who had Software Assurance licensing received Windows 8.1 as a free update.

Windows Embedded

How does the end of support for Windows XP impact Windows Embedded products?

Windows Compact Embedded

Windows Embedded products have their own distinct lifecycles, based on when the product was released and made generally available. It is important for businesses to understand the support implications for these products to ensure that systems remain up-to-date and secure. The following Windows Embedded products are based on Windows XP:

• Windows XP Professional for Embedded Systems. This product is identical to Windows XP, and Extended Support ended on April 8, 2014.

• Windows XP Embedded Service Pack 3 (SP3). This is the original toolkit and componentized version of Windows XP. It was originally released in 2002, and Extended Support ended on January 12, 2016.

• Windows Embedded for Point of Service SP3. This product is for use in point of sale devices. It's built from Windows XP Embedded. It was originally released in 2005, and Extended Support ended on April 12, 2016.

• Windows Embedded Standard 2009. This product is an updated release of the toolkit and componentized version of Windows XP. It was originally released in 2008, and Extended Support ended on January 8, 2019.

• Windows Embedded POSReady 2009. This product for point of sale devices reflects the updates available in Windows Embedded Standard 2009. It was originally released on 2009, and extended support ended on April 9, 2019.

Why does support for Windows XP Professional for Embedded Systems end with Windows XP?

Windows XP Professional for Embedded Systems is a specially licensed version of Windows XP Professional for industry devices, delivering the full features and functionality of Windows XP. Given this relationship, both operating systems followed the same release schedule and share the same timeline.

Why was Windows XP Embedded be supported for two years longer than Windows XP Professional for Embedded Systems?

Windows XP Embedded is a modular form of Windows XP, with additional functionality to support the needs of industry devices. It was released separately from Windows XP and provides a separate support lifecycle to address the unique needs of industry devices. Devices running Windows XP Embedded reached end of support in 2016.

What is the Lifecycle Policy for Windows Embedded 8.1 products?

Windows Embedded 8.1 falls under the same lifecycle policy as Windows Embedded 8 with support ending 7/11/2023. Customers have 24 months to move to Windows Embedded 8.1 to remain supported. This applies to Windows Embedded 8 Industry Enterprise and Industry Pro.

What is the difference in the Extended Support phase for Windows Embedded products versus regular Windows products?

The type of support provided in the Extended Support phase is consistent across all products. Critical security updates are made available for products until the published Extended Support end date. This allows businesses to ensure that they are up to date in protection against security attacks. For Embedded products, these updates will continue to be made available through the usual channels of MyOEM, Windows Embedded Developer Update (WEDU) and Microsoft OEM Online (MOO), as well as through Microsoft Update for the point of sale systems.

Windows Silicon Policy

What is the Windows policy for silicon support?

Windows products will be supported for security, reliability, and compatibility on the latest silicon available at the time of release. This includes previous silicon generations still in support by the Original Equipment Manufacturer (OEM).

What is the Windows Lifecycle policy for Intel's sixth generation of processors (also known as Skylake) released in late 2015?

Windows 7 and 8.1 Devices

Windows Embedded Compact 7 Download

Supported Skylake devices will receive applicable Windows security updates through the end of support. These systems should be upgraded to Windows 10 to continue receiving support after the period ends. Search here to see your product's end of support dates.

Windows Embedded 7, 8, and 8.1

Skylake devices running Windows Embedded 7, 8, and 8.1 will be supported according to the lifecycle support policy for those products. During this supported period, these systems should be upgraded to Windows 10 to continue receiving support after the period ends. There is no supported device list for Windows Embedded.

Windows Server

The Windows Server platform is supported on certified or logoed hardware as listed in the Windows Server Catalog. Today, you can browse the catalog and find hardware that meets or exceeds our minimum server hardware requirements and has been successfully certified for supported Windows Server products. For Windows Server, the policy consists of five years of mainstream support followed by five years of extended support. This lifecycle impacts the timeframe for which new devices and systems can be certified. We allow new systems to be submitted for certification up to the point when the OS transitions to extended support.

Where can I learn more?

To identify what generation of processor you have, see Intel's page on processor numbers. To see if your processor supports Windows 10, see Intel's Product Specification page. Go here to learn more about the latest processor requirements for all Windows products. To find your Windows product end of support date, search the Product Lifecycle site.

Windows RT

What is the Lifecycle Policy for Windows RT?

Microsoft will make software updates, including security updates, available for Windows RT. Search here for your specific product and its corresponding Lifecycle Policy.

What is the Lifecycle policy for Microsoft Office Home and Student 2013 RT, the version of Office available on Windows RT?

Microsoft Office Home and Student 2013 RT has the same lifecycle policy as Windows RT.

How long will Microsoft support device hardware that runs Windows RT?

Please refer to hardware warranties for more information. More details can be found in the Hardware FAQ.

Windows Mobile

What is the Lifecycle Policy for Windows Mobile?

Go here to learn about the Lifecycle Policy for Windows Mobile.

Change Log

^{October 2020 edits
UPDATED the Windows 8.1 section.}

1 Introduction

This article discusses the important tips for Compact 2013 BSP porting.

2 Things that are changed in Compact 2013

• Compiler is updated to new version.
• C Runtime library is updated to latest version.
• Assembler uses ARM thumb 2 instruction set.
• Removal of old ARM SOC code in platformcommon.

3 Things that are not changed in Compact 2013

• BSP Structure – Directory structure is same as WEC 7
• Build System – Directory structure of resulting sysgen’ed files is at same location as windows embedded compact 7.
• OAL Interface – Almost all functions/variables in OAL interface are unchanged.
• Kernel Memory and Organization – Same memory mode and multiprocessor support as WEC 7

4 New Features in Compact 2013

In this section let’s see new features which are newly added in Compact 2013

• You can develop applications and OS for compact 2013 using latest visual studio versions 2012 and 2013. Latest visual studio has updated IDE UI and few more additional features.
• ARM compiler is updated to new version and C runtime libraries also updated to the latest version.
• WEC 2013 networking stack performance is improved and network miniport driver performance also improved.
• Compact 2013 catalog items are all aligned properly. Few catalog items are merged together and some new items are all added.
  • Some catalog items are removed in compact 2013. Most highlighted feature which is removed are Internet Explorer, Remote desktop protocol (RDP), Active Sync and Windows 95 default shell.
• For Native application development, C runtime library’s like Active Template Library (ATL), Standard Template Library (STL) and Microsoft Foundation Class (MFC) are updated to support latest version.
• For Managed application development, .NET framework is updated to version 3.9 from 3.5.
• Compact 2013 supports only THUMB2 mode instruction set. To generate thumb2 assembly code compiler updated to version C++ and assembler supports new version of ARM Embedded- Application Binary Interface (EABI).
• Compact 2013 has snapshot boot feature. It significantly reduces the time that is required for your device to boot by saving the state of your device to persistent storage and then restoring that state when the device reboots
• It support XAML and Expression blend feature to develop rich UI based application

5 Compact 7 to Compact 2013 Porting

Make sure your target BSP is built successfully without any errors in WEC7. You have to copy your target BSP from WINCE700Platform<BSP Name> folder to WINCE800Platform<BSP Name> location.

The following sections explains what should be taken care while porting Compact 2013 BSP from Compact 7 BSP.

5.1 C Runtime Libraries

The first step in porting WEC7 BSP to WEC2013, need do following changes in WEC2013 BSP.

• h renamed to CeTypes.h – simple approach to address this changes is to create Types.h file under {bsp}SRCINC and include the CeTypes.h in that file.
• lib renamed to bootcrt.lib – Have to use new lib name in boot loader and OALEXE sources file.
• lib splits into two lib’s “coredll.lib” and “msvcrt.lib”.It now contains the C runtime API’s

Standard library functions are now updated to secure function – It means function argument require size field for destination buffers.

5.2 ARM Data Alignment

In WEC 2013 ARM code, we may encounter data alignment error (i.e. alignment fault error).The ARM compiler assumes unaligned access handled in hardware but this is not the case for uncached memory access.

Alignment error will not encounter generally because /QRunaligned -flag is set when compile OS and it will generate code for accessing unaligned memory. The memcpy and memory handle unaligned access.

Example for alignment error: CPU generates data alignment fault for the below give code even when unaligned access enabled.

To avoid data alignment fault, developer should take care of alignment of structure when writing code.
Unaligned access in Boot loader:
o If MMU is not activated, all the memory access is treated as uncached.
o In Boot loader code MMU is not enabled and kernel is not used. Unaligned data access should be taken care by developer. Otherwise often will face data alignment fault exception
o Need to enable unaligned support in boot loader startup code to avoid data fault error.
o Enable unaligned support
 Clearing A bit, bit 1 of CP15 register 1.
 Setting U bit, bit 22 of CP15 register 1
Always verify alignment when accessing memory typically face a problem when accessing unaligned structure passed from hardware.
5.3 ARM Stack Alignment
When working on assembly code in WEC2013 you should keep in mind about stack alignment and keep the stack aligned as four byte boundary or eight byte boundary.

Macros such as LEAF_ENTRY and LEAF_END must be matched but many arm assembly files have LEAF_ENTRY and ENTRY_END macros on assembler function.

Difference between LEAF_ and NESTED_ macros
o LEAF_ macros are used for routines that don’t call other routines
o NESTED_ macros are used for routines that call other routines
Use PROLOG_STACK_ALLOC for allocating space on stack and use PROLOG_PUSH and EPILOG_POP to save and restore registers as show in below example.

To know more details about the macro’s definition’s refer the link
In all the assembly files (.s) of WEC2013, you have to change ENTRY_END macro as LEAF_END macro.

Figure 1. Macro example

Windows Embedded Compact 2013 Update

Need to add RODATAAREA macro in the OAL startup code located at SRCOALOALLIB folder.

Figure 2. RODATAAREA macro example

5.4 ARM Thumb2 Code Changes
o Compact 2013 support only ARMV7 THUMB2 mode.
o Thumb2 mode does not support reset and exception handler.
o CPU must be in THUMB2 mode before running any WEC 2013 code.
o ARM assembly code and THUMB2 assembly code should be in separate ASM files.

For more details about ARM Thumb2 porting considerations, Please see the below article.

PC arithmetic operation are not supported in THUMB2 mode instructions. So assembler will through an error “pre UAL syntax not allowed” frequently. Need to change few instruction to THUMB2 UAL syntax. Please see the below blog posts for more details.

5.5 Fixing Start Up code of Initial Boot loaders

Windows Embedded Compact 2013 Queen Tree Pictures

There are some size constrained binaries specifically pre boot loaders such as XLDR/IPL are loaded by processor boot ROM from NAND/SD card to a small size SRAM and this will load the Eboot to DDR and jump to Eboot. Entry point of the boot loader is expected to be the very first instruction for some processor or a set of predefined data that can be understandable by the boot rom of the processor is expected to be at very beginning of the boot loader. Normally STARTUPTEXT Macro is used to place the required code in the very beginning in Windows CE but there are some changes in this macro on WEC2013 due to these there are some changes has to be done in our code to keep the required instruction/data to be in the first location of the binary. Please see the below blogs for more details.

Windows Embedded Compact 2013 – Understanding STARTUPTEXT macro – Part 1

Windows Embedded Compact 2013 – Understanding STARTUPTEXT macro – Part 2

5.6 Replace DLLENTRY MACRO as DLLMAIN

In WEC2013, DLLENTRY macro is renamed as DLLMAIN. So change the DLL entry point in driver as DLL main and in .def file DllEntry import/export as DllMain.

For example, the following change is required in sources file of drivers.

DLLENTRY=_DllMainCRTStartUp

Co-author: Suresh Madhu, Microsoft Certified Technology Specialist