July 20, 2010
Sometimes you just have too many conflicts when synchronizing your offline files in Windows 7 that you have to start over, but gone are the days of CTRL+SHIFT and clicking the Delete Files button in “Folder Options” like you did back in Windows XP to clear out the CSC (Client Side Cache) folder. Well, here’s how I’ve discovered how to clear the cache and start over.
There’s two methods that can use to do this and both make me feel like I’m performing open heart surgery with a chainsaw, and I have found them both affective, but I am only going to cover the Registry Method as it’s a little safer or at least seems a little safer.
DISCLAIMER: Always create a restore point before editing the registry!!! If you render your computer inoperable because of modifying your registry then you will have a better chance of recovery. I am not responsible in the event that you do turn your computer into a door stop. There, you’ve been warned.
- Make sure that your files and folder have been synchronized. Reinitializing the cache prior to synchronizing will cause you to lose any data that isn’t synchronized.
- Click Start, type regedit in the Start Search box, and then press ENTER.
If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.
- Locate the following registry subkey, and then right-click it:
- Point to New, and then click Key.
- Type Parameters in the box.
- Right-click Parameters, point to New, and then click DWORD (32-bit)Value.
- Type FormatDatabase, and then press ENTER.
- Right-click FormatDatabase, and then click Modify.
- In the Value data box, type 1, and then click OK.
- Exit Registry Editor, and then restart the computer.
This method successfully worked for me when I had to flush my Offline Files cache and it’s the same method as described in Microsoft KB Article 942974 so it should work. However, it may not fix your particular issue as all it will do is reinitialize the Offline Files. I’ve got another issue that I’m currently investigating and this was one of the troubleshooting steps.