Cant use "startmenu search"

[Treveo]

I ripped my Vista with vLite 1.1 RC but there is one problem. I cant use the search function in the start menu. I love to use it to start all programs. But now I see some message that the search function cant be used. What should I keep in the image?

[nuhi]

Mine works, maybe you disabled it in the Start Panel options, there are a lot of Search options, enable them all.

If they were enabled then attach your preset.

[django]

Hi nuhi, (firstly, thanks for a wonderful app! )

I also lost the ability to search with version 1.1RC. Both the search from the start menu and also from the file explorer found nothing. There doesn't appear any error messages I just type the thing I'm looking for in the box and nothing happens. This is with the first boot into Vista, ergo no settings were changed in the search options (I did however look through all the options, but I couldn't find anything).

I then tried to vlite again using version 1.1 Beta2, using the exact same settings in vlite as I did with version 1.1RC. And that time search worked 100% they way it should.

I attached the preset used, although I doubt it is of any use.

Is there any list of applications or services that effect Vista Search?

Last_Session.ini

[sp00f]

Here i also cant search anywhere....

Last_Session.ini

Edited January 6, 2008 by sp00f

[HJW]

Mine search function still working

Component deleted:

-Languages (Japanese/chinese )

[sp00f]

I tested with 1.1 beta 2 , and indeed, it works fine.

But with the RC version it gets smaller.

So after i tested with 1.1b2 i reopened the wim with the RC version and there was not much difference.

these 2 :

[Components]

;# Languages #

Table Driven Text Input Processor

;# System #

Run a legacy CPL elevated

I marked those 2 and will test again...

Edit:

After marking those, search still works

So maybe its a way the new vlite removes things?

Edited January 6, 2008 by sp00f

[gdh]

i use a same vlited vista ISO in different computer.

"startmenu search" in some computer is normal,but some computer cant use it.

this is surprisingly

[sp00f]

i use a same vlited vista ISO in different computer.

"startmenu search" in some computer is normal,but some computer cant use it.

this is surprisingly

I tried to install on other computers, but the search function is broken on all computers after install.

Went back to 1.1 beta 2

[yken]

same for me, starting with rc version of vlite i cant use search, even thoughu i did not remove it and windows search service is running ,index is on but it does not start indexing anything, i tried several times but rc makes this.I used previous versions of vlite many times this never happened

[pitape]

Same prob here. I've got a Intel P945/Core 2 Duo 6400 system.

I only removed languages (Japanese, Chinese), speech support, tablet PC and natural language components.

Windows search service is launched and no related error noted in Event Viewer.

Besides this (very) annoying drawback, vLite is wonderful. I never suspected Vista being bloated with:

- 900 MB of modem/printer drivers

- 1.1 GB of Asian languages (why doesn't MS sell a separate Chinese or Japanese version like for French, German, etc)

- 500 MB of speech recognition

- 430 MB of Tablet PC add-ons

- 580 MB of 'natural language' (don't ask what it is... but maybe this is the reason why search does not work if removed)

Total= more than 3.5 GB of features used by % of users?

MS would have been better advised to improve disk and memory management.

[sp00f]

Tested the iso on more pc's, cant use search on any of them after vlite rc

[nuhi]

I think we got enough confirmations to say "yeah there could be some truth in it".

Gonna try it soon, if some of you find out which component it is let us know.

[sp00f]

I wonder why only a few people have this problem

[nuhi]

django, tried your preset and it was fine, did you delete the integrated stuff on the list or it was really this identical preset?

sp00f, can you confirm that it's the Natural Language removal?

[nuhi]

Ok managed to see the issue after integrating any language pack. Fixed for next one.