A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

One for Good Guy



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old May 10th 18, 10:34 PM posted to alt.comp.os.windows-10
Ed Cryer
external usenet poster
 
Posts: 2,621
Default One for Good Guy

This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded OEM
Win10, onto which (after a little removal of bundled garbage) I loaded
Win10 1083 from DVD. I don't know if the indexing was working before
that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in Appdata.
2. SFC/ SCANNOW - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running 1803;
and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the Services
are running and the program is in memory.
8. Googled a lot without success.

Ed



Ads
  #2  
Old May 10th 18, 11:13 PM posted to alt.comp.os.windows-10
Ed Cryer
external usenet poster
 
Posts: 2,621
Default One for Good Guy

Ed Cryer wrote:
This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded OEM
Win10, onto which (after a little removal of bundled garbage) I loaded
Win10 1083 from DVD. I don't know if the indexing was working before
that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in Appdata.
2. SFC/ SCANNOWÂ* - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running 1803;
and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the Services
are running and the program is in memory.
8. Googled a lot without success.

Ed




Correction.
The Windows.edb file is 25MB in size.

Ed


  #3  
Old May 11th 18, 12:50 AM posted to alt.comp.os.windows-10
Jason
external usenet poster
 
Posts: 144
Default One for Good Guy

In article ,
says...

This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded OEM
Win10, onto which (after a little removal of bundled garbage) I loaded
Win10 1083 from DVD. I don't know if the indexing was working before
that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in Appdata.
2. SFC/ SCANNOW - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running 1803;
and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the Services
are running and the program is in memory.
8. Googled a lot without success.

Ed


Search was giving me weird problems recently too. I found
this article that fixed it by, apparently, forcing a re-
install. You set a registry key that indicates that Search
setup failed. It will get re-installed after you reboot.
It wipes the existing index however.

http://www.thewindowsclub.com/window...h-indexer-not-
working
  #4  
Old May 11th 18, 04:37 PM posted to alt.comp.os.windows-10
Ed Cryer
external usenet poster
 
Posts: 2,621
Default One for Good Guy

Jason wrote:
In article ,
says...

This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded OEM
Win10, onto which (after a little removal of bundled garbage) I loaded
Win10 1083 from DVD. I don't know if the indexing was working before
that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in Appdata.
2. SFC/ SCANNOW - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running 1803;
and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the Services
are running and the program is in memory.
8. Googled a lot without success.

Ed


Search was giving me weird problems recently too. I found
this article that fixed it by, apparently, forcing a re-
install. You set a registry key that indicates that Search
setup failed. It will get re-installed after you reboot.
It wipes the existing index however.

http://www.thewindowsclub.com/window...h-indexer-not-
working


This looked hopeful to me, Jason. But the key was set to zero, so I
reset it and saved, rebooted ... no change, unfortunately; and the
Windows.edb has got yesterday's date on it.
I'm starting to wonder if this is a 1803 issue. Maybe the coming days
will tell.

Ed

  #5  
Old May 11th 18, 07:40 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default One for Good Guy

Ed Cryer wrote:
Jason wrote:
In article ,
says...

This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded OEM
Win10, onto which (after a little removal of bundled garbage) I loaded
Win10 1083 from DVD. I don't know if the indexing was working before
that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in Appdata.
2. SFC/ SCANNOW - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running 1803;
and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the Services
are running and the program is in memory.
8. Googled a lot without success.

Ed


Search was giving me weird problems recently too. I found
this article that fixed it by, apparently, forcing a re-
install. You set a registry key that indicates that Search
setup failed. It will get re-installed after you reboot.
It wipes the existing index however.
http://www.thewindowsclub.com/window...h-indexer-not-
working


This looked hopeful to me, Jason. But the key was set to zero, so I
reset it and saved, rebooted ... no change, unfortunately; and the
Windows.edb has got yesterday's date on it.
I'm starting to wonder if this is a 1803 issue. Maybe the coming days
will tell.

