Replies: 3 comments
-
Release notes specify for you to do this already. |
Beta Was this translation helpful? Give feedback.
-
I'll pull this prerelease. |
Beta Was this translation helpful? Give feedback.
-
I think you should say less about the misleading information on the release pages. Simply that it modifies "explorer.exe" is all you need to say and perhaps accept it as "Malware" because malforming the exe is literally what it sounds like you do. I think you explain too much. It is sort of surprising windows doesn't just flat out re-overwrite like it's a system DLL in the protected cache. Maybe trust goes up if you're an "inverted hey-Zeus." |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This issue can be resolved by adding a file exclusion in Windows Defender. Assuming that the file ep_setup.exe will be downloaded to the Downloads folder of the user that is currently logged in to Windows, running the command below in an elevated command prompt will prevent Windows Defender from detecting the file.
"%WinDir%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy Bypass -Command if([Security.Principal.WindowsIdentity]::GetCurrent().Groups -contains 'S-1-5-32-544'){Add-MpPreference -ExclusionPath '%UserProfile%\Downloads\ep_setup.exe' -force;(Get-MpPreference).ExclusionPath}else{'Please run with Administrator privileges.'}
Beta Was this translation helpful? Give feedback.
All reactions