Solved Disable all Windows log file writes to SSD

Hi,

Just was noticing this as I was going through my Resource Monitor,

Is there a way to disable all the small little writes that windows is doing to create log files?

I'ts probably not a big deal but I am not using windows for any IT reason, server work, or even school, or anything actually important.

-I use "this specific" computer to just browse the internet leisurely and play games.. so i just want it to do nothing but be able to watch movies,play games, and use the internet.. i don't care about absolutely anything else.

Which is why i am curious to disable logging as I won't be doing any troubleshooting on this machine.. if i have a problem i just reinstall windows and start over etc..

I'm curious about this one too but so far I don't have any concerns with SSD writes as their performance are clearly not going to be affected by writing a lot as long as TRIM and garbage collection is working. Unless you're running out of space of course.

Hi,

theveterans, - Yes, I know I am not to be worried about the write life of my SSD. I'm actually not worried about that, I just am doing the hardcore tweaker thing where I have absolutely no reason at all for logging and I know that writing bytes to a disk is so small its ok but I still have no reason for windows to write logs at all..

I do however need the space as I only have a 250gig SSD.. so that goes away real fast.. but anyway i know these logs are so small they won't eat up space.. as far as i know so far!

so the point is, I should be able to tell windows to stop or do not write logs.. Anybody know how to disable logging in windows for (well virutally) everything!? ha..

I won't be needing any log to find out whats going on with my computer.. i Only use this machine for Internet and Games! haha..

All files beginning with "$" in the root of the drive are part of the NTFS file system and are critical to it's normal operation. They are used internally by the file system itself. There is no provision for disabling this.

By design utilities such as Windows Explorer do not show these special files. Tampering with these files in any way would be disastrous for the file system.

Hi,

Ok thank you LMiller7. I kinda already had a hunch that that would be the case. I know windows always tries to "claim" it needs this and that for it to operate for any "standard" user..

the thing is, I am not a standard user.. I don't care about anything on the computer at all. i'm not sharing files, I'm not running documents, i'm not creating videos or making music. The machine I have is strictly for games and internet. I have other computers for my "other" things I need to do with computers that would require all the Proper windows settings and installed components/services etc.. but this one particular machine is my leisure game and internet machine.

for example on this "gaming leisure" machine i can totally screw with it and disable all services and maybe i just want to turn off all antivirus and run the computer without a pagefile and just do whatever with it.

so, if there is truly no way to turn off system logging, then I understand, that is something microsoft didn't implement for the user to change.

it just seems odd to me that windows absolutely has to log though.. but anyway.

thanks

The files in question are not written by Windows but by the NTFS file system. The files are not for diagnostic purposes but are used internally by the file system and are essential for it's normal operation. Without these files NTFS ceases to function, and so does your computer.

There are other log files that are provided for diagnostic purposes but there is no provision for disabling them. Providing for this would further complicate an already complex system and provide no significant benefits.

When real world terms are used as technical terms they may change meaning in quite significant ways. Non technical users ofter see these terms and make unwarranted assumptions about their meaning based on their prior knowledge of the term. This often causes confusion. This is not confined to computers.

People often make assumptions about the meaning of "logging". It is assumed this means keeping a text record of what happened for later use by people. This is not always the case. Often they are used internally and are not even in readable form.

Hi,

Alright that's wonderful. I get your point, and personally "I" do understand people making assumptions about meanings- just look at all my posts trying to help people..mainly a recent high horses guy.. (though I do this- as with logging here apparently,) I also can understand that I do not know the way NTFS "has" to work and if it requires "logging" to operate, then I don't need to have any confusion. That makes sense.

I will have to then just install windows and it's NTFS "logging" to another drive inside the computer and then use another drive. So I will then have 2 separate hard drives. one for windows, and one for just space. I'm sure somehow there is still logging involved with the hard drive with only free space as I will have that formatted to NTFS as well but hopefully I won't see a bunch of $log writes to the 2nd hard drive with just free space.. that's all i wanted to achieve.

I have a small feeling I still may be confusing something so chime in again Lmiller.

Hi,

I thought you might get a kick out of this post from another web page while further researching.. this is too funny. (and not at all the reason I was trying to disable logging. I just wanted to stop the constant writing to my drive.)

taken from a website where people discussed the logging ---- this was the final reply -had a good laugh.


-Response to..
---This is not entirely accurate regarding the $LogFile.
With a prefix of "$", this indicates a system hidden file, and normally inaccessible.
However, what is being reported is that it contains metadata specific to the NTFS drive and files located there.
Direct examination of the file reveals a content far different.
This file contains ALL activity performed by the user and/or system during any activity; up to and including which URLs were accessed, on what date and at what time. While it may identify disk files used/accessed/updated/deleted, it certainly does not limit itself to just that activity.
So, when replying, lets get real. Lets not limit our definitions of content nor mislead those that ask questions. $LogFile is the auditor of the system. It will tell anyone that looks what you've been doing, when you've been doing it, and how it was done. It continully grows and expands. There does seem to be a wrapping capability. At present my system has a 64MB sized $LogFile. I've done far more than 64MB on my system since I built it in 2010. I just don't know if that is the limitation and the system will wrap it at that point.
In any case, it is best to understand a person's question before responding to it. Below is an example of $LogFile content:

brooksndun said:

hopefully I won't see a bunch of $log writes to the 2nd hard drive with just free space.. that's all i wanted to achieve.

Click to expand...

Yes you will see this activity if you use it. You can't turn off NTFS journalling (and nor should you if you could) which is what this $LogFile activity is. Logging isn't the same as journalling but if you are interested you could read about it here: NTFS - Wikipedia, the free encyclopedia

Journaling file system - Wikipedia, the free encyclopedia

interesting indeed, a bit to technical for me but interesting just the same

Hi,

AAh! I just wanted a secondary drive to not make a bunch of writes to it! (the only writes it should be doing is writing whatever it needs to for whatever games/internet i'm using it for) Ok, fine NTFS has to log, fine..

What about Ex-FAT?! haha!

The writes involved with journaling are minimal. They are just a few notes the file system makes before updating the file system. This way if anything should go wrong, such as an improper shutdown, the system can usually be returned to a consistent state. Usually the errors are repaired without the user even being aware there was a problem. In simpler file systems like FAT such errors could have serious consequences.

NTFS has always done this and it occurs on all NTFS drives, including secondary drives. Other advanced file systems, such as in Linux, do something similar.

It is a small price to pay for the improved reliability. It cannot be disabled.

Yes, ok NTFS has to log. It's fine. I just wanted my gaming/internet hard drive to only write when I play games/use interenet. not to log when my power loss happens and my computer shuts down and i need to get back to "gaming"..

I was going to make the 2nd hard drive Ex-fat , but even some games/applications don't allow you to use ex-fat they want NTFS.. so either way i'm forced with NTFS..

ok, start logging that i installed Call of Duty so it can put it back if there is a failure.. ha.

solved.