DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 957579 - Last Review: August 31, 2012 - Revision: 5.1

Support for Windows Vista Service Pack 1 (SP1) ends on July 12, 2011. To continue receiving security updates for Windows, make sure you're running Windows Vista with Service Pack 2 (SP2). For more information, refer to this Microsoft web page: Support is ending for some versions of Windows (http://windows.microsoft.com/en-us/windows/help/end-support-windows-xp-sp2-windows-vista-without-service-packs) .

On This Page

INTRODUCTION

This Knowledge Base article contains details about the scenarios that use DNS Devolution functionality that are affected by this update. Windows administrators and support professionals should review this document to determine whether their computing environments are vulnerable to the behavior that is addressed by this update and to make sure that DNS names are successfully resolved after they install this update.

More information

Definitions

Collapse this tableExpand this table
TermDefinition
Fully qualified domain name (FQDN)A FQDN is the complete domain name for a specific computer, or host, on the Internet. An example is host.contoso.com.
Domain Name System (DNS)The DNS is an Internet standard that translates host names to IP addresses.
Primary DNS Suffix (PDS)PDS is the domain name that appears to the right of the hostname in a fully qualified hostname. Computers register host records in this DNS zone.
Disjoint namespaceBy default, the primary DNS suffix part of a computer's FQDN is the same as the name of the Active Directory domain where the computer account is located. If the PDS is different, then the client is said to be in a disjoint namespace. For more information, visit the following Microsoft Web page:
http://technet.microsoft.com/en-us/library/cc773264.aspx (http://technet.microsoft.com/en-us/library/cc773264.aspx)
Forest root domain (FRD)The FRD is the parent, "top," or first domain in an Active Directory forest. The initial domain in an Active Directory tree. For more information, visit the following Microsoft Web page:
http://technet.microsoft.com/en-us/library/cc757391.aspx (http://technet.microsoft.com/en-us/library/cc757391.aspx)
Single label domainA single label domain is a DNS domain name that consists of a single label such as "CONTOSO." Unlike typical Active Directory domain names, they cannot be registered by using an Internet registrar. Additional configuration is required to support a single label domain namespace. For more information, visit the following Microsoft Web page:
http://support.microsoft.com/kb/300684 (http://support.microsoft.com/kb/300684)
Connection specific DNS suffixA connection specific DNS suffix is a DNS suffix that is specific to a connecting adapter (modem, network adapter, and so on) on a computer. The connection specific DNS suffix is usually assigned by a Dynamic Host Configuration Protocol (DHCP) server that leases an IP address to that adapter. It can also be set manually by using the Advanced TCP/IP settings dialog box. For more information, visit the following Microsoft Web page:
http://technet.microsoft.com/en-us/library/cc959322.aspx (http://technet.microsoft.com/en-us/library/cc959322.aspx)
This can also be set by using Group Policy.
DNS devolutionDNS devolution is the process by which the resolver on a DNS client resolves queries for hostnames by appending a name such as "corp.microsoft.com" to a host name. If this query fails, the appended a name is devolved by one label and the new query is sent by appending only "microsoft.com."
Devolution levelThe devolution level can be defined as the minimum number of labels to be appended for a DNS query during DNS devolution. This update gives administrators the ability to control this value. The organizational boundary should define the minimum number of labels to be appended, and therefore, the devolution level. For example, if the organization boundary for an enterprise named "contoso" is "contoso.co.us," the devolution level should be 3. Generally, the FRD is the organization boundary.
Active Directory The Active Directory directory service stores information about objects on a network and makes this information available to users and network administrators.

Current overview of DNS devolution

DNS devolution is the process that is used by Windows computers that have not been configured with DNS suffix search lists to resolve DNS queries for single-label hostnames. Specifically, the resolver submits a DNS query for a hostname that it has been asked to resolve, and then concatenates the hostname to the local computer's primary DNS suffix. If that query is not successfully resolved, the query is iteratively retried by removing the left-most part of the remaining primary DNS suffix name until the query is either resolved, or the resolvers organizational boundary is reached. Devolution is a Windows DNS client feature.

This behavior of DNS devolution effectively enforces an organizational boundary at the second level of the domain. For example, in an Active Directory domain that has the FRD "contoso.com," "contoso" is the organizational boundary and at the second level.

