He asked about how to do something, i explained how to do that something! Doing it or not is not my business!
It's like building a rocket trying to get to Mars but destroying moon at the same time. Thankfully in this case as soon as he runs sfc, imageres will be restored to defaults
Thankfully to who? People patches the OSes since the dawn of time. Feel free to eat only precooked meals, but stop discouraging people with more initiative than you.
i aint going to eat half cooked french fries and patching something well means no dism or sfc errors after applying patch dont you agree?
No I don't agree. Have you posted a more elegant alternative? NO If you know a more elegant way, I'm all ear. If not, the purposed solution is good enough and obviously safe enough and perhaps deadly easy to revert. Perhaps Win 11 is already stockpile of unwanted and harmful crap, "by design". If you want to be paranoid better to look at that rather than a tiny patch to a secondary file
You keep talking about sfc as you are the only one to know about it! Usually, warnings and recommendations comes after you give an answer, but i don't see yours! Also, many users are looking here to see if they can modify something. They are expecting detailed answers, certainly not detailed fears and delirious nightmares (destroy the moon?!). This is an elementary resources modification which is not even critical!
You know, with TI privileges you can overwrite the component folder's version of the file with your own. Then it passes SFC.
It's not exactly the correct description of what happens albeit the final point is correct. There aren't two files, there is one file hard-linked twice, if you delete one of the files, then copy a different version in its place get two different files, which take twice the space. But if you overwrite one of the harlinked version with a new file, you replace the actual file, so both the harlink will point to the same file as it did with the original one. That's what happens at least since 1709 (maybe 1703). Earlier Windows versions treated two hardlinked files as separate files. Hard links, symbolic links and alike are pretty well known in linux/unix world, but almost no one in MS world understand well what they are (including many MS insiders) albeit they are used extensively since vista.