Damaged System files or… (XP Home SP1)

Topic

New Reply

Here are some questions about CHKDSK, Recovery Console, SFC, DirectX. I know, maybe I should put several threads but my problem includes all of them.

Which are the differences between running CHKDSK from Windows XP (cmd.exe) and running from Recovery Console? (Or even running from GUI and wait during reboot.)

What is the difference between SFC /scannow and SFC /scanonce? If, for instance, /scanonce is done during boot process, how does this affect the result?

What is the result of boot alternative “Last good”?

Since it’s not possible to uninstall DirectX, and that’s fine if everything works, is it possible to re-install a previous version (9.0) over 9.0b? Well, after what happened I might have to do this. (Windows certainly can…).

At first, I found that my post was maybe too long. So this is the short version with only questions and no description of my problem, but for the moment it seems to work. It seems though that DirectX files have been changed to original 8.1 (XP SP1).

Argus

Reply | Quote

Replies

1) Running chkdsk from the Recovery console is widely written to be superior, and there are commands that are only available from there. Personal experience I was able to clean up a dirty bit problem that just wouldn’t clear up running it from the command prompt or gui. The best one switch to run is chkdsk /r (implies f and r–cyberspeak for includes).

2) As far as the gui vs. the command prompt, the gui is just as effective, but the command prompt offers a number of switches that the gui does not. The gui is ambiguously setup and thousands of people get confused over those boxes.

3) sfc /scanonce performs a full scan the next time you boot the PC

sfc /scannow performs a full scan now—-generally used when you are running it the first time.

/scanboot sets up SFC so that it will run every time you boot. Rarely used because it’s a pain somewhere if I could just get the anatomy down and remember the location. The only context I could think of would be a lab setup for some reason that was testing repairing discs.

/quiet Allows SFC to replace files without asking permission to run.

/cancel or /revert cancels the scanboot set up.

4) Last known Good Configuration is one of the alternatives when you hit F8 and is one of the options on the so-called Windows Advanced Options Menu. The Win XP Professional Resource Kit Team considers it the first choice for an emergency recovery. Many don’t. I don’t because it doesn’t work often, and has limitations if it does. I favor Safe Mode with a Commands Prompt so you can run a system restore command or other commands. It Starts the XP system using registry information and drivers that Windows saved at the last shutdown. Any changes made since the last successful startup are lost. Use this option only if a part of the system has been configured incorrectly. LNG has no ability to repair or replace corrupt or missing files and drivers. LNG is meant primarily to use when there is a hardware or hardware/software interface problem–like a problematic driver (the most common cause for Win XP crashes–MS says about 65%). It could be a program trashing registry data. LNG’s two big disadvantage is that you lose any configuration changes made since the last start and it doesn’t work a huge percent of the time.[/i]
It cannot fix problems involving control sets–passwords or policy changes.

5) You can try. Microsoft advises two possibilities: 1) You reinstall Direct X 9b again and this should take care of a problem if the problem is in fact your first 9b installation. A system restore point is now set on Direct X installations, so you can system restore and then opt but remember there is a huge vulnerability so 9b has the patch built in and the others 9, 9a and earlier need the patch for protection. Security Update for Direct X August 20, 2003
See also: Direct X FAQ’s

I’m going to put links with extensive explanations I did in prior posts on another post. To get the best quality help now, post your problem in detail with any error messages and don’t forget to look at Event Viewer Systems/Application for any error data there.

hth,

SMBP

Reply | Quote

SMBP

Many thanks for your quick answer and all the links to earlier threads. The system is now stable I think; I have not done any re-install of for instance DirectX. I am aware about the security problem with DirectX, sorry that I didn

Reply | Quote

Argus–

First and foremost, if you read the links, you have been resourceful in your efforts but you could have avoided all of this material and frustration by using one of the best darn tools on this planet when you’re sitting at a Windows computer with problems–and this seems to have been probably driver induced not system file checker induced for sure.. I love SFC–doubt you need it for this. I think you’re right to run Chkdsk /r always from the RC, but system restore from safe mode would have trumped all that you did I believe.[/i]

Read the links on using System restore after booting F8 into Safe Mode with a Command Prompt because all the detailed steps are there.[/i] That move can be the oxygen you need to CPR out of a lot of windows crashes–there are others and boot recovery discs, but it’s my personal favorite.

You can chase down these error codes in the KB, google or something like it, or the XP Error Code sites that abound on the web–the zero is an SFC error code–they’re prolific and the KB was in the context of installing SP1. I spent time and nothing came up.

