ISTA+ STANDALONE BMW Diagnostic & Coding - Workshop Solution 4.59.12

Gemini · 18.02.2026

pethconi said:
Did make the fixreg, and verrified that the files are in place on the dir, in step 3. All correct.
B...

I apologize, I made a mistake in the previous Registry code. I missed the Header Path, so the file you created didn't know *where* to save the settings. That is why the Registry is still empty and ISTA is crashing during the loading bar (it looks for the path, can't find it, and crashes).

Please create the file again with this CORRECT code.

1. Create the Correct Registry Fix
1. Open Notepad.
2. Copy the code below EXACTLY (make sure to include the line starting with [HKEY...):

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMWGroup\ISPI\Rheingold]
"InstallPath"="C:\\ISTA"
"BMW.Rheingold.Programming.ExpertMode"="Enabled"
"BMW.Rheingold.Programming.Enabled"="True"
"BMW.Rheingold.Online.Mode"="False"

3. Save as FixISTA_v2.reg.
4. Important: In the Save dialog, choose "All Files" for the file type.
5. Run the file and click Yes to confirm.

2. Verify the Fix
1. Press Windows Key + R, type regedit.
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMWGroup\ISPI\Rheingold.
3. Now you should see InstallPath on the right side pointing to C:\ISTA.

3. Check the Logs (If it still crashes)
If it still crashes after the Registry is fixed:
1. Go to C:\ISTA\Logs.
2. Delete all files inside (to clear old errors).
3. Run ISTAGUI.exe again until it crashes.
4. Open the new Log file in that folder.
5. Scroll to the very bottom and paste the last 5-10 lines here. This will tell us exactly why it is stopping.

pethconi · 18.02.2026

did it, and the installpath is there now. It wasent there before. But checked the map after re starting but no LOGS directory...
and still the error window !

Gemini · 18.02.2026

pethconi said:
did it, and the installpath is there now. It wasent there before. But checked the map after re start...

Since the Logs folder is not being created, the application is crashing before it can even start writing its own diary. This confirms a low-level system crash (usually .NET or Windows related).

Because you manually edited the ISTAGUI.exe.config file, there is a high chance the file structure was broken (invalid XML), or the version mismatch is still present.

Please follow these steps to find the real cause using Windows tools:

1. Check Windows Event Viewer
Since ISTA isn't creating logs, Windows is capturing the crash.
1. Right-click the Start button and select Event Viewer.
2. On the left, expand Windows Logs -> Application.
3. Look for a generic Error icon (Red circle with !) at the very top of the list (timestamp should match your last attempt).
4. Click it.
5. In the box below, look for Exception Info or Faulting Module Name.
* Does it say KERNELBASE.dll?
* Does it say System.Data.SQLite.dll?
* Does it mention a "Configuration system failed to initialize"?

2. Verify the Config File Syntax
If you pasted the code block in the wrong place (e.g., inside another tag or cut off a closing tag), the program will crash instantly at the loading bar.

Open ISTAGUI.exe.config again.
Ensure the structure looks exactly like this (simplified view):

XML:

<configuration>
   <!-- Other settings -->
   <runtime>
      <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
         <!-- The block you added MUST be inside assemblyBinding -->
         <dependentAssembly>
            <assemblyIdentity name="System.Data.SQLite" publicKeyToken="db937bc2d44ff139" culture="neutral" />
            <bindingRedirect oldVersion="0.0.0.0-1.0.111.0" newVersion="1.0.111.0" />
         </dependentAssembly>
      </assemblyBinding>
   </runtime>
   <!-- Other settings -->
</configuration>

Crucial Check:

Did you accidentally delete </configuration> at the end?
Did you paste the code *outside* of <runtime> or <assemblyBinding>?

3. Revert to Original (If unsure)
If you are unsure if the file is correct:
1. Delete ISTAGUI.exe.config.
2. Rename your backup ISTAGUI.exe.config.bak back to ISTAGUI.exe.config.
3. Try to run it. If it crashes with the original SQLite error, we know the Config file edit was the cause of the "instant close".

Report back: What does the Event Viewer say is the "Faulting Module"? This is the key to solving it.

pethconi · 18.02.2026

Found some errors, one is indeed about KERNELBASE.dll
and this:

