Release Notes for Microsoft Windows XP Embedded with Service Pack 2


December 2004

Please read this documentation carefully. It includes late-breaking information about Microsoft Windows XP Embedded that became available after the product documentation for Windows XP Embedded was written. The information in this document has precedence over the information included in the online Help installed with the product.

Unless stated otherwise, all information included here applies to this version of Windows XP Embedded.

For the most up-to-date Release Notes, see this Microsoft Web site.


Hardware Requirements

    Development and Target System


    Setup Program

    Database and Repositories

Windows Embedded Studio

    Target Designer

    Component Designer

    Target Analyzer

    Device Update Agent

    Remote Boot Service

Component Issues

    Dependency Issues

    Driver Issues

    Registry Issues

    MUI Issues

    Internet Explorer Issues

    Upgrade Issues

    File Issues

    Terminal Services Issues

    First Boot Agent

Run-Time Logon

.NET Framework 1.1 Service Pack 1 and ASP .NET 1.1 Service Pack1


Hardware Requirements

Development and Target System

  • The system requirements for Windows XP Embedded have changed from those documented on the product box. Use the following disk size requirements to install Windows XP Embedded:
    • Development tools only: 200 megabytes (MB)
    • Development tools and database on the same system: 3.2 gigabytes (GB)
    • Shared component database in a team environment: 3.2 GB
  • Windows XP or Windows 2000 with Service Pack (SP) 2 or later, or Windows Server 2003, is required before you install Windows XP Embedded.

For more information about the hardware requirements, see the Installation Guide, located on the distribution medium, or the Getting Started Guide, which is available on your development system after installation.


Upgrading from either Windows XP Embedded with Service Pack 2 Beta or a release candidate (RC) is not supported.



If you have Windows 2000 SP2 installed, you must install the latest version of the Windows Script Host before you install Windows XP Embedded with SP2. To do this, navigate to the MSDN Web site, and then search for the latest version of this update.

For information about installation and configuration options, see the Installation Guide located on the distribution medium.

During the installation of the Windows SP2 database update, the machine may appear to be hung or stopped. The dialog box displayed may also appear unresponsive. This is normal behavior, and is caused by the sheer volume of data the installer is processing and applying to your database. The entire installation process may take between 15-30 minutes to complete, with significant portions of that time consumed by internal processing.

The ewfapi.lib that is included on the installation media is an incorrect version. The correct version is available as a QFE from

Setup Program

During the Windows Embedded Studio tools and database setup, if you type the run-time product key instead of the tools and database product key, the Setup Wizard will not allow you to continue, even if you later type the correct product key. If this occurs, exit, and then run the Setup Wizard again. Be sure to use the tools and database product key.

Database and Repositories

  • The SP2 database update fails if the Windows Embedded Studio is not installed on the same machine.
  • If you remove Windows Embedded Studio and then try to run database engine setup, you may get the following message: "Setup failed to configure the server. Refer to the server error logs and setup error logs for more information." This message may appear if you removed Windows Embedded and then tried to reinstall the Microsoft SQL Desktop Engine (MSDE). Remove or rename the Data folder, typically found in "C:\Program Files\Microsoft SQL Server\MSSQL\." Then try installing the database engine again.
  • Uninstalling the database will remove all components imported into that database. After reinstalling the Windows XP Embedded database, additional components needed or referenced in an .slx or .sld file must be reimported into the database or these files may not open correctly.
  • You must install repositories on the same computer on which you are planning to install the database.
  • When a network connection is not available, the repository paths must be changed from network shares to local paths. To change the repository paths, use the following procedure:
  1. Exit all Windows Embedded Studio applications.
  2. Exit all Windows Embedded Studio applications.
  3. Run Component Database Manager.
  4. Select the Repositories tab.
  5. For each repository:
    1. Select the repository.
    2. Choose Change Location.
    3. Change the MachineName/ShareName from a network path to a local path.
  6. Verify that the Move repositories to the new location check box is cleared.
  7. Choose OK.
  • Dual installations of the database are not supported, whether on the same or different drives or partitions.

Windows Embedded Studio

  • When adding resource extended properties that are formatted as multistring types, do not exceed 3850 characters in the Value field.

  • If you specify an invalid log file when importing a file using the Import File dialog box, the import fails and the following message appears:

    File import failed due to unspecified error while processing file (<filename>).

    You must cancel the import, and then try again using a valid log file.

