Windows Server 2008
Updated: Feb. 21, 2014.
With more folks deploying Windows 7 and Windows Server 2008 R2, the following question is being asked…
Q: In Windows Vista and Windows Server 2008 Service Pack 1/2, you had to install the “Microsoft Windows Dynamic Cache Service” but the “System Requirements” doesn’t have Windows 7 nor Windows Server 2008 R2 listed.
Microsoft Windows Dynamic Cache Service http://www.microsoft.com/downloads/details.aspx?FamilyID=e24ade0a-5efe-43c8-b9c3-5d0ecb2f39af&displaylang=en
A: By design. The memory management algorithms in Windows 7 and Windows Server 2008 R2 operating systems were updated to address many file caching problems found in previous versions of Windows.
You do not need to install this additional service.
The updated version is available at Microsoft Windows Dynamic Cache Service http://www.microsoft.com/en-us/download/details.aspx?id=9258
For more information, please check out the following blog:
I would LOOOOOVE to have that dynamic cache tool for 2008-R2 (with SP1 + all updates) since I still have a lot of servers with that problem.
Current workaround: use supercopier for the affected copy jobs, it forces the sync more often than explorer.exe / xcopy.exe and therefore works better.
Currently I miss a command line variant which allows me to set a copy speed.
Has anyone managed to get a copy of this for 2008 R2 from Microsoft?
Yes, i received a copy of the new test/beta DynCache for Microsoft Windows 2008 R2. You need to go through the official support center in order to get it. My Case id was 112012451164142, if that helps.
I requested that fix because we have issues with HP Data Protector V6.2 (see: h20000.www2.hp.com/.../Document.jsp).
BUT, if you apply this update, there is no more support from Microsoft for this system.
Do you still have this Beta? I have asked Microsoft, but nobody knows that Software for 2008 R2.
Can you send me a copy?
Thanks a lot.
I have the same issue. Something has changed since a recent update. I upgraded from 2008 R1 64bit to R2. I was using DynCache when I noticed the problem on R1. Since going to R2 the performance is shocking. It dies not matter if I have a robocopy, xcopy or application across the network or just copying from disk to disk. I can see the FREE memory going to Zero and then the server is dead slow. I can also see Robocopy stopping every so often and then carry on. I rather go back to R1 and DynCache if I could...
Any chance of sending me a copy for testing? Mahyar.Barad@ukf.net
I am damn sure MS will post and update soon. The forums are full of entries complaining and it has nothing to do with HyperV or Server role etc... MS has broekn it and now they need to fix it. The fact that you have a new DynCache service kinds of proves it. If you could send me a copy I really appreciate it and I can properly test it
Can anyone please send me the "DynCache tool for Windows Server 2008 R2"?
Having the exact same problem with our 2008 R2 server, driving me nuts :(
I would advise you to open a ticket with Microsoft to get the fix for 2008R2 as its a private fix.
We have this problem ( support.microsoft.com/.../976618 ) with Server 2008 R2 aswell and I tried calling Microsoft technical support and they told me they no longer have the file. What can we do now?
Switch to Linux...?
Please Verify if you are facing the same issue as mentioned in the support.microsoft.com/.../976618.
If yes, I would advise you to open a support case with us to obtain the Dyncache service for the server 2008 R2 SP1.
It is a private fix currently.
You will not be charged for the support Ticket.
That is correct, I first had that in my post but they were getting a high volume of calls so they had asked me to remove that portion. I just forgot to put it back. Thanks for pointing that out Alok.
I have this issue on server 2008r2 with Storagecraft imagemanager. It renders the server completely useless. See this:
How do you raise a support case with Micrsoft. Every time I try they try and make you pay with a credit card. Can someone post a link ?
I've written a powershell script you can run on Windows 2008 R2 that uses the SetSystemFileCacheSize to set an appropriate maximum for your server. Simply run the powershell script as an administrator with elevated privileges with task scheduler on every boot.
You can find the script on
that will fix this bug
ps you can also run the script without rebooting and it will fix it on a live system too
So, now that you've finally released the DynCache service for 2008 R2 ( blogs.technet.com/b/supportingwindows/archive/2014/02/27/windows-dynamic-cache-service-updated.aspx ), why should I switch away from the SetSystemFileCache API (described on support.microsoft.com/kb/976618
) on startup to set a reasonable maximum on startup with my powershell script I posted on serverfault.com/questions/325277/windows-server-2008-r2-metafile-ram-usage/527466#527466 ? What feature benefits do you think DynCache provides that outweighs the con
of running yet another service that consumes even more resources compared to the single on startup script that exits when it has made the setting change?
Also, why is the default maximum SystemFileCache setting 90% of physical RAM with the DynCache service, that seems excessive?