As indicated in all my previous emails, there's no reason why any missing libraries wouldn't be updated after running the installer and restarting Windows. Although I don't personally use Windows 11, another FSDT developer does, and we don't have any reports about issues with Windows 11.
Out of thousands of users, I think your and possibly another user have this same problem of the installer saying you used a legacy key and, as I think I already explained to you, the one and only possible reason why the installer code will ever print the "using a legacy key", is if the code you typed didn't start with an A so, perhaps there's something peculiar in your keyboard or regional settings that, when an A is entered, is not really the standard A but, possibly, some alternate character from another alphabet ?