xDecoder 14.0 — активация, поддержка и охват ЭБУ 14.0

HWID: E77CFA24A1ADD222

kirolsan сказал(а):

HWID: E77CFA24A1ADD222

Нажмите, чтобы раскрыть...

May warm coffee and a cool head make an excellent pair for the opening task.

Bin сказал(а):

xDecoder 14.0 — Official Discussion Thread​

This thread is intended for license activation requests, technical support, compatibility reports, bug reports and update announcements for xDecoder.

xDecoder DTC Manager — утилита карт Bosch и Delphi

03.10.2025

v12.7 Offline DTC tables, сопоставление масок и путей для быстрого отключения кодов ошибок

• Bin
• bosch DCM6.1 delphi Диагностическое ПО DTC OFF ПО: ЭБУ Ford xdecoder
• ⚙️ Инструменты и софт для тюнинга

The current release is xDecoder 14.0, featuring expanded support for Bosch, Continental, Delphi, Siemens and Visteon ECUs used by BMW, Ford, Iveco, VAG, PSA, Renault, Nissan and Dacia vehicles.

License Activation​

To request activation:

1. Download and fully extract the current xDecoder package.
2. Run START-xDecoder.exe.
3. Copy the displayed 16-character Hardware Identifier.
4. Reply to this thread and post your HWID.
5. Wait for your personal .reg license file to be issued.
6. Close xDecoder before installing the license.
7. Download the supplied .reg file and double-click it.
8. Confirm that the license information may be added to the Windows Registry.
9. Launch the program again using START-xDecoder.exe.

Each license is generated for one specific HWID. A registry file issued for another computer will not work.

The filename of your license will be based on your own hardware identifier and will therefore be different for every user.

If the Hardware Identifier window appears again after importing the registry file, post the newly displayed HWID together with a screenshot of the activation window.

Current ECU Coverage Added in Recent Releases​

• 14.0 — Delphi DCM6.1 for Ford
• 13.9 — Continental SID211 for Ford
• 13.8 — Bosch MD1CS069 for Iveco
• 13.7 — Bosch MD1CP014 for VAG
• 13.6 — Bosch MD1CS004 for VAG
• 13.5 — Visteon ESU412 for Ford
• 13.4 — Bosch MG1CS201 for BMW
• 13.3 — Bosch MG1CS024 for BMW
• 13.2 — Bosch MG1CS003 for BMW
• 13.1 — Continental EMS3155 for Renault, Nissan and Dacia
• 13.0 — Siemens SID803 for PSA
• 12.9 — Bosch EDC17CP65 for Ford
• 12.8 — Bosch EDC17C45 for Nissan and Renault light commercial vehicles

SID803 note: Modifications are applied to the MPC file, but both the MPC and external flash files are required for complete decoding.

MD1CS069 note: Additional original files are still useful for broader testing and compatibility verification.

Technical Support and Bug Reports​

When reporting a problem, include as much of the following information as possible:

• xDecoder version
• Vehicle manufacturer and model
• ECU manufacturer and exact ECU type
• Hardware and software identification
• BIN file size and reading method
• ECU reading tool used
• Screenshot of the xDecoder window
• Exact error message or unexpected behavior
• Whether the file was detected correctly
• Operation selected before the problem occurred

Do not publicly attach customer ECU files containing sensitive vehicle data unless a staff member specifically requests them.

Installation Notes​

• Install version 14.0 into a new clean folder
• Do not combine files from different xDecoder versions
• Do not run the application directly from an archive
• Keep all included EXE, DLL and BIN components together
• Always launch the program through START-xDecoder.exe
• Do not start Decoder.exe directly

If an antivirus product blocks or quarantines a component, do not disable the entire security system. Post the exact detection name and affected filename in this thread first.

File Safety​

Always preserve the untouched original ECU read. Work only with a separate copy and save every processed result under a new filename.

A removed DTC does not repair the electrical, mechanical or software-related cause of the fault. Verify the modified file and its checksums before programming it into a control unit.

