Windows 10: How do I remove the wasted space on the right side of a folder window.

When I open a folder in Windows 10. It always opens a window that has a large mostly empty area to the right of the listed folder contents. This area contains a picture of a folder along with the some text indicating the number of items in the folder. The area is almost 100% empty and an absolute total waste of space. But I can't figure out how to get rid of it. Can somebody please tell me how to get rid of this?

(When I right click on the area mentioned above. A popup appears that says "Remove properties...". I'm not sure if this is designed to do what I want or to do something else. But either way. It's always grayed out.)

submitted by /u/GeneralTso_2
[link] [comments]

:)

 

Removing Windows.old folder

I recently had to reinstall my OS (don't ask). Once I did there were files that I couldn't delete. Basically SecuROM files. Anyway long story short I found this workaround that I wanted to share with my fellow newbs. This will work for any file and works like a charm. Just follow the directions. *Toast :toast:
Note: there is no space between "Administrators: (F)" I just had to but one in because it kept giving me an "unhappy face"

When installing Windows Vista, Windows stores any existing installation of Windows on the install partition inside a hidden folder called windows.old. This folder could take up a large amount of disk space.

Note: Please check the contents of the windows.old folder before deleting it to make sure there are no files stored there that you may wish to keep.

Deleting the window.old folder using the disk cleanup wizard
Click start
Type: disk cleanup
Press enter
Select "Files from all users on this computer"
Follow the rest of the instructions listed on the wizard and select the option to delete the windows.old folder
Deleting the windows.old folder manually
1) Open an elevated command prompt

Click start
Type: cmd
right-click it under programs
click Run As Administrator
2) Take ownership


Change the directory to the windows.old folder (e.g. cd c:\windows.old)
Type: takeown /F . /A /R /D Y > NUL
3) grant yourself permission

Type: icacls . /grant:r Administrators: (F) /T /L /Q
4) Delete everything

Make sure you close any explorer or command windows that are looking at or inside the windows.old folder (except for the command window you are using). If you don't, you will receive an error while performing this step.

Type: cd ..
Type: rmdir /S /Q windows.old

 

Windows Folder SiZE ???

64 bit has larger folder sizes than 32 bit.

You will have system restore, page file, and a 4GB hibernate file since you have 4GB of ram.

how to remove windows vista service pack uninstallers to free space:
Code: open a run box (windows + r key, or start menu) vsp1cln.exe It cleans up/removes the backup files to uninstall vista SP1. It saves you lots of disk space at the cost that you cant uninstall SP1. for service pack 2 users, use the following compcln.exe[/quote] Code: Disable hibernation/remove hiberfil.sys (same size as your ram amount, wastes space if you dont use it) start->run-> powercfg -h off[/quote]

 

Quick Access not searching Pictures folder

Summary, that last suggestion didn't work.

• I moved the pictures to another folder temporarily.

• Then I tried to remove the Pictures folder with option one at Add or Remove Folders from This PC in Windows 10 | Windows 10 Tutorials. Even after rebooting, the Pictures folder remained.
• So I tried using option two. Same thing: reboot >> Pictures folder still there.

• Since there were no troubleshooting steps for this scenario, just for the heck of it, I ran through the restore steps. Copied some pictures into the Pictures folder, ran a Quick Access search and initial problem remains: Searching all of QA doesn't find any files in Pictures folder, running search on just the Pictures folder does. I want to run a global search and find matching files in any/all of the Documents, Music, Videos, and Pictures folders.

That article dates from 2015 and I'm guessing is out of date. I hope it didn't create potential future problems in my registry.

Bottom line: I'm still looking for a fix.