Explorer phenomenon after clean install of NTLited W11 24H2 (26100.1742)

Alt68er

Member
Messages
70
Reaction score
12
Hello,
I downloaded a Windows ISO (build see above) from Deskmodder.de - I'm stating this in the hope that you know this website and consider it as trustfull - treated it with NTLite and did a clean install onto a clean SSD.
1st try with some reg-files including some reg-files
2nd try like 1, and now removing WMP too
3rd like 2, but with 2 protected files
4th like 3, now also removing Defender
5th like 3, now WITHOUT the reg-files

The 5th try I did it offline to be sure that the installation process or afterwards there will not be any download/installation from MS for whatever.

In all of these installations I had one "problem" and up to now I could not find out the reason for it: The Explorer window is different between the account with admin rights and the account without admin rights.

I'll try to attach hereto screenshots of the both Explorer windows as well as the saved session xml of the 5th try and sincerely hope that any one of you experts thereout can give me a hint to solve that problem which not necessarily is caused by NTLite...

1000 thanks in advance four your kind attention.
 

Attachments

You didn't include a copy of your reg files. If I had to guess, you're applying a HKCU change which only gets applied to the primary user on first logon, and not to other users created on the same system. One way to confirm is to make a second admin account, and check if the problem doesn't follow their admin status.
 
Hi Garlin,
I listed my tries only to show what I already did.
But, even in the last (5th) try - which was WITHOUT any reg-files - I'm having this problem. Therefore I did not include a reg-file.
The 5th try is the naked NTLited Windows nothing else, cause it was an offline install without any additional download of drivers of whatever.
 
Hi Garlin,
in the meantime I followed your recommendation (so stupid that I did not think about this before already...) and created a new admin account which showed the same Explorer-window like Explorer-Admin.jpg. Then I created a new normal user account and this one also had the
 
In the meantime I followed your recommendation (stupid that I did not have this idea before...) and
1. created a new admin account, the explorer showed up like in Explorer-Admin.jpg
2. I restored the system, booted and created a new normal user account, explorer showed up like in Explorer-Admin.jpg
3. Again I restored the system, booted and created both kinds of accounts, in both accounts the explorer showed up like in Explorer-Admin.jpg.
 
Today I amended the autounattend.xml used in the NTLited iso from creating 2 users only to 4 users in the sequence admin1, admin2, user1 and user 2.
Installing Windows with these settings both admin accounts got the Explorer with ribbon and the both standard user accounts the Explorer without ribbon...
In both admin accounts Windows failed to create an additional user cause the settings page with the "create new account" button crashed after clicking on this button.

BTW and because I forgot to mention in my earlier posts: the Explorer with ribbon (the "admin-Explorer") lets me change all settings like window size, navigation pane width, column width in the details window, sequence of these columns, but after closing and restarting it does not remember the position and the size of the window.
 
In the meantime I did the following, all trying to find the reason for the bad behavior and a solution:

1. I created an NTLite-Version of 24H2 26100.1. This works great, at least under the aspect of my above problems.

2. I went online and let Windows update itself to 26100.1742. The same bad behavior like described above.

3. I created an NTLite-Version of 24H2 26100.1 and included the Updates 5043080, 5043353, 5042098, and also added Microsoft.VCLibs.140.00.UWBDesktop which all were offered by NTLite, all in my hope that the integration of the updates will not damage my finally installed Windows.
Unfortunately it shows the same bad behavior like above and even one more: After a while also the standard user's Explorer became a ribbon and after closing forgot its size and position, and also the search doesn't work anymore.

So, for the moment I decided not to update to 24H2 cause with such a behavior of the Explorer I cannot work.

In the meantime I really believe that Microsoft has included something wrong into one of their updates...

Nevertheless I really would appreciate if one of you experts could create an NTLite-Version of 26100.1742 with my above saved settings file to check if the bad behavior is reproducable on a different machine...

Many many thanks in advance for your support.
 
Garlin,
thanks a lot for this information and letting me think and hope that these bugs will be solved soon.
In the meantime I'll not continue "working" on/with 24H2.
A nice weekend to all of you!
 
Hi,
in the meantime I found a way to get the explorer running well: after installation with 2 pre-generated users (the first one always got a ribbon-explorer) I simply created some new users via CLI. I don't remember if it was the first or second or third newly created user was having a well sorking explorer. Then I edited this user to make it one with admin-rights and deleted the pre-generated admin-user with the ribbon explorer and also deleted the newly created ones which i didn't need. A bit long-winded but working...
And today I read a short notice about a damaged explorer by removing of MS' Recall. May be there really is a relation.
And also might be that there is a chance for NTLite to break this relation ... ???
 
in the meantime I found a way to get the explorer running well: after installation with 2 pre-generated users (the first one always got a ribbon-explorer) I simply created some new users via CLI. I don't remember if it was the first or second or third newly created user was having a well sorking explorer. Then I edited this user to make it one with admin-rights and deleted the pre-generated admin-user with the ribbon explorer and also deleted the newly created ones which i didn't need. A bit long-winded but working...
And today I read a short notice about a damaged explorer by removing of MS' Recall. May be there really is a relation.
And also might be that there is a chance for NTLite to break this relation ... ???

It's a reported 24H2 install bug. Do this workaround until MS releases a fix:
https://www.ntlite.com/community/in...of-explorer-exe-in-windows-11.4787/post-47167
 
Back
Top