The resolver on Windows clients does not rely on devolution to resolve non-fully-qualified DNS names if either of the following is true:
  • A DNS suffix search list is configured. The suffix search list may be configured manually or by using Group Policy (expand Computer Configuration, expand Administrative Templates, expand Network, and then click DNS Client). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    294785  (http://support.microsoft.com/kb/294785/ ) New group policies for DNS in Windows Server 2003
  • The append parent suffixes of the primary DNS suffix check box is not selected on the DNS tab in the Advanced TCP/IP Settings dialog box of the Internet Protocol (TCP/IP) component.
For more information about DNS devolution, visit the following Microsoft TechNet Web page:
http://technet.microsoft.com/en-us/library/bb727009.aspx (http://technet.microsoft.com/en-us/library/bb727009.aspx)

Changes to DNS devolution

This update to the DNS client introduces the concept of a "configurable devolution level," which provides detailed control of the label where devolution will terminate. Before this update is installed, Windows clients were hard-coded to use a two-label organizational boundary. Effectively, devolution level provides an administrator with detailed control to determine the organizational boundary of an Active Directory domain for clients that try to resolve resources within the domain.

The devolution levels for a Windows client that is joined to an Active Directory domain that has the FRDs "contoso.com" and "contoso.co.us" are 2 and 3 respectively.

Managing devolution

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756  (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
By default, devolution is switched on for single label hostnames when a suffix search list is not defined. The devolution can be controlled, or switched on or off explicitly, either by manually by changing a registry entry or by using Group Policy. To manually change this setting by editing the registry, add a DWORD value that is named UseDomainNameDevolution to the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
To add this registry entry, follow these steps:
  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then click the following subkey in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
  3. On the Edit menu, point to New, and then click DWORD Value.
  4. Type UseDomainNameDevolution for the name of the DWORD value, and then press ENTER.
  5. Right-click UseDomainNameDevolution, and then click Modify.
  6. In the Value data box, type 1 to enable DNS devolution, and then click OK.

    Note A value of 0 indicates that devolution is disabled.
  7. Exit Registry Editor.
When you change this setting by using Group Policy, a DWORD value that is named UseDomainNameDevolution is added to the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient\
To locate the policy in the Group Policy editor, expand Computer Configuration, expand Administrative Templates, expand Network, expand DNS Client, and then double-click Primary DNS suffix Devolution.

Setting the devolution level

The devolution level should be set to a value of 2 or higher, depending on the organizational boundary:
  • A value of 2 or higher, for example, a value of 3, makes sure that a minimum of 3 labels of primary DNS suffix are appended during devolution.
  • A value of 2 makes sure that the behavior is the same as it was before the installation of the update.
A table is presented later that shows the devolution behavior with different registry value combinations.

For Windows 2000, the devolution level can be set manually only by adding a DWORD value that is named DomainNameDevolutionLevel to the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
For Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 operating systems, the devolution level can be set manually by making changes to the registry or by using Group Policy.
  • To manually change this setting by editing the registry, add a DWORD value that is named DomainNameDevolutionLevel to the following registry subkey:
    HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\Dnscache\Parameters
  • To change this setting by using Group Policy, open the "Primary DNS Suffix Devolution Level" entry in the following location:
    Computer Configuration/Administrative Templates/Network/DNS Client
    "Primary DNS Suffix Devolution Level" is a new policy that is introduced by this feature to define the devolution level that is appropriate to the domain, site, organizational unit, or computer. The policy stores the level in the DomainNameDevolutionLevel DWORD entry that is located in the following subkey in the registry:
    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\WindowsNT\DNSClient\
  • Devolution settings can be pushed over a domain by using Group Policy. For more information about how to edit and apply Group Policy, visit the following Microsoft Web page:
    http://technet.microsoft.com/en-us/library/bb742376.aspx (http://technet.microsoft.com/en-us/library/bb742376.aspx)
Notes about how to set devolution level
  • The devolution level should match the organization boundary for both of the following reasons:
    • Make sure that devolved queries remain inside the organization.
    • Make sure that all domains that were previously available through devolution are still available.
  • A setting of value 2 for devolution level means that the behavior is the same as it was before the installation of the update.
  • Clients to which this Group Policy setting is being applied must be updated with update 957579 for the Group Policy setting to be effective.
  • For more information about pushing scripts through Group Policy, visit the following Microsoft Web page:
    http://technet.microsoft.com/en-us/library/bb742499.aspx (http://technet.microsoft.com/en-us/library/bb742499.aspx)
  • Group Policy for the devolution level is not supported in Windows Server 2000 or in Windows NT 4. To set the key manually, Domain Administrators can write scripts that are run on the domain joined clients.
  • If the local registry entry and the Group Policy are set on a computer, the Group Policy will take precedence.
  • The default behavior of the update on installation is to automatically determine the devolution level. The logic for this is discussed in the next section.

Devolution behavior

The following matrix explains devolution behavior and selection of the devolution level based on the following registry keys.
Collapse this tableExpand this table
Enable devolution (UseDomainNameDevolution)Devolution level (DomainNameDevolutionLevel)Behavior
0 (The devolution feature is disabled.)Any valueDevolution is set to off. The client only appends the primary DNS suffix and connection specific suffixes. It will not devolve the primary DNS suffix.
1 (The devolution feature is enabled.)1Devolution to level 1 is not supported. Therefore, it is switched off.
1 (The devolution feature is enabled.)Values 2 through 50Devolution is turned on, and devolution level is set to the value specified between 2 and 50.
The key does not exist. (By default, the devolution feature is turned on.)1Devolution is turned off.
The key does not exist. (By default, the devolution feature is turned on.)Values 2 through 50Devolution is turned on, and devolution level is set to the value specified between 2 and 50.
The key does not exist. (By default, the devolution feature is turned on.)Neither the local key nor the Group Policy key exists. Devolution level is set to 2.

Devolution level behavior across platforms with and without the update

Collapse this tableExpand this table
PlatformsUpdate InstalledDevolution LevelConfigurable
Windows NT 4, Windows 2000 Service Pack 4, Windows XP Service Pack 2, Windows XP Service Pack 3, Windows Server 2003 Service Pack 2, Windows Vista, Windows Server 2008, Windows Vista Service Pack 1, and Windows Server 2008 Service Pack 1No2No
Windows Vista Service Pack 2 and Windows Server 2008 SP2No2Yes
Windows NT 4, Windows 2000 Service Pack 4,Windows XP Service Pack 2, Windows XP Service Pack 3, Windows Server 2003 Service Pack 2, Windows Vista, Windows Server 2008, Windows Vista Service Pack 1, Vista Service Pack 2, and Windows Server 2008 Service Pack 2YesAutomaticYes
Windows 7NoAutomaticYes
The default behavior of the update on installation is to automatically determine the devolution level. The logic for this behavior is discussed in the next section.

Automatic determination of the devolution level

If the devolution level registry entries that are listed earlier do not exist, the computer will automatically determine the devolution level by using the following process:
  1. First, the computer will determine the FRD of the computer locally. No network queries are used in this operation.
  2. If the FRD is obtained, it is analyzed for the following conditions:
    • The devolution level will be set to 2 if the number of labels in the forest root domain is 1. That is, it is a single label domain.
    • The devolution level is set to the number of labels in the forest root domain if the PDS is a trailing subset of (ends with) the forest root domain.
      • Examples of trailing DNS suffixes for contoso.com and contoso.co.us are corp.contoso.com and corp.contoso.co.us.
      • Examples that are not trailing suffixes for contoso.com and contoso.co.us are corp.contoso.net and corp.contoso.co.au.
    • Devolution will not be performed if the primary DNS suffix is not a trailing subset of the FRD or a disjoint name scenario.

Default behavior

The following is the default behavior for devolution on a client computer after the DNS devolution update is installed on the computer:
  • When the Suffix Search List is enabled on the computer
    DNS devolution has no effect (disabled) when the Suffix Search List is enabled on the computer. There is no change in behavior after the update is installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    275553  (http://support.microsoft.com/kb/275553/ ) How to configure a domain suffix search list on the Domain Name System clients
  • When the name of the domain to which the client is joined to is a single label
    • Devolution level is set as 2 if the FRD is single labeled and the PDS is a trailing subset of the FRD.
    • Devolution level is turned off if the FRD is single labeled and the primary DNS suffix is not a trailing subset of the FRD.

  • When the computer is in a disjoint namespace
    On domain joined computers, DNS devolution depends on the FRD and PDS combinations as depicted in the following table. If FRD is completely disjointed with PDS, devolution is turned off.
The following table summarizes the behavior before and after this update is installed in some hypothetical situations. In this table, the column label FRD represents the forest root domain and the column label PDS represents the Primary DNS Suffix. The cells of the table show Devolution Level Before Update / Devolution Level After Update.
Collapse this tableExpand this table
PDSFRDFRDFRDFRD
Contoso (single label)Contoso.comContoso.co.nzAsiapac.contoso.com
Contoso.com2/OFF2/22/OFF (Disjoint)2/OFF (disjoint)
Contoso.co.nz2/OFF2/OFF (disjoint)2/32/OFF (disjoint)
America.Contoso.co.nz2/OFF2/OFF (disjoint)2/32/OFF (disjoint)
nz (single label)No devolution because PDS is one label only. 2/OFF (contoso.com does not end with nz)2/2 (contoso.co.nz ends with nz)2/OFF (asiapac.contoso.com does not end with nz)
Potential issues because of changes to the earlier behavior, and possible resolutions for these issues, are discussed in the next section.

Resolution for potential issues

This update brings a change to the default DNS devolution behavior when devolution is enabled on the computer. After you install this update, the devolution level is dynamically calculated. Therefore, there might be scenarios that could result in name resolution failures for names that used to resolve immediately.

Administrators of affected networks can resolve this issue in three ways:
  • Manually configure the devolution level limit to a value appropriate for the specific domain name
    In this configuration, DNS will devolve to the administrator-specified level instead of using the level based on FRD.
    For example:
    • On a computer without the update, with devolution enabled:
      If the FRD is Contoso.corp.com and the PDS is America.Contoso.corp.com, an unsuccessful query for "wpad" would eventually lead to a query for wpad.corp.com, which could be valid for the given organization.
    • " On a computer with the update, the query for wpad would stop at wpad.contoso.corp.com. This may break name resolutions that rely on wpad.corp.com. To work around this issue, an administrator could set the devolution level on the computers as appropriate. For more information, see the "Setting the devolution level" section.
  • Create a DNS suffix search list
    In this configuration, when a DNS suffix search list is configured, DNS will try the suffixes in the list. Administrators can make sure that domain of all the servers that are accessed through devolution before is in the suffix search list. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
    275553  (http://support.microsoft.com/kb/275553/ ) How to configure a domain suffix search list on the Domain Name System clients
  • Relocate the network resource to the same FRD as the computer that is trying to access it

Frequently asked questions

  1. Who should deploy this update?

    Answer: For more information about should deploy this update, visit the following Microsoft Web page to see the explanation in the Microsoft Advisory 971888:
    http://www.microsoft.com/technet/security/advisory/971888.mspx (http://www.microsoft.com/technet/security/advisory/971888.mspx)
  2. Why is this not a bulletin?

    Answer: Devolution is a critical behavior for customers who have clients in a child namespace and resources in the parent namespace. This update causes a change in this behavior. This update may cause a problem accessing certain resources for some enterprises. Network administrators are advised to carefully understand the change and then deploy the update in a manner that makes sure that both namespaces are safe and operational.
  3. What is the recommended way to install the update?

    Answer: This depends on the enterprise network configuration. For organizations where all resources are accessed within the FRD, the update can be rolled out, as-is, to all computers. The following are examples:
    • The FRD is contoso.co.us, and the organization boundary is also contoso.co.us. In this scenario, the update can be rolled out as-is.
    • The FRD is ad.contoso.co.us, and the organization boundary is contoso.co.us. That is, there are some resources such as mail.contoso.co.us, and these resources are accessed by using devolution. In this scenario, an administrator can install the update in one computer, set the Group Policy setting for all to use devolution level of 3, and then roll out the update. For more information, see the "Resolution for potential issues" section.
  4. Is there a related security advisory?

    Answer: Yes. For more information, visit the following Microsoft Web page:
    http://www.microsoft.com/technet/security/advisory/971888.mspx (http://www.microsoft.com/technet/security/advisory/971888.mspx)
  5. Is there a way to set (force) the devolution level on the computer regardless of the FRD name and the primary domain suffix?

    Answer: For more information, see the "Resolution for potential issues" section.
  6. Do I have to update my DNS servers?

    Answer: Yes. The DNS client component is affected and must be treated independently from any DNS server issue if the computer is also a DNS server.
  7. Do I have to restart the computer or DNS client service every time that the devolution level is manually changed in the registry or set through group or local policies?

    Answer: No. There are listeners for these registry changes. DNS is notified when the value changes. Therefore, a system or service restart is not required.
  8. How does the behavior change in single label domain FRD scenarios?

    Answer: By design, if the number of labels in the FRD is less than 2, the devolution level will be 2. This is the same as the level that was being used before the update is installed.
  9. What about devolution level precedence? Knowing that there are two different registry locations that define the devolution level, depending on whether the setting was made locally on the computer by using the registry or by an administrator who used Group Policy, what is the order of precedence for the following two registry entries?

    Registry entry 1: Set by manually editing the registry
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DnsCache\Parameters\DomainNameDevolutionLevel

    Registry entry 2: Set by using Group Policy
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient\DomainNameDevolutionLevel


    Answer: Registry entry 2 takes precedence, and it overrides registry entry 1. If the local registry entry and the Group Policy are set on a computer, the Group Policy will take precedence.
  10. Does an administrator-specified devolution level that is set by using Group Policy or by manually editing the registry work for both joined and non-joined computers?

    Answer: Yes, the settings also work for non-domain joined computers.
  11. After installation of the update, is the FRD name read from the local computer, or is there a lookup query waiting for a domain controller?

    Answer: This is a local operation.

DOWNLOAD INFORMATION

The following files are available for download from the Microsoft Download Center:

For all supported 32-bit editions of Windows Vista

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/C/4/2/C42679E3-17ED-4977-9888-774CEA04452B/Windows6.0-KB957579-x86.msu)

For all supported x64-based editions of Windows Vista

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/8/9/D/89D12468-76F9-4D75-A106-3FF13201B77E/Windows6.0-KB957579-x64.msu)

For all supported 32-bit editions of Windows Server 2008

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/3/A/C/3ACA33F4-F92F-4C60-89A4-3BA350FA2246/Windows6.0-KB957579-x86.msu)

For all supported x64-based editions of Windows Server 2008

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/C/D/2/CD2C82B9-E49C-4BF1-98FF-E8C790282992/Windows6.0-KB957579-x64.msu)

