Forum Discussion

lornshrimp's avatar
lornshrimp
Brass Contributor
Oct 01, 2024

Major Bug in Windows 11 26120.1912 System Login Function

After upgrading the system to 26120.1912, the Windows system login function experiences a major malfunction, specifically:

  1. Clicking on Settings - Accounts - Sign-in options has no response, and it is impossible to enter the sign-in options settings interface.
  2. When the system starts or after it is locked, it stays on the user login screen and cannot enter the Windows desktop. The system can only be restarted, and after restarting, there is a high probability that it will still be stuck on the user login screen and unable to enter the desktop, with a small probability of successfully entering the desktop.

This bug is very serious and prevents users from accessing the system. We hope it can be fixed as soon as possible or a solution can be provided.

5 Replies

  • Mousefluff's avatar
    Mousefluff
    Iron Contributor

    lornshrimpThere is official documentation on how to sideload apps, possibly even the app store itself, though that's not the most common thing people would do. When doing offline deployment / provisioning of Windows images, sideloading is a normal process. This other link is an official repo for Winget, which is used by the operating system to install applications and frameworks. I used Winget to do everything btw, which may seem surprising if you're not used to that:

    Microsoft Store Apps fail to start if default registry or file permissions modified -> https://learn.microsoft.com/en-us/troubleshoot/windows-client/shell-experience/microsoft-store-apps-fail-to-start
    Volume Activation Technical Reference - Slmgr.vbs Options for Volume Activation -> https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn502540(v=ws.11)
    Windows volume activation - Troubleshoot Windows activation error codes -> https://learn.microsoft.com/en-us/troubleshoot/windows-server/licensing-and-activation/troubleshoot-activation-error-codes
    Windows Update error code reference -> https://learn.microsoft.com/en-us/windows/deployment/update/windows-update-error-reference
    NuGet Server API - Service index -> https://learn.microsoft.com/en-us/nuget/api/overview#service-index
    Use the WinGet tool to install and manage applications -> https://learn.microsoft.com/en-us/windows/package-manager/winget/
    Github - Windows Package Manager - Releases -> https://github.com/microsoft/winget-cli/releases
    C++ Runtime framework packages for Desktop Bridge -> https://learn.microsoft.com/en-us/troubleshoot/developer/visualstudio/cpp/libraries/c-runtime-packages-desktop-bridge#how-to-install-and-update-desktop-framework-packages
    [cmd.ms] the Microsoft Cloud command line! -> https://cmd.ms/
    akaSearch = Search for aka.ms! -> https://akasearch.net/
    aka.ms/commands -> https://github.com/microsoft/aka
    aka.ms/commands - readme -> https://github.com/microsoft/aka/blob/main/README.md

     

  • Mousefluff's avatar
    Mousefluff
    Iron Contributor

    lornshrimp Most people who experience this, are missing 5 apps that are installed by default. On the release channel build 26100.2033, this is also an issue.

     

    NOTE: If Task Manager is running, you can use both the Command Prompt, and the file manager built into Notepad's open file dialog box, as a temporary replacement for Windows Explorer. When you reset the Start Menu or another app, and those dependencies / frameworks are paused, but not staged, meaning they're physically not present, you didn't reset them first, then of course it will glitch out. Depending on the situation, if you close userinit.exe and shellhost.exe, which will constantly restart, it will stop flashing long enough for you to use xcopy without getting interrupted too many times.

     

    I mounted an RTM version of Win 11 24H2, with no patches, and copied them back over. Then I staged each one, by resetting them, before trying to reset the others. Btw even if you have to do this to activate Windows, they won't be fully functional UNLESS you have already activated your copy of Windows. So you will have to reset them, but you can't even fully utilize them until you activate. ( It will just give you access denied errors, meaning it will stay locked. This has little to do with AUMID or even the access control entries for that one set of files. What I mean, is that while that's important, it will only influence the outcome, once it's activated. ) This glitch appears when you go to reset an app without the dependencies / frameworks in place:

    "C:\Program Files\WindowsApps\Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe"
    "C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe"
    "C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.30704.0_x64__8wekyb3d8bbwe"
    "C:\Program Files\WindowsApps\Microsoft.NET.Native.Framework.2.2_2.2.29512.0_x64__8wekyb3d8bbwe"
    "C:\Program Files\WindowsApps\Microsoft.NET.Native.Runtime.2.2_2.2.28604.0_x64__8wekyb3d8bbwe"
    
    PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Get-AppxPackage -AllUsers Microsoft.UI.Xaml.2.8 | Reset-AppxPackage}"
    PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Get-AppxPackage -AllUsers Microsoft.VCLibs.140.00 | Reset-AppxPackage}"
    PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Get-AppxPackage -AllUsers Microsoft.VCLibs.140.00.UWPDesktop | Reset-AppxPackage}"
    PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Get-AppxPackage -AllUsers Microsoft.NET.Native.Framework.2.2 | Reset-AppxPackage}"
    PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Get-AppxPackage -AllUsers Microsoft.NET.Native.Runtime.2.2 | Reset-AppxPackage}"
    PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Get-AppxPackage -AllUsers Microsoft.StorePurchaseApp | Reset-AppxPackage}"
    PowerShell -NoProfile -ExecutionPolicy Bypass -Command "& {Get-AppxPackage -AllUsers Microsoft.WindowsStore | Reset-AppxPackage}"

     

  • FendiStave's avatar
    FendiStave
    Copper Contributor
    The recent update to Windows 11 version 26120.1912 has caused a critical bug affecting the login function. Users are unable to access Settings > Accounts > Sign-in options, and the system frequently gets stuck on the login screen after startup or lock, preventing access to the desktop. Restarting may occasionally allow access, but this is inconsistent. This issue needs urgent attention as it prevents users from accessing their systems. A prompt fix or workaround is needed.
  • BalazsOrban's avatar
    BalazsOrban
    Brass Contributor

    I have the same issue on one of my machines, but not on the other two oddly enough. I am on build 26100.2152.

     

    Also to add, 

    dsregcmd /status

    just hangs.

  • lornshrimp's avatar
    lornshrimp
    Brass Contributor
    I found that this bug was fixed in version 26120.1930, but it reappeared in version 26120.2122 with the exact same symptoms. So, I want to know what is going on with Microsoft. How can such a serious issue be ignored and left unaddressed?

Resources