Jump to content











Photo
- - - - -

Ultimately Stop c:\ used space bulging from torquoise to red (or almost)


  • Please log in to reply
15 replies to this topic

#1 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 20 June 2019 - 11:07 PM

Hello folx,

I remember discussing *.etl proliferation on c:\ with wonko and alacrán once. there was no effective stopping at the time, as the system would automatically recreate them, thus augmenting used space (to the obvious detriment of free space on c:\. 

Well, now I think I got it done. it is still about resorting to the "infamous" primo ramdisk (or any other customizable ramdisk). In my case, even if u set it to the maximum, with the direct I/O and Dynamic Memory Management options, it will occupy as much space in ram as needed, so do not worry (in my case not more than 5gb in Z:\ (ramdisk)). the capture shows what directories want moving from C:\ to Z:\ and rejunctioning in the right places in C:\ ---> this means it will no longer be C:\'s problem, it will be Z:\ problem (ram, for all we care). at least we can count on an unbulging c:\.

nino

Attached Files



#2 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 22 June 2019 - 04:45 AM

my latest vhd: 870mb --> lz4 260mb; still working without bulging



#3 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 23 June 2019 - 11:54 AM

one more caveat: in order to make sure everything is ok, I suggest u search for *.etl to make sure all of them reside in Z:\ (which means not in C:\); should any new etl file show its location on c:\, simply open primo ramdisk and make a new directory with the same name as the one the new etl file is in, paste it to the Z:\ location and rejunction it back on its original place. the event is rare, though, i.e. highly improbable, but still  possible.

nino 



#4 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14960 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 23 June 2019 - 12:44 PM

Hmmmm. :dubbio:

 

Idea 1:  :lightbulb: set a fixed size for .etl files

Idea 2:  :idea: disable all or most obnoxious channels

 

Semi-random link:

https://www.nirsoft....nnels_view.html

 

:duff:

Wonko



#5 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 23 June 2019 - 04:42 PM

Tx, Wonko.
If I have understood correctly, the software u propose enables the user to even stop .etl file creation. I can't get a full view of it 'cause I am not at home. I'M answering from a cell phone.
Nino

#6 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 23 June 2019 - 11:00 PM

Well, thanks to Wonko, I have managed to identify a windows\system32\winevt dir full of *.etl files; well, what I did was move it to z:\ and rejunction it to windows\system32 --> the etl files have now disappeared.



#7 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 10 July 2019 - 12:02 AM

another tiny bit of saving, ... well it could be a huge bit if u have big wallpapers in slideshow - solved this too. how? same method: the ram way. 

locate %appdata%\roaming\microsoft\windows\themes, leave slideshow.ini where it is but move the rest of the files u find to ramdisk z:\ and make symbolic links of them back to %appdata%\roaming\microsoft\windows\themes.

u will see considerable space and time improvements, even with big pictures.

cheers

nino



#8 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 11 July 2019 - 06:05 PM

2 more caveats, one concerning photo editing, the other periodic routine work on our part. 

1) with full vhd (wof-compress) and vhd.lz4 compression, when u open a picture directory, u might experience pictorial thumbnails immediately turning into indistinct neutral blank thumbnails, which is a bit of a nuisance; u might try working on ur photos more comfortably thru the plain vhd (not the lz4-compressed version); if it acts the same (blank thumbnails), try enlarging the vhd to 2gb, and of course leave the lz4 intact for later (when u have finished).

2) every now and then, it is convenient to make a general search for *.etl and $$* files: should u c any of them on c:\, reach the directories they are in, move them to z:\ (ramdisk) and junction them back into their original positions.

That is about it for now.

Pls, contribute to the stability in vhd used space size in any way u can.

nino



#9 AnonVendetta

AnonVendetta

    Silver Member

  • Advanced user
  • 735 posts
  • Location:A new beginning.....
  • Interests:Self-development, computing

Posted 12 July 2019 - 07:02 AM

Get rid of:

Hiberfil.sys

Pagefile.sys

Swapfile.sys

 

Create junctions for:

 

C:\Windows\Temp and for each user's temp in \AppData\Local\Temp, and create environment variables for both

 

