Before receiving a supported dump, turn Write Protect OFF and enable the System Exclusive MIDI filter. If it still fails, test a different MIDI interface because Korg warns that some interfaces do not carry SysEx correctly.
Try these checks
- Back up current data before any transfer.
- Turn Write Protect OFF and enable the System Exclusive MIDI filter.
- Send only a supported original-microKORG dump.
- If it fails, test with another known SysEx-capable interface before repeating.
Diagnose it
Is Write Protect OFF and the System Exclusive filter enabled?
Yes: Check interface SysEx support and the sender’s data format.
No: Set both required receive conditions before retrying.
Does another interface work?
Yes: The first interface may not carry SysEx correctly.
No: Confirm the dump is intended for the original microKORG.
What should happen
The original microKORG can receive a supported dump when its documented receive conditions are met.
Why this happens
Korg documents the required protection/filter states and qualifies USB-MIDI interface SysEx support.
If it still doesn’t work
Check the connections and settings described above. If your device behaves differently, email us with its model, firmware version and the steps you tried.
All microKORG (2002) fixesMore about microKORG (2002)
Sources & review
Sources reviewed: . Documentation does not replace a physical hardware test.
- microKORG Owner’s Manual · Korg · last checked 2026-09-26 · Open PDF
Sections reviewed: Owner’s Manual, MIDI data dump, MIDI filter and Write Protect.