OutGridView freezes indefinitely in 7.6.6

Prerequisites

Write a descriptive title.
Make sure you are able to repro it on the latest released version
Search the existing issues.
Refer to the FAQ.
Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

Get-Process | Out-GridView

Expected behavior

Opening a GridView.

Actual behavior

Hangs forever, worked in 7.6.5, works in 5.1.

Error details

Hangs, so no output.

Environment data

Name                           Value
----                           -----
PSVersion                      7.6.6
PSEdition                      Core
GitCommitId                    7.6.6
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.4
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

No response

The problem occurs in v7.6.6. Downgrading to 7.6.5 resolve the issue.

I'm on the same build of Windows, & pwsh and not able to replicate this.

dl67

dl67 That's an interesting approach to fixing a bug.

Ryan Yates (@kilasuit) That's too bad, but it hasn't been working for me since version 7.6.6, so something must have changed. The shell freezes completely, and CTRL+C doesn't work then.

I'm on the same build of Windows

Note that $PSVersionTable output is all but useless, as it reflects obsolete data for backward compatibility reasons.

See Make $PSVersionTable report correct and relevant OS information, underlying .NET version, CPU architecture, OS display version on Windows #19121

Got exactly same issue:
Out-GridView completely freezes the terminal window. Can only kill the whole process to recover.
Used to work fine until a while ago, however cannot tell what exactly changed since last successful usage.

Edit after testing around a while:

Uninstalling any Windows updates since Sep-09 didn't make any difference.
Downgrading to PS 7.6.5 solved it, so seems to be only workaround currently.

$PSVersionTable:
Name                           Value
----                           -----
PSVersion                      7.6.6
PSEdition                      Core
GitCommitId                    7.6.6
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.4
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

SamLowryMOI

dl67 That's an interesting approach to fixing a bug.

SamLowryMOI: not really a fixing, but something that may help finding it since (at least in my configuration) the problem occurs with 7.6.6 and not 7.6.5.

I'm having the same problem here. In 7.6.5, Out-GridView works as expected and displays the UI. In 7.6.6, PowerShell freezes completely without displaying a UI.

I have confirmed several ways to work around the issue where Out-GridView fails to open — including the method already mentioned in this thread — and I'd also like to share what I found while investigating the reproduction of this issue, for those who are unable to reproduce it.

[Workarounds] ※The following is based on my own personal investigation, so please note this is not official information.

Downgrade
As already reported, downgrading to 7.6.5 or earlier allows Out-GridView to work.
Use the portable (.zip) build
Get the portable build (.zip) of 7.6.6 and use that instead.
If you'd like to use it as your standard setup, set your PATH so that the extracted portable files are launched preferentially. ※ I haven't tested it, but I'm sure it will work.
Temporarily set CurrentUICulture to en-US
Apply the following UI language setting before calling Out-GridView.
[System.Globalization.CultureInfo]::CurrentUICulture = 'en-US'
I've also confirmed that within a script, changing UICulture before calling Out-GridView allows Out-GridView to be invoked successfully.

[Reproducibility]
My phrasing was poor, but each item number represents an independent checkpoint, not a sequential step.

I have confirmed the following:

