Check Target System Files

ChrisR

Yes, it is wcmsvc which does not start and so wlansvc too

Wcmsvc,DependOnService RpcSs & NSI, i cheked NSI missed nsisvc.dll & nsisvc.dll.mui
i tested with this but same problem

Code: [Select]

RegWrite,HKLM,0x7,Tmp_System\ControlSet001\Services\nsi,DependOnService,rpcss,nsiproxy
RegWrite,HKLM,0x1,Tmp_System\ControlSet001\Services\nsi,Description,"@#$pSystemRoot#$p\system32\nsisvc.dll,-201"
RegWrite,HKLM,0x1,Tmp_System\ControlSet001\Services\nsi,DisplayName,"@#$pSystemRoot#$p\system32\nsisvc.dll,-200"
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsi,ErrorControl,1
RegWrite,HKLM,0x3,Tmp_System\ControlSet001\Services\nsi,FailureActions,80,51,01,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,00,01,00,00,00,C0,D4,01,00,01,00,00,00,E0,93,04,00,00,00,00,00,00,00,00,00
RegWrite,HKLM,0x2,Tmp_System\ControlSet001\Services\nsi,ImagePath,"#$psystemroot#$p\system32\svchost.exe -k LocalService -p"
RegWrite,HKLM,0x1,Tmp_System\ControlSet001\Services\nsi,ObjectName,"NT Authority\LocalService"
RegWrite,HKLM,0x7,Tmp_System\ControlSet001\Services\nsi,RequiredPrivileges,SeCreateGlobalPrivilege,SeImpersonatePrivilege
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsi,ServiceSidType,1
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsi,Start,2
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsi,SvcMemHardLimitInMB,10
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsi,SvcMemMidLimitInMB,6
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsi,SvcMemSoftLimitInMB,4
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsi,Type,32
RegWrite,HKLM,0x2,Tmp_System\ControlSet001\Services\nsi\Parameters,ServiceDll,#$psystemroot#$p\system32\nsisvc.dll
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsi\Parameters,ServiceDllUnloadOnStop,1
//
RegWrite,HKLM,0x1,Tmp_System\ControlSet001\Services\nsiproxy,Description,"@#$pSystemRoot#$p\system32\drivers\nsiproxy.sys,-1"
RegWrite,HKLM,0x1,Tmp_System\ControlSet001\Services\nsiproxy,DisplayName,"@#$pSystemRoot#$p\system32\drivers\nsiproxy.sys,-2"
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsiproxy,ErrorControl,1
RegWrite,HKLM,0x2,Tmp_System\ControlSet001\Services\nsiproxy,ImagePath,system32\drivers\nsiproxy.sys
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsiproxy,Start,1
RegWrite,HKLM,0x4,Tmp_System\ControlSet001\Services\nsiproxy,Type,1


[nsi-AddFiles]
\Windows\system32\drivers\nsiproxy.sys
\Windows\system32\nsisvc.dll
\Windows\System32\??-??\nsisvc.dll.mui

@cretino
nsisvc.dll(.mui) is not added in Network Addition, it is already included in winre.wim


@Slore

Projects/WIN10XPE/01-Components/IME/Ime_Common.bat

:Ime_Reg
if %VER[3]% GTR 18300 (
  call RegCopy %1\Microsoft\FuzzyDS
)

By taking your changes, thanks
I saw that WOW6432Node\Microsoft\FuzzyDS is not included in install.wim but are there once installed.
To get it at build time, I did it like that:

Code: [Select]

ShellExecute,Hide,cmd.exe,"/C Reg Copy #$qHKLM\Tmp_Software\Microsoft\FuzzyDS#$q #$qHKLM\Tmp_Software\WOW6432Node\Microsoft\FuzzyDS#$q /S /F"

By taking your changes, thanks
I saw that WOW6432Node\Microsoft\FuzzyDS is not included in install.wim but are there once installed.
To get it at build time, I did it like that:

Code: [Select]

