Windows 11 Search on Taskbar - Exasperated

Good morning, 

 
Like so many other people, I am experiencing the now infamous "Windows 11 Search Box Blank Screen of Ineptitude" 

 
When I first boot my PC and log in, regardless of how long I wait - an initial click of the taskbar Search Box produces a massive square on my screen that is either solid white, or solid dark gray with no content. 

If I leave it "clicked" it slowly produces data on the right side, and about 15 seconds later the search contents become visible. 

So let's break down what I've tried, and what this OS "is" 

1. This is a brand new Windows 11 installation - installed on 4-6-26. The drive was formatted during installation - Nothing was upgraded. 
2. I did not use Rufus to disable anything - it's 100% Microsoft with TPM, etc. 
3. Windows Update - I have Optional Updates turned on. I have Give me updates as soon as they're available turned on. I've run WU until it says there's nothing left to update. 
4. WinGet - I've used WinGet in PowerShell to update everything that it can see via "winget upgrade --all --accept-package-agreements --include-unknown" 
5. I've tried the PowerShell app-x package reset "fix" 
6. I've searched the registry for the alleged keys that could cause this - they do Not exist in any shape, form or fashion 
7. I've rebuilt the search index via the Advanced Search Options 
8. To appease the obnoxious auto-reddit-bot-moderator that will inevitably tell me to open a Microsoft ticket and include my PC config - See below for a system report. I tried opening a ticket with MS, and their glorious support portal INSTANTLY signs me out the instant I sign in and then gives me a screen that ONLY reads, "Something went wrong." (I wish I was joking) 
9. Yes I have scoured this and other forums looking for answers BEFORE making this post. YES I have TRIED the numerous "Hey THIS will fix it" "solutions".  

So here we are. The irony is that I have a disk image of Windows 11 Pro on this same PC that does not have this issue - but it was originally built with an older version of Windows 11 Pro and then subsequently patched and updated as patches became available. It appears that only newer OS builds suffer from this ridiculous issue. 

 
Does anyone have any solid, tested, proven solutions for this? My next step (for debug/testing) will be to make a new, local user and sign into that to see if this problem is user specific or machine specific. I'll update this thread with those findings. 
 
/exasperated 

OS: Windows 11 Pro 25H2 (10.0.26200) - Fully patched/updated as of 4-7-26 including optional updates and Intel drivers