Microsoft Prerelease Software WinFX Runtime Components (September PDC 2005 Build)


Microsoft Corporation

September 2005

Note   Before installing, you should uninstall (using Add/Remove programs) any earlier version of Microsoft "Avalon," Microsoft "Indigo," or the Microsoft WinFX SDK. You should also uninstall Microsoft Visual Studio 2005 and Microsoft .NET Framework 2.0 releases that are earlier than Beta 2. Be sure to uninstall Microsoft .NET Framework last to ensure a clean uninstall.


System Requirements for Installing WinFX Runtime Components Sept CTP
WinFX Runtime Components: Installation Known Issues
Troubleshooting Steps for Download Errors
Windows Communication Foundation Known Issues
Windows Presentation Foundation Known Issues
Windows Workflow Foundation Known Issues

System Requirements for Installing WinFX Runtime Components Sept CTP

Processor Minimum:
  • 400 megahertz (MHz) Pentium processor


  • 1 gigahertz (GHz) Pentium processor
Operating System WinFX Runtime Components Beta can be installed on any of the following systems:
  • Microsoft Windows 2003 Server Service Pack 1 (SP1)
  • Windows XP SP2
  • Windows Vista PDC Build

Installation of WinFX Runtime Components Sept CTP on the Intel Itanium (IA64) is not supported.

RAM Minimum:
  • 96 megabytes (MB)


  • 256 MB
Hard Disk Up to 500 MB of available space may be required.
CD or DVD Drive Not required.
Display Minimum:
  • 800 x 600, 256 colors


  • 1024 x 768 high color, 32-bit
Mouse Microsoft mouse or compatible pointing device

Performance improvement

Performance improvements have not been tuned for minimum system configurations. Increasing your RAM above the recommended system configuration will increase your performance, specifically when running multiple applications, working with large projects, or doing enterprise-level development.

Installation drive

When you start the WinFX Runtime Components installer, the default installation location is your system drive, which is the drive that boots your system. Please ensure that the required amount of space is available on your system drive.

WinFX Runtime Components: Installation Known Issues

Files left over from older installs are not removed or overwritten by WinFX Runtime Components September CTP.

There was a bug in the November 2004 CTP and March 2005 CTP releases of WinFX Runtime Components, due to which certain shared "Avalon" assemblies were not removed upon uninstall. Moreover, with the September CTP, the setup program does not overwrite existing files. This is by design.

To resolve this issue

  1. Uninstall the previous version of WinFX.
  2. Save the MSI file to a folder on your computer.
  3. Execute the download MSI file, which will run a script to remove the files left over from teh previous installation of WinFX.
  4. Install WinFX September 2005 CTP.

Download failure when downloading and installing WinFX Runtime Components Sept CTP.

The download and installation of a WinFX Runtime Components Beta will intermittently fail.

To resolve this issue

Rerun winfxsetup.exe from the Web site and try the download again. Click here for more troubleshooting information for download errors.

Administrator deployment is not working for WinFX Runtime Components Sept CTP.

Administrator deployment using SMS or Active Directory is not supported for WinFX Runtime Components Beta.

Antivirus applications that are configured to clean the Temp folder will cause setup to fail if setup needs to reboot.

If setup needs to reboot, and the antivirus application is set to clean the Temp directory on launch, necessary setup files will be deleted and setup will fail with a program-not-found error.

To resolve this issue

Before running Visual Studio setup, change your antivirus applications configuration to not clean the Temp folder on launch or reboot. Consult your antivirus documentation for the steps to accomplish this.

Setup does not check disk space when auto-launching after selecting "reboot later."

When reboot later is selected, if the available space on the hard drive is filled beyond the amount of space that is needed by setup, an out-of-space error will occur in setup on reboot.

To resolve this issue

Ensure there is sufficient disk space remaining on the system when rebooting after selecting reboot later if other applications have used a lot of disk space. The required disk space is displayed when you select the location to install the product.

WinFX Runtime Components Sept CTP setup: Launching Maintenance Mode from Add or Remove Programs can take several minutes and might give the appearance that setup has failed.

