Does file "WindowsUpdate.log" grow without bounds?

  • Thread starter Thread starter Bert Hyman
  • Start date Start date
B

Bert Hyman

The file <windir>\WindowsUpdate.log on my system contains entries back to
September and is currently about 500KB in size, and contains little of
interest. I can't delete it from the command line since it's open by some
process.

Does it have an upper size limit? What process is responsible for
maintaining this file?
 
In "Wesley Vogel"
Hint... Windows Update.

Every time http://v5.windowsupdate.microsoft.com/ is visited and
scanning is run. Whether by you or by Automatic Updates.

Automatic Updates has it open. wuauclt.exe or wuauclt1.exe is the
process.
Click to expand...

But does the file grow without bound, or does the update process keep the
file trimmed to a "reasonable" size?

Otherwise, I'll have to stop the process and clean it up myself from time
to time.

[Aside: Your newsreading/posting software appears to be misbehaving, since
it put the text of my message and part of your response after the signature
separator (sigdash).]
 
Bert,

I do not use Automatic Updates. I do delete the contents of my log from
time to time. Because of that I do not know how large the log can grow to.

[shrug]
My Newsreader: Microsoft Outlook Express 6.00.2800.1437

Yours: Xnews/06.08.25

Interesting reading here >>>
CNET > Downloads > Windows > Internet > Newsreaders > Xnews > User Opinions
http://www.download.com/3302-2164_4-10144167.html


--
Hope this helps. Let us know.
Wes

In
Bert Hyman said:
In "Wesley Vogel"
Hint... Windows Update.

Every time http://v5.windowsupdate.microsoft.com/ is visited and
scanning is run. Whether by you or by Automatic Updates.

Automatic Updates has it open. wuauclt.exe or wuauclt1.exe is the
process.
Click to expand...

But does the file grow without bound, or does the update process keep
the file trimmed to a "reasonable" size?

Otherwise, I'll have to stop the process and clean it up myself from
time to time.

[Aside: Your newsreading/posting software appears to be misbehaving,
since it put the text of my message and part of your response after
the signature separator (sigdash).]
Click to expand...
 
Back
Top