Tag Archives: “Hot Fix”

Winword.exe – Pre Service Pack 4 Revision History for Microsoft Word 2007 SP3

Winword.exe – Pre Service Pack 4 Revision History for Microsoft Word 2007 SP3

07-Nov-2012 – 12.0.6670.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2596621 – Description of the Word 2007 hotfix package (Word-x-none.msp): December 11, 2012

07-Nov-2012 – 12.0.6670.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2598172 – Description of the Word 2007 hotfix package (Word-x-none.msp, Wordconv-x-none.msp): December 11, 2012

21-Oct-2012 – 12.0.6668.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2760421 – MS12-079: Description of the security update for Word 2007 Service Pack 2 and Service Pack 3: December 11, 2012

20-Oct-2012 – 12.0.6668.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2687537 – Description of the Word 2007 hotfix package (Wordconv-x-none.msp, Word-x-none.msp): October 30, 2012

14-Aug-2012 – 12.0.6665.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2687333 – Description of the Word 2007 hotfix package (Wordconv-x-none.msp, Word-x-none.msp): August 28, 2012

19-Jul-2012 – 12.0.6662.5003 – Winword.exe – x86 – http://support.microsoft.com/kb/2687315 – MS12-064: Description of the security update for Word 2007 Service Pack 2: October 9, 2012

10-Jun-2012 – 12.0.6662.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2687259 – Description of the Word 2007 hotfix package (Word-x-none.msp, Wordconv-x-none.msp): June 26, 2012

04-Apr-2012 – 12.0.6661.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2598132 – Description of the Word 2007 hotfix package (Word-x-none.msp, Wordconv-x-none.msp): April 24, 2012

09-Feb-2012 – 12.0.6658.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2597961 – Description of the Word 2007 hotfix package (Word-x-none.msp, Wordconv-x-none.msp): February 28, 2012

30-Nov-2011 – 12.0.6656.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2596990 – Description of the Word 2007 hotfix package (Word-x-none.msp, Wordconv-x-none.msp): December 13, 2011

05-Oct-2011 – 12.0.6654.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2596577 – Description of the Office Word 2007 hotfix package (Wordconv-x-none.msp, Word-x-none.msp, Outlook-x-none.msp): October 25, 2011

05-Oct-2011 – 12.0.6654.5000 – Winword.exe – x86 – http://support.microsoft.com/kb/2596543 – Description of the Office Word 2007 hotfix package (Wordconv-x-none.msp, Word-x-none.msp): October 25, 2011

[RESOLVED] Your computer may stop responding when you run an application, Software Firewall or anti-virus package that uses the Windows Filtering Platform API

Your computer may stop responding when you run an application, Software Firewall or anti-virus package that uses the Windows Filtering Platform API

This issue affects the following operating systems:

  • Windows 7 – Service Pack 1
  • Windows Small Business Server 2011 – Service Pack 1
  • Windows SBS 2011 – Service Pack 1
  • Windows Server 2008 R2 – Service Pack 1
  • Windows Small Business Server 2008 – Service Pack 2
  • Windows SBS 2008 – Service Pack 2
  • Windows Server 2008 – Service Pack 2
  • Windows Vista – Service Pack 2

In this situation, the computer may perform slowly or stop responding and network activity may be affected.  You find that a system restart may resolve this issue in some instances.

This issue occurs because the FwpsStreamInjectAsync0 function causes the interrupt request level (IRQL) to leak.  You can resolve the issue by updating to the latest Netio.sys driver.  The download link can be found within Microsoft KB 2664888 http://support.microsoft.com/kb/2664888

 

Windows Filtering Platform (WFP) General Description

Windows Filtering Platform (WFP) is a set of API and system services that provide a platform for creating network filtering applications. The WFP API allows developers to write code that interacts with the packet processing that takes place at several layers in the networking stack of the operating system. Network data can be filtered and also modified before it reaches its destination.

By providing a simpler development platform, WFP is designed to replace  previous packet filtering technologies such as Transport Driver Interface (TDI)  filters, Network Driver Interface Specification (NDIS) filters, and Winsock Layered Service Providers (LSP). Starting in Windows Server 2008 and Windows Vista, the firewall hook and the filter hook drivers  are not available; applications that were using these drivers should use WFP instead.

With the WFP API, developers can implement firewalls, intrusion detection systems, antivirus programs, network monitoring tools, and parental controls. WFP integrates with and provides support for firewall features such as authenticated communication and dynamic firewall configuration based on applications’ use of sockets API (application-based policy). WFP also provides infrastructure for  IPsec policy management, change notifications, network diagnostics, and stateful filtering.

More info can be found here http://msdn.microsoft.com/en-us/library/windows/desktop/aa366510(v=vs.85).aspx

 

[RESOLVED] A process that is being terminated stops responding in Windows 7 or Windows Server 2008 R2 or Small Business Server 2011

You may find that when you try to terminate a process on Windows 7, Windows Server 2008 R2, Windows Small Business Server 2011 SBS 2011 that the termination process stops responding.  The main thread of the process becomes blocked and if you analyse the call stack of the process you will see that a thread is blocked in the ntdll!NtReleaseKeyedEvent() function.  This occurs because of a race condition whereby the main thread that is trying to terminate the process also tries to reactivate another thread when the thread released an SRW lock.

This issue can be resolved by installing a hotfix containing an updated Ntdll.dll driver.  You can find the hotfix download link in Microsoft KB 2582203 http://support.microsoft.com/kb/2582203

32 Bit Applications that utilise NetBIOS API do not receive connection close notifications in Windows 7 64 Bit Edition, Windows Server 2008 R2 or Windows Small Business Server 2011

32 bit applications that utilise NetBIOS API do not receive connection close notifications in Windows 7 64 Bit Edition, Windows Server 2008 R2 or Windows Small Business Server 2011 and as a result they do not try to re-establish a session.  Restarting the application will re-establish the session and recover from the issue.

This issue occurs because when the Netbios.sys driver receives data the driver does not convert the Network Connection Block NCB structure from 64 bit to 32 bit when the session has been dropped.  A 32 bit application cannot understand the 64 bit NCB structure which is why the session cannot be re-established.

The Microsoft Knowledgebase article KB 2633667 provides further information on the issue and a Hotfix containing an updated version of the Netbios.sys driver that that corrects this particular issue http://support.microsoft.com/kb/2633667