The link on top "Evaluation Package" redirect to Windows Defender Testground but it should directly redirect to Exploit Protection
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
That is a fair point, we would not want users to get sidetracked to visit other pages and maybe forget why they went to the currently linked page. I agree with your conclusion.
The XML file name on the page in question (https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/import-export-exploit-protection-emet-xml) seems to be incorrectly referenced, I think I will add the suggestion to correct that one as well:
The Evaluation Package contains a sample configuration file (name ProcessMitigation-Selfhost-v4.xml that you can use to see how the XML structure looks.
The actual file name is simply ProcessMitigation.xml so I will suggest to use that name instead.
I also wonder if the "ProcessMitigation.xml" is up2date (new Chromium-Edge for example)
No idea. I only find time enough to follow up on these issue ticket pages and their reported pages. I am uncertain, because looking at the end-of-life date for EMET (July 31, 2018) and the up-to-date information regarding Microsoft Defender ATP, it is difficult to keep track so long as my daytime job does not offer much need for upscaled IT work. I only hope the page author may find time to shed some light on your question.
To sum up: There were 6 separate issues to resolve in that page:
=> https://demo.wd.microsoft.com/Page/EP=> microsoft-defender-advanced-threat-protection.md ("Applies to" text link, previously pointed to Windows 10 editions comparison PDF)ProcessMitigation-Selfhost-v4.xml => ProcessMitigation.xml (Selfhost v4)=> https://docs.microsoft.com/previous-versions/windows/desktop/gpmc/group-policy-management-console-portal (permanent MSDN redirect, also pointed to an outdated Windows 8, Windows Server 2008 R2, Windows Server 2012 page)=> https://docs.microsoft.com/en-us/windows/win32/srvnodes/group-policy (permanent redirect from MSDN, also landed 1 level above the correct page)=> https://support.microsoft.com/en-us/help/2458544/the-enhanced-mitigation-experience-toolkit (the outdated technet link redirects to https://www.microsoft.com/en-us/msrc?rtc=1 (Microsoft Security Response Center))I notice that I got slightly stressed going back and forth between my PR and this ticket, so I had to make 2 supplemental corrections because of details I overlooked during my main PR commit edit session.
Most helpful comment
To sum up: There were 6 separate issues to resolve in that page:
=>https://demo.wd.microsoft.com/Page/EP=>microsoft-defender-advanced-threat-protection.md("Applies to" text link, previously pointed to Windows 10 editions comparison PDF)ProcessMitigation-Selfhost-v4.xml=>ProcessMitigation.xml(Selfhost v4)=>https://docs.microsoft.com/previous-versions/windows/desktop/gpmc/group-policy-management-console-portal (permanent MSDN redirect, also pointed to an outdated Windows 8, Windows Server 2008 R2, Windows Server 2012 page)=>https://docs.microsoft.com/en-us/windows/win32/srvnodes/group-policy (permanent redirect from MSDN, also landed 1 level above the correct page)=>https://support.microsoft.com/en-us/help/2458544/the-enhanced-mitigation-experience-toolkit (the outdated technet link redirects to https://www.microsoft.com/en-us/msrc?rtc=1 (Microsoft Security Response Center))I notice that I got slightly stressed going back and forth between my PR and this ticket, so I had to make 2 supplemental corrections because of details I overlooked during my main PR commit edit session.