This release contains a variety of features, improvements, and fixes, as noted below.
This will be made available via the self-update channel over the coming days. You can upgrade in place now by downloading the latest MSI installer.
Features
- ARM Support for ConfigMgr and Intune
- Idea: PATCHMYPC-I-6792
- Note: To enable ARM support, you will need to navigate to the Advanced tab and check the box for ‘Enable support for ARM Architecture applications.’ For more information, please see the documentation.
- Allow Publisher to send emails using OAuth2.
- Idea: PATCHMYPC-I-571
Improvements
- Ensure the Publisher gracefully handles the case where the Publisher connection is deleted from the cloud.
- Ongoing improvement to UI validation
- Finish conversion of all sub-forms to modern UI framework.
- Add a tool to compare the publishing history CSV file to the configured tenants’ published Intune packages.
- Allow editing of the DO priority for multiple assigned applications at the same time
- Allow for SQL queries to take an extended period of time. A ConfigMgrJobTimeout registry key can be set alongside the SQLTimeoutinSeconds. SQLTimeoutinSeconds is limited to 3600 seconds. ConfigMgrJobTimeout is stored in minutes, and is limited to 60 minutes.
- Scanning Intune for Applications using the Intune Scan Wizard was very slow to process. This now runs in the background periodically and uses Caching, but the first scan can still be slow.
- Intune reports now run periodically in the background and cache for 8 hours to improve query speed.
- Update button behavior in WSUS tab to be consistent with other tabs.
- On startup, the Publisher only waits for supported products to be ready now. If catalog data is needed, then a check for catalog preparedness is ran. This improves UI startup after the service is restarted.
- Update Azure naming to Entra
- Publisher now creates Content Folder and Local Content Paths if they do not exist.
- Publisher now supports files that are compressed server-side with either gzip or deflate compression algorithms.
- Improved the accessibility of the Conflicting Processes notification. Buttons can now be selected using the Tab key.
- Load all Intune filters and do filtering client-side to improve performance and reduce reliance on graph api.
Fixes
- Fix a bug causing products marked for ‘Exclude from auto-publishing rules’ not be saved when the product treeview is filtered to enabled products only.
- Ensure the list of discovered devices with an application only includes unique device matches within the Intune scan wizard.
- Resolve an issue that causes the Publisher to improperly parse the installation command line for WSUS in some cases. This could result in an update being published with an incorrectly formatted installation command.
- Fixed a bug where some applications would not be found in the local content cache.
- Fix the WMI query used for getting ConfigMgr console folders. In some cases, this would cause a null reference exception in the PatchMyPC.log.
- Resolve a bug causing an exception to be logged “An error occurred while reporting: An item with the same key has already been added. [System.ArgumentException] HResult: -2147024809”
- Loading more groups in the Intune Assignment Group Selector did not load all groups correctly.
- Ensure the cloud connection displays disconnected after deleting the connection
- Updating an existing Intune Assignment from Required to Available did not work as intended if the modified assignment groups were All Devices and All Users
- Publisher would crash when importing settings that have Migration configured
- Prompt to save the configuration after changing the limiting collection for ConfigMgr database scan to ensure the collection is used for filtering.
- Connecting to Graph to query Assignment groups was slow.
- Fixed bug when the Intune retained application was deleted, even though the publish of the new version failed.
- Fixed bug with the show selected button and naming conventions
- Updated the temporary location of the settings.xml file during import to allow the file to properly overwrite the current settings.
- Selective Sync was not always correctly processed during a Sync.
- Ensured that when treeview refreshes, cached product selections are updated, and the filter to selected products checkbox is correctly reset to avoid confusion.
- Ensure long-running operations like scanning the ConfigMgr database or loading the list of WSUS updates do not timeout.
- Publisher no longer allows credentials to be provided for the SMS Provider when it is the local machine.
- Double-clicking an Entra group will now correctly show the group members
- Fixed bug with cloud connection button enablement
- The Publisher will no longer upgrade a retained ConfigMgr application in place. This prevents nested ‘Retained Apps’ folders from being generated.
- Publisher settings would sometimes be out of sync with the UI, causing apps to not be processed.
- Ensure we populate the list of configured Distribution Point Groups within the ConfigMgr options.
- Prevent the Publisher from indefinitely requesting a cloud access token when the connection has been deleted from the Patch My PC portal.
- The “Run installation and uninstall program as 32-bit process on 64-bit clients” option is now set as expected when needed.
- Ensure auto-enabled applications and updates have their detection-related properties appropriately set.
- In some cases, restoring the Publisher settings from backup would place files on the desktop unexpectedly.
- Remove the error message when the user exits the cloud connection dialog.
- Ensure the Server and Database names are saved to settings before querying ConfigMgr database in ConfigMgr Scan Wizard
- Fix issues with the filtered view
- Resolve an issue causing the CVE Import Wizard to not load updates.
- Fix the query used when updating dependencies for ConfigMgr applications. This ensure the Publisher appropriately copies forward dependencies when a new version is published.
- Publisher self update release notes linked to an old page.
- Product selections made in the Intune Scan Wizard did not persist after clicking Save & Close or Apply in Publisher UI.
- Fix log save location on the collect logs button to save to selected folder not parent folder
- Fix a bug where ConfigMgr update “Maximum run time” was not used by the Conflicting Processes notification.