Bright Spark wrote:
> Been using this XP for the past several years, and suddenly in the
> past 2-3 weeks, it has started automatically defragging on its own. I
> will notice that response time is dragging, etc., and when I check the
> Task Master it shows dfrgntfs.exe running. I haven't told it to
> defrag and I haven't set any automatic times for it to do so.
>
> I have checked all the Task Schedulers and other places I can think of
> where I might have accidentally set something, but nothing shows any
> auto defrag set.
>
> I would appreciate any help anyone can give me.
>
> Many thanks.
>
> Bright Spark
"Background defragmentation has always been a feature of Windows XP"
So then, why ask "question is why is it defragging since OP didn't initiate it." ??
The plain fact is that Win XP will enable an internal setting (by default) to
AUTOMATICALLY (look it up!) defragment the boot disk when the PC is idle...
So the OP need do nothing to initiate this effect as it is already enabled!
Also, as Mr Grey points out, it occurs when the PC IS idle and desists when the user
intervenes (similar to the effect of a screensaver) and thus, cannot be responsible
for the slowing down of a PC!
It is certainly NOT the effect of some malware, but a normal in-built feature of
WinXP!
Finally, to disable this feature (why you would want to, I don't know) reset the
following registry value :
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction]
"Enable"="Y"
...and change it to :
"Enable"="N"
...to disable automatic boot-disk background optimization by defrag.exe
==
Cheers, Tim Meddick, Peckham, London. :-)
"Unknown" <unk...@unknown.kom> wrote in message
news:Oe6Brwey...@TK2MSFTNGP06.phx.gbl...
A process can still be in memory but use hardly any memory resources.
When the PC is first perceived to be "idle" defrag.exe starts and begins it's scan
and the defragmentation (optimization). Then, when the user intervenes, the process
should go into a suspended mode waiting for the PC to become "idle" and begin to
defragment again.
While other applications are actively receiving user input the "defrag" process
should not me using any more than a bare minimum of memory (below 100k) and therefore
has no impact on PC performance.
If you are still bothered by this normal WinXP feature, again, as I wrote in my other
post, you can turn it off by locating the registry value :
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction]
"Enable"="Y"
...and change it from a "Y" (for Yes) to an "N" (for NO) :
"Enable"="N"
...to disable automatic boot-disk background optimization by defrag.exe
==
Cheers, Tim Meddick, Peckham, London. :-)
"Bright Spark" <brightspark...@nomore.com> wrote in message
news:hfifq55u8ngkfukcu...@4ax.com...
> Well, thank you for your reply, but from what I have discovered while
> trying to solve this mystery is that even though it (supposedly) has
> always been a feature of Windows XP, it should stop once the computer
> is no longer idle. But it doesn't stop. If it were to occur while
> the PC was idle I doubt I would have noticed it at all, but it
> continues on while I am trying to work at my computer and does,
> indeed, slow it down while it "does its thing" until I end the
> process.
>
> Also, I have been using this computer for over 3 years almost 8-10
> hours per day since it is a function of my work, and I have never
> noticed it doing this "background defragmentation" before. It's very
> odd.
>
> Bright Spark
>
>
In actual fact, in this automatic background defrag, it's another sub-process that
actually governs it : "dfrgres.dll".
But the setting I quoted absolutely does govern the effect of automatic background
boot-disk optimization and no other. Take it or leave it....
==
Cheers, Tim Meddick, Peckham, London. :-)
"Bright Spark" <brightspark...@nomore.com> wrote in message
news:vtkfq598fgfhkt6k7...@4ax.com...
> On Mon, 22 Mar 2010 20:10:46 -0000, "Tim Meddick"
> <timme...@gawab.com> wrote:
>
>>
>>As I said in my last post to "Unknown", "defrag.exe" is only actively scanning /
>>defragmenting when the PC is idle.
>>
> "defrag.exe" is not the process that is running. It is "dfrgntfs.exe"
>
>>A process can still be in memory but use hardly any memory resources.
>>
>>When the PC is first perceived to be "idle" defrag.exe starts and begins it's scan
>>and the defragmentation (optimization). Then, when the user intervenes, the
>>process
>>should go into a suspended mode waiting for the PC to become "idle" and begin to
>>defragment again.
>>
>>While other applications are actively receiving user input the "defrag" process
>>should not me using any more than a bare minimum of memory (below 100k) and
>>therefore
>>has no impact on PC performance.
>
> The process that starts automatically running on my computer,
> "dfrgntfs.exe" is using between 500-600k and is definitely impacting
> performance.
>>
>>If you are still bothered by this normal WinXP feature, again, as I wrote in my
>>other
>>post, you can turn it off by locating the registry value :
>
> Probably wouldn't be wise for me to do this since we seem to be
> talking about two different pieces of the defragging process.
>>
>>[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction]
>>"Enable"="Y"
>>
>>...and change it from a "Y" (for Yes) to an "N" (for NO) :
>>
>>"Enable"="N"
>>
>>...to disable automatic boot-disk background optimization by defrag.exe
>>
>>==
>>
>>Cheers, Tim Meddick, Peckham, London. :-)
>>
>>
> Thank you again.
>
> Bright Spark
I will explain.
You are an idiot ,because you make statements without knowledge....
http://www.extremetech.com/article2/0,2845,1149277,00.asp
==
Cheers, Tim Meddick, Peckham, London. :-)
"Unknown" <unk...@unknown.kom> wrote in message
news:O6BkPHgy...@TK2MSFTNGP06.phx.gbl...
The AUTOMATIC BOOT-DISK OPTIMIZATION EXECUTED BY DEFRAG.EXE EVERY THREE DAYS CALLING
EITHER DFRGNTFS.EXE OR DFRGFAT.EXE CONTROLLED BY DFRGRES.DLL AND UTLIIZING
LAYOUT.INF, IS SET BY DEFAULT BY THE REGISTRY SETTING :
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction]
"Enable"="Y"
PLEASE NOTICE THE "Enable"="Y" THAT IS "Y" FOR YES ENABLE
THAT IS THE DEFAULT SETTING!
==
Cheers, Tim Meddick, Peckham, London. :-)
P.S. I WILL admit that the URL that I quoted was a bit of a loss, I thought it
explained further.
I have so far only got the odd references from here and there - nothing that confirms
and explains the whole thing. Nut be assured I am right about XP automatically
optimizing the boot disk using background disk defragmentation and it being enabled
by default AND not scheduled through the Task Scheduler (although, Task Scheduler
must be enabled for it to work).
"Unknown" <unk...@unknown.kom> wrote in message
news:OQFQAhg...@TK2MSFTNGP02.phx.gbl...
> You are an idiot.
>
> I will explain.
>
> You are an idiot ,because you make statements without knowledge....
>
> http://www.extremetech.com/article2/0,2845,1149277,00.asp
No, he's a troll, which is even worse than being an idiot.
Making a mistake is acceptable. None of us is perfect and we all make
mistakes from time to time. But his working so hard to be anonymous
while attacking so many of us is the mark of a troll, and is not
acceptable.
--
Ken Blake, Microsoft MVP (Windows Desktop Experience) since 2003
Please Reply to the Newsgroup
> As I said in my last post to "Unknown", "defrag.exe" is only actively scanning /
> defragmenting when the PC is idle.
>
> A process can still be in memory but use hardly any memory resources.
And to add to and perhaps clarify that, if some process or program is
in memory, but is not active, and other processes or programs need the
memory, the memory used by the inactive process or program quickly
becomes page file memory, not real RAM. RAM is used by the most active
programs, and the inactive ones get paged out until they need to do
something.
John
* There is no user input.
* The CPU and disk usage is less than 10 percent.
* The system is not running on battery power.
* Presentation programs (such as a slide show or movie playback)
are not running.
Finally, it should be noted that usually the Prefetch defragmentation
would be relatively fast, it doesn't take a very long time to optimize
the prefetch files, after all, the files are optimized every three days
and they don't change all that often so there is usually not all that
much moving around to do with the files. If you want to acquaint
yourself with the Prefetch mechanism read the relevant section here:
http://msdn.microsoft.com/en-us/magazine/cc302206.aspx
Windows XP: Kernel Improvements Create a More Robust, Powerful, and
Scalable OS
Please be advised that there are all kinds of misconceptions about
Prefetch and that 'false' tweaks abound all over the internet, don't
believe any of these tweaks, the author here:
http://members.rushmore.com/~jsky/id14.html sums it up accurately:
[Quote]
Windows XP Prefetching by default is already optimized. There are no
tweaks that do anything but hurt performance. Anyone making any claims
otherwise does not understand how Windows Prefetching works. They also
do not provide documented and accurate reproducible testing to prove
that some "tweak" does work. This nonsense has been copied off one site
to another.
[end quote]
I don't know why dfrgntfs.exe is running and bogging down your system.
This much I can tell you, I don't remember ever having seen this running
in my Task Manager (yes, Prefetch is enabled on my machine and yes the
Task Scheduler service is set to start automatically). I am not saying
that the task doesn't show as part of the boot optimization, I don't
know if it does or not, I'm only saying that if it does I can't remember
ever seeing it showing in the Task Manager... but then if the task only
occurs when the computer is idle for 10 minutes or more, well I wasn't
at the computer to see it or I was asleep at the keyboard...
I think this is probably being launched by one of your maintenance
application. Under which user name is the process running?
John
Bright Spark wrote:
> To tell you the truth, John, I have found a whole lot of this thread
> misleading since I first posted my request for assistance. I was
> hoping for some help in this group, but instead find it seems more
> like a contest of who knows what and calling people names, etc. Can't
> imagine what good all that does other than perhaps some ego-stoking.
> Certainly doesn't actually help anyone looking for solutions,
> unfortunately.
>
> As far as help, I guess I have been informed now that my computer has
> always been doing this whether I knew it or not, and I can change the
> registry if I want (but why would I want to), take it or leave it.
>
> I was in here asking for help because my computer has not, in fact,
> been doing this. I am no computer expert, but I'm not a neophyte
> either and I do at least know some of the more common places to check
> and see what might be slowing things down when they do slow down. In
> other words, hoping perhaps for some suggestions as to why it would
> suddenly start doing this and thinking I might get some ideas here.
> That's what I get for thinking.
>
> Bright Spark
I am "confusing" things am I?
If defrag has got nothing to do with the boot optimize process, as you say, then why
is the registry key that controls the boot optimize process called :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Dfrg\BootOptimizeFunction
???
You will notice the "\Dfrg\" in the middle of that reg-path. Also, under the above
key is a reg-value called : "ResourceDllName"="DfrgRes.dll"
DfrgRes.dll being part of the automatic background boot-disk optimization performed
by defrag.
The WinXP boot-disk optimization is performed by a mix of (background) disk
defragmentation and also improved performance by the realigning of the prefetch
processes.
This happens once every three days, as a rule, but can be forced by rebooting (twice)
and executing the command :
Rundll32.exe advapi32.dll,ProcessIdleTasks
I think it is YOU that do not read the other posts, plus you didn't even check out
the registry setting or even look it up!
==
Cheers, Tim Meddick, Peckham, London. :-)
"Unknown" <unk...@unknown.kom> wrote in message
news:uNWAmhp...@TK2MSFTNGP02.phx.gbl...
You may think this at odds, but the first bit of advice I gave still stands :
While I have learnt that the defragmentation (background) process is concerned only
with defragmenting the prefetch system files. Thing I already said include; it is
still automatically called every three days and is not set in the Task Scheduler
although Task Scheduler must be enabled for it to work.
And more importantly, it should NOT interfere (slow down) your PC and should NOT
consume all but the smallest of memory resources (you said your "dfrgntfs.exe"
process ate 500-600k in my experience it takes a process over 10000k for it to have
any negative impact on PC speed) plus it should desist once user input is detected
(not quit mind you, but stop using up so much memory resources).
And, finally and MOST importantly; if you just don't want this process to begin I
gave you the correct registry setting for you to stop it from happening.
I would not have quoted a registry setting for you to change if it had any serious
consequences.
By stopping automatic boot-disk optimization, you only stop the background defrag
process of the prefetch files (in your case, so "dfrtgntfs.exe" will no longer show
up in Task Manager when you did not start it), you won't stop PREFETCH which, IMHO,
is essential for the smooth running of XP!
==
Cheers, Tim Meddick, Peckham, London. :-)
"Bright Spark" <brightspark...@nomore.com> wrote in message
news:jrlhq5t0n8t6jkorh...@4ax.com...
> Thank you for taking the time, John John. Your explanation certainly
> accounts for why I could not find it anywhere in any scheduling
> settings.
>
> I believe I have possibly found at least some of the answer to my
> mystery in a website called "File.Net" - it is possible that it is
> associated with the Indexing Service. I have shut that off and we'll
> see if that solves this problem which, as I say, has only just
> recently been happening, not been going on since I've been using XP.
>
> http://www.file.net/process/dfrgntfs.exe.html
>
> Again, thank you for taking the time to try to help. I appreciate it.
>
> Bright Spark
>
>
>
>
> On Tue, 23 Mar 2010 09:33:46 -0300, John John - MVP
And have told you many times now that if you want to stop it (and there is NO HARM in
doing so) just change the registry setting I gave you and you will be bothered by the
automatic starting of the "dfrgntfs.exe" process anymore....
For one last and final time....
IT HAS GOT NOTHING TO DO WITH SOME MALICIOUS SOFTWARE INVASION CONSPIRACY BY
INVADING VIRUSSES! - IT IS NORMAL!
==
Cheers, Tim Meddick, Peckham, London. :-)
"Bright Spark" <brightspark...@nomore.com> wrote in message
news:npnhq59gjknsgd99m...@4ax.com...
> Thank you, Unknown .....
>
> < clipped >
>
Boot-disk optimization IS the defragmentation and realignment (according to the
contents of the file Layout.inf) of the prefetch system files.
The defragmentation part of the process is performed by the automatic background
calling of defrag.exe which, in turn, start either "dfrgntfs.exe" (in the case of the
OP) or "dfrgfat.exe" and it then defragments the prefetch system files.
Section : "Prefetch", on page :
http://msdn.microsoft.com/en-us/magazine/cc302206.aspx
"Tim Meddick" <timme...@gawab.com> wrote in message
news:ei3rgIsy...@TK2MSFTNGP02.phx.gbl...
The OP should look elsewhere for the reason his PC is so slow;
Look at; the "Run" reg-key (HKCU & HKLM); in the Startup Folder[s] (on your own Start
Menu and the All Users Start Menu) both for excessive and unnecessary entries.
To the OP: You could download and try this [free] program to determine what process
are started automatically by your system :
http://download.sysinternals.com/Files/Autoruns.zip
==
Cheers, Tim Meddick, Peckham, London. :-)
"Unknown" <unk...@unknown.kom> wrote in message
news:ujRnoRsy...@TK2MSFTNGP05.phx.gbl...
After getting statements from two others, agreeing with me about what "Boot-disk
optimization" means (and that includes "Disk defragmenter" auto-starting in the
background, being part of this process), Mr "Unknown" persistently tried to ridicule
me for what I was saying. And I reacted, in possibly not in the wisest of ways, to
this.
To yourself, I believe that I have been nothing but courteous, attempting to convince
you that the "dfrgntfs.exe" process you see IS quite a normal part of XP, what part
of WinXP this is part of, and how, if you still want it to stop, to stop it from
happening.
I just irked me to think that you may be taken down the "blind alley" of thinking
that the process was started by some unauthorized means (like malware) as was
suggested by "Unknown".
As I said, I believe I have been nothing but polite [to you] and you are free to take
"Unknown"s point of view as fact if you like, but it's my own opinion that the
slowness of your PC may coincide with the appearance of the "dfrgntfs.exe" process,
but I doubt that any process that takes up less than 10000Kb of memory (on a system
with 512Mb RAM) would be impacting on that system's performance.
I suggested you look elsewhere for the cause of the slowing down of you PC.
However, I know I could well be wrong about the cause, but with the information I
gave you on how to stop the automatic launching of the "dfrgntfs.exe" process, you
could experiment and prove it to yourself that it is, indeed, the culprit...
I am sincerely sorry if I have displeased you in some way, it was not my intention to
be pedantic.
Go back to your room.
You do not seem to comprehend.Why are you beating a dead horse on this subject
--
Peter
Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.
"Unknown" <unk...@unknown.kom> wrote in message
news:OtI1DmDz...@TK2MSFTNGP06.phx.gbl...
The "beating a dead horse" comment that "Peter Foldes" made was directed at yourself,
and not at "Twayne"...
==
Cheers, Tim Meddick, Peckham, London. :-)
"Unknown" <unk...@unknown.kom> wrote in message
news:%23cEL2yQ...@TK2MSFTNGP04.phx.gbl...
> What makes you think Twayne is a dead horse? (Even though he is)
>
> < clipped >
You ability to read is fantASStic, as usual, and your
experience as abysmal as your knowledge.
==
Cheers, Tim Meddick, Peckham, London. :-)
"Unknown" <unk...@unknown.kom> wrote in message
news:uC45Racz...@TK2MSFTNGP04.phx.gbl...
> Idiot-------you have no sense of humor???
> "Tim Meddick" <timme...@gawab.com> wrote in message
> news:uaMsbQSz...@TK2MSFTNGP02.phx.gbl...
>> Moron!
>>
>> The "beating a dead horse" comment that "Peter Foldes" made was directed at
>> yourself, and not at "Twayne"...
>>
>
> < clipped >
Oh, almost forgot, this is on Windows 7 x64 incase it matters.
However, I will look into it further, so keep watching this space.
In the mean time, you could create a new Task Scheduler item set to execute
and set it for an idle timeout of your choosing and for it's command, write
in :
Rundll32.exe advapi32.dll,ProcessIdleTasks
...this will start all the PC's "idle tasks", including defrag
optimization, at the timeout you specify.
==
Cheers, Tim Meddick, Peckham, London. :-)
"David" <Da...@discussions.microsoft.com> wrote in message
news:C108A902-5AB9-4557...@microsoft.com...