Audacity won’t open M4A on Windows: a tested FFmpeg fix

1. What this test establishes

This is one observed Windows case, not a claim that every M4A problem has the same cause. Initially the sample was absent from the picker, and manually selecting it returned to an empty editor without a visible error. A known-good WAV did import. We checked Audacity’s FFmpeg status instead of declaring the file damaged.

The images retain the actual Chinese UI. English navigation labels are reading aids, not a claim that we tested an English-language installation. Select any image to open the unchanged original at full size.

2. Preserve your original and try the WAV control

Keep the original recording untouched. Save any open project, or start a separate empty project. Download the WAV control and AAC/M4A control into a local folder you can find again. These are synthetic tones, not speech. Start at a comfortable device volume if you later play them.

1. Choose File → Import → Audio (文件 → 导入 → 音频).
2. Select tone-source.wav and open it.
3. Look for a track named tone-source with a short clip at the start.

If WAV fails too, this comparison has not isolated an M4A-specific problem. Check local access and the import operation first. If WAV works while M4A does not, continue to the library check.

3. Read Audacity’s FFmpeg status

1. Open Edit → Preferences (编辑 → 首选项).
2. Select General (通用) and scroll to the bottom.
3. Read the FFmpeg library version line. Ours said 没有找到 FFmpeg 库 — no FFmpeg library found.

The tested 4.0 interface puts this setting under General, as the current General reference describes. Older instructions may call the category Libraries. Follow your actual version instead of searching for a category that is not present.

A working ffmpeg.exe elsewhere is not this check. We already had a functioning command-line build, yet Audacity reported no library. Its detected shared library is the relevant evidence.

4. Install the compatible library, then check again

Follow the Audacity installation reference to its recommended provider. This x64 Windows case used FFmpeg_5.0.0_for_Audacity_on_Windows_x86_64.exe. Avoid unrelated single-DLL sites and browser-extension advertisements beside download links.

1. Choose the package appropriate to your Windows architecture.
2. Review its source and checksum. Run it and personally review the license and system prompts. Do not disable security protection to force it through.
3. Finish setup, save any unsaved project, and restart Audacity as the official instructions advise.
4. Return to Preferences → General and read the status again.

The operator handled the installer and reported completion. We did not capture its screens or independently verify every installer click or restart. The following screenshot establishes that Audacity subsequently detected the library; an installer finishing is not enough.

If no library is found, check compatibility and the location control rather than repeatedly reinstalling. The library check above explains the executable-versus-library distinction.

5. If M4A is not listed, enter the complete filename

After detection, the operator still saw no separate M4A entry in the dropdown. The audio filter ended with an ellipsis, such as *.mp3, *.aac, …. That list alone did not establish whether the file could import. There was no All files choice in this dialog; the filename-entry method below worked without one.

1. Click OK to leave preferences.
2. Choose File → Import → Audio again.
3. Select All supported files (所有支持的文件).
4. In the File name box, enter the complete path to your downloaded tone-aac.m4a, including the extension.
5. Click Open. This goes in the file chooser, not a terminal.

For example, if you saved it in D:\AudioTest, enter D:\AudioTest\tone-aac.m4a. Use your actual folder. Do not rename it to MP3: changing a suffix does not convert AAC. Complete-filename entry was the method that succeeded after library detection in our test.

6. Confirm the new M4A track

A closed file dialog is not proof of import. Look for a new track or clip with the expected name. In the final image, tone-source is the earlier WAV control; tone-aac underneath is the newly imported M4A. Both short clips begin near zero. We did not convert the M4A to WAV for this successful retry.

The tone is quiet and the timeline is zoomed out: these images are not detailed waveform inspections. For your own recording, compare duration and channels and listen at the beginning, middle and end. A visible clip alone does not prove that the whole file sounds correct.

7. If the sample works but your recording fails

Once the control imports, stop treating the whole installation as broken. Try a working copy of your recording and keep the exact error. Check that it is fully downloaded rather than cloud-only, and compare its duration in a local player. A failure in one app does not establish corruption.

M4A is a container label; its audio codec can differ. Incomplete downloads, protection and file-specific problems require separate investigation. If the source app offers an authorized PCM WAV export, try that as a separate fallback while preserving the original. Conversion cannot recover detail lost to lossy encoding or guarantee repair of an incomplete file. Do not upload confidential audio merely to identify it or attempt to remove copy protection.

When requesting help, include your Windows and Audacity versions, FFmpeg status, whether both controls imported and the exact error. A synthetic reproducer is preferable to a private interview.

8. What is fixed, and what remains untested

In this case, missing-library status changed to detected versions, and the same AAC/M4A sample then appeared as a new track. That is the observed resolution, not proof that every codec or application release behaves identically.

Audible playback, a whole spoken recording, exports and other operating systems were not verified. Save your edit as a separate Audacity project; export an audio file when sharing a finished recording. Exporting and destination-player checks are separate tasks and are not covered by this import test.

The four images are unchanged operator-supplied screenshots from the guided test, not mockups. The remaining verification limits are listed below; the screenshots establish this specific import result, not universal compatibility.