IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing EasyBuilder 8000 error 0xc0000005 at startup

HMI and touchscreens Published 6 min read

Short answer

EasyBuilder 8000 failing at launch with 0xc0000005 while EasyManager still opens is a Windows access violation at process start. The documented cause is Avast antivirus 5.1.889 or later hooking the editor process. Pause the shields to confirm it, then install the EasyBuilder release after EB8000V442_20110420 for the permanent fix.

On this page
  1. What 0xc0000005 means at an EasyBuilder launch
  2. Check the resident Avast version against 5.1.889
  3. The pause test that settles it
  4. Working the case: ten months of Ver4.03, then 0xc0000005
  5. Keeping the editor running until the corrected build arrives
  6. When the pause test changes nothing
  7. Closing the fault
  8. Questions asked

EasyBuilder 8000 that dies at launch with Windows error 0xc0000005 while EasyManager still opens is a Windows access violation at process start, and the documented cause is Avast antivirus from version 5.1.889 onward. The installed editor files are not the problem: this machine ran Ver4.03 for about ten months, failed, and failed identically after a full reinstall, which rules the build out. Pause the Avast shields and launch once to confirm the diagnosis, then install the EasyBuilder release that follows the affected builds for the permanent fix.

What 0xc0000005 means at an EasyBuilder launch #

0xc0000005 is the Windows access-violation status. The editor process touched memory it was not allowed to touch before its main window existed, so the loader terminated it and Windows raised the dialog. EasyManager survives because the launcher runs a different code path from the editor it starts, which is why one opens and the other dies.

The fault is entirely local to the engineering PC. No PLC, no terminal and no Ethernet segment is involved, so leave the panel and the download cable alone. A launch failure is also not a project fault: errors that appear inside a migrated project, such as fixing HMI macro error C70 after an EasyBuilder migration, have different causes and different fixes. And if your editor opens but PC simulation later stops on a timer, read why EasyBuilder Pro PC simulation stops after 15 minutes instead — that is a limit, not a crash.

An antivirus breaking automation software at launch is a pattern rather than a one-off; the same interference shows up elsewhere as software activation failing under Avast on engineering PCs.

Check the resident Avast version against 5.1.889 #

Weintek documented this fault in an FAQ: Avast from version 5.1.889 onward can conflict with EasyBuilder and produce exactly this startup failure, with the correction due in the following EasyBuilder release. Read your installed version from the maintenance or about page of the Avast interface — the menu layout varies by Avast release — and compare it with the boundary.

Avast version you read What it means
Below 5.1.889 This conflict does not apply; work the other-cause section below.
5.1.889 or later The documented conflict applies; run the pause test.
Avast not installed Work the other-cause section below.

Write the version and the date of the last antivirus update next to the day the fault first appeared. An update within days of the onset strengthens the diagnosis, because the antivirus updates itself and your editor does not.

The pause test that settles it #

  1. Close any open EasyBuilder error dialog.
  2. In Avast, pause or disable the resident shields, taking the shortest timed option the interface offers.
  3. Start EasyManager and choose EasyBuilder.
  4. Record whether the editor main window opens.
  5. Re-enable the shields immediately after the test.

The same installed build returning two different results depending only on the shield state is the proof. The editor opening with Avast paused and failing with it active confirms the conflict and closes the diagnosis; the dialog appearing regardless of the shield state means the cause is elsewhere, and no reinstall will find it.

One caution, once: a paused antivirus leaves the PC unprotected for the duration, so keep the pause to the launch itself and re-enable before you open projects or plug in a USB stick. Pausing is the only workaround documented for the affected releases, and it doubles as the diagnostic.

Working the case: ten months of Ver4.03, then 0xc0000005 #

