| 3 | | FWIW, VBox 6.1.18's vboximg-mount works well on my host Mac under macOS 10.13.6 'High Sierra'. I'm also a long-time user of initially MacFUSE {big 'M' (legacy)} and later OSXFUSE / macFUSE {little 'm' (recent renaming of OSXFUSE)}, independently of VBox. So, I have my own installation of macFUSE 4.0.5, along with an older OSXFUSE 3.10.4 that VBox installed. However, I've noticed that the macFUSE installer can try to remove all traces of OSXFUSE, so it's also possible that installing it after installing VBox could lead to this issue. |
| | 3 | FWIW, VBox 6.1.18's vboximg-mount works well on my host Mac under macOS 10.13.6 'High Sierra'. I'm also a long-time user of initially MacFUSE {big 'M' (legacy)} and later OSXFUSE / FUSE for OS X / FUSE for macOS / macFUSE {little 'm' (latest renaming)}, independently of VBox. So, I have my own installation of macFUSE 4.0.5, along with what I recently noticed is an older OSXFUSE 3.10.4 that (presumably) VBox installed afterwards. However, I've also noticed that the macFUSE installer can try to remove all traces of OSXFUSE, so it's also possible that installing it after installing VBox could lead to this issue. |