Transport Driver Interface: The protocol understood by the upper edge of the Transport layer of the Microsoft Windows kernel network stack.

Description: This security update resolves one publicly disclosed and two privately reported vulnerabilities in the Windows kernel. A local attacker who successfully exploited these vulnerabilities could take complete control of an affected system. The vulnerabilities could not be exploited remotely or by anonymous users. The security update addresses the vulnerabilities by correcting window property validation passed during the new window creation process, correcting the manner in which system calls from multiple threads are handled, and correcting validation of parameters passed to the Windows Kernel from user mode. Keep reading →

Consider the following scenario:

• You are running a Windows Vista Service Pack 1 (SP1)-based computer.
• Antivirus and antispyware with e-mail scanning software is installed on the computer.
• An e-mail client, such as Microsoft Office Outlook or Windows Mail, is configured to receive POP3 or SMTP e-mail messages.

When you start the e-mail client, or when you try to send or receive e-mail messages, Windows Vista crashes. Additionally, you receive the following Stop error message:

STOP: 0×1000008E (Parameter1, Parameter2, Parameter3, Parameter4) In TCPIP.SYS
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

Note: This issue does not occur if one of the following conditions is true:

• The e-mail client is configured to receive HTTP e-mail messages instead of POP3 or SMTP e-mail messages.
• The e-mail client works offline.

Description: This security update resolves a privately reported vulnerability in the Windows kernel. A local attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts. Keep reading →

In the Windows Vista “Reliability and Performance Monitor,” you add a Heap Trace Provider for a Data Collector Set. However, you find that the name of the trace session is incorrectly set to NT Kernel Logger.

Note: The NT Kernel Logger session name is reserved for the session that only contains Windows Kernel Trace provider.