Skip to main content

21 posts tagged with "PowerShell"

PowerShell

View All Tags

PowerShell 7.7 has no MSI: what it means for servers (and Nebula.Tools 1.0.8)

· 5 min read
Giovanni Solone
Former Batman, dad of Nebula modules

PowerShell 7.7 is the first release without an MSI installer: on GitHub you only find ZIP archives and an MSIX package. If you install or update PowerShell with the MSI, on servers or with deployment tools, you stay on 7.6 LTS, supported until November 14, 2028. Nebula.Tools 1.0.8 fixes Update-PS7, which reinstalled the same 7.6 release every time you ran it.

PowerShell no longer tells you about new releases (and Nebula.Core will)

· 3 min read
Giovanni Solone
Former Batman, dad of Nebula modules

If PowerShell 7 closed by itself right after start-up with totalWidth ('-5') must be a non-negative value, you met the bug that made Microsoft remove the update notice from PowerShell. The fix is in PowerShell 7.6.8, but from that release on PowerShell no longer tells you when a new version is out. Starting with Nebula.Core 1.3.1, Nebula does it for you.

PowerShell 7.6.6 freezes on Out-GridView (and every -GridView switch)

· 5 min read
Giovanni Solone
Former Batman, dad of Nebula modules

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.

Exchange Online and Microsoft Graph PowerShell assembly clash

· 16 min read
Giovanni Solone
Former Batman, dad of Nebula modules

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.