If you have other processes running when you launch Maintenance Mode, such as virus-scanning software, these processes can slow setup considerably and give the appearance that setup has failed.

To resolve this issue

Be patient. There is no workaround. Setup has not failed.

Microsoft .NET Framework Redistributable 2.0 Beta 2 install fails on a 64-bit machine with error code 25008.

  1. On a Windows 2003 64-bit machine with RTM operating system or SP1 build less than 1184.
  2. Run WinFX Runtime Components Beta install.
  3. Microsoft .NET Framework Redistributable 2.0 Beta 2 setup will fail with error code 25008.

WinFX Runtime Components is not supported on Windows 2003 and Windows 2003 SP1 with build numbers less than 1184 running on 64-bit machines.

To resolve this issue

Install a new operating system (Windows 2003 64-bit with a SP1 build greater than or equal to 1184).

WinFX Redist Setup does not resume after reboot

An application is running that is using the .NET Framework v1.1, for example threadsleep.exe. After starting to install winfxrc.exe, you are presented with a reboot dialog and select "reboot now". After rebooting the following dialog box appears:

WinFX Runtime Components Core Redistributable Beta 2 Setup

The Windows Installer package:


could not be opened.

Choose Retry to try again. Choose Cancel to exit setup.


Retry will not work because, after reboot, the temp folder is gone.

You click Cancel and start a new install of winfxrc.exe.

To resolve this issue:

Install .NET Framework from one of the following locations before running WinFX Setup.

X86 .NET Framework:

X64 .NET Framework:


Manually rerun seutp after the reboot.

Repair from Add/Remove Programs cannot find WinWF_3.0_x86.msi

When trying to repair an installation from Add/Remove Programs WinWF_3.0._x86.msi cannot be found. The WinWF msi is not caching.

To resolve this issue:

Download the standalone Microsoft Workflow Foundation MSI and run it to repair Windows Workflow Foundation. Download locations:

No entries are visible in ARP to repair / uninstall WinFX 3.0 Beta 2 on Vista PDC Build.

You will not see any entries for WinFX Runtime 3.0 Beta2 in Add/Remove Programs on the Vista PDC build. This is hidden for LH integration. However, for the Vista PDC Build, the overall integration is not done.

To resolve this issue:

To repair or uninstall WinFX 3.0 Beta 2 on the Vista PDC Build:

  • On an x86 machine: Run setup.exe from %windir%\Microsoft.NET\Framework\v2.0.05215\WinFX Runtime Components 3.0 Beta 2.
  • On an x64 machine: Run setup.exe from %windir%\Microsoft.NET\Framework\v2.0.50727\WinFX Runtime Components 3.0 Beta 2 x64.

No ARP entry to uninstall Windows Workflow Foundation

You may get the "Please uninstall Windows Workflow Foundation" error when installing WinFX Runtime Components September CTP, but there is no ARP entry for Windows Workflow Foundation to uninstall the product.

To resolve this issue:

Download the standalone Microsoft Workflow Foundation MSI and run it to uninstall Windows Workflow Foundation. Download locations:


For X86 platforms: Run msiexec.exe /x {B644FB52-BB3D-4C43-80EC-57644210536A} in the command-line window to remove Windows Workflow Foundation.

For x64 platforms: Run msiexec.exe /x {9333CA16-67BA-4B3D-BD3E-5CAA39038E56} in the command-line window to remove Windows Workflow Foundation.

Troubleshooting Steps for Download Errors

Background Intelligent Transfer Service (BITS) disabled

This error occurs when the BITS service is disabled, does not exist, has been deleted from the services application, was stopped while download was in progress, or if any service that BITS depends on failed or was deleted. The error message for this problem is "BITS service must be enabled before you start the installation process. Enable the BITS service and run setup again."

To resolve this issue

  1. On the Start menu, click Run.

  2. In the Run Dialog box, type services.msc and then click OK.

  3. In the list of services, right-click Background Intelligent Transfer Service, and then click Properties.

    Note If you do not see Background Intelligent Transfer Service in the list, the service is not installed on your computer. You can download and install BITS from

  4. In the Startup type list, select Manual and then click OK.