The inputs, each from the reported machine or the vendor documentation:

  • Operating system: Windows 7 Professional (the machine's reported configuration).
  • EasyBuilder build in service at onset: Ver4.03 (the installed release).
  • Fault-free service before onset: about 10 months (the operating record).
  • Build installed in response: EB8000V442_20110420 (the release current at the time).
  • Conflict boundary: Avast 5.1.889 or later (the vendor's documented threshold).

The rule in words: the conflict applies when the resident Avast version reads 5.1.889 or later — compare the major number first, then the minor, then the build — and a fault that appears with no change to the engineering tool, survives a reinstall, and coincides with software that updates itself points at that software.

The arithmetic:

  • Builds tested across the onset: Ver4.03 before, EB8000V442_20110420 after → 2 builds, 1 identical result. The EasyBuilder build is not the variable.
  • Service life: install + 10 months = onset. A damaged install fails at install + 0 days; failing at month 10 rules the installation out.
  • Shield state: one build, two states. Shields active → dialog, no window; shields paused → window opens, no dialog. Two outcomes on one build make the shield state the variable.

Result: the machine sits inside the documented boundary, and every test above isolates the same input.

Decision: on any engineering PC where the resident Avast is at or past the boundary and the pause test clears the launch, stop reinstalling. The fix is the corrected EasyBuilder release, with the shields active the rest of the time.

Keeping the editor running until the corrected build arrives #

Path What you do Trade-off
Update EasyBuilder Install the release after EB8000V442_20110420 that names the Avast correction in its release notes; read the version history on the vendor's download page for the exact build number. Permanent; needs that build to be available for your projects.
Pause for the launch Pause the shields, start EasyBuilder from EasyManager, re-enable. The PC is unprotected for the pause window; confirm the editor stays stable after re-enabling, because the conflict bites at startup.
Exclusion list Add the EasyBuilder installation folder to the exclusions, re-enable the shields, relaunch. Not documented for this fault; the result of that one test is your answer, not an assumption.

Take the update as soon as the corrected build covers your projects; until then, pause-for-the-launch keeps the machine working with the smallest exposure.

When the pause test changes nothing #

A 0xc0000005 that survives paused shields — or a machine with Avast below 5.1.889, or no Avast at all — has a different access-violation source. Work it in this order:

  1. Open Event Viewer, then Windows Logs, then Application. Find the Application Error entry stamped at the failed launch and read the faulting module name and the exception code.
  2. A module belonging to a security product points to a second antivirus, a firewall suite, or an endpoint agent that hooks process start. Repeat the pause logic on that product.
  3. A module belonging to EasyBuilder points to a damaged install: uninstall, delete the leftover installation folder, reboot, reinstall.
  4. Still ambiguous, repeat the launch on a second PC. If the editor opens there, the fault is specific to the first machine's software stack.

The faulting module name decides the next action; nothing else on this list does.

Closing the fault #

Reboot the engineering PC so the shields load in their normal startup state, set them to the state you intend to run in — active after the EasyBuilder update, or active with an exclusion that passed its test — and verify:

  • Start EasyManager and choose EasyBuilder: the main window opens, no dialog.
  • Open an existing project and compile: the compile finishes without the editor closing.
  • Close the editor and launch it a second time from EasyManager.

Two clean launches from a cold boot, with the shields in their running state, close this fault. Do not accept a single good launch as the fix.

Questions asked

Will reinstalling EasyBuilder 8000 fix the 0xc0000005 startup error?

No. The fault follows the resident antivirus, not the installed files: Ver4.03 and EB8000V442_20110420 failed identically on the same machine. A reinstall is not diagnostic here. The pause test is, because it changes exactly one variable while holding the build constant.

Why did the editor work for months and then fail overnight?

Because the engineering tool never changed: the antivirus updated itself past 5.1.889 inside that window. Treat the timeline as a diagnostic rule. A tool that fails on day one points at its installation; a tool that fails in month ten points at something else on the PC that changed itself.

Were my HMI project files damaged by these crashes?

No. The process is terminated before its main window exists, which is before any project file is opened. There is nothing to recover. Once the launch is fixed, open the project and compile it normally.

Is the fault on the HMI panel as well?

No. This is an engineering-PC fault between the antivirus shield and the editor process. The runtime on the terminal is untouched, so once the editor launches you compile and download to the panel exactly as before.

Can an antivirus exclusion replace pausing?

Not as a documented fix. The vendor note covers pausing and the corrected build, and nothing covers exclusions for this fault. One test settles it on your machine: add the EasyBuilder installation folder to the exclusions, re-enable the shields, relaunch, and let that result be the answer.

Keep reading

  • Troubleshooting

    Fixing HMI macro error C70 after EasyBuilder migration

    Error C70 appears because EasyBuilder Pro checks macro array bounds at compile time and EasyBuilder 8000 did not: this macro declares short buffRd[10] while its final SetData writes 12 elements from buffRd[0]. Decide the output contract at RW 20-31, then either declare short buffRd[12] and assign the two added elements, or cut the transfer count to 10.

    HMI and touchscreens

  • How-to

    Convert an MT500 Project to EasyBuilder 8000 and Resize It

    EasyBuilder 8000 converts an MT500 .eob into a new .mtp project through the Tools menu; the converter selects the terminal with the nearest dimensions, so you must then select the real destination model on the Model tab and work through the resize dialog it triggers. Verify page geometry and live controller data before the panel returns to service.

    HMI and touchscreens

  • Troubleshooting

    Fix offline simulation port 8000 already in use error

    The error means another program on your PC already listens on TCP 8000, the project's default inter-terminal communication port. End the leftover simulator process if Task Manager shows it; otherwise change the port on the Model tab of the project's system parameters and match it in every HMI-to-HMI partner project.

    HMI and touchscreens