Can't type in Windows 10 search box after LP slipstream

[Ricardo Silva]

Hi.

The last Windows 10 1909 uses the same LP's as the 1903.

After LP integration, via DISM, and performing a install on a real machine or VM, it's impossible to type in search box.

It already hapened to anyone here?

Thanks

 

[Ricardo Silva]

Hi.

 

Found the error. After adding the Language Pack, i also added the new Local Experience Pack (LXP).

Problem solved!

Edited November 24, 2019 by Ricardo Silva
miss speled

[shhnedo]

After spending some time making two images(with and without integrated LXP), I didn't experience the search bug you mentioned(no, I did not forget to integrate the 1909 enablement package).

Edited December 1, 2019 by shhnedo

[Ricardo Silva]

Hi. thank you to take time to see my doubt.

The image base is Windows 10 1909h2 PT-PT. And i'm adding Eng, Fr and Spanish.

Only after adding LP's and LPX's that error stoped.

 

[shhnedo]

@Ricardo Silva If you want an up-to-date 19h2 iso, you shouldn't use a 19h2 iso as base to integrate update/lps. All 19h2 isos are 19h1 base with KB4517245 integrated after the ssu/cu.

What you should do:
1. Get a 18362.1 iso for base.

2. Get the LPs for 18362.1 (1903).

3. Get Servicing Stack Update, Cumulative Update, .NET Cumulative Update and KB4517245(use WHDownloader for this one).

4. Integrate LANGUAGE PACKS into boot.wim index 2 and install.wim index *insert your desired index here*.

5. Integrate SSU/CU/.NET CU updates.

6. Integrate KB4517245 !!! AFTER ALL THE OTHER UPDATES !!! (it's a .cab file so don't put it into the same folder as the others, use a separate dism /add-package for it).

7. You have a proper multilingual 19h2 iso.

The problem likely comes from you integrating LPs into an iso which has integrated updates(which all 19h2 isos are) and that's known to be a problematic practice.

Edited December 10, 2019 by shhnedo

[Ricardo Silva]

Thank you for the explanation.

I'll try it.