Microsoft polluted my brand new disk drive - what can be deleted?

Microsoft polluted my brand new disk drive - what can be deleted?
http://wetakepic.com/images/2018/03/...ft_crap_01.jpg

Given these are the only directories I care about:
http://wetakepic.com/images/2018/03/02/whatisneeded.jpg

I'm first researching if I can just delete, en masse, the Microsoft
pollution.

Do you know off hand?

For the tribal knowledge, I'll tackle this Microsoft pollution one by one.
1. $Windows.~WS (and BT)
2. ESD
3. MSOCache
4. ouput
5. PerfLogs
6. Windows.old

HINT: Poor coding standards are in evidence galore.

ultred ragnusen wrote:

Microsoft polluted my brand new disk drive - what can be
deleted?
http://wetakepic.com/images/2018/03/...ft_crap_01.jpg

Given these are the only directories I care about:
http://wetakepic.com/images/2018/03/02/whatisneeded.jpg

I'm first researching if I can just delete, en masse, the
Microsoft pollution.

Do you know off hand?

I think much can be avoided if you disable the drive(s) while
installing Windows. Then, Microsoft will force only two
folders onto the drive... "System Volume Information" and a
recycle bin. Those folders are neatly hidden via View in the
file manager properties.

And maybe a third folder named "Recovery".
Also hidden.
The Borg will have its way. The best you can do is don't
worry about it.



I wrote:

ultred ragnusen wrote:

Microsoft polluted my brand new disk drive - what can be
deleted?
http://wetakepic.com/images/2018/03/...ft_crap_01.jpg

Given these are the only directories I care about:
http://wetakepic.com/images/2018/03/02/whatisneeded.jpg

I'm first researching if I can just delete, en masse, the
Microsoft pollution.

Do you know off hand?

I think much can be avoided if you disable the drive(s) while
installing Windows. Then, Microsoft will force only two
folders onto the drive... "System Volume Information" and a
recycle bin. Those folders are neatly hidden via View in the
file manager properties.

John Doe wrote:
I think much can be avoided if you disable the drive(s) while
installing Windows. Then, Microsoft will force only two
folders onto the drive... "System Volume Information" and a
recycle bin. Those folders are neatly hidden via View in the
file manager properties.

And maybe a third folder named "Recovery".
Also hidden.
The Borg will have its way. The best you can do is don't
worry about it.

I'm not sure what you mean by "disabling the drives" while installing.
You have to have, at the bare minimum, one disk drive, right?

As for hiding the Microsoft pollution, that's /never/ the goal, as the goal
is to maintain a clean hierarchy that follows clean GUI standards, so let's
not speak of this talk of hiding pollution, which is sort of like crapping
on the floor and covering it up with toilet paper.

The goal is to clean it up as gracefully as possible.

To that end, plenty of people wish to clean up the 1st listed pollution,
which I found out by searching for just the first bit of pollution.
https://duckduckgo.com/?&q=Can+I+del....~WS+directory

For example, this implies that pollution is just a "rollback" release.
Title: What is this "$Windows.~WS" crap?
https://answers.microsoft.com/en-us/...6-0ff8c6355d90

That same discussion suggests the "disk cleanup" tool:
c:\windows\system32\cleanmgr.exe

Hence, I ran that "Disk Cleanup for (C" tool and checked the box for
[Clean up system files], and then I checked all available options:
http://wetakepic.com/images/2018/03/02/disk_cleanup.jpg

