[DISCUSSION] Windows 10 Enterprise/IoT Enterprise (N) LTSC 2021

hmm I think I discovered the powder lol, because this morning I installed the W10 IOT LTSC 2021 again just using the native Windows tools and my old brain seems to be 100%, everything working perfectly and it looks more like W7 than W10 thanks to group policies and my beloved PowerShell V7.2.6

EDIT: well after 3 days of this installation were enough for me to immediately return to the "old" W10 LTSC 2019 running faster than Elon Musk's rocket well at least in this version it also has several serious bugs it is possible to solve while in this "new" one version I got tired of searching here and there bah MSFT I'm furious

 

Its called the discovery of the hot water, here

 

^
yep

 

Code:

/Windows 10/Windows 10 Enterprise LTSC 2019/Windows 10 IoT Enterprise LTSC 2019/
 en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_4c97c86c.iso
 en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_a1aa819f.iso

What are the differences between these two isos?

 

HI everyone, i just wanted to say to all that actively support this forums tat this work you've done is just fantastic, i've been following this forums since a few years now. I just came here to say thanks to everyone that actively support this great and useful community. Could not hold it anymore.

I know he didn't want to learn , but in my case i would love too, if theres a possiblity. I was trying to trim the LTSC 2021 19044.1288 ISO using the MSMG but the process just fails to recognise it as valid image to work on.after extraction.

Kind regards;

E

 

Most Welcome my dear Friend & thanks a lot lot for your so kind words for our community . MSMG is a great tool but user must be clear cut in packages he wants to remove via dism option after toolkithelper finished its work on offline image.
i have done most in depth research of packages which are safe to be removed from any win10 build any sku excluding "Home (Core)" & it results in a great current installed BareBone OS with only 444 number of files inside servicing / packages .
all bloat removed | all system\inbox apps removed as well as very very less telemetry | i am saying very very less tele cuz theres no any way user can get rid of it 100% as "Product Policy" registry inside ProductOptions reg key is found protected wirth sppsvc which is a in depth part of win activation.

Edit the script i used to remove component packages offline as an example :

https://forums.mydigitallife.net/th...0h1-and-ltsc-2019.80038/page-100#post-1753985

but i doubt in msmg creating a new reg value defvis with data 2 & reg type Dword actualy does ?

 

(\_/ ) ^ (\_/) You all deserve the nicest words. Really!, it's just the truth.

Well you just hit it right on the spot, what i was looking for was the closest to a bloat-free and telem-free, LTSC Image as possible. with the objective of gaining significant performance on low spec sys , also reducing unnecessary storage clutter while retaining most compatibility and not breaking any useful functionallity be it entertaintment or work related.. And it sounds you've already achieved it.

In my case i think i'm at bare bones in the knowledge department. But i will try my best.

Kind Regards,

 

Thank You | Thanks a Lot Once Again .
Pl dont feel down via saying "In my case i think i'm at bare bones in the knowledge department" . you too can achieve more then my build .
the most influencing words i can say to you "IMPOSSIBLE = I M Possible" . Yes you can do that with your hard efforts.

Pl Stay Blessed & Be Happy Always

Edit : if somewhere you need my help on this pl don't hesistate to msg me in pvt . i will be most happy to help.

 

Making the impossible unimpossible

 

hmm does anyone here on the Forum know how to format any version of Windows 11, 10 or 8.1 x86 or x64 using Notepad.exe well I'll try to explain how I do it it seems complicated but it's a simple and quick process at first for those who are new to this type of operation maybe be embarrassed at first because the process is practically instantaneous so here we go: after booting from the pendrive it's the usual process: choose the country, region etc here the "serious joke" starts 1st) click shift+ F10 at this point instead of go directly to the command prompt to open Diskpart I do it this way as I have all the Diskpart script in my head I call Notepad.exe and when it opens I type all the information I got from MSFT itself and after finishing the operation I select all the script using control c and now I call Diskpart so I just type control v it's instant in the sequence it remains to follow the usual operations if anyone has anything to add or criticize I'm all ears
Note: if everyone already knows this type of installation I apologize to everyone but since the days of Windows 1.0 I swear I've never seen it until today...

 

You need to login to view this posts content.

 

Code:

echo Cleaning Disk 0
echo sel disk 0 >> %Windir%/Temp/EFI.txt
echo Clean >> %Windir%/Temp/EFI.txt
echo exit >> %Windir%/Temp/EFI.txt
diskpart /s "%Windir%/Temp/EFI.txt"

i do it this way via script from PE but not inside current installed OS.
Warning : Not recommended to those users who dont know what they are doing.

 

You need to login to view this posts content.

 

Personally I rarely use diskpart at all, the last time it was to set R/W a disk that was turned R/O by a disk error.

Other than that I just can't see the scenario where this can be useful.

If I am in the OS and I need to deploy a new new one I have a wide choice of tools, (too much to be mentioned), in the rare case where a full disk wipe/repartitioning is needed, I just boot with a linux distro and use fdisk (way safer and easier to use than diskpart), or I just start with something like strelec, where I have like 10 different partitioning SW.

btw knowing the syntax of diskpart is always a good thing.

 

I like lean and mean PEs, with as little second party tools as possible. So I know DiskPart syntax as well...

On the other hand, adding the standard Windows Disk Management console to PE is not *that* hard, it only needs a handful of registry setting and files from a full Windows install.wim, using a few small "build scripts" (reg export/ import, file export/ import) only takes a few seconds, specially when you use Wimlib-Imagex.

 

About diskpart run from wim (ram) vs live system
When run on online windows 10/11
It does have limitations, auto-assign letters
And don't want to format the partitions ??
Very weird behavior

Edit.
forget another bizarre behavior
sometimes using Clean & Convert GPT
it's creating an EFI partition. (not always)

 

Autoassign letters can be avoided, google or search the registry for the automount option, about formatting sincerely I have no idea, that's why I prefer the linux fdisk. Itd dows one one job and it does well.