Tag Archives: “operate slowly”

.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 2011, Small Business Server 2011, Windows, Windows 7, Windows Server 2008 R2

Windows 7, Server 2008 R2 and SBS 2011 RTM or SP1 – svchost.exe may hold a lock on a service and cause slow Windows startup

You may find that svchost.exe holds a lock on a service whilst all the service libraries are being loaded.  This in turn then prevents any other services in the same instance of svchost.exe from starting up until the call to the function has been returned.

An updated version of svchost.exe that will address the issue is available here http://support.microsoft.com/kb/2510636

Microsoft, Windows, Windows 7, Windows XP, XP Mode

A Virtual Machine, Laptop or Computer running Windows XP is Slow to Startup and/or Applications take a long time to load

These two issues can occur for two different reasons, a corrupt file in the Windows Prefetch Folder or it could be that the Prefetch Folder is cluttered.

To resolve these issues you need to delete the contents of the C:\Windows\Prefetch folder and then restart your computer.

The Prefetch folder is just a cache of recently used application executables and will be recreated based upon the applications you use most frequently.  Over time the folder becomes cluttered with rarely used and prefetched applications hence the launch of applications becomes slower.

You may find following the clear down of the Prefetch folder and reboot that the first time you open each application it is still a little slow, ths is because Windows will automatically re-add the application on its first launch to the prefetch folder.  After your first use of the common applications everything should now be much faster and you should find startup times have been reduced.

Exchange, Exchange 2010, HP, Microsoft, ML350 G5, ML350 G6, ProLiant, SBS 2011, SharePoint, SharePoint 2010, SharePoint Foundation 2010, Small Business Server 2011, Windows, Windows Server 2008 R2

Windows Server 2008 R2 or Windows Small Business Server 2011 is slow to respond or may stop responding for 10-20 seconds

Leave a comment

If your Server is running Windows Server 2008 R2 Service Pack 1 or Windows Small Business Server 2011 Service Pack 1, you utilise RAID and have more than 4GB of memory then you are likely to be affected by this issue.  It seems to impact those servers running memory hungry applications such as Microsoft Exchange, Microsoft SQL Server/Express and Microsoft SharePoint the most.  It can cause the server to operate slowly and/or stop responding for 10-20 seconds to requests.

This issue is related to a limitation in the memory allocation of the storport.sys driver, this file is part of the Microsoft operating system.

All is not lost as Microsoft do provide a solution/fix. The first step is to ensure that your current RAID Controller driver is upto date, the latest version can usually be found on the server manufacturers support site or if you are not sure which update/driver applies to your system then contact the manufacturers technical support by phone or e-mail.

Please note that for HP Smart Array controllers you should be using Driver version 6.28.0.64 (Released 18th Feb 2014) or later for this change to take effect (Enables customers to make use of Microsoft HotFix which enables 64-bit command addressing described by MS KB2468345).

Now that we have the latest RAID controller driver installed lets ensure that we have the latest version of storport.sys installed, the latest version for Windows Server 2008 R2 to date is available from Microsoft using the following link http://support.microsoft.com/kb/2528357 we need this newer version of Storport because the version included with Windows Server 2008 R2 and Windows Server 2008 R2 – Service Pack 1 does not correct the memory allocation limitation.  Once the storport.sys hotfix (KB 2528357) is installed on your server you can proceed to the final step of resolving the overall issue.

The final step is to create a registry entry under the RAID miniport driver to allow it to address more than 4GB Memory via the storport.sys driver that we have updated.

We need to add a registry key so lets open Registry Editor by either typing regedit in the Start Search box or the Run Command and then pressing “Enter”

You will need to browse and locate this registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\<MINIPORT>\Parameters

In place of <MINIPORT> in the example key above you need to enter the name of the Storport miniport driver that is in use on your particular server, i have attached a screenshot of where you can find this information, the example is based upon a HP Smart Array P410i Controller (HpCISSs2) but the principle is the same for most brands of server and RAID controller.

For the HP ProLiant server this Registry key would be: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HpCISSs2\Parameters

Once in the correct key click on the “Edit” menu, click “New”, and then click “DWORD Value”

Type Supports64BitAddressing, and then press “Enter”.

Right-click Supports64BitAddressing, and then click “Modify”

In the “Value data” box, type a value of 1

Your entry should look like the screenshot below

Close the Registry Editor and Restart your Server.

Now the RAID miniport driver that uses the Storport.sys driver can access more than 4 GB of physical memory and it should resolve your performance issue.