[x] Windows Update Cleanup [10.0MB]
Windows keeps copies of all installed updates from Windows
Update, even after installing newer versions of updates. Windows
Update cleanup deletes or compresses older versions of upates
that are no longer needed and taking up space. (You might need
to restart your computer.)
[x] Windows Defender Antivirus [1.14MB]
Non critical files used by Windows Defender Andivirus
[x] Windows upgrade log files [260MB]
Windows upgrade log files contain information that can help
identify and troubleshoot problems that occur during Windows
installation, upgrade, or servicing. Deleting these files can make it
difficult to troubleshoot installation issues.
[x] Downloaded Program Files [0 bytes]
Downloaded Program Files are ActiveX controls and Java applets
downloaded automatically from the Internet when you view certain
pages. TGhey are temporarily stored in the Downloaded Program
Files folder on your hard disk.
[x] Temporary Internet Files [5.21 MB]
The Temporary Internet Files folder contains webpages stored on
your hard disk for quick viewing. Your personalized settings for
webpages will be left intact.
[x] System created Windows Error Reporting [166 KB]
Files used for error reporting and solution checking.
[x] DirectX Shader Cache [0 bytes]
Clean up files created by the graphics system which can speed up
application load time and improve responsiveness. They will be
re-generated as needed.
[x] Delivery Optimization Files [2.66 MB]
Delivery Optimization files are files that were previously
downloaded to your computer and can be deleted if currently
unused by the Delivery Optimization Service.
[x] Device driver packages [0 bytes]
Windows keeps copies of all previously installed device driver
packages from Windows UPdate and other sources, even after
installing newer versions of drivers. This task will remove older
versions of drivers that are no longer needed. The most current
versions of each driver package will be kept.
[x] Previous Windows installation(s) [1.61 GB]
Files from a previous Windows installation. Files and folders that
may conflict with the installation of Windows havfe been moved to
folders named Windows.old. You can access data from the
previous Winodws installation in this folder.
[x] Recycle Bin [2.49 MB]
The Recycle Bin contains files you have deleted from your
computer. These files are not permanently removed until you
empty the Recycle Bin.
[x] Temporary files [34.7 MB]
Programs sometimes store temporary information in a TEMP folder.
Before a program closes, it usually deletes this information.
You can safely delete temporary files that have not been modified
in over a week.
[x] Temporary Windows installation files [380 KB]
Installation files used by Windows setup. These files are left over
from the installation process and can be safely deleted.
[x] Thumbnails [30.1 MB]
Windows keeps a copy of all of your picture, video, and
document thumbnails so they can be displayed quickly when you
open a folder. If you delete these thumbnails, they will be
automatically recreated as needed.

There was still a ton of Microsoft new pollution but it was a bit better.
http://wetakepic.com/images/2018/03/...ft_crap_02.jpg

Yes, I know. From the beginning, I always wanted to clean up
Windows. I spent a decade trying. The mess increased with
every new version of Windows. The poster can do whatever it
wants to do, of course, but I am giving it some good advice.
Forget about it.

Yes, of course you have to have at least one drive in order
to install Windows. But seriously!




ultred ragnusen wrote:

John Doe wrote:
I think much can be avoided if you disable the drive(s) while
installing Windows. Then, Microsoft will force only two
folders onto the drive... "System Volume Information" and a
recycle bin. Those folders are neatly hidden via View in the
file manager properties.

And maybe a third folder named "Recovery".
Also hidden.
The Borg will have its way. The best you can do is don't
worry about it.

I'm not sure what you mean by "disabling the drives" while installing.
You have to have, at the bare minimum, one disk drive, right?

As for hiding the Microsoft pollution, that's /never/ the goal, as the goal
is to maintain a clean hierarchy that follows clean GUI standards, so let's
not speak of this talk of hiding pollution, which is sort of like crapping
on the floor and covering it up with toilet paper.

The goal is to clean it up as gracefully as possible.

To that end, plenty of people wish to clean up the 1st listed pollution,
which I found out by searching for just the first bit of pollution.
https://duckduckgo.com/?&q=Can+I+del....~WS+directory

For example, this implies that pollution is just a "rollback" release.
Title: What is this "$Windows.~WS" crap?
https://answers.microsoft.com/en-us/...6-0ff8c6355d90

That same discussion suggests the "disk cleanup" tool:
c:\windows\system32\cleanmgr.exe

Hence, I ran that "Disk Cleanup for (C" tool and checked the box for
[Clean up system files], and then I checked all available options:
http://wetakepic.com/images/2018/03/02/disk_cleanup.jpg

