I screen grabbed the whole thing so please have a look. I only updated Mapper with my Reg key and changed the AddMountingPoint argument from CBFS_SYMLINK_MOUNT_MANAGER to CBFS_SYMLINK_SIMPLE.
The values I'm using are shown in the dialog of the screenshot.

Such type of mounting points (like "t_MountingPoint" with CBFS_SYMLINK_SIMPLE) are not accessible via Explorer. And they also have not been accessible in CBFS v4 too. Actually you can use them only by means of win32 or NT API (with CreateFile, ZwCreateFile). Also in command line some commands also work. For example:

There are another type of mounting points that have quite similar behavior, but works in Explorer and anywhere (because they are native to Windows). It's network mounting points (CBFS_SYMLINK_NETWORK). So maybe use this one.

In order to have "more hidden" network mounting point add CBFS_SYMLINK_NETWORK_HIDDEN_SHARE to AddMountingPoint call. It protects the created UNC path from enumerating. So Explorer won't show the share name in the list of network shares until someone doesn't access it (for example manually enter in the Explorer's command bar).

Things were going smoothly but I had to move my project to an older snapshot of my VM. After doing this I lost my ability to 'see' the network share I created in Windows Explorer. Now I'm back to my original problem...

I'm still using the same code which amounts to this:
mCbFs.AddMountingPoint(";AP;" + t_MountingPoint, CallbackFileSystem.CBFS_SYMLINK_NETWORK, null);

With the former VM, I could use Explorer and display \\AP
With the older snapshot VM I'm using now I get the Network Error - 0x80004005

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.