Import Default File Associations XML

[Zoom7000]

Is it possible to import the default file associations XML file directly into the Windows image using NTLite as per this article:
https://docs.microsoft.com/en-us/wi...rt-or-import-default-application-associations

 

[crypticus]

I'm not sure but i put my "OEMDefaultAssociations.xml" to here "C:\Windows\System32"

Mine sets classic photo viever - bsplayer - adobeacrobat....

I don't think it works perfectly tho

 

[nuhi]

Already replied on email, but didn't know there is a post.
Basically:

It's not yet in the tool, you can load an image in NTLite, then right-click on it from the Source page and choose Explore Mounted Directory.
Close that Explorer popup and go to command line and:
Dism.exe /Image:C:\test\offline /Import-DefaultAppAssociations:F:\AppAssociations.xml

replace bolded with the Mounted Directory.
Once done, go to NTLite Source page and Unload + tick Save changes. Or when using NTLite to do something else go to Apply page and save like that with other changes.

 

[lenkarin]

Already replied on email, but didn't know there is a post.
Basically:

It's not yet in the tool, you can load an image in NTLite, then right-click on it from the Source page and choose Explore Mounted Directory.
Close that Explorer popup and go to command line and:
Dism.exe /Image:C:\test\offline /Import-DefaultAppAssociations:F:\AppAssociations.xml

replace bolded with the Mounted Directory.
Once done, go to NTLite Source page and Unload + tick Save changes. Or when using NTLite to do something else go to Apply page and save like that with other changes.

Just a advice to the user , with all tips provided by nuhi , you can also edit a few files too. But, recommend to you download a reg file from ten forums or ask vg to restore permissions for TrustedInstaller, I don't know if using dism will overwrite the permission needed to replace the files, so keep in mind if change something in Explorer Mount Directory recover to default state so if you decide share with someone will not have anything related to your computer.

 

[lenkarin]

I'm not sure but i put my "OEMDefaultAssociations.xml" to here "C:\Windows\System32"

Mine sets classic photo viever - bsplayer - adobeacrobat....

I don't think it works perfectly tho

I also check the Ghost Spectre and he applies this OEMDefautlAssociations.xml through a folder inside of sources as well, will be something like this
Your ISO Folder\sources\$OEM$\$1\Windows\System32 - In System32 folder, paste the OEMDefautlAssociations.xml (keep mind to test in a virtual machine, to see if everything works).

 

[Kasual]

I also check the Ghost Spectre and he applies this OEMDefautlAssociations.xml through a folder inside of sources as well, will be something like this
Your ISO Folder\sources\$OEM$\$1\Windows\System32 - In System32 folder, paste the OEMDefautlAssociations.xml

I have tested this months ago and it doesn't works this way, Windows setup restores the Ms file association, I guess the DISM integration register/replace the existing ones.

 

[garlin]

This is another Windows myth that no longer works...

DISM-based default file associations are completely useless on most W10 and all W11 releases. User provisioning from UWP (Store) apps destroys anything you do, since it runs last and doesn't care about the system defaults.

Run DISM in Post-Setup, to capture file associations right after install:

Dism.exe /Online /Export-DefaultAppAssociations:"C:\Post-Setup-AppAssociations.xml"

Run DISM after you log on:

Dism.exe /Online /Export-DefaultAppAssociations:"C:\Post-Provisioning-AppAssociations.xml"

Compare them:

10/27/2022  09:29 PM            11,918 Post-Provisioning-AppAssociations.xml
10/27/2022  09:14 PM             2,338 Post-Setup-AppAssociations.xml

Appx packages cannot make profile changes until the first user gets provisioned (logs on).

If you change your file associations, it only applies to your AppDataLocal. None of it gets updated to DISM's copy, because UWP preferences are per-user and not global. Remember uninstalling UWP apps for yourself doesn't impact another local user who has the same app installed.

Therefore on any Windows with provisioned UWP apps, the default associations are basically ignored.
I have no idea why MS doesn't clean up their docs, to say "it stopped working in Windows 1607" (or whatever).

 

[chrcol]

Does this apply to LTSC also garlin?

Basically i am looking for easiest way to associate XML by default with notepad instead of abandoned IE.

 

[lenkarin]

Does this apply to LTSC also garlin?

Basically i am looking for easiest way to associate XML by default with notepad instead of abandoned IE.

Hi chrcol Yes this apply to LTSC version too, since the versions of LTSC and Stock Windows receive the same approach for each component except for the different scenarios of each edition of windows. So, the components works the same except for updates LTSC receive only security updates.

 

[garlin]

Run SetUserFTA from Post-Setup (User) to apply a personal file association. You can specify multiple FTA's from a config file.
This tool is required because Windows now protects FTA's from getting hijacked by random malware.

 

[chrcol]

Run SetUserFTA from Post-Setup (User) to apply a personal file association. You can specify multiple FTA's from a config file.
This tool is required because Windows now protects FTA's from getting hijacked by random malware.

Tried it out, very simple and effective tool, also the get syntax is useful as well for knowing what to use.

Also yep realised its protected when I tried to use registry changes viewer to analyse what happens and the reg import failed with a hash as one of the monitored changes. Although I did manage to assign 7zip associations via registry, so seems to be only certain extensions that are protected.

Noticed this after I successfully tested it in elevated command prompt. UAC elevation seems ok though, so I guess he just means dont run outside of being interactively logged in.

IMPORTANT: SetUserFTA must run in the users context – no administrative or system privileges. sometimes the timing can be important aswell – make sure it runs after the profile of the user is loaded.

 

[garlin]

Correct. Timing is everything, if you apply changes too early then Windows can wipe out your edits. W10/11 now overrides many user preferences when provisioning a new account, so you have to move those reg changes to Post-Setup (User).

Post-Setup (User) runs your actions with Admin privileges, but inside your user context.