ConfigED client on Windows

[shade]

Hello,

I have been using ConfigED (opsi-configed-windows.exe) on Windows 10 for some time. Recently, I started encountering an error on certain devices that states: “The program cannot run because jli.dll is missing. Try reinstalling the program.”

Upon examining (and extracting) the opsi-configed-windows.exe file, I can see that jli.dll is indeed included within the executable. This problem, however, only seems to occur on some devices, while others remain unaffected.

Do you have any advice or a solution for this issue?

Thank you, and I look forward to your response.

[n.doerrer]

Hello,

are you sure you are using the latest stable version?
see portable here https://tools.43.opsi.org/stable/

[shade]

Hello,

I am currently using version 4.3.2.18 (2024-06-07). However, when I download the latest version for the 4.2 server from https://download.uib.de/4.2/stable/misc/ (updated on 2024-06-28), it fails to open.

Additionally, if I download the newest version from https://tools.43.opsi.org/stable/, it will not run with our current server version.

[n.doerrer]

I cannot reproduce the issue with the 4.2 stable opsi-configed.

A guess would be, that some antivirus program thinks that the specific dll is malicious and quarantenes it.

Anyway I strongly suggest to upgrade to 4.3.

[bergerb]

A similar thing is happening on my W11 VM.
It seems like it survives a restart. Maybe Windows update is destroying it.

I analyzed the .exe a bit, and it looks like it self extracts to:

Code: Alles auswählen

%localappdata%\Temp\ziplaunch.<username>.opsi-configed-windows.<someid>

(can't find anything regarding ziplaunch btw - is that selfmade?)

the whole folder structure remains, but only java\bin\java.exe exists, the other files are gone.

Code: Alles auswählen

└───java
    ├───bin
    │   └───server
    ├───conf
    │   └───security
    │       └───policy
    │           ├───limited
    │           └───unlimited
    └───lib
        ├───jfr
        └───security

I thought your update killed it, but after renaming the .exe, it worked again.

I'll try to copy the extracted files to something other than the Temp folder and see if whatever has been eating it, wont eat it from somewhere else