Removing files from Index

Hi,
I find that Windows Vista's index is not removing files which I
deleted/moved from my harddisk. Is there any way to remove the index of the
files that are deleted from the disk?

"Mugunth" <> wrote in message
news:AE5D38D2-5430-4AAA-852E-...
> Hi,
> I find that Windows Vista's index is not removing files which I
> deleted/moved from my harddisk. Is there any way to remove the index of
> the
> files that are deleted from the disk?


Try clearing 'Recent Items' as a first step

Start > Right-click 'Recent Items' > Clear Recent Items List

--
Jon

No Jon,
I still have that problem...
All my moved and deleted files are still shown up when I search.

-
Mugunth

"Jon" wrote:

>
> "Mugunth" <> wrote in message
> news:AE5D38D2-5430-4AAA-852E-...
> > Hi,
> > I find that Windows Vista's index is not removing files which I
> > deleted/moved from my harddisk. Is there any way to remove the index of
> > the
> > files that are deleted from the disk?
>
>
> Try clearing 'Recent Items' as a first step
>
> Start > Right-click 'Recent Items' > Clear Recent Items List
>
> --
> Jon
>
>
>

"Mugunth" <> wrote in message
news:791B6EC9-8B9C-4621-BE60-...
> No Jon,
> I still have that problem...
> All my moved and deleted files are still shown up when I search.
>
> -
> Mugunth



Check that this setting is set to 'High Performance'

Control Panel > Power Options > Change plan settings > Change advanced Power
settings > Search and Indexing > Power saving mode

If you've got 'Balanced' there, then you can sometimes get that behaviour.


--
Jon

On Sep 19, 5:54 am, Mugunth <Mugu...@discussions.microsoft.com> wrote:
> Hi,
> I find that Windows Vista's index is not removing files which I
> deleted/moved from my harddisk. Is there any way to remove the index of the
> files that are deleted from the disk?

It feels good that I am not alone in this problem, although it really
freaked me out the first time I deleted a batch of files and they
still showed up when I searched for them

You have two or three options..
1) Wait. Wait some more. Then wait some more. The index will (maybe)
(hopefully) eventually catch up with your actions. I have seen this
happen within the time it takes to refresh a directory listing, and I
have seen this take hours. It might be practical to change your
workflow to accomodate this - the cost of the extra 2-3 days it takes
to process a batch of files can be passed on to your client. I am sure
they will not mind.

2) Force the indexer to reindex your system. This is the more drastic
way to get the index up to date. No idea how long it will take and no
idea where the re-indexing starts. But we all know that the Vista
search is 100% effective and any problems you have must be your fault.
The re-indexing will give you time to think about what you hav done.

3) Don't delete files any more. If you do not delete or move files
(and limit the number of new files you create), you should not have
any issues with the index becoming out of date.

or (and as a bonus)

4) Find yourself a replacement explorer shell with a viable search
option.

I used to do this (re-indexing) with GDS and X1 desktop search tools on
windows xp..
I expected, Vista would solve my problem... Again no "WOW"

"theclyde" wrote:

> On Sep 19, 5:54 am, Mugunth <Mugu...@discussions.microsoft.com> wrote:
> > Hi,
> > I find that Windows Vista's index is not removing files which I
> > deleted/moved from my harddisk. Is there any way to remove the index of the
> > files that are deleted from the disk?
>
> It feels good that I am not alone in this problem, although it really
> freaked me out the first time I deleted a batch of files and they
> still showed up when I searched for them
>
> You have two or three options..
> 1) Wait. Wait some more. Then wait some more. The index will (maybe)
> (hopefully) eventually catch up with your actions. I have seen this
> happen within the time it takes to refresh a directory listing, and I
> have seen this take hours. It might be practical to change your
> workflow to accomodate this - the cost of the extra 2-3 days it takes
> to process a batch of files can be passed on to your client. I am sure
> they will not mind.
>
> 2) Force the indexer to reindex your system. This is the more drastic
> way to get the index up to date. No idea how long it will take and no
> idea where the re-indexing starts. But we all know that the Vista
> search is 100% effective and any problems you have must be your fault.
> The re-indexing will give you time to think about what you hav done.
>
> 3) Don't delete files any more. If you do not delete or move files
> (and limit the number of new files you create), you should not have
> any issues with the index becoming out of date.
>
> or (and as a bonus)
>
> 4) Find yourself a replacement explorer shell with a viable search
> option.
>
>