If these steps do not resolve the problem, you may need to enable the services that BITS depends on.

To enable dependencies

  1. Follow steps 1-3 listed above.
  2. In the Background Intelligent Transfer Service Properties dialog box**, click the Dependencies** tab.
  3. For each service listed under This service depends on the following system components, follow steps 3 and 4 listed above to enable the service.

Configuration Errors

These errors occur when BITS interfaces are not registered or the registry settings are corrupted.

To resolve this issue

Upgrade to BITS 2.0 from


Repair the BITS service by running the bitsadmin tool from the command prompt:
Bitsadmin /util /repairservice /force

You can download the Bitsadmin tool from;displaylang=en&familyid=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en.

Network Errors

These errors can occur for one or more of the following reasons:

  • Unable to reach download server
  • URL not found on the server
  • Server is overloaded
  • Bad gateway or proxy
  • Network is disconnected
  • Proxy does not support HTTP 1.1

To resolve this issue

Provide correct settings for the proxy server and ensure that your machine is able to correctly resolve the proxy server.


Upgrade to BITS 2.0. You can download BITS 2.0 from;displaylang=en&familyid=49AE8576-9BB9-4126-9761-BA8011FABF38&displaylang=en.

Note To resolve these errors, exit setup, verify that you are connected to the network, and launch setup again.

Disk Errors

These errors occur when the BITS service failed to create or write to a file. Another program, such as chkdsk.exe, might be running and may have locked the disk and prevented BITS from writing to the file.

To resolve this issue

Make sure that no other program (for example, chkdsk.exe) that could lock the disk is running and retry the download.


Restart your computer and then launch setup again. Make sure that you are connected to the Internet.

Proxy Errors

The BITS service failed because of one of the following proxy-related errors:

  • The proxy settings are not valid.
  • The proxy server requires authentication.
  • The computer is not able to resolve the proxy server.

To resolve this issue

Provide correct credentials for the proxy server authentication and restart setup again.


Upgrade the proxy server to support HTTP 1.1 and ensure that the proxy supports implicit credentials (like NTLM). You may need to contact your network administrator.


Bypass the proxy by changing your Internet Explorer proxy settings.

To bypass a proxy server:

  1. In Internet Explorer, click Tools and then click Internet Options.
  2. Click the Connections tab and then click LAN Settings.
  3. Under Proxy server, unselect Use a proxy server for your LAN (these settings will not apply to dial-up or VPN connections) and then click OK.
  4. Click OK again.

If you need further assistance with your proxy server settings, contact your network administrator.

Other Errors

The BITS service does not run in:

  • Safe-boot mode.
  • On Windows 2000 from a remote desktop connection.
  • When setup is installed by a "run as" command.

To resolve this issue

There is no workaround. These scenarios are not supported.

Windows Communication Foundation (WCF) Known Issues

WOW64 configuration incomplete

In the September CTP release, there is a defect in WCF that affects setup on 64 bit systems. WOW configuration may be incomplete on some systems and WOW64 scenarios are not supported. Native 64-bit scenarios are unaffected and should function as expected. This issue will be addressed in future releases.

Anonymous request-reply interoperability affected by missing "Reply-To" headers

In the September CTP release, there is a defect in WCF that results in "Reply-To" sections in message SOAP headers being dropped in anonymous HTTP communication scenarios. This affects interoperability with other messaging platforms in anonymous request-reply scenarios. This issue will be addressed in future releases.

Windows Presentation Foundation (WPF) Known Issues

Building projects that use local references

If you have a XAML file that uses types defined in your project's assemblies, you may run into the following situation:

  1. The project builds fine.
  2. You put some bad code into a .cs or .xaml.cs file.
  3. The code error is caught by CSC during build.
  4. You fix the error, then build again.
  5. The build runs CSC to compile a new .cs file, but doesn't go back and build a .baml file.
  6. The application runs after you hit F5, but stops with a runtime error saying that Window1.baml (or similar) does not exist.

