Indexing does not work window corrupt files window 7

First test the disk using the disk manufacturer's diagnostic tool If it shows errors it can't fix, replace the disk.

If it doesn't find errors, or if it can fix them, after that open an elevated CMD prompt and enter chkdsk DriveLetter: /f /r

You will get asked whether you want it to schedule this after a reboot, answer with Y, and then reboot. This can take a long time, depending on the disk's size and number of file-system errors it finds. When finished, try the SFC and dism commands above again.

test the disk using the disk manufacturer's diagnostic tool - Did passed .
chkdsk DriveLetter: /f /r - Did passed see attached

I followed jcimarron solution link https://www.experts-exchange.com/questions/28096865/windows-7-indexing-service-not-running.html the first 2 where successful but regsvr32 wshom.ocx gave me a msg error code 0x80040201 see attached so I followed this link https://blogs.msdn.microsoft.com/rajakedar_ganta/2012/06/06/dllregisterserver-failed-with-the-error-code-0x80040201/ when I ran regsvr32 /u scmt.dll it gave me a error the module scmt.dll failed to load
(Maybe should I open a separate case for this?)
chdsk.txt
Regsrv32fail.JPG
Regsrv32.JPG

Dear user
Completely remove Microsoft Office and reinstall it, Check if the search is working fine now. You can also refer to the Experts Exchange solved query by referring to the following link:
https://www.experts-exchange.com/questions/28920569/Indexing-issue-in-OUtlook.html

Check if the above solution works. Other than this I found an Informative article on google. Discussing the ways to fix Outlook Indexing problem. But It would be better if you refer experts exchange solved query first. As it is more authorized.

http://www.msoutlookware.com/error/outlook-pst-indexing-not-working.html

Note: The above link provided is a substitute suggestion and includes lengthy steps. So it would be better to refer the suggestion from the link for better understanding. Remember to keep the backup of your PST before performing any operation.

Thanks & Regards
Edwin Hoffer

I don't think the articles address my issue becuse seems to be a system issue since I can't start the window search service
Error      Search      1006      Search service
The Windows Search Service has failed to create the new search index. Internal error <4, 0x8004117f, Failed to add project: C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Projects>.

I have noticed something that may add additional information that may help in diagnosing the issue.

1- C:\ProgramData\Microsoft\Search\Data is not stable, as it is open  it may suddenly get empty, the window and tamp folder just disappears, with a refresh thy come back sometime just the tamp file disappears in some cases when clicking on the tamp file or when creating a new file in the date folder a msg will show up saying that it refers to a location that in unreachable see full msg attached.

2- when opening the indexing option in control manager everything is grayed out except of advents and when opening advents there a wall everything is grayed out. see attached

3 - The date file sometime shows a lock on the icon see attached.

4 - When starting the window update service it stops my sysing The  service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other service or programs

Dose this information offer any help?
Data-folder.PNG
Indexing-options.JPG
Advanced.JPG
Data-lock.JPG

DISM can't be used to repair Win7.  Try running the System Update Readiness Tool.  https://www.microsoft.com/en-us/download/details.aspx?id=20858