Choosing Normal just might work, and if it does well, so much the better, you just came out smelling like a relative rose. And Windows not a pretty site can be fixed a heckuva lot more easily than no Windows at all that you can never reach with ntloader and ntdetect and the boys.

I don’t know why SFC would ask you for a server CD unless you h ave some connection with a server somehow. It should ask you for your XP Home CD–that’s what you have that’s what I’d use.

Absolutely the command prompt switches are more prolific/varied. It ain’t no “seems like.” It’s expressly on purpose. That’s by developer design. The RC is limited by design with 13 dos commands, and a number of its own–and commands from other OS’s just won’t work. As I stated in the extensive posts I linked you to the RC is deliberately limited as compared with dos. You don’t have access to every file and folder–but you do have access to strategic ones most likely to be needed to access, change, and restore your system from a fresh copy found in the root directory or the Windows installation folder, either installed or on the CD. Sometimes it works from the CD and you’re installed version won’t, or vice-versa. You can’t use text editing tools; change the local Administrator Pass Word; System Restore (but you can from Safe Mode and that’s why Safe Mode can be superior and is higher on the list of emergency Windows CPR equipment to deploy in emergent situations). Documents and Settings files are unavailable, and you cannot write to supported removable media. You can disable services and drivers and this can help troubleshooting particularly when you can’t get to Windows.

Glad you’re fixed hopefully and I appreciate the detailed info. If I can or didn’t answer any questions please let me know–I’ll be happy to try.

SMBP

Reply | Quote

SMBP

Again thanks for a quick reply. I have so far read many of the links.
After my last answer it happened again, not exactly same. Was reading some help files, then suddenly a reboot. This time it just stopped at boot menu and froze. No message at all. I booted and chosed RC and ran chkdsk C: /r. It found some errors and fixed them. I booted back to Normal. Something is not working…

Regarding RC, I do understand what can be done with some of the commands and the limitations to access only root, systemroot and CD etc. It was this understanding that the tool might be useful that made me install it on drive as second option to CD some months ago. I appreciate your work to inform about RC.

As to SFC, something certainly went wrong. I mean, in Event viewer there are a log showing how it tries to restore then another log event that says failed to restore. OK, good nothing happened. But then I find out that DirectX files are ver. 8.1 or at least dxdiag is. AIDA32 reports DirectX version 9.0, 4.09.00.0902 that’s “b” I suppose. Or maybe it was just the dxdiag that went back to old 8.1? But then there are some errors in DirectPlay service providers.

Also, I sometimes use Adaptec/Roxio DirectCD. Now it seems like the program doesn’t work properly. It doesn’t recognize my previous formated CD in CD-RW drive. Now it works as if I had put the CD in CD/DVD-reader, properties does not show empty space. I have not tried to copy anything to the CD though. First the system must be working properly.

Yes, the possibility to use System restore from Safe mode with Command prompt could be very useful in the future, thanks for that link. Now days theres no problem running win programs from command prompt, so the trick is just to remember the file “rstrui.exe”. This KB304449 about running Sys. restore from command prompt is certainly worth mentioning to new XP users who are confused about Adv. boot menu opt. It does not help me for the moment as I deactivated System restore.

I did some initial search for mentioned error codes. Yes, 0x800b0100 was mentioned in KB 263566 installing Win 2000 SP1, “No signature present in the subject.”

My DirectX was, as described, a patched 9.0. Now, I’m not so sure of the status of my DirectX so I guess I have to download the complete 9.0b as you mentioned. I do not know what to do next but search for some info. about error codes. Well, maybe it’s time for autumn cleaning and do a clean install, I have all the patches so far on CD media.

All this could also be related to the fact that the machine now is 12 months and three days… My old win95 machine ran over 5 years before I did reinstall the OS.

Regards,
Argus

Reply | Quote

(Edited by Argus on 08-Sep-03 21:07. Checked with dxdiag once more.)

Today I was looking at Windows Update… and now it tells me that I need some patches that I know is already there (811493, 823980, 816093, 814078, 817287). Sigh, I guess it’s my turn to get those stupid replies from WU that many people already have. I was also looking at DirectX site, as described earlier there might be some problems with my installation. WU did not say anything about DirectX.

Well so I ran dxdiag, and guess what today it says version 902 (9.0b), weird… I certainly did a reboot yesterday, if thats going to change anything.
Oops, wrong. I was to fast. Dxdiag still reports 4.09.00.0902 (8.1). So earlier post is still correct, status of DirectX IS not sure, as today WU does not say anything but dxdiag report 8.1. Of course since I applied the 9.0b patch earlier that mark still exist in registry.

SMBP, or anyone else, if I run chkdsk /r from RC and it says found some errors and fixed them; is it possible to run chkdsk /r again and get no errors? What I mean, of course I can run chkdsk repeatedly, but after it found some errors and fixed them I have never run it directly once more to check. The reason: today I checked and it found some new errors, is this never ending?

Regards,
Argus

Reply | Quote

Argus–

” I guess it’s my turn to get those stupid replies from WU that many people already have.”

If you continue to use Win Update, the consistent thing about it is that you will continue to get those stupid replies from WU that many people already have, and that we are seeing in the lounge today at the rate of one every five posts as Win Update problems. The best way to troubleshoot Windows Update is to stop, cease, and desist from using it period. Instead start using the Microsoft Security Site–a much more reliable site by the same company that brought you Win Update and its stupid replies.

Here are extensive links with equal time to both the Microsoft Security Site and its Update Newsletter and Windows Update. 99% of the updates are security patches. So what do you do to get the others? I have a really complicated formula for this. Ready? You get Office updates from the Office site, IE from the IE site, Direct X from Direct X site, OE from IE, and Win Media from well, I know I can do this if I try– Win Media. Even I can remember this. And guess what happens to Win Update’s unending confusion and draining time waste–it’s gone the heck out of your life!

See references for links:

Links to Microsoft Security Site–the Hassle Free Way to Keep Up With Updates for Other MS Programs

Links to Help With Windows Update and Microsoft Security Site and the Security Newsletter–the Best Way to get Updates

Also see XP Updating Guide

hth, SMBP

Reply | Quote

OK, one answer to my post mentioning WU, could be:
Your files in program filesWindowsUpdate may have been damaged and thus you get strange results from Windows Update, nothing to worry about, there are other ways to check that your patches are still intact.

I have read your posts about Microsoft Security Site, and I’ve been there before, even though I don’t read Bulletins just for the fun of it. I don’t have a fast Internet connection, and I also want to save the patches for future use, so I normally d/l from the Catalog. I, and many people, find WU as an easy way to check if there are any new patches, but I have learned now that one can not trust it.

Regards,

Argus

Reply | Quote

Argus (on both posts)– Please turn system restore on if it isn’t–on all drives but data drives.

What’s up with your memory stop error? Gone now that you repositioned the memory stick?

As to Win Update vs. the Security site, choose what you like. Storage is not a problem. Microsoft has all the patches stored on their security site with links to the servers.

“File protection messed with my DirectX files”

I sincerely don’t believe that SFC screwed up anything. It might not replace a damaged file on occasion–that has been documented and MS has a KB on just that, but it doesn’t damage the merchandise. Your DxDiag might have a corrupt registry file or files. SFC didn’t do it whatever else did. And if you can get it to run, it might fix it.

Again Argus–Roxio what–What version of CD burner are you using with Win XP?