As a workaround, you will need to close all generated code files (for example, .g.cs) and build clean whenever you run into this issue. This problem will be fixed in a future release.

Windows Workflow Foundation Known Issues

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

Please review the following information before installing Windows Workflow Foundation, Beta 1 Release

Software Requirements

Supported operating systems:

  • Windows XP, Service Pack 2 (SP2)
  • Windows XP Professional x64 Edition
  • Windows Server 2003 Standard Edition, Service Pack 1 (SP1)
  • Windows Server 2003 Enterprise Edition, Service Pack 1 (SP1)
  • Windows Server 2003 Web Edition, Service Pack 1 (SP1)
  • Windows Server 2003 Standard x64 Edition
  • Windows Server 2003 Enterprise x64 Edition
  • Windows Server 2003 R2 Standard Edition, Beta 2
  • Windows Server 2003 R2 Enterprise Edition, Beta 2
  • Windows Server 2003 R2 Standard x64 Edition, Beta 2
  • Windows Server 2003 R2 Enterprise Edition, Beta 2
  • Windows Vista, Beta 1

Other software requirements:

  • .NET Framework 2.0 Beta 2

For Microsoft Visual Studio 2005 Extensions for Windows Workflow Foundation only:

  • Microsoft Visual Studio 2005 Beta 2


  • SQL Server 2000 SP3 (required for using durable services)
  • Visual Web Developer (required for creating Visual Basic custom workflow applications)

Hardware requirements

Processor: 800 MHz Pentium III

RAM: 256 MB

Hard Disk Space: 900 MB on system drive, 4.1 GB installation drive

Video: 800 x 600, 256 colors

Release Notes

Workflow cannot use activity defined in the same project

A workflow cannot use a custom activity defined in the same Visual Studio project. The activity should be defined in a separate referenced assembly.

SQL Server backed services do not install properly with SQL2000 SP4 on Vista

SQL Server backend services—SqlTrackingService, SqlStatePersistenceService, and SqlTimerService—will not install properly with SQL2000 SP4 on Vista. You should use SQL 2000 with SP3 for this platform.

No validation failure on updating an atomic scope

If you try to update an atomic scope dynamically by adding an activity, you will not receive a validation error when you compile the workflow, but the update will fail at run time.

Interface selection dialog hides nested interface types

The interface selection dialog in the Visual Studio Extensions for Workflow does not show interface types that are nested within other types.

Parallel Replicators cannot have initializing EventSink

You cannot use an initializing EventSink in parallel instances of a replicator. Use a correlated messaging interface instead, and use an InvokeMethod to initialize the correlation.

Cannot set properties on multiple selected activities

If you select more than one activity containing a given property in Visual Studio Extensions for Workflow, you cannot set properties in the Properties window. You must select each activity separately and set the property on one at a time.

Set registry key to enable free form state machine designer

In order to enable the free form state machine designer, you must add a DWORD value in the registry to HKEYLocalMachine\Software\Microsoft\Windows Workflow Foundation. The name of the DWORD value is "EnableFreeForm", and its value should be 1.

Note that the free form designer is a preview-only feature for this release, and might not be stable.

Generic fields not emitted properly in code

In the Visual Studio Extensions for Workflow, if you enter a field name in the property browser for a given activity, and the activity has a generic type property, when you bind to the field, the generated code will look like this:

public Dictionary dict = new 
System.Collections.Generic.Dictionary<System.String, System.Object>();

It should be:

public Dictionary<string, object> dict = new System.Collections.Generic.Dictionary<System.String, System.Object>();

Do not add activities directly to designers for the code files (*.xoml.cs or *.xoml.vb) in a code-separated workflow

In a code-separated workflow, you should not add activities directly to the Visual Studio design surface for the code (cs/vb) file. Add activities only on the design surface for the .xoml file.

Assembly reference not automatically added for WebService activities

An assembly reference for an interface definition is not added to the project when a custom activity containing a WebService activity is added to a workflow in the Visual Studio Extensions for Workflow. You need to manually include the reference to the interface assembly.

