@User74575862 This messaging and behavior is explained and addressed in the ENS Known issues article KB82450 as "as designed". These can occur when the OS has primary handle on a file and locks us out of scanning it. The specific example highlighted in the article is outlined below:
Issue:A sharing violation error is logged in the local log file after scanning the C:\Windows folder. The sharing violation is expected because of the files being open exclusively (no shared read) in Windows processes.
Resolution:This behavior is as designed. The sharing violation error severity is set to Informational, which means by default the error is not sent to ePolicy Orchestrator. Also, the error does not display in the Windows Event Log by default.
Was my reply helpful?
If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.