Troubleshooting
Fixing EasyBuilder Pro simulation failure on Windows XP
Short answer
When online and offline simulation stop working for every EasyBuilder Pro project on Windows XP after an upgrade, the installed build is the defect: 5.05.02.093 fails simulation on Windows XP while running on Windows 7, and 5.05.02.108 is the corrective release. Read the build number before touching the project, the PLC settings or EB8000.
On this page
- Read the installed build number first
- Why every project failing points at the workstation
- Dead ends to skip until the build is checked
- The Windows XP compatibility boundary
- The evidence, counted
- Install the corrective build without touching the project
- If the simulator launches but still misbehaves
- The decision
- Questions asked
Both simulation buttons dead in EasyBuilder Pro, on every project, right after an upgrade on Windows XP is a build defect, not a project fault. Build 5.05.02.093 fails both online and offline simulation on Windows XP Professional SP3 while working on Windows 7, and build 5.05.02.108 is the corrective release that restored XP simulation. Read the installed build number before touching screens, PLC settings or EB8000, and keep the project unchanged while you fix the workstation.
Read the installed build number first #
Open EasyBuilder Pro and read the full version number from its version information before changing anything else. The decision falls out of three documented results:
- Build 5.05.02.093 on Windows XP Professional SP3: both simulation buttons fail, on every project, reported on two separate computers.
- The same build 5.05.02.093 on Windows 7: simulation works.
- Build 5.05.02.108: released specifically to correct the XP simulation failure, among other fixes.
A completed installer proves installation, not function on that operating system. The editor opening and loading projects proves editing, not simulation. The simulation buttons exercise a different part of the application, and on this operating-system and build pairing that part is the one that broke.
Why every project failing points at the workstation #
Offline simulation never opens a PLC connection, so a wrong device, address or driver setting cannot stop it from launching. When both modes fail across every project, the fault sits above the project layer, in the component every project shares: the installed build running on that operating system.
| Observation | Meaning | Next check |
|---|---|---|
| Online and offline simulation fail for every project after an upgrade | Launch-level fault in a shared component, not one project | Build number plus Windows edition and service pack |
| EB8000 simulation runs on the same PC | Windows itself still launches simulators; EB8000 is a separate application | Test EasyBuilder Pro on its own |
| 5.05.02.093 fails on a second XP Professional SP3 PC | The first machine's project files and install folder drop out as causes | Move to the corrective build |
| 5.05.02.093 works on Windows 7 | The operating-system and build pairing is the live variable | Match the release to the OS before deploying |
| Simulator launches but values do not update | You are past the launch defect and into a communication diagnostic | Selected device, connection path, communication settings |
Dead ends to skip until the build is checked #
- Rebuilding the HMI project. Failure across unrelated projects points above the project layer, and every edit adds a new variable to a fault you have not isolated.
- Changing PLC addresses or communication settings. Those checks belong after the simulator launches; they cannot repair an offline launch failure.
- Treating working EB8000 simulation as proof. EB8000 is a separate Weintek application with its own files, so its success proves nothing about EasyBuilder Pro. If EB8000 instead throws a missing MT8000 library error, that failure has its own documented repair.
- Reinstalling the same build. An affected build reproduces its own defect; reinstall only when the installer or the application gives you a reason to suspect damaged files.
- Blaming the installation folder. The upgrade in the documented case was redirected into the previous version's directory instead of the installer default, which was worth recording, until the same build failed identically on a machine installed to the default folder.
The Windows XP compatibility boundary #
From the 5.05 series onward, Windows XP compatibility stopped being verified for EasyBuilder Pro. Installation still proceeds, but a release may fail in part or totally on XP. That boundary explains how an installable release can carry an XP-specific simulation failure, and it stays true after the fix: 5.05.02.108 corrects the identified simulation defect; it does not certify the whole application for XP.
The vendor's answer on the product page was to carry two downloads: the latest release, and the last release compatible with Windows XP. A compatibility list that names Win2000, NT, XP, Vista, Win7 and Win8 is not release-specific, so match the requirements to the exact installer you intend to deploy.
The evidence, counted #
Count the documented results the way you would count any bench test. Build 5.05.02.093 on Windows XP Professional SP3: machine 1, upgraded in place into the previous version's directory, offline simulation fails and online simulation fails. Machine 2, fresh install to the default folder, offline fails and online fails. That is 0 working launches out of 4 attempts (2 machines × 2 modes). The same build on Windows 7: 2 of 2 modes working on 1 machine.
Between the failing and passing counts the project changed, the folder changed and the computer changed, and the result did not move. The one variable that separates 0 of 4 from 2 of 2 is the operating system paired with the build. Build 5.05.02.108 on the XP machines restored simulation, which closed the case as a build defect. When your own count has that shape, stop editing and change the build.
Install the corrective build without touching the project #
- Record the baseline: full build number, Windows edition and service pack, installation folder, and exactly what each simulation button does, whether nothing, an error, or a window that appears briefly.
- Back up the project untouched, outside the working directory, with any resources you need to reopen it.
- Close EasyBuilder Pro and every running simulator before changing the installation.
- Obtain the installer from Weintek or an authorized distributor, and check that it suits your target HMI. The workstation that writes the programs your operators run is no place for an installer from an unverified source.
- Let the installer remove the older version when it asks; do not delete application folders by hand.
- After installation, open the application and confirm the build number in its version information, so you are not launching an old shortcut.
- Re-run the same two tests on the same, unchanged project.
Change one variable. Combining the update with PLC configuration changes or screen redesign destroys the before-and-after comparison that proves the fix.
If the simulator launches but still misbehaves #
- The window flashes, or simulation reports its port 8000 occupied: open Windows Task Manager, Processes tab, and look for com_e30.exe. If it is running, end that process and start simulation again; that is the vendor-documented check.
- The simulator runs but online values never update: you are in a communication diagnostic, covering selected device, connection path and driver, walked through in testing HMI simulation against a live PLC.
- The simulator runs and then stops after a fixed time: that is a documented time limit rather than a launch defect; see why EasyBuilder Pro PC simulation stops after 15 minutes.
The decision #
- Windows XP with 5.05.02.093, both simulation buttons dead on every project: install 5.05.02.108 and change nothing else. The project was never the fault.
- Windows 7 with 5.05.02.093 and working simulation: no action. This defect does not reach you.
- An XP workstation you cannot move off the OS: run the last XP-compatible release the vendor publishes for the product, and treat every later build as unproven on XP. The 5.05.02.108 fix does not carry forward.
- Simulation launches and only data or uptime is wrong: diagnose the communication path or the time limit separately, after launch.
Keep the failing baseline in your maintenance record, build, OS and symptom per button, so the next upgrade on a legacy workstation starts from evidence instead of edits. If EB8000 on the same machine ever reports a missing MT8000 library, that is a separate repair with its own documented steps.
Questions asked
How do I find which EasyBuilder Pro build is installed?
Open the application and read the full version number in its About or version-information dialog, or read the executable's file properties. Write down every digit group: 5.05.02.093 and 5.05.02.108 sit in the same 5.05 series, and the XP simulation fix is exactly the difference between those two build numbers. An old desktop shortcut can still point at a removed installation, so verify again after upgrading.
Does installing into the previous version's folder cause the failure?
No. Redirecting the upgrade into the old directory was recorded as a suspect, but the identical build then failed on a second Windows XP Professional SP3 computer installed to the default folder, and the corrective build fixed both machines. The folder is background for the maintenance record, not the cause.
Is Windows XP supported by current EasyBuilder Pro releases?
From the 5.05 series onward the vendor stopped verifying XP compatibility: installation completes, but the software may fail in part or totally. The product page answered by listing two downloads, the latest release and the last XP-compatible one. Treat the 5.05.02.108 fix as closing one defect, not as certifying later builds for XP.
EB8000 simulation works on the same PC. Does that clear the computer?
It clears Windows itself of refusing to launch simulators, nothing more. EB8000 is a separate Weintek application with its own runtime files, so its working simulation is a result about that application only. Keep it as the control that proves the PC can simulate, then judge EasyBuilder Pro on its own buttons.
The simulator window appears briefly and closes. Is that the same defect?
Treat it as a different signature: the documented XP build failure left the simulation buttons doing nothing at all. For the flash-and-close case, open Windows Task Manager, Processes tab, look for com_e30.exe, end it and start simulation again, which is the vendor's check for the simulation port being occupied. A simulator that runs at all has passed the launch stage.
Where should the corrective installer come from?
Weintek directly, or one of its authorized distributors. This is the machine that writes the programs your operators run, so an installer from anywhere else is unqualified software on it. Match the download to the exact build you decided on, and record the installer identity alongside the maintenance log entry for the upgrade.