Steno writer won't connect after a Windows update? Here's how to fix realtime
You opened CATalyst (or Eclipse) to write realtime, and your machine won't connect — or it dropped mid-job right after Windows installed an update. This is common, and it's almost always one of three specific causes. This guide helps you find which one is yours and fix it.
A quick word on trust first: the steps below are pulled from Stenograph's own documentation, Prolific's and Microsoft's official notices, and the experience of working reporters. Where something is not officially confirmed, we say so. When in doubt, your writer's manufacturer is the final authority — see the disclaimer at the bottom.
Start here: which situation are you in?
- Realtime connected fine, then dropped during a job → most likely Cause 1 (USB power-saving). Start there.
- You use a newer Stenograph writer (Luminex, Luminex II, Diamante, Wave, NexGen) over USB → check Cause 1, then Cause 3 (writer mode).
- You use an older setup with a USB-to-serial adapter / dongle (a small box or cable with a 9-pin serial end), and Device Manager shows a weird "not Prolific" message → that's Cause 2 (Prolific driver).
Cause 1 — Windows turned your USB port's power-saving back on (most common)
After every Windows update, Windows can silently re-enable a per-port setting called "Allow the computer to turn off this device to save power." When that box is checked, the USB port can power down on its own and disconnect your writer — often mid-realtime. Stenograph has documented this behavior directly.
Fix:
- Plug in your writer. Open Device Manager (right-click Start → Device Manager).
- Expand Universal Serial Bus controllers.
- For each USB Root Hub (and the writer's own entry, if listed): double-click it → Power Management tab → uncheck "Allow the computer to turn off this device to save power" → OK.
- Repeat for every USB Root Hub. Reconnect and test realtime.
Important: because Windows can re-check this after future updates, it's worth re-verifying these boxes after any major Windows update — it's the single most common reason a previously-working setup suddenly drops.
Cause 2 — Windows replaced your Prolific (USB-to-serial) driver
This affects older setups that connect through a generic USB-to-serial adapter — not a genuine Stenograph USB cable (see the box below). Windows Update swaps your working driver for a newer Prolific PL2303 driver that intentionally disables end-of-life and counterfeit chips on Windows 10 and 11. The give-away is in Device Manager, where the device renames itself to something like:
- "THIS IS NOT PROLIFIC PL2303. PLEASE CONTACT YOUR SUPPLIER", or
- "PL2303TA DO NOT SUPPORT WINDOWS 11 OR LATER, PLEASE CONTACT YOUR SUPPLIER"
That message is Prolific's official position on those older chips — so the newer driver will keep disabling them.
Fix (roll back to a legacy driver):
- In Device Manager, find the device (under Ports (COM & LPT), possibly with a yellow warning).
- Right-click → Uninstall device. If offered, check "Attempt to remove the driver for this device." Reboot.
- Install an older Prolific driver that still supports the chip (commonly v3.3.11.152 for HXA/XA chips, or v3.8.36.2 for TA/TB chips), or use Device Manager → Update driver → Browse → Let me pick from a list and choose an older version.
- Stop Windows from re-breaking it: turn off automatic driver updates, or Windows Update will silently reinstall the disabling driver. (Search "Do not include drivers with Windows Updates," or pause driver updates.)
Honest caveats — please read:
- This fix is fragile. It can revert on reboot, and Windows Update will reinstall the breaking driver unless you've stopped automatic driver updates.
- If your adapter has a counterfeit chip, the rollback often won't hold permanently — the reliable cure is replacing the adapter with one using a genuine Prolific (or FTDI) chip.
- Prolific removed the official legacy downloads, so older installers now circulate via third-party mirrors. Only use a driver you trust, and prefer replacing aging hardware over chasing drivers if realtime reliability matters for paid work.
Do you actually have this problem? Don't apply Cause 2 to a genuine Stenograph USB connection. Genuine Stenograph writers (Luminex family, Diamante, Wave, NexGen, élan family, Stentura Fusion over USB) connect with Stenograph's own proprietary USB driver, installed by CATalyst from
C:\Cat4\Drivers\Writer— they show up in Device Manager as a "Stenograph USB Writer" device, not as a Prolific/FTDI COM port. Rolling back Prolific drivers does nothing for those and can confuse your setup. The Prolific issue only applies to a separate USB-to-serial adapter — used on the serial connection path (e.g., a Stentura Fusion's 9-pin serial port) or with CAT software that isn't USB-compatible.
Cause 3 — Your Stenograph writer is in "Mira Emulation Mode"
On newer Stenograph writers (Wave, Diamante, Luminex, Luminex II, NexGen), realtime can fail if the writer is set to Mira Emulation Mode instead of Standard mode. In Mira mode, Windows creates no COM port, so serial-based CAT software (such as Eclipse) can't find the writer. In Device Manager you'll see a "Stenograph USB Writer" with "Stenograph élan Mira" beneath it and no COM port.
Fix: On the writer, go to Setup → More → Options → USB Communications and switch from Mira Emulation to Standard mode. That produces the COM port serial-based software expects. (If your CAT software connects natively over USB, make sure you've installed the Stenograph writer driver from C:\Cat4\Drivers\Writer.)
Heads-up for 2026: a driver-signing change is coming
Microsoft has announced it's tightening which drivers Windows will load by default — moving toward only fully certified drivers plus an approved list, and blocking older "cross-signed" drivers. This is rolling out in an evaluation phase starting with the April 2026 update for Windows 11. It could affect the kind of legacy USB-to-serial drivers some older steno setups rely on. As of this writing it's in evaluation, not full enforcement, and we haven't seen confirmed real-world breakage of specific steno drivers yet — but if you're on older USB-to-serial hardware, it's a reason to plan a move to a writer with native USB or Bluetooth/wifi realtime.
When to stop and call your manufacturer
If none of the above matches your symptoms — or your writer uses Bluetooth/wifi, or you're unsure whether your connection is "native USB" vs. a serial adapter — contact Stenograph (or your writer's maker: ProCAT, Stenovations, etc.) and your CAT software support. We could not find an official 2025–2026 advisory tying recent Windows updates to these dropouts, so for anything outside the three causes above, the manufacturer is the right call.
While you're here
TranscriptProof is a free tool for court reporters and students: a court-reporting punctuation checker (paste a sentence, get the correct punctuation plus the rule) and dictation speed-building practice (60–225 WPM, instant scoring). Runs in your browser — no install, no account.
→ Try the free punctuation checker · Free dictation practice
Found another fix, or a cause we missed? We keep this guide current. Email us at hello@transcriptproof.com and we'll add what works (with credit, if you'd like).
Disclaimer: This guide is provided for general help and is compiled from publicly available vendor documentation (Stenograph, Prolific, Microsoft) and the reported experience of working court reporters. TranscriptProof is not affiliated with, endorsed by, or sponsored by Stenograph, Microsoft, Prolific, or any CAT-software maker. Driver and device changes carry risk; if you're not comfortable, consult your writer's manufacturer or a qualified technician. Always verify driver downloads come from a source you trust.