SoftwareDistributton (updates)

 

C:\Windows\Installer

 

$Recycle.bin

 

Create an empty text file to replace System Volume Information, remove txt extension

Delete Recovery folder in C drive root

Trim down Boot folder in C drive root

 

Change Program Files and Program Files (x86) locations in Registry, robocopy and create junctions. Also don't install programs on C unless not avoidable

 

Don't update Windows

 

Enable NTFS compression if C drive is on an SSD

 

Delete all Metro apps from your image (if running W10), they have a tendency to not work if not installed on C, especially the ones bundled by Microsoft. If you need to use Metro apps then set up a unmodified Home/Pro virtual machine not located on C. Or just use LTSB/LTSC.

 

Trim down your image with MSMG Toolkit (free, it's what I use) or NTLite (paid) to reduce overall size.

 

If you really must update, install security updates only, not cumulatives. WSUS Offline can grab these, or WHDownloader. Or get them manually from Microsoft''s website (forgot what it's called, but it has almost every Windows update ever released). And don't junction C:\Windows\Installer,  C:\Windows\Temp,  or SoftwareDistribution (unless you like getting bizarre messages when running SFC, dism, or PowerShell).

 

If not running Windows in a ramdisk, ignore most of what I've said, just let Windows manage itself for the most part (but I still like to rip components to reduce installed footprint).



#10 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 12 July 2019 - 09:33 AM

My Dear Unprejudiced Vendetta, 

I agree with u totally and thoroughly on almost all points, so much so that I have already done what u have suggested here, but one thing - the installer (as most of these things are moved to ramdisk (which is nothing once u turn it all off) and junctioned back to their original positions (so they point to nothing in the end)): windows needs the folder in order to install anything or keep anything installed.

nino 



#11 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 12 July 2019 - 04:13 PM

sorry about the installer, vendetta, I misread ur post, now I see it more clearly, so 100% coincidence with what I already do, as my explanation points out, after all.



#12 AnonVendetta

AnonVendetta

    Silver Member

  • Advanced user
  • 735 posts
  • Location:A new beginning.....
  • Interests:Self-development, computing

Posted 12 July 2019 - 06:15 PM

Edit: Original post deleted, I posted a reply in the wrong topic.



#13 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 13 July 2019 - 11:11 PM

for those of u who use Imdisk for ramdisk, here is a nice purge file for automating the ridding of *.etl and $$* files from the filedisk. unfortunately, the imdisk software is a little trickier for creating customized folders on startup, so instead of moving those files above into ram, u can delete them from a mounted h:\vhd and then lz4 it all (even if the system in ram recreates the same files and folders, who cares? once u shut it all down, upon next rambooting it will resort to the last version u had when u had booted in the first place.).

of course, the batch file might want extending when u have to rewimboot.

nino

Attached Files



#14 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 14 July 2019 - 12:27 PM

new purge.bat (including the deletion of the recycle bin)

Attached Files



#15 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted 2 weeks ago

I realized some files and directories in the vhd can be erased without so much hindrance to the functionality of the system in order to make an even smaller vhd: bootmgr can be the one and only lonely file in the root dir (the other files are not needed); the boot dir in the root can contain bcd only (logs and other stuff not needed); the other boot dirs (in windows, windows\system32, etc, if any, are not needed); the only language dirs needed are the ones in windows, windows\system32, and windows\syswoa or something). Like this, you will not have the windows logo and the circle at the start and the visibility of the f8 bootmenu (the functionality still stays, so if u want to enter safe mode u need to go down to 1st, 2nd or 3rd option (safe mode, safe mode with networking and safe mode with command prompt respectively). u will have freed a few hundred kbs, though.



#16 antonino61

antonino61

    Frequent Member

  • Advanced user
  • 409 posts
  •  
    Italy

Posted A week ago

I have managed to "purge" the services, little by little, with many trials and few errors. as Wonko once suggested, all u have to do is check the dependencies, both active and passive, and proceed with a backup copy of the vhd to revert to just in case something goes wrong. it takes a few hours but it is worth it.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users