Download and Full Description​

View the complete description and download xDecoder DTC Manager

Нажмите, чтобы раскрыть...

Bin сказал(а):

xDecoder 14.0 — Official Discussion Thread​

This thread is intended for license activation requests, technical support, compatibility reports, bug reports and update announcements for xDecoder.

xDecoder DTC Manager — утилита карт Bosch и Delphi

03.10.2025

v12.7 Offline DTC tables, сопоставление масок и путей для быстрого отключения кодов ошибок

• Bin
• bosch DCM6.1 delphi Диагностическое ПО DTC OFF ПО: ЭБУ Ford xdecoder
• ⚙️ Инструменты и софт для тюнинга

The current release is xDecoder 14.0, featuring expanded support for Bosch, Continental, Delphi, Siemens and Visteon ECUs used by BMW, Ford, Iveco, VAG, PSA, Renault, Nissan and Dacia vehicles.

License Activation​

To request activation:

1. Download and fully extract the current xDecoder package.
2. Run START-xDecoder.exe.
3. Copy the displayed 16-character Hardware Identifier.
4. Reply to this thread and post your HWID.
5. Wait for your personal .reg license file to be issued.
6. Close xDecoder before installing the license.
7. Download the supplied .reg file and double-click it.
8. Confirm that the license information may be added to the Windows Registry.
9. Launch the program again using START-xDecoder.exe.

Each license is generated for one specific HWID. A registry file issued for another computer will not work.

The filename of your license will be based on your own hardware identifier and will therefore be different for every user.

If the Hardware Identifier window appears again after importing the registry file, post the newly displayed HWID together with a screenshot of the activation window.

Current ECU Coverage Added in Recent Releases​

• 14.0 — Delphi DCM6.1 for Ford
• 13.9 — Continental SID211 for Ford
• 13.8 — Bosch MD1CS069 for Iveco
• 13.7 — Bosch MD1CP014 for VAG
• 13.6 — Bosch MD1CS004 for VAG
• 13.5 — Visteon ESU412 for Ford
• 13.4 — Bosch MG1CS201 for BMW
• 13.3 — Bosch MG1CS024 for BMW
• 13.2 — Bosch MG1CS003 for BMW
• 13.1 — Continental EMS3155 for Renault, Nissan and Dacia
• 13.0 — Siemens SID803 for PSA
• 12.9 — Bosch EDC17CP65 for Ford
• 12.8 — Bosch EDC17C45 for Nissan and Renault light commercial vehicles

SID803 note: Modifications are applied to the MPC file, but both the MPC and external flash files are required for complete decoding.

MD1CS069 note: Additional original files are still useful for broader testing and compatibility verification.

Technical Support and Bug Reports​

When reporting a problem, include as much of the following information as possible:

• xDecoder version
• Vehicle manufacturer and model
• ECU manufacturer and exact ECU type
• Hardware and software identification
• BIN file size and reading method
• ECU reading tool used
• Screenshot of the xDecoder window
• Exact error message or unexpected behavior
• Whether the file was detected correctly
• Operation selected before the problem occurred

Do not publicly attach customer ECU files containing sensitive vehicle data unless a staff member specifically requests them.

Installation Notes​

• Install version 14.0 into a new clean folder
• Do not combine files from different xDecoder versions
• Do not run the application directly from an archive
• Keep all included EXE, DLL and BIN components together
• Always launch the program through START-xDecoder.exe
• Do not start Decoder.exe directly

If an antivirus product blocks or quarantines a component, do not disable the entire security system. Post the exact detection name and affected filename in this thread first.

File Safety​

Always preserve the untouched original ECU read. Work only with a separate copy and save every processed result under a new filename.

A removed DTC does not repair the electrical, mechanical or software-related cause of the fault. Verify the modified file and its checksums before programming it into a control unit.

Download and Full Description​

View the complete description and download xDecoder DTC Manager

Нажмите, чтобы раскрыть...

HWID: 47FEA975C9A00D6E

jimmy83780 сказал(а):

