Problems with Search plugin

Hi.

Search into WinPE is not working for me. I've the latest WinBuilder with the latest search plugin. I'm using an iso downloaded (Windows 10 en-US) from TechBench.
The search script was selected and I didn't get any error. If I type something, nothing happens.

I tried with different languages too, such as en-GB, pt-BR and ko-KR. En-us, en-gb and pt-br aren't working. But ko-KR works fine.

So, I don't know if there is something missing from script or I'm doing something wrong.

I wonder someone could help me, please.

Thanks.

I've the latest WinBuilder with the latest search plugin

do not use latest winbuilder, use the one distributed with project, latest winbuilder would have bugs that would cause unwanted results.


Win10PESE is under development with contributions,
 especially "Components" and later plugins developed with contributions,
 project admins mainly work on things of their interest, and core plugins,

as you already know, ied206 made Search available only for Korean builds, and you already posted there:
http://theoven.org/index.php?topic=1457



some ways you should follow:
* wait ied206 respond on other topic, maybe ied206 interested in search for western languages maybe not, up to ied206
* work on search plugin to figure out what is missing
* wait someone get search plugin work on western languages on Win10

Thank you for help me, Lancelot.

I'm using this 2015-10-14 Winbuilder project. Is it right?

Yes, ied206 is helping me, but I created this topic because maybe someone has a tip.

And yes, I've been working to find out what's wrong. And I found something interesting.

On Korean build using process monitor I saw a process running from Windows.Storage.Search.dll, but on my build this process won't start.

So, now I don't know if the problem is a missing file or with registry.

Thanks.

I highly guess, you mean Win10PESE 2015-10-14 zip package.

since there is no such thing named 2015-10-14 Winbuilder project 

*
See FAQ
Important
..
After you download and extract zip distribution
 First use "Utils\Update XXX (Exact and Secure)"
....



*

See FAQ
http://theoven.org/index.php?topic=834.0

** Forum TheOven.org
....

to figure out how wheels turn around here, unlike "General Forums"

I strongly advice, read 


*
Well as you see it is not easy to create such plugins ;)
 Process Monitor is your best friend, you can trace compare what happens when windows calls Windows.Storage.Search.dll , before and after....
 I wish my best luck 

Thank you Lancelot.
I'm doing my best to figure out what's is wrong.

If someone knows what's is wrong or has a tip I would appreciate that.

Thanks.

Hello, I reproduced your search problem in my en-US build today. Now I am trying out to find the cause.
I have been busy lately, sorry for late reply.

To fix this issue, we should research about which dll is needed for en-US search.
In my case, I found ko-KR dependency with a word 'kor', 'dll' and some luck.
Better to start with googling with a keyword like 'Windows 10 Search not working', etc.

As Lancelot said, Process Monitor will be our friend for troubleshooting...

Add) Does this problem exists in Win7PESE, Win8PESE, Win8.1SE too?

