Can I delete MSOCache?












85














I need more space on my SSD drive and I found that MSOCache is occupying 1.3 GB. I have Microsoft Office 2010 installed.



Can I safely delete MSOCache?










share|improve this question






















  • Maybe related: Can I delete the folder “C:WINDOWSInstaller$PatchCache$”? (I am not on Windows, so maybe I'm wrong here?)
    – Arjan
    Dec 2 '10 at 22:55






  • 9




    I would say they're unrelated.
    – oKtosiTe
    Dec 6 '10 at 17:14
















85














I need more space on my SSD drive and I found that MSOCache is occupying 1.3 GB. I have Microsoft Office 2010 installed.



Can I safely delete MSOCache?










share|improve this question






















  • Maybe related: Can I delete the folder “C:WINDOWSInstaller$PatchCache$”? (I am not on Windows, so maybe I'm wrong here?)
    – Arjan
    Dec 2 '10 at 22:55






  • 9




    I would say they're unrelated.
    – oKtosiTe
    Dec 6 '10 at 17:14














85












85








85


26





I need more space on my SSD drive and I found that MSOCache is occupying 1.3 GB. I have Microsoft Office 2010 installed.



Can I safely delete MSOCache?










share|improve this question













I need more space on my SSD drive and I found that MSOCache is occupying 1.3 GB. I have Microsoft Office 2010 installed.



Can I safely delete MSOCache?







windows microsoft-office






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 29 '10 at 15:59









DrakeDrake

2,935134470




2,935134470












  • Maybe related: Can I delete the folder “C:WINDOWSInstaller$PatchCache$”? (I am not on Windows, so maybe I'm wrong here?)
    – Arjan
    Dec 2 '10 at 22:55






  • 9




    I would say they're unrelated.
    – oKtosiTe
    Dec 6 '10 at 17:14


















  • Maybe related: Can I delete the folder “C:WINDOWSInstaller$PatchCache$”? (I am not on Windows, so maybe I'm wrong here?)
    – Arjan
    Dec 2 '10 at 22:55






  • 9




    I would say they're unrelated.
    – oKtosiTe
    Dec 6 '10 at 17:14
















Maybe related: Can I delete the folder “C:WINDOWSInstaller$PatchCache$”? (I am not on Windows, so maybe I'm wrong here?)
– Arjan
Dec 2 '10 at 22:55




Maybe related: Can I delete the folder “C:WINDOWSInstaller$PatchCache$”? (I am not on Windows, so maybe I'm wrong here?)
– Arjan
Dec 2 '10 at 22:55




9




9




I would say they're unrelated.
– oKtosiTe
Dec 6 '10 at 17:14




I would say they're unrelated.
– oKtosiTe
Dec 6 '10 at 17:14










8 Answers
8






active

oldest

votes


















60





+50









Short answer: no. You would most likely no longer be able to perform a repair or install additional components.

I have tried it myself on a virtual machine running Windows 7 with Office 2007–I imagine it would have the same effect on Office 2010.



A safer option (as suggested here) is to burn the folder itself to DVD or move it to a USB drive, and change all references to it in the Windows registry.



From that page:




Solution, what I did recently:




  1. Burn that whole folder to a CD-R or DVD (the filesize of that folder
    depends upon your Office version).

  2. Delete that folder.

  3. Search the registry in RegEdit for C:MSOCache and change all references
    to point to your CD/DVD drive,
    example:
    E:MSOCache (will of course require the disc when something Office related needs those cache files.)







share|improve this answer



















  • 2




    Little "hacky" but should work fine
    – zzeroo
    Dec 2 '10 at 15:52






  • 1




    I finally tried, and it seems working.
    – Drake
    Dec 9 '10 at 8:24






  • 1




    It took about 10 minutes to find and replace all occurances of C:MSOCache...
    – Dean Kuga
    Nov 18 '11 at 17:31






  • 2




    Is there any particular reason you cannot simply stash this folder on a separate drive (assuming Drake has a larger storage drive), then create a directory junction so C:MSOCache references the other drive? Then you wouldn't have to edit the registry.
    – stylez
    Apr 28 '13 at 3:54










  • @stylez: No, but I wouldn't recommend making a junction to en external drive.
    – oKtosiTe
    May 1 '13 at 16:18





















50














Way to go would be Junction Point.



For example, if you have 120 GB SSD Drive as C:, and 3TB Drive (Magnetic) HDD as D::




  • on drive D: create sub folder named C

  • cut and paste folder MSOCache to subfolder C located on drive D:

  • run CMD

  • type: CD

  • type: MKLINK /J MSOCache D:CMSOCache

  • type: EXIT


After this you will have entire content of MSOCache folder in path C:MSOCache, but physically files would be located on D:CMSOCache.





That was the answer about MSOCache folder on C drive.
Now let us talk about a real problem, the same one I experienced few hours ago.



NOT ENOUGH SPACE ON SSD DISK AS C: DRIVE



The main problem here is Windows Installer, and their crappy system of caching all old installation files.
Every old version of some software that once existed on your PC Windows Installer keeps in his cache folder. Stupid thing, don't you think (only because someone might Uninstall some application Windows Installer keeps all files so it could roll back to the previous state - in simplified version - believe me it's much more complicated, but accept this as is).



This wouldn't be much of problem if there aren't even bigger stupidness again from Microsoft, of course, called Windows Updates. That simply floods you with updates.
And what are the Updates!? Nobody!? Updates == Installations == Bigger and bigger Windows Installation Cache.



My situation was I've installed literally base development PC with minimal Office + VS2005, VS2008, VS2010 - That is I must have. I had this on XP machine primary disk with 120 GB just fine and plenty of drive space left with all updates installed (~100GB).
But Windows 7 == 30 GB free space (Imagine my face when I saw that).
I know windows 7 is little bigger but not 70GB bigger.



... and now 2 hours later I am back to 70 GB ;)
HOW you ask me!?



Simply performed same thing as above for following folders:




  • C:WindowsInstaller

  • C:WindowsSoftwareDistribution


Commands are very similar:




  • move above folders to (for example) D:CWINDOWS

  • run CMD elevated as an administrator

  • type: CD C:WINDOWS

  • type: MKLINK /J Installer D:CWindowsInstaller

  • type: MKLINK /J SoftwareDistribution D:CWindowsSoftwareDistribution

  • type: EXIT


Notice only to stop Windows Update, Trusted Installer, and Windows Installer services before moving those folders, run them after if you wish or simply restart (10 seconds for a reboot on SSD).



I have reclaimed back 40GB of (100% uselessly taken space, since I will never uninstall anything I use). Haven't broken any windows rules, since they use for Documents and Settings same Junction Point to Users although on same drive...



Still poking around what else I could move to (Magnetic) HDD drive...
One thing to notice you will have winSxS subfolder in Windows folder DO NOT MOVE this folder as it would defy the purpose of Solid State Disk (fast loading of applications). WinSxS is a folder where all Side by Side dll's are located (and prety much every application uses something from there).
This is also Microsoft's solution for DLL version HELL, if you wonder why it exists.






share|improve this answer























  • This is really the safer solution. It should be marked as correct answer! Thanks mate!
    – psulek
    Mar 25 '14 at 15:12










  • Is it ok to do this with User folder, or better say with AppData folder which is around 10GB on my machine? Btw great answer.
    – nemke
    Jun 2 '15 at 14:48










  • uh, AppData is already an Junction Point, although on same drive. What you need is to locate real folder C:Users<username>AppDataRoaming and move that one to other drive. Now that being said, AppData contains software data on your computer, like configurations, caches, databases, and other data. If you move this to other drive it might defy the purpose of solid state drive. I would try to find what subdirectories use this much of space in AppData folder. And see to what software it belongs, and if I am not actively using these software I would move them, instead of entire AppData folder.
    – SoLaR
    Jan 8 '16 at 17:46










  • If you have a problem on moving SoftwareDistribution folder, it is about "Windows Update is running". Stop Windows Update on services and than try to move that folder. By the way, you save my ssd man, brilliant...
    – matasoy
    Jul 5 '17 at 21:44





















12














The Local Install Source (Msocache) feature is installed so that you do not have to insert the CD during the following Setup operations:




  • Detect and Repair

  • Demand Install

  • Maintenance Mode Setup

  • Installation of service packs and patches


You can use the Windows Cleanup Wizard to remove the Msocache folder. To do this, follow the steps in the related Microsoft article.



Warning: Never delete the MSOCACHE folder by using Microsoft Windows Explorer.






share|improve this answer























  • I followed the guide. It removed my about 100MB-200MB but there are still 1.2 GB in that folder now.
    – Drake
    Nov 29 '10 at 16:23












  • Another work around could be to create a system restore point (call it "safe"), delete the content of the folder completely, work for a few days in this wise, and go back to "safe" if you face any problems.
    – Mehper C. Palavuzlar
    Nov 29 '10 at 16:27












  • This MS article suggests another solution. Check out Q4 and A4.
    – Mehper C. Palavuzlar
    Nov 29 '10 at 16:31










  • that article refers to Microsoft Office 2003. I tried download and install LISTool.exe anyway, but it seems not compatible with Microsoft Office 2010
    – Drake
    Dec 1 '10 at 8:13










  • Then I can only suggest you try what I pointed in my first comment (system restore).
    – Mehper C. Palavuzlar
    Dec 1 '10 at 8:19



















6














The best way to prevent this folder from being placed on your drive in the first place, is by selecting the Delete installation files check-box during the installation of Office.



From this thread :




If you delete it this is what will happen:




  • MS Office's repair function won't work from the hard disk cache anymore - will require the CD to fix it.

  • Microsoft Updates for Office that require the cache won't work from the
    hard disk cache anymore - will require
    the CD to install them.


Solution, what I did recently:




  1. Burn that whole folder to a CD-R or DVD (the filesize of that folder
    depends upon your Office version).

  2. Delete that folder.

  3. Search the registry in regEdit for C:MSOCache and change all references
    to point to your CD/DVD drive,
    example: E:MSOCache (will of course
    require the disc when something
    Office-related needs those cache
    files.)







share|improve this answer

















  • 1




    It seems we found the same page...
    – oKtosiTe
    Dec 2 '10 at 15:26






  • 1




    @oKtosiTe: Yah, and on the same minute, too. Great minds think alike ...
    – harrymc
    Dec 2 '10 at 15:40



















3














I wonder if anyone who's against deletion of this folder have actually met any problems after that in the real life.



I've been shift+deleting this MSOCache since I've seen it for the very first time back in 2003 or so, and have never had any problems with updating or using Microsoft Office after that.



My answer is yes, you may safely delete C:MSOCache folder with no regrets in case you have installation media you may use later in case it is required.






share|improve this answer























  • This answer may sound flippant and unconsidered, but it is one of the best ones here. I've been using office for about 20 years, and the MSOCache directory is the first thing to go after installation. It's in the wrong place, and I've never seen its necessity demonstrated. What's the worst that can happen? Needing to spend a few minutes reinstalling from media without some cached files? After reading this thread I now RAR archive the folder and put it in backup just in case, but I have never once seen a single consequence of just deleting it. Only a problem for enterprise IT types.
    – chronometric
    May 11 '17 at 16:09





















2














I have a 64GB SSD and LOADS of programs. I regularly move space gluttons to a HDD. Many programs now use 500MB-1.3GB for garbage like page borders and all sorts of small image files.



Don't screw with the registry. Sooner or later it'll bite you in the butt bigtime. Create a junction, as mentioned in SoLaR's answer.



HOWEVER -- SOME CAVEATS.




  1. Don't delete the original folder. Rename it with a minus sign, i.e.,

    rename MSOCache to -MSOCache.



  2. MSOCache is an anomaly in that it is in a root folder. Normally you are moving something in a subfolder. So you'll have to modify the following where it says "put in the parent folder".



    In the PARENT folder of the subfolder you are moving, create a TEXT file called JUNCTION LIST.txt with the contents shown below. So if you are moving C:Program FilesAdobeSpacehog you would put the "JUNCTION LIST.txt" file in C:Program FilesAdobe



    CONTENTS OF JUNCTION LIST.txt (of course, modified to your particular case):



    SSD Win 7
    C:ProgramDataAdobeCameraRaw

    was replaced with a junction to

    S:Program_DataAdobeCameraRaw

    mklink /j CameraRaw "S:Program_DataAdobeCameraRaw"


    (Add any others, as needed.)



    The JUNCTION LIST.txt should document EXACTLY what you did.



  3. Open a command prompt in the PARENT folder of the subfolder you are moving.


  4. COPY the "mklink ..." line from the DOCUMENTATION file. This means highlight and press Ctrl-C.



  5. PASTE the command at the prompt, and press enter.



    If it doesn't work, DO NOT make ANY corrections to the command line. Correct the DOCUMENTATION file and repeat the copy and paste.



    You should now have the original folder name with a minus sign and a junction with the original filename.



  6. Move everything from the "minus" folder to the junction.


  7. Copy the JUNCTION LIST.txt folder to the PARENT folder of the TARGET folder on the other drive. The idea is to have documentation all over the place.


  8. Now, except that you have an actual folder with a "minus" name, everything should look the same as before you started.


  9. DO NOT rename the target folder. That destroys the junction. If you need to rename the target folder, delete the junction, correct the JUNCTION LIST.txt file, and create a new junction.







share|improve this answer























  • Related: How to search for all junction links in a given directories and its subdirectories.
    – Arjan
    Jun 15 '14 at 8:02



















1














Very similar to previous answers - the twist is I moved C:MSOCache to my second HD, D:MSOCache and then all I had to do is use regedit to change all references from C:MSOCache to D:MSOCache for an overall quick and painless way to free-up a sizable chunk of space on the C: drive.






share|improve this answer























  • Creating a junction point which points to the new location is much safer solution. It's completely transparent (applications don't recognize it's not a real directory but junction point), it's easier since you don't need to search and change anything in the registry and it will work even if an application uses a hard-coded path (developer for example simply forgot to read that path from the registry).
    – Dawid Ferenczy
    Feb 29 '16 at 1:44





















0














Yes, you can delete the MSOCache folder, if when you install MS Office, you select the option to "Run all from My Computer".



Install office, then delete MSOCache



Check that option under Microsoft Office, then check Not Available for the components you don't need. I've installed only Excel (tons faster than LibreCalc), Word and PowerPoint, then I've renamed MSOCache to "junk.MSOCache.deleteme". I don't plan to install any other Office components.



So far, no problems. Haven't tried installing any Office updates because I don't need any security patches (the only Office files I use are my own), but if you want the updates, install them first and delete/rename MSOCache after.



UPDATE: I've also deleted the MSOCache folder from a Wine installation of Office on Linux, and Excel works just fine.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f216300%2fcan-i-delete-msocache%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    8 Answers
    8






    active

    oldest

    votes








    8 Answers
    8






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    60





    +50









    Short answer: no. You would most likely no longer be able to perform a repair or install additional components.

    I have tried it myself on a virtual machine running Windows 7 with Office 2007–I imagine it would have the same effect on Office 2010.



    A safer option (as suggested here) is to burn the folder itself to DVD or move it to a USB drive, and change all references to it in the Windows registry.



    From that page:




    Solution, what I did recently:




    1. Burn that whole folder to a CD-R or DVD (the filesize of that folder
      depends upon your Office version).

    2. Delete that folder.

    3. Search the registry in RegEdit for C:MSOCache and change all references
      to point to your CD/DVD drive,
      example:
      E:MSOCache (will of course require the disc when something Office related needs those cache files.)







    share|improve this answer



















    • 2




      Little "hacky" but should work fine
      – zzeroo
      Dec 2 '10 at 15:52






    • 1




      I finally tried, and it seems working.
      – Drake
      Dec 9 '10 at 8:24






    • 1




      It took about 10 minutes to find and replace all occurances of C:MSOCache...
      – Dean Kuga
      Nov 18 '11 at 17:31






    • 2




      Is there any particular reason you cannot simply stash this folder on a separate drive (assuming Drake has a larger storage drive), then create a directory junction so C:MSOCache references the other drive? Then you wouldn't have to edit the registry.
      – stylez
      Apr 28 '13 at 3:54










    • @stylez: No, but I wouldn't recommend making a junction to en external drive.
      – oKtosiTe
      May 1 '13 at 16:18


















    60





    +50









    Short answer: no. You would most likely no longer be able to perform a repair or install additional components.

    I have tried it myself on a virtual machine running Windows 7 with Office 2007–I imagine it would have the same effect on Office 2010.



    A safer option (as suggested here) is to burn the folder itself to DVD or move it to a USB drive, and change all references to it in the Windows registry.



    From that page:




    Solution, what I did recently:




    1. Burn that whole folder to a CD-R or DVD (the filesize of that folder
      depends upon your Office version).

    2. Delete that folder.

    3. Search the registry in RegEdit for C:MSOCache and change all references
      to point to your CD/DVD drive,
      example:
      E:MSOCache (will of course require the disc when something Office related needs those cache files.)







    share|improve this answer



















    • 2




      Little "hacky" but should work fine
      – zzeroo
      Dec 2 '10 at 15:52






    • 1




      I finally tried, and it seems working.
      – Drake
      Dec 9 '10 at 8:24






    • 1




      It took about 10 minutes to find and replace all occurances of C:MSOCache...
      – Dean Kuga
      Nov 18 '11 at 17:31






    • 2




      Is there any particular reason you cannot simply stash this folder on a separate drive (assuming Drake has a larger storage drive), then create a directory junction so C:MSOCache references the other drive? Then you wouldn't have to edit the registry.
      – stylez
      Apr 28 '13 at 3:54










    • @stylez: No, but I wouldn't recommend making a junction to en external drive.
      – oKtosiTe
      May 1 '13 at 16:18
















    60





    +50







    60





    +50



    60




    +50




    Short answer: no. You would most likely no longer be able to perform a repair or install additional components.

    I have tried it myself on a virtual machine running Windows 7 with Office 2007–I imagine it would have the same effect on Office 2010.



    A safer option (as suggested here) is to burn the folder itself to DVD or move it to a USB drive, and change all references to it in the Windows registry.



    From that page:




    Solution, what I did recently:




    1. Burn that whole folder to a CD-R or DVD (the filesize of that folder
      depends upon your Office version).

    2. Delete that folder.

    3. Search the registry in RegEdit for C:MSOCache and change all references
      to point to your CD/DVD drive,
      example:
      E:MSOCache (will of course require the disc when something Office related needs those cache files.)







    share|improve this answer














    Short answer: no. You would most likely no longer be able to perform a repair or install additional components.

    I have tried it myself on a virtual machine running Windows 7 with Office 2007–I imagine it would have the same effect on Office 2010.



    A safer option (as suggested here) is to burn the folder itself to DVD or move it to a USB drive, and change all references to it in the Windows registry.



    From that page:




    Solution, what I did recently:




    1. Burn that whole folder to a CD-R or DVD (the filesize of that folder
      depends upon your Office version).

    2. Delete that folder.

    3. Search the registry in RegEdit for C:MSOCache and change all references
      to point to your CD/DVD drive,
      example:
      E:MSOCache (will of course require the disc when something Office related needs those cache files.)








    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Dec 8 '10 at 11:17

























    answered Dec 2 '10 at 15:19









    oKtosiTeoKtosiTe

    6,09183868




    6,09183868








    • 2




      Little "hacky" but should work fine
      – zzeroo
      Dec 2 '10 at 15:52






    • 1




      I finally tried, and it seems working.
      – Drake
      Dec 9 '10 at 8:24






    • 1




      It took about 10 minutes to find and replace all occurances of C:MSOCache...
      – Dean Kuga
      Nov 18 '11 at 17:31






    • 2




      Is there any particular reason you cannot simply stash this folder on a separate drive (assuming Drake has a larger storage drive), then create a directory junction so C:MSOCache references the other drive? Then you wouldn't have to edit the registry.
      – stylez
      Apr 28 '13 at 3:54










    • @stylez: No, but I wouldn't recommend making a junction to en external drive.
      – oKtosiTe
      May 1 '13 at 16:18
















    • 2




      Little "hacky" but should work fine
      – zzeroo
      Dec 2 '10 at 15:52






    • 1




      I finally tried, and it seems working.
      – Drake
      Dec 9 '10 at 8:24






    • 1




      It took about 10 minutes to find and replace all occurances of C:MSOCache...
      – Dean Kuga
      Nov 18 '11 at 17:31






    • 2




      Is there any particular reason you cannot simply stash this folder on a separate drive (assuming Drake has a larger storage drive), then create a directory junction so C:MSOCache references the other drive? Then you wouldn't have to edit the registry.
      – stylez
      Apr 28 '13 at 3:54










    • @stylez: No, but I wouldn't recommend making a junction to en external drive.
      – oKtosiTe
      May 1 '13 at 16:18










    2




    2




    Little "hacky" but should work fine
    – zzeroo
    Dec 2 '10 at 15:52




    Little "hacky" but should work fine
    – zzeroo
    Dec 2 '10 at 15:52




    1




    1




    I finally tried, and it seems working.
    – Drake
    Dec 9 '10 at 8:24




    I finally tried, and it seems working.
    – Drake
    Dec 9 '10 at 8:24




    1




    1




    It took about 10 minutes to find and replace all occurances of C:MSOCache...
    – Dean Kuga
    Nov 18 '11 at 17:31




    It took about 10 minutes to find and replace all occurances of C:MSOCache...
    – Dean Kuga
    Nov 18 '11 at 17:31




    2




    2




    Is there any particular reason you cannot simply stash this folder on a separate drive (assuming Drake has a larger storage drive), then create a directory junction so C:MSOCache references the other drive? Then you wouldn't have to edit the registry.
    – stylez
    Apr 28 '13 at 3:54




    Is there any particular reason you cannot simply stash this folder on a separate drive (assuming Drake has a larger storage drive), then create a directory junction so C:MSOCache references the other drive? Then you wouldn't have to edit the registry.
    – stylez
    Apr 28 '13 at 3:54












    @stylez: No, but I wouldn't recommend making a junction to en external drive.
    – oKtosiTe
    May 1 '13 at 16:18






    @stylez: No, but I wouldn't recommend making a junction to en external drive.
    – oKtosiTe
    May 1 '13 at 16:18















    50














    Way to go would be Junction Point.



    For example, if you have 120 GB SSD Drive as C:, and 3TB Drive (Magnetic) HDD as D::




    • on drive D: create sub folder named C

    • cut and paste folder MSOCache to subfolder C located on drive D:

    • run CMD

    • type: CD

    • type: MKLINK /J MSOCache D:CMSOCache

    • type: EXIT


    After this you will have entire content of MSOCache folder in path C:MSOCache, but physically files would be located on D:CMSOCache.





    That was the answer about MSOCache folder on C drive.
    Now let us talk about a real problem, the same one I experienced few hours ago.



    NOT ENOUGH SPACE ON SSD DISK AS C: DRIVE



    The main problem here is Windows Installer, and their crappy system of caching all old installation files.
    Every old version of some software that once existed on your PC Windows Installer keeps in his cache folder. Stupid thing, don't you think (only because someone might Uninstall some application Windows Installer keeps all files so it could roll back to the previous state - in simplified version - believe me it's much more complicated, but accept this as is).



    This wouldn't be much of problem if there aren't even bigger stupidness again from Microsoft, of course, called Windows Updates. That simply floods you with updates.
    And what are the Updates!? Nobody!? Updates == Installations == Bigger and bigger Windows Installation Cache.



    My situation was I've installed literally base development PC with minimal Office + VS2005, VS2008, VS2010 - That is I must have. I had this on XP machine primary disk with 120 GB just fine and plenty of drive space left with all updates installed (~100GB).
    But Windows 7 == 30 GB free space (Imagine my face when I saw that).
    I know windows 7 is little bigger but not 70GB bigger.



    ... and now 2 hours later I am back to 70 GB ;)
    HOW you ask me!?



    Simply performed same thing as above for following folders:




    • C:WindowsInstaller

    • C:WindowsSoftwareDistribution


    Commands are very similar:




    • move above folders to (for example) D:CWINDOWS

    • run CMD elevated as an administrator

    • type: CD C:WINDOWS

    • type: MKLINK /J Installer D:CWindowsInstaller

    • type: MKLINK /J SoftwareDistribution D:CWindowsSoftwareDistribution

    • type: EXIT


    Notice only to stop Windows Update, Trusted Installer, and Windows Installer services before moving those folders, run them after if you wish or simply restart (10 seconds for a reboot on SSD).



    I have reclaimed back 40GB of (100% uselessly taken space, since I will never uninstall anything I use). Haven't broken any windows rules, since they use for Documents and Settings same Junction Point to Users although on same drive...



    Still poking around what else I could move to (Magnetic) HDD drive...
    One thing to notice you will have winSxS subfolder in Windows folder DO NOT MOVE this folder as it would defy the purpose of Solid State Disk (fast loading of applications). WinSxS is a folder where all Side by Side dll's are located (and prety much every application uses something from there).
    This is also Microsoft's solution for DLL version HELL, if you wonder why it exists.






    share|improve this answer























    • This is really the safer solution. It should be marked as correct answer! Thanks mate!
      – psulek
      Mar 25 '14 at 15:12










    • Is it ok to do this with User folder, or better say with AppData folder which is around 10GB on my machine? Btw great answer.
      – nemke
      Jun 2 '15 at 14:48










    • uh, AppData is already an Junction Point, although on same drive. What you need is to locate real folder C:Users<username>AppDataRoaming and move that one to other drive. Now that being said, AppData contains software data on your computer, like configurations, caches, databases, and other data. If you move this to other drive it might defy the purpose of solid state drive. I would try to find what subdirectories use this much of space in AppData folder. And see to what software it belongs, and if I am not actively using these software I would move them, instead of entire AppData folder.
      – SoLaR
      Jan 8 '16 at 17:46










    • If you have a problem on moving SoftwareDistribution folder, it is about "Windows Update is running". Stop Windows Update on services and than try to move that folder. By the way, you save my ssd man, brilliant...
      – matasoy
      Jul 5 '17 at 21:44


















    50














    Way to go would be Junction Point.



    For example, if you have 120 GB SSD Drive as C:, and 3TB Drive (Magnetic) HDD as D::




    • on drive D: create sub folder named C

    • cut and paste folder MSOCache to subfolder C located on drive D:

    • run CMD

    • type: CD

    • type: MKLINK /J MSOCache D:CMSOCache

    • type: EXIT


    After this you will have entire content of MSOCache folder in path C:MSOCache, but physically files would be located on D:CMSOCache.





    That was the answer about MSOCache folder on C drive.
    Now let us talk about a real problem, the same one I experienced few hours ago.



    NOT ENOUGH SPACE ON SSD DISK AS C: DRIVE



    The main problem here is Windows Installer, and their crappy system of caching all old installation files.
    Every old version of some software that once existed on your PC Windows Installer keeps in his cache folder. Stupid thing, don't you think (only because someone might Uninstall some application Windows Installer keeps all files so it could roll back to the previous state - in simplified version - believe me it's much more complicated, but accept this as is).



    This wouldn't be much of problem if there aren't even bigger stupidness again from Microsoft, of course, called Windows Updates. That simply floods you with updates.
    And what are the Updates!? Nobody!? Updates == Installations == Bigger and bigger Windows Installation Cache.



    My situation was I've installed literally base development PC with minimal Office + VS2005, VS2008, VS2010 - That is I must have. I had this on XP machine primary disk with 120 GB just fine and plenty of drive space left with all updates installed (~100GB).
    But Windows 7 == 30 GB free space (Imagine my face when I saw that).
    I know windows 7 is little bigger but not 70GB bigger.



    ... and now 2 hours later I am back to 70 GB ;)
    HOW you ask me!?



    Simply performed same thing as above for following folders:




    • C:WindowsInstaller

    • C:WindowsSoftwareDistribution


    Commands are very similar:




    • move above folders to (for example) D:CWINDOWS

    • run CMD elevated as an administrator

    • type: CD C:WINDOWS

    • type: MKLINK /J Installer D:CWindowsInstaller

    • type: MKLINK /J SoftwareDistribution D:CWindowsSoftwareDistribution

    • type: EXIT


    Notice only to stop Windows Update, Trusted Installer, and Windows Installer services before moving those folders, run them after if you wish or simply restart (10 seconds for a reboot on SSD).



    I have reclaimed back 40GB of (100% uselessly taken space, since I will never uninstall anything I use). Haven't broken any windows rules, since they use for Documents and Settings same Junction Point to Users although on same drive...



    Still poking around what else I could move to (Magnetic) HDD drive...
    One thing to notice you will have winSxS subfolder in Windows folder DO NOT MOVE this folder as it would defy the purpose of Solid State Disk (fast loading of applications). WinSxS is a folder where all Side by Side dll's are located (and prety much every application uses something from there).
    This is also Microsoft's solution for DLL version HELL, if you wonder why it exists.






    share|improve this answer























    • This is really the safer solution. It should be marked as correct answer! Thanks mate!
      – psulek
      Mar 25 '14 at 15:12










    • Is it ok to do this with User folder, or better say with AppData folder which is around 10GB on my machine? Btw great answer.
      – nemke
      Jun 2 '15 at 14:48










    • uh, AppData is already an Junction Point, although on same drive. What you need is to locate real folder C:Users<username>AppDataRoaming and move that one to other drive. Now that being said, AppData contains software data on your computer, like configurations, caches, databases, and other data. If you move this to other drive it might defy the purpose of solid state drive. I would try to find what subdirectories use this much of space in AppData folder. And see to what software it belongs, and if I am not actively using these software I would move them, instead of entire AppData folder.
      – SoLaR
      Jan 8 '16 at 17:46










    • If you have a problem on moving SoftwareDistribution folder, it is about "Windows Update is running". Stop Windows Update on services and than try to move that folder. By the way, you save my ssd man, brilliant...
      – matasoy
      Jul 5 '17 at 21:44
















    50












    50








    50






    Way to go would be Junction Point.



    For example, if you have 120 GB SSD Drive as C:, and 3TB Drive (Magnetic) HDD as D::




    • on drive D: create sub folder named C

    • cut and paste folder MSOCache to subfolder C located on drive D:

    • run CMD

    • type: CD

    • type: MKLINK /J MSOCache D:CMSOCache

    • type: EXIT


    After this you will have entire content of MSOCache folder in path C:MSOCache, but physically files would be located on D:CMSOCache.





    That was the answer about MSOCache folder on C drive.
    Now let us talk about a real problem, the same one I experienced few hours ago.



    NOT ENOUGH SPACE ON SSD DISK AS C: DRIVE



    The main problem here is Windows Installer, and their crappy system of caching all old installation files.
    Every old version of some software that once existed on your PC Windows Installer keeps in his cache folder. Stupid thing, don't you think (only because someone might Uninstall some application Windows Installer keeps all files so it could roll back to the previous state - in simplified version - believe me it's much more complicated, but accept this as is).



    This wouldn't be much of problem if there aren't even bigger stupidness again from Microsoft, of course, called Windows Updates. That simply floods you with updates.
    And what are the Updates!? Nobody!? Updates == Installations == Bigger and bigger Windows Installation Cache.



    My situation was I've installed literally base development PC with minimal Office + VS2005, VS2008, VS2010 - That is I must have. I had this on XP machine primary disk with 120 GB just fine and plenty of drive space left with all updates installed (~100GB).
    But Windows 7 == 30 GB free space (Imagine my face when I saw that).
    I know windows 7 is little bigger but not 70GB bigger.



    ... and now 2 hours later I am back to 70 GB ;)
    HOW you ask me!?



    Simply performed same thing as above for following folders:




    • C:WindowsInstaller

    • C:WindowsSoftwareDistribution


    Commands are very similar:




    • move above folders to (for example) D:CWINDOWS

    • run CMD elevated as an administrator

    • type: CD C:WINDOWS

    • type: MKLINK /J Installer D:CWindowsInstaller

    • type: MKLINK /J SoftwareDistribution D:CWindowsSoftwareDistribution

    • type: EXIT


    Notice only to stop Windows Update, Trusted Installer, and Windows Installer services before moving those folders, run them after if you wish or simply restart (10 seconds for a reboot on SSD).



    I have reclaimed back 40GB of (100% uselessly taken space, since I will never uninstall anything I use). Haven't broken any windows rules, since they use for Documents and Settings same Junction Point to Users although on same drive...



    Still poking around what else I could move to (Magnetic) HDD drive...
    One thing to notice you will have winSxS subfolder in Windows folder DO NOT MOVE this folder as it would defy the purpose of Solid State Disk (fast loading of applications). WinSxS is a folder where all Side by Side dll's are located (and prety much every application uses something from there).
    This is also Microsoft's solution for DLL version HELL, if you wonder why it exists.






    share|improve this answer














    Way to go would be Junction Point.



    For example, if you have 120 GB SSD Drive as C:, and 3TB Drive (Magnetic) HDD as D::




    • on drive D: create sub folder named C

    • cut and paste folder MSOCache to subfolder C located on drive D:

    • run CMD

    • type: CD

    • type: MKLINK /J MSOCache D:CMSOCache

    • type: EXIT


    After this you will have entire content of MSOCache folder in path C:MSOCache, but physically files would be located on D:CMSOCache.





    That was the answer about MSOCache folder on C drive.
    Now let us talk about a real problem, the same one I experienced few hours ago.



    NOT ENOUGH SPACE ON SSD DISK AS C: DRIVE



    The main problem here is Windows Installer, and their crappy system of caching all old installation files.
    Every old version of some software that once existed on your PC Windows Installer keeps in his cache folder. Stupid thing, don't you think (only because someone might Uninstall some application Windows Installer keeps all files so it could roll back to the previous state - in simplified version - believe me it's much more complicated, but accept this as is).



    This wouldn't be much of problem if there aren't even bigger stupidness again from Microsoft, of course, called Windows Updates. That simply floods you with updates.
    And what are the Updates!? Nobody!? Updates == Installations == Bigger and bigger Windows Installation Cache.



    My situation was I've installed literally base development PC with minimal Office + VS2005, VS2008, VS2010 - That is I must have. I had this on XP machine primary disk with 120 GB just fine and plenty of drive space left with all updates installed (~100GB).
    But Windows 7 == 30 GB free space (Imagine my face when I saw that).
    I know windows 7 is little bigger but not 70GB bigger.



    ... and now 2 hours later I am back to 70 GB ;)
    HOW you ask me!?



    Simply performed same thing as above for following folders:




    • C:WindowsInstaller

    • C:WindowsSoftwareDistribution


    Commands are very similar:




    • move above folders to (for example) D:CWINDOWS

    • run CMD elevated as an administrator

    • type: CD C:WINDOWS

    • type: MKLINK /J Installer D:CWindowsInstaller

    • type: MKLINK /J SoftwareDistribution D:CWindowsSoftwareDistribution

    • type: EXIT


    Notice only to stop Windows Update, Trusted Installer, and Windows Installer services before moving those folders, run them after if you wish or simply restart (10 seconds for a reboot on SSD).



    I have reclaimed back 40GB of (100% uselessly taken space, since I will never uninstall anything I use). Haven't broken any windows rules, since they use for Documents and Settings same Junction Point to Users although on same drive...



    Still poking around what else I could move to (Magnetic) HDD drive...
    One thing to notice you will have winSxS subfolder in Windows folder DO NOT MOVE this folder as it would defy the purpose of Solid State Disk (fast loading of applications). WinSxS is a folder where all Side by Side dll's are located (and prety much every application uses something from there).
    This is also Microsoft's solution for DLL version HELL, if you wonder why it exists.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 5 '16 at 15:22

























    answered Jun 14 '13 at 21:43









    SoLaRSoLaR

    60048




    60048












    • This is really the safer solution. It should be marked as correct answer! Thanks mate!
      – psulek
      Mar 25 '14 at 15:12










    • Is it ok to do this with User folder, or better say with AppData folder which is around 10GB on my machine? Btw great answer.
      – nemke
      Jun 2 '15 at 14:48










    • uh, AppData is already an Junction Point, although on same drive. What you need is to locate real folder C:Users<username>AppDataRoaming and move that one to other drive. Now that being said, AppData contains software data on your computer, like configurations, caches, databases, and other data. If you move this to other drive it might defy the purpose of solid state drive. I would try to find what subdirectories use this much of space in AppData folder. And see to what software it belongs, and if I am not actively using these software I would move them, instead of entire AppData folder.
      – SoLaR
      Jan 8 '16 at 17:46










    • If you have a problem on moving SoftwareDistribution folder, it is about "Windows Update is running". Stop Windows Update on services and than try to move that folder. By the way, you save my ssd man, brilliant...
      – matasoy
      Jul 5 '17 at 21:44




















    • This is really the safer solution. It should be marked as correct answer! Thanks mate!
      – psulek
      Mar 25 '14 at 15:12










    • Is it ok to do this with User folder, or better say with AppData folder which is around 10GB on my machine? Btw great answer.
      – nemke
      Jun 2 '15 at 14:48










    • uh, AppData is already an Junction Point, although on same drive. What you need is to locate real folder C:Users<username>AppDataRoaming and move that one to other drive. Now that being said, AppData contains software data on your computer, like configurations, caches, databases, and other data. If you move this to other drive it might defy the purpose of solid state drive. I would try to find what subdirectories use this much of space in AppData folder. And see to what software it belongs, and if I am not actively using these software I would move them, instead of entire AppData folder.
      – SoLaR
      Jan 8 '16 at 17:46










    • If you have a problem on moving SoftwareDistribution folder, it is about "Windows Update is running". Stop Windows Update on services and than try to move that folder. By the way, you save my ssd man, brilliant...
      – matasoy
      Jul 5 '17 at 21:44


















    This is really the safer solution. It should be marked as correct answer! Thanks mate!
    – psulek
    Mar 25 '14 at 15:12




    This is really the safer solution. It should be marked as correct answer! Thanks mate!
    – psulek
    Mar 25 '14 at 15:12












    Is it ok to do this with User folder, or better say with AppData folder which is around 10GB on my machine? Btw great answer.
    – nemke
    Jun 2 '15 at 14:48




    Is it ok to do this with User folder, or better say with AppData folder which is around 10GB on my machine? Btw great answer.
    – nemke
    Jun 2 '15 at 14:48












    uh, AppData is already an Junction Point, although on same drive. What you need is to locate real folder C:Users<username>AppDataRoaming and move that one to other drive. Now that being said, AppData contains software data on your computer, like configurations, caches, databases, and other data. If you move this to other drive it might defy the purpose of solid state drive. I would try to find what subdirectories use this much of space in AppData folder. And see to what software it belongs, and if I am not actively using these software I would move them, instead of entire AppData folder.
    – SoLaR
    Jan 8 '16 at 17:46




    uh, AppData is already an Junction Point, although on same drive. What you need is to locate real folder C:Users<username>AppDataRoaming and move that one to other drive. Now that being said, AppData contains software data on your computer, like configurations, caches, databases, and other data. If you move this to other drive it might defy the purpose of solid state drive. I would try to find what subdirectories use this much of space in AppData folder. And see to what software it belongs, and if I am not actively using these software I would move them, instead of entire AppData folder.
    – SoLaR
    Jan 8 '16 at 17:46












    If you have a problem on moving SoftwareDistribution folder, it is about "Windows Update is running". Stop Windows Update on services and than try to move that folder. By the way, you save my ssd man, brilliant...
    – matasoy
    Jul 5 '17 at 21:44






    If you have a problem on moving SoftwareDistribution folder, it is about "Windows Update is running". Stop Windows Update on services and than try to move that folder. By the way, you save my ssd man, brilliant...
    – matasoy
    Jul 5 '17 at 21:44













    12














    The Local Install Source (Msocache) feature is installed so that you do not have to insert the CD during the following Setup operations:




    • Detect and Repair

    • Demand Install

    • Maintenance Mode Setup

    • Installation of service packs and patches


    You can use the Windows Cleanup Wizard to remove the Msocache folder. To do this, follow the steps in the related Microsoft article.



    Warning: Never delete the MSOCACHE folder by using Microsoft Windows Explorer.






    share|improve this answer























    • I followed the guide. It removed my about 100MB-200MB but there are still 1.2 GB in that folder now.
      – Drake
      Nov 29 '10 at 16:23












    • Another work around could be to create a system restore point (call it "safe"), delete the content of the folder completely, work for a few days in this wise, and go back to "safe" if you face any problems.
      – Mehper C. Palavuzlar
      Nov 29 '10 at 16:27












    • This MS article suggests another solution. Check out Q4 and A4.
      – Mehper C. Palavuzlar
      Nov 29 '10 at 16:31










    • that article refers to Microsoft Office 2003. I tried download and install LISTool.exe anyway, but it seems not compatible with Microsoft Office 2010
      – Drake
      Dec 1 '10 at 8:13










    • Then I can only suggest you try what I pointed in my first comment (system restore).
      – Mehper C. Palavuzlar
      Dec 1 '10 at 8:19
















    12














    The Local Install Source (Msocache) feature is installed so that you do not have to insert the CD during the following Setup operations:




    • Detect and Repair

    • Demand Install

    • Maintenance Mode Setup

    • Installation of service packs and patches


    You can use the Windows Cleanup Wizard to remove the Msocache folder. To do this, follow the steps in the related Microsoft article.



    Warning: Never delete the MSOCACHE folder by using Microsoft Windows Explorer.






    share|improve this answer























    • I followed the guide. It removed my about 100MB-200MB but there are still 1.2 GB in that folder now.
      – Drake
      Nov 29 '10 at 16:23












    • Another work around could be to create a system restore point (call it "safe"), delete the content of the folder completely, work for a few days in this wise, and go back to "safe" if you face any problems.
      – Mehper C. Palavuzlar
      Nov 29 '10 at 16:27












    • This MS article suggests another solution. Check out Q4 and A4.
      – Mehper C. Palavuzlar
      Nov 29 '10 at 16:31










    • that article refers to Microsoft Office 2003. I tried download and install LISTool.exe anyway, but it seems not compatible with Microsoft Office 2010
      – Drake
      Dec 1 '10 at 8:13










    • Then I can only suggest you try what I pointed in my first comment (system restore).
      – Mehper C. Palavuzlar
      Dec 1 '10 at 8:19














    12












    12








    12






    The Local Install Source (Msocache) feature is installed so that you do not have to insert the CD during the following Setup operations:




    • Detect and Repair

    • Demand Install

    • Maintenance Mode Setup

    • Installation of service packs and patches


    You can use the Windows Cleanup Wizard to remove the Msocache folder. To do this, follow the steps in the related Microsoft article.



    Warning: Never delete the MSOCACHE folder by using Microsoft Windows Explorer.






    share|improve this answer














    The Local Install Source (Msocache) feature is installed so that you do not have to insert the CD during the following Setup operations:




    • Detect and Repair

    • Demand Install

    • Maintenance Mode Setup

    • Installation of service packs and patches


    You can use the Windows Cleanup Wizard to remove the Msocache folder. To do this, follow the steps in the related Microsoft article.



    Warning: Never delete the MSOCACHE folder by using Microsoft Windows Explorer.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Nov 29 '10 at 16:19

























    answered Nov 29 '10 at 16:14









    Mehper C. PalavuzlarMehper C. Palavuzlar

    43.4k42175233




    43.4k42175233












    • I followed the guide. It removed my about 100MB-200MB but there are still 1.2 GB in that folder now.
      – Drake
      Nov 29 '10 at 16:23












    • Another work around could be to create a system restore point (call it "safe"), delete the content of the folder completely, work for a few days in this wise, and go back to "safe" if you face any problems.
      – Mehper C. Palavuzlar
      Nov 29 '10 at 16:27












    • This MS article suggests another solution. Check out Q4 and A4.
      – Mehper C. Palavuzlar
      Nov 29 '10 at 16:31










    • that article refers to Microsoft Office 2003. I tried download and install LISTool.exe anyway, but it seems not compatible with Microsoft Office 2010
      – Drake
      Dec 1 '10 at 8:13










    • Then I can only suggest you try what I pointed in my first comment (system restore).
      – Mehper C. Palavuzlar
      Dec 1 '10 at 8:19


















    • I followed the guide. It removed my about 100MB-200MB but there are still 1.2 GB in that folder now.
      – Drake
      Nov 29 '10 at 16:23












    • Another work around could be to create a system restore point (call it "safe"), delete the content of the folder completely, work for a few days in this wise, and go back to "safe" if you face any problems.
      – Mehper C. Palavuzlar
      Nov 29 '10 at 16:27












    • This MS article suggests another solution. Check out Q4 and A4.
      – Mehper C. Palavuzlar
      Nov 29 '10 at 16:31










    • that article refers to Microsoft Office 2003. I tried download and install LISTool.exe anyway, but it seems not compatible with Microsoft Office 2010
      – Drake
      Dec 1 '10 at 8:13










    • Then I can only suggest you try what I pointed in my first comment (system restore).
      – Mehper C. Palavuzlar
      Dec 1 '10 at 8:19
















    I followed the guide. It removed my about 100MB-200MB but there are still 1.2 GB in that folder now.
    – Drake
    Nov 29 '10 at 16:23






    I followed the guide. It removed my about 100MB-200MB but there are still 1.2 GB in that folder now.
    – Drake
    Nov 29 '10 at 16:23














    Another work around could be to create a system restore point (call it "safe"), delete the content of the folder completely, work for a few days in this wise, and go back to "safe" if you face any problems.
    – Mehper C. Palavuzlar
    Nov 29 '10 at 16:27






    Another work around could be to create a system restore point (call it "safe"), delete the content of the folder completely, work for a few days in this wise, and go back to "safe" if you face any problems.
    – Mehper C. Palavuzlar
    Nov 29 '10 at 16:27














    This MS article suggests another solution. Check out Q4 and A4.
    – Mehper C. Palavuzlar
    Nov 29 '10 at 16:31




    This MS article suggests another solution. Check out Q4 and A4.
    – Mehper C. Palavuzlar
    Nov 29 '10 at 16:31












    that article refers to Microsoft Office 2003. I tried download and install LISTool.exe anyway, but it seems not compatible with Microsoft Office 2010
    – Drake
    Dec 1 '10 at 8:13




    that article refers to Microsoft Office 2003. I tried download and install LISTool.exe anyway, but it seems not compatible with Microsoft Office 2010
    – Drake
    Dec 1 '10 at 8:13












    Then I can only suggest you try what I pointed in my first comment (system restore).
    – Mehper C. Palavuzlar
    Dec 1 '10 at 8:19




    Then I can only suggest you try what I pointed in my first comment (system restore).
    – Mehper C. Palavuzlar
    Dec 1 '10 at 8:19











    6














    The best way to prevent this folder from being placed on your drive in the first place, is by selecting the Delete installation files check-box during the installation of Office.



    From this thread :




    If you delete it this is what will happen:




    • MS Office's repair function won't work from the hard disk cache anymore - will require the CD to fix it.

    • Microsoft Updates for Office that require the cache won't work from the
      hard disk cache anymore - will require
      the CD to install them.


    Solution, what I did recently:




    1. Burn that whole folder to a CD-R or DVD (the filesize of that folder
      depends upon your Office version).

    2. Delete that folder.

    3. Search the registry in regEdit for C:MSOCache and change all references
      to point to your CD/DVD drive,
      example: E:MSOCache (will of course
      require the disc when something
      Office-related needs those cache
      files.)







    share|improve this answer

















    • 1




      It seems we found the same page...
      – oKtosiTe
      Dec 2 '10 at 15:26






    • 1




      @oKtosiTe: Yah, and on the same minute, too. Great minds think alike ...
      – harrymc
      Dec 2 '10 at 15:40
















    6














    The best way to prevent this folder from being placed on your drive in the first place, is by selecting the Delete installation files check-box during the installation of Office.



    From this thread :




    If you delete it this is what will happen:




    • MS Office's repair function won't work from the hard disk cache anymore - will require the CD to fix it.

    • Microsoft Updates for Office that require the cache won't work from the
      hard disk cache anymore - will require
      the CD to install them.


    Solution, what I did recently:




    1. Burn that whole folder to a CD-R or DVD (the filesize of that folder
      depends upon your Office version).

    2. Delete that folder.

    3. Search the registry in regEdit for C:MSOCache and change all references
      to point to your CD/DVD drive,
      example: E:MSOCache (will of course
      require the disc when something
      Office-related needs those cache
      files.)







    share|improve this answer

















    • 1




      It seems we found the same page...
      – oKtosiTe
      Dec 2 '10 at 15:26






    • 1




      @oKtosiTe: Yah, and on the same minute, too. Great minds think alike ...
      – harrymc
      Dec 2 '10 at 15:40














    6












    6








    6






    The best way to prevent this folder from being placed on your drive in the first place, is by selecting the Delete installation files check-box during the installation of Office.



    From this thread :




    If you delete it this is what will happen:




    • MS Office's repair function won't work from the hard disk cache anymore - will require the CD to fix it.

    • Microsoft Updates for Office that require the cache won't work from the
      hard disk cache anymore - will require
      the CD to install them.


    Solution, what I did recently:




    1. Burn that whole folder to a CD-R or DVD (the filesize of that folder
      depends upon your Office version).

    2. Delete that folder.

    3. Search the registry in regEdit for C:MSOCache and change all references
      to point to your CD/DVD drive,
      example: E:MSOCache (will of course
      require the disc when something
      Office-related needs those cache
      files.)







    share|improve this answer












    The best way to prevent this folder from being placed on your drive in the first place, is by selecting the Delete installation files check-box during the installation of Office.



    From this thread :




    If you delete it this is what will happen:




    • MS Office's repair function won't work from the hard disk cache anymore - will require the CD to fix it.

    • Microsoft Updates for Office that require the cache won't work from the
      hard disk cache anymore - will require
      the CD to install them.


    Solution, what I did recently:




    1. Burn that whole folder to a CD-R or DVD (the filesize of that folder
      depends upon your Office version).

    2. Delete that folder.

    3. Search the registry in regEdit for C:MSOCache and change all references
      to point to your CD/DVD drive,
      example: E:MSOCache (will of course
      require the disc when something
      Office-related needs those cache
      files.)








    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Dec 2 '10 at 15:20









    harrymcharrymc

    254k14265565




    254k14265565








    • 1




      It seems we found the same page...
      – oKtosiTe
      Dec 2 '10 at 15:26






    • 1




      @oKtosiTe: Yah, and on the same minute, too. Great minds think alike ...
      – harrymc
      Dec 2 '10 at 15:40














    • 1




      It seems we found the same page...
      – oKtosiTe
      Dec 2 '10 at 15:26






    • 1




      @oKtosiTe: Yah, and on the same minute, too. Great minds think alike ...
      – harrymc
      Dec 2 '10 at 15:40








    1




    1




    It seems we found the same page...
    – oKtosiTe
    Dec 2 '10 at 15:26




    It seems we found the same page...
    – oKtosiTe
    Dec 2 '10 at 15:26




    1




    1




    @oKtosiTe: Yah, and on the same minute, too. Great minds think alike ...
    – harrymc
    Dec 2 '10 at 15:40




    @oKtosiTe: Yah, and on the same minute, too. Great minds think alike ...
    – harrymc
    Dec 2 '10 at 15:40











    3














    I wonder if anyone who's against deletion of this folder have actually met any problems after that in the real life.



    I've been shift+deleting this MSOCache since I've seen it for the very first time back in 2003 or so, and have never had any problems with updating or using Microsoft Office after that.



    My answer is yes, you may safely delete C:MSOCache folder with no regrets in case you have installation media you may use later in case it is required.






    share|improve this answer























    • This answer may sound flippant and unconsidered, but it is one of the best ones here. I've been using office for about 20 years, and the MSOCache directory is the first thing to go after installation. It's in the wrong place, and I've never seen its necessity demonstrated. What's the worst that can happen? Needing to spend a few minutes reinstalling from media without some cached files? After reading this thread I now RAR archive the folder and put it in backup just in case, but I have never once seen a single consequence of just deleting it. Only a problem for enterprise IT types.
      – chronometric
      May 11 '17 at 16:09


















    3














    I wonder if anyone who's against deletion of this folder have actually met any problems after that in the real life.



    I've been shift+deleting this MSOCache since I've seen it for the very first time back in 2003 or so, and have never had any problems with updating or using Microsoft Office after that.



    My answer is yes, you may safely delete C:MSOCache folder with no regrets in case you have installation media you may use later in case it is required.






    share|improve this answer























    • This answer may sound flippant and unconsidered, but it is one of the best ones here. I've been using office for about 20 years, and the MSOCache directory is the first thing to go after installation. It's in the wrong place, and I've never seen its necessity demonstrated. What's the worst that can happen? Needing to spend a few minutes reinstalling from media without some cached files? After reading this thread I now RAR archive the folder and put it in backup just in case, but I have never once seen a single consequence of just deleting it. Only a problem for enterprise IT types.
      – chronometric
      May 11 '17 at 16:09
















    3












    3








    3






    I wonder if anyone who's against deletion of this folder have actually met any problems after that in the real life.



    I've been shift+deleting this MSOCache since I've seen it for the very first time back in 2003 or so, and have never had any problems with updating or using Microsoft Office after that.



    My answer is yes, you may safely delete C:MSOCache folder with no regrets in case you have installation media you may use later in case it is required.






    share|improve this answer














    I wonder if anyone who's against deletion of this folder have actually met any problems after that in the real life.



    I've been shift+deleting this MSOCache since I've seen it for the very first time back in 2003 or so, and have never had any problems with updating or using Microsoft Office after that.



    My answer is yes, you may safely delete C:MSOCache folder with no regrets in case you have installation media you may use later in case it is required.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 29 '17 at 9:28

























    answered Mar 29 '17 at 9:21









    PimpfruPimpfru

    312




    312












    • This answer may sound flippant and unconsidered, but it is one of the best ones here. I've been using office for about 20 years, and the MSOCache directory is the first thing to go after installation. It's in the wrong place, and I've never seen its necessity demonstrated. What's the worst that can happen? Needing to spend a few minutes reinstalling from media without some cached files? After reading this thread I now RAR archive the folder and put it in backup just in case, but I have never once seen a single consequence of just deleting it. Only a problem for enterprise IT types.
      – chronometric
      May 11 '17 at 16:09




















    • This answer may sound flippant and unconsidered, but it is one of the best ones here. I've been using office for about 20 years, and the MSOCache directory is the first thing to go after installation. It's in the wrong place, and I've never seen its necessity demonstrated. What's the worst that can happen? Needing to spend a few minutes reinstalling from media without some cached files? After reading this thread I now RAR archive the folder and put it in backup just in case, but I have never once seen a single consequence of just deleting it. Only a problem for enterprise IT types.
      – chronometric
      May 11 '17 at 16:09


















    This answer may sound flippant and unconsidered, but it is one of the best ones here. I've been using office for about 20 years, and the MSOCache directory is the first thing to go after installation. It's in the wrong place, and I've never seen its necessity demonstrated. What's the worst that can happen? Needing to spend a few minutes reinstalling from media without some cached files? After reading this thread I now RAR archive the folder and put it in backup just in case, but I have never once seen a single consequence of just deleting it. Only a problem for enterprise IT types.
    – chronometric
    May 11 '17 at 16:09






    This answer may sound flippant and unconsidered, but it is one of the best ones here. I've been using office for about 20 years, and the MSOCache directory is the first thing to go after installation. It's in the wrong place, and I've never seen its necessity demonstrated. What's the worst that can happen? Needing to spend a few minutes reinstalling from media without some cached files? After reading this thread I now RAR archive the folder and put it in backup just in case, but I have never once seen a single consequence of just deleting it. Only a problem for enterprise IT types.
    – chronometric
    May 11 '17 at 16:09













    2














    I have a 64GB SSD and LOADS of programs. I regularly move space gluttons to a HDD. Many programs now use 500MB-1.3GB for garbage like page borders and all sorts of small image files.



    Don't screw with the registry. Sooner or later it'll bite you in the butt bigtime. Create a junction, as mentioned in SoLaR's answer.



    HOWEVER -- SOME CAVEATS.




    1. Don't delete the original folder. Rename it with a minus sign, i.e.,

      rename MSOCache to -MSOCache.



    2. MSOCache is an anomaly in that it is in a root folder. Normally you are moving something in a subfolder. So you'll have to modify the following where it says "put in the parent folder".



      In the PARENT folder of the subfolder you are moving, create a TEXT file called JUNCTION LIST.txt with the contents shown below. So if you are moving C:Program FilesAdobeSpacehog you would put the "JUNCTION LIST.txt" file in C:Program FilesAdobe



      CONTENTS OF JUNCTION LIST.txt (of course, modified to your particular case):



      SSD Win 7
      C:ProgramDataAdobeCameraRaw

      was replaced with a junction to

      S:Program_DataAdobeCameraRaw

      mklink /j CameraRaw "S:Program_DataAdobeCameraRaw"


      (Add any others, as needed.)



      The JUNCTION LIST.txt should document EXACTLY what you did.



    3. Open a command prompt in the PARENT folder of the subfolder you are moving.


    4. COPY the "mklink ..." line from the DOCUMENTATION file. This means highlight and press Ctrl-C.



    5. PASTE the command at the prompt, and press enter.



      If it doesn't work, DO NOT make ANY corrections to the command line. Correct the DOCUMENTATION file and repeat the copy and paste.



      You should now have the original folder name with a minus sign and a junction with the original filename.



    6. Move everything from the "minus" folder to the junction.


    7. Copy the JUNCTION LIST.txt folder to the PARENT folder of the TARGET folder on the other drive. The idea is to have documentation all over the place.


    8. Now, except that you have an actual folder with a "minus" name, everything should look the same as before you started.


    9. DO NOT rename the target folder. That destroys the junction. If you need to rename the target folder, delete the junction, correct the JUNCTION LIST.txt file, and create a new junction.







    share|improve this answer























    • Related: How to search for all junction links in a given directories and its subdirectories.
      – Arjan
      Jun 15 '14 at 8:02
















    2














    I have a 64GB SSD and LOADS of programs. I regularly move space gluttons to a HDD. Many programs now use 500MB-1.3GB for garbage like page borders and all sorts of small image files.



    Don't screw with the registry. Sooner or later it'll bite you in the butt bigtime. Create a junction, as mentioned in SoLaR's answer.



    HOWEVER -- SOME CAVEATS.




    1. Don't delete the original folder. Rename it with a minus sign, i.e.,

      rename MSOCache to -MSOCache.



    2. MSOCache is an anomaly in that it is in a root folder. Normally you are moving something in a subfolder. So you'll have to modify the following where it says "put in the parent folder".



      In the PARENT folder of the subfolder you are moving, create a TEXT file called JUNCTION LIST.txt with the contents shown below. So if you are moving C:Program FilesAdobeSpacehog you would put the "JUNCTION LIST.txt" file in C:Program FilesAdobe



      CONTENTS OF JUNCTION LIST.txt (of course, modified to your particular case):



      SSD Win 7
      C:ProgramDataAdobeCameraRaw

      was replaced with a junction to

      S:Program_DataAdobeCameraRaw

      mklink /j CameraRaw "S:Program_DataAdobeCameraRaw"


      (Add any others, as needed.)



      The JUNCTION LIST.txt should document EXACTLY what you did.



    3. Open a command prompt in the PARENT folder of the subfolder you are moving.


    4. COPY the "mklink ..." line from the DOCUMENTATION file. This means highlight and press Ctrl-C.



    5. PASTE the command at the prompt, and press enter.



      If it doesn't work, DO NOT make ANY corrections to the command line. Correct the DOCUMENTATION file and repeat the copy and paste.



      You should now have the original folder name with a minus sign and a junction with the original filename.



    6. Move everything from the "minus" folder to the junction.


    7. Copy the JUNCTION LIST.txt folder to the PARENT folder of the TARGET folder on the other drive. The idea is to have documentation all over the place.


    8. Now, except that you have an actual folder with a "minus" name, everything should look the same as before you started.


    9. DO NOT rename the target folder. That destroys the junction. If you need to rename the target folder, delete the junction, correct the JUNCTION LIST.txt file, and create a new junction.







    share|improve this answer























    • Related: How to search for all junction links in a given directories and its subdirectories.
      – Arjan
      Jun 15 '14 at 8:02














    2












    2








    2






    I have a 64GB SSD and LOADS of programs. I regularly move space gluttons to a HDD. Many programs now use 500MB-1.3GB for garbage like page borders and all sorts of small image files.



    Don't screw with the registry. Sooner or later it'll bite you in the butt bigtime. Create a junction, as mentioned in SoLaR's answer.



    HOWEVER -- SOME CAVEATS.




    1. Don't delete the original folder. Rename it with a minus sign, i.e.,

      rename MSOCache to -MSOCache.



    2. MSOCache is an anomaly in that it is in a root folder. Normally you are moving something in a subfolder. So you'll have to modify the following where it says "put in the parent folder".



      In the PARENT folder of the subfolder you are moving, create a TEXT file called JUNCTION LIST.txt with the contents shown below. So if you are moving C:Program FilesAdobeSpacehog you would put the "JUNCTION LIST.txt" file in C:Program FilesAdobe



      CONTENTS OF JUNCTION LIST.txt (of course, modified to your particular case):



      SSD Win 7
      C:ProgramDataAdobeCameraRaw

      was replaced with a junction to

      S:Program_DataAdobeCameraRaw

      mklink /j CameraRaw "S:Program_DataAdobeCameraRaw"


      (Add any others, as needed.)



      The JUNCTION LIST.txt should document EXACTLY what you did.



    3. Open a command prompt in the PARENT folder of the subfolder you are moving.


    4. COPY the "mklink ..." line from the DOCUMENTATION file. This means highlight and press Ctrl-C.



    5. PASTE the command at the prompt, and press enter.



      If it doesn't work, DO NOT make ANY corrections to the command line. Correct the DOCUMENTATION file and repeat the copy and paste.



      You should now have the original folder name with a minus sign and a junction with the original filename.



    6. Move everything from the "minus" folder to the junction.


    7. Copy the JUNCTION LIST.txt folder to the PARENT folder of the TARGET folder on the other drive. The idea is to have documentation all over the place.


    8. Now, except that you have an actual folder with a "minus" name, everything should look the same as before you started.


    9. DO NOT rename the target folder. That destroys the junction. If you need to rename the target folder, delete the junction, correct the JUNCTION LIST.txt file, and create a new junction.







    share|improve this answer














    I have a 64GB SSD and LOADS of programs. I regularly move space gluttons to a HDD. Many programs now use 500MB-1.3GB for garbage like page borders and all sorts of small image files.



    Don't screw with the registry. Sooner or later it'll bite you in the butt bigtime. Create a junction, as mentioned in SoLaR's answer.



    HOWEVER -- SOME CAVEATS.




    1. Don't delete the original folder. Rename it with a minus sign, i.e.,

      rename MSOCache to -MSOCache.



    2. MSOCache is an anomaly in that it is in a root folder. Normally you are moving something in a subfolder. So you'll have to modify the following where it says "put in the parent folder".



      In the PARENT folder of the subfolder you are moving, create a TEXT file called JUNCTION LIST.txt with the contents shown below. So if you are moving C:Program FilesAdobeSpacehog you would put the "JUNCTION LIST.txt" file in C:Program FilesAdobe



      CONTENTS OF JUNCTION LIST.txt (of course, modified to your particular case):



      SSD Win 7
      C:ProgramDataAdobeCameraRaw

      was replaced with a junction to

      S:Program_DataAdobeCameraRaw

      mklink /j CameraRaw "S:Program_DataAdobeCameraRaw"


      (Add any others, as needed.)



      The JUNCTION LIST.txt should document EXACTLY what you did.



    3. Open a command prompt in the PARENT folder of the subfolder you are moving.


    4. COPY the "mklink ..." line from the DOCUMENTATION file. This means highlight and press Ctrl-C.



    5. PASTE the command at the prompt, and press enter.



      If it doesn't work, DO NOT make ANY corrections to the command line. Correct the DOCUMENTATION file and repeat the copy and paste.



      You should now have the original folder name with a minus sign and a junction with the original filename.



    6. Move everything from the "minus" folder to the junction.


    7. Copy the JUNCTION LIST.txt folder to the PARENT folder of the TARGET folder on the other drive. The idea is to have documentation all over the place.


    8. Now, except that you have an actual folder with a "minus" name, everything should look the same as before you started.


    9. DO NOT rename the target folder. That destroys the junction. If you need to rename the target folder, delete the junction, correct the JUNCTION LIST.txt file, and create a new junction.








    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 20 '17 at 10:17









    Community

    1




    1










    answered Jun 15 '14 at 6:22









    Rick75230Rick75230

    211




    211












    • Related: How to search for all junction links in a given directories and its subdirectories.
      – Arjan
      Jun 15 '14 at 8:02


















    • Related: How to search for all junction links in a given directories and its subdirectories.
      – Arjan
      Jun 15 '14 at 8:02
















    Related: How to search for all junction links in a given directories and its subdirectories.
    – Arjan
    Jun 15 '14 at 8:02




    Related: How to search for all junction links in a given directories and its subdirectories.
    – Arjan
    Jun 15 '14 at 8:02











    1














    Very similar to previous answers - the twist is I moved C:MSOCache to my second HD, D:MSOCache and then all I had to do is use regedit to change all references from C:MSOCache to D:MSOCache for an overall quick and painless way to free-up a sizable chunk of space on the C: drive.






    share|improve this answer























    • Creating a junction point which points to the new location is much safer solution. It's completely transparent (applications don't recognize it's not a real directory but junction point), it's easier since you don't need to search and change anything in the registry and it will work even if an application uses a hard-coded path (developer for example simply forgot to read that path from the registry).
      – Dawid Ferenczy
      Feb 29 '16 at 1:44


















    1














    Very similar to previous answers - the twist is I moved C:MSOCache to my second HD, D:MSOCache and then all I had to do is use regedit to change all references from C:MSOCache to D:MSOCache for an overall quick and painless way to free-up a sizable chunk of space on the C: drive.






    share|improve this answer























    • Creating a junction point which points to the new location is much safer solution. It's completely transparent (applications don't recognize it's not a real directory but junction point), it's easier since you don't need to search and change anything in the registry and it will work even if an application uses a hard-coded path (developer for example simply forgot to read that path from the registry).
      – Dawid Ferenczy
      Feb 29 '16 at 1:44
















    1












    1








    1






    Very similar to previous answers - the twist is I moved C:MSOCache to my second HD, D:MSOCache and then all I had to do is use regedit to change all references from C:MSOCache to D:MSOCache for an overall quick and painless way to free-up a sizable chunk of space on the C: drive.






    share|improve this answer














    Very similar to previous answers - the twist is I moved C:MSOCache to my second HD, D:MSOCache and then all I had to do is use regedit to change all references from C:MSOCache to D:MSOCache for an overall quick and painless way to free-up a sizable chunk of space on the C: drive.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Mar 26 '13 at 14:35









    oKtosiTe

    6,09183868




    6,09183868










    answered Apr 6 '11 at 8:37









    LesterJLesterJ

    112




    112












    • Creating a junction point which points to the new location is much safer solution. It's completely transparent (applications don't recognize it's not a real directory but junction point), it's easier since you don't need to search and change anything in the registry and it will work even if an application uses a hard-coded path (developer for example simply forgot to read that path from the registry).
      – Dawid Ferenczy
      Feb 29 '16 at 1:44




















    • Creating a junction point which points to the new location is much safer solution. It's completely transparent (applications don't recognize it's not a real directory but junction point), it's easier since you don't need to search and change anything in the registry and it will work even if an application uses a hard-coded path (developer for example simply forgot to read that path from the registry).
      – Dawid Ferenczy
      Feb 29 '16 at 1:44


















    Creating a junction point which points to the new location is much safer solution. It's completely transparent (applications don't recognize it's not a real directory but junction point), it's easier since you don't need to search and change anything in the registry and it will work even if an application uses a hard-coded path (developer for example simply forgot to read that path from the registry).
    – Dawid Ferenczy
    Feb 29 '16 at 1:44






    Creating a junction point which points to the new location is much safer solution. It's completely transparent (applications don't recognize it's not a real directory but junction point), it's easier since you don't need to search and change anything in the registry and it will work even if an application uses a hard-coded path (developer for example simply forgot to read that path from the registry).
    – Dawid Ferenczy
    Feb 29 '16 at 1:44













    0














    Yes, you can delete the MSOCache folder, if when you install MS Office, you select the option to "Run all from My Computer".



    Install office, then delete MSOCache



    Check that option under Microsoft Office, then check Not Available for the components you don't need. I've installed only Excel (tons faster than LibreCalc), Word and PowerPoint, then I've renamed MSOCache to "junk.MSOCache.deleteme". I don't plan to install any other Office components.



    So far, no problems. Haven't tried installing any Office updates because I don't need any security patches (the only Office files I use are my own), but if you want the updates, install them first and delete/rename MSOCache after.



    UPDATE: I've also deleted the MSOCache folder from a Wine installation of Office on Linux, and Excel works just fine.






    share|improve this answer




























      0














      Yes, you can delete the MSOCache folder, if when you install MS Office, you select the option to "Run all from My Computer".



      Install office, then delete MSOCache



      Check that option under Microsoft Office, then check Not Available for the components you don't need. I've installed only Excel (tons faster than LibreCalc), Word and PowerPoint, then I've renamed MSOCache to "junk.MSOCache.deleteme". I don't plan to install any other Office components.



      So far, no problems. Haven't tried installing any Office updates because I don't need any security patches (the only Office files I use are my own), but if you want the updates, install them first and delete/rename MSOCache after.



      UPDATE: I've also deleted the MSOCache folder from a Wine installation of Office on Linux, and Excel works just fine.






      share|improve this answer


























        0












        0








        0






        Yes, you can delete the MSOCache folder, if when you install MS Office, you select the option to "Run all from My Computer".



        Install office, then delete MSOCache



        Check that option under Microsoft Office, then check Not Available for the components you don't need. I've installed only Excel (tons faster than LibreCalc), Word and PowerPoint, then I've renamed MSOCache to "junk.MSOCache.deleteme". I don't plan to install any other Office components.



        So far, no problems. Haven't tried installing any Office updates because I don't need any security patches (the only Office files I use are my own), but if you want the updates, install them first and delete/rename MSOCache after.



        UPDATE: I've also deleted the MSOCache folder from a Wine installation of Office on Linux, and Excel works just fine.






        share|improve this answer














        Yes, you can delete the MSOCache folder, if when you install MS Office, you select the option to "Run all from My Computer".



        Install office, then delete MSOCache



        Check that option under Microsoft Office, then check Not Available for the components you don't need. I've installed only Excel (tons faster than LibreCalc), Word and PowerPoint, then I've renamed MSOCache to "junk.MSOCache.deleteme". I don't plan to install any other Office components.



        So far, no problems. Haven't tried installing any Office updates because I don't need any security patches (the only Office files I use are my own), but if you want the updates, install them first and delete/rename MSOCache after.



        UPDATE: I've also deleted the MSOCache folder from a Wine installation of Office on Linux, and Excel works just fine.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Sep 2 '16 at 2:43

























        answered Feb 6 '16 at 7:41









        Dan DascalescuDan Dascalescu

        2,36642747




        2,36642747






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f216300%2fcan-i-delete-msocache%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Список кардиналов, возведённых папой римским Каликстом III

            Deduzione

            Mysql.sock missing - “Can't connect to local MySQL server through socket”