[x] Windows Update Cleanup [10.0MB]
Windows keeps copies of all installed updates from Windows
Update, even after installing newer versions of updates. Windows
Update cleanup deletes or compresses older versions of upates
that are no longer needed and taking up space. (You might need
to restart your computer.)
[x] Windows Defender Antivirus [1.14MB]
Non critical files used by Windows Defender Andivirus
[x] Windows upgrade log files [260MB]
Windows upgrade log files contain information that can help
identify and troubleshoot problems that occur during Windows
installation, upgrade, or servicing. Deleting these files can make it
difficult to troubleshoot installation issues.
[x] Downloaded Program Files [0 bytes]
Downloaded Program Files are ActiveX controls and Java applets
downloaded automatically from the Internet when you view certain
pages. TGhey are temporarily stored in the Downloaded Program
Files folder on your hard disk.
[x] Temporary Internet Files [5.21 MB]
The Temporary Internet Files folder contains webpages stored on
your hard disk for quick viewing. Your personalized settings for
webpages will be left intact.
[x] System created Windows Error Reporting [166 KB]
Files used for error reporting and solution checking.
[x] DirectX Shader Cache [0 bytes]
Clean up files created by the graphics system which can speed up
application load time and improve responsiveness. They will be
re-generated as needed.
[x] Delivery Optimization Files [2.66 MB]
Delivery Optimization files are files that were previously
downloaded to your computer and can be deleted if currently
unused by the Delivery Optimization Service.
[x] Device driver packages [0 bytes]
Windows keeps copies of all previously installed device driver
packages from Windows UPdate and other sources, even after
installing newer versions of drivers. This task will remove older
versions of drivers that are no longer needed. The most current
versions of each driver package will be kept.
[x] Previous Windows installation(s) [1.61 GB]
Files from a previous Windows installation. Files and folders that
may conflict with the installation of Windows havfe been moved to
folders named Windows.old. You can access data from the
previous Winodws installation in this folder.
[x] Recycle Bin [2.49 MB]
The Recycle Bin contains files you have deleted from your
computer. These files are not permanently removed until you
empty the Recycle Bin.
[x] Temporary files [34.7 MB]
Programs sometimes store temporary information in a TEMP folder.
Before a program closes, it usually deletes this information.
You can safely delete temporary files that have not been modified
in over a week.
[x] Temporary Windows installation files [380 KB]
Installation files used by Windows setup. These files are left over
from the installation process and can be safely deleted.
[x] Thumbnails [30.1 MB]
Windows keeps a copy of all of your picture, video, and
document thumbnails so they can be displayed quickly when you
open a folder. If you delete these thumbnails, they will be
automatically recreated as needed.

There was still a ton of Microsoft new pollution but it was a bit better.
http://wetakepic.com/images/2018/03/...ft_crap_02.jpg

John Doe wrote:

Yes, I know. From the beginning, I always wanted to clean up
Windows. I spent a decade trying. The mess increased with
every new version of Windows. The OP can do whatever he
wants to do, of course, but I am giving him some good advice.
Forget about it.

I agree that we only have two options:
1. Try to clean up the inherently objectionable Microsoft garbage, or,
2. Try to just ignore the Microsoft garbage and live in squalor.

Moving on to the next Windows crapware folder, it looks like, again, many
people want to delete it.
https://duckduckgo.com/?q=can+we+del...+10+esd+folder

The name stands for "Electronic Software Delivery" according to this:
https://answers.microsoft.com/en-us/...1-20d565d28527

According to this article, the Electronic Software Delivery folder is used
by "Push Button Reset feature to reset your computer back to its original
install state", whatever that means, given the disk drive is brand new and
has only had this one installation of Windows 10 on it.
https://answers.microsoft.com/en-us/...a-e24381f91e30

It seems that everyone is confused because according to this article, the
ESD folder is used "to make an ISO to keep as backup", which is pretty much
the last thing I need since I just installed Windows 10 from an ISO disc.
https://www.tenforums.com/general-su...er-disk-c.html

This description of the ESD folder is even more confusing in that it says
that Microsoft uses the ESD folder "to upgrade your current build of
Windows 10", but I just installed it from the latest ISO so it shouldn't
need an upgrade.
https://www.windows10forums.com/thre...-deleted.8722/

Anyway, I manually deleted it, so now this is what I need to attack next.
- MSOCache
http://wetakepic.com/images/2018/03/...ft_crap_03.jpg

ultred ragnusen wrote:
Microsoft polluted my brand new disk drive - what can be deleted?
http://wetakepic.com/images/2018/03/...ft_crap_01.jpg

Given these are the only directories I care about:
http://wetakepic.com/images/2018/03/02/whatisneeded.jpg

I'm first researching if I can just delete, en masse, the Microsoft
pollution.

Do you know off hand?

For the tribal knowledge, I'll tackle this Microsoft pollution one by one.
1. $Windows.~WS (and BT)
2. ESD
3. MSOCache
4. ouput
5. PerfLogs
6. Windows.old

HINT: Poor coding standards are in evidence galore.

Start : Run : cleanmgr

Click the system files button, which will start cleanmgr
running a second time. When the system disk is scanned,
it should locate the Windows.old.

The Windows.old can show as much as ~20GB of files. It is the
most significant thing to remove.

You want cleanmgr to remove the contents of that. Do *not*
try to throw Windows.old into the trash. I tried that, and
I was sorry later. (I now have a folder inside there which
cannot be deleted, even with Cleanmgr, and Linux would not
touch it either.)

Don't select "Windows Update cleanup". One of the cleanup
options starts compressing files in WinSXS, and this can take
*three hours*. Um, don't do that.

1. $Windows.~WS (and BT) === one is for media download, one
is for install staging. If you're happy with
your install, you can delete them.
2. ESD === best guess, yet another install folder.
.wim and .esd files normally hold ~3GB of files
for an install. They're like a kind of tar or zip
format. The ESD flavor is encrypted. In this case,
whatever is in there is likely to not be encrypted,
and this is just a misnaming. They may have built
a WIM in there.
3. MSOCache
4. ouput
5. PerfLogs
6. Windows.old === remove only with cleanmgr

The ones where I haven't commented, have a look and make up your
own mind.

The only real reason I have to answer this post, is the warning
about the Windows.old. The rest is discretionary. The core
of the OS is in C:\Windows and C:\Windows\System32. While the other
parts were put there by Microsoft, the folders could well be
re-generated on demand if they're ever needed again. But
to be sure, toss the names into Google and decide for yourself.

I don't have nearly your intolerance for this stuff. I have
manually deleted the ~WS and ~BT, but in subsequent Win10 releases,
Microsoft started chopping down the content in there to around
250KB, so they no longer represent a waste of space. They
aren't cleaned to zero, but the leftovers are typically quite
small. If the Upgrade process succeeded, they could well be
close to empty.

Windows.old will delete itself in 10 days, but you can clean
that out right now (removing the ability to revert to whatever
OS is inside Windows.old) by using Cleanmgr.

Paul

Paul wrote:

Start : Run : cleanmgr

Click the system files button, which will start cleanmgr
running a second time. When the system disk is scanned,
it should locate the Windows.old.

Thanks Paul for that suggestion of running the system part of:
c:\windows\system32\cleanmgr.exe

That got rid of some of the directories, leaving only these:
http://wetakepic.com/images/2018/03/...ft_crap_02.jpg

I just completed figuring out how to get rid of the Office 2007 MSOCache,
which turns out to be super simple, which is to just manually MOVE it to a
location of your choosing - but - the research I did pointed out that any
advice you find on the net for moving or deleting MSOCache is dependent on
the version of MS Office.

For exammple, in MS Office 2003, the cleanup tool you mentioned will clean
it up, but not in MS Office 2007. Likewise, the Office 2003 installation
has a LIS tool for MOVING the MSOCache, which was deprecated by the time of
Office 2007.

Of course, you wouldn't need the C:\MSOCache hierarchy in the root
direcdtory if the installer of MS Office 2007 had selected "Run
all from My Computer" at the time of installation of MS Office 2007, but
now it's too late for that option.
https://i.stack.imgur.com/KM4vq.png

