C drive space is using up on terminal server after upgrading to IE10 or IE11

If you are an IT administrator and decide to upgrade to IE10 or IE11 on your Windows 2008 R2 terminal server, you’d better read this article carefully first before taking any action. It is very possible that your C drive space will be eaten up after several days. Why and how could this happen?

Starts from IE10, IE moves the browser cache to a Jet Blue database(also known as ESC database or .edb file), and the old index.dat memory-mapped file is obsoleted. You may read this blog to learn the benefits of this change, this is not the key topic in our article. With the new cache implementation, the cache files are saved in %LocalAppData%\Microsoft\Windows\WebCache\ folder. And, the cache files will be created when a new user logs on.

Actually, the database is a file named WebCacheV01.dat in the cache folder, and its initial size could be around 20-32MB. The size of this file will keep increasing along with you browse more and more websites. Unfortunately, there’s no way to control the initial size of this database, in another word, the minimal size of this file could be >20MB. Now, let’s suppose there are 1000+ users for this terminal server, then totally >20,000MB space is required for every user’s cache database file at least. In this situation, your C drive space will be probably used up as time goes on.

Then, how to avoid the happening of the subjected issue? Maybe you are thinking about deleting the cache files, right? Exactly, this is the only way to resolve the issue. However, the problem is, you are unable to delete the cache files manually even you are a local admin of this server. Don’t worry, here’s a batch file which can help to delete the cache files. Please save the below contents into ClearIECache.cmd file and try to fun this file.

echo OFF

net stop COMSysApp

taskkill /F /IM dllhost.exe

taskkill /F /IM taskhost.exe

taskkill /F /IM taskhostex.exe

del /Q %LocalAppData%\Microsoft\Windows\WebCache\*.*

net start COMSysApp

echo ON

Furthermore, you’d better deploy the batch file to a logoff script of your local GPO, here are the steps.

1. Copy the batch file to C:\Windows\System32\GroupPolicy\User\Scripts\Logoff folder

2. Run “gpedit.msc” to open “Local Group Policy Editor”

3. Go to User Configuration->Windows Settings->Scripts (Logon/Logoff), refer to the below picture



4. Double click “Logoff” to add a logoff script. Please click the “Add…” button to specify the script file to C:\Windows\System32\GroupPolicy\User\Scripts\Logoff\ClearIECache.cmd. Refer to the below picture.



5. Click OK to finish the setting





Zhixing Lv from GBSD DSI Team

Comments (2)

  1. ppindia says:

    I look at this problem as a bug. why is the cache file created even when the user has not used IE(Login into server is not sufficient for creating file)!

  2. Zhixing Lv says:

    A: The cache is an integral part of WinINET, a core networking component in Windows. WinINET’s cache isn’t just the browser’s cache—it’s also used by most Metro applications, Windows components, and tens of thousands of other applications that rely on WinINET. That’s why, for instance, when you uninstall IE from Windows, WinINET and its data stores remain on the system. The database is loaded by the cache service in order to handle requests from applications that depend on WinINET. Deleting the database would be very bad from a privacy point of view, because the database tracks which files need to be deleted when you use the Delete Browser History / Clear Cache commands. If you were to obliterate this index, these files would be orphaned and present a privacy risk.

    Refer to http://www.ericlawrence.com/…/show.asp

    Zhixing Lv

Skip to main content