call4cloud-code/intunewin-downloader-public

IntuneWin Downloader is a Windows troubleshooting tool for IT admins who work with Microsoft Intune. Intune is the system many companies use to push software to managed work laptops. When something goes wrong with an app install, the original package files are often hard to find or already gone. This tool lets the admin pull the same package the device is already allowed to receive, open it up, and try the installer locally to see what is happening. The tool shows a list of available Win32 apps from the Company Portal catalog, with icons, version, publisher, and status. The admin can select one or several apps, download them in parallel, and the tool will decrypt and extract the IntuneWin package contents into a folder. It also exports metadata, parses the Package.xml file when available, and builds a suggested install command from what the package describes. By default everything lands under C:\Temp\IntuneWinDownloader, with one folder per app. Once a package is extracted, the admin can run a local install test. The test window shows the exact command before it runs, captures the exit code, stdout, stderr, and any MSI log path, and can run either as the current elevated user or as SYSTEM through a temporary scheduled task. There is also an option to remove silent switches so the installer UI shows up. The README is clear that this is only a troubleshooting helper. It cannot grant access to apps the device is not already assigned, it does not change Intune configuration, and it does not fully reproduce what the Intune Management Extension does on a real install. Detection rules, requirement rules, dependencies, supersedence, retries, and reporting are not emulated. An exit code of 0 from the test does not guarantee the app is really installed correctly. The project requires a Windows device already managed by Intune and .NET 8. It runs locally and does not upload anything externally. There is no official support, and the author asks people not to contact Patch My PC support for it. The version history section in the README lists many iterations, with the current builds using a WinUI3 front end and a C# back end.