Return to Answer

It took me two days to fix that mistake! Who would have thought that this is due to the missing file "C:\Windows\SysWOW64\framedynos.dll". When I put the file back in place, everything went back to normal.

UPD:

Please turn on "Show verbose output" in Preferences and browse several last lines. There should be a line like this:

C:\Users\light\AppData\Local\Arduino15\packages\rp2040\tools\pqt-python3\1.0.1-base-3a57aed/python3 -I C:\Users\light\AppData\Local\Arduino15\packages\rp2040\hardware\rp2040\1.10.0/tools/uf2conv.py --serial COM5 --family RP2040 --deploy C:\Temp\arduino_build_214726/...

Copy and run that line in Terminal (Win-R). There may be bug reports to help you solve your problem.

It took me two days to fix that mistake! Who would have thought that this is due to the missing file "C:\Windows\SysWOW64\framedynos.dll". When I put the file back in place, everything went back to normal.

UPD:

Turn on "Show verbose output" in Preferences and browse several last lines. There should be a line like this:

C:\Users\light\AppData\Local\Arduino15\packages\rp2040\tools\pqt-python3\1.0.1-base-3a57aed/python3 -I C:\Users\light\AppData\Local\Arduino15\packages\rp2040\hardware\rp2040\1.10.0/tools/uf2conv.py --serial COM5 --family RP2040 --deploy C:\Temp\arduino_build_214726/...

Copy and run that line in Terminal (Win-R). There may be bug reports to help you solve your problem.

It took me two days to fix that mistake! Who would have thought that this is due to the missing file "C:\Windows\SysWOW64\framedynos.dll". When I put the file back in place, everything went back to normal.

It took me two days to fix that mistake! Who would have thought that this is due to the missing file "C:\Windows\SysWOW64\framedynos.dll". When I put the file back in place, everything went back to normal.

UPD:

Please turn on "Show verbose output" in Preferences and browse several last lines. There should be a line like this:

C:\Users\light\AppData\Local\Arduino15\packages\rp2040\tools\pqt-python3\1.0.1-base-3a57aed/python3 -I C:\Users\light\AppData\Local\Arduino15\packages\rp2040\hardware\rp2040\1.10.0/tools/uf2conv.py --serial COM5 --family RP2040 --deploy C:\Temp\arduino_build_214726/...

Copy and run that line in Terminal (Win-R). There may be bug reports to help you solve your problem.

I have almost the same error, with minor differences (on Arduino 1.8.19, board package Raspberry Pi Pico / RP2040 by Earle F. Philhower III 1.9.15, Windows 10):

Resetting COM4
Converting to uf2, output size: 130560, start address: 0x2000
Traceback (most recent call last):
  File "C:\Users\Lych\AppData\Local\Arduino15\packages\rp2040\hardware\rp2040\1.9.15/tools/uf2conv.py", line 380, in <module>
    main()
  File "C:\Users\Lych\AppData\Local\Arduino15\packages\rp2040\hardware\rp2040\1.9.15/tools/uf2conv.py", line 360, in main
    drives = get_drives()
  File "C:\Users\Lych\AppData\Local\Arduino15\packages\rp2040\hardware\rp2040\1.9.15/tools/uf2conv.py", line 233, in get_drives
    "FileSystem,", "DriveType"])
  File "D:\obj\Windows-Release\37win32_Release\msi_python\zip_win32\subprocess.py", line 395, in check_output
    
  File "D:\obj\Windows-Release\37win32_Release\msi_python\zip_win32\subprocess.py", line 487, in run
    
subprocess.CalledProcessError: Command '['wmic', 'PATH', 'Win32_LogicalDisk', 'get', 'DeviceID,', 'VolumeName,', 'FileSystem,', 'DriveType']' returned non-zero exit status 3221225781.
subprocess.CalledProcessError: Command '['wmic', 'PATH', 'Win32_LogicalDisk', 'get', 'DeviceID,', 'VolumeName,', 'FileSystem,', 'DriveType']' returned non-zero exit status 3221225781.

(I'd also like to point out that I have no folder "D:\obj..." on my disc D.)

Pressing BOOTSEL, reinstalling Arduino IDE, drag-and-dropping flash_nuke.uf2, hello_world.uf2, plugging in another USB port - so far nothing helps.

Important notice: the same Pico board works on another, similar, computer without any conflicts.

It took me two days to fix that mistake! Who would have thought that this is due to the missing file "C:\Windows\SysWOW64\framedynos.dll". When I put the file back in place, everything went back to normal.