Create a separate Windows user with the same Microsoft account first; if that succeeds, migrate to that profile, and if it fails there too, use Windows 11’s repair reinstall before considering a reset or clean installation.
1. Isolate the existing Windows profile
Your Microsoft credentials are accepted initially, while the subsequent local credential transaction fails and rolls back. Since you have already validated the password, time, network, Hello setting, and IdentityCRL state, repeating those checks is unlikely to distinguish the fault.
- Open Settings → Accounts → Other users.
- Under Add other user, select Add account.
- Enter the same personal Microsoft account address and complete setup. This is the supported path for adding a Microsoft-account user. ^1^
- Sign out and try signing in to the newly created user.
Interpret the result:
- The new user works: the failure is confined to the original profile or its identity state. Make the new user an administrator, move your documents from the old profile, and reconfigure applications as necessary. Microsoft’s corrupted-profile procedure uses this new-profile-and-migration approach. Do not copy hidden or protected profile files because that can carry damaged profile state into the replacement. ^2^
- The same Microsoft-account operation fails for the new user: treat it as a system-wide Windows identity/component failure and continue with the repair reinstall below.
- Windows refuses to add that address because it is already associated with a user: create a temporary local administrator, sign into it, and retry the conversion there. This still provides the profile-isolation result without altering the current profile.
Back up important files before migrating or performing repair operations.
2. Repair Windows components without removing apps or data
Windows 11 provides an in-place repair through Windows Update that reinstalls the same Windows version, repairs system files and components, and preserves applications, files, and settings. ^3^
- Connect the Dell to power and the internet.
- Open Settings → System → Recovery.
- Under Fix problems using Windows Update, select Reinstall now.
- Complete the repair and restart.
- Retry Settings → Accounts → Your info → Sign in with a Microsoft account instead.
This is not a clean installation or Reset this PC. If the option is absent, the device may have Windows Update controlled by organizational policy; in that case, proceed to support rather than deleting identity or WMI data.
What 0x80041012 establishes
In the WMI API, 0x80041012 is WBEM_E_INVALID_PROVIDER_REGISTRATION, meaning a WMI provider has an incorrect or incomplete registration. ^4^
That numeric definition does not prove that the LiveId event represents a damaged WMI provider. Your event says the value was returned for a LiveId SOAP authentication request, and no public Microsoft documentation supplied here maps LiveId’s use of 0x80041012 to a specific Microsoft-account server condition. Numeric error values can be reused by different facilities and protocols.
Do not delete or rebuild the WMI repository solely because the number matches a WMI constant. Microsoft explicitly warns that WMI failures can originate elsewhere and that deleting the repository as a first action can damage Windows or installed applications. ^5^
The Security event combination 0xC000006D/0xC000006A records a failed password authentication transaction. It does not establish that the password you manually entered was wrong; it can reflect credentials or account context subsequently submitted by the conversion process.
Build and known-issue status
Build 26300.9974 / KB5132061 is the November 2026 General Availability build of Windows 11 26H2, not an Insider build. ^6^
The current 26H2 release-health page does not list LiveId 0x80041012, local-to-Microsoft-account conversion, or “device password incorrect” as a known issue. The issues listed for this build concern other areas, so there is currently no documented Known Issue Rollback or build-specific workaround for this symptom. ^7^
Escalation to Microsoft
Microsoft Support can investigate the Windows-side failure, but support agents cannot access or change protected Microsoft-account details or issue password-reset links. ^8^
Use the Get Help app and request Windows support. Provide:
- Windows 11 Pro 26H2, build
26300.9974, KB5132061
- Exact UTC timestamps for two fresh attempts
- LiveId events 6114 and 2028
- Security events 4648, 4738, 4724, and 4625
- The profile-isolation result
- Whether the repair reinstall changed the behavior
Also submit a Feedback Hub problem using Recreate my problem, reproducing one conversion attempt while recording diagnostics. Feedback Hub is the bug-reporting channel; Get Help is the channel for direct troubleshooting. ^9^
References
- Manage User Accounts in Windows | Microsoft Support
- Fix a corrupted user profile | Microsoft Support
- Fix issues by reinstalling the current version of Windows | Microsoft Support
- WbemErrorEnum enumeration (wbemdisp.h)
- WMI Error Constants
- Windows 11 release information
- Windows 11, version 26H2 known issues and notifications
- Change or reset your local account password in Windows | Microsoft Support
- Send feedback to Microsoft with the Feedback Hub app | Microsoft Support