In the end, I've moved the MSOCache out of the root hierarchy where the
options a
a. Burn C:\MSOCache to CDROM (it's about 400MB) and then change the
registry (scores of pointers) for all instances of C:\MSOCache and change
them to E:\MSOCache (or whatever the drive letter of your optical drive).

b. Copy C:\MSOCache to C:\app\editor\suite\msoffice\msocache and then
change the registry as above, to point there.

d. Burn or copy C:\MSOCache, and leave the registry alone, and just copy it
back temporarily whenever you change something in MS Office options.

Here's my root directory cleaning status as of the moment...
http://wetakepic.com/images/2018/03/...ft_crap_04.jpg

I am looking up how to safely get rid of the next item on the list, namely
PerfLogs, as we type.

ultred ragnusen wrote:

Anyway, I manually deleted it, so now this is what I need to attack next.
- MSOCache
http://wetakepic.com/images/2018/03/...ft_crap_03.jpg

It seems to be a common question how to delete MSOCache:
https://duckduckgo.com/?q=can+I+dele...socache+folder

This implies it's related to Microsoft Office where it implies the
idiotically located directory is used so that you don't have to insert the
MS Office CDROM in order to update your existing MS Office installation.
https://answers.microsoft.com/en-us/...c-68b599b31bf5

You wouldn't need it if the installer of MS Office 2007 had selected "Run
all from My Computer" at the time of installation of MS Office 2007, but
now it's too late for that option.
https://i.stack.imgur.com/KM4vq.png

This says we can use the "Windows Cleanup Wizard" to remove MSOCache where
it warns "Warning Never delete the MSOCACHE folder by using Microsoft
Windows Explorer".
https://support.microsoft.com/en-us/...ource-msocache

Of course, that's dead wrong because the Windows Cleanup Wizard appears to
just be another name for the disk cleanup utility that we already ran,
which didn't wipe out the MSOCache. However, that article does link to a
"local install source" LIS tool that will allow you to move that
idiotically located MSOCache directory to somewhere more reasonable than
root (like inside the MS Office hierarchy, for starters).
http://www.microsoft.com/downloads/d...5-b812ba0fed3e

This just mirrors the same bad advice above.
https://forums.techguy.org/threads/e...ocache.582673/

This explains more about how the idiotically located MSOCache directory is
a LIS (local install source) for MS Office but it repeats the wrong
information that the "Start Run Cleanmgr" tool will clean it up.
http://techdows.com/2009/05/what-is-...e-it-from.html

OK. This explains the error, in that Office 2007 specifically disallows
removal of the MSOCache directory and hence the cleanup wizard doesn't
delete it (which was my experience) when it says
"you cannot remove the Local Install Source feature after the
installation has been completed. The Windows Cleanup Wizard
does not include an option to remove this feature."
https://support.microsoft.com/en-us/...office-program

This article contains a suggestion for deleting the MSOCache directory
AFTER you make a copy of it so that you can copy it back if MS Office asks
for it.
https://www.sevenforums.com/microsof...-msocache.html

But this seems to have the BEST answer for deleting MSOCache where the
instructions show how to first make a copy to optical media, then change
the registry to point to that optical media, and then delete the MSOCache
directory on root.
https://superuser.com/questions/2163...elete-msocache

Based on that article, and noting that a lot of people suggest creating a
junction point, it seems that the simplest way to move the MSOCache is to
just move it, temporarily, and move it back for when it's needed.

A more permanent solution, albeit more work, is to search the registry for
"C:\MSOCache" and change it to wherever you copy the files to, e.g.,
"C:\apps\editor\office\MSOCache" or even to a CDROM at E:\MSOCache\ (which
will ask you to insert the CD when it's needed by MS Office).

Here's the status of my cleanup, with the MSOCache removed just now, where
my next action is to gracefully clean up PerfLogs.
http://wetakepic.com/images/2018/03/...ft_crap_04.jpg

ultred ragnusen wrote:

Here's my root directory cleaning status as of the moment...
http://wetakepic.com/images/2018/03/...ft_crap_04.jpg

I am looking up how to safely get rid of the next item on the list, namely
PerfLogs, as we type.

Like all the other garbage Microsoft pollutes the root with, lots of people
have already asked if they can safely delete that idiotically placed
PerfLogs directory.
https://duckduckgo.com/?q=can+I+dele...logs+directory

This article implies the directory can be deleted and that it's used by the
"system performance logs and diagnostics", which will re-create it if it
wants to.
https://answers.microsoft.com/en-us/...4-0f9520a0b776
https://www.easytweaks.com/safe-dele...older-what-is/

This article says "perfmon" and "winsat" use the folder and will
re-generate it:
http://www.techsupportforum.com/foru...er-516750.html

More logically, since it will be re-generated, this article explains how to
move PerfLogs to a more sensible place than the root hierarchy.
https://mymce.wordpress.com/2017/12/...in-windows-10/

robocopy ´C:\PerfLogs¡ ´C:\Windows\PerfLogs¡ /E /COPYALL /XJ
takeown /F ´C:\PerfLogs¡ /R /A /D Y
icacls ´C:\PerfLogs¡ /grant Administrators:F /T /C
rd /s /q ´C:\PerfLogs¡
mklink /J ´C:\PerfLogs¡ ´C:\Windows\PerfLogs¡

But that still leaves the link cluttering up the root directory.
For now, until I can figure out how to make the system /generate/ the
PerfLogs folder somewhere else, I'll just delete it.

Here's the cleanup status where root is as clean as I can get it, I think.
http://wetakepic.com/images/2018/03/...ft_crap_05.jpg

On Thu, 1 Mar 2018 23:14:15 -0800, ultred ragnusen wrote:

HINT: Poor coding standards are in evidence galore.

Your argument seems to be with the architecture,not with the coding
standards which you can't see or evaluate unless you have access to
the source files. So you're firing at the wrong target.

On Fri, 2 Mar 2018 00:00:23 -0800, ultred ragnusen wrote:

As for hiding the Microsoft pollution, that's /never/ the goal, as
the goal is to maintain a clean hierarchy that follows clean GUI
standards, so let's not speak of this talk of hiding pollution,
which is sort of like crapping on the floor and covering it up
with toilet paper.

Well this 'pollution' as you call it seems to stem from poor
understanding about how Windows works. Presumably it makes perfect
sense to the people who designed it. Maybe you should work on that
rather than hacking away at the structure.

On 3/2/2018 9:57 AM, Wolf K wrote:
On 2018-03-02 02:14, ultred ragnusen wrote:
Microsoft polluted my brand new disk drive - what can be deleted?
http://wetakepic.com/images/2018/03/...ft_crap_01.jpg

Given these are the only directories I care about:
http://wetakepic.com/images/2018/03/02/whatisneeded.jpg

I'm first researching if I can just delete, en masse, the Microsoft
pollution.

Do you know off hand?

For the tribal knowledge, I'll tackle this Microsoft pollution one by
one.
1. $Windows.~WS (and BT)
2. ESD
3. MSOCache
4. ouput
5. PerfLogs
6. Windows.old

HINT: Poor coding standards are in evidence galore.
I am always amazed by these guys. They get a new installation of
windows 10, or an new computer with Windows 10, and then before the know
know any thing about Windows 10 try to modify it. They never try to
learn what native Windows 10 will do and is capable of.

They want all kinds of functionality in the OS, but refuse to permit the
OS to establish the information that it needs to provide that functionality.

I guess it is possible that the Original Poster, bought a computer like
I saw the other day. It had a decent processor and Windows 10. What it
did not have was main storage capacity (27 GB used out of 32GB or 5 GB
free) to do an update of the OS. The purchaser of this computer will
never have a good system as it will always be locked up trying to
install the current updates.

They should do some research before even considering a computer like
this. MS recommends a minimum of 15 GB free, I have found for easy of
update, Windows 10 needs at least 17 GB free.

If the OP bought one of these machines and has not messed it up to
badly, he take it back to the store and get a computer with adequate
storage.

--
2018: The year we learn to play the great game of Euchre

On 02/03/2018 07:14, ultred ragnusen wrote:
Microsoft polluted my brand new disk drive - what can be deleted?

You are a known paedophile so **** off.

/--- This email has been checked for viruses by Windows Defender
software.
//https://www.microsoft.com/en-gb/windows/comprehensive-security/



--
With over 600 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

mechanic wrote:

As for hiding the Microsoft pollution, that's /never/ the goal, as
the goal is to maintain a clean hierarchy that follows clean GUI
standards, so let's not speak of this talk of hiding pollution,
which is sort of like crapping on the floor and covering it up
with toilet paper.

Well this 'pollution' as you call it seems to stem from poor
understanding about how Windows works. Presumably it makes perfect
sense to the people who designed it. Maybe you should work on that
rather than hacking away at the structure.

The philosophy of software organization is my shtick.

I don't want to give too much private information, but you can consider me
as considering myself, an expert on "organization" of software, where, had
I lived in Redmond instead of San Jose, I would have had decades of
experience cleaning up Microsoft instead of elsewhere.

Had I organized Microsoft software, we'd all have a better time of it.

IMHO, software organization is no different than organizing your house,
where you have a kitchen, a living room, bathrooms, an office, and a
basement where all the heavy machinery lies.

Your front door enters directly into the living room (which is root).
The heavy machinery room is the Windows directory (the basement).

For Windows to store coal for the furnace in your living room is crazy.