I actually resolved this issue months ago by disabling widgets and the search bar on start bar.
Even internally at Microsoft, they still release products that declare runFullTrust and hence can do anything they want, including activities that are unsupported or that violate Microsoft Store policies. Windows Widgets are included in the Windows Web Experience Pack (package name MicrosoftWindows.Client.WebExperience), and if you look at their package manifest (AppxManifest.xml), you'll see the runFullTrust restricted capability. Windows Search is part of the Windows Feature Experience Pack (package name MicrosoftWindows.Client.CBS), and you'll also see its manifest declare runFullTrust.
Windows Phone and Xbox run the strictest editions of Windows where runFullTrust is unnecessary or not even recognized, and once you've seen Windows at its best, you'll want to hold PC editions of Windows to the same standard. I shared my methodology of using S mode auditing to track down uncertified software in hopes of inspiring others to apply the same techniques and hopefully make their own success stories and share other advancements.
Edit (29 November 2023): Here's a tier list for Windows computing safety, highest first, with parenthetical reasoning on why each tier is weaker than its predecessor:
- Compliance with Microsoft Store policies
- Windows on Xbox (because not all of the Microsoft Store policies can be enforced programmatically by the system)
- Windows on Windows Phone (because it's very easy to enable sideloading to bypass Microsoft Store policies, end-user penalties for bad behavior or misuse are insubstantial, and Microsoft lacks business agreements to compel them to stop user / player cheating via running unapproved code in retail)
[Windows editions in this tier and higher are considered to be trusted platforms --- Windows Defender is absent from these editions.] - Windows in S mode on PC (because runFullTrust is selectively allowed)
- Microsoft Store certification (because exceptions to the Microsoft Store policies can be granted, including publications that are not compatible with S mode)
- Windows switched out of S mode on PC (because runFullTrust is always allowed, as are the equivalent loose .exe and .msi programs, and there is no recourse if a policy breach is made)
[This is arbitrary code execution, so ransomware and malware thrive in this environment, and Developer Mode resides here.]
Most people are still in the lowest tier (which is understandable because it was the only option prior to Windows 8 --- it took several engineering whitepapers from the archived Building Windows 8 blog and a few years into Windows 10 before I was finally convinced to advance). My organization (and their Group Policy refresh) is in the lowest tier, too.
It's been several months and a Windows 11 feature update, so the situation is clearly tricker than it seems --- I suspect it involves one or more third-parties, and Microsoft's social media policy probably prevents their staff from disclosing their identity, so we need to figure out who it is ourselves. Hopefully a security researcher can provide a few hints on what WinDbg breakpoints we should set so we can find the caller and the root cause.