NTLite removes stuff out of my Command?

[CodeBro]

As in the title, what are the "MicrosoftWindows.LKG" components like:

1. MicrosoftWindows.LKG.AccountService
2. MicrosoftWindows.LKG.IrisService
3. MicrosoftWindows.LKG.TwinSxS

The thing is, I actually did ask ChatGpt (paid version) this and he gave me a detailed description of what each does, however, I did find "IrisService" extreme trash (spytool) and removed it BUT unfortunately, NTLite did not only remove that component but ALL 3 of them which I found bad, because the other 2 seemed legit and "TwinSxS" even very much needed for windows internal component stuff, and I wanted to ask, is this intended or a bug in NTLite and yes i can assure you that I was very consious about what I removed and checked that I did not uncheck the others aswell, same goes also for 3 similar components called:

1. MicrosoftWindows.LKG.SpeechRuntime
2. MicrosoftWindows.LKG.DesktopSpotlight
3. MicrosoftWindows.LKG.RulesEngine

I did remove 1. which I found garbage but again, NTLite went ahead and removed the other 2 aswell.... Again are you guys sure this is by choice or a bug?

Please let me know!

Cheers!

 

[nuhi]

All 3 share the same payload package, will merge them into one, I was relying from DISM to remove individual ones, but it seems it did not then NTLite's engine kicked in and removed the underlying package as intended - but not informing the user of the pointless 3-component split.
There might be a way to save the split and not remove the non-App payload.

Microsoft is splitting them better each few months, individually should get their payloads soon.
For now keep all 3 of them if there are issues with it removed, I'll merge them or use NTLite to remove individual apps in the meantime.

As for what are they exactly... in short not sure, other than what's indicated by their titles.
It looked temporary to me during the Windows Preview versions, but they sticked.
The entire new App infrastructure is a mess, they reintroduced many existing and new components in the .CBS packages, now .LKG.
It probably has some logic to it, but in essence it's an obfuscation by introducing Copilot and other bloat quickly.
Tricks like if you disable Copilot, it breaks Explorer tabs and such.
Windows componentization again is going in the wrong direction.

 

[CodeBro]

All 3 share the same payload package, will merge them into one, I was relying from DISM to remove individual ones, but it seems it did not then NTLite's engine kicked in and removed the underlying package as intended - but not informing the user of the pointless 3-component split.
There might be a way to save the split and not remove the non-App payload.

Microsoft is splitting them better each few months, individually should get their payloads soon.
For now keep all 3 of them if there are issues with it removed, I'll merge them or use NTLite to remove individual apps in the meantime.

As for what are they exactly... in short not sure, other than what's indicated by their titles.
It looked temporary to me during the Windows Preview versions, but they sticked.
The entire new App infrastructure is a mess, they reintroduced many existing and new components in the .CBS packages, now .LKG.
It probably has some logic to it, but in essence it's an obfuscation by introducing Copilot and other bloat quickly.
Tricks like if you disable Copilot, it breaks Explorer tabs and such.
Windows componentization again is going in the wrong direction.

So you basically saying that they appear to be splitted but in fact its one big package and if you dare to remove a sub-package it will surely break and thus remove ALL of them at once since they 1 package anyway and ntlite thinks it wont work in that broken state so it then removes ALL of them, right?

Sadly I did remove it already and I wish I did not the file explorer tends to be unresponsive when you click on properties or try system related stuff with it....I still sadly do not fully understand how to use "Host refresh wizard" in order to restore stuff without going to far back....

 

[CodeBro]

Microsoft is splitting them better each few months, individually should get their payloads soon.

contradicts abit these lines:

Tricks like if you disable Copilot, it breaks Explorer tabs and such.
Windows componentization again is going in the wrong direction.

 

[tistou77]

The Copilot option (or component) is not directly linked to these LKGs, if i remember correctly
So you can remove these LKGs while keeping Copilot, without problem
I had tested it some time ago, but not recently

 

[CodeBro]

The Copilot option (or component) is not directly linked to these LKGs, if i remember correctly
So you can remove these LKGs while keeping Copilot, without problem
I had tested it some time ago, but not recently

I mean I do not want Copilot, I just want to keep the one with "RulesEngine" which is for managing tasks and scedules or group policies and such which sounds giga important but this IrisService can go...

 

[tistou77]

You can remove Copilot and keep RulesEngine, etc... (Client.Core component)
IrisService and others are also part of Client.Core, not possible to remove separately
Maybe possible in the future

 

[nuhi]

So you basically saying that they appear to be splitted but in fact its one big package and if you dare to remove a sub-package it will surely break and thus remove ALL of them at once since they 1 package anyway and ntlite thinks it wont work in that broken state so it then removes ALL of them, right?

Sadly I did remove it already and I wish I did not the file explorer tends to be unresponsive when you click on properties or try system related stuff with it....I still sadly do not fully understand how to use "Host refresh wizard" in order to restore stuff without going to far back....

Removing apps (as in sub-package) will be fine, if you don't need a particular app/component.

Let me know with a preset if you confirm that the non-responsive explorer is caused by it, haven't seen that one yet.

Microsoft is splitting them better each few months, individually should get their payloads soon.

contradicts abit these lines:

Tricks like if you disable Copilot, it breaks Explorer tabs and such.
Windows componentization again is going in the wrong direction.

They keep on improving it - latest Windows previews have that Copilot disabling breaking Explorer tabs fixed.
As for Windows componentization, the splitting of packages, is bad again with these mentioned LKG and CBS cluster of components as one package.

Over time I'll tackle and split these manually, thing is they keep changing them often, so I allow it to evolve to not waste time on a half-finished product.