Parsec Error 14004 -

Parsec Error 14004 — Complete Analysis and Publication

Conclusion

Error 14004 is rarely a server-side issue; it is almost always a local configuration preventing the establishment of the data stream. By systematically ruling out VPN interference, followed by firewall restrictions, the vast majority of users can resolve this error and establish a stable connection.

Parsec error 14004 is a video decoding failure on the client (guest) side. It occurs when your device cannot process the video stream sent by the host, typically due to hardware incompatibility or driver issues. 🛠️ Essential Fixes 1. Update Graphics Drivers

Outdated or corrupted GPU drivers are the most frequent cause of decoding errors.

Action: Download the latest official drivers for your specific GPU (NVIDIA, AMD, or Intel).

Pro Tip: If updates don't work, use Display Driver Uninstaller (DDU) to perform a clean install in Safe Mode. 2. Switch to Software Decoding

If your hardware is too old to support modern video encoding, you can bypass the hardware decoder entirely. Open Parsec Settings > Client tab. Find Decoder and change it from "Hardware" to "Software".

Note: This increases CPU usage and may cause higher latency, but it will allow the stream to run on unsupported hardware. 3. Adjust Host Resolution

The client may fail to decode if the host's resolution is too high for the guest device to handle.

Ask the host to lower their desktop resolution (e.g., to 1280x720) before you connect.

Try disabling H.265 (HEVC) in the client settings if your hardware only supports H.264. ⚡ Technical Workarounds Use Integrated Graphics

For laptops with "dual graphics" (Intel + NVIDIA), Parsec sometimes struggles to use the dedicated card for decoding.

Windows Settings: Go to System > Display > Graphics settings.

Add parsecd.exe and set its preference to "Power Saving" to force it to use integrated graphics. Windows "N" Versions

If you are using a Windows "N" or "KN" edition, you are missing critical media components required for video playback.

Fix: Manually install the Media Feature Pack from Microsoft's official site. Comparison of Decoding Modes Hardware Low latency, low CPU usage Requires modern GPU drivers Software High compatibility (works on old PCs) High CPU usage, potential lag

To help narrow down the cause, what are the GPU models on both the host and the guest machines? Knowing if either is using a Mac or Linux system would also change the steps. All Error Codes - Parsec support

Review: Troubleshooting Parsec Error -14004 Parsec Error -14004 is a frustrating roadblock for users attempting to host or join a stream. While Parsec's official documentation is often extensive, this specific code typically signals a fundamental compatibility issue between the host hardware and the software's requirements. The Core Problem Error -14004 generally indicates that the host machine is too old

to support Parsec's streaming architecture. Parsec relies heavily on modern hardware video encoding (like NVIDIA NVENC or AMD AMF); if the graphics card or CPU doesn't meet these specific performance standards, the connection will fail immediately. Common Causes Legacy Hardware:

The most frequent cause is trying to host on a machine without a modern GPU or an integrated CPU that lacks hardware-accelerated encoding. Software Encoding Conflicts:

Unlike some remote desktop tools, Parsec is optimized for low-latency gaming, meaning it often rejects systems that can only perform slow software encoding. Driver Discrepancies:

Outdated or improperly installed graphics drivers can sometimes trigger this error by failing to report hardware capabilities correctly to the Parsec client. Recommended Fixes Check Minimum Requirements:

Ensure your host computer meets the "Recommended" specifications on the official Parsec hardware page Update Graphics Drivers: Perform a clean installation of the latest drivers from to ensure encoding features are fully enabled. Use Software Decoding (Client-side): If you are the receiving this error, you can attempt to switch your Client > Decoder

setting to "Software" in Parsec's settings. While this may allow a connection, it significantly increases latency. Lower Host Resolution:

Reducing the host's desktop resolution (e.g., from 4K to 1080p) can sometimes alleviate the strain on older hardware and allow a successful connection.

If these steps don't resolve the issue, Error -14004 is usually a "hard stop" indicating the host hardware is simply incompatible with Parsec's current version. In these cases, users may need to explore less performance-intensive alternatives like Sunshine/Moonlight Are you currently seeing this error on a All Error Codes - Parsec support

2. Firewall and Antivirus Interference

Security suites often inspect outgoing packets. If Parsec tries to open a high-numbered port for data transfer, the firewall may block the "SYN" packet, resulting in a timeout and the 14004 error.

