General discussion • Re: Request for interesting questions!

Once MicroPython is installed, the Pico reboots and stops being a flash drive ... Windows Explorer will no longer show it

"It's supposed to, yes, but every time I drag my UF2 file to it nothing happens, Explorer keeps showing the drive".

We've had a few of those.

It is correct that the RPI-RP2 drive should automatically disappear and the Pico should reboot as soon as the UF2 file transfer is complete. If the drive remains visible after you drag and drop the file, it means the Pico did not successfully process the update.

Here are the most common reasons why this happens and how to fix it:

1. Check the USB Cable
Many Micro-USB cables are charge-only and do not have data lines. However, even if the drive appears, a low-quality or damaged cable can cause the data transfer to fail or "hang" before it completes. Try a different, high-quality USB cable, preferably a shorter one, and plug it directly into your computer rather than a USB hub.

2. Use the "Flash Nuke" Utility
Sometimes the Pico's flash memory gets into a state where it refuses to accept new firmware. You can reset it completely using a special utility:
[n]—[/n] Download the flash_nuke.uf2 file from the official Raspberry Pi documentation (often found under the Resetting Flash memory section).
[n]—[/n] Put your Pico into BOOTSEL mode.
[n]—[/n] Drag the flash_nuke.uf2 file onto the drive.
[n]—[/n] The drive should disappear and then reappear after a few seconds.
[n]—[/n] Once it reappears, try dragging your MicroPython UF2 file onto it again.

3. Verify the UF2 File Version
Ensure you are using the correct firmware for your specific board.
[n]—[/n] If you have a Pico, use the standard Pico UF2.
[n]—[/n] If you have a Pico W (with the silver wireless chip), you must use the Pico W specific UF2.
[n]—[/n] If you have a Pico 2, you must use the RP2350 version.
If the Pico detects a UF2 file intended for a different architecture, it may simply ignore the file and stay in bootloader mode.

4. Windows "Write Caching" Issues
Sometimes Windows reports that a file has finished copying when it is actually still sitting in a cache.
[n]—[/n] Try waiting for a full minute after the "copying" window disappears.
[n]—[/n] Alternatively, try copying the file using the command prompt. Open cmd and use the copy command:

Code:

copy C:\path\to\micropython.uf2 D:\

(Replace D: with whatever drive letter your Pico is currently using).

5. Try a Different USB Port
If you are using a USB 3.0 (blue) port, try a USB 2.0 (black) port if available. Some older Pico firmware versions had occasional compatibility issues with certain USB 3.0 controllers during the hand-off process.

If none of these steps work, it is possible the flash memory on the board is physically damaged, though this is rare. Testing on a different computer can help rule out OS-specific driver or power issues.

Statistics: Posted by gsh — Sun Dec 28, 2025 9:41 am