Error 0x800710D2 accessing via USB cable to phone files

This happened to me a while ago, but I don't remember how I handled it; maybe it resolved itself.
Since this morning, I haven't been able to access my phone's files using the USB cable (which I often do without problems).
I'm getting this error 0800710D2 on all application files.
As you can see in the error message image.
Does anyone know how to restore file access?

Translation:
Unable to copy file. An unexpected error occurred. If the error persists, you can use the error code to find more information about the problem.

Error 0x800710D2: The library, drive, or media pool is empty.

so there are a number of reasons this is happening but the main 2 are:

  1. bad USB connection (Just unplug and re plug or you need a new cable)
  2. software blocking (IDK how to fix that )

I do not know, but I asked Gemini for you
Taifun


That is a frustrating "ghost in the machine" error. The code 0x800710D2 basically means Windows thinks it's looking at a drive that exists but contains absolutely nothing—not even a file system it can read. It’s essentially the digital equivalent of opening a cupboard and finding the shelves have vanished.
Since you've done this before without issue, it’s likely a communication "hiccup" between the Android Media Transfer Protocol (MTP) and Windows. Here is how to get those files back in sight.

  1. The "Handshake" Reset (Most Likely Fix)
    Sometimes the phone and PC get stuck in a loop where they recognize a connection but don't "handshake" the data permissions correctly.
  • Unplug and Unlock: Disconnect the cable. Unlock your phone screen first, then plug it back in.
  • Check USB Preferences: Swipe down your notification shade on the phone. Tap "Charging this device via USB" and ensure File Transfer / Android Auto is selected. Even if it looks selected, toggle it to "No data transfer" and then back to File Transfer.
  • Trust the Device: If a "Trust this computer?" pop-up appears on your phone, accept it immediately.
  1. Clear the Media Storage Cache
    If Windows thinks the "library is empty," it's because the phone's internal indexer (which tells the PC what files are there) has crashed.
  • On your phone, go to Settings > Apps.
  • Tap "See all apps" (you may need to tap the three dots in the corner and select Show system).
  • Find Media Storage and External Storage.
  • For both, select Storage & cache and tap Clear Cache and Clear Data.
  • Restart your phone. It will take a few minutes to rebuild the file list, but this usually clears the "empty library" error.
  1. Hardware & Port Verification
    Since this error can trigger when a connection is "leaking" data (connected but unstable), try these quick swaps:
  • The Port: Move the cable from a front PC case port to a Rear Port (on the motherboard). Front ports often lack the power stability for large file indexing.
  • The Cable: MTP is notoriously sensitive. If you are using a "charging only" cable or one that is slightly frayed, Windows will see the device but fail to pull the file directory.
  1. Update the MTP Driver
    If the above steps fail, Windows might be using a corrupted driver to "talk" to the phone.
  • Connect the phone to the PC.
  • Right-click the Start button and select Device Manager.
  • Expand Portable Devices.
  • Right-click your phone's name and select Update driver.
  • Choose Browse my computer for drivers > Let me pick from a list.
  • Select MTP USB Device and click Next to reinstall it.

Pro Tip: if you are just moving a few photos or documents and the cable remains stubborn, using a cloud service (Google Drive/OneDrive) or a local Wi-Fi transfer app (like Snapdrop or KDE Connect) is a great way to bypass Windows Explorer entirely.
Did switching the USB mode in the notification settings change what you see on the computer at all?

346

I followed Taifun/Gemini's suggestions and performed the steps in #2, and after rebooting, it worked again. Due to translation issues, I'm not sure I used the correct settings, but after rebooting, it worked fine.
I also realized I hadn't tried rebooting before; perhaps that would have solved the problem.
Thanks.

This morning it happened again. It happened because the app I was running crashed while writing a file to Scope App. I restarted my phone and it fixed itself.

The crash is due to an error in the code.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.