MTP Not Working Windows 10

[norcal61]

I am unable to get Windows to mount my Pixel XL in MTP mode. I have the Pixel's screen turned on and unlocked, and the connection option on the phone's pull down menu is set to transfer files. Windows is able to mount the phone when it is in picture transfer mode, but not in MTP mode.. When I look in Window's device manager I can see that the MTP device is connected but I'm getting a yellow triangle exclamation, as in the driver is no good. I uninstalled the driver and tried letting Windows reinstall to no avail. I have searched the web for MTP drivers for Windows, but I can't really find anything. The specific version of Windows that I am using is Windows 10 Education 64.

The main reason for my concern is that I am about to attempt to apply the new root method that is available, and I wasn't sure if I needed to be connected successfully via MTP before I get the ball rolling with ADB. I do have the ADB drivers installed, along with ADB and fastboot and that seems to be working fine. When I run the command 'adb devices' the console shows that my Pixel XL is connected. I am assuming that I should be good to go on that front, but I still want to know why MTP is not working on Windows, and how I can fix it. Any suggestions would be greatly appreciated.

Here's a screen shot of what Window's device manager is showing me.

 

[Scott]

I am unable to get Windows to mount my Pixel XL in MTP mode.

Maybe this will help: http://www.technobuzz.net/download-google-pixel-xl-usb-drivers-adb-fastboot/


Personally I installed the latest SDK which comes with the latest drivers.

 

[norcal61]

Maybe this will help: http://www.technobuzz.net/download-google-pixel-xl-usb-drivers-adb-fastboot/


Personally I installed the latest SDK which comes with the latest drivers.

I tried that already. I stumbled across it while searching for a solution. The adb and fastboot parts worked well but not the regular mtp drivers. I think maybe the problem has to do with Windows itself.

 

[SmokinCharger]

I had a similar issue with my Pixel C tablet. I don't remember which driver that I had to use but I eventually got it to work. I believe that I ended up needing PDANet to resolve. I am using the same computer for my Google Pixel phone. I have successfully been able to use MTP on my Google Pixel phone and have access to all the files via file explorer.

 

[defens23]

I noticed the same thing. When I first attached my phone to the laptop I could see the phone in device manager. Couldn't get into internal storage. Changed the phone from mtp to picture mode then back to mtp and was able to get in. I have to use this method whenever I attach my phone to the laptop using Windows 10. I didn't get any yellow exclamation signs at any time.

 

[Robt628]

plug your phone to your computer then check the notifications,tap on the USB charging this device for other options...just tick the usb to transfer files ....

 

[peejayw]

Check out this Youtube video, fixed it for me.

https://www.youtube.com/watch?v=fUHQzqxxsZI

 

[Scott]

I noticed the same thing. When I first attached my phone to the laptop I could see the phone in device manager. Couldn't get into internal storage. Changed the phone from mtp to picture mode then back to mtp and was able to get in. I have to use this method whenever I attach my phone to the laptop using Windows 10. I didn't get any yellow exclamation signs at any time.

Believe it or not have seen / owned many devices that exhibited this behavior.

Switching back and forth always fixed.

 

[meechieballer]

awesome thanks for that video!!

Check out this Youtube video, fixed it for me.

https://www.youtube.com/watch?v=fUHQzqxxsZI

 

[dmb219]

This was from Microsoft's site, is a little quicker. It would be nice if this got fixed.

(1) Go to C:\Windows\INF
(2) Type "wpdmtp.inf" in search bar provided to the right of the address bar in Windows 10.
(3) Once you found it, just right click on it and select install. It will take a very few seconds.
(4) Connect your device to the pc.

 

[triumvirant]

I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?

 

[bobby janow]

I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?

Nope. Coincidence.

Sent from my Pixel using XDA-Developers Legacy app

 

[Jammol]

I've found that switching from a USB 3.0 port to a USB 2.0 port fixes all file transfer issues with the Pixel XL. Anyone else seeing that? Any ideas why?

Nope. Coincidence.

Sent from my Pixel using XDA-Developers Legacy app

I don't know if it's a coincidence because USB 3.0 is still not fully supported or functional on all new motherboards. Even the brands that claim to and brag about having it still have a half ace implementation of it. I'm looking at you Asus and Gigabyte!!! :crying: I have had to stop using their boards because I've gotten too many complaints from customers.

I can never get any 3.0 device to run off my 3.0 ports, wtf?! I can get flash drives to work all day for sure though!!!:silly:

 

[triumvirant]

i'm running an ASUS MB too...perhaps there are more variables to this equation than we want to believe.

 

[bobby janow]

I don't know if it's a coincidence because USB 3.0 is still not fully supported or functional on all new motherboards. Even the brands that claim to and brag about having it still have a half ace implementation of it. I'm looking at you Asus and Gigabyte!!! :crying: I have had to stop using their boards because I've gotten too many complaints from customers.

I can never get any 3.0 device to run off my 3.0 ports, wtf?! I can get flash drives to work all day for sure though!!!:silly:

I'll grant you that, some of those things happen to me too. But as for a driver not recognizing the device this thread fixes that. That doesn't have anything to do (afaik) with USB 3.0. This was just a silly driver that lost its way. As soon as I tried the method here everything was back to normal.

 

[Jammol]

I'll grant you that, some of those things happen to me too. But as for a driver not recognizing the device this thread fixes that. That doesn't have anything to do (afaik) with USB 3.0. This was just a silly driver that lost its way. As soon as I tried the method here everything was back to normal.

Windows! Lol.