~df****.tmp files in C:\Documents and Settings\Administrator\Local Settings\Temp

[H@C0]

Hi,
Does somebody know what part of Windows xp creates the ~df****.tmp files in
C:\Documents and Settings\Administrator\Local Settings\Temp?
Every time I start or restart the pc a new ~df****.tmp file is created
The files are 131.072 bytes and the last one cannot be deleted.
When viewing the file I find words like : Root Entry , Photoshop , exif
and Adobe urls
Hans

 

[Thee Chicago Wolf]

Does somebody know what part of Windows xp creates the ~df****.tmp files in

C:\Documents and Settings\Administrator\Local Settings\Temp?
Every time I start or restart the pc a new ~df****.tmp file is created
The files are 131.072 bytes and the last one cannot be deleted.
When viewing the file I find words like : Root Entry , Photoshop , exif
and Adobe urls

Most any application creates some sort of temp (temporary) file while
it is resident in memory or working with a file. In the case above,
you mention Photoshop. While you're editing images, Photoshop creates
a temp file, sometimes in the case of an undo, to revert to in case
you ant to go back. You can always delete them as they are often left
behind when a program doesn't clean up after itself. CCleaner is a
great tool at finding these types of junk files and cleaning them out.

- Thee Chicago Wolf

 

[H@C0]

Most any application creates some sort of temp (temporary) file while
it is resident in memory or working with a file. In the case above,
you mention Photoshop. While you're editing images, Photoshop creates
a temp file, sometimes in the case of an undo, to revert to in case
you ant to go back. You can always delete them as they are often left
behind when a program doesn't clean up after itself. CCleaner is a
great tool at finding these types of junk files and cleaning them out.

- Thee Chicago Wolf

Photoshop has been uninstalled and de folders removed.
In the registry there is nothing left of Photoshop.
I still get the .tmp files. I think tey are created by Windows.
I use CCleaner almost daily.

 

[gmanjoe]

Adobe reader can also create these files because parts of it load when windows does.

 

[H@C0]

Found it !
The file is created by Comodo Firewall

 

[Thee Chicago Wolf]

Found it !

The file is created by Comodo Firewall

Ok! Yes, it's typical of most apps to write SOME kind of dumb tmp
file. Sadly, poor coding that doesn't clean up it's mess is indicative
of a poor application.

- Thee Chicago Wolf

 

[Plato]

Does somebody know what part of Windows xp creates the ~df****.tmp files in
C:\Documents and Settings\Administrator\Local Settings\Temp?
Every time I start or restart the pc a new ~df****.tmp file is created
The files are 131.072 bytes and the last one cannot be deleted.
When viewing the file I find words like : Root Entry , Photoshop , exif
and Adobe urls

May or not be a windows fuction, but an app you have insalled. In any
case, no big deal in any case, as you can delete any temp/tmp files in
any folder whenerer you want to.

 

[Robert]

I'm seeing these files (e.g ~DF7C7C.tmp) created on a system running Windows
XP Embedded. I've seen lots of guesses (anti-spyware programs, Photoshop,
MS-Office, Outlook) but in our case, none of these applications are present.

There is no internet connection and the only application that's running is
one we wrote. I see these files on XP-Pro systems as well. They vary in size
and don't necessarily correspond to a login (I've seen them appear after the
system has been running for a while).

Our application does not explicitly create any TMP files. On the XPE system,
these files usually correspond to startup time (but not always).

My theory is that there is some Win32 API function that can creates these
files (or perhaps file system object in the scripting host). So far, I've not
tracked this down.

These files are a real pain in a "box-on-the-wall" embedded system where
storage space is limited and users have no ability or desire to clean up temp
files.

Perhaps someone at MSFT can answer this question definitively.

 

[Allan]

I'm seeing these files (e.g ~DF7C7C.tmp) created on a system running
Windows
XP Embedded. I've seen lots of guesses (anti-spyware programs, Photoshop,
MS-Office, Outlook) but in our case, none of these applications are
present.

There is no internet connection and the only application that's running is
one we wrote. I see these files on XP-Pro systems as well. They vary in
size
and don't necessarily correspond to a login (I've seen them appear after
the
system has been running for a while).

Our application does not explicitly create any TMP files. On the XPE
system,
these files usually correspond to startup time (but not always).

My theory is that there is some Win32 API function that can creates these
files (or perhaps file system object in the scripting host). So far, I've
not
tracked this down.

These files are a real pain in a "box-on-the-wall" embedded system where
storage space is limited and users have no ability or desire to clean up
temp
files.

Perhaps someone at MSFT can answer this question definitively.

They are created by Windows XP itself. In order to delete them you may have
to restart Windows. There may be third-party programs that delete .tmp files
with minimal user intervention. If you are running up against a storage
limit that is affecting performance you may need to figure out a way to
perform this cleanup periodically.

 

[Saavik]

I think it may not be as simple as that. I have two different applications
that create .tmp files - lots and LOTS of them. However, there was a time
when these .tmp files were automatically deleted (by the OS?). Now I have to
reboot the system in order to delete these - what a pain!
So I decided to run a test.
I rolled my system back to a time when I was fairly certain the .tmp problem
did not occur (Jul 2007) and retested - indeed no problem! Then I ran
Windows Update and retested - problem has returned! Unfortunately, I do not
have the time to install each update separately and retest.

Perhaps someone from Microsoft will become aware of this and push for a fix.