I made a few more experiments connecting Android tablets and mobile phones (different brands). Windows mounts their file systems with names, and indeed does not assign any drive letter, for example: "Canon EOS M", "Xperia Tablet Z" -- as opposed to: "E:", "F:", and so on. HOWEVER once mounted Windows Shell gives full access to their file structure, individual files, and provides expected functionality: for example it creates JPEG previews, allows compression/expansion of individual files, and so on.
I also checked XPlorer2, Q-Dir and FreeCommander XE. It is my understanding that at least XPlorer2 does not use standard Windows Shell (not sure about the other two). All mounted tablets and cameras storage properly.
I found your statement "Windows does not assign a drive letter to it, it is not a storage device" to be incorrect. Windows Explorer shows under "Computer" the following groups of devices:
* Hard Disk Drives
* Devices With Removable Storage
* Portable Devices
Fact that no letter drives are assigned to the "Portable Devices" group does not mean that Win handles them as "non storage devices". All file manipulations and specific storage device command appear to be working just fine, reporting of free/available space is correct, formatting from Win shell is allowed, etc.
While I appreciate that you find Windows Shell to be inferior and flawed, I would like to respectfully point out that when tablets, phones or cameras are connected to Win computer it is actually the Multi Commander which "does not always show the truth", thus is flawed. I appreciate time and work you put in the MC, I appreciate that you offer it free, but, before being hyper critical about standard Windows Shell, perhaps some reality check would be good? There are many common scenarios (for example: transferring files from a camera, copying files to tablets, etc) where the MC fails to deliver, and the "inferior" Windows Explorer delivers without a glitch.