Microsoft Intune and the tools around it
View All Tags
IntuneWinAppUtil GUI 1.1.3 is out on the PowerShell Gallery. It fixes a packaging failure that showed up on some machines as exit code -2147024891 (0x80070005, access denied). It also changes what you see while a package is being built.
Update-Module IntuneWinAppUtilGUI
IntuneWinAppUtil GUI 1.1.2 is a small follow-up to 1.1.1: if one of the module's scripts cannot be loaded, the import now stops with an error that names the file.
IntuneWinAppUtil GUI 1.1.1 is a fix for Windows PowerShell 5.1 users: versions 1.0.7 to 1.1.0 did not import correctly in the PowerShell built into Windows.
Update-Module IntuneWinAppUtilGUI
IntuneWinAppUtil GUI 1.1.0 accepts any file type as the setup file, not only EXE and MSI, and fixes the lag when typing in the Source Folder field.
IntuneWinAppUtil GUI 1.0.9 adds Get-IntuneFileVersion, a command that reads the FileVersion of a file, which is the value to use in an Intune detection rule based on a file version.
Get-IntuneFileVersion 'C:\Program Files\Contoso\App.exe'
IntuneWinAppUtil GUI 1.0.8 has a refreshed main window, better handling of PSAppDeployToolkit and MSI metadata, and a more reliable final rename of the package.
IntuneWinAppUtil GUI 1.0.7 warns you about paths that are too long before packaging, and tells you when a new version is available.
IntuneWinAppUtil GUI 1.0.6 fixes the package name proposed for PSAppDeployToolkit packages: the final file name is now proposed even when Invoke-AppDeployToolkit.ps1 does not set AppVersion.
IntuneWinAppUtil GUI 1.0.5 is an emergency fix for 1.0.4, which shipped without the Show-IntuneWinAppUtilGui command. 1.0.4 has been removed from the PowerShell Gallery.
Update-Module IntuneWinAppUtilGUI
IntuneWinAppUtil GUI 1.0.4 brought a round of input checks and a code cleanup. It was withdrawn from the PowerShell Gallery the same day: the package did not export Show-IntuneWinAppUtilGui, so the GUI could not be started. 1.0.5 replaced it about twenty minutes later with the same changes.