WinXp Pro-Chkdsk always runs-Changed Drive letter
Hiyas!
Well, urm, what can I say?
Sheer incompetence on my part, that's what!
The problem :
ChkDsk Always runs on boot for drive D:, an ickle 30gb Maxtor drive, without ever finding a thing wrong.
The scenario leading up to my problem :
Me!
Or rather... I wanted to update my mobo and hard disks, leaving my OS intact.
So I put my new bigger HD in the machine, used Norton Ghost 9 to make a shadow copy of my C: drive to the E: drive, increasing my capacity from 40Gb to about 120Gb. I remember selecting all the "Make bootable" kind of options too. I think I missed the "Volume drive letter" option or something... (Ooops)
When it had nearly finished the old Deathstar HD (I use Seagate these days!) started making funny noises, I backed it up just in time I think.
Anyway, took old small HD out, put new HD in where old one was, set primary on it using the jumpers.
Booted into windows, logged in with my username... Thing froze! This I beleive (in hindsight) was caused by the drive letter still being E, and the profile for my login was in the registry as residing in C.
Used repair thingy for WinXP, computer then allowed me to log in with my profile. SHOCK HORROR! I had no drive C! The evil incarnate had booted off a different drive letter--- E: !!
I looked up the problem online, and found a registry key to alter the mounted E drive, to make it the C drive again.
Profiles and settings seemed to follow it on reboot too! Yay! didn't need to run the repair thingy.
My system is fine now... I repeat... it's -fine-, the registry doesn't appear to be corrupt in a low level big way. The only corruption in it is probably wrong keys set somewhere, during my arsing around.
But, a legacy of all that is now that my D drive (which swopped and changed it's drive letter during the update too), keeps getting chkdsk'd all the time! This didn't happen before the upgrade.
I've used CHKNTFS /x d: to disable the check disk of D, but I want to know WHY the dirty bit's not getting cleared.
I'm posting this because I -know- how to restore old copies of the registry and things, but I don't want to. I want to know what's going on, and to fix -it- in particular, and specifically.
I hate the "Format and install" mentality these days, it's a puzzle, meant to be explored and worked through, out of love, not because a quota of phonecalls needs to be met. :) oh yeah!
Thanks in advance!
Well, urm, what can I say?
Sheer incompetence on my part, that's what!
The problem :
ChkDsk Always runs on boot for drive D:, an ickle 30gb Maxtor drive, without ever finding a thing wrong.
The scenario leading up to my problem :
Me!
Or rather... I wanted to update my mobo and hard disks, leaving my OS intact.
So I put my new bigger HD in the machine, used Norton Ghost 9 to make a shadow copy of my C: drive to the E: drive, increasing my capacity from 40Gb to about 120Gb. I remember selecting all the "Make bootable" kind of options too. I think I missed the "Volume drive letter" option or something... (Ooops)
When it had nearly finished the old Deathstar HD (I use Seagate these days!) started making funny noises, I backed it up just in time I think.
Anyway, took old small HD out, put new HD in where old one was, set primary on it using the jumpers.
Booted into windows, logged in with my username... Thing froze! This I beleive (in hindsight) was caused by the drive letter still being E, and the profile for my login was in the registry as residing in C.
Used repair thingy for WinXP, computer then allowed me to log in with my profile. SHOCK HORROR! I had no drive C! The evil incarnate had booted off a different drive letter--- E: !!
I looked up the problem online, and found a registry key to alter the mounted E drive, to make it the C drive again.
Profiles and settings seemed to follow it on reboot too! Yay! didn't need to run the repair thingy.
My system is fine now... I repeat... it's -fine-, the registry doesn't appear to be corrupt in a low level big way. The only corruption in it is probably wrong keys set somewhere, during my arsing around.
But, a legacy of all that is now that my D drive (which swopped and changed it's drive letter during the update too), keeps getting chkdsk'd all the time! This didn't happen before the upgrade.
I've used CHKNTFS /x d: to disable the check disk of D, but I want to know WHY the dirty bit's not getting cleared.
I'm posting this because I -know- how to restore old copies of the registry and things, but I don't want to. I want to know what's going on, and to fix -it- in particular, and specifically.
I hate the "Format and install" mentality these days, it's a puzzle, meant to be explored and worked through, out of love, not because a quota of phonecalls needs to be met. :) oh yeah!
Thanks in advance!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Not yet, going shops before it closes! back in 30!
np.. :)
ASKER
stevenlewis's fist one was a good link, but the MS idea was restore the complete registry again.
The second link for http://www.regxplor.com/tweak_current.html, found me the registry key was set to : autocheck autochk /k:D *
Which I expeted as it's the one I've blocked chkdsk from running.
I looked through http://support.microsoft.com/kb/q218461/, but nothing apparently the cause caught my eye, again the only reg key I have for chkdsk is the autocheck autochk /k:D * one.
http://support.microsoft.com/?kbid=831426, seems to give fairly the same info.
But, SheharyaarSaahil, I'm going for food inna mo, I'll try using a disk check utility after that.
If there's something ChkDsk -can't- fix, and that's why it keeps restarting on reboot, would it show something damaged when it was doing the scan, or would it report that nothign was found?
Just that it never finds anything on the scan, that's all.
Laters!
The second link for http://www.regxplor.com/tweak_current.html, found me the registry key was set to : autocheck autochk /k:D *
Which I expeted as it's the one I've blocked chkdsk from running.
I looked through http://support.microsoft.com/kb/q218461/, but nothing apparently the cause caught my eye, again the only reg key I have for chkdsk is the autocheck autochk /k:D * one.
http://support.microsoft.com/?kbid=831426, seems to give fairly the same info.
But, SheharyaarSaahil, I'm going for food inna mo, I'll try using a disk check utility after that.
If there's something ChkDsk -can't- fix, and that's why it keeps restarting on reboot, would it show something damaged when it was doing the scan, or would it report that nothign was found?
Just that it never finds anything on the scan, that's all.
Laters!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Just trying it now. I'm doing it from inside Windows with the volume dismounted, and it's verifying indexes, (stage 2 of 5), wooo! 40% completed...
Laters!
Laters!
ASKER
D:\>chkdsk /f /r
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is Sarah.
CHKDSK is verifying files (stage 1 of 5)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 5)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 5)...
Security descriptor verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Windows has checked the file system and found no problems.
20008925 KB total disk space.
17528676 KB in 71886 files.
28136 KB in 8955 indexes.
0 KB in bad sectors.
180473 KB in use by the system.
65536 KB occupied by the log file.
2271640 KB available on disk.
4096 bytes in each allocation unit.
5002231 total allocation units on disk.
567910 allocation units available on disk.
D:\>
Okay, lastly, moving on to the specific Maxtor scan program. =) (I still preffere Seagate)
The type of the file system is NTFS.
Cannot lock current drive.
Chkdsk cannot run because the volume is in use by another
process. Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted. All opened handles to this volume are now invalid.
Volume label is Sarah.
CHKDSK is verifying files (stage 1 of 5)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 5)...
Index verification completed.
CHKDSK is verifying security descriptors (stage 3 of 5)...
Security descriptor verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Windows has checked the file system and found no problems.
20008925 KB total disk space.
17528676 KB in 71886 files.
28136 KB in 8955 indexes.
0 KB in bad sectors.
180473 KB in use by the system.
65536 KB occupied by the log file.
2271640 KB available on disk.
4096 bytes in each allocation unit.
5002231 total allocation units on disk.
567910 allocation units available on disk.
D:\>
Okay, lastly, moving on to the specific Maxtor scan program. =) (I still preffere Seagate)
well Chkdsk reports are looking cool...... hmmmm tricky one! :-?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, I will!
It was [autocheck autochk *] originally, and I myself changed it to [autocheck autochk /k:D *] by using the command line chkntfs command : [chkntfs /x d:], just to stop it runing. Before this it ran every time. But I'll try again, just to see.
I've also just ran the PowerMax utility from Maxtor, and the drive passed all the tests, including the full scan one. (I've been having a shower in the meantime).
I'm thinking somewhere along the line, Windows isn't resetting the Dirty flag for the drive because the drive letter changed, and some of the Registry still points to the old drive location, hence when the scan was successful, Windows may possibly be trying to change the Dirty bit of the wrong drive?
MS's idea of replacing the registry is a bit of a cop out. It's like a callcentre telling you to reformat your HD because your Digicam won't work. It would be nice if they'd just give some information about the Dirty flag, and where that kind of ifo in the registry is.
It was [autocheck autochk *] originally, and I myself changed it to [autocheck autochk /k:D *] by using the command line chkntfs command : [chkntfs /x d:], just to stop it runing. Before this it ran every time. But I'll try again, just to see.
I've also just ran the PowerMax utility from Maxtor, and the drive passed all the tests, including the full scan one. (I've been having a shower in the meantime).
I'm thinking somewhere along the line, Windows isn't resetting the Dirty flag for the drive because the drive letter changed, and some of the Registry still points to the old drive location, hence when the scan was successful, Windows may possibly be trying to change the Dirty bit of the wrong drive?
MS's idea of replacing the registry is a bit of a cop out. It's like a callcentre telling you to reformat your HD because your Digicam won't work. It would be nice if they'd just give some information about the Dirty flag, and where that kind of ifo in the registry is.
ASKER
Bedtime first (12:15am gmt), will try tonight.
hmmmm just onfirming.... did you use this article to change your E: drive back to C: ??
http://support.microsoft.com/support/kb/articles/Q223/1/88.ASP
http://support.microsoft.com/support/kb/articles/Q223/1/88.ASP
ASKER
Yes! That's the very same page!
Er........-worries-
Er........-worries-
when your drive got changed to E:
your present D: must have changed to C: and your cd drive must have changed to D:
then you changed E: to C:
your second drive becamed D:
and now you cd drive is E:
am i taking it rightly ??
your present D: must have changed to C: and your cd drive must have changed to D:
then you changed E: to C:
your second drive becamed D:
and now you cd drive is E:
am i taking it rightly ??
ASKER
This is a screen shot of regedit showing the current state of things, (and also a screenshot of why I hate the reformat kind of option)
http://untamed.dyndns.org/registry.gif
http://untamed.dyndns.org/registry.gif
page not found
did you try the regedit as suggested?
did you try the regedit as suggested?
im getting Network Timeout! :)
ASKER
stevenlewis , where you refering to the one at http://support.microsoft.com/support/kb/articles/Q223/1/88.ASP that SheharyaarSaahil suggested? If so yes, if not, sos, I'm lost!
That screenshot again... http://www.untamed.co.uk/registry.gif
That screenshot again... http://www.untamed.co.uk/registry.gif
hmmm its working now...... but you are having a key there, starting with #{....
the first key in the right pane...... i have checked my xp systems here.... no one has this kind of key..... all are those \\??volume and DosDevices keys! :-?
the first key in the right pane...... i have checked my xp systems here.... no one has this kind of key..... all are those \\??volume and DosDevices keys! :-?
No,
>>It was [autocheck autochk *] originally
change it back to what it was originally
>>It was [autocheck autochk *] originally
change it back to what it was originally
ASKER
stevenlewis... okee, will change it now for the reboot tomorrow. After this last burger here, I'm going to go bed and read for a bit. =) (Now Windows manuals either)
SheharyaarSaahil; I've just asked my partner to check her system, (which has nearly a clean install of XP, which is on the same network as me), and she's got 13 of those keys with the question marks in them. Apart from being on the same network and having MSI Mobo's and Maxtor HD's, thats about where the similarities end. We've never swopped reg-keys that I know of. :)
Maybe the keys are for removeable USB drives/Digicams and things perhaps? One key per USB port? I don't know. But the keys arn't unique to my system, and so don't appear to be the cause of my chkdsk symptom that I can see.
I'm almost winding down for the night, I'll be back on tomorrow around the same time to update on my progress.
I was guessing it wasn't going to be a stock-answer solution, hence the points. Still, I'll share them out for the time you both spent workign through it with me. =)
SheharyaarSaahil; I've just asked my partner to check her system, (which has nearly a clean install of XP, which is on the same network as me), and she's got 13 of those keys with the question marks in them. Apart from being on the same network and having MSI Mobo's and Maxtor HD's, thats about where the similarities end. We've never swopped reg-keys that I know of. :)
Maybe the keys are for removeable USB drives/Digicams and things perhaps? One key per USB port? I don't know. But the keys arn't unique to my system, and so don't appear to be the cause of my chkdsk symptom that I can see.
I'm almost winding down for the night, I'll be back on tomorrow around the same time to update on my progress.
I was guessing it wasn't going to be a stock-answer solution, hence the points. Still, I'll share them out for the time you both spent workign through it with me. =)
Let's get this baby right, and then we'll worry about the points
Have a good nite
Have a good nite
noooo i was talking about that very first key...... this one >> #{bcdd2d4f-6739-11d9-afbf-
??
??
i myself have all those questions marks and DosDevices entries, but i cannot find that #{..... } type key in any system :-?
ASKER
I did a registry search after selecting keys/values/data for [bcdd2d4f-6739-11d9-afbf-0
Hmmm.
Hmmm.
ASKER
I've been running the individual downloads for the XP updates, and came across the following error on the only file that didnt work (Q841356_xpe_sp2_x86_enu.e
QFE Installer - Error
Cannot connect to the database - please check the database.
Setup cannot continue.
[Exit]
I checked the log file generation tick box, and it was nice and helpful and just put the same error text in the error log! Gah!? What database? Who programed the error messages? Let me force them to watch daytime TV!
Anyway, I even tried NTFilMon from sysinternals, and I couldn't see any failed database read requests from the hard disk. I've also deleted that apparently rogue reg key =)
I'm thinking some DB thing is corrupt or missing, but what?
QFE Installer - Error
Cannot connect to the database - please check the database.
Setup cannot continue.
[Exit]
I checked the log file generation tick box, and it was nice and helpful and just put the same error text in the error log! Gah!? What database? Who programed the error messages? Let me force them to watch daytime TV!
Anyway, I even tried NTFilMon from sysinternals, and I couldn't see any failed database read requests from the hard disk. I've also deleted that apparently rogue reg key =)
I'm thinking some DB thing is corrupt or missing, but what?
ASKER
Ok, some info hot from WindowsUpdate.Log......
This is from the detecting new versions page up to the page with the 2 links for express/custom install:
2005-01-22 00:37:32-0000 2084 3a8 Trying to make out of proc datastore active
2005-01-22 00:37:32-0000 2084 3a8 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:32-0000 2084 3a8 Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:32-0000 2084 3a8 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:32-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:33-0000 1828 c98 Trying to make out of proc datastore active
2005-01-22 00:37:33-0000 1828 c98 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:33-0000 1828 c98 Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:33-0000 1828 c98 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:33-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:34-0000 3292 f6c Trying to make out of proc datastore active
2005-01-22 00:37:34-0000 3292 f6c Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:34-0000 3292 f6c Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:34-0000 3292 f6c Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:34-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:34-0000 1068 9c4 WU client fails CClientCallRecorder::Enume
2005-01-22 00:37:34-0000 1636 a64 ISusInternal::EnumerateSer
2005-01-22 00:37:38-0000 536 ec8 Trying to make out of proc datastore active
2005-01-22 00:37:38-0000 536 ec8 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:38-0000 536 ec8 Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:38-0000 536 ec8 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:38-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:39-0000 1216 828 Trying to make out of proc datastore active
2005-01-22 00:37:39-0000 1216 828 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:39-0000 1216 828 Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:39-0000 1216 828 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:39-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:39-0000 932 9b8 Trying to make out of proc datastore active
2005-01-22 00:37:39-0000 932 9b8 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:39-0000 932 9b8 Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:39-0000 932 9b8 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:39-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:39-0000 1068 9c4 WU client fails CClientCallRecorder::Enume
2005-01-22 00:37:39-0000 1636 a64 ISusInternal::EnumerateSer
2005-01-22 00:37:46-0000 1636 a64 Checking for different Redirector at: http://download.windowsupdate.com/msdownload/update/v5/redir/wuredir.cab
2005-01-22 00:37:46-0000 1636 a64 WinInet: Server file is not newer. Skipping download.
2005-01-22 00:37:46-0000 1636 a64 Successfully refreshed Redirector cab.
2005-01-22 00:37:46-0000 1636 a64 WinInet: Server file is not newer. Skipping download.
2005-01-22 00:37:47-0000 1636 a64 WinInet: Download speed is 58920013 bytes/sec
2005-01-22 00:37:47-0000 1636 a64 WinInet: Successfully downloaded http://v5.windowsupdate.microsoft.com/SelfUpdate/AU/x86/XP/en/wusetup.cab to file C:\WINDOWS\SoftwareDistrib
2005-01-22 00:37:47-0000 1636 a64 Loading inf file C:\WINDOWS\SoftwareDistrib
2005-01-22 00:37:47-0000 1636 a64 Section name: cdm: Index: 0
2005-01-22 00:37:47-0000 1636 a64 Section name: iuengine: Index: 1
2005-01-22 00:37:47-0000 1636 a64 Section name: wuapi: Index: 2
2005-01-22 00:37:47-0000 1636 a64 Section name: wuauclt: Index: 3
2005-01-22 00:37:47-0000 1636 a64 Section name: wuauclt1: Index: 4
2005-01-22 00:37:47-0000 1636 a64 Section name: wuaucpl: Index: 5
2005-01-22 00:37:47-0000 1636 a64 Section name: wuaueng_WebSetup: Index: 6
2005-01-22 00:37:47-0000 1636 a64 Section name: wuaueng1: Index: 7
2005-01-22 00:37:47-0000 1636 a64 Section name: wuauserv_WebSetup: Index: 8
2005-01-22 00:37:47-0000 1636 a64 Section name: wucltui: Index: 9
2005-01-22 00:37:47-0000 1636 a64 Section name: wups: Index: 10
2005-01-22 00:37:47-0000 1636 a64 Section name: winhttp: Index: 11
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\cdm.dl
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\cdm.dl
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\iuengi
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\iuengi
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuapi.
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuapi.
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuaucl
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuaucl
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuaucl
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuaucl
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuaucp
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuaucp
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuauen
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuauen
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuauen
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuauen
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wucltu
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wucltu
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wups.d
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wups.d
2005-01-22 00:38:19-0000 1068 6f8 AU received event of 1
2005-01-22 00:38:19-0000 1068 6f8 Setting next AU detection timeout to 2005-01-22 00:38:19
2005-01-22 00:38:19-0000 3944 ab8 Trying to make out of proc datastore active
2005-01-22 00:38:19-0000 3944 ab8 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:19-0000 3944 ab8 Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:19-0000 3944 ab8 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:19-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:20-0000 3912 9fc Trying to make out of proc datastore active
2005-01-22 00:38:20-0000 3912 9fc Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:20-0000 3912 9fc Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:20-0000 3912 9fc Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:20-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:20-0000 2348 9bc Trying to make out of proc datastore active
2005-01-22 00:38:20-0000 2348 9bc Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:20-0000 2348 9bc Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:20-0000 2348 9bc Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:21-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:21-0000 3904 674 Trying to make out of proc datastore active
2005-01-22 00:38:21-0000 3904 674 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:21-0000 3904 674 Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:21-0000 3904 674 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:21-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:22-0000 3160 f20 Trying to make out of proc datastore active
2005-01-22 00:38:22-0000 3160 f20 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:22-0000 3160 f20 Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:22-0000 3160 f20 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:22-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:22-0000 1272 988 Trying to make out of proc datastore active
2005-01-22 00:38:22-0000 1272 988 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:22-0000 1272 988 Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:22-0000 1272 988 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:22-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:22-0000 1068 6f8 Failed to get session from datastore: 80248011
2005-01-22 00:38:22-0000 1068 6f8 Failed to Unserialize from data store: 80248011
2005-01-22 00:38:22-0000 1068 6f8 AU Restart required....
This is from the detecting new versions page up to the page with the 2 links for express/custom install:
2005-01-22 00:37:32-0000 2084 3a8 Trying to make out of proc datastore active
2005-01-22 00:37:32-0000 2084 3a8 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:32-0000 2084 3a8 Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:32-0000 2084 3a8 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:32-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:33-0000 1828 c98 Trying to make out of proc datastore active
2005-01-22 00:37:33-0000 1828 c98 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:33-0000 1828 c98 Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:33-0000 1828 c98 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:33-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:34-0000 3292 f6c Trying to make out of proc datastore active
2005-01-22 00:37:34-0000 3292 f6c Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:34-0000 3292 f6c Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:34-0000 3292 f6c Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:34-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:34-0000 1068 9c4 WU client fails CClientCallRecorder::Enume
2005-01-22 00:37:34-0000 1636 a64 ISusInternal::EnumerateSer
2005-01-22 00:37:38-0000 536 ec8 Trying to make out of proc datastore active
2005-01-22 00:37:38-0000 536 ec8 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:38-0000 536 ec8 Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:38-0000 536 ec8 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:38-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:39-0000 1216 828 Trying to make out of proc datastore active
2005-01-22 00:37:39-0000 1216 828 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:39-0000 1216 828 Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:39-0000 1216 828 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:39-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:39-0000 932 9b8 Trying to make out of proc datastore active
2005-01-22 00:37:39-0000 932 9b8 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:37:39-0000 932 9b8 Out of proc exiting with error 0xc80004b6
2005-01-22 00:37:39-0000 932 9b8 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:37:39-0000 1068 9c4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:37:39-0000 1068 9c4 WU client fails CClientCallRecorder::Enume
2005-01-22 00:37:39-0000 1636 a64 ISusInternal::EnumerateSer
2005-01-22 00:37:46-0000 1636 a64 Checking for different Redirector at: http://download.windowsupdate.com/msdownload/update/v5/redir/wuredir.cab
2005-01-22 00:37:46-0000 1636 a64 WinInet: Server file is not newer. Skipping download.
2005-01-22 00:37:46-0000 1636 a64 Successfully refreshed Redirector cab.
2005-01-22 00:37:46-0000 1636 a64 WinInet: Server file is not newer. Skipping download.
2005-01-22 00:37:47-0000 1636 a64 WinInet: Download speed is 58920013 bytes/sec
2005-01-22 00:37:47-0000 1636 a64 WinInet: Successfully downloaded http://v5.windowsupdate.microsoft.com/SelfUpdate/AU/x86/XP/en/wusetup.cab to file C:\WINDOWS\SoftwareDistrib
2005-01-22 00:37:47-0000 1636 a64 Loading inf file C:\WINDOWS\SoftwareDistrib
2005-01-22 00:37:47-0000 1636 a64 Section name: cdm: Index: 0
2005-01-22 00:37:47-0000 1636 a64 Section name: iuengine: Index: 1
2005-01-22 00:37:47-0000 1636 a64 Section name: wuapi: Index: 2
2005-01-22 00:37:47-0000 1636 a64 Section name: wuauclt: Index: 3
2005-01-22 00:37:47-0000 1636 a64 Section name: wuauclt1: Index: 4
2005-01-22 00:37:47-0000 1636 a64 Section name: wuaucpl: Index: 5
2005-01-22 00:37:47-0000 1636 a64 Section name: wuaueng_WebSetup: Index: 6
2005-01-22 00:37:47-0000 1636 a64 Section name: wuaueng1: Index: 7
2005-01-22 00:37:47-0000 1636 a64 Section name: wuauserv_WebSetup: Index: 8
2005-01-22 00:37:47-0000 1636 a64 Section name: wucltui: Index: 9
2005-01-22 00:37:47-0000 1636 a64 Section name: wups: Index: 10
2005-01-22 00:37:47-0000 1636 a64 Section name: winhttp: Index: 11
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\cdm.dl
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\cdm.dl
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\iuengi
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\iuengi
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuapi.
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuapi.
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuaucl
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuaucl
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuaucl
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuaucl
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuaucp
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuaucp
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuauen
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuauen
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wuauen
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wuauen
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wucltu
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wucltu
2005-01-22 00:37:47-0000 1636 a64 Required Version for binary C:\WINDOWS\system32\wups.d
2005-01-22 00:37:47-0000 1636 a64 Binary: C:\WINDOWS\system32\wups.d
2005-01-22 00:38:19-0000 1068 6f8 AU received event of 1
2005-01-22 00:38:19-0000 1068 6f8 Setting next AU detection timeout to 2005-01-22 00:38:19
2005-01-22 00:38:19-0000 3944 ab8 Trying to make out of proc datastore active
2005-01-22 00:38:19-0000 3944 ab8 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:19-0000 3944 ab8 Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:19-0000 3944 ab8 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:19-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:20-0000 3912 9fc Trying to make out of proc datastore active
2005-01-22 00:38:20-0000 3912 9fc Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:20-0000 3912 9fc Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:20-0000 3912 9fc Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:20-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:20-0000 2348 9bc Trying to make out of proc datastore active
2005-01-22 00:38:20-0000 2348 9bc Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:20-0000 2348 9bc Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:20-0000 2348 9bc Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:21-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:21-0000 3904 674 Trying to make out of proc datastore active
2005-01-22 00:38:21-0000 3904 674 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:21-0000 3904 674 Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:21-0000 3904 674 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:21-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:22-0000 3160 f20 Trying to make out of proc datastore active
2005-01-22 00:38:22-0000 3160 f20 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:22-0000 3160 f20 Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:22-0000 3160 f20 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:22-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:22-0000 1272 988 Trying to make out of proc datastore active
2005-01-22 00:38:22-0000 1272 988 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:38:22-0000 1272 988 Out of proc exiting with error 0xc80004b6
2005-01-22 00:38:22-0000 1272 988 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:38:22-0000 1068 6f8 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:38:22-0000 1068 6f8 Failed to get session from datastore: 80248011
2005-01-22 00:38:22-0000 1068 6f8 Failed to Unserialize from data store: 80248011
2005-01-22 00:38:22-0000 1068 6f8 AU Restart required....
ASKER
Followed by the top link "express"...
2005-01-22 00:40:51-0000 1068 9c4 WU client succeeds CClientCallRecorder::Begin
2005-01-22 00:40:51-0000 1068 2a4 WU client executing call {04D17098-D3FC-403C-B826-F
2005-01-22 00:40:52-0000 1764 5ac Trying to make out of proc datastore active
2005-01-22 00:40:52-0000 1764 5ac Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:52-0000 1764 5ac Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:52-0000 1764 5ac Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:52-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:53-0000 3908 c50 Trying to make out of proc datastore active
2005-01-22 00:40:53-0000 3908 c50 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:53-0000 3908 c50 Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:53-0000 3908 c50 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:53-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:54-0000 2652 f08 Trying to make out of proc datastore active
2005-01-22 00:40:54-0000 2652 f08 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:54-0000 2652 f08 Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:54-0000 2652 f08 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:54-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:54-0000 3024 86c Trying to make out of proc datastore active
2005-01-22 00:40:54-0000 3024 86c Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:54-0000 3024 86c Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:54-0000 3024 86c Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:54-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:55-0000 2948 940 Trying to make out of proc datastore active
2005-01-22 00:40:55-0000 2948 940 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:55-0000 2948 940 Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:55-0000 2948 940 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:55-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:56-0000 2956 e70 Trying to make out of proc datastore active
2005-01-22 00:40:56-0000 2956 e70 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:56-0000 2956 e70 Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:56-0000 2956 e70 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:56-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:56-0000 1068 2a4 WU client failed Searching for update with error 0x80248011
2005-01-22 00:40:56-0000 1068 2a4 WU client calls back to search call WindowsUpdate with code Call failed and error 0x80248011
2005-01-22 00:40:56-0000 1068 2a4 WU client completed and deleted call {04D17098-D3FC-403C-B826-F
2005-01-22 00:40:56-0000 1636 a64 Operation completed due to earlier error. (hr=80248011)
2005-01-22 00:40:56-0000 1636 a64 Unable to complete asynchronous search successfully. (hr=80248011)
2005-01-22 00:40:59-0000 1068 2a4 REPORT EVENT: {9977E5B4-55C9-45AA-B628-4
2005-01-22 00:40:51-0000 1068 9c4 WU client succeeds CClientCallRecorder::Begin
2005-01-22 00:40:51-0000 1068 2a4 WU client executing call {04D17098-D3FC-403C-B826-F
2005-01-22 00:40:52-0000 1764 5ac Trying to make out of proc datastore active
2005-01-22 00:40:52-0000 1764 5ac Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:52-0000 1764 5ac Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:52-0000 1764 5ac Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:52-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:53-0000 3908 c50 Trying to make out of proc datastore active
2005-01-22 00:40:53-0000 3908 c50 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:53-0000 3908 c50 Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:53-0000 3908 c50 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:53-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:54-0000 2652 f08 Trying to make out of proc datastore active
2005-01-22 00:40:54-0000 2652 f08 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:54-0000 2652 f08 Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:54-0000 2652 f08 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:54-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:54-0000 3024 86c Trying to make out of proc datastore active
2005-01-22 00:40:54-0000 3024 86c Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:54-0000 3024 86c Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:54-0000 3024 86c Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:54-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:55-0000 2948 940 Trying to make out of proc datastore active
2005-01-22 00:40:55-0000 2948 940 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:55-0000 2948 940 Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:55-0000 2948 940 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:55-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:56-0000 2956 e70 Trying to make out of proc datastore active
2005-01-22 00:40:56-0000 2956 e70 Failed to initialize datastore: 0xc80004b6
2005-01-22 00:40:56-0000 2956 e70 Out of proc exiting with error 0xc80004b6
2005-01-22 00:40:56-0000 2956 e70 Error: 0xc80004b6. wuauclt datastore: failed to spawn COM server
2005-01-22 00:40:56-0000 1068 2a4 DS: Out of proc datastore process exited with error 0xc80004b6 before signalling ready event.
2005-01-22 00:40:56-0000 1068 2a4 WU client failed Searching for update with error 0x80248011
2005-01-22 00:40:56-0000 1068 2a4 WU client calls back to search call WindowsUpdate with code Call failed and error 0x80248011
2005-01-22 00:40:56-0000 1068 2a4 WU client completed and deleted call {04D17098-D3FC-403C-B826-F
2005-01-22 00:40:56-0000 1636 a64 Operation completed due to earlier error. (hr=80248011)
2005-01-22 00:40:56-0000 1636 a64 Unable to complete asynchronous search successfully. (hr=80248011)
2005-01-22 00:40:59-0000 1068 2a4 REPORT EVENT: {9977E5B4-55C9-45AA-B628-4
ASKER
I went here, after searching google for a bit of the COM error.....
http://www.alegsa.com.ar/Visitas/i39/0xc80004c0%20error%20in%20windowsupdate%20log.php
It mentions....
C:\WINDOWS\SoftwareDistrib
So I have a look.....
In a subfolder [Logs], i have a file [edb.chk] (CHKDSK!!!), that contains references to [E:\WINDOWS\SoftwareDistri
Can I fix it? Or use my partners? Or if I delete it, would it make a new one?
http://www.alegsa.com.ar/Visitas/i39/0xc80004c0%20error%20in%20windowsupdate%20log.php
It mentions....
C:\WINDOWS\SoftwareDistrib
So I have a look.....
In a subfolder [Logs], i have a file [edb.chk] (CHKDSK!!!), that contains references to [E:\WINDOWS\SoftwareDistri
Can I fix it? Or use my partners? Or if I delete it, would it make a new one?
Chkdsk Runs Each Time That You Start Your Computer