Reproducible with the installer (.msi) build. Reproduced on both the x64 and x86 versions.
Not reproducible with the portable (.zip) build (likely because it doesn't include the language-specific files).
I checked the following UICulture values for whether the issue occurs:

OK (no issue):

[System.Globalization.CultureInfo]::CurrentUICulture = 'en-US'
[System.Globalization.CultureInfo]::CurrentUICulture = 'fr-FR'
[System.Globalization.CultureInfo]::CurrentUICulture = 'ko-KR'
[System.Globalization.CultureInfo]::CurrentUICulture = 'ar-SA'  # No “ar” language folder in PowerShell
[System.Globalization.CultureInfo]::CurrentUICulture = 'bg-BG'  # No “bg” language folder in PowerShell

NG (issue occurs):

[System.Globalization.CultureInfo]::CurrentUICulture = 'ja-JP'
[System.Globalization.CultureInfo]::CurrentUICulture = 'es-PR'
[System.Globalization.CultureInfo]::CurrentUICulture = 'ru-RU'
[System.Globalization.CultureInfo]::CurrentUICulture = 'it-IT'

Not reproducible when launching after deleting my own language folder (in my case, ja) from the .msi installation.
Deleting the following file works around the issue.
With my language set to “ja,” deleting the following file caused Out-GridView to launch with the UI language set to English.
ja\Microsoft.PowerShell.GraphicalHost.resources.dll

[My hypothesis]
Based on the above, I suspect this may be caused by a localization-related
change between 7.6.5 and 7.6.6 though I haven't confirmed the exact root cause.

Not reproducible when launching after deleting my own language folder (in my case, ja) from the .msi installation.

I can confirm that. In my case, it's the “de” folder. After deleting it, the UI appeared when I ran Get-Process | Out-GridView.

tkmry

tkmry - thanks for the detail and additional workarounds as well as confirming that this is looking very much to be a localisation issue.

That's too bad, but it hasn't been working for me since version 7.6.6, so something must have changed.

SamLowryMOI - in the cmdlet itself nothing has changed for a long time, however the key things that have changed is the underlying dotnet version & how localisation is generated and packaged which for 7.6.5 & this is what has changed between 7.6.5 & 7.6.6.

With it being localisation related makes sense as why initially I couldn't replicate this as I'm running a en-GB environment but I can replicate this using the steps above.

Prior to 7.6.6 I don't see the localised Microsoft.PowerShell.GraphicalHost.resources.dll being added to folders like de or ja& whilst I'm decompiled these dlls forde&ja` AFAICT there's nothing wrong in them.

I think the next step in diagnosing this likely needs a full memory dump of pwsh process on an affected system.

Thank you for the kind words, and I'm glad to see this issue is now being investigated in earnest.

A few notes regarding capturing the memory dump:

The issue can also be reproduced with 1 | Out-GridView instead of Get-Process | Out-GridView, so I'm planning to use this simpler command instead.
To avoid including any unnecessary personal or environment-specific information, I'm planning to capture this in a virtual machine, provided no one else has already provided a dump before me.
The file size will likely be around 500 MB — what would be the best way to share it? I'd rather not host it on my own personal cloud storage. I'm not very familiar with the conventions here, so I'm not sure which of the following would be appropriate:
1. Can it be attached directly to this GitHub issue thread?
2. Would it be better to create a dedicated repository of my own and reference it from there?
3. Is there any other recommended method?

We quickly discussed this briefly in the Cmdlets Working Group & have reassigned this for discussion this evening in the Interactive UX Working group.

Thanks for reporting this issue!
The WPF key gesture tokens were not properly preserved during localization and caused this issue. I've submitted the PR to fix it.

I also reproduce this on PowerShell 7.6.6 with pt-BR UI culture.
In my case, changing CurrentUICulture to en-US made Out-GridView work again, which confirmed the localization issue.

The workaround that worked consistently for me, including inside the VS Code PowerShell extension, was renaming:
C:\Program Files\PowerShell\7\pt-BR\Microsoft.PowerShell.GraphicalHost.resources.dll to: Microsoft.PowerShell.GraphicalHost.resources.dll.bak

After restarting PowerShell/VS Code, Out-GridView started working normally again.

I documented the issue and workaround here:
https://storagenest.blob.core.windows.net/transfer/docs/erro-powershell-out-gridview.html

PowerShell 7.6.6 — Out-GridView travando em pt-BR
Problema no PowerShell 7.6.6 com Out-GridView em pt-BR e workaround aplicado.

I can repro this with de-DE as already stated by someone above.
Quite annoying. Hope this will be fixed soon and AutoUpdate through Windows Update should be stopped.
In my eyes the release 7.6.6 should be taken back and disable the nag-screen to update.

fix(gridview): avoid Out-GridView hang on PowerShell 7.6.6

fix(intune): fall back to console table when Out-GridView hangs on Po…

fix(gridview): avoid Out-GridView hang on PowerShell 7.6.6

docs(blog): warn about Out-GridView freeze on PowerShell 7.6.6

Navigation Menu

Repository navigation

OutGridView freezes indefinitely in 7.6.6 #27994

Prerequisites

Steps to reproduce

Expected behavior

Actual behavior

Error details

Environment data

Visuals

1 remaining item

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

OutGridView freezes indefinitely in 7.6.6 #27994

Description

Prerequisites

Steps to reproduce

Expected behavior

Actual behavior

Error details

Environment data

Visuals

Activity

dl67 commented on Sep 10, 2026

kilasuit commented on Sep 10, 2026

SamLowryMOI commented on Sep 10, 2026

mklement0 commented on Sep 10, 2026

uwe-braig commented on Sep 12, 2026

dl67 commented on Sep 12, 2026

anrichter commented on Sep 14, 2026

tkmry commented on Sep 15, 2026

SamLowryMOI commented on Sep 15, 2026

kilasuit commented on Sep 15, 2026

tkmry commented on Sep 15, 2026

1 remaining item

kilasuit commented on Sep 16, 2026

daxian-dbw commented on Sep 16, 2026

NicolaPicoli commented on Sep 18, 2026

MrFly72 commented on Sep 22, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions