The servicing bug is that disabling Client.CBS.AIX (Recall feature) triggers a failed installation of WindowsAppRuntime.CBS. You're using the free edition of NTLite, so the proper removal method (which fixes the 24H2 bug) is paywalled from you.
But hey, I never mentioned that the first time.
You did NOT say that.
If you think you did, it's waaay too long that you got waaay too comfortable in your way of telling things to people who know less than you, and you forgot how to tell things so that such people can actually understand what you say.
First of all, the main dish on that comment was your claim that I removed Microsoft.WindowsAppRuntime.CBS, which I did NOT.
And btw you had already claimed it in NTLite community for a previous failed clean install, and I had already told you that I did NOT and that it's a thing that I wouldn't remove. So much for listening to others, like you say that they should listen while you spread your wisdom.
Secondly, you said "
This is a similar bug to what happens when you run DISM /Disable-Feature on Recall", like if you were talking of something unrelated, and I automatically glossed over it as something unrelated.
And if it didn't even occur to you while writing about it that maybe I had indeed removed Recall, why do you blame me?
Which btw you would have known that I had removed Recall if you had a look at the uploaded txt here or uploaded preset in NTLite community where you are a mod. Just saying.
"
When you remove Recall with the DISM /Disable-Feature", or even better "
When you remove Recall with the DISM /Disable-Feature or with a software like NTLite" (considering that it was in the context) would have been more understandable for "less wise" people.
And something like "
Do you disable Copilot + Recall setting (Settings - Privacy) ?" like
@tistou77 asked, would have not made me gloss over it.
Also, asking "did you maybe" instead of claiming things, can have a surprisingly relaxing and opening effect on the people you're trying to help.
Finally, in that comment you said "
If you've disabled the NTLite compatibility protections for an image, then you're allowed to break many things on your own".
Now you say "
You're using the free edition of NTLite, so the proper removal method (which fixes the 24H2 bug) is paywalled from you".
It seems like you like to turn things so that it always seem like people f.ked up because they did something they shouldn't have.
Maybe tell Nuhi to put the damn Recall in the damn compatibility protection's list, when you're less busy slamming people who did NOT remove something which they (despite not being as "wise" as you) would have realized that it sounds like something that they should not remove (e.g. Microsoft.WindowsAppRuntime.CBS), and who are frantically trying to understand WTF went wrong.
Ffs, and I was even writing you something nice in the other post.
Still, I stick to what I was writing you there. But I'll write it there.
No, at this point it makes no sense, I'll just say it here: I do appreciate your commitment. You clearly are helping lot of people, and you helped me too in the NTLite community. I was and am grateful for it.
But there's a dark side to everything.
I'm not here to patronize you, just like I asked you not to patronize me.
But as you are committed to helping people, I'm just telling you that maybe if you stop taking for granted that they must have f.cked up because they removed something that they clearly shouldn't have, if you'd not put everybody in the same bag just because in your many years of helping people you saw lot of similar things, maybe you'd find yourself talking to them in a way which makes them feel like you're happy to help more than like you're happy to point at what they most probably almost certainly did wrong, and most probably, almost certainly this would make you better at what you already do pretty decently.
Take it or leave it.
And thanks :)
news.itsfoss.com
