Sure, there may be many causes of the same symptoms, but here is what fixed this problem for me.
I had only one of many Windows 7 PCs with IE11 that showed the "Access Denied" symptom when trying any JavaScript that included window.localStorage from other reputable and well-managed websites. Using Process Explorer showed that the proximal reason was ACCESS DENIED when taskhost.exe (acting on behalf of Internet Explorer) tried to open DOMStore\container.dat for Generic Read-Write. Actually it was worse: if I deleted container.dat , the same ACCESS DENIED occurred, even through the file no longer existed. And if I deleted the (hidden) DOMStore folder when taskhost.exe tried to recreate it, it also got ACCESS DENIED.
After two days of chasing false wires, the final decision was as follows:
Registry entry:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\LowCache\Extensible Cache\DOMStore\CachePath
(pay attention to LowCache in this line) was installed incorrectly:
%USERPROFILE%\AppData\Local\Microsoft\Internet Explorer\DOMStore
when it should be:
%USERPROFILE%\AppData\LocalLow\Microsoft\Internet Explorer\DOMStore
as a result, low-integrity local storage requests were sent to regions with a high degree of integrity of AppData disk storage, thereby generating ACCESS DENIED errors and killing the use of JavaScript window.localStorage .
This registry entry must have been incorrect for many years: perhaps a side effect of enthusiasm when viewing platform previews, etc. This error persisted while completely uninstalling and reinstalling IE11.
There is a similar registry entry for the medium-definition cache:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\5.0\Cache\Extensible Cache\DOMStore\CachePath
and this is true as:
%USERPROFILE%\AppData\Local\Microsoft\Internet Explorer\DOMStore
and should not be changed.
Robin Walker May 10 '14 at 15:49 2014-05-10 15:49
source share