Place .mez files in C:\Program Files\Microsoft Power BI Desktop\bin\Connectors\ during the repack. Ensure the ACLs allow all users to read.
Always deploy the newly packaged version to a pilot group of 5% of your user base before pushing it to the entire enterprise.
Use the file system detection method targeting PBIDesktop.exe or use the registry string located at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall associated with Power BI Desktop to ensure the software reporting mechanisms see the application as correctly installed.
Example automation skeleton (using Advanced Installer CLI): repack latest power bi desktop version work
Repack Latest Power BI Desktop Version: A Guide to Streamlined Enterprise Deployment
For the purposes of this guide, we will describe a applicable to any tool, plus a specific PSADT script approach for budget-conscious teams.
Yes, for internal deployment. Microsoft’s licensing allows IT administrators to repackage Microsoft software for internal deployment within their organization, provided you do not modify the core binaries or redistribute them externally. You are simply wrapping the installer. Use the file system detection method targeting PBIDesktop
Create a .reg file or inject these paths via your deployment script:
If your organization allows it, deploying via the Microsoft Store ensures automatic monthly updates without manual repackaging.
Deploying software across an enterprise requires control, predictability, and efficiency. Microsoft updates Power BI Desktop monthly. This frequent update cycle creates a continuous challenge for IT administrators. Standard executable installers often fail to meet the needs of automated, silent deployments. for internal deployment.
Use tools like 7-Zip to extract the contents of PBIDesktopSetup_x64.exe . Create Wrapper: Create a new MSI project.
Download and install an MSI editing tool such as Orca (available in the Windows SDK) or advanced packaging suites like Advanced Installer or Master Packager .
The latest versions of Power BI Desktop rely heavily on Microsoft Edge WebView2 for rendering visual elements. If your corporate environment strips out or blocks native Windows apps, ensure that WebView2 is listed as a prerequisite in your repackaging logic, or deploy it as a separate dependency prior to pushing the Power BI package. Test via System Account
When packaged applications fail to launch after successful installation, the culprit often involves missing dependencies captured during the packaging process. One administrator discovered that the Power BI installer installs Microsoft Edge WebView2 components that are critical for application functionality. Attempting to exclude these components from the package to reduce size resulted in launch failures. Including all files and registry entries created during the installation capture is essential for creating functional packages.
(Updated for latest monthly releases)