These 3 links describe how to look at the resulting log file and correct issues (there's some duplication of information in the links).
https://support.microsoft.com/en-us/kb/947821
https://support.microsoft.com/en-us/kb/2700601
http://www.dell.com/support/article/us/en/04/SLN285523/EN

Here are my own notes from using it.  If you don't understand the code bits below, then I'd just suggest reading the above links and working it out for yourself.

A note about file placement - the KB article mentions putting files in \%windir%\temp\CheckSUR\packages (and \manifests), and another article mentioned extracting files from an .MSU into %windir%\Temp\CheckSUR\servicing\packages, but \Windows\CheckSUR\packages works as well.  Not sure if one is better than another.

The CheckSUR.log file is located under %windir%\Logs\CBS\

If any packages are referenced in the log file, download the corresponding .MSU file and place it in C:\Windows\CheckSUR\packages

From the CheckSUR.log file, copy the names of all .manifest files to a .txt file (e.g. C:\temp\manifest-files.txt) and save it.  On the source machine, create a temporary folder where you will copy all the files that are needed by the destination machine.  Then run a PS command to parse the file for names and copy all matches to a temporary folder (which you should already have created).

cd C:\Windows\winsxs\Manifests
gc C:\temp\manifest-files.txt | % { Copy-Item -Path $_ -Destination c:\temp\missingfiles\$_ }

Select allOpen in new window

Copy the missing manifest files to C:\Windows\CheckSUR\manifests on the destination computer and rerun the System Update Readiness tool.

 

From the CheckSUR.log file, copy the section that lists all the missing payload files to a .txt file (e.g. C:\temp\missing-payloads.txt) and save it.  The following PS command can help with parsing the file to retrieve just the file names (and their parent folder), and then copy those files to a temporary folder.

ipcsv C:\temp\missing-payloads.txt -Delimiter "`t" -Header "Action","Error","Code","File","Folder" |
 % {If ( !(Test-Path "c:\temp\missingfiles\$($_.folder)") ){New-Item "c:\temp\missingfiles\$($_.folder)" -ItemType directory}; Copy-Item "..\$($_.folder)\$($_.file)" -Destination "c:\temp\missingfiles\$($_.folder)\$($_.file)"}

Select allOpen in new window

You can compare counts of lines in the source file vs. files in the specified destination to verify all were copied.  These files will need to be copied to the folders under C:\Windows\winsxs, but before you can do that you will need to take ownership of the folders and change their ACLs.  Unless there's just a couple, it doesn't make sense to just do this to the subfolders, but rather make the changes to the winsxs folder and let inheritance do the rest.

At an elevated command prompt.

cd C:\Windows
takeown /F winsxs /A  (might also use the /R switch)
icacls winsxs /grant:r Administrators:(OI)(CI)(F)

Select allOpen in new window

Copy all the folders from the temporary source and paste into the winsxs folder, merging as needed.  Afterwards you can reset the ownership and ACLs back to default if desired.

icacls winsxs /grant:r Administrators:(OI)(CI)(RX)
psexec -s takeown /F winsxs  (comment:  might also use the /R switch for takeown)

Select allOpen in new window

If I understand you correctly you are to if there is any errors showing in the CheckSUR.log Buy in this case see attached no errors showing in the log. but from the above and see CBS log file my seams to be a permission issue here.

two more pieces of information
1- When ruing the System Update Readiness tool - Error, installer encountered an error 0x800247
2- flowing https://support.microsoft.com/en-us/help/10164/fix-windows-update-errors Right-click the network icon in the notification area and then select Troubleshoot problems  / Shared folder Rtoubleshooting - error, a problem prevent troubleshooting from starting.
CBS.log
CheckSUR.log
CheckSUR.persist.log
WindowsUpdate.log

Sometimes I see the System Update Readiness Tool correct errors that the System File Checker (sfc) cannot.   You mentioned an error when running the tool, but it looks like it ran fine.

I can't say about CBS.log.  I've never been good at interpreting that, so I won't try to walk anyone through it.

I only have a guess about the WindowsUpdate.log - given the message about initializing the datastore, it may be best to just delete the folder C:\Windows\SoftwareDistribution
There are some caveats here.  It's not the first action I would jump to, and I haven't researched the specific message.  This thread has some good discussion about the SoftwareDistribution folder (I would give weight to Lawrence Garvin's comments).
https://social.technet.microsoft.com/Forums/windowsserver/en-US/f5744a18-d4ca-4631-8324-878b9225251d/windowssoftwaredistribution-folder-cleanup-automation?forum=winserverwsus

See attached
System-Update-Readiness-tool.JPG

I did find a mention that for some people that error (and the indexing service) was resolved by installing updated Intel RST drivers.  I don't know if you use those though.
It seems you won't be able to install the SUR tool until Windows updating is fixed.  If updating drivers doesn't resolve the issue, I don't know if there's any other option than clearing out the SoftwareDistribution folder.

I deleted the folder waited 15 minutes restart wait 15 minutes- issue not solved

Do you use the Intel drivers?

I downloaded intel driver update utility it detected a update for the network card but did not install since it cannot be installed as a update need to uninstall the current driver and then run the install. But I had this with a other computer and after uninstalling at restart windows already reinstalled the driver so it was again unable to install the newer version

Agree but the lenovo and intel driver update tool did only detect a update on the network card, so I assume everything else is up to date. agree?

(intel 5 series/3400 series sata ahci controller)

I have no knowledge about the driver update tool.
What's the version of driver listed for "intel 5 series/3400 series sata ahci controller"?

9.5.4.1001
(11/20/09)

Progress!!!!

Its no more giving the error- When starting the window update service it stops my sysing The  service on Local Computer started and then stopped.

But error code 80072efd see attached
WindowUpdate.JPG

The Indaxing started to work

the cfs /scannow passed

The System Update Readiness Tool is running and doing a install will post update.

That's good news!

What's the history of this machine?  When did the problem start?  When was the OS installed?

Its a window 7 used worked fine in general but used to crash but not often. about 3 weeks ago it started crashing a few times a day. I replaces the video card see https://www.experts-exchange.com/questions/28987502/Computer-crashes-on-daily-bases-need-help-to-find-the-cusses.html and since then it stopped crashing but the indexing stopped working, so I checked if windows is up do date and recognized that it does not work. so I opened two tickets one for the indexing (the current) and one for the window update issue https://www.experts-exchange.com/questions/28990438/Windows-update-error.html. My assumption was that because of the crashing so many times the system got corrupt, the  cfs /scannow reported errors and.... today I got a yelling from the business owner that he cannot continue with out the indexing working. so after all the steps in this post and in the other failed I started looking in the direction of a clean install which is not a easy process due to what is on this workstation. now thanks to your support at least I can text the business owner that outlook is indexing and window update needs to be taken care but this is not something that the owner cars about (if he even knows what this is all about- thy care about function and care little when we start to give excuses in technical terms...)

If you're not able to get Windows Update working, I would not rely on the computer and would wipe and reinstall the OS.
When did Windows Update last successfully install updates?

Thank you for your help