Found the cause : prm0009.dll was missing.
According to NirSoft (http://windows10dll.nirsoft.net/prm0009_dll.html), the name of dll is 'Microsoft English Natural Language Data and Code'.

When I tried to do search in en-US Win10PESE, I analyized explorer.exe with Process Monitor.
explorer.exe was looking for prm0009.dll, but it was missing.
So I added prm0009.dll to Target directory and repacked wim, then Search works well in en-US Win10PESE.
(Praise Sysinternals again for its great debug tool!  )

I guess that search bug in en-US may affect Win7PESE, Win8PESE, Win8.1SE too, so mynhow, can you test it?
Attached plugin is an experimental script (v11) which adds prm0009.dll when using en-US source.

I guess that search bug in en-US may affect Win7PESE, Win8PESE, Win8.1SE too, so mynhow, can you test it?

For me, search works fine in Win7PESE. In Win10PESE, I had the same issue - search was not working, so I used the Start10 plugin as a workaround.

ied206, I've just tested you v11 search plugin with the Classic Shell plugin, it works fine. The only disadvantage is that this Start menu needs a lot more time to load on boot against Start10.

Kvark, thank you for your test.
I also tested en-US Win8.1SE too, which works fine without prm0009.dll.
It seems prm0009.dll is only needed for en-US Windows 10.

So I changed v11 plugin to copy prm0009.dll only for en-US Windows 10.
Here it is, please test is with SE Projects.

Kvark, thank you for your test.
I also tested en-US Win8.1SE too, which works fine without prm0009.dll.
It seems prm0009.dll is only needed for en-US Windows 10.

So I changed v11 plugin to copy prm0009.dll only for en-US Windows 10.
Here it is, please test is with SE Projects.

Thank you, ied206. I can see that the new version of the plugin is on the server.
How can I add Russian language support to this plugin?

Kvark, Process Monitor is a best tool for debugging executable's dependency.

Build PE with 'Apps - System Tools - Debug - Sysinternals Process Monitor' checked.
Then, boot a built PE, and launch Process Monitor.

You can see an icon looks like radar.


Drag this icon to explorer's search bar.


Before you start typing into search bar, press Ctrl+X in process monitor.
It will remove unrelated events.
When you are ready, type some words into search bar, then press Ctrl+E to stop logging.

You can save a log into PML file and analyize it later with Process Monitor (or analyize at runtime)

When you open PML file in Process Monitor, you should filter events to find some information.

Filter with [Path] [contains] [dll] then [Include] option.
Search for file operations : CreateFile, ReadFile, QueryOpen, QueryStandardInformation, etc.
(You can exclude registry operations in this case)

Then search for failure message like NAME NOT FOUND in 'Result' column.
Look for the time near when you typed in search bar, and you will be able to notice some dll dependency.
(Simple Scenario : An executable looks for dll as a dependency, but it cannot find it : produce NAME NOT FOUND message)

When you found some uncopied dependency dlls, copy it manually to System32 and repack wim.
Repeat this to find all of dependency dlls, then at some point Search will work in your locale.

Thank you ied206. It's working now.

But for me I needed to include NlsData0009.dll too. Just prm0009.dll didn't work. Copy these files by script to an en-GB build works fine too.

Now I'm testing with pt-BR. But it uses different files.

Thanks again.

In my case, I used MSDN Official Image (en-US, ko-KR) as a source.
It seems dependency is slightly different by source of ISO.

According to mynhow, it should be changed to like this.

Code: [Select]

If,%DistLang%,Equal,en-US,Begin
Require_FileQ,prm0009.dll
Require_FileQ,NlsData0009.dll
End
If,%DistLang%,Equal,en-GB,Begin
Require_FileQ,prm0009.dll
Require_FileQ,NlsData0009.dll
End

It has to be checked that if en-NonUS (like en-GB) workes well with this code.
If it is, it can be modified to support all of English locales generally.

Code: [Select]

StrFormat,LEFT,%DistLang%,2,%DistLangFirst%
If,%DistLangFirst%,Equal,en,Begin
Require_FileQ,prm0009.dll
Require_FileQ,NlsData0009.dll
End

Thanks ied206,

I added your reply 11 to FAQ
http://theoven.org/index.php?topic=834
Q: How to Find dependencies ?

If it is, it can be modified to support all of English locales generally.

Just for info:
MS call them with name: "Western Europe Language Group"
or "Western Europe and United States Language Group" ... 

Hi ied206.

I tested here and works fine on en-GB. So you don't need to create "If,%DistLangFirst%,Equal,en,Begin" to both.

I tested pt-BR and I found the missing files: NlsData0416.dll and MLS6.dll

I cannot upload files, so if you ied206 or a moderator could update the script, I would really appreciate it.

I will try with a Italian iso now.

Off: ied206, thank you for your tip about process monitor. The work is easier now.

Thanks.

Thanks ied206, mynhow 

 Search_v12.script (53.49 kB - downloaded 118 times.)

prm00*.dll files and Nlsdata*.dll: Ms Neutral language data and code seems not require in 7, 8 and 8.1. I have not added

mynhow: Can you confirm for NlsData0009.dll, here, with an en-US build, it works without. And for fr-FR it works without NlsData000c.dll ?

For compatibility with different languages, I added with if existFile....

Code: [Select]

If,ExistFile,%Source_sys%\prm*.dll,FileCopy,%Source_sys%\prm*.dll,%Target_sys%
If,ExistFile,%Source_sys%\MLS*.dll,FileCopy,%Source_sys%\MLS*.dll,%Target_sys%
If,ExistFile,%Source_sys%\NlsData*.dll,FileCopy,%Source_sys%\NlsData*.dll,%Target_sys%
// NlsData0000.dll seems not needed
If,ExistFile,%Target_sys%\NlsData0000.dll,FileDelete,%Target_sys%\NlsData0000.dll

Hi, ChrisR.

Thanks for update the script.

I was testing here an en-US build and  it doesn't need NlsData0009.dll to work. I've thought it was necessary but it isn't.

pt-BR and it-IT need MLS6.dll to work. I think nlsdata*.dll isn't necessary anymore.

I'll test both again and post here the results. About fr-FR I'll test it too. Just give me some time.

Thanks.

Hi mynhow,

For the french one, it's my base and it does not need additional files, even if NlsData000c.dll is in the source DVD.
I guess that NlsData*.dll file are not required for the the search plugin, to put in comment probably.
with the if existFile prm*.dll, MSI*.dll I hope it should work for most languages.

I wait your latest results, no rush, to put on the server 

Hi ChrisR.

I've tested here and the results are:

en-US and en-GB need prm*.dll only.   
pt-br and it-IT need MLS*.dll only.

So, I guess most of languages will work with one of these files.

Thanks.