A server that is running Server Message Block Version 2 (SMB2) does not respond to certain FSCTL_SRV_NOTIFY_TRANSACTION requests from SMB2 clients. This causes time-out issues when the SMB2 client is running Windows Vista or Windows Server 2008.

Consider the following scenario:

• On a computer that is running Windows Vista or Windows Server 2008, you enable Microsoft Message Queuing (also known as MSMQ) 4.0.
• The computer has multiple IP addresses. For example, multiple network adapters are installed on the computer.
• You configure the BindInterfaceIP registry entry to enable an instance of Message Queuing 4.0 to bind to a single IP address on the computer.
  Note: The BindInterfaceIP registry entry is located under the following registry key:
  HKEY_LOCAL_MACHINE\Software\Microsoft\MSMQ\Parameters\BindInterfaceIP

In this scenario, the BindInterfaceIP registry entry value is incorrect. Therefore, messages are not received or sent when you use Message Queuing 4.0.

Note: This problem occurs on clustered computers and on nonclustered computers.

Description: This security update resolves a privately reported vulnerability in the Windows Message Queuing Service (MSMQ). The vulnerability could allow elevation of privilege if a user received a specially crafted request to an affected MSMQ service. By default, the Message Queuing component is not installed on any affected operating system edition and can only be enabled by a user with administrative privileges. Only customers who manually install the Message Queuing component are likely to be vulnerable to this issue. The security update addresses the vulnerability by modifying the way that the MSMQ service validates input data before passing the data to the allocated buffer. Keep reading →

Consider the following scenario:

• On a Windows Vista-based computer, you install a signed driver.
• You open Device Manager, and then you click the Driver Details button on the Driver tab.

In this scenario, the Digital Signer field for the device displays the following status message:

Not digitally signed

However, when you right-click the properties of the device on the main Device Manager tab, a message is displayed that states that the driver is signed.

After you upgrade a computer from Windows XP to Windows Vista, you cannot send or receive encrypted Microsoft Message Queuing, also known as MSMQ, 4.0 messages. The attempts to send or to receive encrypted Message Queuing messages fail. Additionally, you receive the following error message:

0×80090016 “The key container could not be opened”.

Consider the following scenario:

• You run the release version of Windows Vista in Workgroup mode.
• You install Windows Vista Service Pack 1 (SP1).
• You uninstall Windows Vista SP1.
• You run Windows Vista in Workgroup mode again.

In this scenario, the Microsoft Message Queuing (also known as MSMQ) service does not start. Additionally, an event is logged to indicate that the notify_queue$ queue is not found.

When you try to send messages to the HTTP address or to the multicast address of a Microsoft Message Queuing queue on a computer that is running a 64-bit version of Windows Vista, the attempt is unsuccessful. Additionally, you receive the following error message:

404 not found

After you use the “Turn Windows features on or off” wizard in Windows Vista to configure Windows features, no Microsoft Message Queuing 4.0 components are enabled when the wizard is finished.

Note: Microsoft Message Queuing is also known as MSMQ.

Consider the following scenario:

• You send a message to a local transactional queue in Microsoft Message Queuing, also known as MSMQ, 4.0.
• You set the AcknowledgeType property to System.Messaging.AcknowledgeTypes.NegativeReceive for the message that you are sending.
• You specify a value for the AdministrationQueue property of the message.
• You specify a value for the DeadLetterQueueName property of the message.
• A negative acknowledgement is generated for the message that you are sending.

In this scenario, the sent message is written to the specified dead letter queue. However, a negative acknowledgement is not sent to the specified administration queue.