Yesterday I enabled "Launch Folder Windows in Separate Process" for a user who was having the issue and it helped right away. Today however he reports that extracting zip files is not working again. FYI. the registry key path for enabling this setting is found here: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] >> "SeparateProcess"=dword:00000001 Yesterday I received an update from SentinelOne on the issue:
*This issue is not extremely common with windows explorer and Zip files. This issue was brought to the attention of SentinelOne sometime back. We think it's an issue with the AMSI and SentinelOne causing crashes resembling OS issues. When this does occur a policy override is needed.
The Windows Antimalware Scan Interface (AMSI) is a versatile interface standard that allows your applications and services to integrate with any antimalware product that's present on a machine.
Please test disabling AMSI on the endpoint where you are experiencing the issue.
Disable the AMSI for that specific endpoint as specified below using sentinel ctl.
Open an administrative command prompt and go to:
C:\Program Files\SentinelOne\Sentinel Agent version\
run the following commands:
sentinelctl config amsiConfig.registerAsIoavProvider false -k "passphrase"
sentinelctl config amsiConfig.registerAsAmsiProvider false -k "passphrase"
The following policy override will resolve this issue:
{
"amsiConfig": {
"registerAsAmsiProvider": false,
"registerAsIoavProvider": false
}
}
This is a known issue that we are working to resolve. There is no ETA currently, however, we advise to use 7zip for the meantime while this gets worked on.*
I told them that I fully disabled SentinelOne for a workstation where this issue was seen and still had the issue. They replied:
If you disabled the agent and the issue persists, that means it's not S1 causing the issues with unzipping. To be 100% sure, I would temporarily completely uninstall S1 from that endpoint and test unzipping.
I have not yet uninstalled SentinelOne.