Hi Ivan,
Thanks for the reply. A bit more context that should help skip a few steps:
I've already tested this across accounts — I checked another Administrator profile on the same machine, and the taskbar/system tray/audio problems occur there too. So this isn't a single corrupted user profile; it's system-wide. I also confirmed my account is genuinely in the Administrators group (net localgroup administrators shows it), and I can get a real High-integrity elevated token via Task Manager → Run new task with admin privileges — whoami /all confirms BUILTIN\Administrators is enabled, not deny-only. So this isn't a standard permissions issue either; msconfig's error message appears to be a misleading symptom of deeper corruption rather than an actual privilege problem.
Where I'm actually stuck: I already agree a clean install is likely necessary — component-store corruption is confirmed via DISM /ScanHealth, and CBS.log shows CBS_E_REPAIR_CONTENT_MISSING (it's asking for old package versions like 10.0.26100.1591/1742 that aren't in any current ISO, online or local).
The problem is that even a clean install attempted from within the existing Windows installation fails. I tried:
- In-place repair via Setup.exe (Keep personal files) — reached "Installing Windows 11," failed after restart, logs were auto-deleted before I could check.
- Full clean install (Keep nothing) via Setup.exe from inside Windows — got to ~21%, failed again. This time I captured the logs, and they show repeated 0x80070005 (Access Denied) during device inventory/compatibility scans, with a fatal error: failed to mount
C:\$WINDOWS.~BT\Sources\SafeOS\winre.wim.
So there appear to be two separate issues: the component-store corruption itself, and a second problem where Windows Setup can't complete even a clean install when launched from inside this installation.
System Restore isn't an option either — System Protection was disabled and there are no restore points.
Given the SafeOS WIM mount failure, my plan is to boot directly from a USB installer (bypassing the existing Windows environment entirely, rather than running Setup.exe from within it) since that avoids whatever is blocking Setup from inside the current install. Does that sound right to you, or is there something about the 0x80070005 you'd want me to check first before going the USB-boot route?
Thanks again for the help.