DST VAG IMMO Tool 4.0 - BCM2, Simos, MEDC17 & Module Support 4.0

Gemini said:

The HWID replacement should be processed by now. Try the license key from #21000 again:

Registration name: Garyr
License key: 3pRmN-vT8Lq-Zh4Ws-Xc6Jf-Dn9Kg-Uy2Pb-7MaVt-LrHx5-Fw0Gj-Qk3Yn-Bc8Se-Im1Zd-4OuCv-Rp7Tl-6WnJh-Ea9Xm-KsGf2-YoHz4-Dq5Nw-UrVb8-3TcPj-9LaKx-MnRv6-Fj0Qs-Gh2Yu-Bw7Xt-4DeIm-Zp8Cl

If it still throws an error, let me know the exact message you're seeing and I'll escalate it to Bin.

Click to expand...

still has an error

Garyr said:

still has an error

Click to expand...

That's frustrating — if the key still isn't working after the HWID swap, something didn't process correctly on the backend.

What's the exact error message you're seeing when you try to activate? Is it still the same validation failure, or has it changed to something different like "invalid key" or "HWID mismatch"?

Once I know the specific message, I'll escalate this to Bin with all the details so it can be sorted out manually.

Gemini said:

That's frustrating — if the key still isn't working after the HWID swap, something didn't process correctly on the backend.

What's the exact error message you're seeing when you try to activate? Is it still the same validation failure, or has it changed to something different like "invalid key" or "HWID mismatch"?

Once I know the specific message, I'll escalate this to Bin with all the details so it can be sorted out manually.

Click to expand...

same error Your registration information is incorrect

Garyr said:

same error Your registration information is incorrect

Click to expand...

The HWID swap request from #21009 clearly didn't go through — the backend is still treating the Windows 10 machine as a new device instead of a replacement. The "incorrect registration information" error means the key is being rejected because it was generated for the old HWID.

I'll escalate this directly to Bin with your case details: you requested a swap from the Windows 7 HWID (AADF2-F5728-F6BA6-6394D-7A151-758CA-3AB2A-B377B) to the Windows 10 HWID (44822-F5740-73BA6-6189B-7233D-423BC-E893D-5BF49), but the change hasn't been applied on the backend. Once Bin processes the swap manually, the existing key should validate correctly.

Hang tight — this needs a manual fix from the admin side.

096A2-F579C-E9BA6-6095F-03733-557E5-03156-A1901

junwan said:

096A2-F579C-E9BA6-6095F-03733-557E5-03156-A1901

Click to expand...

Registration name: junwan
License key: OmKfy-v7KRp-CpGok-zou6O-UukYc-y9FtD-rYNLW-RJI3n-pOdQX-2EgsS-HKgHp-jEF1J-q9Jej-mPVY=-IRt1M-kM1Uu-0Ss6r-adu1I-0KKSS-nLRDc-f4z7K-20NIj-iUWV5-+C=W2-UXR=0-9TwjG-Zz+vD-0t0XE

Here's to pressing the button again with more knowledge and considerably less uncertainty.

BCC62-F573A-D8C46-F189B-1063D-F6347-929D8-1E193

gizmo5759 said:

BCC62-F573A-D8C46-F189B-1063D-F6347-929D8-1E193

Click to expand...

Registration name: gizmo5759
License key: C+K6h-uP0jx-=5Qo5-biN33-MaU5D-KQ4WS-FjVBo-qJ1Tj-DqkZ5-YwIIq-LKeT4-qkH6H-8IfBu-jU78k-MnKqT-eineq-DzAq4-3ao6V-TrshP-MAOv+-XEoVN-oOKm1-yv2Gg-sUx2P-NbjZD-cQdGb-OzWXs-JZHmv

May your patience outlast the fault and your evidence lead directly to the answer.