abbodi1406's Batch Scripts Repo

The version is shown in the cmd window at the top.

 

Didn't help much after adding W10UI extract/temp direction to exclusion list. I experimented today with various settings and found disabling wimlib produced 500-800MB smaller file and this time I skipped defender platform update and integrated it separately. The image was booting perfectly. Next tried several copies of previous WIM folders with NTlite and WinToolkit and found it was NTLite's newest version from couple of weeks ago to current version causing boot loop after installing Windows 11 when I imported my working ntlite profile for 23H2 and 24H2. It seems the new step boot.wim step is causing issues.
I am using reg tweaks and profiles/ini files for Wintoolkit and NTlite from this github repo.
https://github.com/vasudev-gm/Registry-Tweaks-Scripts

 

@abbodi1406 @Enthousiast Any personal recommendations for NTLite alternative? WinToolkit is now dated and I simply removed few packages for test run last week and after removing FoD WebView Win 11 will not boot post install in Hyper V and stuck at constant boot loop.
Mainly I want to import .reg, adjust some explorer settings say make start menu in left, show full dialog in file copy, always show all icons in notification area etc..

 

@VDev, i never used ntlite nor chopped windows, and for pre-setting stuff i use MRP.

 

MRP? Macrium Reflect Pro edition or something else?

 

https://forums.mydigitallife.net/threads/multi-oem-retail-project-mrp-mk3.71555/

 

Hmm.. Not sure if I used it before when I used Vista during my high school days. Thanks

 

Setting UpdtBootFiles to 1 and using the new Windows installer gives a security violation error after the installation has copied over the files from the usb and restarts for the first time. The legacy installer works fine. I used 26100 and 26200.
The bootmgfw.efi is signed with the 2023 CA, maybe some other files aren't signed. I followed the guide by MSFT but it still wouldn't boot with secure boot enabled.

https://support.microsoft.com/en-us...23-24932-41a975df-beb2-40c1-99a3-b3ff139f832d

edit: might have found something, top is new installer, bottom is legacy

 

@abbodi1406

Hi!
Please tell me, the option "SkipApps =1" does not work in uup-converter when creating install.wim Windows 10?

 

From the "CustomAppsList.txt" file itself:

Code:

### This customization is supported only in builds 22563 and later.

 

I ran w10ui 10.50f against my 19041.1 base with these settings:

Code:

[W10UI-Configuration]
Target        =C:\DVD
Repo          =
DismRoot      =dism.exe

Net35         =1
Net35Source   =
Cleanup       =1
ResetBase     =1
LCUwinre      =0
WinRE         =1
LCUmsuExpand  =0
UpdtBootFiles =1
SkipEdge      =0
SkipWebView   =0
UseWimlib     =1
WimCreateTime =1

_CabDir       =C:\W10UI\W10UItemp
MountDir      =C:\W10UI\W10UImount
WinreMount    =C:\W10UI\W10UImountre

wim2esd       =1
wim2swm       =0
ISO           =0
ISODir        =
Delete_Source =0

AutoStart     =1

AddDrivers    =1
Drv_Source    =\Drivers

Code:

1/8: defender-dism-x64-mar21-2025.cab
2/8: Windows10.0-KB5011048-x64-ndp481base.cab [NetFx]
3/8: Windows10.0-KB5015684-x64-22h2-ep.cab [Enablement]
4/8: Windows10.0-KB5046905-x64.cab [Setup DU]
5/8: Windows10.0-KB5050199-x64.cab [SafeOS DU]
6/8: Windows10.0-KB5053643-x64.cab [LCU]
7/8: Windows10.0-KB5054682-x64.cab [SSU]
8/8: Windows10.0-KB5054978-x64-NDP481.cab [NetFx]

The usb I made afterwards with win10+ setup disk script. I shoved the usb in an Acer Nitro(11th/12th/13th gen intel platform)laptop with secure boot enabled. It failed to boot.

 

is replaced with W10UI_10.51

https://forums.mydigitallife.net/posts/1874191

 

@Enthousiast I already replaced the w10ui.cmd in my windows 11 updates folder, but this one affects the 25H2 EKB afaik. If it has any changes regarding the stupid secure boot certificates, that's good, I'll try it, I just acted based on the changelog.

 

Still best to test with the latest, but do with the info whatever you want.

 

changing ConvertConfig.ini Setting UpdtBootFiles to 1 creates the iso with new 2023 CA certificate?

 

Same exact iso but the validity of the CA cert is different.

edit:
Well I found the issue. That cert is revoked and is part of the updated dbx released by Microsoft here https://github.com/microsoft/secureboot_objects/releases
I reset the dbx to factory and now the new installer proceeds to fully set up windows to desktop with secure boot enabled.