Indexing and Searching broken

Slartybart said:

Follow OPTION TWO and OPTION THREE in this tutorial: SFC /SCANNOW Command - System File Checker

Also, please attach sfcdetails.txt from OPTION THREE to your next post

Thanks

Could you please do this as well? This way we can read the log and attempt to fix your corrupted instillation of windows 7.

This is most likely why you are having problems.

Thanks, I'm going to ask for some help on this. The members who do this all the time are quicker at it. I'd have to look up an error and find a solution.

Putting out the call.

edit: Now we wait for the big SFC guns.
I've asked Tom982 and NoelDP to take a look at the SFC output.
There's also output from the SF diagnostic tool.

CBS.zip (see sfcdetails.txt attached to this post)
SF_25-01-2014.zip

Screen shot of SFC results in Command Prompt Window
-

andrew129260 said:

Slartybart said:

Follow OPTION TWO and OPTION THREE in this tutorial: SFC /SCANNOW Command - System File Checker

Also, please attach sfcdetails.txt from OPTION THREE to your next post

Thanks

Could you please do this as well? This way we can read the log and attempt to fix your corrupted instillation of windows 7.

This is most likely why you are having problems.

where do I find the sfcdetails.txt file?

It's in Option 3 as told.
How to See and Read Only the "SFC" Scan Results from the CBS.LOG
NOTE: When SFC runs, it logs it's actions into the C:\Windows\Logs\CBS\CBS.log. The steps in this option will show you how to see only the specific SFC entries with the [SR] tags in this CBS.log. This can be helpful to show you what files SFC could not fix automatically if you wanted to try and manually replace them.

1. Open an "elevated command prompt" (right click -> Run as administrator).

2. In the elevated command prompt, copy and paste the command below, and press Enter. (See screenshot below)
NOTE: This will place a sfcdetails.txt file on your desktop with only the SFC scan result details from the CBS.LOG in it.

Code:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

Attachment 192748

3. Close the elevated command prompt.

4. Open the sfcdetails.txt file on your desktop to see the SFC scan details in the CBS.LOG.

5. You can safely delete the sfcdetails.txt file afterwards if you like.

grandpavic said:

where do I find the sfcdetails.txt file?

Don't worry about it, you already posted the CBS.zip file in post# 80
I ran the findstr command on it when I looked at it. All of the files needed for now are on post# 82

Here's the important bits from the log...

Code:

 Line 67779: 2014-01-28 15:09:47, Info                  CSI    00000631 [SR] Repairing 2 components
 Line 67780: 2014-01-28 15:09:47, Info                  CSI    00000632 [SR] Beginning Verify and Repair transaction
 Line 67783: 2014-01-28 15:09:57, Info                  CSI    00000634 [SR] Cannot repair member file [l:38{19}]"NlsLexicons0009.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 67786: 2014-01-28 15:10:00, Info                  CSI    00000636 [SR] Cannot repair member file [l:38{19}]"NlsLexicons0024.dll" of Microsoft-Windows-NaturalLanguage6, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 67789: 2014-01-28 15:10:01, Info                  CSI    00000638 [SR] Cannot repair member file [l:24{12}]"M1033DSK.CSD" of Microsoft-Windows-MulanTTSVoiceENUDsk, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

I'll post a fix a bit later....

I've uploaded a file - gpcaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\gpcaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\gpcaa
or
DIR E:\gpcaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\gpcaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply.

NoelDP said:

I've uploaded a file - gpcaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.
Pick the option to use a Command Prompt
At the prompt type
DIR C:\gpcaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\gpcaa
or
DIR E:\gpcaa

The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...

XCOPY <drive>:\gpcaa <drive>:\windows\winsxs /y /i /s /v /h

(e.g.XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )

run the command (it should take almost no time)and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.
Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply.

I think that all of the above worked -- THANK YOU

I have attached the log file (cbs.zip)

Do you mean search is working now? That would be really good news.

There are some things left to do regarding search. Things we changed in the process of troubleshooting need to be changed back.

I'll go through the CBS log and see if there's more to do with SFC.

Bill

edit: The SFC log looks good. There are some minor things still reported (NLS / Speechengine) but these might be known issues. I'll do some research, but I'm confident that they can be ignored for now. These entries are not critical.

1. Does Search work in all three location?
2. Does the Search Index show X items indexed, indexing complete?
3. The properties of C:\ need to include "Allow Files on this drive to have..."
   - This folder and all sub foilder/file
   --> it will complain about changing attributes on some files.
   This is not a problem.
4. The Indexed Locations are currently IE History and Start Menu
   - this needs to be expanded to include c:\users [excluding AppData from your profile]

That's a good start.
Let me know if you have any questions before you begin any step, I typed them in abbreviated form and will expand the step if you ask for help. I think you've been in all of the areas and have a good idea of what to do.