Prevent IE10 from creating WebCache through Group Policy

IE10 implemented the WebCache which appears to be the new way of doing Temporary Internet Files.
The location of this is C:\Users\\AppData\Local\Microsoft\Windows\WebCache

In my situation we have a terminal server where the user profiles are limited to 15MB of disk space, which has always been more than enough prior to installing IE10. The new WebCache folder has increased the amount of disk space required by nearly 500%, and while space is cheap there is a technical limitation which requires the quotas to be set low.

I have investigated the group policy settings, and there are a bunch of line items that are specific to IE10. Two items of note are 'Allow websites to store indexed databases on client computers' and 'Allow websites to store application caches on client computers', both of which I have set to disabled. It appears however that these items refer to something else, as the WebCache files continue to be re-created.

There doesn't seem to be a lot of talk on the internet about this being an issue, though the few incidents I have read about have had similar trouble reigning in the size of this WebCache folder.

So far the only thing that seems to work is revoking the users permission to access the WebCache folder. While this works, it is far from what I would consider to be a recommended solution.

Does anyone have any insight into how I can limit the file size of the WebCache or prevent it from existing all together via GPO?

Solution 1:

Webcache is part of WinINET and is loaded before IE (as other WinINET. To stop the caching you need to tell WinINET to stop caching.

Credit to http://www.tenforums.com/general-support/37841-disable-webcachev01-dat.html

First, stop the following task in task scheduler: Microsoft > Windows > Wininet

Second step is to delete the dcom REGEDIT search for this GUID:{3EB3C877-1F16-487C-9050-104DBCD66683} Delete this GUID You will have to change the ownership to your user to be able to delete this key.

Not pretty but it seems IE is piggybacking WinINET