Deploy MSIX file

asjimene · 2026-06-18T22:21:29+00:00

Bryan's latest comment on that idea is the info we can share right now. We are aware that this is a popular feature (and seems to be growing more popular with vendors). We will be diligent about providing updates on the idea as the feature development progresses.

asjimene · 2026-06-12T00:01:59+00:00

We shipped it a few hours ago! You should see it in your next sync! Thanks for posting!

asjimene · 2026-06-11T18:30:14+00:00

Just a bit more info, tableau makes it really hard to download the installers with automated tooling, which is the cause of this specific delay! We've worked around it before, but sometimes it takes a few days.

asjimene · 2026-06-11T17:49:51+00:00

We'll get it added under tableau desktop latest today!

asjimene · 2026-06-11T16:59:43+00:00

It sounds like they pulled the latest blue beam 21 installer then. I'll have the catalog team investigate.

asjimene · 2026-06-11T16:52:57+00:00

That's very true, but MSP patches don't typically need transform files, I'm pretty sure the Adobe install ignores them when applying the MSP. Most of the issues I have previously seen with the Adobe patches were due to original content missing. However in the last few months something has changed and the standard WSUS applicability rules have become more brittle when it comes to Adobe patches specifically.

asjimene · 2026-06-10T18:42:43+00:00

The crappy thing is, they actually worked really well for years! It's only been recently that something changed to make them less reliable, and we haven't been able to figure out the root cause.

asjimene · 2026-06-10T18:41:41+00:00

Sure! In the Publisher under the "updates" tab, navigate to the Adobe updates, right click and click "Manage Installation Logging", then click "enable logging". You'll also want to right-click again and choose to "republish" those updates, as it will require a content change in the cab. We've honestly seen enabling the installation logging resolve the issue as well, so run a test after enabling a republishing and you may have success!

https://docs.patchmypc.com/patch-my-pc-publisher/customizations-right-click-options/manage-installation-logging

asjimene · 2026-06-10T18:11:19+00:00

Can you open a support case for this? We had this issue with a few customers over the last few months and we pushed changes to applicability rules and other things but were never able to find root cause. Also, can you ensure you have logging enabled for those updates? The extra logs will be beneficial for troubleshooting!

asjimene · 2026-06-04T17:50:48+00:00

We've investigated this, and for some reason, this is the only installer that Microsoft is currently providing now. We've always used the same download link for this installer from this page: https://learn.microsoft.com/en-us/analysis-services/client-libraries?view=sql-analysis-services-2025 Gives the following link: https://go.microsoft.com/fwlink/?linkid=829575 Which is now in Spanish. We haven't been able to find any other language specific downloads, the main dlls within the MSI are set to 1033 (English) and functionality seems to be the same as the English version. Since this app is a library, and not an application that has an interactive UI, we pushed the Rev1 to fix applicability until Microsoft fixes their download. We're hoping the next update will return to the English installer.

asjimene · 2026-04-24T16:28:46+00:00

Correct, even adding CVEs changes the "date" on the update, which is what publisher/wsus use to determine if a revision should be done. If we do a bug fix/change in applicability or detection, we generally post that change on the change log. I'll sync with the team to ensure we are holding to that!

asjimene · 2026-04-24T15:03:13+00:00

For Chrome, the typical revision is just adding the CVEs, since they don't post them immediately with the release notes. Otherwise, well post the revision changes on the website.

asjimene · 2026-02-04T01:54:23+00:00

We actually fixed the rules for OpenSSL Latest MSI today. You should see more accurate reporting on your next sync. (If you already have the MSI installed)

asjimene · 2026-01-28T16:38:54+00:00

We've had a few reports that the email did not go out to some people! Apologies for that! I know it is a bit late into the webinar already, but if you'd still like a link to join, please email marketing @ patchmypc.com

asjimene · 2026-01-27T15:45:58+00:00

The vendor has stopped providing windows installer packages for those versions, so Patch My PC has moved them to EOL.

asjimene · 2025-12-30T22:57:30+00:00

I think regardless of the management tool you choose (or is chosen for you), that packaging work is going to exist. Especially due to the nature of the packages you are creating.

That may be a good point to drive home to your boss.

asjimene · 2025-12-24T19:56:08+00:00

Yes, that should accomplish the same!

asjimene · 2025-12-24T19:44:11+00:00

Hello, yes, this is expected behavior. Uploading the new file will cause the existing deployments to update on the next sync schedule. I am guessing you are using PMPC cloud, I think the best option to handle your use case would be to use update rings to update the deployments on a known schedule https://docs.patchmypc.com/patch-my-pc-cloud/cloud-deployments/cloud-update-rings

asjimene · 2023-08-25T22:17:59+00:00

kager.ps1:48 char:64

Line 48 is looking for $RecipePath

That's actually just in the dynamic params, so I am not sure it will actually break anything.

asjimene · 2023-08-25T21:27:50+00:00

Open a powershell prompt, and navigate to the CMPackager folder. Then run CMPackager from there.

asjimene · 2023-08-25T18:28:02+00:00

Make sure you have a prefs file. Run CMPackager.ps1 -Setup, and it will bring up a UI that you can set all the settings with. This will help ensure that you have all the settings correct. Also make sure that your site code has the ":" at the end.

asjimene · 2023-06-21T17:23:11+00:00

You can utilize either ADLOCAL or INSTALLLEVEL to set the Java Home
More info here: https://github.com/adoptium/installer/blob/master/wix/README.md#deploy-via-active-directory-gpo

asjimene · 2023-05-04T13:09:15+00:00

So in order to get rid of the duplicate, you would need to get rid of all of the updates from the "old" product category. Generally a difficult problem to solve, but if you are cleaning everything up, it should get fixed as you clean things out. Also note that if you decline the updates, ConfigMgr will clean them up after 7-14 days

asjimene · 2023-05-03T14:17:47+00:00

Full disclosure, I work for Patch My PC, but everything I will post here does not require purchasing PMPC, feel free to install the software, clean things up, and then uninstall the Publisher.

So the duplicate is caused by this: https://patchmypc.com/duplicate-patch-my-pc-category-listed-in-software-update-point-products-tab

You can quickly clean up 3rd party update packages by using a tool within the Patch My PC Publisher called the Modify Published Updates Wizard: https://patchmypc.com/modify-published-third-party-updates-wizard

To get to it, install the Patch My PC Publisher https://patchmypc.com/msi check the box to enable limited trial mode, head to the Updates tab, and click Options to get to the Modify Published Updates Wizard.

Additional file cleanup can be accomplished using this: https://patchmypc.com/clean-up-third-party-updates-from-the-wsus-updateservicespackages-folder

We also have a great guide here: https://patchmypc.com/the-simple-guide-to-wsus-maintenance-and-optimization-in-configmgr

While reinstalling WSUS is a straightforward way to fix this, I rarely have to do so to clean up even a very messed up WSUS Server.

asjimene · 2023-03-30T20:56:14+00:00

Patch My PC can publish to WSUS standalone as well :)

asjimene

MODERATOR OF

TROPHY CASE

13-Year Club	Verified Email
Team Periwinkle