abbodi1406's Batch Scripts Repo

thanks Enthousiast
I just tested it.
1.afaik The previous exclusions in setupcomplete.cmd worked, but now whats changed is that "1-SppExtComObjPatcher will create exclusions in defender"

 

???
i've used your old ver kms_vl_all $oem$ folder to preactivate win 10 1709 many times in past, and it always successfully created exclusion in defender.
today i tried new ver 20 kms_vl_all, 1-SppExtComObjPatcher.cmd and it also successfully created exclusion in defender win 10 1709.

 

in 1-SppExtComObjPatcher.cmd there are these 2 lines for defender exclusion

Code:

WMIC /NAMESPACE:\\root\Microsoft\Windows\Defender PATH MSFT_MpPreference call Add ExclusionPath="%SystemRoot%\system32\SppExtComObjPatcher.exe" >nul 2>&1
WMIC /NAMESPACE:\\root\Microsoft\Windows\Defender PATH MSFT_MpPreference call Add ExclusionPath="%SystemRoot%\system32\SppExtComObjHook.dll" >nul 2>&1

these 2 line working fine in cmd when i ran them separately, i suppose simple cmd can also create exclusions !

 

just passing by, greeting to @abbodi1406 it's been a long time man

Code:

WDE = Windows Defender Exclusion

call :WDE add
call :WDE remove

:WDE
for %%a in (Patcher.exe, Hook.dll) do WMIC /NAMESPACE:\\root\Microsoft\Windows\Defender PATH MSFT_MpPreference call %1 ExclusionPath="%SystemRoot%\system32\SppExtComObj%%a" >nul 2>&1
exit /b

 

I've used v20 of the script & the defender exclusions have been added by setupcomplete.
Even with these 2 exclusions, if you perform a full scan with defender it still flags these files...

 

W10UI 4.5 : i suggest inserting the architecture in the filename of the generated iso file. Change statement 747 as follows :

Code:

set isofile=Win10_%isover%_%isodate%_%arch%.iso"

 

@abbodi1406 The OP still shows UUP>ISO v14 instead of v15

 

your add store to ltsb package is not listed here, pls add it and as well other work if they are not listed here, thanks.

 

Why add Store to LTSB?
I believe people install LTSB to actually avoid/get rid of Store and Metro/Modern apps?

 

metro apps can be easily uninstalled in home/pro.
but metro apps is not the only reason why people choose ltsb, they also choose it bcoz they dont have to deal with feature upgrade every six month and can continue use same version for long time with regular monthly updates.
the people who seek my help to install windows, i always prefer ltsb bcoz of 2nd reason.
metro apps arent bad, there are some good apps which worth to be used by every users. so ltsb with store is a perfect solution for me.

 

I tried making a multi-architecture ISO using the multi_arch_iso.cmd from the UUP>ISO script ver 15. My two ISOs were from Techbench and were the 1803 ISOs the 32bit (Win10_1803_English_x32.iso 3.3GB) and the 64bit (Win10_1803_English_x64.iso 4.6GB). These are the paths that I specified:

Code:

E:\Users\RMT\Downloads\1\Win10_1803_English_x32.iso
E:\Users\RMT\Downloads\1\Win10_1803_English_x64.iso

I get the following error:

Spoiler

I checked both ISOs and they are not both x64

Spoiler

Do you have any clue what I am doing wrong?

 

I followed your instruction and the script worked flawlessly. Yeah, the nomenclature that MS uses sometimes makes no sense. The x32 term in reference to architecture has always struck me as odd, but that MS for ya. I use at least one of your scripts in one form or other on a daily basis. Thank you for all you efforts here at MDL.

 

hi @abbodi1406 just wondering if there is any reason for setting scripts to asking manually run as admin, in kms_vl_all.why this cant be set to auto?

 

Hey Abbodi1406,
So a question comed up.
I want to integrade Microsoft-Windows-LanguageFeatures-Basic-fa-ir-Package-amd64.cab and Microsoft-Windows-LanguageFeatures-Fonts-Arab-Package-amd64.cab FODs when using your W10UI. If I copy them into \sources\sxs, and keep net35 as 1, will it work? Or does the script only integrade net35 and not the other CABs in that folder?
Thanks.