We have a legacy app using DomDocument30 data type. It's a long way to update it to DomDocument60, so I don't want to discuss that over here.

What I do want to discuss is a strange phenomenon I have been observing on Windows 10.

Earlier we used to develop the app inside a VM having XP and everything was smooth. We decided to ditch that and move to Win 10 as the development environment, and once we made the switch, this problem has been nagging us all the time.

When I open the project in the IDE, it automatically sets a reference to the C:\Windows\SysWOW64\MSXML6.dll
If I try to compile the project right away, I get compilation errors for the DomDocument30 type used in the code.
OK, so maybe the latest MSXML6.dll does not use these types (it uses DomDocument60)

I have a copy of the MSXML6.dll saved from a production backup. I add a reference to this file. Thish being an older version, has the DomDocument30 type. Everything works fine now.

After finishing work, when I stop VB6, re-start VB6 and open the project again, it again shows reference to C:\Windows\SysWOW64\MSXML6.dll, instead of the reference I had set in its earlier run.

WHat gives?