As to version of Direct X–I’m going with the Registry as the final arbiter. The Dxdiag.exe tool is installed when Direct X is installed–I think what registers is accurate. So your registry says you have Direct X 9( and that means in fact you have the latest Dxdiag.exe Tool. Sometimes install progress bars can falsely indicate something got in, and if it isn’t in the registry it’s not in. The registry says you have 9( whatever the gui distortions. We have seen this several times –when the registry and gui disagree as to version–the registry is right every time.

Most common false indicator is Help About IE with patches that I’ve seen.[/b] You may have to live with the gui saying the wrong thing, but so what– as you really have the latest with the best functionality.

hth,

SMBP

Reply | Quote

I have turned System Restore on, on system drive. Did that when the rebooting stoped.

Yes, no memory stop error (I suppose you refer to my other thread, sorry was trying to post an answer to that as well, but had problem with connection.) I have only seen that error once before this time, some months ago, but that time I didn’t find any source, what might caused, and it didn’t come back until some days ago.

I don’t understand what: Storage, is not a problem. Well I just said that I like to download patches to have them for future use.

Ah, well I suppose it can not go any worse. I will try and run SFC.

OK, I don’t have any more problem with Roxio. As I described, when you use DirectCD, it uses CDUDFRW file system when cd-rw disk is in burner, but if I move the cd-rw disk to my CD/DVD-drive the file system is UDFRDR, and now it can be read in any CD-drive that support UDF, My, one time , problem was that it behaved as it was in a CD-drive and not in the CD-RW. If you want to know version is:
Roxio Easy CD Creator 5, 5.1 (60), and Direct CD 5.10(115).

Yepp, Well it IS fine that registry say version 9.0b, and I am not worried that the patch isn’t there. Because I know it is there. But it is annoying that “dxdiag.exe” in system32 got changed, and that some other files was changed or damaged so that when I run the new dxdiag it finds errors.

Argus

Reply | Quote

I have turned System Restore on, on system drive. Did that when the rebooting stoped.

Yes, no memory stop error (I suppose you refer to my other thread, sorry was trying to post an answer to that as well, but had problem with connection.) I have only seen that error once before this time, some months ago, but that time I didn’t find any source, what might caused, and it didn’t come back until some days ago.

I don’t understand what: Storage, is not a problem. Well I just said that I like to download patches to have them for future use.

Ah, well I suppose it can not go any worse. I will try and run SFC.

OK, I don’t have any more problem with Roxio. As I described, when you use DirectCD, it uses CDUDFRW file system when cd-rw disk is in burner, but if I move the cd-rw disk to my CD/DVD-drive the file system is UDFRDR, and now it can be read in any CD-drive that support UDF, My, one time , problem was that it behaved as it was in a CD-drive and not in the CD-RW. If you want to know version is:
Roxio Easy CD Creator 5, 5.1 (60), and Direct CD 5.10(115).

Yepp, Well it IS fine that registry say version 9.0b, and I am not worried that the patch isn’t there. Because I know it is there. But it is annoying that “dxdiag.exe” in system32 got changed, and that some other files was changed or damaged so that when I run the new dxdiag it finds errors.

Argus

Reply | Quote

OK, one answer to my post mentioning WU, could be:
Your files in program filesWindowsUpdate may have been damaged and thus you get strange results from Windows Update, nothing to worry about, there are other ways to check that your patches are still intact.

I have read your posts about Microsoft Security Site, and I’ve been there before, even though I don’t read Bulletins just for the fun of it. I don’t have a fast Internet connection, and I also want to save the patches for future use, so I normally d/l from the Catalog. I, and many people, find WU as an easy way to check if there are any new patches, but I have learned now that one can not trust it.

Regards,

Argus

Reply | Quote

Argus–

” I guess it’s my turn to get those stupid replies from WU that many people already have.”

If you continue to use Win Update, the consistent thing about it is that you will continue to get those stupid replies from WU that many people already have, and that we are seeing in the lounge today at the rate of one every five posts as Win Update problems. The best way to troubleshoot Windows Update is to stop, cease, and desist from using it period. Instead start using the Microsoft Security Site–a much more reliable site by the same company that brought you Win Update and its stupid replies.

Here are extensive links with equal time to both the Microsoft Security Site and its Update Newsletter and Windows Update. 99% of the updates are security patches. So what do you do to get the others? I have a really complicated formula for this. Ready? You get Office updates from the Office site, IE from the IE site, Direct X from Direct X site, OE from IE, and Win Media from well, I know I can do this if I try– Win Media. Even I can remember this. And guess what happens to Win Update’s unending confusion and draining time waste–it’s gone the heck out of your life!

See references for links:

Links to Microsoft Security Site–the Hassle Free Way to Keep Up With Updates for Other MS Programs

Links to Help With Windows Update and Microsoft Security Site and the Security Newsletter–the Best Way to get Updates

Also see XP Updating Guide

hth, SMBP

Reply | Quote

(Edited by Argus on 08-Sep-03 21:07. Checked with dxdiag once more.)

Today I was looking at Windows Update… and now it tells me that I need some patches that I know is already there (811493, 823980, 816093, 814078, 817287). Sigh, I guess it’s my turn to get those stupid replies from WU that many people already have. I was also looking at DirectX site, as described earlier there might be some problems with my installation. WU did not say anything about DirectX.

Well so I ran dxdiag, and guess what today it says version 902 (9.0b), weird… I certainly did a reboot yesterday, if thats going to change anything.
Oops, wrong. I was to fast. Dxdiag still reports 4.09.00.0902 (8.1). So earlier post is still correct, status of DirectX IS not sure, as today WU does not say anything but dxdiag report 8.1. Of course since I applied the 9.0b patch earlier that mark still exist in registry.

SMBP, or anyone else, if I run chkdsk /r from RC and it says found some errors and fixed them; is it possible to run chkdsk /r again and get no errors? What I mean, of course I can run chkdsk repeatedly, but after it found some errors and fixed them I have never run it directly once more to check. The reason: today I checked and it found some new errors, is this never ending?

Regards,
Argus

Reply | Quote

Argus–

Win Update is covered in the next post–you have 6 or so problems thrown into one thread.

Please!!!!! start separate threads on unrelated problems–you’ll get better resolution. Throwing 6 problems into one thread is confusing and people will pick out one problem and answer it only. SFC , Direct X version, Recovery Console, and Roxio are different problems.

1) SFC–run it again–put in the CD–be ready to hit retry several times.

2) Roxio–to relate it to XP please give the version. Meanwhile uninstall and reinstall. I have Nero 5.5plus, Nero 6.0–the new one and Roxio 6.0 and Roxio is has more instability problems but to each his own. And give the Roxio problem its own thread please.

