ISTA 4.59.30 Full programming

roman66 said:

ISTA 4.59.30
Full version of BMW ISTA-PLUS with programming
German English Russian

Works with D-CAN, ENET, ICOM A1, A2, and NEXT

Uninstall the previous version of ISTA before installation!
Ideally, install on a clean system.
BEFORE INSTALLING, YOU MUST:
Run the uninstaller for the previous version, if available.
Delete all possible ISTA folders:
"C:\Program Files\BMW"
"C:\ProgramData\BMW"
"C:\EC-APPS\ISTA"
"C:\ISTA"
"C:\Users\Username\AppData\Roaming\ISTA"
Delete the following Registry key branches:
"\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMW"
"\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMWGroup"
"\HKEY_LOCAL_MACHINE\SOFTWARE\BMW"
"\HKEY_LOCAL_MACHINE\SOFTWARE\BMWGroup"

INSTALLATION:
‣1. Disable Windows Defender and other antivirus programs during installation.
‣2. Install 7ZIP (if it is not already installed).
‣4. Install all add-ons from the Windows folder.
‣5. Run the "BMW ISTA+ Standalone.exe" file.
(The installation may take up to 3 hours, but it is easier to leave it overnight ).
‣6. Add the "C:\Program Files\BMW" folder to Windows Defender exceptions.
(At this point, ISTA is ready for use in diagnostic mode; you do not need to download and paste "PSDZ Lite.")
‣7. Full version with programming: activate the "full-with-programming" registry file, download and unzip "PSdZData 4.59.21 full" to "C:\Program Files\BMW\ISPI\TRIC\ISTA\PSdZ\data_swi"
OR create a symbolic link if you need the full "PSDZ" database to be located elsewhere. To do this, open "CMD" as administrator and enter the command (example):
mklink /D "C:\Program Files\BMW\ISPI\TRIC\ISTA\PSdZ\data_swi" "C:\EC-APPS\PSDZ\data" —
where the first quotation marks indicate the desired path to "PSDZ" in "ISTA," and the second quotation marks indicate the actual path to "PSDZ."
‣8. Russian language support: Unzip the "RU SQLiteDBs" archive to "C:\Program Files\BMW\ISPI\TRIC\ISTA\SQLiteDBs" and change the language in the settings.

For "DCAN" users:
Before launching "ISTA," launch "ICOM-ENET or DCAN Switch" and change the settings to "DCAN."
After connecting the DCAN adapter, change the settings in the Device Manager properties to "Port number COM3, timeout 1 ms."

Click to expand...

• Antivirus / Windows Defender — Disable it completely during the installation. This is the number one cause of this freeze. At a minimum, add an exclusion for the entire installation folder.
• Disk space — Make sure you have at least 50–60 GB free on C:.
• Run as administrator — Right-click on BMW ISTA+ Standalone.exe → Run as administrator.
• Complete cleanup — Before trying again, make sure to delete all remnants as indicated in the first post (BMW folders + registry keys).
• UAC — Temporarily lower User Account Control to the minimum.

Gemini said:

The "Installer is no longer responding" error during the "Updating component registration" step is fairly common. Here are the things to check:

1. Do not click too quickly
This step can take a very long time (sometimes 20–30 minutes or more), and Windows displays "not responding" even though the installer is still working in the background. Before clicking "Retry" or "Cancel", open Task Manager and check whether the process is still using CPU or disk resources. If it is, let it run.

2. Checks before reinstalling

• Antivirus / Windows Defender — Disable it completely during installation. This is the number one cause of this issue. At the very least, add an exclusion for the entire installation folder.
• Disk space — Make sure you have at least 50–60 GB free on C:.
• Run as administrator — Right-click BMW ISTA+ Standalone.exe → Run as administrator.
• Complete cleanup — Before trying again, make sure to remove all remaining files as indicated in the first post (BMW folders + registry keys).
• UAC — Temporarily lower User Account Control to the minimum.

3. Additional tip
Start the installation with the Internet connection unplugged/disabled. Some components try to check certificates online, and this can cause a timeout that blocks the installer.

Try again with these precautions and let us know whether it works.

Click to expand...

edhweb said:

antivirus and related protections disabled, 600 GB of space, ISTA run as admin, no leftover files...

Click to expand...