Windows Defender: Ensure "Parsec.exe" and "pservice.exe" are allowed through the Firewall for both Private and Public networks.
Third-Party AV (e.g., Norton, ESET, Kaspersky, McAfee): These are aggressive at blocking P2P traffic. You may need to add an explicit exception for the Parsec installation folder (C:\Program Files\Parsec).
Test: Temporarily disable the antivirus/firewall for 10 minutes to see if the connection succeeds. If it does, the issue is confirmed to be the firewall rules.

When to Contact Parsec Support

If none of the above works, gather the following and email support@parsec.app:

Your Parsec logs (%APPDATA%\Parsec\logs.txt)
Your network details (ISP, router model, VPN usage)
A screenshot of error 14004

Parsec Error 14004 is a specific connection-related error that typically occurs when a user attempts to connect to a host machine that has Privacy Mode enabled, but the required Parsec Virtual Display Driver is missing or malfunctioning.

This error effectively blocks the connection to ensure that sensitive information on the host remains private when a virtual display cannot be properly established. Below is a comprehensive guide to understanding and resolving this issue. Understanding Error 14004

The error code is part of Parsec's security suite. When Privacy Mode is active, Parsec attempts to redirect the video stream to a virtual display rather than the physical monitor to prevent local observers from seeing what the remote user is doing. If the system cannot find or initialize the virtual display driver to handle this stream, it throws Error 14004 and terminates the connection attempt. Key Causes of Error 14004

Missing Virtual Display Driver: The most common cause is that the Parsec Virtual Display Driver was never installed on the host machine.

Corrupted Driver Installation: Existing drivers may have become corrupted due to Windows updates or conflicting software.

Driver Version Mismatch: Using an outdated version of the Virtual Display Driver that is no longer compatible with the current Parsec client.

Disabled Privacy Mode Requirements: Attempting to use Privacy Mode on a host that does not support the necessary virtual display features. How to Fix Parsec Error 14004 1. Install or Update the Virtual Display Driver

The primary fix is to ensure the Parsec Virtual Display Driver is installed on the host machine. Open Parsec on the host computer. Go to Settings > Host. Look for the Virtual Display Driver section.

If it is not installed, click the install button. If it is already there, consider uninstalling and reinstalling it to clear any corruption. 2. Disable Privacy Mode (Temporary Workaround)

If you do not strictly require the screen to be hidden from local viewers, you can bypass the error by disabling Privacy Mode. On the host machine, go to Settings > Host. Find the Privacy Mode toggle and turn it Off. Try connecting again from the client device. 3. Verify Driver in Device Manager

If the driver is installed but the error persists, check if Windows is recognizing it correctly. Right-click the Start button and select Device Manager. Expand the Display adapters section.

Look for Parsec Virtual Display. If there is a yellow warning triangle, right-click it and select Update driver or Uninstall device (then reinstall via Parsec settings). 4. Restart Parsec Services

Sometimes the background service responsible for managing virtual displays fails to start. Open the Task Manager (Ctrl + Shift + Esc). Go to the Services tab and find pservice (Parsec Service). Right-click it and select Restart. 5. Check for Windows Compatibility parsec error 14004

Users on Windows N versions may lack the necessary media components for advanced streaming features. Ensure you have the Media Feature Pack installed if you are using a European or "N" edition of Windows. All Error Codes - Parsec support

Leo’s comms fizzled, then died. Again.

He was three hours into a solo maintenance crawl along the Event Horizon’s dorsal truss, the stars fixed and indifferent around him. The suit’s internal display blinked a single, ugly red rectangle: PARSEC ERROR 14004 – REALITY ANCHOR OFFLINE.

“Control, this is EV-4. I’ve lost telemetry and spacial sync. Error 14004. Repeat, 14004.”

Silence. Not the hiss of dead air, but an active, swallowing silence, as if the vacuum had ears.

Leo had seen 14004 once before, during training. A simulation where the station’s Parsec Anchor—the quantum lattice that pinned a volume of space to a fixed set of physical laws—failed. In the sim, a wrench had turned into a jellyfish, and his partner’s screams had stretched into a low, endless moan before the reset. They’d called it a “safety drill.” Leo had called it nightmare fuel.

Now, it was real.

