r/windowsinsiders • u/Davidthejuicy • 11h ago
Meta Happy Anniversary, Windows Insider! Huge shoutout to Microsoft and the team!
To preface my little story, I've been in the Windows Insider Program since day one. I am very aware of what that comes with, sometimes even painfully. I am not complaining, calling out the WIP, or blaming anyone for me having tons of issues.
I've embraced the masochism 🤣
I'm always on the bleeding edge, Canary, now Experimental, and ALWAYS on my daily driver. We don't use VMs over here, son.
We install things and run ChatGPT commands like barbarians over here.
Anyways, Windows Update has been bricked on my computer for about 4–5 months with the DISM / Servicing issue. This is the longest I've EVER gone without being able to fix it.
Normally, I can hack my way through it, or the I/O Gods decide I've become much too bold with my commands and demand a clean install.
Mind you, since 2013 I've been on an Intel i7-3820 on MBR partitions straight up raw dogging the CSM - ALL THE WAY UP UNTIL I got my first M.2 eight months ago.
Like I be out here foo. LMFAOOO.
But this time? Nothing works. No repair source, no SFC brute forcing, literally nothing has worked.
It all started when Microsoft started messing with Memory Integrity and Cross signed certs (I'll make another post on that).
Then it was failed updates, servicing stack errors, missing paths, certificates failing, CBS turning into the literal definition of a red flag.
With no options left and the shop I had my custom built PC naming my user folder "Owner", I had decided -
Either I'm going to test Windows 11 to its absolute limits at the software level, or I'm going to beat it into submission.
Which brings us to my six-month obsession with NTFS 8dot3 filenames.
You know, those old DOS paths like C:\PROGRA~1.
I've disabled 8dot3 globally repeatedly, but I KEEP finding short names. And they KEEP coming back.
How did I notice?
Well, I'm not some genius with elaborate scripts monitoring everything. I barely know what I'm doing half the time - just to be absolutely clear.
I'm just weirdly obsessed with environment variables and use the old 2018 Rapid Environment Editor.
Which JUST got a major update, by the way. Check out RapidEE. (not mine, no affiliation).
Then I started stripping existing short-name aliases.
Program Files. Windows. AppData. ProgramData. User profiles.
And eventually...
THE ENTIRE C: DRIVE.
Because apparently I can't just own a computer and use it normally.
After analyzing 11 logs:
- 398,494 short-name removal operations.
- 8,559,730 files/directories scanned across overlapping passes.
- 5,711 registry-reference hits.
- 873 filesystem errors.
Yes, almost FOUR HUNDRED THOUSAND short-name aliases removed from a live Windows installation. Running processes, open files. I even included aliases that registry entries might still reference.
This is probably the moment where Microsoft technical support hangs up.
I was literally playing Deadlock during this because I wasn't sure when the next time I would be able to play was after this. Pretty dumb by all accounts lmfao 😂😂
Nothing else to do, I ran SFC and the trusty `Get-AppXPackage -allusers" and got my clean install USB out.
BUT THEN WE REBOOTED.
Windows booted normally. Applications opened. No immediately obvious catastrophe. No freezing. Everything worked.
Did I check Event Viewer?
ABSOLUTELY NOT.
WE'RE TAKING THE WIN, BABY.
Now, I'm not saying this fixed Windows Update (it hasn't), or that 8dot3 caused the problem.
But holy moly, I've put Windows through MANY beatings over the past 6 months and it keeps getting back up.
My current machine is a Z890 AORUS Master, Core Ultra 9 285K, RTX 4070, and more development software than any sane person should have installed.
I even installed one of M.2 in the wrong slot and dropped my GPU to x8 PCIe lanes.
All while me and ChatGPT have been going #YOLO in full-access mode for months.
And you know what?
Windows keeps booting, somehow stays stable, and has managed to force push it's way through 3 Windows Updates now.
So in honor of Windows Insider's 12th anniversary, I genuinely want to give the Windows engineering team some serious kudos.
I've been doing this since the Windows 10 Technical Preview days, and I've NEVER seen Windows this resilient.
My old ASUS Rampage IV Extreme would have been on fire by now, I'd have been reinstalling Windows or repairing DISM from another PC.
However, I'm stuck being known as "Owner" until I find a way to burn this build down, up next:
While digging through the Windows SDK, I found a Microsoft batch file called:
register_com_dlls_advanced_winsxs.bat
Supposedly it registers every DLL and com in the system with it's original intentions to fix missing printer files!?!?
Yeah we're gonna see what else that does.
Anyone else got any obscure Windows repair tools, undocumented-looking utilities, or absolute Hail Mary experiments worth investigating?
Because apparently removing 398,494 short names wasn't enough.
Happy Anniversary, Windows Insider.
And I'm sorry for whatever I'm about to do next and the logs that come with it.




