It seems that with every release of Windows 10, Microsoft throws us a curve ball that we must “figure out.” What mysterious “change” from the previous version is now causing our typical image customization to fail?
This time, it’s customizing the default application associations. It appears that Microsoft decided, in this version, to flag the file C:\Windows\System32\OEMDefaultAssociations.xml as “read only,” causing my DISM command to fail (Error 5 – access denied).
Luckily, it’s a simple, straightforward fix — disable the R/O flag and retry the DISM command. Not hard but I thought I’d share this so that no one else goes diving too deep into the abyss trying to figure out something relatively easy…