Components of new GUI of Explorer.exe in Windows 11

ASome tweaks could be repeated but only by applying it this way everything is as I like it, but with this build I am having the problem mentioned before, By the way, is there any way to have ntlite process all these xml in a single session in a specific order?
 
There are no options (yet) in NTLite to have the W10 explorer with W11 (legacy explorer)
Either it is a removed component, or the problem is not directly related to NTLite (maybe a registry key added / removed, etc...)

Have you tried installing Windows with your ISO and without using NTLite (without tweaks) and see if the problem persists ?
 
tistou77 said:
There are no options (yet) in NTLite to have the W10 explorer with W11 (legacy explorer)
Either it is a removed component, or the problem is not directly related to NTLite (maybe a registry key added / removed, etc...)

Have you tried installing Windows with your ISO and without using NTLite (without tweaks) and see if the problem persists ?
Click to expand...
I tried 2 times, both times the problem only occurred when applying those presets, I think I also have the option to go 1x1 and or peobando, remember that this only happened to me In the latest compilation of 24h2.
 
You can already try 1 preset by 1 preset and you will see, but since you do not delete components, it is weird
Using this "explorer", I always had it

Otherwise nuhi will maybe have an idea
 
tistou77 said:
Ya puedes ir probando 1 preset por 1 preset y veras, pero como no borras componentes, queda raro
Usando este "explorador", siempre lo tuve

De lo contrario, nuhi tal vez tenga una idea.
Click to expand...
YOn the ntlite discord there is another user who has the same problem
 
He posted on this topic too (if it's the same), if you remove no components and just tweaks, nuhi should be able to help you
I didn't see an option for this explorer in NTLite
 
tistou77 said:
También publiqué sobre este tema (si es lo mismo), si no elimina ningún componente y solo realiza ajustes, ahora debería poder ayudarte.
No vi una opción para este explorador en NTLite
Click to expand...
AI just installed windows clean and used ntlite applying the same settings, the explorer did not change, It only happens when you add settings to an iso for later installation.
 
Yes, I am with 26100.1742
I don't use the "Insider channel" on this PC (26120.xxxx, eg)
 
tistou77 said:
Sí, estoy con 26100.1742
No uso el "canal Insider" en esta PC (26120.xxxx, por ejemplo)
Click to expand...
Hola de nuevo, te facilitaré el trabajo, esto solo desactiva todo lo relacionado a la sección de canales del visor de eventos, desactiva el inicio rápido,
deshabilitar todo en el control de errores, deshabilitar todo en la sección Seguimiento del registrador automático,
Desactiva las tareas. UScheduler

y deshabilitar 68 funciones, simplificar las cosas y crear un solo archivo xml, eliminar varias configuraciones, instalar el iso y efectivamente el explorador de archivos se muestra en el estilo de Windows 10, lo cual me gustaría evitar,
Agregar al archivo xml.

Mister nuhi Maybe I could take a look?

UPDATE: The problem occurs when removing "RECALL" from the features section, I applied all my settings excluding this and the browser appears normal,Once inside Windows I can remove the recall with ntlite. Microsoft and their crap to force users not to remove the recallI guess it records something and that's why Microsoft made it this way to prevent it from being deleted before you log in for the first time
 

Attachments

Last edited:
Indeed, disabling the Recall feature in the ISO / Image "activates" the old explorer (W10)
Feature to disabled only in Live for those who want to keep W11 explorer

On the other hand, disabling the Copilot+Recall (Settings-Privacy) option does not affect the explorer
 
I didn't see anyone try to confirm if this problem is specific to NTLite, or 26100.1742 in general.

From a clean install.wim, I manually DISM /Disable-Feature /FeatureName:"Recall" before creating a new ISO. NTLite was only used for the ISO creation process. After the clean install, Explorer is borked.

So it's not an NTLite problem.

View attachment 12834
 
YGood to know
garlin said:
I didn't see anyone try to confirm if this problem is specific to NTLite, or 26100.1742 in general.

From a clean install.wim, I manually DISM /Disable-Feature /FeatureName:"Recall" before creating a new ISO. NTLite was only used for the ISO creation process. After the clean install, Explorer is borked.

So it's not an NTLite problem.

View attachment 12834
Click to expand...
I confirm that the problem does occur in that compilation, in the previous one, I could disable the recall feature without problems.
 
Microsoft locked it, it was unintentional to allow disabling - like they did for Edge at first.
Example of such news:
campustechnology.com

Microsoft Will Disable Default 'Recall' Feature Due to Security Concerns -- Campus Technology

Microsoft's controversial new Recall feature (currently in preview) will not be activated by default for Windows users, the company announced.
campustechnology.com campustechnology.com

You should be able to remove it in NTLite Components, let me know if you see other methods that would like to see implemented.
 
Just to follow up, if you re-enable Recall on the "broken" PC everything returns to normal after the first reboot.
Code: 
dism /online /enable-feature /featurename:recall

From checking with ViveTool, moving Recall between Enabled and Disabled states only changes two Feature ID's (48455785, 44063183). But manually changing them with ViveTool isn't enough to restore Explorer to a W11 appearance.

48455785 enables another set of apps under the Start Menu's Recommended section. It's probably unrelated to the glitch.

This definitely points to a Servicing stack bug on clean install, since the broken ribbon isn't a permanent change.
 
Perfect information. Could you help to fix this in future versions perhaps? I personally tried to reactivate the recall feature when I had the problem, I did it through ntlite, I restarted and file explorer was the same
 
You must log in or register to reply here.
Back
Top