He pulled himself hand-over-hand toward the nearest emergency airlock, the carbon-fiber truss groaning under his gloves. That was wrong. Carbon fiber doesn’t groan in a vacuum. There’s no air to carry the sound.

He stopped breathing.

The groan came again, but this time from inside his helmet. A low, resonant hum that vibrated through his jawbone. The error message flickered, then changed.

PARSEC ERROR 14004 – LOCAL PHYSICS CORRUPTION: 0.003% DEVIATION.

“That’s nothing,” Leo whispered to himself. “Point zero zero three percent. That’s… that’s a rounding error.”

But rounding errors don’t make your own heartbeat sound like a drum from a mile away. He glanced down at his suit’s bio-monitor. His heart rate was 82. Normal. But the waveform was wrong—the peaks were too sharp, the troughs too flat. It looked like a square wave. Like his heart was a machine pretending to be an organ.

He unclipped his tether and pushed off toward the airlock. In zero-G, the motion felt sluggish, as if space itself had become a thick syrup. The error climbed: 0.007% deviation.

The airlock door was a simple manual wheel. Leo spun it left. The wheel turned, but the latch didn’t click. He spun it right. Same. He put his visor close to the seal and saw something that made his blood crystallize.

The metal of the door was growing.

Thin, hair-like filaments of steel were weaving themselves across the seam, stitching the door shut. They moved with a purpose, curling and knotting like vines in fast-forward.

“Control, this is EV-4! I’m locked out. The hull is… it’s growing. Requesting emergency extraction!”

Through the static, a voice. Distorted. Too slow, like a recording played at half speed. “Leooooo… do not… look… at… the… staarrrrrs.”

Leo looked up.

The stars were rearranging themselves.

Not moving—not drifting—but snapping into new positions, like pixels on a broken screen. Constellations he’d known since childhood—Orion, Cassiopeia—unraveled and reformed into jagged, angry geometries. Angles that should not exist. Shapes that hurt to track.

ERROR 14004 – DEVIATION: 0.019%.

Then the suit alarms blared. Oxygen levels: dropping. Not leaking—dropping. The molecules were simply deciding not to be oxygen anymore. His HUD showed N2, O2, CO2 all converting into a single, unlabeled gas: ???.

Leo clawed at his helmet latches, desperate to breathe real air, even if it killed him. But the latches had changed. They were now hexagonal. He had no hex tool.

He was going to die because physics had forgotten how to be physics.

A final voice broke through, clear and cold. Not Control. Something else. Something that lived in the space between error codes.

“14004: Reality anchor failure. Local volume no longer belongs to this universe. Thank you for your service.”

The stars went out.

Leo floated in perfect, silent dark. No suit. No body. Just awareness, like a single conscious neuron adrift in the void between realities.

Then, a new sensation: pressure. A hand on his shoulder.

He opened eyes he didn’t know he had.

He was in the simulation pod. Cold sweat plastered his hair to his forehead. A technician in a grey jumpsuit was unhooking the neural leads from his temples.

“Sim complete,” she said flatly. “Passed. You held for four minutes without cardiac arrest. New record.”

Leo tried to speak. His throat was raw.

“The error,” he croaked. “14004. That’s not a real code, is it?”

The technician’s smile didn’t reach her eyes. “It’s real now. You looked at the stars, Leo. They saw you back.”

She walked away. The pod door hissed shut.

Behind him, the main screen flickered. Not a simulation control panel. Just a black screen with a single line of green text. Parsec Error 14004 — Complete Analysis and Publication

PARSEC ERROR 14004 – REALITY ANCHOR OFFLINE. DEVIATION: 0.000% (LOCAL).

And somewhere, very far away or very close, the stars began to rearrange themselves again.

Parsec Error 14004 is a relatively rare but frustrating error typically encountered by users attempting to host or connect to a remote session. While it is not as common as more famous codes like 6023 or 14003, it generally falls into the category of initialization or communication failures between the Parsec client and the host's graphics system. Understanding Parsec Error 14004

Technically, error codes in the "14000" range are often related to capture and display initialization on the host machine. When this specific error occurs, it indicates that Parsec was unable to successfully start the stream or "handshake" with the host's display drivers. Common triggers include:

Driver Mismatches: Outdated or corrupted graphics drivers on either the host or client.

Incompatible Resolutions: The host attempting to use a resolution that the client cannot decode.

