Hi,
currently we have deployed round about 55 Applications in PatchMyPc and this cause that Application Updates will increase the Time.
Documents from MS recommending to use Filters so we Pushed the Freeware as Available to every Computer also the Intune Updates Apps.
MS said Filters are faster than Groups to we used them.
We record the time with 20 Applications and the ESP was done in 30 min, now we have 55 Applications and now its 45 min longer as before.
Is there an recommendation do get this fast again?
hey mguenth83,
We recommend configuring "blocking apps" in your Enrollment Status Page. You can find more details here (https://learn.microsoft.com/en-us/mem/intune/enrollment/windows-enrollment-status).
Please ensure that you deploy any software you specify as "blocking app" as Required to the same Autopilot device as well.
By doing, only the apps you select will be evaluated during the enrollment of the device. The rest of the apps will be evaluated by Intune after the device is enrolled.
Hi Liviu,
thanks for the fast reply but makes no sense for me because i dont want Install the free software on the Computer.
The Intune Application are configure as Available and the Intune Application Updates marked as Required so the flow is in ESP.
Check if the Application is avaiable > check if the Intune App Update is needed
The Check of the Updates takes too long, so we need another solution.
hey mguenth83,
During Autopilot, Intune will evaluate all win32 apps that are deployed as Required to all your devices.
In your case, I assume all Intune Updates you package through the PMPC Publisher are deployed as required to all your devices.
This will slow Autopilot down, because the more Intune Updates you deployed through PMPC, the longer it will take Intune to evaluate all of them during the enrollment of the device.
The Intune Updates are win32 apps as well, so Intune thinks it needs to evaluate them as well during Autopilot.
Having Intune Updates being evaluated during Autopilot is not necessary, as they won't apply anyway.
The best option to go here is to have one app, maybe Company Portal or anything else, deployed as Required to All Devices and then marked as a "blocking app" in your Enrollment Status Page.
Intune will then evaluate that win32 app only.
Ah okay i know what you meaning if i added the application in blocked apps Intune will only evaluate the blocked apps an ignore the other Win32 apps that is assigned as required.
Is that correct?
that is correct.
In addition to adding the app under "blocked apps", please make sure to deploy the software as required to the same group the Enrollment Status Page profile is deployed to.
Then Intune will only evaluate that single app during Autopilot.
Hi,
thanks for the Tip i have now configured that all Apps will be installed during the ESP (not the Updates) and i decrease the time from 45 min to 20 min :-)
I wish you a nice Weekend :-)
Greetz
Matthias
This is great news, Matthias! I'm happy this works fine for you now!
Hi,
one question to this i have. What will be Happens if i forget one in the ESP Status Page?
Do Intune will evelate all required Apps?
hi mguenth83,
I'm sorry, I don't understand the question. Can you please provide more details?
I just wanted to ask what happens if, for example, I have marked 8 apps as Required and entered 7 in the ESP? Will the ESP become slower again?
And another question do I also have to enter the update applications in the ESP?
The more applications you add to your ESP, the longer it will take for them to install during the enrollment of the device.
That can make the process slower.
There is no need to add 'Intune Updates' to the ESP as a blocking app. 'Intune Updates' will only be installed if an older version is found.
As the device will be completely new, no older version will be installed at that time anyway.
Adding 'Intune Updates' to the ESP will unnecessarily slow the enrollment down.
I am experiencing this issue now. I pre-provision my devices and I only have 8 apps required in there. The pre-provisioning is fine, computer Reseals then I give it to the user. The problem is that when the user logs in and it does the ESP Device setup section, the Apps (Identifying) takes like 10 minutes, then it says (None Applicable) or something like that.
I checked the AppWorkLoad.log and I can see that's evaluating all my "Update for <app>" packages because they are marked as Required to All Devices.
Lets say I have the VLC Media Player package created, I mark it as Available for All Devices that way people can download from Company Portal. I also create the Update for VLC Media Player package and mark it as Required for All Devices, assuming that that way when an update gets released those who installed the software will get the update.
My AppWorkLoad.log is processing around 45 packages.
What can I do so I can make this better?
Quote from: MassDeployment on January 28, 2026, 09:47:56 PMI am experiencing this issue now. I pre-provision my devices and I only have 8 apps required in there. The pre-provisioning is fine, computer Reseals then I give it to the user. The problem is that when the user logs in and it does the ESP Device setup section, the Apps (Identifying) takes like 10 minutes, then it says (None Applicable) or something like that.
I checked the AppWorkLoad.log and I can see that's evaluating all my "Update for <app>" packages because they are marked as Required to All Devices.
Lets say I have the VLC Media Player package created, I mark it as Available for All Devices that way people can download from Company Portal. I also create the Update for VLC Media Player package and mark it as Required for All Devices, assuming that that way when an update gets released those who installed the software will get the update.
My AppWorkLoad.log is processing around 45 packages.
What can I do so I can make this better?
Same recommendation was given above I would suggest.
Remove the UPDATES from ESP entirely. It's not necessary to have them there.
They will still evaluate separately based on the Standard InTune evaluation cycles after ESP completes and the device is online.
Keep the ESP list restrained to only the most critical core requires apps. Everything else shouldnt be in ESP.