Remove Internet Explorer without breaking the MMC Extended View

[francis11]

francis11
I don't use any 3rd party cleaning tool like that. Only use NTLite to make Win10 as blot free as possible with all the optional analytical data sending option stopped as per my preference. After removing IE11, I didn't notice anything.

The only issue that I (still) have is this, while opening the group policy editor, I got these error pop-ups (4 times)

View attachment 4456View attachment 4457View attachment 4458View attachment 4459

While one is related to the defender as it says, no idea about the other one. & yes, I did remove defender as well and earlier also get such error messages while opening GPE. IDK why this error appear & why it is still not fixed by nuhi (if anything can be done from his side).

Back in June 2020 I posted about this here as an individual OP, but it's still not fixed yet it seems.

Hi
I see this before in another context, when opening GPO.
Keep and protect these .admx files (same names mentioned in popup) from your original install iso. Seems related to ApplicationGuard i tried remove before too (HVSI) keeping Defender. Then GPO should open without error popups.
Not a NTL issue as i see it. Why keep the related .admx files from what's removed!?! Same you've removed IE and the related IE .admx files gets removed too.

 

[francis11]

Try protect the related .admx templates, when removing Defender/ Systemguard, in Compatibility right window with the following lines (Yellowed out):
\Windows\PolicyDefinitions\AppHVSI.admx
\Windows\PolicyDefinitions\WindowsDefender.admx
\Windows\PolicyDefinitions\WindowsDefenderSecurityCenter.admx

​

 

[SM03]

Try protect the related .admx templates, when removing Defender/ Systemguard, in Compatibility right window with the following lines (Yellowed out):
\Windows\PolicyDefinitions\AppHVSI.admx
\Windows\PolicyDefinitions\WindowsDefender.admx
\Windows\PolicyDefinitions\WindowsDefenderSecurityCenter.admx
View attachment 4460

​

well, thanks for the heads up, I'll try this in my next build & revert (update) here.

 

[Windows 10 User]

well, thanks for the heads up, I'll try this in my next build & revert (update) here.

I was also having this problem until running NTLite's Remove Reinstalls feature.

 

[AeonX]

by saying this, do you mean that I don't have to remove this existing IE11 package from the ISO manually while modding the ISO to remove IE11 fully?

Sorry for the delay but yes you are correct.

In version 1909 after using my preset with NTLite doing the way I described I get this:

Spoiler

 

[SM03]

Sorry for the delay but yes you are correct.

In version 1909 after using my preset with NTLite doing the way I described I get this:

Spoiler

View attachment 4491

AeonX yes, I tried that by myself earlier, after I posted that question here and before you commented here today, and the result is the same as you wrote today, still, thanks for confirming.

 

[SM03]

well, thanks for the heads up, I'll try this in my next build & revert (update) here.

Okay, Update

francis11

Last week, I made the 20H2 ISO 19042.804 by NTL with the process you suggested i.e. adding those four ADMX files to the exclusion list from compatibility settings and installed the OS via that ISO. After a fresh installation, open GPE, no error pop-up

Now, recently, after I upgraded to the latest 21H1 via the 21H2 EP KB5000736 & with the latest (Insider/beta) LCU KB4601382 [19041.844.1.7], I am now on 19043.844 (from 19042.804) and now if I open GPE, those same happening, the six pop-up coming in the following order

