Good morning
I installed arduino ide 2.3.3 in a practical work room with the alluser option.
When the IDE is started by a user (student) who is not an administrator, the IDE freezes. I see that it creates dpinst-amd64 processes in a loop.
This executable is in the user profile created when the IDE starts. It seems to be blocked by the firewall. How to get around the problem?
A couple things might be for sysad to give your session admin privs to allow executables. Or, tell the sysad to install the IDE for all users (allowing IDE instances adequate permissions).
veille
We don't have a sysad. User authentication is done by an LDAP request.
Are there operations to do so that the executables and libraries are common and not in the user profile, as should be the case with an installation in /allusers?
Old topic here, but so far my only hope.
We are in the same situation here.
dpinst-amd64 processes are created in a loop when student users (not admins) add a board in Arduino IDE.
I have tried a lot of things unsuccessfully. lebrun22 have you found any solution?
You should start your own topic, but if these issues are similar, or the same, supply as much detail about your issue as you can gather (O.S., IDE ver, observations, et c.) for the Arduino systems rep.
One guess: UNCHECK "Preferences >> Use external editor"
This is very similar issue and similar production environnement aswell (scool computers with multiple non admin users).
Os is Windows 11 24h2 and Arduino IDE version : 2.3.6
Post-install script from board installation runs dpinst-amd64 in a loop (several hundred times until you sign off Windows session) :
No UAC popup for board drivers installation.
No error in IDE log :
time="2025-05-23T10:10:10+02:00" level=info msg="Installing platform" platform="arduino:mbed_giga@4.3.1"
2025-05-23 10:10:40 2025-05-23T08:10:40.829Z daemon INFO time="2025-05-23T10:10:40+02:00" level=info msg="Running post_install script" platform="arduino:mbed_giga@4.3.1"
Look like we have a security/UAC issue. Seem more related to OS policy than Arduino
Hi @admincir. Can you provide detailed step-by-step instructions I can follow to reproduce the fault?
When I install a platform using a non-admin account, I simply get this UAC dialog:
If I click the "No" button, then it simply closes and the platform is installed, but the drivers are not installed (which won't be a problem if the system administrator already installed the necessary drivers).
If I provide the PIN of the admin account (yes, I know the student would not be able to do that, but I'm just covering all the possibilities), then the drivers are installed as usual.
In neither case does the fault of dpinst-amd64 being run in a loop occur.
I'm guessing there is some different configuration of your system than mine. Unfortunately I'm not knowledgeable in this area of institutional system administration.
The Arduino developers are now tracking the problem via this formal report:
@lebrun22 @admincir have you made any progress on finding the cause and/or a solution for the problem?
I am still interested in investigating this, but I am not able to proceed due to the fact that I can't reproduce the problem. So I am limited by your willingness to cooperate, and I never received a response from my last reply.
We now have a better understanding of the nature of the problem:
https://github.com/arduino/ArduinoCore-avr/issues/608#issuecomment-3457624067
running the batch file from the command line, or double-clicking it directly, we observe the same multiplication of
dpinst.exeprocesses.
So the problem is not caused by Arduino IDE invoking Driver Package Installer repeatedly, but instead that a single invocation somehow results in this situation, regardless of how it is invoked. So the problem can not be resolved by any change to the Arduino development tools.
Driver Package Installer is invoked as part of the installation of the "Arduino AVR Boards" platform that Arduino IDE performs on the first run of a fresh installation.
My recommendation is for the system administrator to pre-install the "Arduino AVR Boards" platform when provisioning the user accounts. Arduino IDE checks for an existing installation of the platform, and only attempts the automatic installation if the platform is not found. So this will serve as an effective workaround for the problem. Furthermore, it will improve the user experience as everything will already be in place when the user starts Arduino IDE the first time, rather than them having to wait for an installation process to complete. Additionally, installation of the platform using an administrative account will allow you to install the USB drivers that may be needed for certain boards.
Although you could accomplish this by simply starting Arduino IDE during the account provisioning process, a system administrator may prefer to perform the operation via a command line tool in order to enable automation or make the process more efficient. This can be done via the official Arduino CLI tool:
https://arduino.github.io/arduino-cli/latest/
The arduino-cli core install arduino:avr command will install the platform:
https://arduino.github.io/arduino-cli/latest/commands/arduino-cli_core_install/
By default, the command will execute the post-install script that invokes Driver Package Installer when the command is invoked in an "interactive" context. Likewise, by default it will skip the post-install script if the command is invoked in a "non-interactive" context (e.g., via a script). You can force the post-install script execution using the --run-post-install flag, or force it to be skipped using the --skip-post-install flag.