search

SysManSquad / sysmansquadblog

1 stars 3 forks source link

Multilingual Windows 10 20H2 OSD with ConfigMgr-SysManSquad | Systems Management Squad #11

Open utterances-bot opened 2 years ago

utterances-bot commented 2 years ago

Multilingual Windows 10 20H2 OSD with ConfigMgr-SysManSquad | Systems Management Squad

A community blog and subsidiary of WinAdmins.io

https://sysmansquad.com/2021/02/16/multilingual-windows-10-20h2-osd-with-configmgr/

danzirulez commented 2 years ago

Adam, as much as I love the article, I simply cannot make a TS work. All logs are fine installing LP, FoD and LXP and then I always end up on the Why did the PC restart? blue error screen being offered an update that'd fix it, of course it doesn't and it's a reboot look from then on :(

It's been weeks now with this :(

Xen10nXen10n commented 1 year ago

Hi there,

First of All thank you for your post, the world of the language pack si getting a bit tricky ... I got the same issue like the previous comment ( Why Did the PC Restart ? with blue Screen).

Do you have a clue about what could be the cause ?

I will try to inject the latest Cumulative update in offline mode...

Thanks again

Best Regards

danzirulez commented 1 year ago

Hi, yes, it's been solved.

Long story short: The ISO (wim) is vanilla, so it does not have anything language-related. When you inject an LCU in this wim, it's NOT updating anything language-related, cos the iso wim still has only en-US in it.

After adding the LP, FoD (LXP can actually be omitted) reapplying LCU is an ABSOLUTE MUST. This is when all the language specific parts of the LCU get applied.

I got this confirmed by an MS imaging guru.

So, what I have now is apply windows image, dism offline the LP, dism offline the FOD and apply the LCU as the last step, still offline, everyrhing in WinPE. Actually the dell driver package is also in winpe so by the step 'install configuration manager client' comes and restarts the machine, I have a full blown healthy windows with the localization.

Some apps like calculator, snip and sketch will stay english for like 1-2 restarts until there's a refresh, which can be forced by a scrip e.g. on the user's first logon, but I misplaced the script myself. got it from the MS guy too. but we aren't using it (now that I lost it :D )

Happy imaging

Xen10nXen10n commented 1 year ago

Hello Danzirulez,

Dude, if I would see you one day let me offer you a nice beer :)

I applied your scenario as following :

  1. From an Install.wim from W10 22H2
  2. Inject Offline all the LXP and FOD
  3. Inject Offline the LCU (KB5019959)

and it works smoothly !

I will make more tests on it but for the moment you helped me to sleep a bit better last night !

Best Regards,

Harry3co commented 1 year ago

Hey everyone I couldn't make it work either with that manual and ts of that post. Still thanks for your effort. I downloaded all the FoD in .cab format and tryd to add them to my basic win10 22h2 install.wim offline. I always get an error 0x800f0818 source file not found even when i pointed to the right directory though. How did you add your LXP to the offline image? I mean it seems to add it by command but when i check get-packages it doesn't show up. Any help would be appreciated. Regards

Harry3co commented 1 year ago

It's actually the error 0x800f081f Here my dism logs: CBS Exec: Failed to retrieve FOD payload [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING] CBS Failed to download and plan capabilities [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING] CBS Failed to plan execution. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING] CBS Failed to process single phase execution. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING] CBS WER: Generating failure report for package: Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.19041.1, status: 0x800f081f, failure source: CBS Other, start state: Absent, target state: Absent, client id: DISM Package Manager Provider CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] i exported all the FoD Cab. en-us files into a repository as descirbed above.

scugulu commented 1 year ago

Hello, Same issue here with the last KB and Windows Wim, If you try to apply the xml file (control intl.cpl,, /f:"UIGermanCH.xml") you have the error, but if you apply the settings with "Apply Windows Settings" the error doesn't come but you need to choose the language over oobe at the end of the staging... Was somebody able to solve the issue ?

I tried with the new Windows 10 21H2.16 version and addind the KB to Windows 10 21H2.7 same issue. Thank you