Category Archives: Service Pack 2

.NET Framework, 4, Microsoft, SBS 2003, 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 2003, Small Business Server 2008, Small Business Server 2011, Windows, Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP, XP Mode

Microsoft Windows may stop responding or respond very slowly when the .Net Framework 4 Optimization Service (Mscorsvw.exe) starts

The computer may stop responding or respond very slowly when the .Net Framework 4 Optimization Service (Mscorsvw.exe) starts. This issue effects the following operating systems: Windows XP SP3, Windows Server 2003, SBS 2003, Windows Vista SP2, Windows Server 2008 SP2, SBS 2008 SP2, Windows 7 SP1, Windows Server 2008 R2 SP1 and SBS 2011 SP1.

The issue occurs because the process sets its service configuration incorrectly.

A hotfix is available but must be requested from Microsoft using KB 2571181 http://support.microsoft.com/kb/2571181

Alternatively you can immediately download the hotfix from “thehotfixshare” website

Windows x86

http://thehotfixshare.net/board/index.php?showtopic=16259&hl=2571181

Windows x64

http://thehotfixshare.net/board/index.php?showtopic=16258&hl=2571181

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

Windows Vista, Server 2008 and SBS 2008 Service Pack 2 – You may find that Memory Manager can no longer commit Memory Pages resulting in applications and services experiencing performance and reliability issues

If you are running Windows Vista, Windows Server 2008 or Windows Small Business Server 2008 with Service Pack 2 you may find that Memory Manager can no longer commit Memory Pages resulting in applications and services experiencing performance and reliability issues.

This issue occurs because the Memory Manager incorrectly attempts to return more memory pages than have actually been allocated.

The issue can be resolved by applying the hotfix KB 2619529 http://support.microsoft.com/kb/2619529