I'm moving my VB6 dev environment from Windows Server 2016 to Windows Server 2022. I've installed and registered all the components our legacy projects use. When one tlb file is referenced VB6 asks to save the vbp file every time I run the project. There is no change to the vbp file. I've unregistered and registered the tlb files multiple time. Anyone have any ideas what I can check?
Compare the project file before/after saving it. VB6 does a lot of "magic" behind the scenes and tries to get the COM stuff "right". My money would be on another COM-compatible TLB is registered (elsewhere) and VB sees that as the "fitting one". I would expect the GUID to change.
Use something like Nirsoft's ActiveXHelper or RegDllView to find possible duplicates and unregister those.