Consider the following scenario:

• You run a Windows Filtering Platform (WFP)-based network filtering application on a computer that is running Windows Vista or Windows Server 2008.
• A WPF callout driver is used to pend packet processing by calling the FwpsPendOperation0() API.
• This call returns a completion context.

In this scenario, the Remote Address field in the completion context is zeroed out. Additionally, the computer may crash, depending on how the callout driver handles the Remote Address field.

Note: This issue may occur if a reauthentication request is triggered by calling the FwpsCompleteOperation0() API.

Consider the following scenario:

• Multiple network adapters are installed on a computer.
• One network adapter is configured to use an Automatic Private Internet Protocol Addressing (APIPA) IP address.
• Another network adapter is configured to use a non-APIPA IP address.
• The interface metric is smaller on the second network adapter than the metric that is configured on the first network adapter.
• An application calls the getaddrinfo function on the computer.

In this scenario, the first-returned IP address is the APIPA IP address.

Notes:

• This issue prevents network applications that use only the first-returned local IP address by calling the getaddrinfo function (such as a Java-based application that calls the GetLocalHost Java API) from connecting to network resources.
• This issue occurs on a computer that is running one of the following operating systems:
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)

Assume that an application or a service loads and then unloads the Netshell.dll module frequently on a computer that is running Windows Vista or Windows Server 2008. For example, an application frequently queries the Win32_NetworkAdapter WMI namespace. In this situation, the memory usage of the application or the service keeps increasing. With time, the application or the service stops working if available memory resources are exhausted.

Note: The Netshell.dll module can be loaded directly or indirectly by an application or a service.

When you change the network adapter teaming configuration on a computer that is running Windows Vista or Windows Server 2008, you randomly receive various Stop error messages that resemble the following:

STOP: 0x000000D1 (parameter1, parameter2, parameter3, parameter4)

Note: This Stop error describes a DRIVER_IRQL_NOT_LESS_OR_EQUAL issue.

STOP 0×00000050 (parameter1, 0, parameter3, parameter4)

Note: This Stop error describes a PAGE_FAULT_IN_NONPAGED_AREA issue.

STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4)

Note: This Stop error describes an IRQL_NOT_LESS_OR_EQUAL issue.

Notes:

• The parameters in these Stop error messages vary, depending on the configuration of the computer.
• Not all “0x000000D1″, “0×00000050″, and “0x0000000A” Stop errors are caused by this issue.
• You may also experience other Stop errors when this issue occurs.

When user is trying to monitor network using SNMP agent (SNMP Service) , it can not collect NIC name correctly.
It is using ifAlias (.1.3.6.1.2.1.31.1.1.1.18) If NIC name contains multi byte Characters, then, it fails to get NIC name using ifAlias

Consider the following scenario:

• You have a Windows Vista or Windows 7 machine.
• After you boot the machine, you hot plug a PCI Express card.
• The PCI Express card may not be detected in Windows.

In the event that the card is detected, you may experience issues communicating with the device.

On a NTP client computer that is running Windows Vista, Windows Server 2008, Windows 7 or Windows Server 2008 R2, it may not correct its time if the following conditions are true:

• The NTP client syncs its time with the manually specified NTP server.
• The NTP client uses SpecialPollInterval as a polling interval.
• The time offset between the NTP client and the NTP server is greater than the LargePhaseOffset configured in the NTP client.

In this situation, the NTP client cannot correct its time even after waiting for SpikeWatchPeriod is over.

When working with a Terminal Server RemoteApp connection, the name of the application in the taskbar does not appear as expected. For Example, when connected to the application Product Studio, the name listed in the taskbar appears as (Remote):

Your expected result would be that when connected to the application Product Studio, the name listed in the taskbar appears as Application Name (Remote).

Starting with Windows Server 2008 and Windows Vista, USB overcurrent pop-up notifications no longer appear. This is by design. Previously, in Windows Server 2003 and Windows XP, these notifications would appear when USB overcurrent conditions occurred.

When attempting to install applications you may receive the following error:

“The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.”

For this issue on Windows XP or Windows Server 2003 see the following article:

315346 Error message when you try to add or remove a program on a computer that is running Windows XP or Windows Server 2003: “The Windows Installer service could not be accessed”