Conflict with Hardware Acceleration: Issues with how the GPU is processing the stream, especially on laptops with dual graphics (integrated vs. discrete). Step-by-Step Fixes for Error 14004 1. Update Graphics Drivers

This is the most critical step. Ensure both the host and the client are running the latest drivers from NVIDIA, AMD, or Intel. Parsec relies heavily on modern hardware encoding/decoding, so even a slightly outdated driver can cause a crash. 2. Switch to Integrated Graphics (For Laptops)

If you are hosting from a laptop with both an integrated Intel/AMD chip and a dedicated NVIDIA/AMD card, Parsec may be trying to use the "wrong" card to capture the display. Open Windows Graphic Settings. Browse for parsecd.exe and pservice.exe. Set both to "Power Saving" or "Integrated Graphics". Restart the Parsec app. 3. Lower Host Resolution

If the host is running at a very high resolution (like 4K) and the client is on an older machine, the client may fail to initialize the stream.

Try lowering the host resolution to 1920x1080 before connecting.

Ensure the host has a monitor physically connected or is using a headless HDMI ghost plug if it's a remote server. 4. Force Software Decoding (Client-side)

If your hardware is struggling to initialize the hardware decoder, you can bypass the GPU check by using software decoding. This is a "safe mode" for Parsec. Go to Settings > Client > Decoder. Change the setting from "Auto" to "Software".

Note: This will increase CPU usage and may lead to higher latency. 5. Check for Windows "N" Versions

If you are using a Windows "N" version (common in Europe), you may be missing the Media Feature Pack required for video streaming. You must manually install it from Microsoft's website to enable Parsec's decoding capabilities. Summary Table: Troubleshooting 14004 Potential Cause Outdated Drivers Update GPU drivers on both ends. Resolution Conflict Lower Host resolution to 1080p. Laptop GPU Conflict Set Parsec to "Integrated Graphics" in Windows. Missing Media Pack Install Windows Media Feature Pack (for "N" versions). Hardware Failure Switch Client Decoder to "Software" mode.

The glow of the dual monitors was the only light in Elias’s apartment, casting long, jittery shadows against the peeling wallpaper. On the left screen, a high-fidelity render of a digital cityscape sat frozen. On the right, a jagged red dialogue box mocked him: Parsec Error 14004

"Not tonight," Elias whispered, his voice cracking. He’d been trying to remote into his workstation across town for three hours. 14004 wasn't just a connection failure; it was a ghost in the machine. According to the forums, it was the "Hardware Hosting" error—a polite way for the software to say it couldn't find the soul of the machine it was trying to reach.

He checked his internet. Stable. He checked the drivers. Updated. He even performed the "ritual"—restarting the host, toggling the hosting settings, and sacrificing a cold cup of coffee to the silicon gods. Each time, the progress bar would tease him, reaching 99% before collapsing back into that red box.

Elias leaned back, the springs of his chair groaning. To the outside world, Error 14004 was a technical glitch involving unsupported hardware or driver conflicts

. But to Elias, it felt like a wall. He was a digital architect, and his entire life's work was trapped behind a door that refused to recognize his key.

He tried one last trick: a manual override of the encoder settings. He dived into the configuration files, changing encoder_bitrate and forcing the app_lan_quality . He hit 'Connect.'

The screen flickered. The red box didn't appear. Instead, the monitors went pitch black. For a heartbeat, Elias saw his own reflection—haggard, desperate. Then, a single line of white text pulsed at the top of the screen: Host Initialized. Welcome back, Elias.

The cityscape didn't load. Instead, the camera was looking through his workstation's webcam in the dark, empty office across town. But the office wasn't empty. A figure was sitting in his chair, staring back into the lens. The figure raised a hand and tapped the screen from the other side.

On Elias's end, the red box reappeared, flickering like a dying heartbeat. Error 14004: Host occupied.

Elias pulled the plug, but the red box stayed on the screen, glowing in the dark long after the power was gone. What is Parsec Error 14004?

In the real world, this error is less supernatural but equally frustrating. It typically occurs when the Host computer's GPU fails to initialize the video encoder . Common causes include: Unsupported Hardware

: The GPU is too old to support NVENC (Nvidia) or AMF (AMD) encoding. Driver Issues : Display drivers are outdated or have crashed. Headless Hosting

