Error Message 'Unable to open folder'

New post

Comments

75 comments

  • Luis Aguirre

    The regkey option does not work for us, the errors are constant and the only real workaround is to "ignore it" - this needs to be addressed. 

    0
    Comment actions Permalink
  • Bryan Garrant

    Below is what ours looks like. Are you using tenable as well?

    Once we implemented this GPO and rebooted the pop ups went away.

     

    0
    Comment actions Permalink
  • hawkeyeba

    I have people still having this issue. Does anyone know what causes this yet or if Box is planning on patching this issue? I have tried things people have suggested here. We have Win10 machines deployed if that helps.

    0
    Comment actions Permalink
  • Bryan Garrant

    hawkeyeba

    Do you have any vulnerability scanning tool installed on your machines?

    0
    Comment actions Permalink
  • hawkeyeba

    Bryan, we do have a AntiVirus software installed not sure if that does vulnerability scanning or not specifically.

    0
    Comment actions Permalink
  • Jimmy Buck

    You need to look through the Box Drive logs and see which processes are accessing the files. And then exclude that .exe with the registry key outlined here. We were able to fix the issue by excluding powershell.exe for the tenable scanner.

    0
    Comment actions Permalink
  • Box User

    So, I'm getting this today - over and over again.  This is on Windows 10.  It's clearly a defect in the Box Drive design - don't they have any intention of fixing it?  There is no reason I should have to remove or disable programs or their access to certain directories.  Box should work OK with the same things every other program is OK with.

     At a minimum, can't Box give us a way to reduce the number of messages?  For example, why can't I get just ONE notification each time Box goes through all the folders, instead of a notification for each of the (many) folders I have?

    0
    Comment actions Permalink
  • Jimmy Buck

    While the registry keys worked for my enterprise, I totally agree that it shouldn't be necessary. When a company is debating between Box and OneDrive, the little things like this make a big difference.

    0
    Comment actions Permalink
  • ITAdmin81

    Box Support provided the following explanation:  "This is a behavior that we have seen in the past and our Engineering Team has identified that this is caused by 3rd party programs traversing through the filesystem. When scanning files in the Box Drive folder, this triggers a download of any non-cached documents. For users with a large number of files, you'll see high CPU usage, network degradation, and if the download requests exceed a rate limit, you'll start receiving these notifications. Since the software continues to scan, the user gets hit with a bunch of notifications in quick succession."

    They recommend creating the "Banned Processes Name" registry key as others have mentioned previously...not the answer I was hoping for :(

    0
    Comment actions Permalink
  • Box User

    I'd bet that hiding any directory from scanning by any program is against my company policy, since it would prevent any of their security or compliance related scan programs from seeing things there.

    1
    Comment actions Permalink
  • hawkeyeba

    Agree with the last post. This is not a fix it's more of a workaround/band-aid to the problem. 

    0
    Comment actions Permalink
  • Jimmy Buck

    Your company shouldn't be relying on tools that scan the users' PC's for Box security. You should be relying on Box's built-in virus scanning and/or using other tools that scan Box directly.

    0
    Comment actions Permalink
  • hawkeyeba

    Jimmy Buck I don't think anyone is relying on a tool to scan the users PC for box security, it's endpoint security that's the concern. The Box Drive folders are still on the users endpoint and adding an exception is one place that you won't be looking for malicious content that could harm the computer.

    0
    Comment actions Permalink
  • Jeffrey Allen

    I had this issue as well. Looking at the Box logs, Git was bombarding Box. For some reason, there was an open Git repository in the same folder as the Box Drive app scanning all of the files. After deleting the repository, the notices seem to have stopped. 

    0
    Comment actions Permalink
  • esantana

    I found the culprit in my environment. Review the Streem file located in %localappdata%\Box\Box\Logs\Box_Stream_DATE.log

    To fix I remotely ran this command to fix. (Keep in mind for my environment it was EmUser.exe (Related to an Ivanti product we use)

    REG ADD "HKLM\SOFTWARE\Box\Box" /v BannedProcessNames /t REG_MULTI_SZ /d EmUser.exe

    Here is a sample from log file...

    2022-09-21 12:06:11.577 ERROR 0x00004494 [winfs:647][onEnumerateDirectory] [EmUser.exe] ..\streemfs\filesystem\folderfetch\folderfetcher.cpp(114): Throw in function void __cdecl box::throwAppropriateFetchErrorIfNecessary(const class std::shared_ptr<class box::BaseFSFolder> &)
    Dynamic exception type: struct boost::wrapexcept<class box::FSTimeoutException>
    std::exception::what: Unknown exception
    [struct box::exceptionInodeIdObject * __ptr64] = 43553 

    0
    Comment actions Permalink

Please sign in to leave a comment.