Target Designer

  • Run-time images must be placed in the root directory of the boot partition on the device. There must not be any other operating system on the boot partition that could conflict with the Windows XP Embedded image.
  • Some Start menu shortcuts are broken. Links to features, such as Activate Windows, Tour of Windows XP, Imaging, System Information, and CD Player, will not operate correctly because these features are not included in Windows XP Embedded. These links are provided by the Standard Start Menu Shortcuts component. You can disable these in the resources node of that component in Target Designer.
  • After building a configuration, if you manually inspect the run-time hives using RegEdit, you cannot build an image in that folder again until you unload the hives, and then exit and run Target Designer again. Target Designer will display a message that you cannot clear the contents of the destination folder even though the destination folder may be empty.
  • Setting cmiUnjoinDomain = "FALSE" in system cloning in Target Designer does not retain setting on reseal. To work around this issue:
  1. Go to Start and select Run.

  2. In the Run dialog box, enter the following command: \Windows\System32\fbreseal –keepdomain

    See this Microsoft Web site for more details.

  • Running Target Designer on Chinese (PRC), Chinese (Taiwan), or Korean development machines may result in a script error when building a configuration with the Speech API Core component. If this component is required for your configuration, build the configuration from a development machine set for any other language. If the Speech API Core component is not required, you can ignore the error.

  • Some components require the selection of other components that have a visibility as low as 100. To view these additional components, you must lower the visibility in Target Designer to 100 and keep the visibility set to 100 throughout the life of the configuration. This is also true for any other development system that will host these configurations. The following components must be altered as indicated:

    • The Map Network Drive/Network Places Wizard component requires you to manually add the Primitive: MPRUI and Msxml Libraries components.
    • The Terminal Services Web Control Extensions component requires you to manually add the Terminal Services Web Control Core component.
  • If you add a prototype component to a configuration, you will receive a CMI error that the prototype does not contain a valid cmiLangID property and you will not be able to build a run-time image. Prototype components should not be manually added to a configuration with Target Designer.

  • You cannot make copies of components from a configuration and then add multiple instances of that component to the same configuration. To add multiple instances of the same component to a configuration, use either a drag-and-drop operation or double-click the component for each instance you want to create. You can also copy a component instance, including its settings, and then add it to a second configuration if that component does not already exist in the second configuration.

  • If you are using a complex filter, the following error message may appear:

    The CMI encountered the following error: 0x80042335 (-2147212491) A database error occurred within the CMI. 

    To resolve this issue, add the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Embedded\CMI\DBCmdTimeout registry key.

    You can then create the DBCmdTimeoutDWORD and set the value to 300, which is five minutes. If the error occurs again, or if you are using a more complex filter algorithm, you may need to increase the DBCmdTimeout value.

  • If Target Designer displays a script error while shutting down, you can safely ignore the error message.

  • A Text Services framework cannot be configured within Target Designer, but can be managed from Control Panel on the device at run time.

  • To ensure that locale settings are applied to a run-time image, you must use the extra files in Target Designer to add %windir%\system32\Winnls.dll to your configuration.

  • When a dependency check is run, the log file will occasionally truncate the last few characters of the report.

  • Upgrading a configuration enables all previously disabled components. This can cause your run-time image size to increase. To work around this issue:

    1. Find the re-enabled components immediately after the upgrade
    2. Disable these components before running a dependency check to avoid a run-time image size increase.
  • Once the component browser or output panes are undocked, they cannot be docked again by dragging them to their original locations. To dock them, you must double-click their title bar.

  • When browsing a run-time image, you may notice that there is a system identifier associated with all files and folders. This is expected behavior and can be ignored.

  • When the operating system is increasing the pagefile size to allow allocation of more memory, Target Designer may display a message that not enough storage is available to complete this operation. Perform the same operation again after the operating system finishes increasing the pagefile size.

Component Designer

  • If you add file resources using the Add File, Multiple Files, or All Files in Folder option, the effective path of the files will not automatically be converted to directory identifiers (DIRIDs) if the source file location is on a network share, different partition, or separate physical disk. The absolute path of the file is inserted instead of the DIRID and must be manually converted from the absolute paths to the correct DIRID.
  • When importing .inf files to create components, Component Designer may not correctly parse file resources referenced as strings. You must manually author these resources if they are missing after the import completes.

