I believe I had Samsung USB driver ver 1.5.33.0 which is later than the one above (1.3.1500.0). I tried both and found no difference between them.... the problems persist. Both the Android ADB interface (2.11.70) and the driver for the Samsung Mobile Composite Device are the latest available.
Eventually I am drawn to the conclusion that the S4 is very fussy about USB leads. I bought some cheap ones a while ago and although they were fine with other devices when I connected the S4 some would not connect as a device at all. I have a theory that when an S4 is connected via USB that it draws all it's power from that connection. If the voltage drop across a substandard USB lead is too much it will perform unexpectedly. A charge app I use says the S4 discharges at around 450mA when active so if the device is soley reliant on USB power when connected a standard USB2 port (500mA max) might struggle to support the higher demands during operations such as r/w. Incidently the misbehaviour is not confined to cheap leads.... an nice blue Belkin one I purchased also does the same thing.
Using the B4A bridge over a a Peer-to-Peer network with seems to be the only way ahead. Unfortunately in Win 8.1 the prompts to set this up have been removed from the Network & Sharing centre so...... Idiots Guide.....
Check your adapter is capable. Open a command prompt as an administrator and execute:
If the string: "Hosted network supported=Yes" Is present then you are good to begin.
The following two batch files will switch the Peer2Peer capability on/off. You should change the filenames to .bat and edit the SSID and password to suit your purposes. The B4A bridge should then work perfectly over WiFi in Peer2Peer mode.