• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

Recent posts

#21
Hi Liviu,
I checked our Defender policy that is applied to our fleet and the following paths are specifically excluded:
C:\Program Files (x86)\Microsoft Intune Management Extension\Content
C:\windows\IMECache

Also buried in the logs was:

[Win32App] Set EnforcementStateMessage.ErrorCode -2146992128   IntuneManagementExtension   29/05/2023 8:38:40 AM   37 (0x0025)
[Win32App] Admin did NOT set mapping for lpExitCode: 32768 of app: 2ceb1c22-3f54-4a04-a643-fd0bd92dbca8   IntuneManagementExtension   29/05/2023 8:38:40 AM   37 (0x0025)
[Win32App] Setting enforcementState as: Error with lpExitCode: 32768 without mapping   IntuneManagementExtension   29/05/2023 8:38:40 AM   37 (0x0025)

[StatusService] Sending an update to user xxxx-xxxx-xxxx via callback for app: 2ceb1c22-3f54-4a04-a643-fd0bd92dbca8. Applicability: Applicable, Status: Failed, ErrorCode: -2146992128   IntuneManagementExtension   29/05/2023 8:38:55 AM   37 (0x0025)
[Win32App][ExecutionActionHandler] Handler completed with action status: Failed.   IntuneManagementExtension   29/05/2023 8:38:55 AM   37 (0x0025)
#22
Perfect!
Thank you and have a nice weekend!
#23
Yes, we will be sure to mention it in the notification emails, and I'll update this thread when we ship that change.
#24
Great news, thank you Andrew!
I guess it will be stated in the notification emails right?
#25
The limited detection logic for Adobe Acrobat DC is also interfering with updates for Acrobat DC x64 and Acrobat Reader DC x64.  Both updates are considered required for a PC with Reader x64 which causes a conflict in ConfigMgr and therefore NO updates are advertised for Reader.  I understand that Adobe has made detection difficult by branding both Acrobat and Reader as "Acrobat", but PMPC is the creator of the detection scripts and should be able to differentiate the two.
#26
This is perfect, everything I have seen shows 2015-2022 as a drop-in replacement for 2015-2019. We are planning on  removing 2015-2019 and replacing it with 2015-2022 this month (with the next Publisher release).
#27
Hi Andrew,

I checked on Microsoft's SharePoint resources for the VC++ requirements and it seems that we can go with 2015-2022 for the versions of SharePoint 2016 and onwards.
Also checked our servers and discussed this with our SharePoint Admins and we reached to the conclusion of using that one and replacing the 2015-2019 were it is installed.
Did you do any research from your side?

#28
Thanks, Andrew!

The only solution for now would be to force the correct order. 32-bit first, 64-bit second. I do that using an "Application Group".

But using Software Updates, it probably relies on alphabetical order. Which results in deploying "x64" BEFORE "x86". So, better naming would be "32-bit" and "64-bit" ;-)
#29
Quote from: trevorbuley on May 24, 2023, 11:26:16 PMHi,

MEM Intune/Azure Environment here.
Every second PC or so seems to be getting this error when trying to install Oracle Java 8 JRE 8.0.3710.11 (x64).  Just occurred on a freshly imaged and deployed device, but the previous device has no issues.
Both devices have the same basic staff profile, Microsoft Surface devices running Windows 10 22H2 Enterprise.


Hello Trevor,

That error message means that the file cannot be found on the device. It could mean that it was deleted before the install could take place.
This usually means that the file is being quarantined by a security solution. Can you please check your AV and whitelist installers from the IME Cache?


#30
Hi,

MEM Intune/Azure Environment here.
Every second PC or so seems to be getting this error when trying to install Oracle Java 8 JRE 8.0.3710.11 (x64).  Just occurred on a freshly imaged and deployed device, but the previous device has no issues.
Both devices have the same basic staff profile, Microsoft Surface devices running Windows 10 22H2 Enterprise.