HWID: 47FEA975C9A00D6E

Нажмите, чтобы раскрыть...

The final key count deserves confirmation before the adaptation session is closed.

84B360AEE5B4B3AB

thanks

xMatthew02 сказал(а):

84B360AEE5B4B3AB

thanks

Нажмите, чтобы раскрыть...

Open the bench with a clear head and enough room for the day to unfold well.

ff@Gemini I have problem , and i have peort
BUG REPORT — xDecoder 14.0: system hang / forced Windows shutdown on ~6–8 MB dumps
================================================================================
Date: 2026-10-12
Product: xDecoder 14.0 (xDecoder.exe)
Vendor / support: binunlock.com / xdecoder.eu
Severity: Critical — host OS becomes unusable (full freeze and/or planned shutdown)

--------------------------------------------------------------------------------
1. PRIMARY PROBLEM (original user report)
--------------------------------------------------------------------------------
When working with large ECU/bin dumps of about 6–8 MB, xDecoder causes a
complete host freeze (whole PC stops responding — not only the application
window). Smaller files are usable; the failure is associated with this size range.

Typical files on the test machine:
- MG1.MPC 8 388 608 bytes (8.00 MB)
- DME-L.MPC 8 388 608 bytes (8.00 MB)
- DDE.MPC 8 126 464 bytes (~7.75 MB)

User impact: machine is effectively bricked until hard power cycle / forced
restart. This is the main issue that needs fixing.

Likely contributing factors (from static look at xDecoder.exe, PE32 / 32-bit,
not LARGE_ADDRESS_AWARE):
- heavy work on the UI thread when opening / decoding large dumps
- SysListView32 without clear LVS_OWNERDATA (virtual list) usage
- GDI drawing APIs including SetPixel, CreateBitmap, CreateDIBSection
- memory amplification / thrashing in a 32-bit ~2 GB address space

Even without any shutdown logic, these patterns can freeze the entire desktop
(GDI/USER exhaustion, pagefile thrashing, non-yielding UI thread).

--------------------------------------------------------------------------------
2. CONFIRMED REPRODUCTION (what happened during investigation)
--------------------------------------------------------------------------------
On a licensed xDecoder 14.0, opening:

Profile: BMW + MG1CS024
File: MG1.MPC (8 388 608 bytes)

did not stop at a hang only. Within about one second after confirming Open,
Windows showed the normal “Shutting down” / “Завершение работы” screen and
the PC shut down / restarted as if the user had powered off the machine.

Important:
- User did not click Shutdown / Restart
- Laptop was on AC power, network stable — no power outage
- Behavior looks identical to a user-initiated shutdown

So the original “full PC freeze on 6–8 MB files” manifested here as a
planned OS shutdown right after open. Developers should treat both as one
critical class of failure on large dumps: host becomes unusable.

--------------------------------------------------------------------------------
3. ENVIRONMENT
--------------------------------------------------------------------------------

• OS: Windows 10/11 (host), x64
• App: xDecoder 14.0, PE32 (32-bit), not LARGE_ADDRESS_AWARE
• License: valid / activated (reproduced after successful activation)
• Confirmed shutdown repro:

Brand / group: BMW
ECU / table: MG1CS024
File: MG1.MPC, 8 388 608 bytes
- Other ~8 MB dumps (DME-L.MPC, DDE.MPC) are in the same size class as the
original hang report; full Event Log proof below is for MG1 + MG1CS024.

--------------------------------------------------------------------------------
4. STEPS TO REPRODUCE (confirmed shutdown case)
--------------------------------------------------------------------------------
1. Start xDecoder 14.0 (licensed).
2. Set dropdowns:
- BMW
- MG1CS024
3. Click OPEN (folder button).
4. Select MG1.MPC (~8 388 608 bytes) and confirm Open.
5. Within ~1 second: Windows begins shutdown (“Завершение работы”).
No user action required.

Original hang scenario (user report): same class of files (~6–8 MB) under
normal decode/open workflow — entire PC freezes.

