- Joined
- Jan 4, 2017
- Messages
- 46
- Reaction score
- 3
@Trouble You do realize a fragmented MFT [Master File Table] will result in slow performance on mechanical HDDs and the Defragger included with Windows is unable to correct that, or fragmentation in most of the other aforementioned system level access only locations, because it cannot gain system level access right?
You can analyze the aforementioned areas that require system level access with Contig/Power Defragmenter by utilizing PsExe (another SysInternals program) to launch Contig/Power Defragmenter as System [NT AUTHORITY\SYSTEM].
It shouldn't matter whether one's an "every day user" or a power user... the best tool for the job should be used, otherwise one runs the risk of doing a lot of work for nothing, discovering they should have used the best tool for the job to begin with.
You can analyze the aforementioned areas that require system level access with Contig/Power Defragmenter by utilizing PsExe (another SysInternals program) to launch Contig/Power Defragmenter as System [NT AUTHORITY\SYSTEM].
It shouldn't matter whether one's an "every day user" or a power user... the best tool for the job should be used, otherwise one runs the risk of doing a lot of work for nothing, discovering they should have used the best tool for the job to begin with.
- For example, you clearly believe the "every day user" should simply use the defragger included with Windows, however what happens when they have MFT fragmentation? Not only will the stock defragger not be able to inform the user, the user won't even be aware that's the cause until after significant time is spent researching forums on line. Since I believe no one likes to waste their own time, shouldn't the best tool for the job be used to begin with, thereby negating all of that?
Last edited: