Severity Rating: Important
Revision Note: V1.0 (October 14, 2014): Bulletin published.
Summary: This security update resolves a publicly disclosed vulnerability in Microsoft Windows. The vulnerability could allow elevation of privilege if an attacker sends a specially crafted input/output...
Severity Rating: Important
Revision Note: V1.0 (October 14, 2014): Bulletin published.
Summary: This security update resolves a publicly disclosed vulnerability in Microsoft Windows. The vulnerability could allow elevation of privilege if an attacker sends a specially crafted input/output...
Fixes an issue that occurs when you use a Direct=TCP format to send messages to queues on many Message Queuing clients in Windows 7 or in Windows Server 2008 R2.
More...
Fixes an issue in which you receive Stop error messages when messages are not received by applications in Windows 7 or in Windows Server 2008 R2. This issue occurs after Message Queuing moves the messages to a dead-letter queue.
Link Removed
Fixes an issue that occurs when you use a Direct=TCP format to send messages to queues on many Message Queuing clients in Windows 7 or in Windows Server 2008 R2.
More...
Fixes an issue in which the MSMQ service might not send or receive Message Queuing (MSMQ) messages after you restart a computer that is running Windows 7, Windows Server 2008 R2, Windows Vista or Windows Server 2008.
More...
Fixes a high memory usage issue that occurs when you perform a remote transactional read on a Message Queuing 5.0 queue in Windows 7 or in Windows Server 2008 R2. This issue occurs after the queue is filled.
More...
Fixes an issue in which the MSMQ service might not send or receive Message Queuing (MSMQ) messages after you restart a computer that is running Windows 7 or Windows Server 2008 R2.
More...
Fixes an issue in which you cannot send or receive messages by using Message Queuing 4.0 or Message Queuing 5.0. This issue occurs on a computer that has multiple IP addresses.
More...
Fixes an issue in which an error occurs when you send messages from one instance of Message Queuing 4.0 to another instance of Message Queuing 4.0. This issue occurs on a Windows Server 2008-based computer that is in a failover cluster.
More...