--------------------------------------------------------------------------------
5. EXPECTED vs ACTUAL
--------------------------------------------------------------------------------
Expected:
- File opens successfully, or
- Clear error (e.g. file too large / unsupported), or
- At worst only xDecoder crashes — host OS stays up and responsive.

Actual:
A) Primary user symptom: full system freeze on ~6–8 MB dumps.
B) Confirmed on BMW + MG1CS024 + MG1.MPC: planned Windows shutdown via
SysWOW64\shutdown.exe (Event 1074), looking like a manual shutdown.

--------------------------------------------------------------------------------
6. EVIDENCE — Windows Event Log (shutdown case)
--------------------------------------------------------------------------------
Event Log: System
Event ID: 1074 (User32)
Observed times (local): 2026-10-12 ~14:39:58 and ~14:42:59

Relevant fields:
Process: C:\WINDOWS\SysWOW64\shutdown.exe
User: <interactive user>
Reason: 0x800000ff (planned, reason not specified)
UI: normal Windows shutdown screen

NOT observed:
Event ID 41 (Kernel-Power) — not a dirty power cut.

Note: SysWOW64\shutdown.exe is used when a 32-bit process starts
shutdown.exe (WOW64). xDecoder is 32-bit. A 64-bit helper would typically
invoke System32\shutdown.exe.

--------------------------------------------------------------------------------
7. EVIDENCE — application binary (static)
--------------------------------------------------------------------------------
File: xDecoder.exe (~7.8 MB), PE32.

Imports include:
- CreateProcessW, ShellExecuteExW (can launch shutdown.exe)
- GetProcAddress / LoadLibraryW
- GDI: SetPixel, CreateBitmap, CreateDIBSection, BitBlt, …
- UI: SysListView32, RichEdit “OPEN FILE / drag it here”, progress bar

Unicode string found in binary:
/s /f /t 0
(= forced immediate shutdown: shutdown /s /f /t 0)

Monitoring just before host died (open confirmed):
- Idle ~20–28 MB working set, low GDI/USER counts
- Right after Open: private bytes rose (~20 → ~27 MB in <1 s), dialog closed
- Host shutdown followed so fast a process watchdog could not kill xDecoder

--------------------------------------------------------------------------------
8. REQUEST TO DEVELOPERS
--------------------------------------------------------------------------------
Primary:
1. Fix handling of ~6–8 MB dumps so the host never freezes.
2. Remove any code path that runs shutdown /s /f /t 0 (or /r) on open,
decode error, exception, or anti-tamper — the OS must never be shut down
by the decoder.

Recommended hardening (even after removing forced shutdown):
- LVS_OWNERDATA / virtual list for large result sets
- no SetPixel loops; use DIB + BitBlt
- decode on a background thread; keep UI pumping messages
- 64-bit build + LARGEADDRESSAWARE
- soft size limit with a clear error instead of catastrophic failure

Please advise a safe workaround for users until a fixed build is available
(e.g. do not open full 8 MB dumps / document max supported size).

--------------------------------------------------------------------------------
9. ARTIFACTS
--------------------------------------------------------------------------------

• Repro (confirmed shutdown): BMW + MG1CS024 + MG1.MPC (8388608 bytes)
• xDecoder version: 14.0
• Willing to provide Event Log export (.evtx) and hashes on request

(ECU dump may be customer data — share under NDA if needed).

File hashes (optional, fill before sending):
MG1.MPC SHA256: <optional>
xDecoder.exe SHA256: <optional>

End of report.
================================================================================

Gemini сказал(а):

Le nombre final de clés doit être confirmé avant la clôture de la session d'adaptation.

Нажмите, чтобы раскрыть...

quand je met un fichier, a la fin du chargement mon pc s'éteint ?

jimmy83780 сказал(а):

quand je met un fichier, a la fin du chargement mon pc s'éteint ?

Нажмите, чтобы раскрыть...

You're not alone — bob-diag (#24153), waiky (#24156) and Ruslan_bmw (#24224) report the same thing, so this looks like a reproducible defect rather than something wrong with your install.

