Hi,
I recently upgraded to Windows 10 and have encountered an interesting problem. I realized it initially when I would press start and begin to type a program's name in order to run it, as I was doing with Windows 7, but it would not find any results and would prompt me to Google the program. I found it strange but didn't think much of it.
Once I started looking into the issue, I noticed when I go to Indexing Options it says "Indexing is not running." When trying to rebuild indexing, it gives the message about how it will take a while, and then does nothing. So I decided to look into Windows Search.
Windows Search is not and will not run. First: If I go to services.msc and try to start the Windows Search service, it tells me that "The Windows Search service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
So I tried through an elevated cmd prompt: "net start wsearch" gives me error 15:
"C:\WINDOWS\system32>net start wsearch
The Windows Search service is starting..
The Windows Search service could not be started.
A system error has occurred.
System error 15 has occurred.
The system cannot find the drive specified."
Finally, and perhaps the strangest thing, one post told me to go to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows Search \ SetupCompletedSuccessfully and change the value to 0. However, the only thing in the registry under Windows Search is a Preferences folder. There are no keys there. So to me it looks as though Windows Search does not currently exist on my computer.
So of course I run sfc /scannow. Unfortunately, it tells me:
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
Any help would be appreciated.
I recently upgraded to Windows 10 and have encountered an interesting problem. I realized it initially when I would press start and begin to type a program's name in order to run it, as I was doing with Windows 7, but it would not find any results and would prompt me to Google the program. I found it strange but didn't think much of it.
Once I started looking into the issue, I noticed when I go to Indexing Options it says "Indexing is not running." When trying to rebuild indexing, it gives the message about how it will take a while, and then does nothing. So I decided to look into Windows Search.
Windows Search is not and will not run. First: If I go to services.msc and try to start the Windows Search service, it tells me that "The Windows Search service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs."
So I tried through an elevated cmd prompt: "net start wsearch" gives me error 15:
"C:\WINDOWS\system32>net start wsearch
The Windows Search service is starting..
The Windows Search service could not be started.
A system error has occurred.
System error 15 has occurred.
The system cannot find the drive specified."
Finally, and perhaps the strangest thing, one post told me to go to HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows Search \ SetupCompletedSuccessfully and change the value to 0. However, the only thing in the registry under Windows Search is a Preferences folder. There are no keys there. So to me it looks as though Windows Search does not currently exist on my computer.
So of course I run sfc /scannow. Unfortunately, it tells me:
C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
Any help would be appreciated.