WimBuilder2 - New Builder with Re:WIN10XPE project(~20H2 Supported)

Hello all,
Seeing a new wimbuilder, I'm eager to try it out.
Sadly, there is an issue running the script:

The path of the script is short, no spaces. I'm using a mounted 20H2 iso.
Later, there was a similar error in the wsh.js file.

What could be wrong?

Cheers. 

Hi, PE_tester,
What's the windows version?

Did you use the latest version WimBuilder2-Full.v2021-04-04?


Edit the fso.js, goto 23 line, add a  alert(parentdir) to see the parentdir path.

function get_subdirs(parentdir) {
    var arr = new Array();
    alert(parentdir);
    var folder = fso.GetFolder(parentdir);                     <---  here got the errror  Path not found, let us to see the path of parentdir.

Do not mix XPEPlugins with Plugins. 

I don't mix them. I just want to say some design on application update.

The easy way for wimbuilder is, a general patch which edits its ui only to add shortcut with an example shortcut syntax (2 lines with Desktop and StartMenu which most people ask) and a small instruction (opendir button) to put files to.
eg.
Customization\Apps\"Applications" Patch
having a button "_Custom_Files_(Program Files)" button
 and another "Edit Button" (probably not required at all)
   Under that button a black ui like Advanced menu
     having default shortcut example for desktop and startmenu maybe starting with rem giving example with Q-Dir_x64.exe (or any very small app, 7-zip already there  )
eg.
Click to "_Custom_Files_(Program Files)" button opening
...\x\Program Files\ folder

so during build XCopy...\X\Program Files\* to target and your patch runs shortcut syntax shown on patch ui

most portable apps will work out of box, which most people use, and easy to customize.
 I know it is easy with wimbuilder batches and syntax already available,
  But new users expect ui which we already talked at wimbuilder1 times,
   I am sure new users will jump to such a ui patch and you will get rid of requests pointing that patch ui.
    On my side I create Utils\"PC Packed (Plugin Creator Packed)" ago as a reult you do not see any question asking to add a simple portable app to build.

Sometimes we spend time to get things already available by providing an ui  ....

I prefer builder be simple. Why when people want to add a application, them need to add a plugin/patch for the application, for two options:
shortcut on desktop or startmenu.

Most Chinese PE, use a petools.cmd or something to detect the ?:\PETools\ folder, and auto create shortcut for them.
just put application in the PETools folder is fine.

For WimBuilder:
I show a patch about:

PEMaterial\
      Collection\
            --->  vendor/_PEMaterial_
                               Installers\
                               PortableApps\
                               Program Files\
                               PEStartup.bat


_Custom_Files button on UI, you can open the vendor/_PEMaterial_ folder, and add your applications.
Edit the PEStartup.bat to add only 2 lines for shorcut, all will be done.
No need to build, them can be copied to X:\(boot.wim), ISO\, U:\.

For v2021.04.04, the AppData/_PEMaterial_ be added.


WimBuilder2 can add a UI easily, but I don't want to spend time on it.


APP_Dism++.bat
APP_Everything.bat
APP_SumatraPDF.bat
APP_WinNTSetup.bat

Add aboe batch files is easiler than 4 sub folder,  4 main.html, 4 main.bat ...


Back to the name of _Cache_ path. For now, dism++, SumatraPDF or something in it.
They are not the core tools for PE, like PECMD, WinXShell, StartIsback(related on booting PE).
The latest version of them is fine, even some thing wrong in the latest version, It won't cause problem unless you use them in PE.
So the like a web resource cache.
StartIsBack, 7-Zip or something, they have their own folder in vendor/.

I'm not good at the naming stuff, make thing be simple, Downloads is fine on my side.
(Users\<username>\Downloads, \Documents, \Desktop)

About the naming, I have one new folder PEMaterial. I designed to add Tools, Drivers, wallpaper, startup scripts ...
Recent, I think it could be simple to be PEToolbox. For the compatibility, I don't change it.

Hi Slore,

Yes, it is the latest version WimBuilder2-Full.v2021-04-04.
I made the changes to the fso.js script and ran the script again.
Now there is an alert that says: Projects.

But after clicking OK, the same error returns, albeit now on line 24.
The project list is still empty, so it is not possible to choose a project nor build it.

The host OS is Windows 10 version 1809 LTSC.
Thank you very much for the help and assistance.

Cheers.

Yes, the 'Projects' is OK.

The get_subdirs() should return the 'WIN10XPE' to be the project.
(E:/Wimbuilder/Projects/WIN10XPE folder)

But on your enviroment, the fso.GetFolder('Projects')  failed.

Would you please to add a alert(wsh.CurrentDirectory); to see what is your work directory?

It should be 'E:\Wimbuilder'.


And could it be OK, if you change it to be:

var folder = fso.GetFolder('E:\\Wimbuilder\\' + parentdir);

Hi Slore,

Yes there is some progress.
First, "alert(wsh.CurrentDirectory);" also reported the same error: Path not found.
So the issue is with the work directory.
I have checked security settings and even moved the folder to a different drive, it reported the same error.

Then I changed the line to reflect:
var folder = fso.GetFolder('E:\\Wimbuilder\\' + parentdir);
as you suggested.
It works, now I can see the Win10XPE label.

However, there are more places in the script that need that line to be changed to explicit path name.
Will test and report back.

Cheers.

Hi slore,

Better I replay other things after you fix thing reported by PE_Tester,
 

+
Maybe this helps:
Ps: After first wimbuilder extraction to new fılder,
First things I always do is
1 select source
2 select project
3 click customize

To avoid similar things PE_Tester reported

I feel Wimbuilder do not have a fallback to default when selected project is empty
 which cause a chain reaction with script error.....
  Only an idea which may help....

Hi all,

Here is some feedback from testing today.
As said yesterday, it was needed to correct more path statements to explicit path names.
I recall making three changes, but the script still wouldn't complete a build.

Issues:
The Win10XPE project has several options, for example minimal build etc. It is not possible to view/choose/select those options.
The build with log button works, but the log only contains one single line, the first line.
In the build section, there is some progress shown, can we use that to troubleshoot?
(Since yesterday I have shortened the path even more and used a different drive)

W i m B u i l d e r - v2021.04.04.6cab797f
Check User Custom Files ...
[ ] - "D:\Wim\AppData\Projects\WIN10XPE\_CustomFiles_\ProductOptions.txt"
[ ] - "D:\Wim\AppData\Projects\WIN10XPE\_CustomFiles_\IE_Settings.bat"
[Found] - "D:\Wim\AppData\Projects\WIN10XPE\_CustomFiles_\_Prepare_.bat"
[Found] - "D:\Wim\AppData\Projects\WIN10XPE\_CustomFiles_\MyCustom\"
[Found] - "D:\Wim\AppData\Projects\WIN10XPE\_CustomFiles_\final.bat"
[ ] - "D:\Wim\AppData\Projects\WIN10XPE\_CustomFiles_\_CustomISO_.bat"
2021-04-19 21:50:41 - Building Start ...
[WIN10XPE] --- build information
WB_ARCH=x64
WB_BASE=winre.wim
WB_BASE_INDEX=2
WB_BASE_PATH=D:\Wim\_Factory_\target\WIN10XPE\winre.wim
WB_HOST_LANG=9226
WB_PROJECT=WIN10XPE
WB_PROJECT_PATH=D:\Wim\Projects\WIN10XPE
WB_ROOT=D:\Wim
WB_RUNAS_TI=1
WB_SKIP_UFR=1
WB_SKIP_URR=1
WB_SRC=H:\sources\install.wim
WB_SRC_FOLDER=H:
WB_SRC_INDEX=2
WB_STRAIGHT_MODE=1
WB_TMP_PATH=D:\Wim\_Factory_\tmp\WIN10XPE
WB_USER_PROJECT_PATH=D:\Wim\AppData\Projects\WIN10XPE
WB_VER_STR=2021.04.04.6cab797f
WB_WORKSPACE=.
WB_X_DRIVE=A:
BUILD_LOGNAME=20210419215041_Build[LOG]_WIN10XPE.log
BUILD_LOGTIME=20210419215041
Extracting file data: 0 MiB of 417 MiB (0%) done
..
Extracting file data: 417 MiB of 417 MiB (100%) done
Done extracting files.
PHRASE:Get WIM image INFO
Get WIM image's information failed.

Creating ISO...
The system cannot find the path specified.

OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility
Copyright (C) Microsoft, 1993-2012. All rights reserved.
Licensed only for producing Microsoft authorized content.
ERROR: Could not open boot sector file "_ISO_\boot\etfsboot.com"
Error 3: The system cannot find the path specified.
ISO Created -* _Factory_\BOOTPE.iso
make boot iso successfully.

 

After the process, no ISO has been build.
I hope this info can help find the issues.

Cheers.

The main problem is that THE hta can not get the workdirectory， maybe some IE settings related.
I will try to install ltsc 1809 to try.

The path is missing,  so lot of file reading and writing operation failed. The builder can not write your options.

Would you try to boot to the original boot.wim/winre.wim(Normal Window 10 version),

and type:
X:\>cd /d E:\Wim
E:\Wim>wimbuilder.cmd

wsh.currentdirectory is Microsoft's method,
It should return the working path.

Hi PE_tester,

I usually get this kind of error message when the virus defense (Bitdefender) blocks the mshta file.

Kind regards

Hi slore,

Nice work. Become more and more perfect.
Bitdefender says 32-bit wincmd.exe and WinXShell_x86.exe infected with Trojan.
I picked up the list of exceptions.

Sincerely

 hu-HU.js_files.7z (13.36 kB - downloaded 15 times.)