Side by Side Config Incorrect

hello i'm french and i'have same error side by side with ver 2019-03-12 it's ok with 2019-02-02 but i'have lost it's possible sent to me ?

(sorry for my english)

find ver 2019.02.12 it's working

hello i'm french and i'have same error side by side with ver 2019-03-12

find ver 2019.02.12 it's working

With the same things, ISO, Package, it works here without problems here

If you have the same windows 10 17663.107 French ISO from Techbench by WZT

Code: [Select]

Win10_1809Oct_French_x64.iso (SHA1: 9c0cc504ccf1412a124c46863cc2d46c36327666)
Win10_1809Oct_French_x32.iso (SHA1: d363480055eb103a8347393849659f39ef930bcd)

With the same package, unchanged, you should have the same result.
Wimlib extract should have the same behavior and you should have the same file list.
I don't see any reason why it shouldn't be the same

Using an old package is not really the right way to understand 

I created a plugin to generate an extended Log for Support with

Code: [Select]

SupportLog_Win10XPE.html (builder log)
dism.log
script.project
TargetlistFiles.txt

Packed in SupportLog_Win10XPE_YYYMMDD_HHMM00.7z at the base project directory
The SupportLog File is auto created if the checkBox "Enable Support Log" is enabled in Win10XPE main interface .
It should be able to help, in part, I hope 

Please, Can you rebuild using a fresh Win10XPE_2019-03-12 extracted in a new folder (without any modification) 
Save Projects_SupportLog.7z below, at root of this new folder + Extract here
 Projects_SupportLog.7z (9.8 kB - downloaded 44 times.)

And share SupportLog_Win10XPE_YYYMMDD_HHMM00.7z 

my ISO  is Win10_1809Oct_French_x64.iso from techbench with win10xpe2019-02-12 full ok not bug side by side, same ISO with win10expe2019-02-18 -> win10xpe2019-03-12 bug side by side.

my log without my log add

Salut Ledu,
In French
Merci pour ta coopération et pour essayer de comprendre
Je vais essayer de préparer un script ce soir pour faire des tests supplémentaires. Est-ce que c'est Ok pour toi ?

Pas facile pour comparer les Logs, tu n'es pas avec la construction standard sans modifications, ex: DotNET, Network, SoundEvents, AllInRam sont activés
Je veux dire par construction standard:
Extraire Win10XPE_2019-03-12.7z dans un nouveau dossier > Lancer WinXPE.exe > Selectionner l'ISO > Construction 

Please, Can you rebuild using a fresh Win10XPE_2019-03-12 extracted in a new folder (without any modification) 

Autant pour moi je refais un log demain sans aucune modification si besoin je n'avais juste pas mis mon custom folder pour le test

hi ChrisR

didnt read it  ,vous êtes un génie 

Start_Win10XPE.cmd


@Echo Off
Pushd %~dp0
Set "params=%*"
( If Exist "%temp%\getadmin.vbs" Del "%temp%\getadmin.vbs" ) && fsutil dirty query %systemdrive% 1>nul 2>nul || (  echo Set UAC = CreateObject^("Shell.Application"^) : UAC.ShellExecute "cmd.exe", "/C cd ""%~sdp0"" && %~s0 %params%", "", "runas", 1 >> "%temp%\getadmin.vbs" && "%temp%\getadmin.vbs" && Exit /B )

Set WIMLIB_IMAGEX_IGNORE_CASE=1
Start /B Win10XPE.exe

this solved the problem 

Not for me cretino :/

So, has this been fixed?

I tried the 3-10 version with 1809 32-bit.
First, it was missing the 64-bit EFI boot files (copied over)
Then, it is missing winloader.efi in the image Windows\(system?) directory, so I couldn't even test it :(

Try Booting X64 Build on X64 UEFI PC
32Bit Build on X64 UEFI PC > only supported with ATOM processors

Otherwise you Need MBR/Legacy Support Enabled

Not for me cretino :/

@Ledu, peux tu faire un essai STP avec ce script, à mettre dans le dossier Projects\Win10XPE et transmettre la log WinSxS_Win10XPE.7z ensuite

 Check_WinSXS.script (8.68 kB - downloaded 53 times.)

