Simply because it is a system file does not mean that it does not depend upon others for its operation, or that MS will not change it and/or others somehow in a future configuration.
I had a similar problem some years ago when a few particular pieces of software would no longer run when there was no problem previously. Turned out that MS had updated a particular dll file for "greater efficiency", however the update broke other (non-MS) programs that needed a particular function in that file to operate. Not surprised that something similar appears to have occurred again.
Got it. That explanation makes sense.