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

Page 1 of 2 12 LastLast

  1. Posts : 360
    Windows 10 v. 21H1, Build 19043.1348
       #1

    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.
      My Computers


  2. Posts : 149
    windows 10 Pro
       #2

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


  3. Posts : 360
    Windows 10 v. 21H1, Build 19043.1348
    Thread Starter
       #3

    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.

    Google Pixel 5 no longer recognized with version 20H2, Build 19042.867-win10_device-mgr_pixel5.png
    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.
      My Computers


  4. Posts : 149
    windows 10 Pro
       #4

    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 .
      My Computer


  5. Posts : 360
    Windows 10 v. 21H1, Build 19043.1348
    Thread Starter
       #5

    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!
      My Computers


  6. Posts : 149
    windows 10 Pro
       #6

    Have you tried going into Developer Options?

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


  7. Posts : 360
    Windows 10 v. 21H1, Build 19043.1348
    Thread Starter
       #7

    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.
      My Computers


  8. Posts : 360
    Windows 10 v. 21H1, Build 19043.1348
    Thread Starter
       #8

    Another thing that's annoying me to no end...

    "ClockworkMod". The ADB driver that keeps appearing... is dated 08/27/2012. Wouldn't there be a more updated driver? No matter what I do... every time I attach my Pixel 5 via USB, this driver appears. I've done everything I could think of. I even went through the registry and removed every "ClockworkMod" entry I could find. It keeps returning. I even tried "Update Driver", but Windows doesn't find anything newer.

    Any suggestions on how to wipe this clean for good?
    Google Pixel 5 no longer recognized with version 20H2, Build 19042.867-google-nexus-adb-interface-clockworkmod-driverdetails.png

    - - - Updated - - -

    I ran DISM /online /get-drivers.
    Sure enough "ClockworkMod" is showing up, tagged to oem47.inf.
    In the Windows/INF folder, that file exists... and "ClockworkMod" is in it.

    I tried running DISM /online /remove-driver /driverem47.inf, but that failed.
    Error: 50, "This command can only be used with an offline image."
    I could rename the oem47.inf and oem47.pnf files, then move off to a TEMP folder.
    But when I reboot, I'm finding that the oem47.inf is still in the DISM driver list...

    - - - Updated - - -

    SOLVED.

    Thanks to a technical guy over on XDA Developer forums.

    The only way I could thoroughly get rid of that pesky INF file containing ClockworkMod was:
    pnputil -d oem47.inf

    This effectively removed the ClockworkMod driver that kept getting assigned and causing my Pixel 5 not to appear for file transfers. I don't know if that would have also pulled out the oem47.inf file from the Windows/INF folder, as I'd already manually removed it.

    SUCCESS !

    I can now see my Pixel 5 in Windows Explorer once again. And, it's showing up under "Portable".

    The Android USB INF driver indicates a date of 2016... but this isn't what's being used. It's wpdmtp, which is dated 2006. So if 20H2 is trying to use a newer driver, it found ClockworkMod dated 2012 and loaded it... even though, it's not the correct driver (used for ADB interface).

    CONCLUSION:
    This was really nasty. I don't think a novice could've figured this out. Whose fault was this, anyway? Was it a goof by the ClockworkMod programmers? Or were Microsoft Windows programmers tripped up somehow? In my searching, I had come across some heat for ClockworkMod a number of years back and people itching to know how to wipe off all traces. I did not see this solution that worked for me.
    Last edited by cytherian; 27 Mar 2021 at 17:07.
      My Computers


  9. Posts : 149
    windows 10 Pro
       #9

    Congrats on getting it resolved.
      My Computer


  10. Posts : 360
    Windows 10 v. 21H1, Build 19043.1348
    Thread Starter
       #10

    trevo said:
    Congrats on getting it resolved.
    Thanks! It's a major relief. Now that I know about this issue, I'll be sure to clean off my other laptop of this driver fault. I alerted Microsoft about it, as it seems that 20H2 has changed its default driver assignment logic.

    So now, instead of oem47.INF being used (incorrectly), my Pixel 5 is mapped to a 20H2 internal driver, wpdmtp.inf.
    Last edited by cytherian; 26 Mar 2021 at 10:22.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 01:38.
Find Us




Windows 10 Forums