: Attempting to host without a monitor or a "headless ghost" adapter plugged into the GPU. Virtual Displays

: Conflicts with software like Citrix or LogMeIn that use their own display drivers. Are you currently troubleshooting this error on your own machine, or are you looking for more technical steps to bypass it?

When you’re trying to jump into a game or access your workstation and hit Parsec Error 14004, it’s a frustrating roadblock. Essentially, this error is Parsec’s way of saying: "I see the host computer, but I can't establish a stable stream because something is blocking the handshake." The Core Culprit: Network "Handshaking"

Error 14004 is almost always a network negotiation failure. Unlike some errors that point to hardware bugs, 14004 usually occurs when the Peer-to-Peer (P2P) connection between the client and the host is interrupted by a security layer, a strict router, or a misconfigured VPN. 1. The Firewall/Antivirus Hurdle

The most common cause is a software firewall on either the host or client machine. Parsec requires specific "holes" in your digital fence to pass video data.

The Fix: Ensure Parsec is added to the "Allowed Apps" list in Windows Defender or your third-party antivirus (like Bitdefender or Malwarebytes). If you are on a corporate or school network, their hardware firewall might be blocking the high-range UDP ports Parsec uses. 2. VPN Interference

VPNs are the natural enemy of low-latency streaming. Because a VPN reroutes your traffic through an encrypted tunnel, it often hides the "real" IP address Parsec needs to link the two computers.

The Fix: Disable your VPN on both the host and the client. If you must use one, look for "Split Tunneling" settings to exclude Parsec from the VPN path. 3. Router and UPnP Issues

Your router uses a protocol called UPnP (Universal Plug and Play) to automatically map ports. If UPnP is disabled or malfunctioning, the host computer can’t "tell" the router how to direct the incoming game data to your specific PC. The Fix:

Restart your router. It sounds cliché, but it clears the UPnP table.

Log into your router settings and ensure UPnP is toggled On.

If you’re tech-savvy, try Manual Port Forwarding. Assign a static IP to your host PC and forward a range of UDP ports (default is usually 8000-8010) in your router settings. 4. ISP "Double NAT" Problems Windows Defender: Ensure "Parsec

Sometimes the issue isn't in your house; it's with your provider. If you have two routers (e.g., a modem/router combo from your ISP connected to your own gaming router), you might be in a Double NAT situation. This confuses the connection because there are two layers of private addresses to get through.

The Fix: Put your ISP-provided modem into "Bridge Mode" so your personal router handles all the traffic directly. 5. Simple Software Mismatch

Occasionally, the error is less about the network and more about a "stuck" session. The Fix:

Restart the Parsec Service: On the host, go to the Parsec settings, click "Restart Parsec," or kill it in Task Manager and reopen.

Update: Ensure both the host and client are running the same version of the app.

If you see 14004, start with the easiest fix: turn off any VPNs and restart your router. If that fails, the problem is likely a firewall setting or a port forwarding issue that requires a quick dive into your router's admin panel.

The Parsec Error 14004 is a specific variant of Error 14, which indicates a Client Decoder Error. Essentially, your device is struggling to handle the video stream it's receiving from the host computer.

The "long story" usually involves a mismatch between what the host is sending and what your hardware (or software) can actually translate in real-time. Here is how to break it down and fix it: Why It’s Happening

Hardware Limitation: Your device’s graphics card might be too old to decode the high-resolution or high-bitrate stream coming from the host.

Missing Software: If you are on Windows 10/11 N, you are likely missing the Media Feature Pack, which Parsec needs for decoding.

Driver Mismatch: Outdated graphics drivers often cause the hardware decoder to crash or fail to initialize. How to Fix It

Lower the Host Resolution: The simplest fix is to go to the host computer's settings and reduce the resolution (e.g., from 4K to 1080p). High resolutions put significantly more strain on the client's decoder.

Switch to Software Decoding: If your hardware can't keep up, you can force Parsec to use your CPU instead of your GPU. Open Parsec Settings > Client tab. Set Decoder to Software.

Note: This will increase CPU usage and may cause slight lag, but it usually bypasses the 14004 error.

Update Graphics Drivers: Ensure the device you are joining from has the latest drivers from NVIDIA, AMD, or Intel.

Disable H.265 (HEVC): Sometimes the client hardware claims to support H.265 but fails during the handshake.

