If you go to Features page, it is disabled to uncheck or it is disabled as unchecked or it its is disabled to uncheck in Components page?The resulting features indicate IE-11 has been disabled, in which the opposite is true.
How did you get NTLite to recognise IE11 install? I've integrated it just fine? For me, I see no option for IE11 but I do see IE8 as disabled. Do I need to install the cumulative update first (KB3148198). Not looking to remove it just disable.
On installed machine I can just disable it manually, that's fine but would be nice to pre disable.
Thanks
So IE11 cannot be disabled via features. IE8 is self disabled when IE11 installed. IE11 remains totally operational upon install.IE11 is update for IE8
the feature name (option) is inbox, and doesn't change
So IE11 cannot be disabled via features. IE8 is self disabled when IE11 installed. IE11 remains totally operational upon install.
In my case, IE installed fine, automatically IE8 became self disabled and I get no feature to switch off IE11.It does not, the files get replaced, but the feature will be the same: Internet-Explorer-Optional-amd64 or Internet-Explorer-Optional-x86
I presumed that IE is used as a framework, I presumed this because despite being disabled on previous machines you still get offered IE11 update and one of the early cumulative updates without wrappingMy question is why would you bother installing IE11 KB to replace IE8, if you didn't intend to enable that Feature? With the patch set frozen on normal W7 (non-Embedded or Server) releases, it's not like you need to care if WU suggests installing an IE update.
I was just wondering how the poster manages to get IE11 to show up in features under NTLite, for me that doesn't happen. When IE11 is installed, IE11 does not show up in features but I see that IE8 suddenly shows as disabled which ofcourse the latter is to be expected.When a Windows Feature is disabled, that means its component folders are present, but hidden in WinSxS, and none of the target files are hardlinked ("installed") or any of the registry keys added. Therefore in this state, it doesn't fully exist.
What you're thinking of is a different state where IE is installed, but doesn't auto-start or run at all. That has to be accomplished by a set of more involved reg keys to block IE's execution.
If any of your apps require the IE11 libraries then you have no choice but to install IE11, and leave the feature enabled. Unlike Edge, where the Legacy Components for IE11 are split into a separate package, this option doesn't exist for IE11 on W7.
I've heard that, the telemetry is apparently more quirky than even 10/11?abbodi's point is "inbox" Features or apps are marked as non-removable. You can't remove them after post-installation, and the offline image is the only chance you get to choose what happens. A lot of W7-era software is quirky, and you just have to live with it.
Yeah it's no hindrance, as said I will disable feature after OS install, just would have been convenient to be able to disable in NTLite as a preset, like we could do with IE8.
I just have misread something but I was under the impression that the poster was able to disable IE11 feature in NTLite
I have indeed yes, the image WIM has been unmounted and remounted a couple of times. For me, I still see IE8 under NTLite, which now shows as disabled since installing IE11. IE11 and it's IE April 2016 cumulative update are detected just fine under the updates tab aswell. Within the system post install, I can see it as you've shown, that's not the issue, I presumed that I should also be able to see IE11 via features tab within NTLite UI