G
Guest
I'm getting an error message saying that Windows Updater has to shut down and
wanting to know if I want to tell MS about the problem. I sent it a few times
but stopped letting it. I used EVENTVWR to get more info and here are the
results:
Category100)
Event ID: 1000
Faulting application wuauclt.exe, version 5.4.3790.2182, faulting module
wuauclt.exe, version 5.4.3790.2182, fault address 0x0000c0b5.
Then the next event is:
Category: (100)
Event ID: 1005
Windows cannot access the file C:\WINDOWS\WindowsUpdate.log for one of the
following reasons: there is a problem with the network connection, the disk
that the file is stored on, or the storage drivers installed on this
computer; or the disk is missing. Windows closed the program
WindowsUpdate.log because of this error.
Program: WindowsUpdate.log
File: C:\WINDOWS\WindowsUpdate.log
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that
corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that
there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify
that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click
Start, click Run, type CMD, and then click OK. At the command prompt, type
CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the
disk might be damaged. If it is a hard disk, contact your administrator or
computer hardware vendor for further assistance.
Additional Data
Error value: C000009C
Disk type: 3
I tried to access c:WINDOWS\WindowsUpdate.log with notepad and got a message
that the file was being used by another application.
I then tried using an application called Filealyzer and got a similar
message. Clicking the Hex dump option, I can see entries made today so I
don't think the problem is the drive. Filealyzer won't let me copy and paste
the hex dump but it does produce the following report:
********************************************************************
FileAlyzer © 2003 Patrick M. Kolla. All Rights Reserved.
********************************************************************
File: C:\WINDOWS\WindowsUpdate.log
Date: 2/11/2005 11:14:17 AM
***** General ******************************************************
Location: C:\WINDOWS\
Size: 708267
Version:
CRC-32: ?
MD5: ?
Read only: No
Hidden: No
System file: No
Directory: No
Archive: No
Symbolic link: No
Time stamp: Friday, February 11, 2005 8:24:04 AM
Creation: ?
Last access: ?
Last write: ?
Not much info there but I am able to see that the file is being changed by
the automatic updater. I turned off automatic updates and it appeared in the
log. I turned Automatic updates back on and that also appeared in the log
then about a minute later, the error message appeared again.
This has been going on for a couple of days so I've been checking for
updates manually and the first day, I had like 6 critical updates that I
downloaded and installed. Any suggestions on how to solve this puzzle would
be appreciated.
wanting to know if I want to tell MS about the problem. I sent it a few times
but stopped letting it. I used EVENTVWR to get more info and here are the
results:
Category100)
Event ID: 1000
Faulting application wuauclt.exe, version 5.4.3790.2182, faulting module
wuauclt.exe, version 5.4.3790.2182, fault address 0x0000c0b5.
Then the next event is:
Category: (100)
Event ID: 1005
Windows cannot access the file C:\WINDOWS\WindowsUpdate.log for one of the
following reasons: there is a problem with the network connection, the disk
that the file is stored on, or the storage drivers installed on this
computer; or the disk is missing. Windows closed the program
WindowsUpdate.log because of this error.
Program: WindowsUpdate.log
File: C:\WINDOWS\WindowsUpdate.log
The error value is listed in the Additional Data section.
User Action
1. Open the file again. This situation might be a temporary problem that
corrects itself when the program runs again.
2. If the file still cannot be accessed and
- It is on the network, your network administrator should verify that
there is not a problem with the network and that the server can be contacted.
- It is on a removable disk, for example, a floppy disk or CD-ROM, verify
that the disk is fully inserted into the computer.
3. Check and repair the file system by running CHKDSK. To run CHKDSK, click
Start, click Run, type CMD, and then click OK. At the command prompt, type
CHKDSK /F, and then press ENTER.
4. If the problem persists, restore the file from a backup copy.
5. Determine whether other files on the same disk can be opened. If not, the
disk might be damaged. If it is a hard disk, contact your administrator or
computer hardware vendor for further assistance.
Additional Data
Error value: C000009C
Disk type: 3
I tried to access c:WINDOWS\WindowsUpdate.log with notepad and got a message
that the file was being used by another application.
I then tried using an application called Filealyzer and got a similar
message. Clicking the Hex dump option, I can see entries made today so I
don't think the problem is the drive. Filealyzer won't let me copy and paste
the hex dump but it does produce the following report:
********************************************************************
FileAlyzer © 2003 Patrick M. Kolla. All Rights Reserved.
********************************************************************
File: C:\WINDOWS\WindowsUpdate.log
Date: 2/11/2005 11:14:17 AM
***** General ******************************************************
Location: C:\WINDOWS\
Size: 708267
Version:
CRC-32: ?
MD5: ?
Read only: No
Hidden: No
System file: No
Directory: No
Archive: No
Symbolic link: No
Time stamp: Friday, February 11, 2005 8:24:04 AM
Creation: ?
Last access: ?
Last write: ?
Not much info there but I am able to see that the file is being changed by
the automatic updater. I turned off automatic updates and it appeared in the
log. I turned Automatic updates back on and that also appeared in the log
then about a minute later, the error message appeared again.
This has been going on for a couple of days so I've been checking for
updates manually and the first day, I had like 6 critical updates that I
downloaded and installed. Any suggestions on how to solve this puzzle would
be appreciated.