![]() We can manually overwrite this using Set-ProcessMitigation as follows to test this solution: Set-ProcessMitigation -Name outlook.exe -Disable EnableExportAddressFilterPlus, EnableExportAddressFilter The resulting output shows the payload where EnableExportAddressFilterPlus and EnableExportAddressFilter are both set to ON Payload:ĪuditEnableExportAddressFilterPlus : NOTSET But first to confirm that these are enabled, we can run the following PowerShell command and examine the output: Get-ProcessMitigation -Name outlook.exe The article also states in Method 2 of the resolution that setting EnableExportAddressFilterPlus and EnableExportAddressFilter to false addresses this issue. NET Framework versions 4.8 and 3.5 which is why we’re seeing this behaviour. ![]() In this case, we’re running Windows 10 Enterprise 1909, Microsoft 365 Apps release 2004 on Semi-Annual Enterprise channel and devices Hybrid Azure AD joined, with the Microsoft MDM Security Baseline being applied from Endpoint Manager (formerly Intune) which includes an Exploit Guard policy. ![]() This often occurs when Windows is running the Microsoft. This happens because Windows Defender Exploit protection prevents Outlook from growing beyond its assigned memory. I came across this article from Microsoft which pointed to Windows Defender Exploit Guard: NET Runtime version 7.9151 - Fatal Execution Engine Error (00007FFAAD0A6D4E) (80131506) NET Framework 2.0 runtime error when the crash would occur. I had an interesting issue at a customer recently where Outlook would crash to the desktop without error whenever a Teams meeting invite was selected – not ideal when we’re all trying to work from home!Įxamining the Application log in Event Viewer showed the following. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |