Messages

Ok, so it seems like that is how the installer functions when running as the SYSTEM account unfortunately.

I also checked if you can overwrite the temp folder path for MSIs, and it looks like that isn't allowed either...

Authors should not need to set the TempFolder property. Windows Installer uses the GetTempPath function to retrieve the path of the directory designated for temporary files and to set this property.

https://learn.microsoft.com/en-us/windows/win32/msi/tempfolder

Hello,

We don't do anything special regarding those installers, so you may be out of luck. I would try to install them manually using the SYSTEM account and see if you notice the same behavior.

We actually followed up on this a bit more, and we had a mistake in our detection method. This issue should be remediated with today's catalog release (6-15-2023).

Patch My PC updates for Microsoft Visual C++ 2015-2022 updates will now upgrade existing 2015-2019 installations. We will also be completing removing 2015-2019 from our catalog this week. Thank you!

Happy to help!

Hello,

This likely occurred because we have 3 employees with physical code-signing keys. 2 of the keys were recently renewed, and were not included in the catalog for a short period of time. Because of this, if you synced when one of the new keys were used to sign the catalog, you would get the "trust failed" error.

Since you are still seeing updates being published, I think you might also have the Patch My PC Publisher set up. If you do have the Publisher installed and running, you very likely do not need to have Patch My PC configured in the "Third-Party Software Updates" section of the ConfigMgr console, and the error can be ignored/that connection can be removed.

Just an update. This issue was likely caused by Microsoft removing a Graph endpoint. We're working internally to see what we need to change to get things working again!

We created a KB article for this as well, you can watch that page for more information as new details emerge: https://patchmypc.com/intuneapplicationmanagerstatistics

Hello,

The way you are attempting to do this is the right way, however, it seems you might be getting time outs from the Intune service. We should have a new prod build in the next few days that might fix this for you. I'll comment on this thread when that release is live.

Hi, that is quite the version jump! We'll check it out!

Yes, we will be sure to mention it in the notification emails, and I'll update this thread when we ship that change.

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).

Following up on this. We have had 1 other customer report a similar issue, however, because the issue is with the Java installer itself, there is not much we can do to remedy it. We have looked at different install commands and have been unable to resolve the issue ourselves. We'll continue to watch the issue, I imagine this issue will be resolved with Java 381 in July.

We looked into this a bit more, we are actually providing 1.4.5, however, this version did not update the registry properly, and we use the title in determining the version to look for in the registry, which is why the title version does not match the version that we install.

Thanks! We'll look at our automations to catch new versions of this app in the future, and have this version added either today or tomorrow.

I'd say so, feel free to send them over to support to help the developers further.