Install & Uninstall iMazing in Enterprise Environments
Updated on Apr 1, 2026
Reading time ~9 minutes
Silent Installation on Windows
To install iMazing silently, open a Windows Command Prompt with administrative privileges or use Intune (https://learn.microsoft.com/en-us/intune/intune-service/fundamentals/what-is-intune). Then, execute the following command, making sure to replace <path to installer> with the path to the location where the iMazing Installer is located:
"<path to installer>\iMazing3forWindows.exe" /verysilent /closeapplications /suppressmsgboxes /dontstart
To prevent iMazing Installer from automatically launching iMazing at the end of the installation, you can pass the parameter /dontstart, as shown in the example above.
Automatic Apple Components Installation
Starting from version 2.17, iMazing Installer can download all necessary Apple components from the Microsoft Store to install them. iMazing Installer will place all components in the following folder:
C:\ProgramData\DigiDNA\iMazing\MobileDevice
To troubleshoot Apple components installation, a log file is created at this path:
C:\ProgramData\DigiDNA\iMazing\MobileDevice\log.txt
Ensure that the computer on which iMazing Installer is running can access the domain names used to download the components:
downloads.imazing.comtlu.dl.delivery.mp.microsoft.com
To disable automatic installation of Apple components, pass the following argument to iMazing Installer:
"<path to installer>\iMazing3forWindows.exe" /dontinstallapplecomponentsNote that if iMazing Installer is unable to connect to these domains, Apple components and drivers will not be installed. To install Apple components manually, you will first need to download iTunes’ installer, follow the steps below.
Custom Apple Components Installation
First, download the standalone version of iTunes. Then, follow the instructions below:
- For Windows 64-bit systems: https://www.apple.com/itunes/download/win64
- For Windows 32-bit systems: https://www.apple.com/itunes/download/win32
Apple Components installation for Windows 64-bit systems:
- Once iTunes is downloaded, extract the contents of iTunes64Setup.exe to the location of your choice using 7zip (https://www.7-zip.org) or WinRAR (https://www.win-rar.com). Here is the list of files required to install Apple components contained in the iTunes64Setup.exe package:
AppleMobileDeviceSupport64.msi
- Then open a Windows Command Prompt with administrative privileges and type in the following commands making sure to replace
<path to installer>with the path to the files you've just extracted:
"<path to installer>/MobileDeviceSupport64.msi" /quiet /qnApple Components installation for Windows 32-bit systems:
- Once iTunes is downloaded, extract the contents of iTunesSetup.exe to the location of your choice using 7zip (https://www.7-zip.org) or WinRAR (https://www.win-rar.com). Here is the list of files required to install Apple components contained in the iTunesSetup.exe package:
AppleMobileDeviceSupport.msi
- Then open a Windows Command Prompt with administrative privileges and type in the following commands making sure to replace
<path to installer>with the path to the files you've just extracted:
"<path to installer>/MobileDeviceSupport.msi" /quiet /qnSilent Uninstallation on Windows
To uninstall iMazing silently please open a Windows Command Prompt with administrative privileges and execute the following command:
"C:\Program Files\DigiDNA\iMazing\unins000.exe" /verysilent /closeapplications /suppressmsgboxes
When running the uninstaller silently, the computer will automatically restart to unregister iMazing's Windows Explorer shell extension (which manages drag and drop functionality from iMazing).
Remove iMazing working directory, activated license and preferences from the local hard drive
C:\Users\<username>\AppData\Roaming\iMazing(Beware, iMazing backups are by default located in:C:\Users\<username>\AppData\Roaming\iMazing\Backups)C:\Users\<username>\AppData\Local\DigiDNAC:\ProgramData\DigiDNA\iMazing
Remove other remaining Windows Registry keys completely
Computer\HKEY_CURRENT_USER\Software\Classes\.imazingComputer\HKEY_CURRENT_USER\Software\Classes\.imazingappComputer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.imazingComputer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.imazingappComputer\HKEY_CURRENT_USER\Software\DigiDNA\\iMazingComputer\HKEY_CURRENT_USER\Software\DigiDNA\iMazingMiniComputer\HKEY_CURRENT_USER\Software\iMazingComputer\HKEY_CURRENT_USER\Software\iMazingMini
Apple Components complete uninstallation when installed via the custom installation method
To uninstall all apple compoents silently please open a Windows Command Prompt with administrative privileges and execute the following commands.
if exist "%COMMONPROGRAMW6432%\Apple\Mobile Device Support" wmic product where name="Apple Mobile Device Support" call uninstall /nointeractive
if exist "%COMMONPROGRAMFILES%\Apple\Mobile Device Support" wmic product where name="Apple Mobile Device Support" call uninstall /nointeractive
if exist "%COMMONPROGRAMFILES(X86)%\Apple\Mobile Device Support" wmic product where name="Apple Mobile Device Support" call uninstall /nointeractive
if exist "%COMMONPROGRAMW6432%\Apple\Apple Application Support" wmic product where name="Apple Application Support (64-bit)" call uninstall /nointeractive
if exist "%COMMONPROGRAMFILES%\Apple\Apple Application Support" wmic product where name="Apple Application Support (32-bit)" call uninstall /nointeractive
if exist "%COMMONPROGRAMFILES(X86)%\Apple\Apple Application Support" wmic product where name="Apple Application Support (32-bit)" call uninstall /nointeractive
if exist "%PROGRAMW6432%\Bonjour" wmic product where name="Bonjour" call uninstall /nointeractive
if exist "%PROGRAMFILES%\Bonjour" wmic product where name="Bonjour" call uninstall /nointeractive
if exist "%PROGRAMFILES(X86)%\Bonjour" wmic product where name="Bonjour" call uninstall /nointeractiveNote: if you want to continue to use iTunes, you shouldn't uninstall Apple components.
Automatic Activation with License Code
Windows
To automate activation on Windows, you can create a text file license.txt containing the license code at the following user path:
C:\Users\<username>\AppData\Roaming\iMazing\license.txt
Replace
<username>by the username.
or at the following computer-wide path for all users:
C:\ProgramData\DigiDNA\iMazing\license.txt
Tip: you can also add a
deleteLicenseFileempty file in the same location as thelicense.txtfile. This will delete thelicense.txtfile after iMazing is activated, preventing users from accessing the license code.
On Windows you can alternatively pass the license code to the iMazing Installer, that way:
"<path to installer>\iMazing3forWindows.exe" /license=<license_code>Note: Replace
<path to installer>by the path pointing to the installer and<license_code>by your license code.Tip: you can also add an argument
/deletelicensefile. This will delete thelicense.txtfile after iMazing is activated, preventing users from accessing the license code.
macOS
To automate activation on macOS, you can create a text file license.txt containing the license code at the following user path:
/Users/<username>/Library/Application Support/iMazing/license.txt
Replace
<username>by the username.
or at the following computer-wide path for all users:
/Users/shared/iMazing/license.txt
Tip: you can also add a
deleteLicenseFileempty file in the same location as thelicense.txtfile. This will delete thelicense.txtfile after iMazing is activated, preventing users from accessing the license code.
Connecting to the iMazing Licensing System
iMazing will need to connect to the following domain name to communicate with iMazing’s licensing system:
api.imazing.com
iMazing will be activated automatically when launched. In addition, depending on the feature you use, you will need to whitelist certain domains that iMazing will connect to. A full list of what iMazing connects to and why is available here:
https://support.imazing.com/hc/en-us/articles/360010474920-List-of-domains-iMazing-connects-to
File Locations: Preferences, Backups, Library, and Cache Data
iMazing stores important data in several folders: preferences, backups, library (for downloaded iOS/iPadOS apps .ipa and OS images .ipsw), and cached files.
Windows
- Preferences:
C:\Users\<username>\AppData\Roaming\iMazing\Prefs - BackupLocations.plist: backup locations
- Devices.plist: devices paired with iMazing
- Organizations.plist: supervising organizations (without their identities (certificates and private keys) which are stored in the Windows Certificate Store
- Prefs.plist: iMazing non-UI preferences
- Schedules.plist: automatic backup preferences for iMazing Mini
- Shortcuts.plist: file system and app shortcuts
- UI Preferences:
C:\Users\<username>\AppData\Local\DigiDNA(UI and automatic updates) - Default backup location :
C:\Users\<username>\AppData\Roaming\iMazing\Backups - One folder per device backup, each named with the device's UDID
- Default backup snapshots location :
C:\Users\<username>\AppData\Roaming\iMazing\Backups\iMazing.Versions - Blueprints: editable backups
- Temp: temporary backups built during restore operations. All files stored in this folder are automatically deleted when iMazing launches or quits.
- Trash: deleted backups that are being removed in the background
- Versions: backup snapshots per device
- Note: All the above folders contain hard links pointing to the main related backup folder. Do not move or edit files manually, as this would result in corrupted backup snapshot chains. Also note that Windows File Explorer cannot properly calculate storage usage for hard links, which leads to misleading reported sizes.
- Default library location:
C:\Users\<username>\AppData\Roaming\iMazing\Library - Apps.plist and Apps folder: downloaded
.ipafiles - Blueprints.plist and Blueprints folder: iMazing Configurator blueprints
- Profiles folder: configuration and provisioning profiles
- Systems folder: IPSW OS installation images stored in library
- Apps.plist and Apps folder: downloaded
- Caches:
C:\Users\<username>\AppData\Roaming\iMazing\Caches - One folder per device, each named with the device's UDID
- Temporary:
C:\Users\<username>\AppData\Roaming\iMazing\Caches\Temp - All files stored in this folder are automatically deleted when iMazing launches or quits
- Logs:
C:\Users\<username>\AppData\Roaming\iMazing\Caches\Logs - Pairing records:
C:\ProgramData\Apple\Lockdown\ - Apple Drivers installed by iMazing:
C:\ProgramData\DigiDNA\iMazing\MobileDevice(downloaded during iMazing installation) - Apple Drivers installed by iTunes:
C:\Program Files\Common Files\Apple\Mobile Device Support(installed during iTunes installation)
macOS
- Preferences:
/Users/<username>/Library/Application Support/iMazing/Prefs - BackupLocations.plist: backup locations
- Devices.plist: devices paired with iMazing
- Organizations.plist: supervising organizations (without their identities (certificates and private keys) which are stored in the macOS Keychain
- Prefs.plist: iMazing non-UI preferences
- Schedules.plist: automatic backup preferences for iMazing Mini
- Shortcuts.plist: file system and app shortcuts
- USBPort.plist: USB port mapping for iMazing Configurator
- UI Preferences:
/Users/<username>/Library/Preferences/ com.DigiDNA.iMazing2Mac.plist(UI and automatic updates) - Default backup location:
/Users/<username>/Library/Application Support/iMazing/Backups - One folder per device backup, each named with the device's UDID
- Default backup snapshots location :
/Users/<username>/Library/Application Support/iMazing/Backups/iMazing.Versions - Blueprints: editable backups
- Temp: temporary backups built during restore operations. All files stored in this folder are automatically deleted when iMazing launches or quits.
- Trash: deleted backups that are being removed in the background
- Versions: backup snapshots per device
- Note: All the above folders contain hard links pointing to the main related backup folder. Do not move or edit files manually, as this would result in corrupted backup snapshot chains. Also note that Finder cannot properly calculate storage usage for hard links, which leads to misleading reported sizes.
- Default library location:
/Users/<username>/Library/Application Support/iMazing/Library - Apps.plist and Apps folder: downloaded
.ipafiles - Blueprints.plist and Blueprints folder: iMazing Configurator blueprints
- Profiles folder: configuration and provisioning profiles
- Systems folder: IPSW OS installation images stored in library
- MDMServer.plist: MDM servers configured in iMazing Configurator
- Apps.plist and Apps folder: downloaded
- Caches:
/Users/<username>/Library/Application Support/Caches/iMazing - One folder per device, each named with the device's UDID
- Temporary:
/Users/<username>/Library/Application Support/Caches/iMazing/Temp - All files stored in this folder are automatically deleted when iMazing launches or quits
- Logs:
/Users/<username>/Library/Application Support/Caches/iMazing/Logs - Pairing records:
/var/db/lockdown(protected and not accessible without SIP disabled) - Apple Drivers:
/System/Library/PrivateFrameworks/MobileDevice.framework(managed by macOS)
Domains Required by iMazing
iMazing keeps all data local. Your iOS device data is only stored in iMazing's Cache folder and your chosen backup location—never on our servers.
To ensure all iMazing features function properly, whitelist these domain names for ports 80 and 443.
Installing or updating iMazing and Apple components:
downloads.imazing.com- iMazing updates
tlu.dl.delivery.mp.microsoft.com- Apple components’ updates for Windows, downloaded from the Microsoft Store
iMazing licensing system:
imazing.com- iMazing embedded store
store.imazing.com- iMazing embedded store
api.imazing.com- iiMazing's licensing and activation system
Features relying on Apple servers:
*.apple.com- Activating new or erased devices
- Installing or reinstalling iOS, iPadOS, and macOS on Apple Silicon (IPSW downloads)
- Downloading iCloud data
- Searching and downloading App Store apps
- App Volume Purchasing (VPP) license management
*.mzstatic.com- Apple's Content Delivery Network (CDN) that supports some of the features listed above
Spyware Analyzer:
The Spyware Analyzer needs to resolve HTTP redirects for URLs found in analyzed device data. To detect spyware, iMazing must be able to send HTTP requests to any domain or IP address.
downloads.imazing.com- Downloading the up-to-date list of indicators of compromise (IoCs) used for analysis
raw.githubusercontent.com- Downloading indicators of compromise (
.stixfiles)
- Downloading indicators of compromise (
Issue reporting:
sentry.io*.sentry.io
Network connectivity check:
If iMazing fails to contact its activation server on api.imazing.com, it will perform a sanity check and attempt to reach Google or Baidu. No information is exchanged with Google and Baidu servers–iMazing strictly performs a reachability check.
google.combaidu.com
Customer Experience Program:
When users opt in to participate in the Customer Experience Program, iMazing sends anonymized usage data to Google Analytics, our platform for collecting anonymous usage statistics to help improve our product. We record in-app navigation events, without any user data.
Third-Party Libraries Used by iMazing
iMazing leverages these third-party packages:
- boost
- BoringSSL
- ccard
- Chilkat
- ColorSetKit
- CoreCrypto
- CoreFoundation++
- CPPAtomic
- dirent
- dlib
- exif
- FunctionalSharp
- gmock-xcode
- heic-convert
- HTML Renderer
- ID3v2
- idevice
- ISOBMFF
- libarchive
- libavutil / libswresample / libavcodec / libavformat
- libgpod
- libjpeg
- libmediainfo
- libmtp
- libpng
- libusb
- libwebp
- libzip
- macho
- macos-unifiedlogs
- mp3lame
- objc-uti
- OBJCXX
- Objective-CPP
- PDFLib
- PDFsharp
- PIMPL
- Protocol Buffers
- Sentry
- SQLite
- SRPXX
- SWIG
- TagLib
- UTI
- ValueTransformers
- XS++
- zenlib
- zlib
iMazing bundles iMazing Profile Editor which leverages these third-party packages:
- Device Management Client Schema
- EonilFSEvents
- plist-cil
- PlistCS
- ProfileManifests
- YamlDotNet
- .NET