Question on replacing corrupt files

I read the tutorial on how to access files from your Vista Install DVD. I'm a little confused, what is the difference between Windows AIK and windows WAIK? or is it the same thing?
Also is AIK the same as a Windows PE (physical environment)? I bought Macrium reflect and to use it (because Vista didn't come with a PE) I had to install this PE thing. Macrium had to pay for a license from Microsoft to include it in their software. Anyway, now that I've confused you too, if I have that (PE) already do I need to download and install the AIK?
Can the folder I create to place the install.wim be on my external Hard Drive?
I have already looked at the CBS.Logs. I have 5 corrupt files on the last (sfc) scan, but if I go back further there are a few more. Were those fixed by sfc/r or do I have to do those too. I read about the deleting the contents of the log files and running it again and use only the ones that come up this time. Is that the route to go?

Hello!

Sorry about the late reply. Things got a bit busy. I am sure you know the feeling!

I am a bit confused by some of your question. I shall answer what I understand, and then you can re-ask anything that I have missed. Thanks!

WAIK stands for Windows Automated Installation Kit. We usually say WAIK, although Windows AIK is not wrong. Windows WAIK is, because it repeats twice the work Windows. There is only one tool.

To replace a corrupt file, due to old media, copying from an installation CD/DVD will work, but is not the best. I can usually find you a better replacement.

Don't delete CBS.log, because that deletes the evidence for me.

If you would just like me to help you fix your corruptions, that is fine. It is also fine if you want me to teach you how, providing you would describe yourself as very advanced at computing, and the inner workings of the computer from the software point of view.

To help you, first, I need to see the logs.

Please run steps 1, 2A, 3 (about 15 minutes), 4, 5, and then Step 1 from the top yellow box, but only follow this last one if Integrity Violations were found. Please upload the new sfcdetails.txt from your Desktop. System Files - SFC Command

Thanks!

Richard

P.S. Any files no longer reported by SFC should now be fixed, but I can confirm all of this from the log file if you upload them without deleting CBS.log.

I'm send you 2 files to look at. The zip file is a scan I ran on the 15th. I then rescanned on the 17th. While some of the errors were consistent I found some that I didn't understand. Same number of errors, different files? One,(second scan) the source file was corrupt, didn't see that on the first report.
I have a fairly good knowledge of the software, advanced,well.... Let me put it this way, I know where the registry is and how to access it. As to changing values, I haven't ever done that. Actually I take that back; a Microsoft Tech walked me through removing some files in the AutoPlay. My AutoPlay does not display on the desktop. To get my System Restore to work I have to disable Nortan Anti-virus, almost to the point of uninstalling it.
The files were opened with windows notepad. By the way when I tried to get into the files through command prompt I I couldn't. I went in through the long path, when I got to logs it still denied me access to open the logs, even though I have administrative rights. I had to copy the folders out to the desktop and go from there. On the second file I only included the errors, not the whole log. If you need a whole log I can run it again. It only takes about 20 minutes to do and if I can get this thing straightened out it's time well spent.

Hello!

I have looked at your logs, and having the whole log does help, but first I would like to see all of them together. Can you please create the logs following STEP ONE from this tutorial: http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html

and upload the new sfcdetails.txt from your Desktop.

Will talk more tomorrow.

Thanks!

Sorry about that, Before when I tried the "findstr" in the command prompt line nothing happened except it opened a second line on the command prompt. Nothing showed up on the desktop. Possibly when I copied it I didn't get all of the end of it.
Anyway here it is, hope this helps better than what I sent you before. Now that I have it I'm going to look it over and compare it to what the others look like.

messed up said:

Sorry about that, Before when I tried the "findstr" in the command prompt line nothing happened except it opened a second line on the command prompt. Nothing showed up on the desktop. Possibly when I copied it I didn't get all of the end of it.
Anyway here it is, hope this helps better than what I sent you before. Now that I have it I'm going to look it over and compare it to what the others look like.

Click to expand...

No problems! Thanks for that! Have pieced the log together, and had a look.

It is the strangest log I have ever seen. It just seems to choose on the spur of the moment which files should be corrupt. Here are the reports from each scan, deliminated by a double return:

network.h1s
NlsData0039.dll


msiexec.exe.mui
msiexec.exe


RGBBalance.wmv
SS2.dvr-m
msiexec.exe.mui
msiexec.exe
NlsLexicons0007.dll
Chess.exe.mui
unimdm.tsp


playing.H1S
msiexec.exe.mui
msiexec.exe


PositioningOS16x9.wmv
msiexec.exe.mui
msiexec.exe
NlsData004a.dll


I need to think about this for a little while. I don't really know what to say. What are the only patterns:

Nls*.dll
msiexec.exe.mui
msiexec.exe
+ odd files

May I please ask you a few questions? How old is this computer (approx. in years) The only thing that I can think of on the spur of the moment is a dying hard disk. Let me come back to you. If you would like, you can see how to test a hard disk, although they are not completely definitive: HD Diagnostic

Thanks!

Sorry it took so long to get back to you. I've been doing scans.
First off I already have the WD diagnostic CD for boot diagnostics. I ran it about 3 weeks ago and it said everything is fine. I ran it yesterday and it's telling me it can't find a drive. see attachment I'm working with Western Digital on that one, they said the test was outdated, to change a bunch of stuff in the BIOS. So not doing that, that is right up there with playing in the registry without guidance.
I then ran Western Digitals desktop hard drive scan. see attachment 2 & 3 & 4 Amazing how a drive that doesn't exist passes. Also wondering about that test since the drive was making a weird low grade whistling noise when Adobe wanted to access the web to check for updates. Again; will take that up with WD too.

I also just ran another sfc check, some results the same, still interesting.

I ran sfc in "safe mode" it came back a match for the one I ran earlier today. I ran that command prompt from step 1 afterward but all I got was a blank notepad page. Tried several times, blank page every time. That's what happened before too. I even went on-line and tried it, still blank page.
Getting conflicting results on a sfc scan is not new. It's 1 of the primary reasons I did an in place upgrade (repair). 3 times actually. Shouldn't that have fixed those missing files?
If I have to change this HD I will probably change to Windows 7, no reason to put Vista (which I hate) back in. I see OEM versions of that out there. If I change my own hard drive can I buy an OEM version and legally use it??