Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

20
  • 26
    this is great solution. i need to cleanup my SSD c drive by moving files to other drive. many thanks
    – marek
    Commented Aug 15, 2013 at 16:34
  • 9
    +1 for Hardlink Shell Extension. Couldn't live without it.
    – Dennis G
    Commented Dec 15, 2013 at 12:47
  • 248
    Dear Microsoft: Please do not use the name "cache" to describe a folder that causes this much headache when deleted. Thanks. Commented May 11, 2016 at 23:27
  • 11
    Did the trick with moving to another drive and making a junction. Running VS2015 SP3 installer today, the installer caused the junction to devolve to a normal directory (possibly when uninstalling an older version of some component, it recursed through "empty" parent directories removing them -- there are known problems with junctions and naive empty directory tests). So it placed new components in C:\ProgramData\Package Cache and then failed to find items in the new location where the junction formerly pointed. Just a warning to future readers the junction may need to be re-established.
    – Ben Voigt
    Commented Jul 19, 2016 at 21:15
  • 5
    As a more permanent fix, use NTFS permissions and deny "delete" permission on the junction itself.
    – Ben Voigt
    Commented Jul 19, 2016 at 21:15