Target Analyzer

  • To produce a starter configuration in Target Designer, the Logical Disk Manager component is added to the configuration. However, it is not critical to boot the system and may be removed to reduce footprint.
  • The Target Analyzer probe file, Tap.exe, may report hardware devices that are no longer in your system. You should manually remove these devices from the configuration before building a run-time image.
  • Target Analyzer does not detect infrared devices. To enable infrared support, add the Built-in Infrared Device component.

Device Update Agent

  • Device Update Agent (DUA) requires that the binary data for REG_BINARY in the update script (.dus) file be in decimal format instead of hexadecimal. When data is exported from the registry, or Win32 API calls are made to query registry values, the data returned is in hexadecimal format. You must convert the hexadecimal-formatted values to decimal in order for DUA to apply the REG_BINARY value.
  • You need to manually include the TCP/IP Networking component so it can poll an HTTP server.
  • Do not leave the Working Directory field blank in the Device Update Agent component settings. Leaving the working directory blank will cause a build error and make DUA not work correctly when the run-time image is booted.
  • Do not set update program (.dup) file attributes to read-only. When DUA attempts to parse a read-only .dup file or parse a .dup file from a read-only local folder, it will fail to execute any commands in the file. If the .dup file is read-only, DUA will also leave behind a copy of the .dup file in the local DUA working directory. DUA can correctly parse .dup files that are stored in a read-only remote share (UNC path).
  • In order to use proxy settings, Proxy Access Type must be set to 3.
  • Selecting the Administrator Service Account causes the DUA service to not start without user intervention. From the run-time image, open the DUA service in Services.msc and manually set the password for the administrator account.
  • DUA deletes the .dup file after consuming it in local polling scenarios. To work around this issue: DUA can correctly parse .dup files that are stored in a read-only remote share (UNC path).
  • Specifying a password causes build errors. If you need a user name and password for polling, use the following procedure:
  1. Type a user name in the User Name field of the Device Update Agent component settings.
  2. Leave the Password field blank.
  3. Set the HKEY_LOCAL_MACHINE\System\ControlSet001\Services\DUAgent\Parameters\Config\Sessions\0000 registry key value as the password for polling. The type should be either REG_SZ or REG_EXPAND_SZ.

Remote Boot Service

  • If a Preboot eXecution Environment (PXE) client attempts to download an image that is too large to run in memory, the following error message is displayed: "Windows could not start due to an error while booting from a RAMDISK. Windows failed to open the RAMDISK image." This error means that the client computer does not have enough RAM for the current RamDisk image to run.

Component Issues

  • Allowing auto-resolve to add Windows Logon to a runtime causes the automatic logon default username to be overwritten.
  • If you configure the Legal Notice text setting in Windows Logon (Standard) component with several lines of text, no scroll bars appear during boot, which prevents the user from reading the entire End-User License Agreement (EULA).
  • Minlogon runtimes fail to system restore.
  • Use the XPePM.exe tool to change the system power state only if you are deploying a minimal kernel-only image. XPePM.exe does not implement all the steps necessary to shut down or standby a Minlogon- or Winlogon-based image. Instead, use such exiting Windows functions as ExitWindows[Ex], InitiateSystemShutdown[Ex], or SetSystemPowerState.
  • The User Interface core component setting cmiShowAccessories can only be set by means of the Advanced button.
  • In the User Interface core component, disabling Show context menu on files and folders causes the Explorer task pane to behave erratically.
  • Changing the following display adapter attributes to a value not normally shown in the configuration list will cause a script error:
    • cmiColorQuality
    • cmiScreenRefresh
  • You may receive an access violation - code c0000005 when issuing the command netsh bridge show adaptors in Windows XP Embedded images.
  • Some component Help topics may include dependencies to end-of-life components. These end-of-life components do not include component Help topics and appear as broken links.

