On certain laptops or notebooks, when you attempt to clear TPM information you may receive following error:

0x80290300: A general error was detected when attempting to acquire the BIOS’s response to a Physical Presence command.


When you install a Type 8 PCIe device such as the PCI/PCI-X to PCI Express Bridge on a Windows-based computer, the device does not function. Additionally, you see a yellow triangle error that contains an exclamation mark in Device Manager. When you double-click the error, you receive the following error message:

This device cannot start. (Code 10)


The supported password-change protocols are:

  1. The NetUserChangePassword protocol
  2. The NetUserSetInfo protocol
  3. The Kerberos change-password protocol (IETF Internet Draft Draft-ietf-cat-kerb-chg-password-02.txt) [port 464]
  4. Kerberos set-password protocol (IETF Internet Draft Draft-ietf-cat-kerberos-set-passwd-00.txt) [port 464]
  5. Lightweight Directory Access Protocol (LDAP) write-password attribute (if 128-bit Secure Sockets Layer [SSL] is used)
  6. XACT-SMB for pre-Microsoft Windows NT (LAN Manager) compatibility

Change-password operations require that the user’s current password be known before the change is allowed. Set-password operations do not have this requirement, but are controlled by the Reset Password permissions on the account.

When you are using LDAP (method 5), the domain controller and the client must both be able to use 128-bit SSL to protect the connection. If the domain controller is not configured for SSL or if appropriately long keys are not available, the password-change write is denied.

An Active Directory domain controller listens for change-password requests on all of these protocols.

As stated earlier in this article, different protocols are used in different circumstances. For example:

  • Interoperable Kerberos clients use the Kerberos protocols. UNIX-based systems with MIT Kerberos version 5 1.1.1 can change user passwords in a Windows-based domain by using the Kerberos change-password protocol (method 3).
  • When a user changes his or her own password by pressing CTRL+ALT+DELETE and then clicking Change Password, Windows NT up to Windows 2003 the NetUserChangePassword mechanism (method 1) is used if the target is a domain. From Windows Vista onwards, the Kerberos change password protocol is used for domain accounts. If the target is a Kerberos realm, the Kerberos change-password protocol (method 3) is used.
  • Requests to change a password from computers that are running Microsoft Windows 95/Microsoft Windows 98 use XACT-SMB (method 6).
  • A program that uses the ChangePassword method on the Active Directory Services Interface (ADSI) IaDSUser interface first tries to change the password by using LDAP (method 5), and then by using the NetUserChangePassword protocol (method 1).
  • A program that uses the SetPassword method on the ADSI IaDSUser interface first tries to change the password by using LDAP (method 5), then the Kerberos set-password protocol (method 4), and then the NetUserSetInfo protocol (method 2).
  • The Active Directory Users and Computers snap-in uses ADSI operations for setting user passwords.


On a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2, you may experience one of the following issues:

  • IP address and default gateway settings are assigned incorrectly.
  • After you configure additional IP addresses, the IP addresses are displayed incorrectly when you run the ipconfig command.
  • After you restart the computer, IP address settings revert to previous settings.


While connecting to a wireless network on a Windows system that is part of a workgroup, a Windows Security Alert dialog similar to the following may be displayed:

The server “<Authentication server>” presented a valid certificate issued by “<CA name>”, but “<CA name>” is not configured as a valid trust anchor for this profile. Further, the server “<Authentication server>” is not configured as a valid NPS server to connect to this profile.


The server “<Authentication server>” presented a valid certificate issued by “<CA name>”, but “<CA name>” is not configured as a valid trust anchor for this profile.

If you click the Connect button on the dialog box, the wireless connection will be established successfully.


Consider the following scenario:

You have a Windows 7 or Vista PC that is connected to an external display using a DisplayPort or HDMI cable.
The external display has built-in speakers.
The display’s speakers are set as the default audio playback device in Windows.
You are running an on-screen display (OSD) application that displays the volume level or screen brightness state whenever there is a change in levels.

In this scenario you may notice that whenever audio is played through the external display’s speakers, the OSD application will appear for a couple of seconds and display the volume level. The expected behavior is that the application should only display the volume state when the volume is changed or muted.


When using Windows Vista with a touch-enabled display, the default “press and hold” behavior is to perform the equivalent of a mouse right-click. This may be configured through the Pen and Touch control panel.
Ordinarily, when you press a finger to the touch screen and hold, an animated ring starts to appear to indicate that you are entering the “press and hold” mode. If you wait for the ring to complete drawing and then remove your finger, the ring should disappear and the context menu should be displayed.

In rare instances, if you quickly move your finger while removing it from the screen, the context menu will not be displayed, and instead the “press and hold” ring will stay on the screen and finger touch may no longer function correctly.


On Windows Vista and later, the Win32_NetworkAdapterConfiguration class is unable to retrieve information about a PPPoE connection and VPN connection.
If a program is designed to get the information about the dial-up connection or a virtual private network by using the Win32_NetworkAdapterConfiguration class on Windows XP, it may not work on Windows Vista and later.

For more information about the Win32_NetworkAdapterConfiguration class, see the following MSDN documentation:

Win32_NetworkAdapterConfiguration Class


When you search for an item in Windows 7 or in Windows Vista, Windows Search may return many undesired Windows Live Mail files.


Consider the following scenario. On a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP 1 or that has KB9823246 installed, you recompile a Microsoft ActiveX Data Objects (ADO) application by using one of the following applications:

  • Microsoft Visual C++
  • Microsoft Visual Basic for Applications (VBA)
  • Microsoft Visual Basic 6
  • Microsoft .NET applications

In this scenario, you find that the application does not run on down-level operating systems. For example, it does not run on the release version of Windows 7, on Windows Vista, and on other earlier versions of Windows. Depending on your implementation, you also receive an error message that resembles one of the following. (You may receive other error messages.)

Error message 1


Error message 2

E_POINTER (0x80004003)

Error message 3

E_NOINTERFACE (0x80004002)

Error message 4

Unable to cast COM object of type ‘System.__ComObject’ to interface type ‘ADODB.Connection’. This operation failed because the QueryInterface call on the COM component for the interface with IID ‘{00001550-0000-0010-8000-00AA006D2EA4}’ failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).”

The following Visual C++ code segment replicates this issue.

#import ” msado15.dll” no_namespace rename(“EOF”,”EndOfFile”)
int main()
_ConnectionPtr pConnection = NULL;
HRESULT hr = pConnection.CreateInstance(__uuidof(Connection)); //hr gets E_NOINTERFACE here

The following Visual Basic for Applications code segment replicates this issue.

Private Sub Form_Load()
Dim Conn As New ADODB.Connection ‘Runtime error here: Class does not support Automation or does not support expected interface
End Sub

Note: Microsoft no longer supports the primary interop assembly for ADO and no longer supports Visual Basic 6. For more information about Visual Basic 6 supportability, visit the following MSDN webpage:
Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7
For more information about the primary interop assembly for ADO supportability, click the following article number to view the article in the Microsoft Knowledge Base:
318559 Using the primary interop assembly for ADO (ADODB) in Visual Studio .NET