Related to issue report ID CE-3335: Unspecified Error with M‑Files Desktop After March ’26 Release, we believe we're experiencing an abnormal presentation of the error described here.
Some users currently get a message of "CoShellView.cpp, 6451, Unspecified error. (Unspecified error) (0x80004005)" when trying to access a vault. This is what we expect from the post above. However, one user instead gets the following error when trying to access a vault: 
Rebooting their computer solves the problem, as described in the Workarounds in the "Unspecified Error" post. The need to reboot occurs every day, and I've confirmed that their system has ample available memory before M-Files is opened.
Can anyone else confirm that this is related to the same error described in CE-3335? Or would this error potentially not be resolved when CE-3335 is addressed in a patch?
