Error: Write EPIPE

lorgar1721 · November 14, 2019, 7:10am

Hey there,

I’ve been using WeMod for a couple of months, where it has been working flawlessly.
Suddenly yesterday it startet acting up and i couldn’t activate any trainers.
I’ve tried following the advices from a couple of the threads in here, but it has so far only resulted in WeMod no longer automatically detecting my games directories.

I’m running on win7 64-bit, and I’m using WeMod with steam games, in this case trying to run a trainer for EU4, but the probem remains in every game I’ve tried.

vendor-bundle.js:1 ERROR [native] VersionGuard::GetInstalledVersion:1 failed. Error: write EPIPE
at afterWriteDispatched (internal/stream_base_commons.js:146)
at writeGeneric (internal/stream_base_commons.js:137)
at Socket._writeGeneric (net.js:696)
at Socket._write (net.js:708)
at doWrite (_stream_writable.js:417)
at writeOrBuffer (_stream_writable.js:401)
at Socket.Writable.write (_stream_writable.js:301)
at Server. (~/output/app-bundle.js:1)
at Server.emit (events.js:200)
at Pipe.onconnection (net.js:1471)
e. @ vendor-bundle.js:1
vendor-bundle.js:1 Uncaught (in promise) Error: write EPIPE
at afterWriteDispatched (internal/stream_base_commons.js:146)
at writeGeneric (internal/stream_base_commons.js:137)
at Socket._writeGeneric (net.js:696)
at Socket._write (net.js:708)
at doWrite (_stream_writable.js:417)
at writeOrBuffer (_stream_writable.js:401)
at Socket.Writable.write (_stream_writable.js:301)
at Server. (~/output/app-bundle.js:1)
at Server.emit (events.js:200)
at Pipe.onconnection (net.js:1471)
vendor-bundle.js:1 ERROR [native] FileSystem::ResolvePath:35 failed. Error: write EPIPE
at afterWriteDispatched (internal/stream_base_commons.js:146)
at writeGeneric (internal/stream_base_commons.js:137)
at Socket._writeGeneric (net.js:696)
at Socket._write (net.js:708)
at doWrite (_stream_writable.js:417)
at writeOrBuffer (_stream_writable.js:401)
at Socket.Writable.write (_stream_writable.js:301)
at Server. (app-bundle.js:1)
at Server.emit (events.js:200)
at Pipe.onconnection (net.js:1471)
e. @ vendor-bundle.js:1
e @ vendor-bundle.js:1
(anonymous) @ vendor-bundle.js:1
handleRequestError @ app-bundle.js:1
(anonymous) @ app-bundle.js:1
processTicksAndRejections @ internal/process/task_queues.js:89
Promise.catch (async)
run @ app-bundle.js:1
resolvePath @ app-bundle.js:1
(anonymous) @ app-bundle.js:1
(anonymous) @ vendor-bundle.js:1
u @ vendor-bundle.js:1
findOrLaunchApp @ app-bundle.js:1
(anonymous) @ app-bundle.js:1
(anonymous) @ vendor-bundle.js:1
u @ vendor-bundle.js:1
findOrLaunchGame @ app-bundle.js:1
(anonymous) @ app-bundle.js:1
s @ vendor-bundle.js:1
Promise.then (async)
u @ vendor-bundle.js:1
s @ vendor-bundle.js:1
Promise.then (async)
u @ vendor-bundle.js:1
(anonymous) @ vendor-bundle.js:1
u @ vendor-bundle.js:1
launchInternal @ app-bundle.js:1
(anonymous) @ app-bundle.js:1
(anonymous) @ vendor-bundle.js:1
u @ vendor-bundle.js:1
launch @ app-bundle.js:1
e @ vendor-bundle.js:1
e @ vendor-bundle.js:1
e @ vendor-bundle.js:1
an @ vendor-bundle.js:1
e.bugsnag @ vendor-bundle.js:1
vendor-bundle.js:1 Uncaught (in promise) Error: write EPIPE
at afterWriteDispatched (internal/stream_base_commons.js:146)
at writeGeneric (internal/stream_base_commons.js:137)
at Socket._writeGeneric (net.js:696)
at Socket._write (net.js:708)
at doWrite (_stream_writable.js:417)
at writeOrBuffer (_stream_writable.js:401)
at Socket.Writable.write (_stream_writable.js:301)
at Server. (~/output/app-bundle.js:1)
at Server.emit (events.js:200)
at Pipe.onconnection (net.js:1471)
errnoException @ internal/errors.js:463
afterWriteDispatched @ internal/stream_base_commons.js:146
writeGeneric @ internal/stream_base_commons.js:137
Socket._writeGeneric @ net.js:696
Socket._write @ net.js:708
doWrite @ _stream_writable.js:417
writeOrBuffer @ _stream_writable.js:401
Writable.write @ _stream_writable.js:301
(anonymous) @ app-bundle.js:1
emit @ events.js:200
onconnection @ net.js:1471
Promise.then (async)
u @ vendor-bundle.js:1
(anonymous) @ vendor-bundle.js:1
u @ vendor-bundle.js:1
launch @ app-bundle.js:1
e @ vendor-bundle.js:1
e @ vendor-bundle.js:1
e @ vendor-bundle.js:1
an @ vendor-bundle.js:1
e.bugsnag @ vendor-bundle.js:1