Dependency Issues

  • File sharing requires Windows Firewall and its associated dependencies to be present. So as part of footprint reduction, if you do not go with the default settings when using the Core Networking component and instead configure your image so that it does not bring in Windows Firewall, there is a known issue of the command net start lanmanserver giving error 126 (the specified module could not be found). This is due to the missing dependency on Hnetcfg.dll, which is part of the Windows Firewall component.

  • Adding the Windows Firewall component to your runtime but not including the Windows Firewall Control Panel component may present a user with the RunDLL error "Unable to locate firewall.cpl." You should either add the Windows Firewall Control Panel component to your configuration, or unblock the necessary applications within the Windows Firewall component.

  • Notifications of Bluetooth events like bonding, connection over PAN, and new device, do not appear unless the Tray Icon Add/Remove Support component is added to the runtime and the Show Notifications on Task bar check box is selected in the User Interface Core component settings.

  • Runtimes that include the Microsoft System Management BIOS Driver Installer component are missing a dependency to the WMI Win32 Provider component.

  • If you do not use the El Torito CD Support macro component to build an El Torito configuration, you will have to manually add the CDFS component to your configuration.

  • To change the screen savers on the runtime, include the Display Control Panel component in your configuration.

  • The User Account control panel behaves erratically if Help files are not included in the runtime. To include help files, access the base component's Other Settings section and clear Do not copy help files for this configuration.

  • The Communications Port component is missing dependencies on the Plug and Play Software Device Enumerator and PnP (User-mode) components.

  • Service Control Manager (SCM) component dependencies are missing in some components that require SCM and may not automatically be added to the configuration as part of dependency checking. If this occurs, you should manually add the Service Control Manager (SCM) component.

  • To enable USB printer support, add the Primitive:Win32spl component.

  • The Add Printer Wizard will not work unless the Unidrv.hlp file and all printer-specific .hlp files are present. This also affects Bluetooth printers that are dynamically discovered in the field.



    To reduce the run-time footprint, you will need to adjust your global settings to include Help files, and then clear the Help inclusion option for all unwanted Help in the configuration.

  • For the FBA to bind TCP/IP to a 1394 adapter, you must add the PnP User Mode component.

  • The Home Gateway and Kiosk/Gaming macro components do not contain the Dialer Application component necessary to dial a phone number. You must manually add this component, or you must use a third-party application to enable this feature.

  • The following components are only supported when used with the Windows Logon Standard component:

    • Japanese Input Method Editor (IME) components
    • Utility Manager component accessibility features
    • Default presentation setting for the power policy in the **Computer****component
    • Hotmail through MSN Explorer
  • If your embedded run-time image is based on the Minlogon baseline configuration and you add the System Cloning Tool component, you must also ensure that your configuration includes the Local Security Authority Subsystem (LSASS) and TCP/IP Networking components. To locate the LSASS component in Target Designer, you must first set visibility to 200 or lower.

  • If you add the Local Network Bridge component in your run-time image, add the Connection Manager Runtime component.

  • The route argument (-r) in the NetStat command does not work properly unless you manually add the Route.exe file in your configuration.

  • If you add the Software Installation Group Policy MMC Snap-in component to a configuration, add the NLS: Time Zones component.

  • When adding the Windows XP Explorer User Interface component to a configuration, a dependency check may reveal that it contains a dependency on at least one format utility. You can disregard this dependency.

  • If you add the Remote Registry component to a configuration, add the RPC Remote over Named Pipes component.

  • If you add the RPC over Named Pipes component to a configuration, add the server service.

  • User account pictures in the Users program in Control Panel will not appear unless you add the Windows Picture and Fax Viewer and Images and Media components.

  • The ICM User Interface component requires the Display Control Panel component to enable you to select color profiles at run time.

  • To enable full graphical user interface (GUI) functionality for the Users program in Control Panel, add the Administration Support Tools component in your run-time image.

  • Some .chm files require the Help and Support Services component. If you use one of these files and do not add this component to your configuration, script error messages may appear.

  • If you add the Windows Movie Maker component to a configuration and want to use video recording features, add the DirectX9.0c Macro component.

  • Help files are not available and do not launch when the HTML Help Engine component is added to a configuration unless you manually add the Primitive: Winhelp32 component.

  • Desktop wallpaper preview will not function unless you add the Windows Picture and Fax Viewer component.

  • The Troubleshooters component requires the Help and Support Services component.

  • If you add the NetBIOS Driver component in a configuration, add the PnP (User-mode) component.

  • The ASP.NET 1.1 component is missing a dependency on the IIS Web Server component.

  • Context-sensitive Help in the Windows Explorer shell requires the Primitive: Winhlp32 component.

  • If you add the Error Reporting component to a configuration, add the Terminal Services Macro component.

  • If you add the Serial Input Support component to a configuration, add the Accessibility Control Panel component.

  • If you add the Internet Connection Discovery Client component to a configuration, add Hnetcfg.dll as an extra file.

  • If you add the Microsoft Management Console (MMC) component to a configuration, add the MSXML 3.1 component.

  • If you add the Search Assistant User Interface component, add the MSXML 3.1 component.



    The search pane is not centered correctly because the animated character cannot be rendered on a Windows XP Embedded system. To center the pane, choose Change preferences, and then choose Without an animated screen character.

  • You should always use the Internet Information Services Technologies (IIS) macro component. If you require the Internet Information Services and printer management using Active Server Pages (ASP) components, manually add the Printing (Server/Shared) component to the configuration.



    The System Cloning component prevents the IIS service from running automatically after the cloning process. You must manually run IIS.

  • If you add the HyperTerminal component to a configuration, add the **TAPI 2.2component, and, optionally, the **Phone and Modem Control Panelcomponent.

  • If you add the **Telnet****component to a configuration, add one of the TCP/IP macro components.

  • The **Administration Support Toolscomponent includes a number of tools, all of which will be included in your build. If you require the File Share Management add-in (Shrpubw.exe), manually add the **Computer Browser Servicecomponent.

  • If you experience issues when running the NetView and NetSend commands, add the Computer Browser Service component to your configuration.

