Error codes in Device Manager in Windows

You probably reached this article because Device Manager reported an error code, and you are not sure how to resolve it. In this article, we will help you find your error code and suggest what you might try to correct the error.
First, try any of the following common resolutions to correct the error: Run an automated troubleshooting service
Collapse this imageExpand this image
Run the Hardware devices are not working or are not detected in Windows
( troubleshooter from the Microsoft Support website.
Additional troubleshooter for USB devices

Collapse this imageExpand this image
If you encounter the error on devices that are connected by using a USB port, you can also try the Diagnose and fix Windows USB problems automatically
( troubleshooter.
Note This troubleshooter currently does not apply to Windows 8.1 and Windows 8.
Collapse this imageExpand this image

Collapse this imageExpand this image
Update the device driver
Collapse this imageExpand this image
Update the device driver from Windows UpdateUpdate the hardware’s device driver through Windows Update
( Updated the device driver from the vendor’s websiteUpdate the device driver from the vendor’s website. Follow their installation or update instructions.If the device was preinstalled on the computer, visit the computer manufacturer’s website. If the device was installed after the purchase of the computer, visit the device manufacturer’s website. If the device was preinstalled on the computer, and the computer manufacturer does not have an updated driver for the device, visit the device manufacturer’s website. Note Make sure that the device drivers that are being installed are compatible with your current Windows version and platform.
Collapse this imageExpand this image

KDC interoperability with MIT Kerberos implementations when using Read Only Domain Controllers

This article describes circumstances under which devices implementing MIT Kerberos libraries will fail authentication when used in conjunction with a Windows 2008 or 2008R2 domain which utilises Read Only Domain Controllers (RODC). This article describes the symptoms and configurations under which the issue may present itself and suggests potential workarounds. In addition it explains the underlying reason for the failure. 

In an environment with one or more RODCs authentication may fail when interacting with certain MIT based Kerberos devices in one of the following scenarios.
·          The client is an MIT device which received a TGT from Windows KDC on RODC
·          The client passes a TGT generated by Windows KDC on RODC to MIT Device which in turn uses the TGT to request a TGS on behalf of the calling user.
In both scenarios the TGT will have been issued by an RODC where the  msDS-SecondaryKrbTgtNumber associated with the krbtgt account for that RODC will have a value greater than 32767.

In the first scenario the client will receive the error KRB_ERR_S_PRINCIPAL_UNKNOWN in response to any TGS request.
In the second scenario the TGS request will be silently dropped by the Windows Key Distribution Center KDC and a TCP connection Reset response will be issued.
In this circumstance capturing the traffic from the device you will see that the Key Version Number (KVNO) in the outgoing request is prepended with a 0 making the entire KVNO a 5 bytes in length.
Windows KDCs will always reject a 5 byte KVNO as they consider this to be malformed.
Note: Other clients may be unaffected and depending upon network topology the issue may be intermittent on affected clients

A VSS backup operation may fail in a Windows Server 2008-based failover cluster

Consider the following scenario:
You configure a failover cluster by using some computers that are running Windows Server 2008.You run a backup application that performs Volume Shadow Copy Service (VSS)-based backup operations on the active node.A failover occurs in the cluster.
In this scenario, the backup operations may fail. Additionally, an event that resembles the following is logged in the Application log: 

Event Type: Error
Event Source: VolSnap
Event Category: None
Event ID: 9
Date: <date>
Time: <time>
User: N/A
Computer: <computer name>
The flush and hold writes operation on volume <volume name> timed out while waiting for file system cleanup.
This issue occurs because of a race condition in the mounting of volumes after a failover. In this race condition, NTFS uses a target device object that is not a volsnap device object. Therefore, the Flush & Hold Writes operations are not sent to the Volsnap.sys driver.

Update for the DFS Replication (DFSR) Management interface is available

An update is now available for the DFS Replication (DFSR) Management interface for Windows Server 2008 R2-based computers and for Windows 7-based computers. This update increases the discoverability of the existing guidance from Microsoft about how to configure DFSR staging folder quotas. This update also adds a link in the wizards to the following Microsoft TechNet topic:
Edit the Quota Size of the Staging Folder and Conflict and Deleted Folder
( to install this updateYou should install this update on any Windows Server 2008 R2-based computer that has the DFS Replication role enabled or on any Windows 7 client that has the Remote Server Administration Tools (RSAT) package installed for remotely managing a DFSR server. Follow the guidance that is provided in the updates to optimize DFSR performance and also to protect against unexpected downtime that may be caused by a misconfiguration of the staging folder quota.

This installation makes several significant interface updates and provides new guidance regarding the updated content. Specifically, this installation updates the following binary files:dfsobjectmodel.dlldfsmgmt.dlldfsres.dllThis installation updates the following DFSR wizards:New Replication GroupNew Replicated FolderAdditionally, this installation updates the Replicated Folder Properties page in the wizards.
For example, after you install this update, you see the following updated wizard screen.
Note The updated content is indicated by the red box.
Collapse this imageExpand this image
Restart informationAfter you install this update, you must close and then reopen the DFS Management interface to access the new guidance content. You do not have to restart the system or the DFSR service after you install this update.How to obtain this updateClick the following link to obtain the appropriate update, depending on your operating system.
Update for Windows Server 2008 R2 x64 edition (KB2607047)
( for x86-based versions of Windows 7 (KB2607047)
( for x64-based versions of Windows 7 (KB2607047)

An access violation exception occurs in the “NdrClientCall2″ function in Windows Vista or in Windows Server 2008

Consider the following scenario:You have a computer that is running Windows Vista or Windows Server 2008.You use some remote procedure calls (RPC) to send data between an RPC client and an RPC server.Some callback functions are called between the RPC client and the RPC server.In this scenario, an access violation exception occurs in the NdrClientCall2 function on the RPC client. This access violation exception may cause data loss. Additionally, the memory usage of the RPC client keeps increasing. 
This issue occurs because the RPC driver (Rpcrt4.dll) handles an RPC call that involves the callback functions incorrectly.
When the call back function is called, the RPC client allows the RPC server to access some data of the RPC client. However, the RPC server does not notify the RPC client to free a buffer that may be used later when the callback function returns. This behavior causes a memory leak on the RPC client. Additionally, an access violation occurs when the RPC client tries to use the buffer again.

SQL Server Questions and Answers, SQL QA