file access errors when anti virus is active

[ghost]

hi,

here in our company we are forced to change our anti virus solution due to new iso 27001 certification process. with eset antivirus i never had problems but now with sophos sh*t its a pain.

choco install atom for example will fail due to it can't access files choco has extracted recently. it turned out that sophos locks the file to scan for viruses.

also on choco uninstall atom its the same. folders can't be deleted because they are not empty and again sophos has a lock on each file to scan for viruses. choco is too hasty and blames instantly.

here is my question now.
is it possible to change chocos behavior on accessing files in a way it does maybe wait to get access before it instantly fails and blames for inaccessible files?

here in company i cannot uninstall sophos because of group policy permissions i am lacking off to uninstall this sh*tty sophos thing.

I thought also about scoop.sh but it has the same problems. again sophos is holding locks until scan is finished. no shadow copy access. those guys at sophos are living like back in 1995...

[ferventcoder]

Ahhh virus scanners. You can't live with them, you can't live without them. :/

[ferventcoder]

I wonder if we could get something there that allows it to wait on a lock...

[ghost]

i have no idea about powershell. on my mac i dont have it. i try to draw a picture.

what about having a global read_file function and a global write_file function.
both do nothing else then read file and inside a looped try-catch and when ever an exception is catched which is about file access than a timeout is 'executed' and read or write loop is continued.

read_file x
    while true
        try
            read file x
        catch exception ex
            if ex is about file access
                timeout 200ms
                continue
            else
                bubble up ex

that would be my idea. wait 200ms then try again if an access exception was catched. all other exception (no permissions etc) should be bubbled up the chain like it is today.

this write function knows maybe some more exception types to continue after waiting. that is why i think about 2 functions.

[ferventcoder]

This won't be fixed in powershell. The posh version is at its limit. The new c# version is almost done.

[ghost]

okay so what is the time horizon for this issue?

[ferventcoder]

@fibric We'll see if this remains an issue once the new c# version comes out. I expect many of the logged issues to just close as non-issues once that happens. This may be one of them.

[Stanzilla]

@ferventcoder any ETA on that? Where is the repo for it?

[ferventcoder]

@Stanzilla Repo is not publicly available yet. For ETA, I'd suggest signing up for the newsletter. :)

[Stanzilla]

Alright, will do! Thanks!