How To Use Sysinternals Contig.exe

[ColTom2]

I think you are right about it being a component of WU.... if I recall
reading it correctly somewhere.

ColTom2

That database file is created as part of the bootup sequence. Usually it
averages around ~1.0 Megabyte. Windows will have open file handle(s)
to the file so it's not something you can delete or possibly modify with a
defrag utility. I can't say for sure, but based on it's location I'd guess
it is
a component of Windows Automatic updates.

 

[Ian D]

I think you are right about it being a component of WU.... if I recall
reading it correctly somewhere.

ColTom2

To get rid of tmp.edb, disable the Automatic Updates service, and
make sure the Distributed Transaction Coordinator service is set
to manual, then reboot. After reboot tmp.edb will either be gone,
or accessible. The other edb.* files are also now accessible and can
be deleted. The tmp.edb is used for Windows update transactions.

 

[ColTom2]

Hi Ian:

You have provided more info about this file than anyone. I am proud of
you!

I assume that if you change the settings back to Automatic Updates and
Distributed Transactions Coordinator that Windows will build the file back
to the same status that it is currently.

I still am amazed that you found this info, as I have looked high and low
off an on for a good period of time.

Thanks so much and a BIG salute to you!

ColTom2

I think you are right about it being a component of WU.... if I recall
reading it correctly somewhere.

ColTom2

To get rid of tmp.edb, disable the Automatic Updates service, and
make sure the Distributed Transaction Coordinator service is set
to manual, then reboot. After reboot tmp.edb will either be gone,
or accessible. The other edb.* files are also now accessible and can
be deleted. The tmp.edb is used for Windows update transactions.

 

[3c273]

Hi Ian:

You have provided more info about this file than anyone. I am proud of
you!

I assume that if you change the settings back to Automatic Updates and
Distributed Transactions Coordinator that Windows will build the file back
to the same status that it is currently.

I still am amazed that you found this info, as I have looked high and low
off an on for a good period of time.

Thanks so much and a BIG salute to you!

ColTom2

And now you've wasted 2 days of your life trying to defrag a 1MB file that
gets deleted on shutdown.
(Sorry, couldn't resist.)
Louis

 

[ColTom2]

I'll close by saying that Ian answered the question and it certainly was
not you.

Bet you learned a little something in the process....(I could say sour
grapes, couldn't resist.)

ColTom2

Hi Ian:

You have provided more info about this file than anyone. I am proud of
you!

I assume that if you change the settings back to Automatic Updates and
Distributed Transactions Coordinator that Windows will build the file back
to the same status that it is currently.

I still am amazed that you found this info, as I have looked high and low
off an on for a good period of time.

Thanks so much and a BIG salute to you!

ColTom2

And now you've wasted 2 days of your life trying to defrag a 1MB file that
gets deleted on shutdown.
(Sorry, couldn't resist.)
Louis

 

[dougyl]

Thousands of files that refuse to defrag.

I would just like to add my experience.

C:\ drive 50% used, over 10,000 fragmented files, refused to defrag with any tool including PerfectDisk 10 and safemode efforts.

The answer was to remove the Page File.Thereafter defrag worked parfectly.

Seemingly there is cross-talk between the page file contents and the fragmented files that effectively locks them.

Full description of the solution by "Gerry" was found at www.eggheadcafe.com/conversation.aspx?messageid=34237057&threadid=34237050

This solution should be more widely known. The problem has occurred on my machines several times and always proved refractory till now. Many thanks to Gerry.

 

[Rick V]

I have to agree with Louis. 2 days to get an answer about how to defrag a 1mb file, that cannot possibly be defragmented, because it is not accessible when created, but is not created if you turn off the auto updates. I guess you could go so far as to dual boot your system, just to find that, because you didn't boot into your Windows OS, the file was never created, hence cannot be defragmented. Sounds like the 'ol catch 22 scenario. I believe you are right, we all learned something in this process (with the apparent exception of ColTom2). I know that I learned that there is no limit to the length of time a person will waste to solve a problem that is

a) So insignificant that it warrants no thought
b) Is not really possible since the file is either there and not accessible, or not there so irrelevent.

This reminds me of a line from the 1988 movie Off Limits by the Fred Ward character. "You guys are floating in a rowboat in a cesspool full of turds, and you look down at one turd and say 'That turd p#$(%^s me off!, I'm gonna do something about that turd!'"

(I could have resisted, but didn't want to)

Hi;

I would like to defrag the following file
"C:\Windows\System32\CatRoot2\tmp.edb" with Sysinternals Contig v1.55.

I extracted the file Contig.exe from the Sysinternals Suite to my Desktop,
but when I click on it the Command Prompt screen briefly appears and then is
gone.

How can I use this application to defrag the file listed above? Please
give me specific instructions.

Thanks,

ColTom2

On Monday, March 16, 2009 3:44 PM Pegasus [MVP] wrote:

You need to perform the first debugging step yourself, by making all
messages visible:
1. Click Start
2. Type the three letters cmd
3. Click OK
4. Type the command you wish to execute, e.g.
desktop\contig.exe
5. Read the message(s) you see.

 

[Jack Knoff]

Egghead HoopleHead.

I have to agree with Louis. 2 days to get an answer about how to defrag a
1mb file, that cannot possibly be defragmented, because it is not
accessible when created, but is not created if you turn off the auto
updates. I guess you could go so far as to dual boot your system, just to
find that, because you didn't boot into your Windows OS, the file was never
created, hence cannot be defragmented. Sounds like the 'ol catch 22
scenario. I believe you are right, we all learned something in this
process (with the apparent exception of ColTom2). I know that I learned
that there is no limit to the length of time a person will waste to solve a
problem that is

a) So insignificant that it warrants no thought
b) Is not really possible since the file is either there and not
accessible, or not there so irrelevent.

This reminds me of a line from the 1988 movie Off Limits by the Fred Ward
character. "You guys are floating in a rowboat in a cesspool full of
turds, and you look down at one turd and say 'That turd p#$(%^s me off!,
I'm gonna do something about that turd!'"

(I could have resisted, but didn't want to)