Forum Discussion
We’re running into an Intune issue where a Win32 app with a dependency sits at "Download Pending"
Setup:
Main App: Installs in User Context
Dependency: Installs in System Context
Dependency Detection:
- Hosts file modification detection script
- Direct file detection does NOT work either
- When the hosts file modification is present (detection is met), detection works, and everything installs fine manually
The Problem:
- If detection passes (exit 0) → Everything installs fine.
- If detection fails (exit 1) → Intune never moves forward, just stays at "Download Pending" indefinitely.
- Happens with both file-based detection and script-based detection.
- Dependency app as well at parent app install fine via Intune on their own as well as manual testing.
What We Need to Know:
Does Intune get stuck in "Download Pending" instead of moving forward when dependency detection fails?
Could the install context mismatch (dependency in SYSTEM, main app in USER) be causing this?
Myth or fact? Does Intune break the install process if a dependency app is in system context and the parent app is in user context? Again, both apps work fine independent of each other. Thanks for any help!
4 Replies
Just wanted to leave a record of the fix that worked for me. I was in a similar situation, 2 applications, both set as available, 1 being a dependency for the other (.Net Desktop Runtime being the dependency). Il leave out the middle part but the fix was to remove the available assignment from the dependency app (.Net) as that was stopping Intune from enforcing its installation.
As soon as I did that BOOM
All the evidence came from the AppActionProcessor.log and when dependency app was set to available you can see:"effective intent: RequiredInstall, and enforceability: DetectOnly"
Once I removed the "Available" assignment, next time i tried to install my Parent application it installed the dependency without issue as indicated in the same log:effective intent: RequiredInstall, and enforceability: Enforceable
This might have been answered in another forum post but thought I would drop it here as this one was unanswered.Seeing the same behavior here. The dependent apps are using same SYSTEM context method, same OS requirements and assigned as available. Seems that the automatic install setting isn't working for some reason. Anything change with the 2507 Service release???
Hi gladdin123, is the dependency an msi? If so, have you tried wrapping the msi as an intunewin and deploy it as win32? As far as I know, but I would be happy to be corrected, the dependency for a win32 app also has to be a win32 app.
Also, you can check the IntuneManagementExtension logs in: C:\ProgramData\Microsoft\IntuneManagementExtension\Logs
I can at least answer your main question. This isn't explicitly stated in Microsoft's documentation: https://learn.microsoft.com/en-us/intune/intune-service/apps/apps-win32-add#step-5-dependencies but in testing, Yes you can install an app with install behaviour set to User and it will automatically deploy a dependant app with install behaviour set to System.
I have a very similar situation that has made me question everything. Both apps install and are detected successfully when run in sequence separately. When the USER win32app is installed with a win32app dependency not already met, the deployment appears to hang indefinitely in "Download Pending..." when navigating back to company portal the status resets to "Install". Automatic Install doesn't trigger when enabled. When automatically install is disabled the status doesn't show that the assigned dependent System app is missing. For me this effects a specific app deployment and multiple test devices. The deployment failure is never logged in Intune.In my case, the deployment works with other win32apps system apps set as dependencies, so I believe the issue lies with the dependant System app but have yet to pin point the difference in the app deployments in Intune Management Logs.