For all supported Itanium-based editions of Windows Server 2008

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/F/D/5/FD58F4B7-C123-48B5-99BD-5316B164F1FF/Windows6.0-KB957579-ia64.msu)

For all supported 32-bit editions of Windows XP

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/0/B/8/0B82251F-F4AC-49AA-90C5-17CC1B2836C5/WindowsXP-KB957579-x86-ENU.exe)

For all supported x64-based editions of Windows XP

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/9/C/F/9CF5151C-E35C-4CA7-B217-2693411FC702/WindowsServer2003.WindowsXP-KB957579-x64-ENU.exe)

For all supported x64-based editions of Windows Server 2003

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/8/3/F/83F3E764-CB47-41C4-87AF-AACFFBACFCE3/WindowsServer2003.WindowsXP-KB957579-x64-ENU.exe )

For all supported 32-bit editions of Windows Server 2003

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/C/F/0/CF08D43D-3CB5-4D9A-96DA-9C9DA0F95CFE/WindowsServer2003-KB957579-x86-ENU.exe)

For all supported Itanium-based editions of Windows Server 2003

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/9/5/E/95EFC211-5BA4-4420-BBF6-417F6B1DC80D/WindowsServer2003-KB957579-ia64-ENU.exe)

For all supported editions of Windows 2000