Driver Issues

  • If there are third-party drivers in the database but not in a configuration, when you build, the Generic Driver component will throw an error for each file of each component that was not manually added to the configuration, but is in the database. These errors can be safely ignored.

  • Unsigned device drivers are not installed on run-time images. Users trying to install unsigned drivers should contact the hardware vendor to determine if updated signed drivers are available. Otherwise, you can use the Sigverif.exe tool that is included in Windows ME, Windows 2000, and Windows XP Professional to detect unsigned drivers and files. Sigverif.exe allows you to scan specific directories or the entire system for unsigned files and will produce a report of its findings. You can also change the value of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing\Policy to hex:00 so that unsigned drivers will install.

  • If you are using an ATI Rage Mobility Pro video adapter in a configuration, you will find that the ATI Hotkey Poller Service entry that accompanies the ATI Rage Mobility Pro drivers will not run correctly in the run-time image. This causes the video adapter to be incorrectly installed when the run-time image is complete.

    To properly use the service that is supplied in the .inf files for this video adapter, you must first disable the ATI Hotkey Poller service entry in the component resources. During the initial boot of the run-time image, the ATI Hotkey Poller is then installed and runs correctly. This allows you to use the full functionality of the ATI Rage Mobility Driver in the run-time image.

  • Windows Media Player 9.0 does not properly detect Sonic Blue drivers, such as Rio 600, Rio 800, and Nike, in Windows XP Embedded images. They will not appear in the list of supported devices in Windows Media Player 9.0.

  • The Thinkpad Modem and Thinkpad Digital Signal Processor components do not operate properly with drivers in the Windows XP Professional Edition. To resolve this issue, install the driver after the First Boot Agent (FBA) completes and after you reboot the device.

Registry Issues

  • The Windows API - User component is missing the following registry keys that can prevent system beeps: HKEY_CURRENT_USER\Control Panel\Sound\Beep REG_SZ=yes and ExtendedSounds REG_SZ=yes
  • Remote assistance is not enabled by default. The HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Remote Desktop\Policies\fAllowToGetHelp registry value that enables Remote Assistance is overwritten by the Terminal Services core component while FBA is running. To enable Remote Assistance, you must manually set the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Remote Desktop\Policies\fAllowToGetHelp registry value to 1 using the Target Designer tool prior to building your run-time image.
  • Windows Media Player 9.0 components lack support for playback of .avi files that use the Indeo 3 codec. If this capability is required, see the following steps to resolve the issue:
  1. Add ir32_32.dll to Windows\system32

  2. Add the following REG_SZ values to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 registry entry:



  • For the Remote Desktop client to connect to a Windows XP Embedded Terminal Server at high color (24-bit) add the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp registry key.

    The default value must be changed from 3 to 4 in the Terminal Server Remote Desktop component.

