We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
not relevant for this issue
PublicClient - desktop app
This is a new app or experiment
The code from https://learn.microsoft.com/en-us/entra/msal/dotnet/acquiring-tokens/desktop-mobile/wam#parent-window-handles no longer works correctly with Windows Termin v1.22+, as the handle points to a hidden pseudo console.
No response
Please update the sample code so that also works with Windows Termin v1.22+ and hidden pseudo consoles.
Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)
The text was updated successfully, but these errors were encountered:
Windows Termin 1.22.2702.0 has been released, with the handle pointing to a hidden pseudo console.
Does someone already have an idea how to get the correct parent window handle now?
Sorry, something went wrong.
No branches or pull requests
Library version used
not relevant for this issue
.NET version
not relevant for this issue
Scenario
PublicClient - desktop app
Is this a new or an existing app?
This is a new app or experiment
Issue description and reproduction steps
The code from https://learn.microsoft.com/en-us/entra/msal/dotnet/acquiring-tokens/desktop-mobile/wam#parent-window-handles no longer works correctly with Windows Termin v1.22+, as the handle points to a hidden pseudo console.
Relevant code snippets
No response
Expected behavior
Please update the sample code so that also works with Windows Termin v1.22+ and hidden pseudo consoles.
Identity provider
Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)
Regression
No response
Solution and workarounds
No response
The text was updated successfully, but these errors were encountered: