Same issue as everyone else, I'm getting notifications (18 in the last 5 minutes) saying that Box is unable to open a folder. It started as soon as I opened After Effects. 

2019 MacBook Pro

Mac OS 11.5.2 

I am having same issues - not using the Adobe feature, not using a Mac.  Windows 2016 on a PC. This is very frustrating.  Any news on what is going on?

The new version of Box Drive for Windows (2.23.422) did not fix this issue for my organization.

The new version of Box Drive for MacOS did not fix the problem. 

Other symptoms that I noticed are:
1) Ping and trace route times for www.box.com are excessive when compare with other cloud drive services for example:
    googledrive and dropbox ping times are 9-10 ms with 0% packet loss
    box ping times are 70 to 300 ms with 0 to 30% packet loss

2) My team notice that file upload and download speeds are faster when processing through the web interface vs. using the Box App.

3) Longer ping times and packet loss correlates to UI error and significant loss of computer performance. I see no performance losses when I quit the box app. 

Is anyone else see these problems?  I suspect if it is related to a inadequate sync algorithm in the box app.

We are also noticing significant performance issues when running Box Drive. 

I'm trying turning off "allow handoff between this Mac and your iCloud Devices" to see if this is the source of the problem.

I'll report back soon.  Has anyone else tried the ping or trace route measurements?

I have been seeing this lately and seem to notice a common problem in my case.

I am working from a Win10 64 with Box Drive installed, connected via our OKTA MFA single sign on application.

When I leave a document opened overnight from a Box Drive folder inside an application(Word), but I am logged out of our MFA Okta accounts due to our 24 hour access window, the connection is broken between the local copy I am working on and the Box Drive to Box.com cloud repository.

It seems if I open the Box Drive SEARCH BOX which is installed with Box Drive, and exit the account, then open the Box.com site in the browser and sign in, it repairs the connection.

Not sure if this works for everyone, but I'm just sharing.

Same issue. This is really annoying.

I've also opened a bug report referring to this thread.

Same issue as all Mac Users. I turned off all notifications for Box Helper and Box UI and that removed the notifications although the issue is still there. 

macOS Mojave
Processor Name: Intel Core i7
Processor Speed: 3.70 GHz
Memory: 64 GB

This solved the problem. 

Please check to see if you have "Calculate all sizes" enabled for the Box folder and, if so, turn it off

• Open Finder

• Click on the Box mount

• Open View->Show View Options

• "Calculate all sizes" is second from the bottom

Hello, I have a user on my team that is having this exact issue, specifically when Adobe AfterEffects is open. The Box Drive update did not fix this issue, and the fix from David was not available to the user. Is there any update on this problem?

I am getting the exact same error messages running on Windows 10.  The only Adobe product that I know is installed is Acrobat.  This has been going on for a couple of months and it is annoying to have these notifications bombard my computer with at least 20 at a time in rapid succession.

@Laura Brown - If your user is on a Mac, this fix will 100% work.

We tried the 'calculate all sizes' fix - didn't work for us.

My team has users experiencing the same issue.  We are on Windows 10 and I do not see the option to un-check "Calculate all sizes."  Users have been able to get the errors to stop by logging out of Box Drive and logging back in.  Would like to find a better solution, however.

Any update on this?  More Windows 10 users are reporting this.  For us it only happens when we have cloud backups running.

The MacOS fix does not work for me. All I have to do is Open Adobe Premiere and it opens the floodgates.

I have the same problem on 2 different pcs even when adobe is not open. Can someone help please. 

This is what Box wanted me to perform on my Windows machine.  I do not have Admin rights to do so.
Their investigation into this issue concluded that there was an executable file continually scanning/crawling your Box Drive content resulting in the encountered error messages. 

The at fault file was found to be dllhost.exe​. If the at fault file is temporarily removed, it will confirm the resolution to the behavior being experienced, which is why our engineering team recommends that you block this executable file explicitly within the affected user's system via the banned process regkey 'BannedProcessNames'​ within Registry editor. 

My in house support Team said that this is caused by someone attempting to save files to Box with Invalid characters.  Not sure.

Yep, still an issue on the Mac. Using MacOS 10.15.7 on a new iMac.  Everything is fine until *after* I open a document in Box for the first time, only then does the deluge of error messages start.  All of them have to do with various plugins not loading.

I'm also getting these errors and am now starting to see this spreading throughout my organization. This needs to be resolved ASAP.

Windows 10 machine, no Adobe products installed, so far nothing I have tried has worked.

I'm having the same issue too! This happens every morning for a handful of users.

It seems to be caused by a lot of Powershell calls (Box Support reviewed the logs, suggested I reach out to Microsoft, who did not help).

Box appears to function but the notifications come in all at once (sometimes 70+ notifications)

OS: Windows 10 Pro 2009 (version 20H2)
Box version: 2.24.208
Workspace One v21.07 and Carbon Black Cloud Sensor v3.7.0.1253

The user has Carbon Black Cloud Sensor installed, but removing that program (and even reinstalling Box) did not resolve the issue. The error messages happen every morning around the same time (I think when the PowerShell calls start) and multiple notifications come in at once. WorkspaceOne location sync happens about 30 minutes before the errors come in.

Below is a snippet from a log (for BOX) that shows some of the Powershell calls (please note file names have been redacted, but this is for multiple folders): 

2022-01-24 09:44:04.322 INFO 0x00003320  winfs:461]]onCloseFile]  powershell.exe] "***filename redacted***"
2022-01-24 09:44:04.323 INFO 0x00003314  winfs:537]]onGetFileInfo]  powershell.exe] "***filename redacted***" 
2022-01-24 09:44:04.323 INFO 0x00003324  winfs:421]]onOpenFile]  powershell.exe] "***filename redacted***", shareMode: 0x2010, desiredAccess: 0x100001 
2022-01-24 09:44:04.323 INFO 0x00003318  winfs:421]]onOpenFile]  powershell.exe] "***filename redacted***", shareMode: 0x2010, desiredAccess: 0x100001 
2022-01-24 09:44:04.324 INFO 0x0000331c  winfs:461]]onCloseFile]  powershell.exe] "***filename redacted***" 
2022-01-24 09:44:04.324 INFO 0x0000332c  folderfetcher:187]]fetchWithWait] Fetching inodeId: 1886, path: "***filename redacted***", priority: 205497324, fetching state: 1, max wait: 30000 initiated by: powershell.exe 
2022-01-24 09:44:04.351 INFO 0x00003184  baseengineipcreceiver:361]]reportFolderFetchError] folderInodeId: 1886, reason: UNKNOWN"

If anyone has a solution I would welcome it, since it has yet to be resolved!

Hi, We are seeing the same issues.

Do you by chance run Nessus or anything from Tenable.IO? It's a vulnerability scanner, Box support mentioned it to us.

I am trying to figure out why powershell is in the Box directories but I am just not sure yet.

1525421546381

Just seeing your comment. The company I work for is having the same notification issues and we have tracked it down to being a Tenable scanner. I think it is the log4j scanner, but that's not my department and I don't know for sure. That scanner uses powershell to do the scanning. Tenable allows you to exclude certain directories on Unix and Mac, but not Windows. So until Box decides to address this in the Box Drive client, you either have to just live with the notifications or disable the scanner.