Naam van toepassing met fout: ISTAGUI.exe, versie: 4.57.30.32356, tijdstempel: 0x696a3793
Naam van module met fout: KERNELBASE.dll, versie: 10.0.19041.6280, tijdstempel: 0x56511854
Uitzonderingscode: 0xe0434352
Foutmarge: 0x0000000000025369
Id van proces met fout: 0x1934
Starttijd van toepassing met fout: 0x01dca02c6f5782f0
Pad naar toepassing met fout: C:\ISTA\TesterGUI\bin\Release\ISTAGUI.exe
Pad naar module met fout: C:\Windows\System32\KERNELBASE.dll
Rapport-id: f6ab693d-7b79-4a2b-9635-8bbf43abf23d
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:

Gemini · 18.02.2026

pethconi said:
Found some errors, one is indeed about KERNELBASE.dll
and this:

Naam van toepassing met fout: ISTAG...

This error log reveals the exact problem!

The Mismatch:
Your error log shows the program is running from:
C:\ISTA\TesterGUI\bin\Release\ISTAGUI.exe

But we set the Registry and applied the fixes to:
C:\ISTA

Because the program is running from that deep subfolder (...Release), it is not using the fixed SQLite.Interop.dll you copied to the main folder, and it is not finding the databases.

You must "flatten" the folder structure so everything is in C:\ISTA.

Step 1: Move the Files
1. Go to the folder: C:\ISTA\TesterGUI\bin\Release\
2. Select ALL files and folders inside it (Ctrl+A).
3. Cut them (Ctrl+X).
4. Go back to the main folder: C:\ISTA\
5. Paste them (Ctrl+V).
6. When asked, confirm to Overwrite or Replace existing files.

Step 2: Re-Apply the x86 Fix
By moving the files, you might have overwritten the "good" x86 DLL with the "bad" one from the Release folder. We need to make sure the correct one is there.

1. Go to your x86 folder (wherever you have the source files).
2. Copy SQLite.Interop.dll.
3. Paste it into C:\ISTA\ (next to ISTAGUI.exe).
4. Overwrite the existing file.

Step 3: Verify the Structure
Your C:\ISTA folder should now look like this:

C:\ISTA\ISTAGUI.exe (The program)
C:\ISTA\SQLite.Interop.dll (The x86 file you just copied)
C:\ISTA\SQLiteDBs\ (Folder containing the databases)

Delete the empty TesterGUI folder if it is still there to avoid confusion.

Now, right-click ISTAGUI.exe in the main C:\ISTA folder and select Run as Administrator. It should work now.

pethconi · 18.02.2026

did it, but again no, still the error about its not valid

Gemini · 18.02.2026

pethconi said:
did it, but again no, still the error about its not valid

If the error message says something like "The databases are not valid" or "The connection to one of the required databases could not be established", this is actually progress!

It means the program is now starting (the crash is gone), but it cannot find the language and data files to display the interface.

This usually happens because the SQLiteDBs folder is in the wrong place or empty.

Please verify this specific folder structure:

1. Check the Folder Location
Open your C:\ISTA folder.
Do you see a folder named SQLiteDBs right there next to ISTAGUI.exe?

Correct: C:\ISTA\SQLiteDBs\
Wrong: C:\ISTA\TesterGUI\SQLiteDBs\
Wrong: C:\ISTA\bin\SQLiteDBs\

2. Check the File Sizes
Open the C:\ISTA\SQLiteDBs folder.
You should see files like:

streamdataprimitive_ENGB.sqlite (Should be around 400MB - 1GB)
xmlvalueprimitive_ENGB.sqlite (Should be around 400MB - 1GB)
DiagDocDb.sqlite (Should be around 1GB+)

If this folder is empty or the files are 0KB:
You need to copy these files from your original download (look for a folder named SQLiteDBs in the tоrre**/download) and paste them into C:\ISTA\SQLiteDBs.

3. Unblock the Files (Crucial for Windows 10/11)
Sometimes Windows blocks these files because they came from the internet, causing them to be "invalid".
Run this command to unblock everything in the folder at once:

1. Click Start, type PowerShell, right-click it and Run as Administrator.
2. Paste this command and press Enter:

Code:

powershell
    Get-ChildItem -Path "C:\ISTA" -Recurse | Unblock-File

3. Wait for it to finish (it might take a few seconds without printing anything).

After checking the folder structure and running the unblock command, try running ISTAGUI.exe again.

pethconi · 18.02.2026

Failed to start ISTA.
Please make sure your ISTA configuration is valid.
In doubt reset any non standard ISTA configuration and reinstall ISTA.

this is the text from the window

Gemini · 18.02.2026

pethconi said:
Failed to start ISTA.
Please make sure your ISTA configuration is valid.
In doubt reset any non stan...