"theclyde" <> wrote in message
news: oups.com...
> On Sep 19, 5:54 am, Mugunth <Mugu...@discussions.microsoft.com> wrote:
>> Hi,
>> I find that Windows Vista's index is not removing files which I
>> deleted/moved from my harddisk. Is there any way to remove the index of
>> the
>> files that are deleted from the disk?
>
> It feels good that I am not alone in this problem, although it really
> freaked me out the first time I deleted a batch of files and they
> still showed up when I searched for them
>
> You have two or three options..
> 1) Wait. Wait some more. Then wait some more. The index will (maybe)
> (hopefully) eventually catch up with your actions. I have seen this
> happen within the time it takes to refresh a directory listing, and I
> have seen this take hours. It might be practical to change your
> workflow to accomodate this - the cost of the extra 2-3 days it takes
> to process a batch of files can be passed on to your client. I am sure
> they will not mind.
>
> 2) Force the indexer to reindex your system. This is the more drastic
> way to get the index up to date. No idea how long it will take and no
> idea where the re-indexing starts. But we all know that the Vista
> search is 100% effective and any problems you have must be your fault.
> The re-indexing will give you time to think about what you hav done.
>
> 3) Don't delete files any more. If you do not delete or move files
> (and limit the number of new files you create), you should not have
> any issues with the index becoming out of date.
>
> or (and as a bonus)
>
> 4) Find yourself a replacement explorer shell with a viable search
> option.
>

lol. I can tell you're a big fan of Vista's Search ;-)

--
Jon

On Sep 19, 7:54 am, "Jon" <Email_Addr...@SomewhereOrOther.com> wrote:
> "theclyde" <thecl...@happy-gods.com> wrote in message
>
> news: oups.com...
>
>
>
>
>
> > On Sep 19, 5:54 am, Mugunth <Mugu...@discussions.microsoft.com> wrote:
> >> Hi,
> >> I find that Windows Vista's index is not removing files which I
> >> deleted/moved from my harddisk. Is there any way to remove the index of
> >> the
> >> files that are deleted from the disk?
>
> > It feels good that I am not alone in this problem, although it really
> > freaked me out the first time I deleted a batch of files and they
> > still showed up when I searched for them
>
> > You have two or three options..
> > 1) Wait. Wait some more. Then wait some more. The index will (maybe)
> > (hopefully) eventually catch up with your actions. I have seen this
> > happen within the time it takes to refresh a directory listing, and I
> > have seen this take hours. It might be practical to change your
> > workflow to accomodate this - the cost of the extra 2-3 days it takes
> > to process a batch of files can be passed on to your client. I am sure
> > they will not mind.
>
> > 2) Force the indexer to reindex your system. This is the more drastic
> > way to get the index up to date. No idea how long it will take and no
> > idea where the re-indexing starts. But we all know that the Vista
> > search is 100% effective and any problems you have must be your fault.
> > The re-indexing will give you time to think about what you hav done.
>
> > 3) Don't delete files any more. If you do not delete or move files
> > (and limit the number of new files you create), you should not have
> > any issues with the index becoming out of date.
>
> > or (and as a bonus)
>
> > 4) Find yourself a replacement explorer shell with a viable search
> > option.
>
> lol. I can tell you're a big fan of Vista's Search ;-)
>
> --
> Jon- Hide quoted text -
>
> - Show quoted text -

Was it that obvious? Actually, I am no a really big fan of any
windows search I have seen. Perhaps for some users they are helpful,
but full text search of all file types is very important for me.

I first realized there was an issue when I was to update a shared
module in an application I support. I wanted to scan through all my VB
source files to find any code that references a public subroutine.
Really freaked me out when the search did not even return the module I
was working on (and had open to the subroutine). Now at work I use
AgentRansack which does a pretty good job. Have not tried it at home
on Vista yet

"theclyde" <> wrote in message
news: ups.com...
>>
>> lol. I can tell you're a big fan of Vista's Search ;-)
>>
>> --
>> Jon- Hide quoted text -
>>
>> - Show quoted text -
>
> Was it that obvious? Actually, I am no a really big fan of any
> windows search I have seen. Perhaps for some users they are helpful,
> but full text search of all file types is very important for me.
>
> I first realized there was an issue when I was to update a shared
> module in an application I support. I wanted to scan through all my VB
> source files to find any code that references a public subroutine.
> Really freaked me out when the search did not even return the module I
> was working on (and had open to the subroutine). Now at work I use
> AgentRansack which does a pretty good job. Have not tried it at home
> on Vista yet
>

Yep, it's a bit odd that the .vb extension should have the 'File Properties
only' filter by default, rather than a plain text filter, which allows
content search. Some of the default settings are certainly questionable.

--
Jon

"theclyde" <> wrote in message
news: ups.com...
> ... Perhaps for some users they are helpful,
> but full text search of all file types is very important for me.
>
> I first realized there was an issue when I was to update a shared
> module in an application I support. I wanted to scan through all my VB
> source files to find any code that references a public subroutine.
> Really freaked me out when the search did not even return the module I
> was working on (and had open to the subroutine).

Windows Vista: It's not for scientists or programmers. Unfortunately for
me, I'm a scientific programmer.

When will Microsoft care enough to listen and fix search in Vista?

C. elegans