3) There is no “trick” to remembering the System restore command. You can simply email the KB to yourself and you’ll have it wherever on earth you are. You can also write the command down on a business card and carry it, and save it to your hard drive on every machine, tablet and PDA you have. I know it didn’t help you for the moment but it sure as heck is useful when you don’t turn off System Restore and you won’t in the future. I also told you how to save space with it.

4) If you run chkdsk /r from the recovery console and keep getting errrors, I suspect a hardware problem, or a problem with damage to your hard drive that the command is not going to fix.

The Registry Keys That Verify Versions of Direct X[/u]

5) There are several registry keys that will verify the Direct X Version, and they are all listed on this thread below and here they are:

Hive: HKEY_LOCAL_MACHINE
Key: SOFTWAREMicrosoftWindows NTCurrentVersionHotfix

HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdates

There will be a subkey for each hotfix that has been applied
__________________________________________________________________________

Additional registry keys to verify it’s in since it’s a Direct X patch/update:

Confirm that the following registry key is installed:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftDirectXVersion

and that the value is 4.09.00.0902:

To verify that the DirectX 9.0a security patch is installed on your computer, confirm that the following registry key is present and that it has a value of 1:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdatesDirectXdx819696IsInstalled

Also you’ll find this reference helpful:

Critical Direct X Updates and Review on Running Chkdsk/r from Recovery Console

hth,

SMBP

Reply | Quote

Sometimes it’s hard to know if problems are unrelated. But I agree that the questions about the tools (chkdsk, RC and sfc) should have been in another thread.

1) OK, for the moment, given how the problems has developed, I consider to do a clean install. If/how/when I do that is not a result only from having trouble with SFC or DirectX individually. I do not urge people to not use sfc, I just mentioned that I have had some trouble with it and how File protection messed with my DirectX files. I think SFC, as you said, can be a great tool, but somehow it didn’t work as planned some days ago.

2) Regarding Roxio, at that time it didn’t work. Some days later, and after the rebooting started, it’s now working. My intention with mentioning problem with Roxio was not to ask for help regarding that specific problem. I just added the info. to the thread to give a broader picture of the situation.

4) OK. I don’t know. If software can cause file errors etc. that can be repaired with chkdsk, then the next time your “bad software” causes an error you will get a new error/fix with chkdsk, and no specific hardware problem is involved, possible?

5) Yes, I know the places in registry. In my case, before the trouble with sfc and after, still the same:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftDirectXVersion
Value is: 4.09.00.0902.
Regarding the patch, same before trouble and after;
HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdatesDirectXdx819696IsInstalled
is present and has the value of 1.

That all seem so fine, so good. And of course I could stop there and rest assured I have the very latest DirectX and also the patched version. But my trouble is that during the process of running sfc something happened. As I mentioned earlier “dxdiag” (the tool – not DirectX files) in system32 changed back to the old version.

If I run dxdiag from Run, or my Quick launch toolbar, both will run the version that is placed in System32, thats OK, but please take a look at the screenshot. It is the old dxdiag, and it reports 8.1 AND 4.09.00.0902)! The second tab DirectX files reports no problems as I have mentioned before.

But if I do a search on the disk for the new dxdiag I find it in WindowsRegisteredPackages (and System32dllcache if I uncheck Hide protected system files). If I run the new dxdiag it reports 9.0 and 4.09.0000.0902, see second screenshot. The new dxdiag second tab report “some problems with DirectX files, try reinstall”. But then I can not reinstall the because it find that it’s already there.

Regards,

Argus

Reply | Quote

