Direkt zum Inhalt

Clone disabled win7 indexing and troubleshooting

Thread needs solution

I used Acronis True Image HD 2014 to clone a laptop HD to a Curcial MX100 SDD. Everything on the clone works great as far as I can tell, but Win7 Indexing will not start. Furthermore Windows (usually useless) troubleshooting function will not start ("A problem is preventing troubleshooting from starting"). A web search has revealed that others have had this problem but I cannot find where anyone has fixed it.

Is there anything I can do other than a fresh windows install?

Thanks,

Mark

0 Users found this helpful

First indexing on an SSD is useless, those drives are so fast that indexing serves no purpose. It may well be that Windows itself has disabled indexing on your SSD.

Second, your issue with Windows troubleshooting function sounds like there may be some system files corrupted. I would suggest opening an elevated command prompt (right click on the command prompt in the menu and choose Run as Administrator) and at the blinking cursor type sfc /scannow. This will start the Windows system file scanner which when run will check all system files and any found corrupt will be corrected from the file repository. In the command I quoted make certain that you type a space between the sfc and the /scannow.

Thanks for your help. I mistakenly thought indexing was the problem. I often have to search my documents subdirectory, but search does not work in that. Even when I look for a file I know is in there, the search function does not work. Search does seem to work in many other subdirectories. So that is the problem that started after cloning. At first, troubleshooting worked and told me something was preventing indexing from starting, though now it looks like indexing is not the problem.

Now troubleshooting does not work, nor does search in the Documents subdirectory. Troubleshooting gives me the generic 0x8E5E0247 error. BTW, sfc /scannow tells me Windows Resource Protection found corrupt files but was unable to fix some of them.

Any ideas?

I suggest trying the solutions found in the link below :

http://www.thewindowsclub.com/windows-resource-protection-found-corrupt…