ShellExecute,Hide,cmd.exe,"/C Reg Copy #$qHKLM\Tmp_Software\Microsoft\FuzzyDS#$q #$qHKLM\Tmp_Software\WOW6432Node\Microsoft\FuzzyDS#$q /S /F"

If there is no FuzzyDS in WOW6432Node, then needn't copy them from Tmp_Software\Microsoft.
I tested IME in 32 bit APPs, it works.

By the way,
For the latest 19H1,20H1 version, it needs more registy items.
IME works with full SOFTWARE only now(WimBuilder v2019.03.31).
(Edited: Confirmed Software\Microsoft\Input is required)

And the candidate words bar is changed to be MetroApp,
so you can't select the words, needs type a phrase for inputing words you want,
otherwise the first candidate word will be inputted.

I have to seperate the IME indicator, and add 3rd part Input Method software.

Thanks for all infos Slore, I am unable to play with IME Chinese or Korean
It will become complicated in PE if it becomes a metro app...
I will continue to follow the ways chosen by the good Chinese or Korean guys 

Ran CheckSysFiles and get an error that CheckSysFiles.exe is not able to be extracted.

Any ideas why not? I made folder writeable and took ownership and still no go.

Run - Processing section: [CreateTargetSysFile] From file: [%BaseDir%\Projects\Win10XPE\Features\CheckSysFiles.script]
                   [Success] IF - Directory exists: [%BaseDir%\Target\Windows\System32] evaluated string: [If,ExistDir,%GTarget_Sys%,ShellExecute,Hide,cmd.exe,"/D /C Dir /A:-D /B "%GTarget_Sys%\*.*" >> "%TargetSys32File%"",%TempFolder%]
                   [Success] ShellExecute: [Hide] using: [cmd.exe] with parameters: [/D /C Dir /A:-D /B "%BaseDir%\Target\Windows\System32\*.*" >> "%BaseDir%\Temp\CheckSysFiles\TargetSys32File.txt"]
                         [Success] IF - File exists: [%BaseDir%\Temp\CheckSysFiles\TargetSys32File.txt] evaluated string: [If,ExistFile,%TargetSys32File%,Begin]
                         [Success] FileCopy - Copied [%BaseDir%\Temp\CheckSysFiles\TargetSys32File.txt] to: [%BaseDir%\Temp\CheckSysFiles\TargetSysFile.txt]
                               [Success] IF - Directory exists: [%BaseDir%\Target\Windows\SysWOW64] evaluated string: [If,ExistDir,%GTarget_Win%\SysWOW64,Begin]
                               [Success] ShellExecute: [Hide] using: [cmd.exe] with parameters: [/D /C Dir /A:-D /B "%BaseDir%\Target\Windows\SysWOW64\*.*" >> "%BaseDir%\Temp\CheckSysFiles\TargetSys64File.txt"]
                               [Success] ShellExecute: [Hide] using: [cmd.exe] with parameters: [/D /C Dir /A:-D /B "%BaseDir%\Target\Windows\SysWOW64\*.*" >> "%BaseDir%\Temp\CheckSysFiles\TargetSysFile.txt"]
                         [Success] [End]
                   [Success] [End]
                         [Ignore] ELSE - [Begin]
                               [Skipped] [If,ExistDir,%GTarget_Win%\SysWOW64,Begin]
                               [Skipped] [ShellExecute,Hide,cmd.exe,"/D /C Dir /A:-D /B #$q%GTarget_Win%\SysWOW64\*.*#$q >> #$q%TargetSys64File%#$q",%TempFolder%]
                               [Skipped] [ShellExecute,Hide,cmd.exe,"/D /C Dir /A:-D /B #$q%GTarget_Win%\SysWOW64\*.*#$q >> #$q%TargetSysFile%#$q",%TempFolder%]
                         [Ignore] [End]
                         [Skipped] [Else,FileCreateBlank,%TargetSysFile%]
                   [Ignore] [End]
             Run - Processed section [CreateTargetSysFile] in file: [%BaseDir%\Projects\Win10XPE\Features\CheckSysFiles.script]
             [Info] [//--]
             [Success] Retrieve - Sucessfully retrieved the file size from: [%BaseDir%\Temp\CheckSysFiles\TargetSysFile.txt] to variable: [%TargetSysFileSize%] with result: [26621]
                   [Success] IF - [26621] is bigger than

• evaluated string: [If,%TargetSysFileSize%,Bigger,0,Begin]

[Success] IF - File does not exist: [%BaseDir%\Temp\CheckSysFiles\CheckSysFiles.exe] evaluated string: [If,Not,ExistFile,%TempFolder%\%ProgramEXE%,ExtractFile,%ScriptFile%,%HostOSArch%,%ProgramEXE%,%TempFolder%]
                  [Failed] ExtractFile - Failed to expand file: [CheckSysFiles.exe] to: [%BaseDir%\Temp\CheckSysFiles]
                  [Warning] Halt
             Exec - Processed section [CheckSysFiles] in file: [%BaseDir%\Projects\Win10XPE\Features\CheckSysFiles.script]

well clearly the script exists > [%BaseDir%\Projects\Win10XPE\Features\CheckSysFiles.script]
It is trying to extract the file to >  [%BaseDir%\Temp\CheckSysFiles]

Either the script is corrupt
or the program.exe is being blocked (by A/V software ??)

the BaseDir - should be a simple path > C:\win10xpe\temp or D:\win10xpe\temp

well clearly the script exists > [%BaseDir%\Projects\Win10XPE\Features\CheckSysFiles.script]
It is trying to extract the file to >  [%BaseDir%\Temp\CheckSysFiles]

Either the script is corrupt
or the program.exe is being blocked (by A/V software ??)

the BaseDir - should be a simple path > C:\win10xpe\temp or D:\win10xpe\temp

Turned out the %HostOSArch% is returning x1 instead of x86 or x64 so it did not know which CheckSysFiles to extract, Created a %OS%=x64 and it extracted the file fine and gave me a AddFiles list.

List of files in Win10 1909 Pro (18362.418)

Code: [Select]

; Win10XPE: Missing Resources Files. Check Mui=True - Check Mun=True - Windows 10.0.18362.418

ExtractSectionFiles,%ScriptFile%,Win10XPE_AddFiles

[Win10XPE_AddFiles]
\Windows\System32\en-US\appinfo.dll.mui
\Windows\System32\en-US\AppResolver.dll.mui
\Windows\System32\en-US\avifil32.dll.mui
\Windows\System32\en-US\batmeter.dll.mui
\Windows\System32\en-US\bdesvc.dll.mui
\Windows\System32\en-US\bdeunlock.exe.mui
\Windows\System32\en-US\cacls.exe.mui
\Windows\System32\en-US\cdp.dll.mui
\Windows\System32\en-US\choice.exe.mui
\Windows\System32\en-US\clip.exe.mui
\Windows\System32\en-US\Clipc.dll.mui
\Windows\System32\en-US\comp.exe.mui
\Windows\System32\en-US\compmgmt.msc
\Windows\System32\en-US\CompMgmtLauncher.exe.mui
\Windows\System32\en-US\ctfmon.exe.mui
\Windows\System32\en-US\DDORes.dll.mui
\Windows\System32\en-US\desk.cpl.mui
\Windows\System32\en-US\DeviceCenter.dll.mui
\Windows\System32\en-US\DeviceProperties.exe.mui
\Windows\System32\en-US\DeviceSetupManager.dll.mui
\Windows\System32\en-US\DeviceSetupManagerApi.dll.mui
\Windows\System32\en-US\DeviceSetupStatusProvider.dll.mui
\Windows\System32\en-US\devmgmt.msc
\Windows\System32\en-US\devmgr.dll.mui
\Windows\System32\en-US\diskmgmt.msc
\Windows\System32\en-US\Display.dll.mui
\Windows\System32\en-US\dmdskres.dll.mui
\Windows\System32\en-US\dmdskres2.dll.mui
\Windows\System32\en-US\dmutil.dll.mui
\Windows\System32\en-US\dsreg.dll.mui
\Windows\System32\en-US\dtsh.dll.mui
\Windows\System32\en-US\dwm.exe.mui
\Windows\System32\en-US\dwmcore.dll.mui
\Windows\System32\en-US\dwminit.dll.mui
\Windows\System32\en-US\dwmredir.dll.mui
\Windows\System32\en-US\elscore.dll.mui
\Windows\System32\en-US\fc.exe.mui
\Windows\System32\en-US\findstr.exe.mui
\Windows\System32\en-US\fsmgmt.msc
\Windows\System32\en-US\fvenotify.exe.mui
\Windows\System32\en-US\hdwwiz.cpl.mui
\Windows\System32\en-US\hdwwiz.exe.mui
\Windows\System32\en-US\help.exe.mui
\Windows\System32\en-US\hotplug.dll.mui
\Windows\System32\en-US\imageres.dll.mui
\Windows\System32\en-US\InputSwitch.dll.mui
\Windows\System32\en-US\intl.cpl.mui
\Windows\System32\en-US\kdcpw.dll.mui
\Windows\System32\en-US\label.exe.mui
\Windows\System32\en-US\main.cpl.mui
\Windows\System32\en-US\mblctr.exe.mui
\Windows\System32\en-US\mmc.exe.mui
\Windows\System32\en-US\mmcbase.dll.mui
\Windows\System32\en-US\mmcndmgr.dll.mui
\Windows\System32\en-US\mmcshext.dll.mui
\Windows\System32\en-US\MsCtfMonitor.dll.mui
\Windows\System32\en-US\msinfo32.exe.mui
\Windows\System32\en-US\mssph.dll.mui
\Windows\System32\en-US\mssrch.dll.mui
\Windows\System32\en-US\mssvp.dll.mui
\Windows\System32\en-US\msutb.dll.mui
\Windows\System32\en-US\mycomput.dll.mui
\Windows\System32\en-US\ncsi.dll.mui
\Windows\System32\en-US\netplwiz.dll.mui
\Windows\System32\en-US\Netplwiz.exe.mui
\Windows\System32\en-US\NetworkExplorer.dll.mui
\Windows\System32\en-US\objsel.dll.mui
\Windows\System32\en-US\pdh.dll.mui
\Windows\System32\en-US\powercfg.cpl.mui
\Windows\System32\en-US\powercpl.dll.mui
\Windows\System32\en-US\provsvc.dll.mui
\Windows\System32\en-US\ProximityCommon.dll.mui
\Windows\System32\en-US\Query.dll.mui
\Windows\System32\en-US\query.exe.mui
\Windows\System32\en-US\rshx32.dll.mui
\Windows\System32\en-US\sc.exe.mui
\Windows\System32\en-US\searchfolder.dll.mui
\Windows\System32\en-US\SearchIndexer.exe.mui
\Windows\System32\en-US\sendmail.dll.mui
\Windows\System32\en-US\services.msc
\Windows\System32\en-US\SettingSyncCore.dll.mui
\Windows\System32\en-US\setx.exe.mui
\Windows\System32\en-US\shsvcs.dll.mui
\Windows\System32\en-US\shutdown.exe.mui
\Windows\System32\en-US\sort.exe.mui
\Windows\System32\en-US\srchadmin.dll.mui
\Windows\System32\en-US\srpapi.dll.mui
\Windows\System32\en-US\StartTileData.dll.mui
\Windows\System32\en-US\sti.dll.mui
\Windows\System32\en-US\stobject.dll.mui
\Windows\System32\en-US\StorageContextHandler.dll.mui
\Windows\System32\en-US\sysdm.cpl.mui
\Windows\System32\en-US\systemcpl.dll.mui
\Windows\System32\en-US\SystemPropertiesAdvanced.exe.mui
\Windows\System32\en-US\SystemPropertiesComputerName.exe.mui
\Windows\System32\en-US\SystemPropertiesHardware.exe.mui
\Windows\System32\en-US\SystemPropertiesPerformance.exe.mui
\Windows\System32\en-US\SystemPropertiesRemote.exe.mui
\Windows\System32\en-US\taskkill.exe.mui
\Windows\System32\en-US\themecpl.dll.mui
\Windows\System32\en-US\themeservice.dll.mui
\Windows\System32\en-US\themeui.dll.mui
\Windows\System32\en-US\timedate.cpl.mui
\Windows\System32\en-US\tquery.dll.mui
\Windows\System32\en-US\twext.dll.mui
\Windows\System32\en-US\twinui.appcore.dll.mui
\Windows\System32\en-US\twinui.dll.mui
\Windows\System32\en-US\twinui.pcshell.dll.mui
\Windows\System32\en-US\ubpm.dll.mui
\Windows\System32\en-US\uDWM.dll.mui
\Windows\System32\en-US\UIRibbon.dll.mui
\Windows\System32\en-US\umpoext.dll.mui
\Windows\System32\en-US\wdi.dll.mui
\Windows\System32\en-US\Windows.Gaming.Input.dll.mui
\Windows\System32\en-US\windows.internal.shell.broker.dll.mui
\Windows\System32\en-US\Windows.StateRepository.dll.mui
\Windows\System32\en-US\Windows.UI.Immersive.dll.mui
\Windows\System32\en-US\winver.exe.mui
\Windows\System32\en-US\WorkFoldersShell.Dll.mui
\Windows\System32\en-US\wsepno.dll.mui
\Windows\System32\en-US\wshext.dll.mui
\Windows\System32\en-US\zipfldr.dll.mui
\Windows\SysWOW64\en-US\adsldpc.dll.mui
\Windows\SysWOW64\en-US\apphelp.dll.mui
\Windows\SysWOW64\en-US\avifil32.dll.mui
\Windows\SysWOW64\en-US\comctl32.dll.mui
\Windows\SysWOW64\en-US\fwpuclnt.dll.mui
\Windows\SysWOW64\en-US\gpapi.dll.mui
\Windows\SysWOW64\en-US\iertutil.dll.mui
\Windows\SysWOW64\en-US\msvfw32.dll.mui
\Windows\SysWOW64\en-US\msxml3r.dll.mui
\Windows\SysWOW64\en-US\msxml6r.dll.mui
\Windows\SysWOW64\en-US\ntdll.dll.mui
\Windows\SysWOW64\en-US\poqexec.exe.mui
\Windows\SysWOW64\en-US\reg.exe.mui
\Windows\SysWOW64\en-US\rtutils.dll.mui
\Windows\SysWOW64\en-US\shellstyle.dll.mui
\Windows\SysWOW64\en-US\slc.dll.mui
\Windows\SysWOW64\en-US\svchost.exe.mui
\Windows\SysWOW64\en-US\sxs.dll.mui
\Windows\SysWOW64\en-US\twinapi.dll.mui
\Windows\SysWOW64\en-US\urlmon.dll.mui
\Windows\SysWOW64\en-US\user32.dll.mui
\Windows\SysWOW64\en-US\wimgapi.dll.mui
\Windows\SysWOW64\en-US\wldap32.dll.mui
\Windows\SystemResources\batmeter.dll.mun
\Windows\SystemResources\DDORes.dll.mun
\Windows\SystemResources\DeviceCenter.dll.mun
\Windows\SystemResources\dmdskres.dll.mun
\Windows\SystemResources\dwmcore.dll.mun
\Windows\SystemResources\imageres.dll.mun
\Windows\SystemResources\intl.cpl.mun
\Windows\SystemResources\main.cpl.mun
\Windows\SystemResources\mmcbase.dll.mun
\Windows\SystemResources\mmcndmgr.dll.mun
\Windows\SystemResources\mssvp.dll.mun
\Windows\SystemResources\msutb.dll.mun
\Windows\SystemResources\mycomput.dll.mun
\Windows\SystemResources\networkexplorer.dll.mun
\Windows\SystemResources\powercpl.dll.mun
\Windows\SystemResources\SearchIndexer.exe.mun
\Windows\SystemResources\shsvcs.dll.mun
\Windows\SystemResources\srchadmin.dll.mun
\Windows\SystemResources\stobject.dll.mun
\Windows\SystemResources\sysdm.cpl.mun
\Windows\SystemResources\systemcpl.dll.mun
\Windows\SystemResources\themecpl.dll.mun
\Windows\SystemResources\themeui.dll.mun
\Windows\SystemResources\timedate.cpl.mun
\Windows\SystemResources\tquery.dll.mun
\Windows\SystemResources\twinui.appcore.dll.mun
\Windows\SystemResources\twinui.dll.mun
\Windows\SystemResources\Windows.UI.Immersive.dll.mun
\Windows\SystemResources\zipfldr.dll.mun

Code: [Select]

Turned out the %HostOSArch% is returning x1 instead of x86 or x64 so it did not know which CheckSysFiles to extract

Just a little info..
The HostOSArch is set to x86 By Default in Script.Project
Once the "Source" is selected the %HostOSArch% is actually retrieved from the Host OS

The %OS% variable is pulled from the "Source" Media - which would be (%OS%=Win10) as XPE only supports Windows 10
So not understanding your use of that %OS% variable

If you boot into a different Arch OS and run XPE - you must "Reset" Your Build to pull proper HostOSArch

Code: [Select]

Turned out the %HostOSArch% is returning x1 instead of x86 or x64 so it did not know which CheckSysFiles to extract

Just a little info..
The HostOSArch is set to x86 By Default in Script.Project
Once the "Source" is selected the %HostOSArch% is actually retrieved from the Host OS

The %OS% variable is pulled from the "Source" Media - which would be (%OS%=Win10) as XPE only supports Windows 10
So not understanding your use of that %OS% variable

If you boot into a different Arch OS and run XPE - you must "Reset" Your Build to pull proper HostOSArch

Ok that adds some confusion then as when I looked at the log in html mode it shows HostOSArch is (x1) so if (x1) denotes x64 OS then why wouldn't it extract checksysfiles.exe? When I changed %HostOSArch% to %OS% and added a variable %OS% in the script equaling x64 then it extracted fine.

Have not changed the OS or ran this on a different system, Always the same.

not sure why you get x1 as the result...
x86 is the default result and that result will change to x64 if true

what you using for Builder and what OS is your host..

The %PROCESSOR_ARCHITECTURE% variable is gathered from your Host and the results are written as %HostOSArch%

not sure why you get x1 as the result...
x86 is the default result and that result will change to x64 if true

Not sure either but here is the image of what is shown in the log.

%ProcessorType% shows 8664

Running the latest Win10XPE downloaded here, Win10 1909 pro x64
AMD system

HostOSArch.cmd

Code: [Select]

@ echo off
If %PROCESSOR_ARCHITECTURE%== x86 (If Not Defined PROCESSOR_ARCHITEW6432 Echo 86)
echo 64
pause >nul

Results in ???

HostOSArch.cmd

Code: [Select]

@ echo off
If %PROCESSOR_ARCHITECTURE%== x86 (If Not Defined PROCESSOR_ARCHITEW6432 Echo 86)
echo 64
pause >nul

Results in ???

64

well that is the exact method we use to populate %HostOSArch% variable...
so not sure why prior results of X1 instead of x64

well that is the exact method we use to populate %HostOSArch% variable...
so not sure why prior results of X1 instead of x64

Not sure either and it even shows x64 in script.project file after running.