• name du/des visible processes
• CPU and Disk: is it still running, or is everything at 0?

• C:\ProgramData\BMW (often there)
• or the installer folder (setup.exe) where you started the installation

• Windows 10 or 11?
• 64-bit?
• Are you reinstalling on the same machine after repeated failure, or is this a first clean attempt recently?

• Ouvre gpedit.msc (Éditeur de stratégie de groupe locale)
• Va dans : Configuration ordinateur → Modèles d'administration → Composants Windows → Antivirus Microsoft Defender
• Active la stratégie "Désactiver l'antivirus Microsoft Defender" → Activé
• Redémarre le PC
• Vérifie dans le Gestionnaire des tâches que Antimalware Service Executable n'apparaît plus

• C:\Windows\Temp\ — supprime tout
• %TEMP% (tape ça dans la barre d'adresse de l'explorateur) — supprime tout
• Ouvre regedit et vérifie que ces clés n'existent pas/plus :
  
  Code:

  HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMW
  HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMWGroup

• Redémarre après avoir tué Defender
• Clic droit → Exécuter en tant qu'administrateur
• Quand ça arrive à "Updating component registration", ne touche à rien — cette fois sans Defender ça devrait passer

Gemini said:

La capture est très parlante. Deux problèmes visibles :

1) L'installeur est complètement figé
BMW Group ISTA Installer (32 bit) et Windows® Installer (32 bits) sont tous les deux à 0% CPU et 0 Mo/s disque — rien ne travaille, c'est un vrai blocage.

2) Antimalware Service Executable est toujours actif
Tu vois Antimalware Service Executable à 142,7 Mo de RAM — Windows Defender tourne encore malgré ce que tu penses avoir désactivé. C'est très probablement lui qui bloque la registration des composants.

Ce qu'il faut faire :

Étape 1 — Vraiment tuer Defender
Désactiver dans les paramètres ne suffit pas toujours :

• Ouvre gpedit.msc (Éditeur de stratégie de groupe locale)
• Va dans : Configuration ordinateur → Modèles d'administration → Composants Windows → Antivirus Microsoft Defender
• Active la stratégie "Désactiver l'antivirus Microsoft Defender" → Activé
• Redémarre le PC
• Vérifie dans le Gestionnaire des tâches que Antimalware Service Executable n'apparaît plus

Si tu es sur Windows 10/11 Home (pas de gpedit), utilise Defender Control (de Sordum) pour le désactiver complètement.

Étape 2 — Nettoyer les restes de l'install ratée
Même si tu ne vois pas les dossiers BMW :

• C:\Windows\Temp\ — supprime tout
• %TEMP% (tape ça dans la barre d'adresse de l'explorateur) — supprime tout
• Ouvre regedit et vérifie que ces clés n'existent pas/plus :
  
  Code:

  HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMW
  HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMWGroup

Étape 3 — Relancer l'installation

• Redémarre après avoir tué Defender
• Clic droit → Exécuter en tant qu'administrateur
• Quand ça arrive à "Updating component registration", ne touche à rien — cette fois sans Defender ça devrait passer

Dis-moi ta version de Windows (10 ou 11, Home ou Pro) si tu n'arrives pas à accéder à gpedit.

Click to expand...

edhweb said:

windows 10 64

Click to expand...

• First: Home or Pro?
  Tell me whether you are using Windows 10 Home or Windows 10 Pro (Settings → About).
• When it gets stuck
  Open Task Manager → Details and check:
  • the process is indeed called Antimalware Service Executable
  • its CPU</b] et/ou Disque</b> usage is > 0 when the installation “stops responding”
    
  
  

Gemini said:

Okay, Windows 10 x64.

In your previous screenshots, we can clearly see Antimalware Service Executable → so Defender is not actually “disabled,” and it may be blocking Updating component registration.

• First: Home or Pro?
  Tell me whether you are using Windows 10 Home or Windows 10 Pro (Settings → About).
• When it gets stuck
  Open Task Manager → Details and check:
  • that the process is indeed called Antimalware Service Executable
  • that its CPU</b] et/ou Disque</b> is > 0 when the installation “stops responding”
    

Then I’ll give you the exact proper method to disable it permanently depending on Home/Pro.
To save time: start by answering the 2 points above.

Click to expand...

edhweb said:

home

Click to expand...

• that the process is indeed called Antimalware Service Executable ?
• and that it is using CPU et/ou Disk (value > 0) when it “stops responding”?

• run Defender Control as admin
• select Disable Windows Defender (and disable real-time protection if prompted)
• restart
• rerun the ISTA installation

Gemini said:

OK, Home.

While the installation is “frozen,” open Task Manager → Details and check:

• the process is indeed called Antimalware Service Executable ?
• does it use CPU et/ou Disk (value > 0) when “it stops responding”?

If so, Defender is still active and may block the install (so C:\ProgramData\BMW peut ne jamais appear until the registration step has gone through).

For Windows 10 Home (no gpedit), do a “hard” disable using Defender Control (Sordum) :

• run Defender Control as admin
• set Disable Windows Defender (and disable real-time protection if prompted)
• restart
• restart the ISTA installation

Reply with the 2 pieces of info from point (1) (exact name + CPU/Disque > 0) and I’ll tell you what to check next if C:\ProgramData\BMW ne se still doesn’t create it.

Click to expand...

reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release

• Download and install (or repair) Visual C++ Redistributable 2013, 2015-2022 in both x86 AND x64
• Restart after installation

msiexec /unregister
msiexec /regserver

• Delete the folder C:\Users\<ton user>\AppData\Roaming\BMWGroup
• Clear %TEMP% and C:\Windows\Temp
• Right-click → Run as administrator on the ISTA installer

Gemini said:

Good news: this time Antimalware Service Executable no longer appears in the list — Defender is definitely disabled. But the installer is still stuck at 0% CPU / 0 Mo/s disk at the same point ("Updating component registration").

The folder in C:\Users\<ton user>\AppData\Roaming\BMWGroup is normal — some configuration files go there first. The real problem is that the installer dies before finishing the component registration.

Let's try something else:

1) Check .NET Framework
ISTA requires .NET Framework 4.8 minimum. Open a command prompt (as administrator) and type:

Code:

reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release

If the value is lower than 528040, you don't have .NET 4.8. Install it manually from the Microsoft website before trying again.

2) Check the Visual C++ Redistributables
The ISTA installer registers C++ components (hence "component registration"). If the redistributables are corrupted, this can cause it to hang.

• Download and install (or repair) Visual C++ Redistributable 2013, 2015-2022 in x86 AND x64
• versions
  Restart after installation

3) Repair Windows Installer
The Windows® Installer (32 bits) process is stuck too. Open an administrator command prompt and run:

Code:

msiexec /unregister
msiexec /regserver

Restart.

4) Restart the installation
After the 3 steps above:

• Delete the C:\Users\<ton user>\AppData\Roaming\BMWGroup
• folder
  Empty %TEMP% and C:\Windows\Temp
• Right-click → Run as administrator on the ISTA installer

Tell me the result of the .NET command and whether it works after these cor

Click to expand...

1. DO NOT CLICK Retry or Cancel
2. Let it run. It may take 15–30 minutes or even longer depending on your drive.
3. Monitor Windows® Installer in Task Manager: as long as it is using CPU et/ou and Disk, the installation is progressing.
4. It is only finished when Windows® Installer drops back to 0% CPU / 0 Mo/s Disk AND the ISTA window changes state (moves to the next step or closes).

Gemini said:

This screenshot is very different from the previous ones, and that's good news :

Windows Installer® is at 51.8% CPU and 79.2 Mo/s disk — it's working hard! The BMW Group ISTA Installer (32 bit) process is at 0% CPU, but that's normal; it's waiting for Windows Installer to finish registering the components.

The installation is NOT stuck this time. The message "Installer is no longer responding" is misleading — Windows displays it because the ISTA Installer window is not responding while Windows Installer is working in the background.

What you need to do:

1. DO NOT CLICK on Retry or Cancel
2. Let it run. It may take 15–30 minutes or even longer depending on your disk.
3. Monitor Windows Installer® in Task Manager: as long as it is using CPU et/ou Disk, the installation is progressing.
4. It is finished only when Windows Installer® drops to 0% CPU / 0 Mo/s disk AND the ISTA window changes status (moves to the next step or closes).

As long as Windows Installer is running → don't touch anything. Come back and tell us what happens once it has finished.

Click to expand...