About the only thing I can think of, to enable your Samsung Galaxy Tab 2 to
connect, would be an MTP driver. If you are attempting to connect to storage
on such a device, the paths available are USB Storage Class (for which a driver
has been installed in the OS for a dogs age) or MTP. The MTP driver, however,
is treated differently by Microsoft. At one time, it might have
accompanies Windows Media Player (because the driver also support DRM
USBStor does not support DRM as such, and generally "just works". MTP
as a transport, allows features such as preventing you from copying
multimedia content to a portable device. On the plus side, MTP allows
both the tablet and the desktop PC, to be writing to the storage
device inside the tablet at the same time.
Generally, portable devices support USBstor or MTP, but not both.
I am not advocating this page as a solution, merely showing that
someone had a problem with the named device and MTP.
So now, we will ask the great Wiki, where the Media Transfer Protocol can be
of Windows Media Player 10 or higher."
Windows Media 11 Runtime) is installed."
Which to my mind, is not a very good answer. At heart, it should just be
a stinking driver, not a "jail" for your new device.
If the Samsung *Application Software* is .NET based, it may require
that some .NET file be installed. That's a possibility. The .NET should
not really be needed to make MTP work. .NET based applications, would
need .NET libraries to work.
The .NET people have a cleanup tool, with some instructions.
uninstall, repair or patch installation did not succeed for
unusual reasons. It is not a substitute for the standard uninstall procedure.
You should try the steps listed in this blog post before using this cleanup tool.
* This cleanup tool will delete shared files and registry keys used by other
versions of the .NET Framework. If you run the cleanup tool, you will need
to perform a repair/re-install for all other versions of the .NET Framework
that are on your computer or they will not work correctly afterwards.
The tool cannot remove versions of .NET which are "native" to the computer.
For example, on Windows 7, something like .NET 2.0 is probably already on there,
and the cleanup tool cannot remove it. The cleanup tool is for removing
incrementally installed .NET. Like maybe you installed .NET 4.0 by accident
(it was in Windows Update), something went wrong, and you need an option. Then
the Cleanup tool might be a solution.
Anyway, safety first. Make sure you have got some kind of backup available,
in case things go downhill.
I do not know if that Cleanup tool, can unravel a half-installed .NET.
it is not logical that it should, since generally tool design assumes
or the install died and backed itself out (failed). Installs should not
get stuck half-way, but I think you know that already. So while there
is a Cleanup tool, it probably does not know how to tell the MSI subsystem
to stop trying or whatever. That would take too many software skillz.