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

Nebula.KB-dev is gone. The documentation for the development versions of the Nebula modules now lives here, on kb.gioxx.org, next to the documentation for the released versions.

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.

If you run a Nebula command with -GridView on PowerShell 7.6.6 and the console stops responding, the command is not slow and nothing is wrong with your tenant. On that release Out-GridView never returns and never opens its window, so the session is stuck until you close it.

Get-EntraGroupMembers "My Entra Group" -GridView   # never returns on PowerShell 7.6.6

The bug is in PowerShell itself, not in Nebula: a plain Get-Process | Out-GridView freezes in exactly the same way. Every Nebula command that offers -GridView is affected until you either update Nebula.Core or avoid that PowerShell release.

Updating PowerShell and the Microsoft 365 administration modules should be a routine maintenance operation. Unfortunately, a currently open regression can make the latest Exchange Online and Microsoft Graph modules fail when they are used in the same PowerShell 7 session.

The failure was first confirmed with PowerShell 7.6.4, ExchangeOnlineManagement 3.10.1, and Microsoft.Graph 2.38.1. A follow-up test with Microsoft.Graph 2.39.0 still found a conflict in the same combined session: Graph connected after the order change, but Exchange Online WAM failed with a RuntimeBroker/NullReferenceException. In the original Nebula flow, the error appeared while Connect-Nebula was establishing the Microsoft Graph session:

Connect-MgGraph:
InteractiveBrowserCredential authentication failed:
Method not found: '!0
Microsoft.Identity.Client.BaseAbstractApplicationBuilder`1.WithLogging(
Microsoft.IdentityModel.Abstractions.IIdentityLogger, Boolean)'.

This is not a permissions, Conditional Access, consent, or token-cache error. It is an in-process assembly dependency conflict between Microsoft modules.

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.

If you ever check both Nebula.KB-dev and kb.gioxx.org, there is one simple rule to keep in mind: the -dev documentation is usually the most up to date.