|
I have issues with Box Drive on Win 11. Context:Intel core, laptop with dual boot configuration, Win 10 and Win 11 Box Drive version 2.46.240 installed on both (Win 10 works, Win 11 does not) I have admin privileges in both systems, latest updates installed, both run BitLocker. Win 11 Details:Edition Windows 11 Pro Box Drive installs, login screen opens, login process goes through 2FA, browser shows Launching Box Drive… (tried Edge, Firefox, latest stable releases), the box login splash disappears, Windows Explorer is restarted, gray box icon displayed in the system tray with Connecting to Box… hint. The process never completes. Hangs forever, affects the overall function of the OS, probably due to the hook with the Windows Explorer. I can see Box a Box Drive File System (streem.exe) running in the Task Manager. The streem process is unstoppable, causes Task Manager hang if I try to kill it. It also prevents Windows restart, I have to do a hard reset of my laptop to get the system operating again. When Box is running the Windows Explorer does not work properly (e.g. it does not refresh the UI after file is deleted). I went through the forums, reinstalled the app several times, performed the reset operation, compared registry entries with the working instance on Win 10. I performed diagnosis of the system using chkdsk, sfc, dism. So far, I have not found anything. The Win 11 installation is pretty new. I also tried to install the Box Sync, just to try (it installed and logged in without an issue). So, I have the same installation package in two different OS on the same hardware. Win 10 runs, Win 11 not. With all the security functions of the Win 11 OS, I suspect there is some Windows thing blocking it. LogsI inspected logs, the only issue I can see is that the box updater cannot download manifest file, but that should not stop the service. 2025-07-2413:20:30.978INFO 0x00001444 lUpdateManifest:182]lDownloadUpdateManifest] Download update manifest - url: https://cdn07.boxcdn.net/Autoupdate6.json 2025-07-2413:20:31.053INFO 0x00001444 oUpdateManifest:197]oDownloadUpdateManifest] Downloading update manifest 2025-07-2413:20:31.157ERROR0x00001444 oUpdateManifest:214]oDownloadUpdateManifest] Failed to download update manifest 2025-07-2413:20:31.237ERROR0x00001444 oUpdateManifest:214]oDownloadUpdateManifest] System.Net.WebException: The remote name could not be resolved: 'cdn07.boxcdn.net' at System.Net.WebClient.DownloadDataInternal(Uri address, WebRequest& request) at System.Net.WebClient.DownloadString(Uri address) at Box.Desktop.UpdateService.UpdateManifest.DownloadUpdateManifest(String url, Boolean& downloadFailed, Dictionary`2 metrics)
Any ideas are appreciated.
Page 1 / 1
Based on the log entry from the Shell Extension it looks like the BoxFolderPathProvider cannot find or parse the box folder path. [error][2025-07-2421:04:57.254735][0x000008fc][BoxFolderPathProvider.cpp:217][getBoxFolderPathAndPidl] SHParseDisplayName(boxFolderPathCached.c_str(), pbc, &boxFolderPidlCached, 0, NULL) failed, error:0x80070002
Internet says: Error code 0x80070002 typically indicates that Windows Update cannot find or access the necessary files to complete an update, often due to missing or corrupted files. If the path is not found/parsed properly, I believe the virtual file system cannot be initialized and mounted. But that does not bring me any closer to a solution. The path comes from the win registers, I guess, and the data is correct there.
I am experiencing the same with one of our users. I’ve also done the whole uninstall / reinstall / restart. Eventually I will get this pop up that tells me to send the logs to Box and then to create a ticket. The below also pops up but we have no files open.
My last attempts to make it working show this log entries: 2025-07-2911:44:10.9018940INFO StreemProcessMonitor log_recent_process_ex Recent process exits: 2025-07-2911:44:10.9308940ERROR StreemProcessMonitor streem_process Detected that the Streem process has died unexpectedly before the file tree was delivered. 2025-07-2911:44:10.9358940INFO StreemProcessMonitor metrics_collector Recording exception in Drive Version: None 2025-07-2911:44:10.9358940CRITICAL StreemProcessMonitor unhandled_exception_h Unhandled exception Traceback (most recent call last): File "box\sync\core\sync_thread.py", line 37, in run File "threading.py", line 1012, in run File "box\ipc\streem_process.py", line 457, in _monitor_streem_process box.ipc.streem_process.UnexpectedStreemProcessExitBeforeFileTreeDelivered: Windows (CBFS) Streem exited with mSQLite error: database is locked] and return code 3765269347. (before the file tree was delivered) 2025-07-2911:44:10.9428940INFO StreemProcessMonitor unhandled_exception_h Exception Hash: 5d88eb7463cde6512a56754cc14904f2c3c64bf1 2025-07-2911:44:10.9438940WARNING StreemProcessMonitor unhandled_exception_h Quitting - product_crash: True, prompt: UIPromptReason.CRASH, issue_id: None, action: PROMPT_TO_UPLOAD_LOGS
The systems thinks the streem.exe died, but it remains running. So, the StreemProcessMonitor can have an issue itself, the streem.exe has issue, or the db has an issue (it looks like the underlying exception comes from the db). Or is it a timing issue, like the system does not respond in time?
Further investigation. There are logs in the Event Viewer, reporting the events: The process 'C:\Program Files\Box\Box\FS\streem.exe' exited with exit code 3765269347. The creation time for the exiting process was 0x01dc007273c8d9fc.
I am wondering whether it relates to the FLS callback, as the error code 3765269347 is part of the documentation. |
