Google Pixel 5 no longer recognized with version 20H2, Build 19042.867

I'd been using my Google Pixel 5 on two Windows 10 laptops with no issues. One of my laptops just updated to Windows version 20H2, Build 19042.867. And now, my Google Pixel 5 is no longer recognized for file transfer. Normally, I'd select USB-File Transfer on the Pixel 5 and then it would appear in Windows Explorer as a device node. Windows 10 no longer does this. I don't see any unrecognized devices in my device list.

I double-checked on my other Windows 10 laptop that has not yet updated. It still sees the Pixel 5 just fine. It appears the huge 20H2 update has invalidated the Google Pixel device drivers somehow. Is there some way to correct this or am I forced to wait for a future update that fixes this problem? Thanks.

I have the same Windows build as you and I just tested with a Pixel 4 and did not get the error you describe.

trevo said:

I have the same Windows build as you and I just tested with a Pixel 4 and did not get the error you describe.

Thanks for sharing your experience. I don't know if there's some device difference at hand... or if in some cases, updates don't complete as cleanly as others. Comparing the two device driver screens across the two Windows 10 versions/builds shows that Microsoft decided to reclassify how the cellphone device is now recognized. Instead of under "Portable", it now appears under "Android". But clearly, as shown below, there's no "Pixel 5" device listed as before.


This shows 2 different laptop devices, running the two different versions of Windows 10.

Btw, I checked under "Other Devices" and while there are some devices listed, this does not change when unplugging the Google Pixel 5... so it's not getting flagged there.

I just got a Windows Update and am now on Windows version 20H2, Build 19042.868.

I attached my Pixel 4 to the computer and file transfer was available as normal.

I opened Device Manager and the Pixel showed under "portable devices" as your left side screenshot above.

Good luck in working this out .

trevo said:

I just got a Windows Update and am now on Windows version 20H2, Build 19042.868.
I attached my Pixel 4 to the computer and file transfer was available as normal.
I opened Device Manager and the Pixel showed under "portable devices" as your left side screenshot above.
Good luck in working this out .

Thanks. Good to know that on your laptop with the latest 20H2, it's showing up as it appears on the left... on my older Windows 10 installation. So, something screwed up with the update.

I looked around to see if there may be Google device driver software available somewhere, but kept falling into "SDK" territory. No, I do not want to install that--my days of loading firmware on mobile devices is over!

Have you tried going into Developer Options?

Under default USB configuration, there is the option to go straight to File Transfer.

trevo said:

Have you tried going into Developer Options?
Under default USB configuration, there is the option to go straight to File Transfer.

It doesn't matter. My laptop is simply not seeing my device at all in Windows Explorer.

I have developer options enabled for debugging. And when I plug my device in under working circumstances, I use the Android menu to change to File Transfer. No longer showing up in Windows Explorer.

Now, the only issue I can think of is that I had the Android SDK with ADB installed on my computer. BUT... as I stated before, I didn't have this problem before the update to 20H2. Unfortunately I did not take a look in my Device Manager for the Pixel 5 as it appeared prior... so all I can go by is what is on my other laptop with the older version of Windows.

- - - Updated - - -

Well, I was surprised to find that I could get chat level support from Microsoft.

I was told that Microsoft KB5000802 addresses this as a known issue. The technician I chatted with said that it may be a few weeks when the update will be propagated.

I don't know why it would be fine on one laptop but not on another, both running 20H2. It must be some unique combination of software components and/or versions.

Congrats on getting it resolved.