-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install doesn't work under Intune Autopilot #1825
Comments
Just had the same issue, have you found any more information? Have you found a Workaround? |
No, unfortunately, I didn't find a workaround. After some time I gave up and now it is a "limitation" in our deployment environment. |
I don't know how InTune works but I suspect it is trying to execute the installer as a service account, you probably need to talk to your application vendor to get an MSI instead. Alternatively, every Squirrel app is fundamentally a portable app, so you could just copy If you have more documentation about how InTune works I could provide a better recommendation, I don't really know what it is doing internally |
The applications run with current user permissions - there is such possibility in Intune. Unfortunately, not all vendors provides alternative installers. Yes, it is possible to extract files and trigger executable in the script, etc., but question why Squirrel doesn't run in usual way, and how to make it run. |
I have no idea how to make Intune work with Squirrel, sorry! I cannot speculate as to why Intune was coded to only work with "the usual way" installers, because I did not write Intune. |
Description
Squirrel based per user installers don't work under Intune Autopilot
Steps to recreate
Expected behavior
Application successfully installed
Actual behavior
The installation seems to even cannot start. Log file not created.
The installer returns error code -1073741819
In the Event Viewer Exception code: 0xc0000005
The text was updated successfully, but these errors were encountered: