Is there a way to prevent WIndows 10 (pro) from overwriting config.nt every time there is a major update (ie creators update, etc)?

I have a client who has a highly customized config.nt file required to operate a legacy DOS application. Every time there's a major windows update the file gets overwritten and their application stops functioning until I can get back in and restore the file from backup.

It's beyond me why MS would even feel the need to default a config file only used for legacy DOS apps. I don't recall any previous version of windows touching the file... ever.