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

Congratulations. 

Here my wim size results a bit smaller with "Win10_1809_English_x64"

Keeping short:
With all Slim options selected ,
All "Components-->Options" unselected -- "Components\Shell" selected -- Rest of "Components\*" patches unselected
All Drivers\* patches unselected
All Apps\* patches unselected


WinXShell - 157 MB
Explorer - 188 MB
Explorer + MMC 191 MB

 
*

I can not create a working iso with WimBuilderUI using "2-make_iso" button ("_ISO_ folder is not available" --> but it is...)
 but I can use boot.wim to create my own iso which I test the results,
  All boots fine here. 

ResEdit.exe can convert dll<=>rc.
Quick_Any2Ico.exe can reduce the ico by dimension,

and tested in commandline.

Which ico(s) can be replaced very small <1kb,
Which ico should keep <48x48 dimensions, needs be defined.
Once this is done, We can reduce resource dlls auto.

AFAIK, ONLY reduce next files could make big effects.

• imageres.dll(imageres.dll.mun)
• shell32.dll(shell32.dll.mun)
• ieframe.dll?

I can not create a working iso with WimBuilderUI using "2-make_iso" button ("_ISO_ folder is not available" --> but it is...)

add @echo on to  bin\_MakeBootISO.bat, try to see what's wrong.

Or tell me your path, I can try. ("D:\D e v" is tested  )

Here my wim size results a bit smaller with "Win10_1809_English_x64"

I tested 19H1, and also works. but as you said, I should add

Code: [Select]

@echo off
set X=X:
for /f %%i in ('dir /a-d /b "%X%\Windows\SystemResources"') do (
    if not exist "%X%\Windows\System32\%%~ni" (
        echo %%i
        del /f /a /q "%X%\Windows\System32\%%i"
    )
)

for /f %%i in ('dir /a-d /b "%X%\Windows\System32\%WB_PE_LANG%"') do (
    if not exist "%X%\Windows\System32\%%~ni" (
        echo %%i
        del /f /a /q "%X%\Windows\System32\%WB_PE_LANG%\%%i"
    )
)

With all Slim options selected ,
All "Components-->Options" unselected -- "Components\Shell" selected -- Rest of "Components\*" patches unselected
All Drivers\* patches unselected
All Apps\* patches unselected

Do you test the Preset selection? Did it work fine?

Hi slore,

ResEdit.exe --> I need to learn modify rc and recompile with modified rc (assuming ResEdit can recompile ... or other ways .... )
Quick_Any2Ico.exe --> Nice Tool    For a start only editing resources will be enough, not only for slim but also other resource related changes (eg. MediaPlayer pictures ;) )

See you next post...

v2019.04.09.e8ae8977 released:

* add Ultra-Slim option
(19H1,20H1 support than Preivew version)

* add preset for quick choosing the options, and patches.
(WimBuilder2\Projects\WIN10XPE\_Assets_\preset\*.js)

 WimBuilder2.part1.rar (6000 kB - downloaded 86 times.)
WimBuilder2.part2.rar (5,457 kb)

 WimBuilder2.part2.rar (5456.84 kB - downloaded 134 times.)

(part2 of v2019.04.09.e8ae8977)

Hi slore,

trouble is not path, It is about missing \

add @echo on to  bin\_MakeBootISO.bat, try to see what's wrong.

I feel you never tested with extracted to an empty folder,
or I am the only careful tester around and others only wait to see things get mature enough,
or local settings on your side changes default cmd etc. behaviour (get things work without \ ) ?

*
_MakeBootISO.bat :
I add missing \ to some lines and added \* to xcopy :