MUI Issues

  • In a Japanese run-time, text characters are not displayed properly in full-screen command windows. To work around this issue, add the Full screen video driver for console component to your image.

  • In a non-English runtime, both localized and non-localized folders are created under Documents and Settings. To work around this issue:

    1. Boot into US English so that FBA is performed in English.
    2. Switch languages from the runtime.
  • Input Method Editor (IME) components are not automatically added to your run-time image if you choose Japanese, Korean, or Chinese as your default input language. To enable the appropriate IME functionality, you must manually add the IME components that you want.

  • Runtimes that include the Brazilian Language Support and Regional and Language Options components must be manually set to Portuguese – Brazil in the Regional and Language Options component settings.

  • Runtimes using Finnish, French, German, Norwegian, Polish, or Swedish require QFE 824055 to fix a domain login delay issue.

  • There is no MUI support for .NET Framework 1.1 with NOR, DAN, FIN, ARA, HEB, or GRE.

  • After you have installed HEB & ARA MUI packs, when you open up a configuration that contains the XP SP2 Resource DLL component you will notice an upgradeable icon in front of the component. You need to manually upgrade this particular component in the configuration if you are building images for HEB & ARA.

  • If you change the language in the International Control Panel on your run-time image to a language that is not included on the system, the run-time image will fail to boot. This behavior is apparent on Asian and Tier 3 languages because they use a different class of fonts from Roman-based languages.

  • In run-time images configured for Hebrew or Arabic languages, the icon Internet Options in the Windows Security Center is not displayed. To display the icon, you must update the following registry key after FBA completes:

    Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\Extended Properties\{305CA226-D286-468e-B848-2B2E8E697B74} 2\

    Name: inetcpl.cpl

    Type: REG_SZ

    Value: 3,10

Internet Explorer Issues

  • Internet Explorer supports an Image toolbar with four buttons, one of which opens the My Pictures folder. If you choose the button that opens the My Pictures folder when Internet Explorer is not running, an error results and Internet Explorer is launched. To avoid this issue, while using command shell components, disable the Internet Explorer component property called Enable Picture Toolbar.

  • Running a dependency check on a configuration that includes the Japanese Internet Explorer MUI component unnecessarily includes Outlook Express. You can remove Outlook Express to reduce run-time footprint.

  • You must specify the protocol in cmiIESearchPage field of Internet Explorer settings. When setting the value, specify the protocol using the following format: cmiIESearchPage: =

  • Run-time images that include the command shell using Internet Explorer may receive the following error message when attempting to view images using the Image Viewer toolbar:

    Windows cannot find '/idlist, :2712:1964,D:\Documents'. 

    To resolve this issue, add the Explorer Shell component.

Upgrade Issues

  • If you upgrade Language Support components, they will lose their settings.
  • If you upgrade the User Account component, the User Account component names are changed. Actual account name/user name and any other configurable settings for this component are not changed.

File Issues

  • The Display Control Panel DPI settings in the advanced properties of the Display Control Panel are grayed out. To work around this issue:
    • Copy Font.inf from the repository to the %WINDIR%\INF folder.


    • Add International Control Panel to the configuration.

  • If you add the Oledb Provider for Internet Publishing component in a configuration, run Regsvr32 from Program Files\Common Files\System\OLE DB\Msdaipp.dll at run time.
  • To enable full functionality support of Message Queuing (MSMQ) COM Library and Message Queuing (MSMQ) DCOM Library components, register Mqoa.dll by creating an FBA COM/DLL registration resource or by running the command RegSvr32.exe Mqoa.dll from the command line. Failure to register Mqoa.dll will have an impact on applications using IDispatch, such as Microsoft Visual Basic Scripting Edition (VBScript) programming language and Active Server Pages (ASP).
  • Some components reference Capi20.sys, Serial.vxd, and Dmicall.sys, which do not exist in Windows XP Professional or Windows XP Embedded. Resulting errors can be safely ignored.
  • When accessing Movie Maker Help, an error message appears stating that the Help file cannot be found. This occurs because the Help file was placed in the MUI\1033 folder instead of the MUI\0409 folder.
  • Creating desktop shortcuts to MS-DOS programs is not supported. To resolve this issue, add Apps.inf, which is located in the repository to the Windows/INF folder, to your image. This will allow you to create shortcuts to MS-DOS programs. Shortcuts to MS-DOS programs will then have a generic icon instead of the MS-DOS icon.
  • For direct cable connections to work properly with the Unimodem component, you must move the Rootmdm.sys file from the Windows\System32 (%11%) folder to the Windows\System32\Drivers (%12%) folder in the run-time image or on the target system after booting the run-time image.

