Tag Archives: 64bit

Microsoft, SBS 2008, Service Pack 2, Service Pack 2, Service Pack 2, Service Pack 2, Small Business Server 2008, Windows, Windows Server 2008, Windows Vista

Ole32.dll – Pre Service Pack 3 Revision History for Windows Server 2008 SP2, Windows Vista SP2 and Windows Small Business Server 2008 (SBS 2008)

Ole32.dll – Pre Service Pack 3 Revision History for Windows Server 2008 SP2, Windows Vista SP2 and Windows Small Business Server 2008 (SBS 2008)

28-Apr-2011 – 6.0.6002.22633 – Ole32.dll – x86/x64 – http://support.microsoft.com/kb/2545479 – A memory leak occurs, and client requests may take a long time, when you run an application that is based on COM+ and that is registered as single-threaded

08-Nov-2010 – 6.0.6002.22520 – Ole32.dll – x64 – http://support.microsoft.com/kb/2457836 – The call operation fails with error code “0x800706f7” when you run an application that calls the OleCreateFromFile() function to create an embedded object from the contents of a named file in a 64-bit version of Windows Vista or Windows 7

28-Jun-2010 – 6.0.6002.22433 – Ole32.dll – x86/x64 – http://support.microsoft.com/kb/979687 – MS10-083: Description of the security update for WordPad: October 12, 2010

Microsoft, SBS 2008, SBS 2011, Service Pack 1, Service Pack 1, Service Pack 1, Service Pack 1, Service Pack 2, Service Pack 2, Service Pack 2, Service Pack 2, Small Business Server 2008, Small Business Server 2011, Windows, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows Vista

[RESOLVED] 32 Bit Application or Game with the /LARGEADDRESSAWARE option running on a 64 Bit Version of Windows Vista, Windows Server 2008, Windows SBS 2008, Windows 7, Windows Server 2008 R2 or Windows SBS 2011 may generate an error message

When you run a 32 Bit Application or Game with the /LARGEADDRESSAWARE option on a 64 Bit Version of Windows you may receive one of the following errors

  • WSANO_DATA
  • ERROR_NO_DATA (232)
  • ERROR_NOACCESS (998)

These errors will occur if the application consumes large amounts of memory, the kernel denies read or write access to the address and returns an error to the application.

The Microsoft Knowledgebase article KB 2588507 provides a hotfix to address these issues http://support.microsoft.com/kb/2588507/en-gb

To apply this hotfix, you must be running one of the following 64 Bit operating systems:

  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7 (RTM)
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2 (RTM)
  • Windows Server 2008 R2 Service Pack 1 (SP1)
Microsoft, SBS 2011, Service Pack 1, Service Pack 1, Service Pack 1, Service Pack 1, Small Business Server 2011, Windows, Windows 7, Windows Server 2008 R2

[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

Microsoft, SBS 2011, Service Pack 1, Service Pack 1, Small Business Server 2011, Windows 7, Windows Server 2008 R2

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