In Parsec Settings > Client, set H.265 (HEVC) to Off. This forces the more widely compatible H.264 codec. Error Codes - 14 (Client Decoder Error) - Parsec support

Parsec error -14004 typically indicates that the hardware you are using is incompatible or too old to support Parsec's streaming requirements. It often occurs on older laptops or mobile devices that lack the necessary modern video decoding hardware. Potential Fixes and Workarounds

Since this error is usually hardware-dependent, standard software fixes may not always work, but you can try the following:

Check Hardware Compatibility: Ensure your device meets the minimum requirements listed on the Parsec Support page.

Update Graphics Drivers: Outdated drivers can lead to decoding failures. Visit the website of your GPU manufacturer (Intel, AMD, or NVIDIA) to download the latest stable drivers.

Switch Graphics Processors (Laptops): If you are on a laptop with dual graphics (e.g., Intel integrated and NVIDIA dedicated), try forcing Parsec to use the integrated graphics for decoding, as some dedicated mobile GPUs struggle with certain capture/decode tasks.

Enable/Disable Hardware Acceleration: In the Parsec settings, try toggling hardware acceleration if the option is available, or experiment with different Decoder settings (e.g., switching between H.265 and H.264).

Use the Web App: If the desktop client fails due to hardware limitations, try connecting via a modern browser (Chrome or Edge) at Parsec Web App, though performance may be lower.

Note: If your device is significantly aged (e.g., 10+ years old), it may simply lack the hardware-level instruction sets required for Parsec to function. All Error Codes - Parsec support

In the world of remote gaming, Parsec Error 14004 is often a digital ghost—a rare, frustrating hurdle that usually appears when the software struggles to initialize the display or capture settings on the host machine. While Parsec's official support documentation focuses heavily on errors like 14003 (hardware encoding issues) or 15002 (unsupported resolutions), the 14004 code typically signals a deep-seated disagreement between Parsec and your graphics driver or display hardware. The Story of the Setup

Imagine it’s Friday night. You’ve spent hours meticulously configuring your high-end gaming PC to act as a host so you can play Elden Ring from your aging laptop in the other room. You hit "Connect," the screen flickers with hope, and then—darkness. A small, cold dialog box appears: Error 14004.

This error is the software's way of saying it can't find a valid screen to capture. It’s the digital equivalent of a cameraman walking onto a movie set only to find the lights are off and the actors are missing. Why It Happens

The "story" behind this error usually involves one of three culprits:

The Phantom Monitor: You are trying to connect to a host that doesn't have a physical monitor plugged in. Some GPUs refuse to output a signal if they don't detect a "handshake" from a real screen, leaving Parsec with nothing to stream.

The Driver Conflict: Your graphics drivers are either outdated or, ironically, too new and contain a bug that breaks the desktop duplication API Parsec relies on.

Integrated vs. Dedicated: On laptops, Parsec might be trying to use your low-power integrated graphics to capture a game running on your high-power Nvidia or AMD card, causing a "handshake" failure. The Quest for a Fix

To banish the 14004 ghost, users often follow a familiar ritual:

The HDMI Headless Ghost: Many veterans of remote play buy a "dummy plug"—a tiny HDMI stick that tricks the PC into thinking a 4K monitor is always attached.

Driver Rollbacks: If the error started after a Windows update, the solution often lies in the Nvidia Control Panel or AMD equivalent, ensuring the "Preferred Graphics Processor" is set correctly.

Resolution Matching: Sometimes, simply lowering the host's resolution to 1920x1080 before connecting allows the capture service to "see" the desktop again.

When 14004 strikes, it isn't just a technical glitch; it's a reminder that even in the age of seamless peer-to-peer streaming, the bridge between hardware and software remains a delicate one.

Are you currently seeing this error on a laptop or a headless desktop?

15002 (You're Trying To Connect At An Unsupported Resolution)

Fix 5: Reinstall or Repair Microsoft Visual C++ Redistributables

Parsec’s decoder relies on Visual C++ runtime libraries. If these are corrupted, the decoder fails.

Download the latest Microsoft Visual C++ Redistributable (All-in-one or latest package from Microsoft’s official site).
Run the installer and select Repair (if available) or install fresh.
Restart your PC.
Reinstall Parsec after ensuring these runtimes are healthy.