Ed


I forced a rebuild of the Search Index on my 1803
install, and didn't have an issue. It was 1.9GB for 290,000 files.

C:\ProgramData\Microsoft\Search\Data\Applications\ Windows\windows.edb

In Data\Applications\Windows you can also find Gatherlogs\SystemIndex
where there are .crwl and .gthr files. One gather file is 49KB
of text and shows some places it has visited.

You could also try looking in EventVwr for breadcrumbs,
but I don't really know what the best place is to look
for logs for that thing.

I suppose you could also trace down the dependencies
of the Windows Search service, and see if those services
are running.

Paul
  #7  
Old May 12th 18, 03:11 AM posted to alt.comp.os.windows-10
Jason
external usenet poster
 
Posts: 144
Default One for Good Guy

In article ,
says...
But the key was set to zero, so I
reset it and saved, rebooted ... no change,


Are you saying the key was already set to zero? In my case
it wasn't.

  #9  
Old May 12th 18, 12:54 PM posted to alt.comp.os.windows-10
Ed Cryer
external usenet poster
 
Posts: 2,621
Default One for Good Guy

Paul wrote:
Ed Cryer wrote:
Jason wrote:
In article ,
says...

This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded OEM
Win10, onto which (after a little removal of bundled garbage) I loaded
Win10 1083 from DVD. I don't know if the indexing was working before
that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in
Appdata.
2. SFC/ SCANNOWÂ* - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running 1803;
and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the Services
are running and the program is in memory.
8. Googled a lot without success.

Ed

Search was giving me weird problems recently too. I found
this article that fixed it by, apparently, forcing a re-
install. You set a registry key that indicates that Search
setup failed. It will get re-installed after you reboot.
It wipes the existing index however.
Â* http://www.thewindowsclub.com/window...h-indexer-not-
working


This looked hopeful to me, Jason. But the key was set to zero, so I
reset it and saved, rebooted ... no change, unfortunately; and the
Windows.edb has got yesterday's date on it.
I'm starting to wonder if this is a 1803 issue. Maybe the coming days
will tell.

Ed


I forced a rebuild of the Search Index on my 1803
install, and didn't have an issue. It was 1.9GB for 290,000 files.

C:\ProgramData\Microsoft\Search\Data\Applications\ Windows\windows.edb

In Data\Applications\Windows you can also find Gatherlogs\SystemIndex
where there are .crwl and .gthr files. One gather file is 49KB
of text and shows some places it has visited.

You could also try looking in EventVwr for breadcrumbs,
but I don't really know what the best place is to look
for logs for that thing.

I suppose you could also trace down the dependencies
of the Windows Search service, and see if those services
are running.

Â*Â* Paul


I've installed "Everything" and that is broken too. No response, just
sits there. Try to rebuild index, and nothing. It's strangely the same
as with WindowsSearch in its dumb behaviour. I can usually get some kind
of response from a screwed-up program.
Obviously some common service or device is missing.
They have an excellent trouble-shooting help page. I'll have to peruse
that when I have time.
http://www.voidtools.com/faq/#troubleshooting

Ed

  #10  
Old May 13th 18, 12:29 PM posted to alt.comp.os.windows-10
Ed Cryer
external usenet poster
 
Posts: 2,621
Default One for Good Guy

Ed Cryer wrote:
Paul wrote:
Ed Cryer wrote:
Jason wrote:
In article ,
says...

This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded
OEM
Win10, onto which (after a little removal of bundled garbage) I loaded
Win10 1083 from DVD. I don't know if the indexing was working before
that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in
Appdata.
2. SFC/ SCANNOWÂ* - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running
1803;
and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the Services
are running and the program is in memory.
8. Googled a lot without success.

Ed

Search was giving me weird problems recently too. I found
this article that fixed it by, apparently, forcing a re-
install. You set a registry key that indicates that Search
setup failed. It will get re-installed after you reboot.
It wipes the existing index however.
Â* http://www.thewindowsclub.com/window...h-indexer-not-
working


This looked hopeful to me, Jason. But the key was set to zero, so I
reset it and saved, rebooted ... no change, unfortunately; and the
Windows.edb has got yesterday's date on it.
I'm starting to wonder if this is a 1803 issue. Maybe the coming days
will tell.

Ed


I forced a rebuild of the Search Index on my 1803
install, and didn't have an issue. It was 1.9GB for 290,000 files.

C:\ProgramData\Microsoft\Search\Data\Applications\ Windows\windows.edb

In Data\Applications\Windows you can also find Gatherlogs\SystemIndex
where there are .crwl and .gthr files. One gather file is 49KB
of text and shows some places it has visited.

You could also try looking in EventVwr for breadcrumbs,
but I don't really know what the best place is to look
for logs for that thing.

I suppose you could also trace down the dependencies
of the Windows Search service, and see if those services
are running.

Â*Â*Â* Paul


I've installed "Everything" and that is broken too. No response, just
sits there. Try to rebuild index, and nothing. It's strangely the same
as with WindowsSearch in its dumb behaviour. I can usually get some kind
of response from a screwed-up program.
Obviously some common service or device is missing.
They have an excellent trouble-shooting help page. I'll have to peruse
that when I have time.
http://www.voidtools.com/faq/#troubleshooting

Ed

Agent Ransack works, however.

Ed


  #11  
Old May 13th 18, 03:36 PM posted to alt.comp.os.windows-10
Ed Cryer
external usenet poster
 
Posts: 2,621
Default One for Good Guy

Ed Cryer wrote:
This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded OEM
Win10, onto which (after a little removal of bundled garbage) I loaded
Win10 1083 from DVD. I don't know if the indexing was working before
that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in Appdata.
2. SFC/ SCANNOWÂ* - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running 1803;
and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the Services
are running and the program is in memory.
8. Googled a lot without success.

Ed




I've got Everything working, simply by re-installing it with "Everything
Services" ticked. It now has an entry in the Services with automatic start.

I think I have no option now other than to look through the Services
list one by one, fully attentive.

Ed

  #12  
Old May 13th 18, 06:58 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default One for Good Guy

Ed Cryer wrote:
Ed Cryer wrote:
Paul wrote:
Ed Cryer wrote:
Jason wrote:
In article ,
says...

This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from
preloaded OEM
Win10, onto which (after a little removal of bundled garbage) I
loaded
Win10 1083 from DVD. I don't know if the indexing was working before
that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in
Appdata.
2. SFC/ SCANNOW - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running
1803;
and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the
Services
are running and the program is in memory.
8. Googled a lot without success.

Ed

Search was giving me weird problems recently too. I found
this article that fixed it by, apparently, forcing a re-
install. You set a registry key that indicates that Search
setup failed. It will get re-installed after you reboot.
It wipes the existing index however.
http://www.thewindowsclub.com/window...h-indexer-not-
working


This looked hopeful to me, Jason. But the key was set to zero, so I
reset it and saved, rebooted ... no change, unfortunately; and the
Windows.edb has got yesterday's date on it.
I'm starting to wonder if this is a 1803 issue. Maybe the coming
days will tell.

Ed


I forced a rebuild of the Search Index on my 1803
install, and didn't have an issue. It was 1.9GB for 290,000 files.

C:\ProgramData\Microsoft\Search\Data\Applications\ Windows\windows.edb

In Data\Applications\Windows you can also find Gatherlogs\SystemIndex
where there are .crwl and .gthr files. One gather file is 49KB
of text and shows some places it has visited.

You could also try looking in EventVwr for breadcrumbs,
but I don't really know what the best place is to look
for logs for that thing.

I suppose you could also trace down the dependencies
of the Windows Search service, and see if those services
are running.

Paul


