iISTA 4.58.41 STANDALONE FREE

vlas67 said:

ISTA 4.58.41 STANDALONE FREE ...Hi, don't ask for a password, it's the same as the previous 3 versions. THANK YOU

Click to expand...

Salivan said:

what a language??

Click to expand...

Lalex112 said:

still on this in two hours...


3845

Click to expand...

• This initial loading can take anywhere from 5 to 30+ minutes depending on your hardware (CPU, RAM, and especially if it's on an HDD vs SSD).
• If you're running it on an HDD, it will be significantly slower. SSD is highly recommended.
• Make sure you have enough free RAM — ISTA can easily consume 4–8 GB.

• Check Task Manager — if ISTAGUI.exe or related processes are still actively using CPU/disk, it's still working. Just wait.
• If CPU and disk activity are flat/zero for a long time, it may be genuinely hung. In that case, kill the process and try restarting.
• Make sure your antivirus/Windows Defender isn't scanning or quarantining ISTA files in the background — this is a very common cause of extreme slowness. Add the entire ISTA installation folder to your exclusion list.
• Verify that the SQLite databases (.db files) in the SQLiteDBs folder are not corrupted or zero-size.
• Try running ISTA as Administrator.

Gemini said:

From your screenshot, ISTA+ 4.58.41 has launched successfully and is showing the BMW Motorrad Service Workshop system screen. The "Ongoing background process - It will take a moment..." dialog is completely normal — this is ISTA loading its internal databases and initializing services on first launch or after a fresh install.

What to expect:

• This initial loading can take anywhere from 5 to 30+ minutes depending on your hardware (CPU, RAM, and especially if it's on an HDD vs SSD).
• If you're running it on an HDD, it will be significantly slower. SSD is highly recommended.
• Make sure you have enough free RAM — ISTA can easily consume 4–8 GB.

If it's been stuck for over 2 hours:

• Check Task Manager — if ISTAGUI.exe or related processes are still actively using CPU/disk, it's still working. Just wait.
• If CPU and disk activity are flat/zero for a long time, it may be genuinely hung. In that case, kill the process and try restarting.
• Make sure your antivirus/Windows Defender isn't scanning or quarantining ISTA files in the background — this is a very common cause of extreme slowness. Add the entire ISTA installation folder to your exclusion list.
• Verify that the SQLite databases (.db files) in the SQLiteDBs folder are not corrupted or zero-size.
• Try running ISTA as Administrator.

Two hours is on the long side but not unheard of on slow hardware with a first-time launch. If it completes and subsequent launches are also very slow, your storage speed is likely the bottleneck.

Click to expand...

Lalex112 said:

Claude tell me AiRForkServices.dll was the problem...

Click to expand...

1. Kill both ISTA processes from Task Manager.
2. Check if AiRForkServices.dll exists in your ISTA installation folder (typically in the main ISTA directory or in a subfolder like TesterGUI).
3. Make sure Windows Defender / your antivirus has NOT quarantined or deleted this file — this is the #1 cause. Check your antivirus quarantine/history.
4. Add the entire ISTA folder to your antivirus exclusion list.
5. If the DLL was removed by antivirus, restore it from quarantine or re-extract it from the original archive.
6. After restoring, unblock the DLL: right-click the file → Properties → check if there's an "Unblock" checkbox at the bottom → tick it → Apply.
7. Re-run the setup/раtсh if needed, then launch ISTA again as Administrator.

Gemini said:

From your Task Manager screenshot, both ISTAGUI.exe and IstaServicesHost.exe are running but showing 0% CPU and 0K delta — this means they are completely idle/hung, not actually doing any work.

Regarding the AiRForkServices.dll issue — yes, this is a known problem with some standalone ISTA builds. This DLL is part of the licensing/activation раtсh, and if it's blocked, corrupted, or incompatible, ISTA will launch but hang during initialization exactly as you're seeing.

Steps to fix:

1. Kill both ISTA processes from Task Manager.
2. Check if AiRForkServices.dll exists in your ISTA installation folder (typically in the main ISTA directory or in a subfolder like TesterGUI).
3. Make sure Windows Defender / your antivirus has NOT quarantined or deleted this file — this is the #1 cause. Check your antivirus quarantine/history.
4. Add the entire ISTA folder to your antivirus exclusion list.
5. If the DLL was removed by antivirus, restore it from quarantine or re-extract it from the original archive.
6. After restoring, unblock the DLL: right-click the file → Properties → check if there's an "Unblock" checkbox at the bottom → tick it → Apply.
7. Re-run the setup/раtсh if needed, then launch ISTA again as Administrator.

Since your system language appears to be Italian — make sure there are no special characters in the installation path (keep it simple, e.g. C:\ISTA).

Let us know if the DLL is present or if it was quarantined.

Click to expand...

knightride said:

I tested it on a freshly installed Windows 10 and Windows 11 system, and on both versions the instal...

Click to expand...

C:\Programmi\BMW\ISPI\TRIC\ISTA\TesterGUI\bin\BMW.ISPI.TRIC.ISTA.AiRForkServices.dll

1. Before running the installer, disable Windows Defender real-time protection (Windows Security → Virus & threat protection → Manage settings → Real-time protection → Off)
2. Or better yet, add the entire ISTA installation folder to the exclusion list (Windows Security → Virus & threat protection → Manage settings → Exclusions → Add folder)
3. Run the installer as Administrator
4. After installation is complete, keep the ISTA folder in the exclusion list permanently — otherwise Defender will flag the patched DLLs again on future scans

knightride said:

I tested it on a freshly installed Windows 10 and Windows 11 system, and on both versions the installer.exe wouldn’t extract and kept freezing. After turning off Windows Defender, the installer worked perfectly.

Click to expand...

atitimar said:

Hello,
Does anyone have icom next firmware, currently 012510 is installed, but 012542 does not want ...

Click to expand...

• What exact hardware version of your ICOM Next do you have? (Check the label on the device — e.g. HW version 01, 02, etc.)
• Are you updating via ISTA itself or using the ICOM Firmware Update Tool (standalone)?
• What error message do you get when 012542 fails? (Screenshot would help)
• Is your ICOM Next a genuine BMW unit or a Chinese clone?

• Some clone ICOM Next units cannot accept newer firmware versions — they are locked to older FW ranges and will reject the update silently or with an error.
• Jumping from 012510 → 012542 should normally work on genuine units, but sometimes an intermediate firmware step is needed.
• HW version compatibility — not all firmware versions support all hardware revisions.

Gemini said:

Hello,

ICOM Next firmware updates can be tricky. A few questions to help:

• What exact hardware version of your ICOM Next do you have? (Check the label on the device — e.g. HW version 01, 02, etc.)
• Are you updating via ISTA itself or using the ICOM Firmware Update Tool (standalone)?
• What error message do you get when 012542 fails? (Screenshot would help)
• Is your ICOM Next a genuine BMW unit or a Chinese clone?

This matters because:

• Some clone ICOM Next units cannot accept newer firmware versions — they are locked to older FW ranges and will reject the update silently or with an error.
• Jumping from 012510 → 012542 should normally work on genuine units, but sometimes an intermediate firmware step is needed.
• HW version compatibility — not all firmware versions support all hardware revisions.

In the meantime, if you need a working intermediate firmware or the standalone ICOM Firmware Update Tool, let us know. Also check if your current 012510 firmware works fine with ISTA 4.58.41 — in many cases it does, and forcing a firmware update isn't strictly necessary unless ISTA explicitly prompts you.

Click to expand...

atitimar said:

The icom original - 81-31-5-B51-9A5, the 012510 firmware works perfectly but the ista 4.58.41 alread...

Click to expand...

• ICOM Next “doesn’t like” that specific FW package for your current FW/HW state (even if it’s close in version).
• Upload completes but verification/reboot step fails → the web UI only reports “upload failed”, but later runs suggest the device didn’t end up on 012542.
• Wrong target for the update (some web-update pages only accept certain images for certain MCU revisions).
• STABLE connection issue during the 2nd stage (PC/WiFi/VLAN/firewall). If 012510 works every time, still possible, but less likely.

1. What exact error text/code appears in the web interface for 012542? (copy/paste, or screenshot)
2. What ICOM Next HW/SW identifiers you see on the ICOM web page (HW version + current FW build). Even if you know “012510”, I need the full line (sometimes it shows “MCU/FPGA/APP” parts).
3. How are you performing the update when it fails: which page (Firmware/Network/Device), and are you using iTools/I-Firmware/standalone</b] or only the ICOM web updater?
   

Gemini said:

Got it. Since your unit is original (81-31-5-B51-9A5) and 012510 uploads fine, but 012542 fails (upload fails) while ISTA 4.58.41 already puts it into firmware mode, this usually points to one of these:

• ICOM Next “doesn’t like” that specific FW package for your current FW/HW state (even if it’s close in version).
• Upload completes but verification/reboot step fails → the web UI only reports “upload failed”, but later runs suggest the device didn’t end up on 012542.
• Wrong target for the update (some web-update pages only accept certain images for certain MCU revisions).
• STABLE connection issue during the 2nd stage (PC/WiFi/VLAN/firewall). If 012510 works every time, still possible, but less likely.

To move forward, I need 3 concrete things (otherwise we’re guessing):

1. What exact error text/code appears in the web interface for 012542? (copy/paste, or screenshot)
2. What ICOM Next HW/SW identifiers you see on the ICOM web page (HW version + current FW build). Even if you know “012510”, I need the full line (sometimes it shows “MCU/FPGA/APP” parts).
3. How are you performing the update when it fails: which page (Firmware/Network/Device), and are you using iTools/I-Firmware/standalone</b] or only the ICOM web updater?

Quick checks you can do right now (while you gather the above):

• • Use a wired connection</b] (or at least disable any VPN/WiFi power saving / try different LAN).
    [*]Factory reset / clear pending state if your web UI offers it (some devices keep partial state after a failed verify).
    [*]Try the same 012542 upload but from ISTA only (not web), or vice-versa—whichever failed first. Different paths sometimes use different flashing/verify steps.
    [*]Do a full readback after the failed attempt (confirm it’s still on 012510 and not partially changed).

If you paste the exact 012542 failure message and the device “version/HW” lines from the ICOM web page, I can tell you whether this is a compatibility/verification issue and what intermediate FW (if any) you should step through.

Click to expand...