if exist "%WB_SRC_FOLDER%\boot" (
xcopy /E /Y "%WB_SRC_FOLDER%\boot\*" "%ISO_DIR%\boot\"
xcopy /E /Y "%WB_SRC_FOLDER%\efi\*" "%ISO_DIR%\efi\"
copy /y "%WB_SRC_FOLDER%\bootmgr" "%ISO_DIR%\"
copy /y "%WB_SRC_FOLDER%\bootmgr.efi" "%ISO_DIR%\"

Above works, well adding other xcopy parameters might be better, up to you:

if exist "%WB_SRC_FOLDER%\boot" (
xcopy /i /s /e /r /k /f /c /h /y "%WB_SRC_FOLDER%\boot\*" "%ISO_DIR%\boot\"
xcopy /i /s /e /r /k /f /c /h /y "%WB_SRC_FOLDER%\efi\*" "%ISO_DIR%\efi\"
copy /y "%WB_SRC_FOLDER%\bootmgr" "%ISO_DIR%\"
copy /y "%WB_SRC_FOLDER%\bootmgr.efi" "%ISO_DIR%\"

And now It works. 

(At last, I can create iso with WimBuilderUI  )


*
"2-make_iso" button
and
"create ISO after building" checkbox

( first delete .\_ISO_\ folder or \_ISO_\bootmgr file manually to get following result)

==>

error ui :"The _ISO_ folder is not available, ..." comes from html (checks \_ISO_\bootmgr file)
WimBuilderUI (html) creates .\_ISO\ folder but error screens comes up at first run or without \_ISO_\bootmgr file .

After clicking ok on "error ui" , _MakeBootISO.bat take the task and continue with success.

( I feel again \ trouble ---> \_ISO_\bootmgr )





***
Launch right of the box with text: "VBox.cmd testvm" does not work with available iso file.
"Test ISO after building with" checkbox does not start VirtualBox here
clicking inside "VBox.cmd testvm" box cause text disappear.

I feel instead of textbox with "VBox.cmd testvm" ,
 there should be selection boxes (like Explorer and WinXShell on \Shell patch) to select virtualization.
eg.
VirtualBox
HyperV

******
I feel default distribution with
 "Create ISO after building" default enabled
and
 "Test ISO after building with" default enabled with selected "VirtualBox"
    (if not found VirtualBox simply exits , if exists boots with VirtualBox)

will be better for new users... up to you...

********
I see you posted new packages when I create the current post,
 I will post anyway to feedback even fixed with other things.

I feel you never tested with extracted to an empty folder,

  I download the attachments and tested(empty folder, contain space in path) ...

or local settings on your side changes default cmd etc. behaviour (get things work without \ ) ?

I never change, but it works on my side. (OS difference, CMD again?)

"VBox.cmd testvm" is sample like "please input username", css is bad, not good font color on it...

change testvm to your VitrualBox's vitrual machine name, it should work.

there should be selection boxes

End user can add any cmds in test\ folder, and call it, like copy the wim to somewhere(USB device), so make it be input box.

HTML can easy to change to any form, but it is not matter of priority on my todo list. (NO body feedback on it before)

will be better for new users... up to you...

Different people have different default option ... so I leave it in auto_config.js .
Which default option is good, I have no idea.

Just change the default value in assets\default_config.js, change it is very easy, but which one is best is hard to decide.

(OS difference, CMD again?)

I use Win10x64 home enu at home with tr localized settings (which is %99 same with enu and with all passing years since DOS 5.0 same results with enu)

I mean your localized settings, I do not feel It is about OS.


eg.
%WB_SRC_FOLDER%boot
%WB_SRC_FOLDER%efi
is technically wrong but works on your side.
 something auto adds or ignores \ on your side.
  I feel localized settings on your side with CMD ? ignores missing \ but does not ignore missing \ here.

Test WimBuilderUI with an enu default virtual win machine with enu localized.
(ps: localized settings on cmd may still require restart when changed .... )

I believe, Since you are a very good coder, you did not miss adding \ even if it is ignored on your side
 but only with this case you missed.

(NO body feedback on it before)

sure.
Nobody feedback or ask to create projects or many features we add to projects here,
 even nobody feedback to create current forum ............... 





*
Another thing, just to share, up to you:

It is our mistake to use a variable like yours %ISO_DIR%
It should be something like %FinalDir%  .... ( I update on my side some months ago to %TargetFinalDir% )
I do not know what you call but I will use %TargetDir% in following demo:
( %TargetDir% where you delete add files which exists in final boot.wim )

This way:

%TargetDir%=.\_Factory_\target\WIN10XPE\mounted
(I assume this is the location where you delete add files)
%FinalDir%=.\_Factory_\target\WIN10XPE_Final
--->
\_Factory_\target\WIN10XPE_Final\sources\boot.wim
with other \Boot\ + \Efi\ files (like your current \_ISO_\ )

=====>
\_ISO_\ folder with only BOOTPE.iso


Advantages are:
+
you do not need to spend time to copy boot.wim from .\_Factory_\target\WIN10XPE\build\boot.wim to \_ISO\sources\
+
You with a patch or anyone with cmd can use same Final Folder (%FinalDir%) easily for usb for iso .... or any other thing.
+
...... (well some other nice advantages with other build type options ...... but keeping short for now)

ps: make a small Basic Test on my side to see what I mean.....

----  I am sure NO body feedback on such thing before, just an idea to share, up to you.

"VBox.cmd testvm" is sample like "please input username", css is bad, not good font color on it...

change testvm to your VitrualBox's vitrual machine name, it should work.

There is chain reaction of misunderstanding:

My mistake, I thought you were creating VirtualBox's virtual machine like I did.

there should be selection boxes

End user can add any cmds in test\ folder, and call it, like copy the wim to somewhere(USB device), so make it be input box.

Ok understood. I thought box was only to select VirtualMachine.

checkbox "Test ISO after building with" and box near to it creates such confusion ....

Now I understand checkbox, in reality do "last cmd file you like to execute" 

anyway, up to you ....

HTML can easy to change to any form, but it is not matter of priority on my todo list. (NO body feedback on it before)

chain reaction of misunderstanding. no need to.

will be better for new users... up to you...

Different people have different default option ... so I leave it in auto_config.js .
Which default option is good, I have no idea.

Just change the default value in assets\default_config.js, change it is very easy, but which one is best is hard to decide.

Sure. I only shared my ideas.

--->
Something missing with New option "Patch Preset:"

It always starts with default and will be confusing to new users on some areas...
(close WimBuilderUI and re open always starting with "Patch Preset:" Default ... )

Anyway, I can handle such things easily and I know where to look to change start setting,

I leave further to somebody else feedback on it in future. 

Thanks for all updates, WimBuilderUI looks nicer to me when I find time to test.

trouble is not path, It is about missing \

I know why "\" missed.

I select a Win10.ISO mounted drvie, like "H:\",
you select a folder. so there is no "\" in the end.

funny, I dealed with some people who don't use select button,
but manually input H:, I check whether or not the last is ":" then, and
and a "\" for that.

Should be if not "\" then add a "\" in the end.
I will fix it in next version.

I don't know why you need %FinalDir%.

.\_Factory_\target\WIN10XPE\mounted is %_WB_MNT_DIR% or short %X%,
when you want to delete add files in "X:\", just use:

%X% => boot.wim\                     => X:\              after winre.wim booted
%X_PF% => boot.wim\Program Files     => X:\Program Files after winre.wim booted
%X_WIN% => boot.wim\Windows          => same
%X_SYS% => boot.wim\Windows\System32 => same

anyone can add his own environment variables.
I just add what I used(Projects\WIN10XPE\prepare.bat, main.bat).

\_ISO_\ folder with only BOOTPE.iso

NO, the \_ISO_\ folder is actually \_ISO_TEMPLATE_\,
How the ISO structure will be, is depend on his hand.
(add PETools, or Linux,Windows Bootable stuff)


+

you do not need to spend time to copy boot.wim from .\_Factory_\target\WIN10XPE\build\boot.wim to \_ISO\sources\

I use Dism.exe command to mount the winre.wim than extract winre.wim to folder.
+less disk fragmentation.
+not spend time on delete those small/lots system files on next build.

I build PE in 30 sec~60sec, 50+ times a day.

+use prepare.bat to reduce wim before mounting by wimlib-imagex.exe.
  just mark flag in wim to [DELETE], not actually delete them(build\boot.wim changed).

dism /commit(build\boot.wim changed), than call wimlib-imagex.exe to create wim,
so I need copy orgin winre.wim again. on my SSD the first time is 2~3 secs, from second time, it is < 1 secs.
(>spend time to copy boot.wim)

You with a patch or anyone with cmd can use same Final Folder (%FinalDir%) easily for usb for iso .... or any other thing.

test\vbox.cmd, I need ISO, so I use %ISO_DIR%.
anyone want do other things than that, he should use his environment variable for better mean.

When you build, It output the export WB_ infomation you can use.

WB_ROOT=D:\d e v\WimBuilder2_0408\
WB_PROJECT_PATH=D:\d e v\WimBuilder2_0408\\Projects\WIN10XPE

WB_SRC_FOLDER=G:\
WB_SRC=G:\sources\install.wim

WB_PROJECT=WIN10XPE
WB_X_DRIVE=X:

with %WB_ROOT%, %WB_PROJECT%, you can access any path.

misunderstanding
confusion

missing tip, or bad English words, I will update it.

"Input last cmd file you like to execute"

Tooltips on it:
"like VBox.cmd <your vitualmachine name>, cmd files is in test\."

It always starts with default and will be confusing to new users on some areas...
(close WimBuilderUI and re open always starting with "Patch Preset:" Default ... )

This is unfinsh feature but good to release.
in WimBuilder2\Projects\WIN10XPE\_Assets_\config.js,
you can change the default preset.
for now, it is "auto", if exist "custom.js" then use it,
otherewise use "default.js".

The fininal image is:
+Pathes Page UI will select the preset you defined in config.js($patches_preset).

+Also, the list is load by your _Assets_\preset folder, not hard-code one.
like: full.js, net.js ...

+ [ ] set as default option on the right of the selectbox.

replace "var $patches_preset = 'XXXX'; " to the selected item.

But for now, I don't have much time on prefect it, so just:
WimBUilder_UI.hta

Code: [Select]

    <!-- Selectmenu -->
    <select id="patch_preset" width="300">
        <option selected="selected">default</option>
        <option>custom</option>
        <option>custom1</option>
        <option>custom2</option>
        <option>custom3</option>
        <option>custom4</option>
        <option>lite</option>
        <option>lite1</option>
        <option>lite2</option>
        <option>lite3</option>
        <option>lite4</option>
        <option>-</option>
    </select>

Maybe set "-" to be default is better for now?

I select a Win10.ISO mounted drvie, like "H:\",
you select a folder. so there is no "\" in the end.

I totally forgot that ....

Since 9 years or more I use Buttons for Provided folders and files to avoid such things ....

That is a good example to demonstrate the idea:

Sometimes it looks very nice and simple to put FileBox or FolderBox for the developer 
But It causes internal check each time FolderBox used ( check last \ etc.)

Putting "Provide File" or "Provide Folder" button at first looks not necessary,
But Passing time with no error from public proves It is better and simpler syntax compared to internal check for \ etc.

Public tests is a good social experience for the developers to see behaviors of end users and to create out of the box working stable solutions. 

I will fix it in next version.

*
Just to demonstrate similarity

%_WB_MNT_DIR% or %X% -------> %TargetDir%
%X_PF% ---------------------> %Target_Prog%
%X_WIN% --------------------> %Target_Win%
%X_SYS% --------------------> %Target_Sys%

%WB_ROOT% ------------------> %BaseDir%
%WB_PROJECT_PATH% ----------> %ProjectDir%
%WB_SRC_FOLDER%  -----------> %SourceDir%


%WB_SRC% -------------> not required for today
%WB_PROJECT%  --------> not used, when required mostly folder name used from %ProjectDir% ( %WB_PROJECT_PATH% )
%WB_X_DRIVE% --------> mostly not used, mostly %SystemDrive% prefered for plugins and when required hardcoded X: used for project special plugins.

*

NO, the \_ISO_\ folder is actually \_ISO_TEMPLATE_\,
How the ISO structure will be, is depend on his hand.
(add PETools, or Linux,Windows Bootable stuff)

Sure, I fully understand all logic behind, I came from the same path and we do very same with %TargetFinalDir% to add PETools or Linux etc....
 I only remind you, the same folder with added PETools or Linux and Windows Bootable stuff can be used
  to create not only iso but also bootable usb, bootable hdd, mmc etc.

Reminding Another advantage, This way no need 
copy /y "%Factory%\target\%WB_PROJECT%\build\boot.wim" "%ISO_DIR%\sources\boot.wim"

That is the reason I comment sharing experience, further up to you.

*

I use Dism.exe command to mount the winre.wim than extract winre.wim to folder.
+less disk fragmentation.
+not spend time on delete those small/lots system files on next build.

I build PE in 30 sec~60sec, 50+ times a day.

As I wrote before elsewhere you will always be fastest since using full cmd. 

I use RamDrive to also avoid disk fragmentation
and mostly build Basic PE between 1 and 2 minutes ...

I will be faster after
+I simplify Basic plugins on my side (which is not my design)
+Learning cmd more (19H1 and later, mun files and mui checks cause extra 1 minute without using For /F with my low cmd skills)

But whatever I do, you will always be fastest. 

+
using dism to mount wim or other similar options to mount things was always on my table for various reason (including avoid disk fragmentation )
 but requires too much time which I do not have for today. ( I do not have time to make 50 builds per day even with WimBuilderUI, maybe at summer time)
  Good to see you go on this path. 

*
about
> "Patch Preset:"

eg. When you change windows settings to show hidden files, you expect windows continue to show hidden files after restart or re login 
you do not expect windows to always start with "default" etc. settings. which does not show hidden files.

Anyway, I know It is complicated to provide "Patch Preset:" option on the developer side, we had posted about this subject earlier...

 I leave feedback from others in this case. Nothing critical to me, I am experienced enough now using WimBuilderUI.

*****
Overall, all comments about things,

I will fix it in next version.

To me Important update, thanks for fixing on next version. 

See You on next post...

*
About codebox your Reply 122
http://theoven.org/index.php?topic=2390.msg32865#msg32865

+

Code: [Select]

@echo off
set X=X:
for /f %%i in ('dir /a-d /b "%X%\Windows\SystemResources"') do (
    if not exist "%X%\Windows\System32\%%~ni" (
        echo %%i
        del /f /a /q "%X%\Windows\System32\%%i"
    )
)

I feel it should be something like:

Code: [Select]

@echo off
set X=X:
for /f %%i in ('dir /a-d /b "%X%\Windows\SystemResources"') do (
    if not exist "%X%\Windows\System32\%%~ni" (
        echo %%i
        del /f /a /q "%X%\Windows\SystemResources\%%i"
    )
)

?
But what about if some mun files are for some win apps under \Program Files\... not \System32\
eg. maybe paint ?

or maybe I am missing something ...

+

Code: [Select]

for /f %%i in ('dir /a-d /b "%X%\Windows\System32\%WB_PE_LANG%"') do (
    if not exist "%X%\Windows\System32\%%~ni" (
        echo %%i
        del /f /a /q "%X%\Windows\System32\%WB_PE_LANG%\%%i"
    )
)

Keep in mind to loop other %WB_PE_LANG% folders.

---->
For today, I do not feel good to delete mui or mun files if they do not exist on System32, I did not do such thing on my side yet.
Maybe good for the early beginning of the build (winre or bootwim first mount before adding things to clear files forgotten by ms !? ) but not at the end.... !

Just to clarify, what I did on the other topic for mui is very different. Lancelot Reply 48 http://theoven.org/index.php?topic=2669.msg32612#msg32612

And for mun files, I check System32 and add mun files if not exists. (without overwrite) I do not delete.

About  M & M codebox

fixed in v2019.04.09
https://github.com/slorelee/wimbuilder2/blob/0dc129ddde830b008629bc7f187211caa04dc5dd/Projects/WIN10XPE/last.bat

Code: [Select]

rem remove usless mui & mun files
set Check_SysWOW4=0
if "x%opt[support.wow64]%"=="xtrue" set Check_SysWOW4=1
if not exist "%X_WIN%\SystemResources" goto :END_DEL_MUN

for /f %%i in ('dir /a-d /b "%X_WIN%\SystemResources"') do (
    if not exist "%X_SYS%\%%~ni" (
        if %Check_SysWOW4% EQU 0 (
            call :DELEX "/f /a /q" "%X_WIN%\SystemResources\%%i" "Remove useless "
        ) else (
            if not exist "%X_WIN%\SysWOW4\%%~ni" (
                call :DELEX "/f /a /q" "%X_WIN%\SystemResources\%%i" "Remove useless "
            )
        )
    )
)
:END_DEL_MUN
rem ignore *.msc files
for /f %%i in ('dir /a-d /b "%X_SYS%\%WB_PE_LANG%\*.mui"') do (
    if not exist "%X_SYS%\%%~ni" (
        call :DELEX "/f /a /q" "%X_SYS%\%WB_PE_LANG%\%%i" "Remove useless "
    )
)

if %Check_SysWOW4% EQU 0 goto :END_DEL_MUI

for /f %%i in ('dir /a-d /b "%X_WIN%\SysWOW4\%WB_PE_LANG%\*.mui"') do (
    if not exist "%X_WIN%\SysWOW4\%%~ni" (
        del /f /a /q "%X_WIN%\SysWOW4\%WB_PE_LANG%\%%i" "Remove useless "
    )
)

if DLL is not exist, it is useless by design. for normal mode, it should be just ADD.
But ultraslim option, delete lots of system files,  I can check it when deleting, but I don't think it is nessasary.(no bad effort report)

?But what about if some mun files are for some win apps under \Program Files\... not \System32\

No 19H1 official released, I don't check it clearly(just make PE now).

Keep in mind to loop other %WB_PE_LANG% folders.

UltraSlim should forcily select (remove other lang mui files) option.

if DLL is not exist, it is useless by design. for normal mode, it should be just ADD.

I agree, that is also what I do.

+
I understand you did your codebox for slim ...... all written.... rest on your hands. 

*
I learn from your codebox ?
--> mun files can be only for SysWOW64 at same folder \SystemResources\ with System32 files.
theory eg.
System32\attrib.exe not exists
SysWOW64\attrib.exe exists
SysWOW64\attrib.exe use mun file at \SystemResources\

I guess to delete mun files for slim with wow64, you check both System32 AND SysWOW64 and delete mun files if not exists at both.

Just a theory following your codes, I can not find time to test things these days ....

Public tests is a good social experience for the developers to see behaviors of end users and to create out of the box working stable solutions.

For 19H1,20H1 already got feedback than RS5 tested.

* StartMenu reboot button will block.

StartIsBack needs to update to 2.8.4

* [known]Dism.exe can't work(Russian friend's PE is same).
needs set workgroup.

startnet.exe token 14 seconds, PECMD call is fine.
without PECMD, In startnet.cmd I try to use ChrisR's SetWG.exe.
it is OK, but it check lanmanstation service which is not necessary, I will feedback later.

* Services.msc got error(explorer.exe).

iframe.dll(12MB) -> mshtml.dll(22MB) -> Chakra.dll(7 MB) => needs JScript/HTA.
(I got solution now)

* devmgmt.msc can't work

wbem\WMI*.dll is required.


I will not update the WimBuilder2.part1,2.rar frequently ....

please use git pull or download from github if you got the same issues.

I will not update the WimBuilder2.part1,2.rar frequently ....

please use git pull or download from github if you got the same issues.

_MakeBootISO.bat --> memo : on your to do to fix.

Cosmetics: About (left bottom on WimBuilderUI ) --> links not working ( I simply copy paste nicely  only cosmetics )

*
Big Thanks for the updates on 19H1, 20H1. I follow your discoveries and mostly take notes, but I do not have time to join the adventure....
 I left future core updates to JFX and Bob.Omb 
  and slowly continue my own tasks when I can find some free time:
   - cmd (or another alternative, still checking around, I get sick of wb and etc.) and plugin related development.
   - clean up bad organizations on my side created before me ( similarity %ISO_Dir%  ) to get plugins to work on all projects easily.

***
Go WimBuilderUI Go 

v2019.04.18 updated:

fixed:Can't create ISO when using extracted folder than mounted drive
fixed:Perfect combination of Slim patch with other feature patches (Search, IME)
new:add 4GB, 8GB options for fbwf cache size
new:add .Net Framework feature
new:add system event sounds
new:add "Edit main.bat, Edit last.bat" contextmenu on patch node. (default open with notpead.exe, you can change the editor by _CustomFiles_\editor.cmd)


1/2  WimBuilder2.part1.rar (6000 kB - downloaded 63 times.)
2/2 WimBuilder2.part2.rar (5819.67 kB)

[ Specified attachment is not available ]

v2019.04.28.8a4aaaea updated:

Added: SnipingTool (Components - > Windows Accessories)
Added: Microsoft Wubi Input Method Option
Updated:set 4GB fbwf cache size with Windows 10 origin driver
Fixed: BitLocker unlock menu does not display problems
Fixed: Administrator cannot be switched when using Korean input method
Fixed: Korean/English toggle key can not be used
Fixed: 20H1 (10.0.18885) unable to switch Administrator account
Fixed: 20H1 Administrator account can not automatically create user profiles and load the user registry hive. (Thanks to yamingw  )
          fixed problems:can not rename folder, software incorrect Association and other issues

 WimBuilder2.part1.rar (6000 kB - downloaded 330 times.)
WimBuilder2.part2.rar (5612 kB)