I've installed "Everything" and that is broken too. No response, just
sits there. Try to rebuild index, and nothing. It's strangely the same
as with WindowsSearch in its dumb behaviour. I can usually get some
kind of response from a screwed-up program.
Obviously some common service or device is missing.
They have an excellent trouble-shooting help page. I'll have to peruse
that when I have time.
http://www.voidtools.com/faq/#troubleshooting

Ed

Agent Ransack works, however.

Ed


If Everything.exe runs as Administrator, it should be
able to read the $MFT. That's one reason the collection
of file names can be fast on the thing.

A benefit of using the $MFT, is being able to build
a complete file list. Fewer pesky permissions to get
in the way.

However, when Everything wants to get size and date
info, that's probably collected a more traditional way.

I'm not aware of any utility that is guaranteed to list
everything. There are always a few items that remain
illusive, but these would not be something you were
searching for either.

*******

Windows Search doesn't work like that. It has "crawling"
and "gathering" functions. On the first pass, obviously
it has to build a map of what to index.

On subsequent runs, it uses the USN Journal, which is
a log of file system changes. New files could be created,
or old files deleted, and each of those events is
recorded in the Journal. Even Everything.exe uses
the USN Journal on NTFS, to instantaneously add or
modify the file list, to keep it up to date.

If you were starting Windows Search for the first time,
or if you clicked the "Rebuild" function, it should
look at the list of exceptions, and build a path to
be indexed. And then it crawls that path, to discover
all the files in the path or tree. Some log files are
kept, of the results (but probably not with the
level of detail you need right now). And outright failure,
you'd think that would be logged in Event Viewer.

And remember that Windows doesn't take "no" for an answer
when it comes to Indexing. It's very persistent. So whatever
is wrong, some service can't be started or starting.

Paul
  #13  
Old May 13th 18, 07:46 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default One for Good Guy

Ed Cryer wrote:
Ed Cryer wrote:
This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded
OEM Win10, onto which (after a little removal of bundled garbage) I
loaded Win10 1083 from DVD. I don't know if the indexing was working
before that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in Appdata.
2. SFC/ SCANNOW - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running
1803; and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the Services
are running and the program is in memory.
8. Googled a lot without success.

Ed




I've got Everything working, simply by re-installing it with "Everything
Services" ticked. It now has an entry in the Services with automatic start.

I think I have no option now other than to look through the Services
list one by one, fully attentive.

Ed


Services used to have "Dependency" information, such
that you could tell what services a given service needs
to work. As an example, virtually every service now has
a dependency on RPC (remote procedure call). It's become
so bad, I don't think you can even turn off RPC, because it
would seriously gut the OS.

Note that this Dependency information is not "automatically generated".
It's statically generated at Microsoft and loaded into
the tabs for your usage. In Windows 7, one of the dependencies
to make audio work, was missing from one service. And users
who disabled a certain service, would lose audio, and yet
the Dependencies info would not list the missing service
they needed to re-enable.

So while Dependency information is present in the OS, it
comes with no guarantee of correctness. The information
is "mostly correct".

Paul
  #14  
Old May 13th 18, 08:31 PM posted to alt.comp.os.windows-10
Ed Cryer
external usenet poster
 
Posts: 2,621
Default One for Good Guy

Paul wrote:
Ed Cryer wrote:
Ed Cryer wrote:
This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed out,
and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded
OEM Win10, onto which (after a little removal of bundled garbage) I
loaded Win10 1083 from DVD. I don't know if the indexing was working
before that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in Appdata.
2. SFC/ SCANNOWÂ* - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running
1803; and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the
Services are running and the program is in memory.
8. Googled a lot without success.

Ed




I've got Everything working, simply by re-installing it with
"Everything Services" ticked. It now has an entry in the Services with
automatic start.

I think I have no option now other than to look through the Services
list one by one, fully attentive.

Ed


Services used to have "Dependency" information, such
that you could tell what services a given service needs
to work. As an example, virtually every service now has
a dependency on RPC (remote procedure call). It's become
so bad, I don't think you can even turn off RPC, because it
would seriously gut the OS.

