Azure Storage Explorer authentication fails on M3 MacBook Pro (macOS ARM64) – Hub Controller exits with code 131

[taoye0330]

I am unable to sign in to my Azure account using Microsoft Azure Storage Explorer on an M3 MacBook Pro.

I downloaded and installed the macOS ARM64 version of Azure Storage Explorer. When I try to authenticate/sign in to my Azure account, the sign-in page keeps loading indefinitely and authentication never completes.

Storage Explorer displays the following error:

The authentication library used by Storage Explorer has failed to start properly. Please ensure you have .NET 10 installed. If .NET 10 is already installed then refer to the troubleshooting guide for help. Verbose authentication logging has been enabled.

Error: Hub Controller process exited prematurely with exit code 131.

Environment
Device: MacBook Pro with Apple M3
Architecture: ARM64 / Apple Silicon
OS: macOS
Storage Explorer: macOS ARM64 version
Authentication: Azure/Microsoft account sign-in
.NET requirement referenced by error: .NET 10
Steps to Reproduce
Install the macOS ARM64 version of Microsoft Azure Storage Explorer on an M3 MacBook Pro.
Launch Storage Explorer.
Select the option to sign in with an Azure account.
Start the authentication process.
The sign-in interface continues loading and authentication does not complete.
Storage Explorer reports that the authentication library failed to start and that the Hub Controller process exited with code 131.
Expected Behavior

Storage Explorer should launch the Microsoft authentication flow and allow me to sign in to my Azure account.

Actual Behavior

The authentication interface keeps loading and eventually reports:

Hub Controller process exited prematurely with exit code 131

Storage Explorer also indicates that the authentication library failed to start properly and asks me to ensure that .NET 10 is installed.

Additional Information

This appears to happen before Azure account authentication itself completes, so it may be related to the local authentication library / Service Hub / .NET runtime initialization on macOS ARM64 rather than Azure account permissions.

I would appreciate guidance on:

Whether this is a known issue with Apple Silicon/M3 Macs and the ARM64 build.
Which specific .NET 10 runtime/build is required.
Whether Storage Explorer expects .NET to exist at a particular path on macOS.
Whether there are additional logs I can provide to help diagnose the Hub Controller exit code 131.

[charan-kamasani]

Thanks for the detailed report. Exit code 131 on macOS typically means the Hub Controller process was terminated by the operating system before it could initialize, which usually points to a missing or incompatible .NET 10 runtime.

Could you confirm the following?

1. Is .NET 10 installed? You can check by running dotnet --list-runtimes in Terminal. We require a macOS ARM64 build of the .NET 10 runtime.
2. If .NET is installed, does dotnet --info show arm64 as the architecture (not x64 running under Rosetta)?
3. Please share your Storage Explorer logs (Help > Open Log Folder) — the hub-controller logs in particular would help us identify the exact failure.