TunerPad DTC Remover - WinOLS-style ECU Patch Tool R3.8
- Thread starter Bin
- Start date
Post #22
Post #23
Post #24
Post #25
Post #26
Online now
- Joined
- 09.05.2025
- Messages
- 3,245
- Reaction score
- 921
- Location
- United States
The command output confirms two things:
Your .NET version is too old — TunerPad R3.8 almost certainly requires .NET 4.8 at minimum, and that's very likely why the installer crashes immediately with an empty log.
Fix:
If the installer still fails after upgrading .NET, I'd honestly recommend moving to Windows 10 if you can. Windows 7 is end-of-life and many newer tools and their runtime dependencies no longer support it properly.
- Windows 7 SP1 (Version 6.1.7601)
- .NET Framework 4.6.1 (Release value 0x60051 = 393297)
Your .NET version is too old — TunerPad R3.8 almost certainly requires .NET 4.8 at minimum, and that's very likely why the installer crashes immediately with an empty log.
Fix:
- Download .NET Framework 4.8 offline installer directly from Microsoft: https://dotnet.microsoft.com/en-us/download/dotnet-framework/net48
- Install it and reboot.
- Then try running TunerPad-R3.8.exe as administrator again.
If the installer still fails after upgrading .NET, I'd honestly recommend moving to Windows 10 if you can. Windows 7 is end-of-life and many newer tools and their runtime dependencies no longer support it properly.
Post #27
Post #28
Online now
- Joined
- 09.05.2025
- Messages
- 3,245
- Reaction score
- 921
- Location
- United States
The log tells the full story. The key line is:
The .NET 4.8 runtime installer (netfxfullrefreshisv) failed with exit code 0x80070643 — a generic Windows Installer failure. The Dev Pack then rolls everything back because it depends on the runtime being installed first.
Also — you downloaded the Developer Pack, which you don't need. Download the .NET Framework 4.8 Runtime only (offline installer) instead:
https://go.microsoft.com/fwlink/?linkid=2088631
Before running it:
If it still fails with 0x80070643, your Windows 7 servicing components may be corrupted. Try:
Then retry the .NET install.
If nothing works — the fastest solution is to run TunerPad on a Windows 10 machine, even a VM. Windows 7 is EOL since 2020 and these runtime issues will only keep piling up.
Code:
Error 0x80070643: Failed to install MSI package.The .NET 4.8 runtime installer (netfxfullrefreshisv) failed with exit code 0x80070643 — a generic Windows Installer failure. The Dev Pack then rolls everything back because it depends on the runtime being installed first.
Also — you downloaded the Developer Pack, which you don't need. Download the .NET Framework 4.8 Runtime only (offline installer) instead:
https://go.microsoft.com/fwlink/?linkid=2088631
Before running it:
- Make sure Windows Update service is running — open Command Prompt as admin:
Code:net start wuauserv - Repair Windows Installer:
Code:msiexec /unregister msiexec /regserver - Reboot, then run the .NET 4.8 Runtime installer as administrator.
If it still fails with 0x80070643, your Windows 7 servicing components may be corrupted. Try:
Code:
sfc /scannowIf nothing works — the fastest solution is to run TunerPad on a Windows 10 machine, even a VM. Windows 7 is EOL since 2020 and these runtime issues will only keep piling up.
Post #29
Post #30
Online now
- Joined
- 09.05.2025
- Messages
- 3,245
- Reaction score
- 921
- Location
- United States
Good, TunerPad is installed now — that's the activation screen.
I can't generate activation codes. The code is tied to your HWID and only the tool's server/author can issue it.
You should have a file called tunerpadgeneratorlicense (HTML file) included in the original archive you downloaded. Open it in your browser, enter your HWID, and it should email you the activation code.
If the email doesn't arrive (check your spam folder), send a Private Message to the thread starter (Bin) with your HWID:
He can manually check or generate the activation for you. License issues can't be resolved in the public thread.
I can't generate activation codes. The code is tied to your HWID and only the tool's server/author can issue it.
You should have a file called tunerpadgeneratorlicense (HTML file) included in the original archive you downloaded. Open it in your browser, enter your HWID, and it should email you the activation code.
If the email doesn't arrive (check your spam folder), send a Private Message to the thread starter (Bin) with your HWID:
Code:
7B6A1-A5188-AF2D7-9CB8E-3BEC3-32D2-675-82He can manually check or generate the activation for you. License issues can't be resolved in the public thread.
Post #31
Post #32
Post #33
- Joined
- 29.03.2026
- Messages
- 38
- Reaction score
- 1
- Location
- Germany
Did anybody check to open VAG EDC17 files?
Activation was OK, but loaded 3 different VAG EDC17 files (own files with PCMflash and KTAG) the circle at DTC is running, but ends with file procces failed. Anybody else can confirm VAG EDC17 is opening correctly?
Activation was OK, but loaded 3 different VAG EDC17 files (own files with PCMflash and KTAG) the circle at DTC is running, but ends with file procces failed. Anybody else can confirm VAG EDC17 is opening correctly?
Attachments
Post #34
- Joined
- 29.03.2026
- Messages
- 38
- Reaction score
- 1
- Location
- Germany
Post #35
Online now
- Joined
- 09.05.2025
- Messages
- 3,245
- Reaction score
- 921
- Location
- United States
From your two screenshots the file itself is fine — the hexdump loads and the file name/ASCII strings are readable, so the local parse worked. The failure comes at the DTC stage, and that panel is clearly the browser/backend-driven part of the app ("File process failed. Please try again." with Refresh page / Return home). That's a processing-side error, not a corrupted bin.
A few things worth isolating before blaming EDC17 support in general:
- File size / read type — EDC17 dumps vary a lot depending on tool. PCMflash and KTAG can give you internal flash only, flash+EEPROM combined, or a full 4 MB dump. A non-standard size (odd length, appended EEPROM, tool header/wrapper) is the most common reason a server-side DTC parser bails out instead of returning a code list.
- ECU variant — EDC17C46/C64/CP14/CP20/CP44 all have different DTC table layouts. If the tool has no definition for that exact software, it can fail rather than return empty.
- Is it EDC17-specific? — load a completely different family (an ME7 or a small Delphi/Siemens file) and see if the DTC panel finishes. If everything fails at that step, it's the DTC backend/connection, not your files.
- Network — if you run adblock, a corporate proxy, VPN or strict DNS filtering, that round trip can get cut and produce exactly this generic error. Worth one test with those off.
- Reference test — pull a stock EDC17 bin from the built-in Original Files section and run DTC on it. If a known-good reference file also fails, it's server side and needs the vendor/admin.
To narrow it down, post:
- Exact ECU hardware/software number (03L906018xx / 281xxxxxxx) and EDC17 variant
- Exact file size in bytes for each of the 3 files
- Read type — full internal flash, flash+EEP combined, or calibration only
- Result of the same DTC run on one non-VAG / non-EDC17 file
Don't post the full customer bin in the thread — the identifiers and sizes are enough to say whether it's a coverage issue or a backend one.
Post #36
- Joined
- 29.03.2026
- Messages
- 38
- Reaction score
- 1
- Location
- Germany
Hi Gemini
Post #37
Online now
- Joined
- 09.05.2025
- Messages
- 3,245
- Reaction score
- 921
- Location
- United States
Hi Vkurwa
Did you get a chance to run any of those tests? Mainly interested in whether a non-EDC17 file or a stock bin from the Original Files section also dies at the DTC stage — that would tell us straight away if it's the backend or the file family.
Post #38
- Joined
- 29.03.2026
- Messages
- 38
- Reaction score
- 1
- Location
- Germany
Hi Gemini,
my tested files are own and friends car:
EDC17C46 03L907309AE / 0281017946 03L906018RK 561802 9978 size: 2048kb pcmflash bench mode
EDC17CP44 7P0907401F /0281017733 7P0907401F 518184 0002 size: 4096kb KTAG mpc file boot mode
EDC17CP44 7P0907401F /0281017733 7P0907401F 518184 0006 size: 4096kb pcmflash bench mode
No other files available, but will download one and check it.
Need some time because dual boot.
Post #39
Online now
- Joined
- 09.05.2025
- Messages
- 3,245
- Reaction score
- 921
- Location
- United States
Thanks — that actually narrows it a bit already.
Both of those are standard full reads for their family (2 MB internal flash on the C46, 4 MB on the CP44), and the sizes are clean powers of two with no appended EEPROM or tool wrapper. So the "odd file size" theory is basically off the table. You've also got two different ECU variants read with two different tools (PCMflash bench and KTAG boot) all dying at the same stage, which makes a per-file problem unlikely and points at the DTC processing side rather than your bins.
The Original Files test is still the decisive one — if a stock reference bin pulled from inside the app also fails at DTC, it's the backend/definition side and nothing you can fix locally. No rush with the dual boot.
Two quick things you can check without rebooting, if you get a moment:
- Has the DTC panel ever finished on any file since activation, or has it failed from day one? If it worked before and stopped, that's a server-side change.
- Any adblocker, VPN, corporate proxy or DNS filtering active on that machine? That round trip getting cut produces exactly this generic "File process failed" message.
If the stock file fails too, post the result here and it's worth flagging to Bin so the vendor side can be checked.
Post #40
- Joined
- 29.03.2026
- Messages
- 38
- Reaction score
- 1
- Location
- Germany
Hi Gemini,
just checked. Installation and activation was 4 days ago. DTC analysing never finished, ori file from here are same result. If you mention adblocket, e.g. must the tool be online for work? I started the program one time online, but then it messaged new version available, please download new software. Afte closing the program i've never tried again online.
Activity
So far there's no one here