Sometimes it’s hard to know if problems are unrelated. But I agree that the questions about the tools (chkdsk, RC and sfc) should have been in another thread.

1) OK, for the moment, given how the problems has developed, I consider to do a clean install. If/how/when I do that is not a result only from having trouble with SFC or DirectX individually. I do not urge people to not use sfc, I just mentioned that I have had some trouble with it and how File protection messed with my DirectX files. I think SFC, as you said, can be a great tool, but somehow it didn’t work as planned some days ago.

2) Regarding Roxio, at that time it didn’t work. Some days later, and after the rebooting started, it’s now working. My intention with mentioning problem with Roxio was not to ask for help regarding that specific problem. I just added the info. to the thread to give a broader picture of the situation.

4) OK. I don’t know. If software can cause file errors etc. that can be repaired with chkdsk, then the next time your “bad software” causes an error you will get a new error/fix with chkdsk, and no specific hardware problem is involved, possible?

5) Yes, I know the places in registry. In my case, before the trouble with sfc and after, still the same:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftDirectXVersion
Value is: 4.09.00.0902.
Regarding the patch, same before trouble and after;
HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdatesDirectXdx819696IsInstalled
is present and has the value of 1.

That all seem so fine, so good. And of course I could stop there and rest assured I have the very latest DirectX and also the patched version. But my trouble is that during the process of running sfc something happened. As I mentioned earlier “dxdiag” (the tool – not DirectX files) in system32 changed back to the old version.

If I run dxdiag from Run, or my Quick launch toolbar, both will run the version that is placed in System32, thats OK, but please take a look at the screenshot. It is the old dxdiag, and it reports 8.1 AND 4.09.00.0902)! The second tab DirectX files reports no problems as I have mentioned before.

But if I do a search on the disk for the new dxdiag I find it in WindowsRegisteredPackages (and System32dllcache if I uncheck Hide protected system files). If I run the new dxdiag it reports 9.0 and 4.09.0000.0902, see second screenshot. The new dxdiag second tab report “some problems with DirectX files, try reinstall”. But then I can not reinstall the because it find that it’s already there.

Regards,

Argus

Reply | Quote

Argus–

Win Update is covered in the next post–you have 6 or so problems thrown into one thread.

Please!!!!! start separate threads on unrelated problems–you’ll get better resolution. Throwing 6 problems into one thread is confusing and people will pick out one problem and answer it only. SFC , Direct X version, Recovery Console, and Roxio are different problems.

1) SFC–run it again–put in the CD–be ready to hit retry several times.

2) Roxio–to relate it to XP please give the version. Meanwhile uninstall and reinstall. I have Nero 5.5plus, Nero 6.0–the new one and Roxio 6.0 and Roxio is has more instability problems but to each his own. And give the Roxio problem its own thread please.

3) There is no “trick” to remembering the System restore command. You can simply email the KB to yourself and you’ll have it wherever on earth you are. You can also write the command down on a business card and carry it, and save it to your hard drive on every machine, tablet and PDA you have. I know it didn’t help you for the moment but it sure as heck is useful when you don’t turn off System Restore and you won’t in the future. I also told you how to save space with it.

4) If you run chkdsk /r from the recovery console and keep getting errrors, I suspect a hardware problem, or a problem with damage to your hard drive that the command is not going to fix.

The Registry Keys That Verify Versions of Direct X[/u]

5) There are several registry keys that will verify the Direct X Version, and they are all listed on this thread below and here they are:

Hive: HKEY_LOCAL_MACHINE
Key: SOFTWAREMicrosoftWindows NTCurrentVersionHotfix

HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdates

There will be a subkey for each hotfix that has been applied
__________________________________________________________________________

Additional registry keys to verify it’s in since it’s a Direct X patch/update:

Confirm that the following registry key is installed:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftDirectXVersion

and that the value is 4.09.00.0902:

To verify that the DirectX 9.0a security patch is installed on your computer, confirm that the following registry key is present and that it has a value of 1:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftUpdatesDirectXdx819696IsInstalled

Also you’ll find this reference helpful:

Critical Direct X Updates and Review on Running Chkdsk/r from Recovery Console

hth,

SMBP

Reply | Quote

SMBP

Again thanks for a quick reply. I have so far read many of the links.
After my last answer it happened again, not exactly same. Was reading some help files, then suddenly a reboot. This time it just stopped at boot menu and froze. No message at all. I booted and chosed RC and ran chkdsk C: /r. It found some errors and fixed them. I booted back to Normal. Something is not working…

