iMazing Profile Editor 2.0.0 for Windows Release Notes
Version 2.0.0, release date: Mon, 02 Feb 2026 16:33:23 +0100
What's New in iMazing Profile Editor 2.0.0 for Windows
Improvements in 2.0.0
- Payloads can now be imported from plist
- Payloads can now be imported from other profiles
- Payloads can now be exported to macOS shell script (macOS user preference payloads only)
- Payload export to plist is now also supported on unfamiliar payloads
- Common payload properties can now be included when exporting payloads to plist
- All profile identifiers and UUIDs can now be reset from the menu and are reset by default on a profile Save-As
- Managed Client (MCX) payloads can now be displayed and edited
- Payloads can now be converted to and from MCX (macOS user preference payloads only)
- visionOS configuration and validation are now supported
- The profile identifier prefix, which distinguishes locally created profiles from MDM ones, now defaults to the name of the editing app instead of the authoring machine, and can now also be set to none
- Multiple installed signing certificates with the same subject name can now be distinguished by their serial number
- File and folder selection now uses modern Windows dialogs which enables path pasting and advanced options
- The UI has received a refresh
Fixes in 2.0.0
- Fixed a rare issue that led to an app crash when selecting bundle ID
- Fixed an issue that led to an app crash on Windows versions prior to 10 1809 (10.0.17763)
- Resolved an issue that caused required properties to be set to their default value on profile load
- Property presence documentation updated to distinguish conditional requirement
- Fixed an issue that caused the group selector to remain visible in collapsed payloads
- Fixed the incorrect entry field for code requirement in the Parental Controls: Application Restrictions section
- Fixed an issue that disabled conditionals on dictionary-nested properties
- Fixed incorrect grouping and exclusion of a Restrictions preference key
Other notes for 2.0.0
- The direct distribution version of iMazing Profile Editor now requires Windows 10 1607 (10.0.14393) or higher
What's New in iMazing Profile Editor 1.8.2 for Windows
Fixes in 1.8.2
- Fixed an issue that prevented correct conditional evaluation under certain circumstances
- Fixed an issue that in some cases led to a crash when a property's conditional requirement changed
- Removed redundant error label in image fields
What's New in iMazing Profile Editor 1.8.1 for Windows
Fixes in 1.8.1
- Fixed issue with presence conditional evaluation
- Resolved issue with selection in boolean popup buttons on non-English machines
What's New in iMazing Profile Editor 1.8.0 for Windows
Improvements in 1.8.0
- A new information popover now features expanded documentation, availability, and community notes for both configuration payloads and properties
- String fields can now suggest common values while still allowing custom ones. For example the Extension Identifier field in the Single Sign-On Extensions section
- In accordance with advice from Apple, iMazing Profile Editor will no longer rotate profile or payload UUIDs when saving profile changes
- Table-nested boolean properties now better support the latest improvements to the PPPC section
Fixes in 1.8.0
- Fixed incorrect validation of integer properties with a value range
What's New in iMazing Profile Editor 1.7.2 for Windows
Improvements in 1.7.2
- Dictionary properties can now partake in exclusion of other properties, improving interactivity in the Wi-Fi section
Fixes in 1.7.2
- Fixed incorrect validation of the maximum range restriction for array properties
- Fixed an issue that prevented combo-boxes from displaying boolean properties
What's New in iMazing Profile Editor 1.7.1 for Windows
Fixes in 1.7.1
- Resolved an issue that caused certain table columns to be presented together as one custom dictionary
- Fixed the incorrect reporting of available manifest update
- Fixed issues that led the app to crash on certain user actions in table fields
- Resolved an issue with the factory restore functionality
- Fixed a number of visual glitches
What's New in iMazing Profile Editor 1.7.0 for Windows
Improvements in 1.7.0
- All plist data types are now supported in table fields, adding Data, Date, custom Array, and custom Dictionary
- All table input fields now support interaction and type adapters similar to their free-standing counterparts
- Microsoft Edge's
ManagedFavorites as well as both Google Chrome's and Brave's ManagedBookmarks are now fully supported thanks to new non-homogeneous array handling capabilities
Fixes in 1.7.0
- Fixed issues that prevented correct loading, entry, and saving of data in complex array properties which affected sections such as Parental Controls: Application Access, Nudge, and NoMAD Shares
- Fixed issues with displaying placeholders in various text-entry fields
- Fixed an issue with validating maximum repetition of properties in arrays
- Fixed an issue that led the section error counter to not reset correctly
- Fixed an issue that led to a crash when configuring a Microsoft OneDrive payload
- Fixed the rejection of a leading forward slash character in X.500 fields
What's New in iMazing Profile Editor 1.6.8 for Windows
Improvements in 1.6.8
- Added watchOS as a configurable platform
Fixes in 1.6.8
- Fixed incorrect preference key maximum version evaluation
- Fixed missing display names in the payload selection dialog window
- Resolved incorrect validation of required arrays
- Addressed inability to load certain certificate formats as root
What's New in iMazing Profile Editor 1.6.7 for Windows
Improvements in 1.6.7
- Unfamiliar payload keys (those loaded from file but not matched to keys in the payload manifest) are now kept on save and can be optionally removed
Fixes in 1.6.7
- Resolved manifest optimizations not updating on unchanged remote manifests
What's New in iMazing Profile Editor 1.6.6 for Windows
Improvements in 1.6.6
- Key description can now be optionally shown for boolean properties (checkboxes)
- Table rows can now be duplicated when working with array-based properties
Fixes in 1.6.6
- Fixed an issue that prevented search term highlighting on boolean property titles
- Fixed an issue that prevented value-indicators from displaying correctly for array-based properties
What's New in iMazing Profile Editor 1.6.5 for Windows
Fixes in 1.6.5
- Fixed an issue that led to the app crashing in rare circumstances
What's New in iMazing Profile Editor 1.6.4 for Windows
Improvements in 1.6.4
- The Profile Signing field now indicates which identities are trusted on the signing computer
- The Root Certificate manifest now has its own section
- Profiles can now also be signed without installing the signing identity's full chain of trust on the signing computer
What's New in iMazing Profile Editor 1.6.3 for Windows
Fixes in 1.6.3
- Fixed an issue that led to the app crashing on startup under certain conditions (Microsoft Store only)
What's New in iMazing Profile Editor 1.6.2 for Windows
Improvements in 1.6.2
- Multiple stability improvements
What's New in iMazing Profile Editor 1.6.1 for Windows
Improvements in 1.6.1
- iMazing Profile Editor now bundles the latest preference updates introduced with iOS 16
Fixes in 1.6.1
- Fixed a rare visual glitch in the display of platform tags.
What's New in iMazing Profile Editor 1.6.0 for Windows
Improvements in 1.6.0
- Platform tags now feature version and lifecycle stage information
- Platform tags added to configured sections and to individual preference keys. On keys, tags appear by default only if the individual key's versions are divergent from the payload's
- Target devices version range can now be entered to receive out-of-range alerts on configured preference keys
- Key requirement is now ignored in nested-required keys whose container is not required and is not written out to the profile
- Documentation buttons added to individual preference keys where available
What's New in iMazing Profile Editor 1.5.3 for Windows
Fixes in 1.5.3
- Fixed an issue that under certain configurations prevented the saving of VPN and other payloads
- Fixed an issue that prevented the payload removal button from appearing on certain payloads
- Fixed an issue that made certain preference conditionals skip evaluation on initial values
- Fixed a display issue with in-array Boolean properties
- Fixed an issue that led to the app crashing in rare circumstances
What's new in iMazing Profile Editor 1.5.2
Improvements in 1.5.2
- In compliance with recent configuration profile changes announced by Apple, generated PayloadIdentifier values are now guaranteed to be unique
- PayloadUUID values are now automatically regenerated when a saved payload changes, except in Certificate payloads
- Preference keys in the Restrictions section have been reorganized into more groups
- Section documentation can now be accessed via a new dedicated button as well as via a new help menu option (where available)
- String fields in arrays now support line breaks using Ctrl+Shift+Enter and on paste
- Misconfigured boolean fields can now display errors similar to other field types
- Local caches of inactive manifest repositories are now cleaned on launch
- Bundled preference manifests updated to the latest available
- Maintenance options are now available in the Preferences window
Fixes in 1.5.2
- Fixed an issue that in some cases prevented manifest updates when changing to a different branch in the same repository
- Fixed an issue preventing values of boolean preference keys without known default from staying set when toggled
- Matched the behavior of integer preference keys presented as booleans to that of native booleans in the context of setting to a known default value
What's new in iMazing Profile Editor 1.5.1
Fixes in 1.5.1
- Resolved issue preventing profiles which contain multiple payloads of the same type from being deployed to iOS 15. Learn more here: https://digidna.notion.site/IPE-Profiles-iOS-15-Compatibility-0cd72002024c435a96f37bfe6a83e21a
What's new in iMazing Profile Editor 1.5
Improvements in 1.5
- Preference manifests are now updated in-place from an online repository
- The User PFM files folder option has been renamed to Local folder for custom and override preference manifests and manifests in that folder can now override those from the online repository
- Users can now also define a local repository which can be either a local checkout of ProfileManifests (or forks) or any folder containing at least the general settings manifest
- Profile signing is now a preference in the General settings section
- Unfamiliar configuration payloads which are those whose domain lacks a defining preference manifest, are now preserved on profile save and can be optionally removed
- Support added for custom Dictionary properties via dictionaries loaded from Plist files
- Support added for string entry in Data properties that represent hexadecimal strings
- Capabilities added for integration with third-party system management software
- Notice alerting of failed profile saves added
- Bundled preference manifests updated to the latest available
Fixes 1.5
- Fixed an issue that led to crashes in rare occasions