This error confirms that the ISTAGUI.exe.config file is broken (corrupted XML). This happens if the code we added earlier was pasted in the wrong place, or if a bracket > or < was accidentally deleted.

We need to undo the damage to the config file first.

Step 1: Restore the Backup
1. Go to C:\ISTA.
2. Delete the current ISTAGUI.exe.config.
3. Find the backup you made earlier (ISTAGUI.exe.config.bak).
4. Rename it back to ISTAGUI.exe.config.

Step 2: Test Run
Try to run ISTAGUI.exe now.

If it crashes silently or gives the old SQLite error: This is GOOD. It means the "Invalid Configuration" is fixed, and we are back to the original problem.
If it still says "Failed to start... configuration": Then the backup was also bad, or the file is missing.

Step 3: Apply the Fix Correctly (Only if Step 2 worked)
If Step 2 got you back to the old error, let's edit the file again, but this time we will replace the entire block to avoid syntax errors.

1. Open ISTAGUI.exe.config with Notepad.
2. Press Ctrl+F and search for: <runtime>
3. You will see a block of code that starts with <runtime> and ends with </runtime>.
4. Delete everything between <runtime> and </runtime> (including those tags).
5. Paste this exact block in its place:

XML:

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Data.SQLite" publicKeyToken="db937bc2d44ff139" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-1.0.111.0" newVersion="1.0.111.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

6. Save the file.
7. Run ISTAGUI.exe as Administrator.

pethconi · 18.02.2026

did do it, but still the same window. Event log states:

Naam van toepassing met fout: ISTAGUI.exe, versie: 4.57.30.32356, tijdstempel: 0x696a3793
Naam van module met fout: KERNELBASE.dll, versie: 10.0.19041.6280, tijdstempel: 0x56511854
Uitzonderingscode: 0xe0434352
Foutmarge: 0x0000000000025369
Id van proces met fout: 0x2474
Starttijd van toepassing met fout: 0x01dca0a1ace3e864
Pad naar toepassing met fout: C:\ISTA\ISTAGUI.exe
Pad naar module met fout: C:\Windows\System32\KERNELBASE.dll
Rapport-id: ae27cb4c-513a-40d1-b6af-86872f38f350
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:

and

Application: ISTAGUI.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: BMW.Rheingold.CoreFramework.UserCanceledException
at BMW.Rheingold.PresentationFramework.CommandCancelDialog.Execute(System.Object)
at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(System.Windows.Input.ICommandSource, Boolean)
at System.Windows.Controls.Primitives.ButtonBase.OnClick()
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows.Input.MouseButtonEventArgs)
at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
at System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent)
at System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Window.ShowHelper(System.Object)
at System.Windows.Window.ShowDialog()
at BMW.Rheingold.PresentationFramework.DialogBase.ShowDialog(Boolean)
at BMW.Rheingold.ISTAGUI.App..ctor()
at BMW.Rheingold.ISTAGUI.App.Main()

Gemini · 18.02.2026

pethconi said:
did do it, but still the same window. Event log states:

Naam van toepassing met fout: ISTAGUI.exe, ...

The error "Failed to start ISTA... configuration is valid" combined with the UserCanceledException confirms exactly what is happening:

The Cause:
When you moved the files from TesterGUI\bin\Release to C:\ISTA, you "flattened" the folder structure. However, the ISTAGUI.exe.config file still contains relative paths (dots like ..\..\) that tell the program to look for files two or three folders up. Since you are now in the main folder, those paths point to nowhere, so ISTA thinks the configuration is invalid and shuts down.

The Fix:
You need to update the paths in the config file to point to the current folder.

1. Open C:\ISTA\ISTAGUI.exe.config with Notepad.
2. Press Ctrl+F and search for: <appSettings>
3. Look for lines that contain .. (double dots) in the value="..." section. They usually look like this:

Code:

xml
    <add key="BMW.Rheingold.CoreFramework.Path" value="..\..\.." />
    <add key="BMW.Rheingold.Interfaces.Path" value="..\..\.." />

4. Change the value to just a single dot . (which means "current folder") or the full path C:\ISTA.

Change them to look like this:

Code:

xml
    <add key="BMW.Rheingold.CoreFramework.Path" value="." />
    <add key="BMW.Rheingold.Interfaces.Path" value="." />
    <add key="BMW.Rheingold.Programming.Path" value="." />

*(Note: Only change the lines that have paths. Do not change True/False settings).*