I am not having issue - but figured I'd join the Test..
Win8.1 Host OS, 1809 x64 Source, WB, Ram Build, en-US

Thanks James for your Test 
It matches the plugin but, well, the plugin was made only for French 1809 Oct update 177663.107 with fr-FR +-hard coded
Small changes however in the plugin, updated in the previous post:
    Support windows 10 1809 sept update 17763.1 and 1809 Oct update 177663.107
    If the Language is fr-FR it checks for fr-FR files/folders otherwise it checks for en-US files/folders

Waiting for Ledu's log. I failed to understand why with the same ISO and package, he doesn't have the same result as me

Same source 17763.107, Comparison of Ledu's TargetlistFiles.txt file with mine (NOT OK=Missing file for Ledu)

Code: [Select]

(NOT OK) \Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.17763.107_fr-fr_111a069d984ed33d\comctl32.dll.mui
(OK) \Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.17763.1_fr-fr_46ad52e678931eec\comctl32.dll.mui
(NOT OK) \Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.17763.107_fr-fr_05f18b233b39c868\comctl32.dll.mui
(OK) \Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.17763.1_fr-fr_f07bb2ae335bef27\comctl32.dll.mui
//-
(NOT OK) \Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.17763.107_fr-fr_111a069d984ed33d.manifest
(OK) \Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_5.82.17763.1_fr-fr_46ad52e678931eec.manifest
(NOT OK) \Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.17763.107_fr-fr_05f18b233b39c868.manifest
(OK) \Windows\WinSxS\Manifests\x86_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.17763.1_fr-fr_f07bb2ae335bef27.manifest

hi ChrisR
i tested the script on 3 different pc
- Win7 32bit Host OS, 1809 x64 Source, WB, fr_fr
- Win7 64bit Host OS, 1809 x64 Source, WB, fr_fr
- Win10 1809 32bit Host OS, 1809 x64 Source, WB, fr_fr

Hi cretino,
Thanks, that's very helpful 
It seems that wimlib has a different behavior depending on the host system: windows 7 vs windows 10
For ex:

Code: [Select]

wimlib-imagex.exe extract "F:\sources\install.wim" 6 "\Windows\WinSxS\x86_microsoft.windows.c..-controls.resources_*_fr-FR_*" --dest-dir="%BaseDir%\Target" --no-acls --nullglob --preserve-dir-structure

It extracts 2 folders with windows 10 host (%ExitCode%=0)
It does NOT extract the 2 folders with windows 7 host x86/x64 (%ExitCode%=0)

With wimlib-imagex.exe extract @LISTFILE
It works on both Host OS. It was done like that with Win10XPE_2019-02-12.7z

I'll try to do some additional tests tomorrow on windows 7 before changing or see with Eric Bigger.
 

Cretino,
Would there be a problem related to Case Sensitive between Win7 and 10

I'll quickly prepare an addition to Check_WinSXS for testing on Win7 x86 or x64
Thank you in advance for your future feedback, really helpful 

Wimlib-Imagex 1.13 was released 11.23.2018
Wonder if the cause

hi ChrisR
I do not work tomorrow, so this nnight I'm trying windows login unloker while smoking ... 
and making new scrip x86

I updated the plugin in the previous post #Reply 49 by trying more method to see how they work on windows 7 x86 or x64.
while you smoke cretino, maybe you can (Re)test it.

@James
XPE use Wimlib-Imagex 1.13 x86 version only
Yep, it would be good to test also with 1.12 - 2017-07-29 wimlib-1.12.0-windows-i686-bin.zip with libwim-15.dll and wimlib-imagex.exe in tools

It is little late

hi ChrisR
test done ...

Yep, it would be good to test also with 1.12 - 2017-07-29 wimlib-1.12.0-windows-i686-bin.zip with libwim-15.dll and wimlib-imagex.exe in tools

give error: wimlib extract winsxs_addfiles_fr-fr.txt from instal.wim return:47
edit
was mu fault didnt see the hdd was disconected 
will reetested

edit
same log with wimlib-1.12, wimlib-1.11, wimlib-1.10

voila 2 log propre sans aucune modification

fait sous W10 1809 x64