Terminal Services Issues

  • The Terminal Services core component has a default setting to allow users to connect remotely to the computer. It should be disabled unless this functionality is needed and all users have strong passwords.
  • The initial attempt to copy folders from the Terminal Services Client to the Terminal Services Remote Desktop fails. Subsequent attempts to copy should operate correctly.
  • For users to connect remotely to a computer, the user account must have a password. Windows Firewall will be configured to allow remote desktop connections to this computer.

First Boot Agent

  • When First Boot Agent (FBA) completes, it will reboot the device without notification. This is expected behavior.

  • A cloning process (that is, SysPrep) fails to restart MSDTC service when other services have started or are starting. In order to restart MSDTC and IIS, enter the following commands after cloning completes:

    • msdtc -install -a
    • msdtc -resetlog
    • iisreset /restart
  • If the runtime is on a partition other than C: and the runtime does not have the file system component for the file system on C: partition, you may receive the following error in the FBALog: "[FBAInstallSecurity] SCE Error: 0x4b8." This error can be safely ignored as it means it was not able to read files on the boot partition.

  • Upon first boot into the runtime, there will be a Windows Product Activation (WPA) error in the Application log of the event log. This is a harmless error and can safely be ignored; it is a one-time occurrence and is not indicative of any WPA problem. It is due to the unique behavior that WPA has on Windows XP Embedded images.

  • The FBA log will show a harmless error if the Performance Counter Configuration component is included in a runtime. The log text is as follows and can be disregarded:

    [FBAApplySecurityStringToRegKey] RegSetKeySecurity Failed!  Error: 0x6
    [FBAReplaceSecurityInRegistry] FBAApplySecurityStringToRegKey(009) #1 Failed!
  • FBA refers to syssetup.inf located at %WINDIR%\INF for installing devices or any DLLs during setup. Even though a component in a runtime might have a DLL/INF registration/installation file set at a particular phase, FBA gives precedence to syssetup.inf and installs the INFs and DLLs specified therein, if any.

  • The following error may appear during FBA:

    [FBALaunch]c:\windows\\framework\v1.1.4322\aspnet_regiis.exe –I –enable (exitcode: 0xc000013a)

    The workaround is to run the following after the machine has booted into the OS and FBA is complete:

    %windir%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis -i -enable

Run-Time Logon

Run-time images are by default created with a single user account with full administrative privileges. The account name is Administrator and the password is blank. You should use Target Designer to set a strong administrator password and can also add one or more additional user accounts. For a password to be strong, it should:

  • Be at least seven characters long. Because of the way passwords are encrypted, the most secure passwords are 7 or 14 characters long.
  • Contain characters from each of the following three groups:
    • Letters (uppercase and lowercase) A, B, C... (and a, b, c...)
    • Numerals 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
    • Symbols (all characters not defined as letters or numerals) ` ~ ! @ # $ % ^ & * ( ) _ + - = { } | [ ] \ : " ; ' < > ? , . /
  • Have at least one symbol character in the second through sixth positions.
  • Be significantly different from prior passwords.
  • Not contain your name or user name.
  • Not be a common word or name.

.NET Framework 1.1 Service Pack 1 and ASP .NET 1.1 Service Pack 1

.NET Framework 1.1 Service Pack 1 and ASP .NET 1.1 Service Pack 1 are contained in the VALUEADD folder on Disk 1 of the installation media. To use them, see the following steps:

  1. Copy the contents of folder '{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}' from VALUEADD\MSFT\PRERELEASE\NETFX1.1SP1\rep into the repository root folder under Windows Embedded Data\Repositories\{67C85615-B0C5-42EA-8B8A-E8AB47DB2B1D}
  2. Using Component Database Manager, import the NETFXV1.1.sld from VALUEADD\MSFT\PRERELEASE\NETFX1.1SP1. Be sure that you clear the Copy repository files to repository root check box before you start the import.

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2004 Microsoft Corporation. All rights reserved.

Active Directory, ClearType, Direct3D, DirectDraw, DirectPlay, DirectX, Microsoft, MS-DOS, MSDN, NetMeeting, Outlook, Visual C++, Visual Studio, Win32, Windows, Windows Media, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

© Microsoft Corporation. All rights reserved.