Error when going live with the patching

[DazzlingDuke]

I just experienced this. I'm running Win 10 and it just published an update and restarted my computer while the program was running. When I tried to load and compile any Axoloti patch, I would get this error. I restarted the computer and the error is gone. If you get this error, I recommend restarting your computer. Luckily it was an easy fix.

[mtyas]

Just had this error again (hdan't had it since a long time), I just deleted the 3 files in the documents/axoloti/build folder and it works again, as usual.
Just thought I'd let you know

[SmashedTransistors]

Got this problem today.
Thanks for the tip @mtyas !

[thetechnobear]

ok, so just got myself a windows laptop (something I'm surprised about too ) and been playing with Axoloti on it (quite fun with a touchscreen, doesn't work too bad.)

and just encountered this error.

so, I can now confirm its the precompiled header that is the issue, if you delete xpatch.h.gch then the problem is resolved. it is corrupted.

a quick check shows the corrupted file is the same size as the 'uncorrupted version' but has some bytes differing... now, I know that last time I used Axoloti, it was ok.
BUT the accompanying dependency file has the same timestamp, so it doesn't look like its been altered... quite odd.

[Enkerli]

Thanks for this. Might make sense to put a sticky on this answer or document it somehow.
Had the same issue and deleting documents/axoloti/build/xpatch.h.gch did the trick.
A bit more info. Windows 10 machine. Installed the software about a month ago, played with somebody else’s Core without getting this problem.
Just received my own Core today. Plugged it in, updated the firmware, encountered the same problem with the first tutorial patch (01_sine_oscillator). Did a web search for MapViewOfFileEx axoloti and got to this thread. Scanned the thread, saw @mtyas mentioning the correct folder, and @thetechnobear confirming which file was affected.

Disconnected everything, deleted the xpatch file, fired up the Axoloti software, plugged the Core, and now everything sounds like it’s working.

Now comes the fun part of learning how to really do stuff with Axoloti.

[KrizRoring]

Got the same problem today.
Reinstalling didn't help but in the end found the problem:

Windows Defender enabled a setting called: Controller folder access

This is enabled for the \Documents folder, which axoloti used for the live patch.
Disabling this option in Windows Defender> Virus and Threat protection (remember to turn it on again afterusing the axoloti software) solves the error for the live patches.

Greetings,
Kriz

[reaganry]

wow, so glad i found this thread before I started cutting the traces to IC4! I'm not sure if this was related to my overheating problem (don't plug into your computer speakers!) or just randomly concurrent...

[soren1]

same problem here.. deleting that file in documents helped, but I hope this is not something that needs to be done regularly

[nominal]

I just had the same issue after shutting down my PC to troubleshoot a separate unrelated (Ableton audio) issue. I don't believe I'd cleanly shut down the Axoloti patcher beforehand, but I can confirm that dropping a .old extension to the end of xpatch.h.gch resolved it.

A quick google search brought me right to this page, so thanks for having that posted and easy to find, TechnoBear!

[kale]

had the same problem, deleting files in documents/axoloti/build folder solved it as reported before by @mtyas