Index.Dat Viewer and Zapper is a straightforward tool that does exactly what its name says: it displays the content of the “index.dat” files and allows you to delete them from your computer.Īlthough there are multiple application that can save data in “index.dat” files, this tool is designed to locate and work with the ones generated by Internet Explorer.
Your local user windows temp folder is now used for any temporary files created by the program rather than assuming it has write access to the root of C:.Useful if your index.dat files have been collected and placed in a certain folder. New preferences dialog allows you to specify a single folder to scan, rather than assuming all drives.Search empty folders on Windows with the SearchMyFiles tool.What's new in Index.Dat Viewer and Zapper 1.05:.Gilmour’s birthday yesterday!! Thanks again Nir, your new pal Mir: yes, everybody calls me Mir… That’s so funny:)!! March 9, 2013, 4:39 pm I think I will take a break first and go on Facebook and listen to Pink Floyd in honor of David My eyes are kind of hurting from looking at the screen so much. Well happy programming… I sure hope I don’t screw this up. But the problem is that I don’t have a business!! I get very paranoid and wonder why someone is monitoring me so consistently. I think someone in another country deployed an enterprise and other servers on my home premium! There are millions of files and it seems I am running a bunch of servers. This week I have to again completely reformat my hard drive as it is so corrupted. Well, now I will try to go through the steps to extract your files onto a flash drive. I hope this profession makes you a lot of money:)! You deserve it.
I just finished reading about you as well. Hi Nir, I have spent quite a bit of time reading about all these fascinating inventions of yours. Follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. This entry was posted by NirSoft on Decemat 3:34 pm under NirSoft Tips.
Remember that you have to execute BrowsingHistoryView as administrator, otherwise, it won’t be able to read the history file while it’s locked. If you have a system with Internet Explorer 10, you’re welcomed to try it and see if it’s reasonable to use this ‘Volume Shadow Copy’ method regularly. There is also an option to read the history when the database file is locked (using Volume Shadow Copy), but it’s active only when running BrowsingHistoryView.exe with /UseVolumeShadowCopy command-line parameter:īrowsingHistoryView.exe /UseVolumeShadowCopy For now, I updated only one tool, BrowsingHistoryView, for reading the browsing history of IE10. Generally, I prefer to avoid from using this ‘Volume Shadow Copy’ method and find a better way to read the locked database of IE10. The latest history/cache is written to the database a few minutes after closing the IE10 Web browser, when the file is unlocked. The copied locked database doesn’t contain the latest browsing history.On 64-bit systems, only 64-bit application can use this service.This process and quite slow and aggressive.
Reading the locked database using the ‘Volume Shadow Copy’ method has a few drawbacks: There is one solution to bypass this database locking problem – by copying the database into another location using ‘Volume Shadow Copy’ service and then reading the copy of the database.
I have already developed the code to read this file in order to update my tools for Internet Explorer 10, but there is still one major problem with this file: While Internet Explorer is opened, and also a few minutes after it’s closed, this file is completely locked, and other software (like my tools) cannot open it. This database file is WebCacheV24.dat, and it’s located under C:\Users\\AppData\Local\Microsoft\Windows\WebCache folder Instead of the old index.dat file, IE10 stores all cache/history information inside a single Jet Blue database (Also known as ESE database or.
Recently, I have received multiple reports from users of Internet Explorer 10 ( On Windows 8 ) saying that my history/cache utilities fail to work with IE10, and they are right…Īs opposed to all previous versions of Internet Explorer that used the same file structure to store the history/cache/cookies information, IE10 uses a completely new file structure.