Regarding RC, I do understand what can be done with some of the commands and the limitations to access only root, systemroot and CD etc. It was this understanding that the tool might be useful that made me install it on drive as second option to CD some months ago. I appreciate your work to inform about RC.

As to SFC, something certainly went wrong. I mean, in Event viewer there are a log showing how it tries to restore then another log event that says failed to restore. OK, good nothing happened. But then I find out that DirectX files are ver. 8.1 or at least dxdiag is. AIDA32 reports DirectX version 9.0, 4.09.00.0902 that’s “b” I suppose. Or maybe it was just the dxdiag that went back to old 8.1? But then there are some errors in DirectPlay service providers.

Also, I sometimes use Adaptec/Roxio DirectCD. Now it seems like the program doesn’t work properly. It doesn’t recognize my previous formated CD in CD-RW drive. Now it works as if I had put the CD in CD/DVD-reader, properties does not show empty space. I have not tried to copy anything to the CD though. First the system must be working properly.

Yes, the possibility to use System restore from Safe mode with Command prompt could be very useful in the future, thanks for that link. Now days theres no problem running win programs from command prompt, so the trick is just to remember the file “rstrui.exe”. This KB304449 about running Sys. restore from command prompt is certainly worth mentioning to new XP users who are confused about Adv. boot menu opt. It does not help me for the moment as I deactivated System restore.

I did some initial search for mentioned error codes. Yes, 0x800b0100 was mentioned in KB 263566 installing Win 2000 SP1, “No signature present in the subject.”

My DirectX was, as described, a patched 9.0. Now, I’m not so sure of the status of my DirectX so I guess I have to download the complete 9.0b as you mentioned. I do not know what to do next but search for some info. about error codes. Well, maybe it’s time for autumn cleaning and do a clean install, I have all the patches so far on CD media.

All this could also be related to the fact that the machine now is 12 months and three days… My old win95 machine ran over 5 years before I did reinstall the OS.

Regards,
Argus

Reply | Quote

Argus–

First and foremost, if you read the links, you have been resourceful in your efforts but you could have avoided all of this material and frustration by using one of the best darn tools on this planet when you’re sitting at a Windows computer with problems–and this seems to have been probably driver induced not system file checker induced for sure.. I love SFC–doubt you need it for this. I think you’re right to run Chkdsk /r always from the RC, but system restore from safe mode would have trumped all that you did I believe.[/i]

Read the links on using System restore after booting F8 into Safe Mode with a Command Prompt because all the detailed steps are there.[/i] That move can be the oxygen you need to CPR out of a lot of windows crashes–there are others and boot recovery discs, but it’s my personal favorite.

You can chase down these error codes in the KB, google or something like it, or the XP Error Code sites that abound on the web–the zero is an SFC error code–they’re prolific and the KB was in the context of installing SP1. I spent time and nothing came up.

Choosing Normal just might work, and if it does well, so much the better, you just came out smelling like a relative rose. And Windows not a pretty site can be fixed a heckuva lot more easily than no Windows at all that you can never reach with ntloader and ntdetect and the boys.

I don’t know why SFC would ask you for a server CD unless you h ave some connection with a server somehow. It should ask you for your XP Home CD–that’s what you have that’s what I’d use.

Absolutely the command prompt switches are more prolific/varied. It ain’t no “seems like.” It’s expressly on purpose. That’s by developer design. The RC is limited by design with 13 dos commands, and a number of its own–and commands from other OS’s just won’t work. As I stated in the extensive posts I linked you to the RC is deliberately limited as compared with dos. You don’t have access to every file and folder–but you do have access to strategic ones most likely to be needed to access, change, and restore your system from a fresh copy found in the root directory or the Windows installation folder, either installed or on the CD. Sometimes it works from the CD and you’re installed version won’t, or vice-versa. You can’t use text editing tools; change the local Administrator Pass Word; System Restore (but you can from Safe Mode and that’s why Safe Mode can be superior and is higher on the list of emergency Windows CPR equipment to deploy in emergent situations). Documents and Settings files are unavailable, and you cannot write to supported removable media. You can disable services and drivers and this can help troubleshooting particularly when you can’t get to Windows.

Glad you’re fixed hopefully and I appreciate the detailed info. If I can or didn’t answer any questions please let me know–I’ll be happy to try.

SMBP

Reply | Quote

SMBP