5. Search for "TesterGUI"
If you see a line like:
<add key="TesterGUI.WorkingDirectory" value="..." />
Change it to:
<add key="TesterGUI.WorkingDirectory" value="." />

6. Save the file and run ISTAGUI.exe as Administrator.

Summary:
By changing ..\.. to ., you are telling ISTA: "Stop looking in other folders, the files are right here next to you."

pethconi · 18.02.2026

Gemini said:
The error "Failed to start ISTA... configuration is valid" combined with the UserCanceledException confirms exactly what is happening:

The Cause:
When you moved the files from TesterGUI\bin\Release to C:\ISTA, you "flattened" the folder structure. However, the ISTAGUI.exe.config file still contains relative paths (dots like ..\..\) that tell the program to look for files two or three folders up. Since you are now in the main folder, those paths point to nowhere, so ISTA thinks the configuration is invalid and shuts down.

The Fix:
You need to update the paths in the config file to point to the current folder.

1. Open C:\ISTA\ISTAGUI.exe.config with Notepad.
2. Press Ctrl+F and search for: <appSettings>
3. Look for lines that contain .. (double dots) in the value="..." section. They usually look like this:

Code:

xml <add key="BMW.Rheingold.CoreFramework.Path" value="..\..\.." /> <add key="BMW.Rheingold.Interfaces.Path" value="..\..\.." />

4. Change the value to just a single dot . (which means "current folder") or the full path C:\ISTA.

Change them to look like this:

Code:

xml <add key="BMW.Rheingold.CoreFramework.Path" value="." /> <add key="BMW.Rheingold.Interfaces.Path" value="." /> <add key="BMW.Rheingold.Programming.Path" value="." />

*(Note: Only change the lines that have paths. Do not change True/False settings).*

5. Search for "TesterGUI"
If you see a line like:
<add key="TesterGUI.WorkingDirectory" value="..." />
Change it to:
<add key="TesterGUI.WorkingDirectory" value="." />

6. Save the file and run ISTAGUI.exe as Administrator.

Summary:
By changing ..\.. to ., you are telling ISTA: "Stop looking in other folders, the files are right here next to you."

again after starting the same window.
your step 5 is not in the .confug file the rest i changed, only two line were there

Gemini · 18.02.2026

pethconi said:
again after starting the same window.
your step 5 is not in the .confug file the rest i changed, onl...

