In older COM first approach would have been to refresh registry entries.
.Net does not depend on registy as much as COM, but sometimes/someone still uses it ;-)
VFP-.Net also uses COM bridge in the scenarios I checked (basically with and without Rick's approach...

But: only describing a failure is not a methodical approach.
You should expand the effort to describe YOUR way of install (manifest file, dropping dll in common repository or inside app directory and so on.
Singular effort on your side eliminates much guess work on everybody thinking about YOUR problem....
Another option is to apply each install step via manual entry or compare pre/post situation (or just to run) done once from start,
once from end. VM's with killed app allow diagnosis with repatable error situation ;-)


>Hi!
>
>We've made some Visual .NET ActiveX Classes, for our VFP Program.
>We've made an Installer (nSis) an every thing is fine.
>
>Bud: If Microsoft Updates the .NET Runtime (latest to .NET 4.8) this Update kills every Time something.
>Our Customers get errors like 'OLE-Errorcode 0x80020003: Member not found'
>
>Only reinstall our Setup solves the Problem!
>
>Bud: Every .NET Framework Update Time this error Rises again. This is since 2017.
>Before it worked well.
>
>Any Suggestions? Ideas?