I understand that there are reasons why you would need to run the IDE from Visual Studio, which is why I didn't ask you why you needed to run the IDE from Visual Studio. I asked if the executables available on SourceForge exhibited the same behavior. There have been over 6000 downloads of the installer for the 6.4.1 IDE and yours is the first report of this behavior. I can't reproduce the behavior you're describing running the IDE from Visual Studio. So the first question to resolve is whether there's something unique about your environment that's causing the issue. If the SourceForge executables exhibit the same behavior with the Fact Browser, that would indicate that the problem resides with IDE code that behaves incorrectly with certain configurations of Windows or versions of the .NET libraries.
If the SourceForge executables don't exhibit the same behavior, then you need to determine if there's something different about your Visual Studio configuration. I'm able to run the IDE VS projects in Visual Studio 2022 without having to make changes to them, so that would be the next thing to check. The only way to add user functions to the IDE is by being able to recompile the executable, so if you also want the Fact Browser working you should determine the source of the Fact Browser issue first before attempting to add your user functions. Without a specific set of steps and conditions for reproducing a bug, there's not much that can be done to determine the cause of it.