Cannot publish workflow as WebService on machine with only Visual Basic installed

To publish a workflow as a WebService in Visual Studio, Visual C# must be installed.

Need to close and reopen Visual Studio to see changes in custom activity

If you compile a workflow with a custom activity in it, and then make changes to the custom activity, such as adding a property, you will not be able to see the changes until you have closed and reopened Visual Studio.

Nested property bindings not saved correctly

In the Activity Reference dialog within the Visual Studio Extensions for Workflow, you can select a nested property, if the type of an available property has properties of its own.

When you select a nested property such as myProperty.myNestedProperty, the entire reference, in this case "myProperty.myNestedProperty", should be stored in your .cs file or .xoml file.

The reference is not saved property in this release. Instead it will be saved as "myNestedProperty", and you must type in the parent property name manually.

Visual Basic string constants not parsed correctly in Activity Designer

In Visual Basic .NET, code statements that use static fields are not parsed correctly. For example, if you use vbCrLf in a property value in the code file, the value displayed will be incorrect in the Activity Designer.

Cannot promote a While code condition in Visual Basic through Activity Designer

Promoting a While code condition in the Activity Designer will result in an event declared with a delegate type that has a return type, which is not allowed by Visual Basic.

Build failure when changing base type on nested custom activities in Visual Basic

When you change the base type of a nested custom activity in Visual Basic, the change is not managed correctly by the Visual Studio Extensions for Workflow, and you will get a build failure. You can change the inherited class manually in the code file.

Raise event from different thread when implementing communication services

If you want raise a workflow event when implementing communication services, raise the event from a different thread as opposed to raising it directly from the thread of the runtime engine. Otherwise, you will receive an EventDeliveryFailedException and an inner exception stating that potential deadlock has been detected.

Manually update Custom Tool property when adding existing XSD file to workflow project

When adding an existing item of type XML schema (XSD) to your workflow project, manually add the value "WorkflowXSDGenerator" to the Custom Tool property associated with the XSD file. Note that this is not necessary if you are adding a new XML Schema file to your workflow project.

Event handlers must be defined as dependency events

For this release, event handlers must be defined as dependency events, as follows:

public static DependencyProperty myEventEvent = 
DependencyProperty.Register("myEvent", typeof(System.EventHandler), 

public event EventHandler myEvent
        base.AddHandler(myEventEvent, value);
        base.RemoveHandler(myEventEvent, value);

Cannot select overloaded method names on InvokeMethod activity

If you have two or more methods on an InvokeMethod activity with the same name but different parameters, you will be unable to select all of the methods in the dropdown in the Visual Studio Extensions for Windows Workflow. Use unique method names to avoid this problem.

Form data activities not supported in Activity Designer

Form data activities are no longer supported in the Activity Designer.

Cannot publish activity libraries as Web services

You cannot publish an activity library project as a Web service, even though the context menu item is enabled. You can only publish workflows as web services.

Do not use System.Workflow.Activities.CorrelationSet

The System.Workflow.Activities.CorrelationSet class is present in the API, but is no longer used.

Cannot invoke another workflow in same Visual Studio project

A workflow cannot invoke another workflow in the same Visual Studio project; the second workflow will not appear as an option for the InvokeWorkflow.TargetWorkflow value.

Cannot set new breakpoint using F9 in workflow in debug mode

You cannot set a new breakpoint using F9 in a workflow that is in debug mode. Either set breakpoints at design time, or use the New Breakpoint window while in debug mode.

Referenced project not in type browser

If you do not see a referenced project in the type browser, compile the referenced project, remove the reference, and add the reference back in. The assembly will then be visible in the type browser.

WorkflowAborted event not raised

The WorkflowAborted event is not raised as expected when the workflow is aborted.

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, and is the confidential and proprietary information of Microsoft Corporation. It is disclosed pursuant to a non-disclosure agreement between the recipient and Microsoft. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. 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.

© 2005 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows NT, Windows Server, Visual Basic, Visual Studio, and Windows Vista 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.

© 2005 Microsoft Corporation. All rights reserved.