The upgrade from Windows Server 2008 to Windows Server 2008 R2 fails if you have applied some TCP-A and NetDMA settings before the upgrade


You try to upgrade Windows Server 2008 to Windows Server 2008 R2. However, the upgrade process fails, and the following information is logged in the Setup log file:
2009-06-05 22:57:33, Info                  MIG    IPostApply::ApplySuccess for Plugin={ServerPath="%windir%\system32\Migration\netiomig.dll", CLSID={ea51459a-a30d-4a33-b294-0e0163551c75}, ThreadingModel=Apartment} - Working directory: C:\$UPGRADE.~OS\OnlineUpgradeApplyWork\srcworking\agentmgr\CCSIAgent\005A6BFD
2009-06-05 22:57:33, Info TCPIP: Starting application of all settings from registry.
2009-06-05 22:57:33, Warning TCPIP: Instance number 0 does not match the current NSI object description.
2009-06-05 22:57:33, Warning TCPIP: Failed to collect instances of object number 2 from the registry: 0xd.
2009-06-05 22:57:33, Warning TCPIP: Failed to assemble complete list of object instances that should be applied to NSI (0xd). Aborting all TCPIP upgrade.
2009-06-05 22:57:33, Error [0x08038d] MIG Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="%windir%\system32\Migration\netiomig.dll", CLSID={ea51459a-a30d-4a33-b294-0e0163551c75}, ThreadingModel=Apartment}. Error: 0x8007000D
Additionally, some network settings in the registry are reverted to their default values unexpectedly.

This problem occurs if you have applied some TCP-acceleration (TCP-A) and network direct memory access (NetDMA) settings before the upgrade.


A fix that is included in Windows Server 2008 R2 has a defect. This defect prevents certain additional settings from being updated during upgrade. Therefore, after the upgrade fails, the system restores some settings to their default values.


To work around this problem, remove the following settings if you have applied them, and then upgrade to Windows Server 2008 R2:
  • Subkey:
  • Subkey:
After you upgrade to Windows Server 2008 R2, reapply these settings.

More Information

When this problem occurs, the following settings are restored to the default values:

TCP window scaling configurations

netsh interface tcp set global autotuninglevel = <parameter>
netsh interface tcp set heuristics wsh= <parameter>
UDP dynamic port range

netsh interface <ipv4/ipv6> set dynamicport udp <parameters>
Network layer settings
  • Global settings
  • Compartment settings
  • Interface settings
  • Address settings
  • Static neighbor settings
  • Path settings
  • Proxy neighbor settings
  • Route settings
  • Subinterface settings
  • Multicast Forward Entries Settings
netsh interface <ipv4/ipv6> set global <parameter>
Network Driver Interface Specification settings
  • NdisNsiObjectInterfaceInformation
  • NdisNsiObjectNetwork
  • NdisNsiObjectCompartment
  • NdisNsiObjectInterfacePersist
  • NdisNsiObjectInterfaceInformationRaw
Forwarding layer interface settings

netsh interface <ipv4|ipv6> set interface [interface id] forwarding=enabled
Teredo port number

Netsh interface teredo set state clientport = <port>
Teredo remote v4 address

Netsh interface teredo set state server <ipv4>


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

ID do Artigo: 973422 - Última Revisão: 26/01/2010 - Revisão: 1