The "UserCanceledException" in your log confirms that ISTA is reading the configuration file, finding it invalid (or finding paths that don't exist), showing you the error message, and then crashing when the message closes.

Since we have edited the file multiple times and moved folders around, the current config file is likely a mix of old relative paths (..\..\) and new settings, which is confusing the program.

We need to delete the current config file and create a clean, simple one with absolute paths pointing directly to C:\ISTA.

Please follow these steps exactly:

Step 1: Delete the Old Config
1. Go to C:\ISTA.
2. Delete the file ISTAGUI.exe.config.

Step 2: Create a Fresh Config File
1. Open Notepad.
2. Copy the code block below EXACTLY. I have set the paths to C:\ISTA explicitly to avoid any confusion.

XML:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <appSettings>
    <!-- Force paths to the main folder -->
    <add key="BMW.Rheingold.CoreFramework.Path" value="C:\ISTA" />
    <add key="BMW.Rheingold.Interfaces.Path" value="C:\ISTA" />
    <add key="BMW.Rheingold.Programming.Path" value="C:\ISTA" />
    
    <!-- Disable online checks -->
    <add key="BMW.Rheingold.Online.Mode" value="False" />
    <add key="BMW.Rheingold.Programming.Enabled" value="False" />
    <add key="BMW.Rheingold.Programming.ExpertMode" value="False" />
  </appSettings>
  
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8" />
  </startup>
  
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <!-- SQLite Fix -->
      <dependentAssembly>
        <assemblyIdentity name="System.Data.SQLite" publicKeyToken="db937bc2d44ff139" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.0.0.0" newVersion="1.0.111.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

3. Click File -> Save As.
4. Name the file: ISTAGUI.exe.config
5. Crucial: Change "Save as type" to **All Files (.)**.
6. Save it into C:\ISTA.

Step 3: Final Unblock (Just in case)
Since we moved files around, Windows might have blocked the main executable again.
1. Right-click ISTAGUI.exe.
2. Select Properties.
3. If you see a checkbox at the bottom that says Unblock, check it and click OK. (If it's not there, that's fine).

Now, right-click ISTAGUI.exe and select Run as Administrator.

pethconi · 18.02.2026

did it but again the same !

Gemini · 18.02.2026

pethconi said:
did it but again the same !

The error UserCanceledException combined with "configuration is valid" confirms that the "minimal" config file I gave you was too simple. It was missing some critical settings that ISTA checks on startup (like TesterGUI.WorkingDirectory), so the program deliberately shuts down.

Also, the fact that your original config had "only two lines" means it was linking to an external settings file (likely App.config in a different folder), which is why it broke when you moved the files.

Since you have "flattened" the installation to C:\ISTA, we need a Complete Standalone Config that has all the settings inside it, with no links to external files.

Please follow these steps to create the final working configuration.

Step 1: Create the Complete Config File
1. Go to C:\ISTA.
2. Delete the current ISTAGUI.exe.config.
3. Open Notepad.
4. Copy the code block below EXACTLY. This contains all the necessary keys for a flattened installation.

XML:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <appSettings>
    <!-- Critical Paths - Pointing to current folder -->
    <add key="TesterGUI.WorkingDirectory" value="." />
    <add key="BMW.Rheingold.CoreFramework.Path" value="." />
    <add key="BMW.Rheingold.Interfaces.Path" value="." />
    <add key="BMW.Rheingold.Programming.Path" value="." />
    
    <!-- Online / Programming Settings -->
    <add key="BMW.Rheingold.Online.Mode" value="False" />
    <add key="BMW.Rheingold.Programming.Enabled" value="False" />
    <add key="BMW.Rheingold.Programming.ExpertMode" value="False" />
    <add key="BMW.Rheingold.CoreFramework.LightMode" value="False" />
    
    <!-- Diagnostics Settings -->
    <add key="BMW.Rheingold.Diagnostics.VehicleIdent.ReadBasicVehicleData" value="True" />
    <add key="BMW.Rheingold.Diagnostics.VehicleIdent.ReadVehicleData" value="True" />
  </appSettings>
  
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8" />
  </startup>
  
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <!-- SQLite Fix -->
      <dependentAssembly>
        <assemblyIdentity name="System.Data.SQLite" publicKeyToken="db937bc2d44ff139" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.0.0.0" newVersion="1.0.111.0" />
      </dependentAssembly>
      <!-- JSON Fix -->
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

5. Save as ISTAGUI.exe.config in C:\ISTA.
6. Important: Ensure "Save as type" is set to All Files.

Step 2: Verify the SQLite DLL
Since you moved files around, let's make 100% sure the correct DLL is in the main folder.
1. Find your x86 version of SQLite.Interop.dll (from your fix files).
2. Copy it into C:\ISTA.
3. Overwrite the existing file if asked.
*(Note: Even on 64-bit Windows, ISTA is a 32-bit program, so it MUST have the x86 DLL next to the .exe)*.

Step 3: Run as Administrator
Right-click ISTAGUI.exe and select Run as Administrator.

Why this works:
This config file explicitly defines TesterGUI.WorkingDirectory as . (current folder). Without this specific key, ISTA assumes it is running from a bin\Release subfolder, looks for files that aren't there, and throws the "UserCanceled" error you saw.

pethconi · 18.02.2026

still the same....
noticed that the config files are notepad files, since i opend them with notepad, hopefully that doesn't interact in this proces ?

Gemini · 18.02.2026

pethconi said:
still the same....
noticed that the config files are notepad files, since i opend them with notepad,...

Yes, that is exactly the problem! If the file is saved as a text file, ISTA cannot read your settings. It ignores the file completely, tries to use the default settings (which point to the wrong folders), and crashes with the "UserCanceledException" because it can't find the databases.

You need to fix the file extension immediately.

Step 1: Fix the File Extension

Windows often hides the .txt extension, so you might see ISTAGUI.exe.config but the real name is ISTAGUI.exe.config.txt.

1. Open the folder C:\ISTA.
2. At the top of the window, click the View tab.
3. Check the box that says File name extensions.
4. Now look at your config file. Does it say ISTAGUI.exe.config.txt?
5. If yes:
* Right-click the file and select Rename.
* Delete the .txt part so it is just ISTAGUI.exe.config.
* Press Enter. Windows will ask if you are sure. Click Yes.

Step 2: Verify the Icon

Wrong: The icon looks like a lined sheet of paper (Text Document).
Correct: The icon looks like a blank white sheet or an XML file icon, and the "Type" column says "CONFIG File" or "XML Configuration".

Step 3: Install Missing Runtimes (If Step 1 doesn't fix it)

If the file name was already correct, the KERNELBASE.dll error usually means your computer is missing the C++ libraries required to run the app. Even if your Windows is 64-bit, ISTA is a 32-bit program and needs the x86 versions.

1. Download the Visual C++ Redistributable 2015-2019 (x86).
* Search Google for "Visual C++ Redistributable latest supported downloads".
* Download the file vc_redist.x86.exe.
2. Install it and restart your computer.
3. Try running ISTAGUI.exe again.

Summary:
The "UserCanceledException" happens because ISTA can't find the databases. This is almost certainly because your config file is named .txt and is being ignored. Fix the name, and it should start.

pethconi · 18.02.2026

did it all, and yes its a .config file and reinstalled C++ again
but still the same pop-up

Gemini · 18.02.2026

pethconi said:
did it all, and yes its a .config file and reinstalled C++ again
but still the same pop-up

The "UserCanceledException" and the "Configuration is invalid" error are happening because we moved the files to C:\ISTA, but Windows Registry still thinks the program is installed in the old location (or doesn't know where it is at all).

ISTA checks the Registry on startup to find its "Home" folder. If the Registry path doesn't match the actual folder, it assumes the configuration is broken and shuts down.

Please follow these two steps to fix the location mismatch.

Step 1: Fix the Windows Registry
We need to tell Windows that ISTA is now located in C:\ISTA.

1. Open Notepad.
2. Copy the code block below EXACTLY:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\BMWGroup\ISPI\Rheingold]
"InstallPath"="C:\\ISTA"
"BMW.Rheingold.Programming.ExpertMode"="false"
"BMW.Rheingold.Programming.Enabled"="false"
"BMW.Rheingold.Online.Mode"="false"

3. Click File -> Save As.
4. Name the file: FixRegistry.reg
5. Save it to your Desktop.
6. Close Notepad.
7. Double-click FixRegistry.reg on your Desktop.
8. Click Yes when Windows asks to confirm.
9. Click OK.

Step 2: Update Config with Logging Support
The previous config file I gave you was too simple and removed the logging settings. ISTA tries to start the log system immediately, fails because the settings are missing, and crashes.

1. Go to C:\ISTA.
2. Delete ISTAGUI.exe.config.
3. Open Notepad.
4. Copy this complete configuration block:

XML:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <configSections>
    <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net" />
  </configSections>
  
  <appSettings>
    <!-- Paths set to current folder -->
    <add key="TesterGUI.WorkingDirectory" value="." />
    <add key="BMW.Rheingold.CoreFramework.Path" value="." />
    <add key="BMW.Rheingold.Interfaces.Path" value="." />
    <add key="BMW.Rheingold.Programming.Path" value="." />
    
    <!-- Settings -->
    <add key="BMW.Rheingold.Online.Mode" value="False" />
    <add key="BMW.Rheingold.Programming.Enabled" value="False" />
    <add key="BMW.Rheingold.Programming.ExpertMode" value="False" />
    <add key="BMW.Rheingold.Diagnostics.VehicleIdent.ReadBasicVehicleData" value="True" />
  </appSettings>
  
  <log4net>
    <appender name="FileAppender" type="log4net.Appender.FileAppender">
      <file value="Logs\ISTAGUI.log" />
      <appendToFile value="true" />
      <layout type="log4net.Layout.PatternLayout">
        <conversionPattern value="%date [%thread] %-5level %logger - %message%newline" />
      </layout>
    </appender>
    <root>
      <level value="DEBUG" />
      <appender-ref ref="FileAppender" />
    </root>
  </log4net>

  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8" />
  </startup>
  
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Data.SQLite" publicKeyToken="db937bc2d44ff139" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.0.0.0" newVersion="1.0.111.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-13.0.0.0" newVersion="6.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

5. Save as ISTAGUI.exe.config (make sure "Save as type" is All Files).
6. Create a new empty folder named Logs inside C:\ISTA (so the logger has a place to write).

Now, right-click ISTAGUI.exe and Run as Administrator.

pethconi · 18.02.2026

still the same pop-up and Logs stays empty....

ISTA+ STANDALONE BMW Diagnostic & Coding - Workshop Solution 4.59.12

Post #261

Post #262

Post #263

Post #264

Post #265

Post #266

Post #267

Post #268

Post #269

Post #270

Post #271

Post #272

Post #273

Post #274

Post #275

Post #276

Post #277

Post #278

Post #279

Post #280

Similar threads