Universally unique identifiers that are returned contain the same seed value in Windows Server 2003

You may experience one of the following symptoms:

• When you call the ExUUIDCreate routine in kernel mode, all the universally unique identifiers (UUID) that are returned by the call may have the same seed value. The seed value is the last twelve characters of the UUID.
• When you use the Uuidgen command-line utility with the –x parameter to force serial UUIDs, all the UUID values that are generated may have the same seed value.

The seed value that is repeated is 505054503030. These 12 characters are the ASCII representation of the seed value PPTP00.

This problem may occur if the Network Driver Interface Specification (NDIS) wide-area network (WAN) miniport drivers do not support the OID_GEN_VENDOR_ID object. The OID_GEN_VENDOR_ID object specifies a three-byte vendor code that is followed by a single byte that the vendor assigns to identify a particular network adaptor. The vendor code that is specified is a vendor code that is registered with the Institute of Electrical and Electronics Engineers, Inc. (IEEE). The IEEE code uniquely identifies the vendor and is the same as the three bytes that appear at the beginning of the network adaptor hardware address. Vendors that do not have an IEEE-registered code are expected to use the value 0xFFFFFF. These vendors are expected to use this value so that the value is correctly interpreted by the UUID creation code. This problem occurs if the value that is returned is 0x00000000 instead of 0xFFFFFFFF. Because the value 0x00000000 is returned, the UUIDs that are generated are not unique.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Windows Server 2003, 32-bit versions

Windows Server 2003, 64-Bit Enterprise Edition

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

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: