Licensing Requirements and Guidelines (Windows Embedded Standard 2009)


The following information provides guidance on licensing Windows Embedded Standard tools for developing your devices and licensing Windows Embedded Standard run-time images for distribution with your devices. This topic is informational and is provided as a convenience. If there is any conflict between this information and the licenses for Windows Embedded Standard or run-time images, the terms of the licenses will apply.

The licensing process for Windows Embedded Standard involves:

  • Purchasing a Windows Embedded Standard license to start building your device image.
  • Purchasing a Windows Embedded Standard Run-time License for each device that you will sell.

To create a customized Windows Embedded Standard image, you must first purchase a license for Windows Embedded Standard, which contains Windows Embedded Studio - the development tools necessary to build your image. Each Windows Embedded Standard Toolkit License allows you to install one copy of Windows Embedded Studio for Windows Embedded Standard development tools, and one copy of the component database. With a single Windows Embedded Standard Toolkit License, you can install these on the same computer, or you can install development tools on one computer, and component database on another computer. In a team environment, you must purchase an additional Windows Embedded Standard Toolkit License for each computer on which you install Windows Embedded Studio development tools - that is one toolkit license for each computer you use for developing or building images.

A run-time operating system license is required in order to sell devices that contain the customized Windows Embedded Standard image. Windows Embedded Standard run-time image licenses can be ordered in single units. To reproduce and distribute Windows Embedded Standard, you must acquire a Windows Embedded Standard run-time image license for each computing device or system that incorporates the Windows Embedded Standard operating system. Each Windows Embedded Standard run-time image license includes a serialized PID number and a Certificate of Authenticity (COA) sticker. A valid PID number is necessary to generate a target operating system image for distribution. A Certificate of Authenticity sticker must be attached directly to each device or system that incorporates the Windows Embedded Standard operating system. If the PID number is not valid, or you do not specify a PID, Windows Embedded Standard will not generate a distributable image when you build a configuration. Instead, it will create a 120 day evaluation-only version of your run-time image.

An embedded system is any computer system or computing device that performs a dedicated function or is designed for use with a specific embedded software application. Embedded systems may use a ROM-based operating system or they may use a disk-based system, like a PC. An embedded system cannot be used as a commercially viable substitute for multipurpose computers or devices. This limits the use of office automation/personal computing functions (e-mail, word processing, spreadsheets, database, network browsing, scheduling, and personal finance) permitted with the particular embedded licensed product.

Windows Embedded Standard is licensed for devices that perform Office Automation and Personal Computing Functions only to the extent that the Office Automation and Personal Computing Functions: (i) directly support the operation of, and are an integral part of, the Embedded Application (defined below); and (ii) operate only when used with the Embedded Application (that is, the Office Automation and Personal Computing Functions shall only permit creation, play, display, or communication of content that is directly related to the commercial or industrial processes or tasks that the device is specifically designed to address).

An Embedded Application means industry or task-specific software programs and/or functionality that provide the primary functionality of the device and which offer significant functionality in addition to Windows Embedded Standard.

For more information, see your License Agreement on the Windows Embedded Standard disc, and Run-Time Image Licensing in the Windows Embedded Standard Studio Help.

Community Additions