Note that this Dependency information is not "automatically generated".
It's statically generated at Microsoft and loaded into
the tabs for your usage. In Windows 7, one of the dependencies
to make audio work, was missing from one service. And users
who disabled a certain service, would lose audio, and yet
the Dependencies info would not list the missing service
they needed to re-enable.

So while Dependency information is present in the OS, it
comes with no guarantee of correctness. The information
is "mostly correct".

Â*Â* Paul


I've found a very deeply buried suggested cure;
https://goo.gl/88a8mV
I started deleting the files until I got to some that I couldn't because
they were open to System. I also noticed that (even though I'd stopped
the Windows Search service) some were being recreated before my eyes as
I proceeded!!?
Right, so I'll try Safe Mode or dig out my old Knoppix disk. But not
until after a good night's sleep, as I'm approaching burn-out for
today's allowance.

Ed
  #15  
Old May 13th 18, 11:38 PM posted to alt.comp.os.windows-10
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default One for Good Guy

Ed Cryer wrote:
Paul wrote:
Ed Cryer wrote:
Ed Cryer wrote:
This will take a real Win10 lover.

Indexing problem.

The Indexing Options GUI has a message "Waiting to receive indexing
status ...".
The indexed locations are blank, "Modify" and "Pause" are greyed
out, and when I hit "Advanced" the thing crashes.
This is a brand new computer, only set-up 3 days ago from preloaded
OEM Win10, onto which (after a little removal of bundled garbage) I
loaded Win10 1083 from DVD. I don't know if the indexing was working
before that. The Windows.edb file is dated set-up date, 25GB but empty.

Everything else is beautiful and smooth.
Things I've tried
1. Memory scan, HD scan, several AVs - all excellent; including
individual ones of the SearchIndex progs in Win32 and the DB in
Appdata.
2. SFC/ SCANNOW - 100% violation free.
3. Checked Services; Windows Search depends on;
Remote Procedure Call (RPC), which includes;
DCOM Server Process Launcher
RPC Endpoint Mapper
All up and running.
4. Tried all three index rebuild methods mentioned herein;
https://goo.gl/zNxrWZ
5. Checked that indexing is working OK on two other boxes running
1803; and it is on both.
6. Analysed the DB file with Windows Search Index Analyser
(http://www.edbsearch.com/freetrial.html), and the file seems empty.
7. Deleted Windows.edb, restarted, not recreated although the
Services are running and the program is in memory.
8. Googled a lot without success.

Ed




I've got Everything working, simply by re-installing it with
"Everything Services" ticked. It now has an entry in the Services
with automatic start.

I think I have no option now other than to look through the Services
list one by one, fully attentive.

Ed


Services used to have "Dependency" information, such
that you could tell what services a given service needs
to work. As an example, virtually every service now has
a dependency on RPC (remote procedure call). It's become
so bad, I don't think you can even turn off RPC, because it
would seriously gut the OS.

Note that this Dependency information is not "automatically generated".
It's statically generated at Microsoft and loaded into
the tabs for your usage. In Windows 7, one of the dependencies
to make audio work, was missing from one service. And users
who disabled a certain service, would lose audio, and yet
the Dependencies info would not list the missing service
they needed to re-enable.

So while Dependency information is present in the OS, it
comes with no guarantee of correctness. The information
is "mostly correct".

Paul


I've found a very deeply buried suggested cure;
https://goo.gl/88a8mV
I started deleting the files until I got to some that I couldn't because
they were open to System. I also noticed that (even though I'd stopped
the Windows Search service) some were being recreated before my eyes as
I proceeded!!?
Right, so I'll try Safe Mode or dig out my old Knoppix disk. But not
until after a good night's sleep, as I'm approaching burn-out for
today's allowance.

Ed


Yes, you want to be fully rested.

https://www.tenforums.com/performanc...ng-broken.html

There's a troubleshooter for it. A troubleshooter that
can't fix it :-)

Paul
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 02:02 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.