As a workaround I note that the Minecraft Legacy Launcher works as expected.
Thanks for the suggested steps - unfortunately non of them worked. In my case for step #3, only launcher_accounts_microsoft_store.json
existed. Before deleting it I confirmed the contents was:
{
"mojangClientToken" : ""
}
Once deleted, I relaunched the launcher, and the same issue persists. It's worth noting the launcher recreated launcher_accounts_microsoft_store.json
before I click "Microsoft Login"
My logs are very similar to others, i.e. lines such as
[Info: 2023-06-01 20:03:17.4294059: LauncherAppBrowser.cpp(83)] Will launch a Chromium subprocess with command line string: "C:\Program Files\WindowsApps\Microsoft.4297127D64EC6_1.2.4.0_x64__8wekyb3d8bbwe\Minecraft.exe" --type=renderer --log-severity=info --user-data-dir="%USERPROFILE%\AppData\Local\CEF\User Data" --launcherui --workdir="<WORKDIR>\.minecraft"
But no window pops up. Full logs at https://gist.github.com/danfoster/4dc2a9dcd685a472a1b7062783eca1c4
Hi,
Upon attempting to be able to send a recording via the feedback hub, I've stumbled on the fix. I'll describe my journey in the hope it helps narrow down the root cause.
I couldn't attach a recording to the bug report as I was told I needed to enable "Send optional diagnostic data".
When I went to "Privacy & security -> Diagnostics & feedback" to be told "your organisation prevents sending diagnostic data to Microsoft" even though this is a personal machine.
Eventually I found that removing one of the registry keys listed in this post allowed me to manage my down diagnostic data again and I could enable optional diagnostic data: https://answers.microsoft.com/en-us/windows/forum/all/windows-11-saying-some-of-these-settings-are/b31603cf-958e-426b-bf27-baa52c16e0d1
Unfortunately, I didn't capture which exact key it was.
Before continuing with the feedback hub, I decided to try launching Minecraft again, and this time the login window popped up as desired.
It worth noting that even with "Send optional diagnostic data" turned off, the login pop-up still works. Therefore it's not explicitly that toggle, but sometime related to the registry key that made settings think it was "Managed by my organisation".
Thinking back further, I did once try https://github.com/ChrisTitusTech/winutil - looking at the registry keys it adds, I can fairly confidently think this is the culprit: https://github.com/ChrisTitusTech/winutil/blob/main/config/tweaks.json#L1454