AppHVSI.admx
inetres.admx [NEW, google search says it's the Administrative Templates for IE11]
WindowsDefenderSecurityCenter.admx
AppHVSI.admx
inetres.admx ["]
WindowsDefenderSecurityCenter.admx

Now, you have anything to add on this?

 

[francis11]

Okay, Update

AeonX
Last week, I made the 20H2 ISO 19042.804 by NTL with the process you suggested i.e. adding those four ADMX files to the exclusion list from compatibility settings and installed the OS via that ISO. After a fresh installation, open GPE, no error pop-up

Now, recently, after I upgraded to the latest 21H1 via the 21H2 EP KB5000736 & with the latest (Insider/beta) LCU KB4601382 [19041.844.1.7], I am now on 19043.844 (from 19042.804) and now if I open GPE, those same happening, the six pop-up coming in the following order

AppHVSI.admx
inetres.admx [NEW, google search says it's the Administrative Templates for IE11]
WindowsDefenderSecurityCenter.admx
AppHVSI.admx
inetres.admx ["]
WindowsDefenderSecurityCenter.admx

Now, you have anything to add on this?

What happen if you don't upgrade to beta 19043.844 and test on the full beta from UUP and keep the 4 .admx exclusions?
I don't have any problems you describe - you can download the .admx (policy files) needed to implement in your image from here after you choose what EDGE build you want to download.
NTL is not supposed to support beta (aka Insider builds) away from a short testing form to make it right when released to public.

 

[francis11]

Okay, Update

francis11

Last week, I made the 20H2 ISO 19042.804 by NTL with the process you suggested i.e. adding those four ADMX files to the exclusion list from compatibility settings and installed the OS via that ISO. After a fresh installation, open GPE, no error pop-up

Now, recently, after I upgraded to the latest 21H1 via the 21H2 EP KB5000736 & with the latest (Insider/beta) LCU KB4601382 [19041.844.1.7], I am now on 19043.844 (from 19042.804) and now if I open GPE, those same happening, the six pop-up coming in the following order

AppHVSI.admx
inetres.admx [NEW, google search says it's the Administrative Templates for IE11]
WindowsDefenderSecurityCenter.admx
AppHVSI.admx
inetres.admx ["]
WindowsDefenderSecurityCenter.admx

Now, you have anything to add on this?

Hi SM03

As you stated you've updated to 19043.844 with the EP package from 19042.804 installed.
The LCU KB4601382 put everything back removed (known fact) and i'm not sure the RemoveReinstall function is an exact copy of the preset used ( my best guess it's not as it's used in the free version too).
Normally when i update - after restart i run my preset again (not including exclusions in any way as i dont remove defender but only IE) and never had an error message from oppening GPO from removing IE.
So best advice is running your preset over the live install again so the GPO errors disappear.

 

[SM03]

Hi francis11

First, sorry for the late reply.

What happen if you don't upgrade to beta 19043.844 and test on the full beta from UUP and keep the 4 .admx exclusions?

I didn't upgrade to 21H1.844 in that way you described here, so can't really say anything about that part. I just installed the 21h1 EP+v844 Cu over my existing 20h2.804 & then upon checking this issue via opening the GPE, I can see & confirm that the same issue returned i.e. because of having those four ADMX files present in the C\Windows\PolicyDefinitions DIR, that's cause those error popup occur

I don't have any problems you describe - you can download the .admx (policy files) needed to implement in your image from here after you choose what EDGE build you want to download.
NTL is not supposed to support beta (aka Insider builds) away from a short testing form to make it right when released to public.

I don't need to download those ADMX files, I just need to delete those ADMX files to get rid of those error pop-ups while opening GPE. I think you got me wrong. I don't want EDGE, Defender & IE11 in my system so I deleted all those from stock win10 ISO while modding via NTL. & That's the reason I guess this error happen

initially, I thought protecting those ADMX via compatibility section (in NTL) as you described & instructed earlier, would solve this issue once & for all, but seems it's not.

Currently, the easiest & only thing I found & do, to deal with this, is to delete all those ADMX files from the C\Windows\PolicyDefinitions DIR

but Maybe nuhi (or anyone else) can help me/us to solve & understand this matter and/or how to deal with this in a better & precise way.

 

[SM03]

Hi SM03

As you stated you've updated to 19043.844 with the EP package from 19042.804 installed.

Yes, that's the way I upgraded in my system from 20H2.804 as I said earlier

The LCU KB4601382 put everything back removed (known fact)

Hmm, I know that & that's the issue here I guess

and i'm not sure the RemoveReinstall function is an exact copy of the preset used ( my best guess it's not as it's used in the free version too).

Maybe nuhi or anyone else can clarify on this matter

Normally when i update - after restart i run my preset again (not including exclusions in any way as i dont remove defender but only IE) and never had an error message from oppening GPO from removing IE.
So best advice is running your preset over the live install again so the GPO errors disappear.

I never did that, but it seems pretty obvious i.e if you perform that then you won't be getting those pop-up.

But I am seeking a permanent solution of getting rid of those without deleting those ADMX files manually or without running NTL on the same PRESET.

 

[francis11]

But I am seeking a permanent solution of getting rid of those without deleting those ADMX files manually or without running NTL on the same PRESET.

Tried fresh updated 20H2 (19042.844) and 21H1(19043.844) from UUP with latest NTL v2.0.0.7797 and ripped out System Guard and WindowsDefender together with IE32 and 64 bit. Now it seems the related .admx files gets removed from \Windows\PolicyDefinitions folder. Tested install of both and no errors opening gpedit.msc!?! Even tested on my liveinstall 19042.804 and manually removed
AppHVSI.admx
inetres.admx
WindowsDefenderSecurityCenter.admx
and try opening gpedit.msc again after restart- and still no error message!
So maybe the problem is related to something else you've removed in NTL.
Beside JScript i keep Internet Explorer HTML Viewer as it seems needed for some Windows functions like MMC extended e.g. services.msc to open without error.
Also keeping Anti-Malware Scan Interface even i removed WindowsDefender and System Guard in testbuilds as if removed can cause file system error prompts.
So either the problem is solved in NTL otherwise i'm sure the error is somewhere else. I just know that removing the related .admx files earlier from removed components then the error messages came when opening GPO.

 

[francis11]

Okay, Update

francis11

Last week, I made the 20H2 ISO 19042.804 by NTL with the process you suggested i.e. adding those four ADMX files to the exclusion list from compatibility settings and installed the OS via that ISO. After a fresh installation, open GPE, no error pop-up

Now, recently, after I upgraded to the latest 21H1 via the 21H2 EP KB5000736 & with the latest (Insider/beta) LCU KB4601382 [19041.844.1.7], I am now on 19043.844 (from 19042.804) and now if I open GPE, those same happening, the six pop-up coming in the following order

AppHVSI.admx
inetres.admx [NEW, google search says it's the Administrative Templates for IE11]
WindowsDefenderSecurityCenter.admx
AppHVSI.admx
inetres.admx ["]
WindowsDefenderSecurityCenter.admx

Now, you have anything to add on this?

Fwiw:
Can confirm updated/ upgraded with NTL on liveinstall 19042.804 with SSU (ssu-19041.841-x64) + LCU (windows10.0-kb4601382-x64) + EP (windows10.0-kb5000736-x64) NTL now show the restartbox with a (new?) checkbox: Remove Reinstalled componets. After restart i got a bunch of error messages opening GPO, but they all related to some other components i removed earlier in offline, ie: reagent.admx, Uservirtualization.admx etc. and not one from missing:
AppHVSI.admx
inetres.admx
WindowsDefenderSecurityCenter.admx
Then run my preset again on liveinstall 19043.488 - restart and have no errors opening GPO!?!
So I can still only interpret it as if there is a mismatch between RemoveReinstalls and the Preset the individual is using, as it seems that RemoveReinstalls is not as thorough in depth.

 

[SM03]

Tried fresh updated 20H2 (19042.844) and 21H1(19043.844) from UUP with latest NTL v2.0.0.7797 and ripped out System Guard and WindowsDefender together with IE32 and 64 bit. Now it seems the related .admx files gets removed from \Windows\PolicyDefinitions folder. Tested install of both and no errors opening gpedit.msc!?! Even tested on my liveinstall 19042.804 and manually removed
AppHVSI.admx
inetres.admx
WindowsDefenderSecurityCenter.admx
and try opening gpedit.msc again after restart- and still no error message!
So maybe the problem is related to something else you've removed in NTL.
Beside JScript i keep Internet Explorer HTML Viewer as it seems needed for some Windows functions like MMC extended e.g. services.msc to open without error.
Also keeping Anti-Malware Scan Interface even i removed WindowsDefender and System Guard in testbuilds as if removed can cause file system error prompts.
So either the problem is solved in NTL otherwise i'm sure the error is somewhere else. I just know that removing the related .admx files earlier from removed components then the error messages came when opening GPO.

francis11

You ain't probably getting my point.

The matter is, whenever you install W10 (modded via NTL with removing those components & protecting those ADMX as you suggested) you will never get any error, the issue will only start (or I'd say return) when any newer (than the ISO installed version) released & you updated/installed that LCU, then you'll get those errors (depending on what you removed from Stock ISO) while opening GPE.

& as said earlier, that issue can be resolved by simply removing those ADMX files, & that's the more simple solution rather than running NTL with PRESET in LIVe OS again, also time effective. But, those are workaround (to bypass those errors) & am actually interested to know a permanent solution where we don't have to do/perform any of those workaround to get rid of those errors

 

[francis11]

SM03

I got it.
But i still don't see how NTL with RemoveReinstalls can predict what components and subcomponents gets reinstalled with the next LCU from MS.
And still 19043.xxx is not official.
A simple component as Xbox App gets installed with an LCU update, which is not there in the first place from basic image 19041.1 even i remove everything else related to Xbox as i don't use it?!?
That's the reason i use my (updated) master preset on as live install which seem to do the job instead of RemoveReinstalls after every monhtly update and clean my installation fully.
There must be a reason why RemoveReinstalls also can be used in the free version.
I haven't compared paid or free preset removals contra RemoveReinstalls thoroughness.
But it should not surprise me if there is an inequality.

 

[Kasual]

There must be a reason why RemoveReinstalls also can be used in the free version.

Slim down Windows on a computer with unlicensed NTLite and save activations or you could have spent all activations or missed the license or anything else that could happen.

 

[Windows 10 User]

Now I removed Internet Explorer - 32 bits, the whole Internet Explorer component and JScript - 32 bits and the MMC Extended View wasn't broken, only when JScript was removed.