Collapse this imageExpand this image
Download
Download the package now. (http://download.microsoft.com/download/F/A/B/FABF6F45-9939-4952-9E82-0BFB24B2075F/Windows2000-KB957579-x86-ENU.EXE)

Release Date: June 9, 2009

For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591  (http://support.microsoft.com/kb/119591/ ) How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

How to determine whether you are running a 32-bit or a 64-bit edition of Windows

If you are not sure which version of Windows that you are running or whether it is a 32-bit version or 64-bit version, open System Information (Msinfo32.exe), and review the value that is listed for System Type. To do this, follow these steps:
  1. Click Start, and then click Run.
  2. Type msinfo32.exe, and then press ENTER.
  3. In the System Information window, review the value for System Type.
    • For 32-bit editions of Windows, the System Type value is x86-based PC.
    • For 64-bit editions of Windows, the System Type value is x64-based PC.
For more information about how to determine whether you are running a 32-bit or 64-bit edition of Windows, click the following article number to view the article in the Microsoft Knowledge Base:
827218  (http://support.microsoft.com/kb/827218/ ) How to determine whether your computer is running a 32-bit version or a 64-bit version of the Windows operating system

FILE INFORMATION

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). The dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time (DST) bias. Additionally, the dates and times may change when you perform certain operations on the files.

Windows 2000 file information

For all supported editions of Microsoft Windows 2000 Service Pack 4

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Afd.sys5.0.2195.7204119,15217-Oct-200810:38x86
Dnsapi.dll5.0.2195.7280139,02420-Apr-200920:30x86
Dnsrslvr.dll5.0.2195.728098,06420-Apr-200920:30x86
Msafd.dll5.0.2195.7158105,74420-Apr-200920:30x86
Tcpip.sys5.0.2195.7162320,52818-Jun-200822:35x86

Windows XP and Windows Server 2003 file information


  • The files that apply to a specific milestone (RTM, SPn) and service branch (QFE, GDR) are noted in the "SP requirement" and "Service branch" columns.
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes.
  • In addition to the files that are listed in these tables, this software update also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.

For all supported x86-based versions of Windows XP

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
6to4svc.dll5.1.2600.2975100,35216-Aug-200611:58x86SP2SP2GDR
Afd.sys5.1.2600.3463138,36816-Oct-200814:35x86SP2SP2GDR
Dnsapi.dll5.1.2600.3557150,52820-Apr-200917:41x86SP2SP2GDR
Dnsrslvr.dll5.1.2600.355745,56820-Apr-200917:41x86SP2SP2GDR
Mswsock.dll5.1.2600.3394245,24820-Jun-200815:38x86SP2SP2GDR
System.admNot Applicable1,750,61418-Apr-200905:07Not ApplicableSP2SP2GDR
Tcpip.sys5.1.2600.3394360,32020-Jun-200810:45x86SP2SP2GDR
Tcpip6.sys5.1.2600.3394225,92021-Jun-200823:22x86SP2SP2GDR
6to4svc.dll5.1.2600.2975100,35216-Aug-200612:08x86SP2SP2QFE
Afd.sys5.1.2600.3463138,36816-Oct-200814:48x86SP2SP2QFE
Dnsapi.dll5.1.2600.3557149,50420-Apr-200917:29x86SP2SP2QFE
Dnsrslvr.dll5.1.2600.355745,56821-Apr-200918:29x86SP2SP2QFE
Mswsock.dll5.1.2600.3394245,24820-Jun-200815:49x86SP2SP2QFE
System.admNot Applicable1,752,13218-Apr-200905:04Not ApplicableSP2SP2QFE
Tcpip.sys5.1.2600.3394360,96020-Jun-200810:44x86SP2SP2QFE
Tcpip6.sys5.1.2600.3394225,92020-Jun-200809:32x86SP2SP2QFE
Afd.sys5.1.2600.5695138,49616-Oct-200814:43x86SP3SP3GDR
Dnsapi.dll5.1.2600.5797149,50420-Apr-200917:17x86SP3SP3GDR
Dnsrslvr.dll5.1.2600.579745,56820-Apr-200917:17x86SP3SP3GDR
Mswsock.dll5.1.2600.5625245,24820-Jun-200816:02x86SP3SP3GDR
System.admNot Applicable1,752,13218-Apr-200905:04Not ApplicableSP3SP3GDR
Tcpip.sys5.1.2600.5625361,60020-Jun-200811:51x86SP3SP3GDR
Tcpip6.sys5.1.2600.5625225,85620-Jun-200811:08x86SP3SP3GDR
Afd.sys5.1.2600.5695138,49616-Oct-200815:07x86SP3SP3QFE
Dnsapi.dll5.1.2600.5797149,50420-Apr-200917:06x86SP3SP3QFE
Dnsrslvr.dll5.1.2600.579745,56820-Apr-200917:06x86SP3SP3QFE
Mswsock.dll5.1.2600.5625245,24820-Jun-200817:43x86SP3SP3QFE
System.admNot Applicable1,752,13218-Apr-200905:04Not ApplicableSP3SP3QFE
Tcpip.sys5.1.2600.5625361,60020-Jun-200811:59x86SP3SP3QFE
Tcpip6.sys5.1.2600.5625225,85620-Jun-200811:16x86SP3SP3QFE

For all supported x64-based versions of Windows Server 2003 and of Windows XP Professional x64 edition

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Afd.sys5.2.3790.4392291,84030-Apr-200920:57x64SP2SP2GDR
Dnsapi.dll5.2.3790.4498308,22430-Apr-200920:57x64SP2SP2GDR
Dnsrslvr.dll5.2.3790.449879,36030-Apr-200920:57x64SP2SP2GDR
Mswsock.dll5.2.3790.4318492,54430-Apr-200920:57x64SP2SP2GDR
System.admNot Applicable1,772,18430-Apr-200920:57Not ApplicableSP2SP2GDR
Tcpip.sys5.2.3790.4318768,51230-Apr-200920:57x64SP2SP2GDR
Tcpip6.sys5.2.3790.4318375,68030-Apr-200920:57x64SP2SP2GDR
Wdnsapi.dll5.2.3790.4498161,79230-Apr-200920:57x86SP2SP2GDR\WOW
Wdnsrslvr.dll5.2.3790.449845,56830-Apr-200920:57x86SP2SP2GDR\WOW
Wmswsock.dll5.2.3790.4318233,47230-Apr-200920:57x86SP2SP2GDR\WOW
Afd.sys5.2.3790.4392292,35230-Apr-200920:50x64SP2SP2QFE
Dnsapi.dll5.2.3790.4498308,73630-Apr-200920:50x64SP2SP2QFE
Dnsrslvr.dll5.2.3790.449879,36030-Apr-200920:50x64SP2SP2QFE
Mswsock.dll5.2.3790.4318493,05630-Apr-200920:50x64SP2SP2QFE
System.admNot Applicable1,772,18430-Apr-200920:50Not ApplicableSP2SP2QFE
Tcpip.sys5.2.3790.4318784,89630-Apr-200920:50x64SP2SP2QFE
Tcpip6.sys5.2.3790.4318375,80830-Apr-200920:50x64SP2SP2QFE
Wdnsapi.dll5.2.3790.4498161,79230-Apr-200920:50x86SP2SP2QFE\WOW
Wdnsrslvr.dll5.2.3790.449845,56830-Apr-200920:50x86SP2SP2QFE\WOW
Wmswsock.dll5.2.3790.4318234,49630-Apr-200920:50x86SP2SP2QFE\WOW

For all supported x86-based versions of Windows Server 2003

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Afd.sys5.2.3790.4392150,52816-Oct-200815:46x86SP2SP2GDR
Dnsapi.dll5.2.3790.4498161,79220-Apr-200918:38x86SP2SP2GDR
Dnsrslvr.dll5.2.3790.449845,56820-Apr-200918:38x86SP2SP2GDR
Mswsock.dll5.2.3790.4318256,00020-Jun-200818:32x86SP2SP2GDR
System.admNot Applicable1,772,18418-Apr-200904:52Not ApplicableSP2SP2GDR
Tcpip.sys5.2.3790.4318384,00020-Jun-200814:22x86SP2SP2GDR
Tcpip6.sys5.2.3790.4318234,36820-Jun-200813:55Not ApplicableSP2SP2GDR
Afd.sys5.2.3790.4392150,52816-Oct-200816:03x86SP2SP2QFE
Dnsapi.dll5.2.3790.4498161,79220-Apr-200918:30x86SP2SP2QFE
Dnsrslvr.dll5.2.3790.449845,56820-Apr-200918:30x86SP2SP2QFE
Mswsock.dll5.2.3790.4318257,02420-Jun-200819:01x86SP2SP2QFE
System.admNot Applicable1,772,18418-Apr-200904:52Not ApplicableSP2SP2QFE
Tcpip.sys5.2.3790.4318390,65620-Jun-200811:01x86SP2SP2QFE
Tcpip6.sys5.2.3790.4318234,49620-Jun-200810:19Not ApplicableSP2SP2QFE

For all supported IA-64-based versions of Windows Server 2003

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Afd.sys5.2.3790.4392583,68030-Apr-200920:54IA-64SP2SP2GDR
Dnsapi.dll5.2.3790.4498442,36830-Apr-200920:54IA-64SP2SP2GDR
Dnsrslvr.dll5.2.3790.4498129,02430-Apr-200920:54IA-64SP2SP2GDR
Mswsock.dll5.2.3790.4318785,40830-Apr-200920:54IA-64SP2SP2GDR
System.admNot Applicable1,772,18430-Apr-200920:54Not ApplicableSP2SP2GDR
Tcpip.sys5.2.3790.43181,287,16830-Apr-200920:54IA-64SP2SP2GDR
Tcpip6.sys5.2.3790.4318763,77630-Apr-200920:54Not ApplicableSP2SP2GDR
Wdnsapi.dll5.2.3790.4498161,79230-Apr-200920:54x86SP2SP2GDR\WOW
Wdnsrslvr.dll5.2.3790.449845,56830-Apr-200920:54x86SP2SP2GDR\WOW
Wmswsock.dll5.2.3790.4318233,47230-Apr-200920:54x86SP2SP2GDR\WOW
Afd.sys5.2.3790.4392584,19230-Apr-200920:50IA-64SP2SP2QFE
Dnsapi.dll5.2.3790.4498442,36830-Apr-200920:50IA-64SP2SP2QFE
Dnsrslvr.dll5.2.3790.4498129,02430-Apr-200920:50IA-64SP2SP2QFE
Mswsock.dll5.2.3790.4318789,50430-Apr-200920:50IA-64SP2SP2QFE
System.admNot Applicable1,772,18430-Apr-200920:50Not ApplicableSP2SP2QFE
Tcpip.sys5.2.3790.43181,310,20830-Apr-200920:50IA-64SP2SP2QFE
Tcpip6.sys5.2.3790.4318764,41630-Apr-200920:50Not ApplicableSP2SP2QFE
Wdnsapi.dll5.2.3790.4498161,79230-Apr-200920:50x86SP2SP2QFE\WOW
Wdnsrslvr.dll5.2.3790.449845,56830-Apr-200920:50x86SP2SP2QFE\WOW
Wmswsock.dll5.2.3790.4318234,49630-Apr-200920:50x86SP2SP2QFE\WOW

Windows Vista and Windows Server 2008 file information
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductMilestoneService branch
    6.0.6000. 16xxxWindows VistaRTMGDR
    6.0.6000. 20xxxWindows VistaRTMLDR
    6.0.6001. 18xxxWindows Vista SP1 and Windows Server 2008 SP1SP1GDR
    6.0.6001. 22xxxWindows Vista SP1 and Windows Server 2008 SP1SP1LDR
    6.0.6002. 18xxxWindows Vista SP2 and Windows Server 2008 SP2SP2GDR
    6.0.6002. 22xxxWindows Vista SP2 and Windows Server 2008 SP2SP2LDR
  • Service Pack 1 is integrated into the original release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000. xxxxxx version number.
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Dnsclient.admlNot Applicable37,55404-May-200915:50Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200916:03Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200915:50Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200913:05Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200915:50Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200913:01Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200915:56Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200915:51Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200913:05Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200915:50Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200916:03Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200916:03Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200913:04Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200913:04Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200915:50Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200916:05Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200916:05Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200915:56Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200916:03Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200915:51Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200916:03Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200916:05Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200913:04Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200913:04Not Applicable
Dnsclient.admlNot Applicable37,55404-May-200915:24Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200915:29Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200915:24Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:36Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200915:24Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:34Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200915:20Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200915:24Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:36Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200915:23Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200915:29Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200915:29Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:35Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:35Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200915:24Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200915:29Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200915:29Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200915:20Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200915:29Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200915:24Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200915:29Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200915:29Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:35Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:35Not Applicable
Dnsclient.admlNot Applicable37,55404-May-200916:14Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200916:15Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200916:16Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:43Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200916:16Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:33Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200916:05Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200916:14Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:43Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200916:14Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200916:15Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200916:05Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:45Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:44Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200916:16Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200916:15Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200916:15Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200916:05Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200916:15Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200916:05Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200916:15Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200916:15Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:44Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:44Not Applicable
Dnsclient.admlNot Applicable37,55404-May-200916:19Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200916:38Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200916:22Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:37Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200916:22Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:28Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200916:02Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200916:19Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:37Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200916:19Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200916:36Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200916:02Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:49Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:49Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200916:25Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200916:36Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200916:36Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200916:02Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200916:36Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200916:02Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200916:36Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200916:36Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:48Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:48Not Applicable
Dnsclient.admlNot Applicable37,55404-May-200915:10Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200915:30Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200915:10Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:26Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200915:11Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:19Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200915:28Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200915:11Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:27Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200915:10Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200915:30Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200915:28Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:44Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:44Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200915:11Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200915:30Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200915:30Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200915:28Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200915:30Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200915:28Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200915:30Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200915:30Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:44Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:44Not Applicable
Dnsclient.admlNot Applicable37,55404-May-200918:12Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200918:45Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200918:14Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:36Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200918:14Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:26Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200918:34Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200918:14Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:36Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200918:12Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200918:45Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200918:34Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:50Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:50Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200918:12Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200918:45Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200918:45Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200918:34Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200918:45Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200918:34Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200918:45Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200918:45Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:50Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:50Not Applicable
Dnsapi.dll6.0.6000.16857164,35204-May-200912:42x86
Dnscacheugc.exe6.0.6000.1685724,57604-May-200910:25x86
Dnsrslvr.dll6.0.6000.1685783,96804-May-200912:42x86
Dnsapi.dll6.0.6000.21052164,86404-May-200912:16x86
Dnscacheugc.exe6.0.6000.2105224,57604-May-200910:13x86
Dnsrslvr.dll6.0.6000.2105284,48004-May-200912:16x86
Dnsapi.dll6.0.6001.18255167,42404-May-200912:23x86
Dnscacheugc.exe6.0.6001.1825525,08804-May-200910:11x86
Dnsrslvr.dll6.0.6001.1825586,52804-May-200912:23x86
Dnsapi.dll6.0.6001.22425167,93604-May-200912:17x86
Dnscacheugc.exe6.0.6001.2242525,08804-May-200910:18x86
Dnsrslvr.dll6.0.6001.2242586,52804-May-200912:17x86
Dnsapi.dll6.0.6002.18031168,44804-May-200912:08x86
Dnscacheugc.exe6.0.6002.1803125,08804-May-200909:59x86
Dnsrslvr.dll6.0.6002.1803186,52804-May-200912:08x86
Dnsapi.dll6.0.6002.22128168,44804-May-200912:18x86
Dnscacheugc.exe6.0.6002.2212825,08804-May-200910:06x86
Dnsrslvr.dll6.0.6002.2212886,52804-May-200912:18x86
Dnsclient.admxNot Applicable10,29001-Apr-200915:55Not Applicable
Dnsclient.admxNot Applicable10,29001-Apr-200915:55Not Applicable
Dnsclient.admxNot Applicable10,29027-Mar-200908:23Not Applicable
Dnsclient.admxNot Applicable10,29001-Apr-200918:54Not Applicable
Dnsclient.admxNot Applicable10,29003-Apr-200920:36Not Applicable
Dnsclient.admxNot Applicable10,29003-Apr-200920:41Not Applicable

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Dnsclient.admlNot Applicable37,55404-May-200916:48Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200917:07Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200916:48Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200913:08Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200916:49Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200913:06Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200916:41Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200916:48Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200913:08Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200916:49Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200917:08Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200917:07Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200913:11Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200913:06Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200916:48Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200917:07Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200917:07Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200916:43Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200917:07Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200916:49Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200917:08Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200917:07Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200913:06Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200913:06Not Applicable
Dnsclient.admlNot Applicable37,55404-May-200916:01Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200916:02Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200916:01Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200913:03Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200916:01Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200913:02Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200915:56Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200916:01Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200913:03Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200916:01Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200916:02Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200916:02Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200913:06Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200913:07Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200916:01Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200916:02Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200916:02Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200915:56Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200916:02Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200916:01Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200916:02Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200916:02Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200913:02Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200913:02Not Applicable
Dnsclient.admlNot Applicable37,55404-May-200917:18Not Applicable
Dnsclient.admlNot Applicable29,02905-May-200919:28Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200917:18Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200913:16Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200917:20Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200913:15Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200917:09Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200917:20Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200913:16Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200917:18Not Applicable
Dnsclient.admlNot Applicable30,67405-May-200919:28Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200917:09Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200913:29Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200913:22Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200917:20Not Applicable
Dnsclient.admlNot Applicable28,91205-May-200919:28Not Applicable
Dnsclient.admlNot Applicable31,16805-May-200919:29Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200917:09Not Applicable
Dnsclient.admlNot Applicable29,15405-May-200919:28Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200917:09Not Applicable
Dnsclient.admlNot Applicable26,69405-May-200919:28Not Applicable
Dnsclient.admlNot Applicable27,43805-May-200919:28Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200913:22Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200913:22Not Applicable
Dnsclient.admlNot Applicable37,55405-May-200917:49Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200917:16Not Applicable
Dnsclient.admlNot Applicable27,89205-May-200917:52Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:52Not Applicable
Dnsclient.admlNot Applicable51,85805-May-200917:52Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:49Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200917:03Not Applicable
Dnsclient.admlNot Applicable27,74505-May-200917:51Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:52Not Applicable
Dnsclient.admlNot Applicable32,15705-May-200917:49Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200917:16Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200917:03Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200913:05Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200913:02Not Applicable
Dnsclient.admlNot Applicable27,19105-May-200917:51Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200917:16Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200917:16Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200917:03Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200917:16Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200917:03Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200917:16Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200917:16Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200913:02Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200913:02Not Applicable
Dnsclient.admlNot Applicable37,55404-May-200918:49Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200918:41Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200918:50Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:29Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200918:49Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:28Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200918:44Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200918:49Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:30Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200918:49Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200918:40Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200918:44Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:48Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:45Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200918:49Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200918:41Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200918:41Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200918:44Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200918:41Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200918:44Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200918:41Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200918:41Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:45Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:45Not Applicable
Dnsclient.admlNot Applicable37,55404-May-200919:35Not Applicable
Dnsclient.admlNot Applicable29,02904-May-200919:58Not Applicable
Dnsclient.admlNot Applicable27,89204-May-200919:35Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:29Not Applicable
Dnsclient.admlNot Applicable51,85804-May-200919:35Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:26Not Applicable
Dnsclient.admlNot Applicable28,52704-May-200919:36Not Applicable
Dnsclient.admlNot Applicable27,74504-May-200919:35Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:29Not Applicable
Dnsclient.admlNot Applicable32,15704-May-200919:35Not Applicable
Dnsclient.admlNot Applicable30,67404-May-200919:58Not Applicable
Dnsclient.admlNot Applicable28,42004-May-200919:36Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:51Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:48Not Applicable
Dnsclient.admlNot Applicable27,19104-May-200919:35Not Applicable
Dnsclient.admlNot Applicable28,91204-May-200919:58Not Applicable
Dnsclient.admlNot Applicable31,16804-May-200919:58Not Applicable
Dnsclient.admlNot Applicable28,49004-May-200919:36Not Applicable
Dnsclient.admlNot Applicable29,15404-May-200919:58Not Applicable
Dnsclient.admlNot Applicable43,79704-May-200919:37Not Applicable
Dnsclient.admlNot Applicable26,69404-May-200919:58Not Applicable
Dnsclient.admlNot Applicable27,43804-May-200919:58Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:48Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:48Not Applicable
Dnsapi.dll6.0.6000.16857219,13604-May-200912:50x64
Dnscacheugc.exe6.0.6000.1685727,64804-May-200910:41x64
Dnsrslvr.dll6.0.6000.16857114,17604-May-200912:50x64
Dnsapi.dll6.0.6000.21052219,13604-May-200912:46x64
Dnscacheugc.exe6.0.6000.2105227,64804-May-200910:42x64
Dnsrslvr.dll6.0.6000.21052114,68804-May-200912:46x64
Dnsapi.dll6.0.6001.18255221,18404-May-200912:59x64
Dnscacheugc.exe6.0.6001.1825528,67204-May-200910:38x64
Dnsrslvr.dll6.0.6001.18255117,76004-May-200912:59x64
Dnsapi.dll6.0.6001.22425221,69604-May-200912:36x64
Dnscacheugc.exe6.0.6001.2242528,67204-May-200910:41x64
Dnsrslvr.dll6.0.6001.22425117,76004-May-200912:36x64
Dnsapi.dll6.0.6002.18031221,69604-May-200912:16x64
Dnscacheugc.exe6.0.6002.1803128,67204-May-200910:21x64
Dnsrslvr.dll6.0.6002.18031117,76004-May-200912:16x64
Dnsapi.dll6.0.6002.22128221,69604-May-200912:15x64
Dnscacheugc.exe6.0.6002.2212828,67204-May-200910:20x64
Dnsrslvr.dll6.0.6002.22128117,76004-May-200912:15x64
Dnsclient.admxNot Applicable10,29002-Apr-200919:25Not Applicable
Dnsclient.admxNot Applicable10,29001-Apr-200915:56Not Applicable
Dnsclient.admxNot Applicable10,29024-Mar-200909:01Not Applicable
Dnsclient.admxNot Applicable10,29001-Apr-200915:54Not Applicable
Dnsclient.admxNot Applicable10,29003-Apr-200920:39Not Applicable
Dnsclient.admxNot Applicable10,29003-Apr-200920:39Not Applicable
Dnsapi.dll6.0.6000.16857164,35204-May-200912:42x86
Dnscacheugc.exe6.0.6000.1685724,57604-May-200910:25x86
Dnsapi.dll6.0.6000.21052164,86404-May-200912:16x86
Dnscacheugc.exe6.0.6000.2105224,57604-May-200910:13x86
Dnsapi.dll6.0.6001.18255167,42404-May-200912:23x86
Dnscacheugc.exe6.0.6001.1825525,08804-May-200910:11x86
Dnsapi.dll6.0.6001.22425167,93604-May-200912:17x86
Dnscacheugc.exe6.0.6001.2242525,08804-May-200910:18x86
Dnsapi.dll6.0.6002.18031168,44804-May-200912:08x86
Dnscacheugc.exe6.0.6002.1803125,08804-May-200909:59x86
Dnsapi.dll6.0.6002.22128168,44804-May-200912:18x86
Dnscacheugc.exe6.0.6002.2212825,08804-May-200910:06x86

For all supported IA-64-based versions of Windows Server 2008

Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Dnsclient.admlNot Applicable29,52404-May-200912:38Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:37Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:38Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:58Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:53Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:53Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:53Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:39Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:39Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:39Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:50Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:47Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:47Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:47Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:16Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:15Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:17Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:32Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:30Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:30Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:30Not Applicable
Dnsclient.admlNot Applicable29,52404-May-200912:20Not Applicable
Dnsclient.admlNot Applicable25,57904-May-200912:19Not Applicable
Dnsclient.admlNot Applicable30,33204-May-200912:20Not Applicable
Dnsclient.admlNot Applicable33,02604-May-200912:36Not Applicable
Dnsclient.admlNot Applicable28,28904-May-200912:32Not Applicable
Dnsclient.admlNot Applicable23,09604-May-200912:32Not Applicable
Dnsclient.admlNot Applicable23,26904-May-200912:32Not Applicable
Dnsapi.dll6.0.6001.18255430,08004-May-200912:26IA-64
Dnscacheugc.exe6.0.6001.1825560,41604-May-200910:29IA-64
Dnsrslvr.dll6.0.6001.18255223,23204-May-200912:26IA-64
Dnsapi.dll6.0.6001.22425430,08004-May-200912:25IA-64
Dnscacheugc.exe6.0.6001.2242560,41604-May-200910:36IA-64
Dnsrslvr.dll6.0.6001.22425223,23204-May-200912:25IA-64
Dnsapi.dll6.0.6002.18031430,08004-May-200912:03IA-64
Dnscacheugc.exe6.0.6002.1803160,41604-May-200910:14IA-64
Dnsrslvr.dll6.0.6002.18031223,23204-May-200912:03IA-64
Dnsapi.dll6.0.6002.22128430,08004-May-200912:08IA-64
Dnscacheugc.exe6.0.6002.2212860,41604-May-200910:15IA-64
Dnsrslvr.dll6.0.6002.22128223,23204-May-200912:08IA-64
Dnsclient.admxNot Applicable10,29027-Mar-200908:23Not Applicable
Dnsclient.admxNot Applicable10,29001-Apr-200915:54Not Applicable
Dnsclient.admxNot Applicable10,29003-Apr-200920:39Not Applicable
Dnsclient.admxNot Applicable10,29003-Apr-200920:40Not Applicable
Dnsapi.dll6.0.6001.18255167,42404-May-200912:23x86
Dnscacheugc.exe6.0.6001.1825525,08804-May-200910:11x86
Dnsapi.dll6.0.6001.22425167,93604-May-200912:17x86
Dnscacheugc.exe6.0.6001.2242525,08804-May-200910:18x86
Dnsapi.dll6.0.6002.18031168,44804-May-200912:08x86
Dnscacheugc.exe6.0.6002.1803125,08804-May-200909:59x86
Dnsapi.dll6.0.6002.22128168,44804-May-200912:18x86
Dnscacheugc.exe6.0.6002.2212825,08804-May-200910:06x86

Additional file information for Windows Server 2008 and for Windows Vista

For a list of additional files provided within these packages, click the following link:
File tables for KB 957579 - .xls (http://download.microsoft.com/download/6/A/C/6ACC1392-5A94-471F-ACF6-C2B109F4F46C/File%20tables%20for%20KB%20957579%20-%20%20Post-installation%20behavior%20on%20client%20computers%20after%20you%20install%20the%20DNS%20update.xls)

Applies to
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 for Itanium-Based Systems
  • Windows Server 2008 Standard without Hyper-V
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • Windows Web Server 2008
  • Windows Vista Service Pack 1, when used with:
    • Windows Vista Business
    • Windows Vista Enterprise
    • Windows Vista Home Basic
    • Windows Vista Home Premium
    • Windows Vista Starter
    • Windows Vista Ultimate
    • Windows Vista Enterprise 64-bit Edition
    • Windows Vista Home Basic 64-bit Edition
    • Windows Vista Home Premium 64-bit Edition
    • Windows Vista Ultimate 64-bit Edition
    • Windows Vista Business 64-bit Edition
  • Microsoft Windows Server 2003 Service Pack 1, when used with:
    • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
    • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
    • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
    • Microsoft Windows Server 2003, Web Edition
    • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
    • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows Server 2003 Service Pack 2, when used with:
    • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
    • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
    • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
    • Microsoft Windows Server 2003, Web Edition
    • Microsoft Windows Server 2003, Datacenter x64 Edition
    • Microsoft Windows Server 2003, Enterprise x64 Edition
    • Microsoft Windows Server 2003, Standard x64 Edition
    • Microsoft Windows XP Professional x64 Edition
    • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
    • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows XP Service Pack 2, when used with:
    • Microsoft Windows XP Home Edition
    • Microsoft Windows XP Professional
  • Microsoft Windows XP Service Pack 3, when used with:
    • Microsoft Windows XP Home Edition
    • Microsoft Windows XP Professional
  • Microsoft Windows 2000 Service Pack 4, when used with:
    • Microsoft Windows 2000 Advanced Server
    • Microsoft Windows 2000 Professional Edition
    • Microsoft Windows 2000 Server
Keywords: 
atdownload kbbug kbexpertiseinter kbfix kbsecbulletin kbsecurity kbsecvulnerability kbsurveynew kbregistry KB957579
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support