What could be making File Explorer default to legacy (and with bugs) at a clean install of 24H2?


InnerBrat

New member
Local time
2:37 AM
Posts
2
OS
Windows 11 Pro, 64bit, 24H2
Hello,

I "have reasons to suspect" that the problem comes from the fact that I modded the image with NTLite :lmao:
No hiding that. No need to, I had a proud working modding routine, but 24H2 is weird. No modding software really works on it with constant reliability.
So, tbh I'm relatively confident that this issue doesn't come from a mistake of mine, but from a bug in NTLite or let's say an incompatibility with the problematic 24H2.
And yet I cannot exclude human error and I'm here to narrow down as much as possible where I should focus my search.

I will tell you exactly what happens, so maybe you super experts can think about something which would potentially cause that.

I had some problematic back and forth with the ISO from UUP Dump, but the Microsoft one worked well.
Only issue: although I had removed the legacy Explorer, File Explorer completely and passionately defaulted to legacy, with even an old school "Windows Blue" as accent color.
On top of that, in the Home where there should be the Quick Access there's just an empty background.
I tried pinning My PC to Quick Access and it appeared in the left panel together with the other folders which are usually in Quick Access.
But the home is still empty.
And finally, the navigation arrows on the left of the address bar don't work, most of the times.
Although I can navigate with the side buttons of my mouse, which get automatically assigned to back and forward.

I swear, I only removed things which I either knew well, or was reasonably certain about after a thorough search.
Before burning the ISO I saved the "preset" of my mods, and now I applied it on the ISO from Microsoft, and I can't see any mod which would cause this.

Now more context: the CU KB5051987 solved this issue.
So I'm not stressed. I mean, I have a "solution".
But still, I want to understand what's going on, and correct whatever made it happen.
In fact I didn't install any CU in this second attempt, so I can try things out.

Can you think at anything which might cause all that?
Thanks
 
Windows Build/Version
24H2

My Computer

System One

  • OS
    Windows 11 Pro, 64bit, 24H2
So, if you are curious you can have a look at this txt which I took from the preset of my tweaks to this installation.
The preset has lot of things like languages and wifi packages which make it very long, so I have taken only the relevant things like the apps, features and services which I have removed/disabled.

I just can't fathom how any of that could ever possibly make the Explorer default to legacy (even less when I had explicitly marked legacy for removal).
Claude AI says it can be some shell issue.
But how? Bug?
 

Attachments

My Computer

System One

  • OS
    Windows 11 Pro, 64bit, 24H2
Back
Top Bottom