When looking in the console log, i get a few errors called “write EPIPE”, not something I’ve seen before.
I hope some of you guys might know the cause of this, as it seemingly came out of nowhere.

Best regards
Lorgar1721

User_N4m3 · November 14, 2019, 10:45pm

First thing to try is kill WeMod in task manager CTRL+SHIFT+ESCAPE then delete these two folders:

C:\Users\YOURUSER\AppData\Roaming\WeMod\Cache
C:\Users\YOURUSER\AppData\Roaming\WeMod\App\trainers

After removing both folders, try using a trainer again.

Post back with your results

lorgar1721 · November 15, 2019, 6:44pm

Hey thanks for the advice
I tried it out, but sadly it seemed not to make any difference, and i still get the same error as I originally posted.

Ravenfyre · November 15, 2019, 8:35pm

An Epipe error (otherwise known as “broken pipe error”) is triggered when the client closes the socket connection to the server after a specific time, but the server isn’t aware that the connection has been closed until it attempts to send data to the client through the closed socket.

I’ll provide you a few troubleshooting steps. Apologies if I mention something you’ve already tried.

Version Check

In your WeMod program, could you:

Click the arrow in the top-right
Click Settings
On the left panel, check you have Version V6.2.7

The reason I’m asking you to check is because I’ve noticed “VersionGuard” mentioned in the error snippet you provided. VersionGuard was removed in V6.1.4. (Related support article - click).
If you don’t have V6.2.7, try updating WeMod.

Restart your computer and router

Seriously, you’ll be surprised how many issues can be resolved with a simple restart. Still pleasantly surprises me. You never know.

Antivirus & Firewall

Turn off your antivirus and firewall, then attempt to try WeMod again.
If WeMod works fine with them deactivated, you’ll likely need to add WeMod as an exception in your antivirus and firewall.

Comcast / Xfinity

Comcast’s advanced security feature likes to block legit and harmless software, such as WeMod. You’ll need to disable the advanced security feature if you have Comcast. This support article will help you with instructions on that: https://support.wemod.com/article/83-wemod-fails-to-download-cheats

Nuke it

Launch Task Manager
Expand the list by clicking “More Details” at the bottom of Task Manager, of you haven’t already.
Scroll down to “Background processes” and look for all occurrences of “WeMod”.
Right-click and choose “End Task” on all the WeMod background processes until none are left.

Now:
5) In your Start Menu settings/control panel, find and open the “Add Or Remove Programs” tool.
6) Search for and uninstall WeMod using this tool.
7) Once uninstalled, download and re-install WeMod from this link: https://api.wemod.com/client/download

Hopefully one of those helps to resolve the issue for you. If not then we might have to call in the cavalry. It’s a weird one for sure.

lorgar1721 · November 15, 2019, 9:18pm

Hey,

Thank you for this extensive list of tings to try
Regretably nothing seems to be different after trying out most of these things, I haven’t done the comcast one as I don’t have comcast.
My version is V6.2.7 as well.

But I appriciate the help, on the bright side we are now closer to finding the problem, as we know of a lot of things that didn’t help

Best regards
Lorgar

User_N4m3 · November 15, 2019, 10:13pm

I think we should bring in some devs on this. @frank, @Chris any ideas?