When you have a Windows Vista-based computer that is connected to a USB optical disc drive, and you resume the computer from Standby, you may receive a error message that resembles one of the following error messages:

STOP: 0×000000E4 (parameter1, parameter2, parameter3, parameter4)
STOP: 0×0000000A (parameter1, parameter2, parameter3, parameter4)

Notes

• The parameters in the error message vary, depending on the configuration of the computer.
• This issue may occur on a computer that is running Windows Vista, Windows Vista Service Pack 1 (SP1), or Windows Server 2008.
• Not all “0×000000E4″ or “0×0000000A” Stop errors are caused by this problem.

When you install update 938371 from Windows Update, you may lose access to the USB mouse or the USB keyboard on a computer that is running Windows Vista.

Notes

• This problem occurs when a very specific chain of events occurs in a specific order. This problem is not common. But when this problem occurs, it is very difficult to troubleshoot because you may lose access to the mouse and the keyboard. And, such access is required to troubleshoot the problem.
• See the “Advanced Troubleshooting” section for more information about the conditions in which this problem is known to occur and about the cause of the problem.

So you just woke up your PC and one of your USB devices isn’t working as it should? Here’s a half-dozen Microsoft suggestions on how to troubleshoot the problem. Keep reading →

Consider the following scenario:

• You are running a Windows Vista-based computer.
• This computer has a USB device, such as a USB fingerprint reader, attached.
• You resume the computer from standby or from hibernation,

In this scenario, you may receive the following Stop error message:

Stop 0×000000FE ( 00000008 , 00000006 , 00000001 , parameter4 )
BUGCODE_USB_DRIVER

Note: In this error, the value of the Parameter4 placeholder may vary.

Consider the following scenario. You connect a USB Chip/Smart Card Interface Devices (CCID) smart card reader to a Windows Vista-based computer through an external USB hub. Then, the USB hub is disconnected from the computer while an application is communicating with the smart card reader. In this scenario, the Smart Card Resource Manager may stop responding (hang).

After the Smart Card Resource Manager stops responding, you cannot stop the Smart Card Resource Manager by using Task Manager. Additionally, you cannot access the smart card reader even if the USB hub is plugged into the computer again. In this case, you have to restart the computer.

Note: This problem does not occur if the smart card reader is directly connected to the computer.

• BitLocker Drive Preparation Tool Available For Download - Get Connected With Aubrey
  If you don't partition your drive correctly before the OS install, you won't be able to install Bitlocker. This tool will create another volume to boot from so that you can get BitLocker set up.
  (tags: BitLocker )
• Fixing Windows Vista, Part 2: Taming UAC
  An excellent article on how to make UAC work for you, instead of turning it off and losing all the benefits it can offer.
  (tags: Security UAC )

Keep reading →

Microsoft handing out USB keys that circumvent Vista security? I don’t think so. Keep reading →

• When you are prompted to enter administrative credentials for a directory to which you do not have permissions, your user ID is added to the DACL list for the directory in Windows Vista
  This article describes the behavior that occurs in Windows Vista when you are prompted to enter administrative credentials for a directory to which you do not have permissions.
  (tags: Administrator Credentials )
• Microsoft Vista Update Causes USB Problems - News and Analysis by PC Magazine
  One of last weeks updates, a re-release, is causing some to have problems with their USB devices. Microsoft has confirmed the bug.
  (tags: USB Update )

Keep reading →

One of last weeks updates, a re-release, is causing some to have problems with their USB devices. Microsoft has confirmed the bug. Keep reading →

Consider the following scenario:

• On a Windows Vista SP1-based computer that has a USB Bluetooth radio device installed and running, you perform a Windows Hardware Quality Lab (WHQL) Bluetooth “Disable/Enable I/O” test.
• In this test, you use the Driver Verifier utility (Verifier.exe) to monitor the driver.
• Then, you disable the Bluetooth Enumerator device in Device Manager.

In this scenario, a warning bubble appears on the taskbar, and it contains a warning that the device hardware ID cannot be found. Additionally, a yellow exclamation mark (!) appears next to the Bluetooth Enumerator device in Device Manager. Finally, a Code 9 error is generated in the Device status box in the Bluetooth Enumerator Properties dialog box.

Note: After this issue occurs, you cannot enable the device before you restart the computer.