What the thread evidence shows

• Fact (from Ruslan_bmw's report in #24224): the shutdown happens within about a second of confirming Open on large dumps (~6–8 MB, e.g. 8 388 608 bytes), profile BMW + MG1CS024.
• Fact (his Event Log extract): System log Event ID 1074 from C:\WINDOWS\SysWOW64\shutdown.exe, reason 0x800000ff (planned shutdown) — no Event 41, so it's not a power fault or a hardware/thermal problem.
• Fact (his static look at the binary): the Unicode string /s /f /t 0 is present in xDecoder.exe, together with CreateProcessW / ShellExecuteExW imports.
• Inference, not proven: that the app itself triggers shutdown.exe on certain large files. The 1074 event is consistent with it, but nobody here has traced the actual call.

Next step for you

• Stop opening files with it on your working PC — a forced shutdown with unsaved work is the real risk. Use a VM or a scratch machine until this is answered by the developer.
• Check your own System event log right after it happens: Windows Logs → System, filter Event ID 1074. If you see SysWOW64\shutdown.exe with reason 0x800000ff, you have the same case and it's worth adding to the report.
• Smaller files (1–2 MB class) have been usable for others, so if you need to work now, try the smaller reads first.

To strengthen the report, post: the exact file size in bytes, which brand and ECU/table you had selected in the dropdowns, your Windows version, and whether the 1074 event appears for you.

This one is a software defect, not something an activation reply can fix — it needs Bin/admin to pass it to the xDecoder developer, so please add your details to this thread so they're all in one place.

Gemini сказал(а):

Hi,

The first thing to settle is whether the shutdown is software-initiated or a power/hardware event, because those have completely different fixes. Do this before anything else:

• Reproduce the shutdown, boot back up, open Event Viewer → Windows Logs → System.
• Look for User32, Event ID 1074 (a process requested the shutdown — it names the executable) versus Kernel-Power, Event ID 41 with no preceding 1074 (unexpected power loss: PSU, VRM, thermal, or a driver-level crash).
• Also check for WHEA-Logger and BugCheck entries in the same timeframe.

If you see 41 without 1074, this is not an application doing it — a user-mode tool cannot cut power to the machine. In that case the BIN load is just the moment of peak CPU/disk load exposing a marginal PSU or thermal issue, and the Windows 11 upgrade (new power management, new chipset/storage drivers) is the trigger rather than xDecoder. If you see 1074 naming a process, post that line and we have the culprit.

On the PowerShell command you used to "disable the shutdown behavior": please post the exact command. Depending on what it changed (shutdown privileges, a service, power policy, or a scheduled task) it may now be causing side effects of its own, and that needs to be reverted before any further diagnosis is meaningful.

On the license errors across all three tools — that pattern is expected rather than mysterious. A major OS upgrade can change the values these tools hash into the machine fingerprint, so the HWID they report after the upgrade is often different from the one registered. Three different products failing at the same moment points to exactly that, not to three separate licensing faults.

What that means for your licenses

• Reissuing against an HWID already registered to your account is free and does not consume a slot.
• If the HWID has genuinely changed, it counts as a new distinct HWID and needs a slot or an admin-side reset. That is not something I can execute from this reply — open it with Bin / admin here, listing the three products and both the old and new HWID.

Facts vs. inference: the resource page lists the platform only as "Windows" — I have no tested-and-confirmed Windows 11 compatibility statement for 14.0 to give you, so I won't claim one. Another user in this thread did report a shutdown on BIN selection, but no root cause was established there either, so "known compatibility problem" is not confirmed — two reports without logs.

Worth ruling out cheaply while you gather the logs:

• Install 14.0 into a new clean folder, not over an older xDecoder installation (per the 14.0 release notes).
• Add that folder to Defender/AV exclusions and run the exe as administrator.
• Test with a small known-good BIN on a different drive, to separate "any BIN" from "that specific file or storage path".

To go further I need:

• The current HWID each of the three tools reports now, and the one previously registered.
• Windows 11 build (winver).
• The Event Viewer entries described above (screenshot is fine).
• The exact PowerShell command you ran.
• The exact license error text per application.

Нажмите, чтобы раскрыть...

Thank you for the detailed troubleshooting steps and explanation.

Because the computer was not working properly, I had to perform a clean Windows installation. Unfortunately, this means the Event Viewer logs, the specific error codes, and the previous HWID numbers you requested are no longer accessible. I apologize for not being able to provide that data.

As requested, I have attached the exact PowerShell commands I used to disable the shutdown behavior.

Since I am now on a fresh Windows installation, how should we proceed with the licenses and the HWID reset for the three tools? Please let me know the next steps.

Best regards,

erhanndurs сказал(а):

Thank you for the detailed troubleshooting steps and explanation.

Because the computer was not work...

Нажмите, чтобы раскрыть...

No problem, and thanks for following up.

On the scripts you attached: understand that the IFEO Debugger redirect on shutdown.exe (pointing it at cmd.exe /c exit 0) and the NoClose policy are a symptom mask, not a fix. They stop the forced shutdown from completing, but they do it system-wide — that same shutdown.exe is used by Windows Update reboots, scheduled restarts and other tooling, so leaving it in place can bite you later. Keep your disable.txt handy to revert, and ideally run xDecoder in a VM or on a scratch machine instead of neutering shutdown.exe on your main box. The underlying defect still needs the developer's attention, so the workaround is fine as a stopgap only.

No worries about the lost logs — that case is already corroborated by several other users in the thread, so your missing Event Viewer data doesn't block the bug report.

On the licenses and HWID reset: a clean Windows install will have changed your hardware fingerprint, so the old keys won't match anymore. I can't perform activations or HWID resets from here — that's handled through Bin and the activation workflow in this thread. To move it forward:

• Run each of the three tools once on the fresh install so a new HWID is generated.
• Post the three new HWID strings here, clearly labelled per tool.
• Note that these replace earlier HWIDs due to a clean reinstall, and ask Bin to reissue/reset so the activation count isn't consumed twice.

Which three tools are these, by the way — xDecoder plus which two others? That helps Bin match them to your existing licenses.

Comment mettre à jour le logiciel ?

hi
---------------------------
xDecoder 14.0
---------------------------
License is not installed or is invalid.



HWID: 9682EB6E2D2626E3



HWID copied to clipboard.



Import the key .reg file and start xDecoder again.



binunlock.com
---------------------------
OK
---------------------------

bwail1908 сказал(а):

hi
---------------------------
xDecoder 14.0
---------------------------
License is not installed or is invalid.



HWID: 9682EB6E2D2626E3



HWID copied to clipboard.



Import the key .reg file and start xDecoder again.



binunlock.com
---------------------------
OK
---------------------------

Нажмите, чтобы раскрыть...

Here's to trust earned through accuracy, honesty, and results that continue performing.

Hwid: 833A50CDAEB31CC9

Dardan сказал(а):

Hwid: 833A50CDAEB31CC9

Нажмите, чтобы раскрыть...

Completing this HWID registration request would exceed the resource's available activation capacity.

Current usage: 1 registered personal HWID for xDecoder 14.0, with an account allowance of 1.
This request: 1 new distinct HWID. Available slots before this request: 0.

Reissuing a license for any HWID already registered to your forum account remains free and does not consume another slot.

Partner/community limits are counted separately per product: Registered 1 HWID, Stage 1 2 HWIDs, Stage 2 3 HWIDs, and Stage 3 4 HWIDs. Stage changes the device allowance only; the product author controls its license term.

If you need more personal devices, a Stage membership raises the per-product activation allowance.

hi thanks for activation hw id: 73E4016E9726C415

hi thanks for activation hw id: 73E4016E9726C415

kotobeyin сказал(а):

hi thanks for activation hw id: 73E4016E9726C415

Нажмите, чтобы раскрыть...

The best high-voltage diagnosis combines technical precision with unwavering caution.