Many thanks for your quick answer and all the links to earlier threads. The system is now stable I think; I have not done any re-install of for instance DirectX. I am aware about the security problem with DirectX, sorry that I didn

Reply | Quote

1) Running chkdsk from the Recovery console is widely written to be superior, and there are commands that are only available from there. Personal experience I was able to clean up a dirty bit problem that just wouldn’t clear up running it from the command prompt or gui. The best one switch to run is chkdsk /r (implies f and r–cyberspeak for includes).

2) As far as the gui vs. the command prompt, the gui is just as effective, but the command prompt offers a number of switches that the gui does not. The gui is ambiguously setup and thousands of people get confused over those boxes.

3) sfc /scanonce performs a full scan the next time you boot the PC

sfc /scannow performs a full scan now—-generally used when you are running it the first time.

/scanboot sets up SFC so that it will run every time you boot. Rarely used because it’s a pain somewhere if I could just get the anatomy down and remember the location. The only context I could think of would be a lab setup for some reason that was testing repairing discs.

/quiet Allows SFC to replace files without asking permission to run.

/cancel or /revert cancels the scanboot set up.

4) Last known Good Configuration is one of the alternatives when you hit F8 and is one of the options on the so-called Windows Advanced Options Menu. The Win XP Professional Resource Kit Team considers it the first choice for an emergency recovery. Many don’t. I don’t because it doesn’t work often, and has limitations if it does. I favor Safe Mode with a Commands Prompt so you can run a system restore command or other commands. It Starts the XP system using registry information and drivers that Windows saved at the last shutdown. Any changes made since the last successful startup are lost. Use this option only if a part of the system has been configured incorrectly. LNG has no ability to repair or replace corrupt or missing files and drivers. LNG is meant primarily to use when there is a hardware or hardware/software interface problem–like a problematic driver (the most common cause for Win XP crashes–MS says about 65%). It could be a program trashing registry data. LNG’s two big disadvantage is that you lose any configuration changes made since the last start and it doesn’t work a huge percent of the time.[/i]
It cannot fix problems involving control sets–passwords or policy changes.

5) You can try. Microsoft advises two possibilities: 1) You reinstall Direct X 9b again and this should take care of a problem if the problem is in fact your first 9b installation. A system restore point is now set on Direct X installations, so you can system restore and then opt but remember there is a huge vulnerability so 9b has the patch built in and the others 9, 9a and earlier need the patch for protection. Security Update for Direct X August 20, 2003
See also: Direct X FAQ’s

I’m going to put links with extensive explanations I did in prior posts on another post. To get the best quality help now, post your problem in detail with any error messages and don’t forget to look at Event Viewer Systems/Application for any error data there.

hth,

SMBP

Reply | Quote

Argus–

Here are links to posts on threads where I have explained the items on the F8/Win. Adv. Options menu in detail. Scroll because there are explanations on more than one post in some threads, and a good deal of material is covered in these links that you asked about in considerable detail:

Win Adv Options Menu, System Restore, Rec Console, Last Known Good on several posts here 284723, 284948

Post 283049, 283092, 283101 Recovery Console, RC Password, and Chkdsk from the Recovery Console

Post 288633 F8 The Win Adv Option Choices, System Restore from Safe Mode’s Command Prompt and the Recovery Console; Last Known Good Several Llinks in Post

Post 289709, 289769 Recovery Console, Chkdsk How To Use

Direct X Home User FAQ’s

Direct X News and Reviews from Microsoft

Thread on Installing Direct X, Difference Among Direct X Versions, the Security Update, and Registry Verification of Installation

hth,

SMBP

Reply | Quote

Argus–

Here are links to posts on threads where I have explained the items on the F8/Win. Adv. Options menu in detail. Scroll because there are explanations on more than one post in some threads, and a good deal of material is covered in these links that you asked about in considerable detail:

Win Adv Options Menu, System Restore, Rec Console, Last Known Good on several posts here 284723, 284948

Post 283049, 283092, 283101 Recovery Console, RC Password, and Chkdsk from the Recovery Console

Post 288633 F8 The Win Adv Option Choices, System Restore from Safe Mode’s Command Prompt and the Recovery Console; Last Known Good Several Llinks in Post

Post 289709, 289769 Recovery Console, Chkdsk How To Use

Direct X Home User FAQ’s

Direct X News and Reviews from Microsoft

Thread on Installing Direct X, Difference Among Direct X Versions, the Security Update, and Registry Verification of Installation

hth,

SMBP

Reply | Quote