This registry hack is not SOLVING the problem, it is simply MASKING the problem.
As far as I can see, it is merely bypassing the broken Gaming Services while starting MSFS to allow it to run but that now means that any tasks, checks, maintenance, or updates that are usually done by Gaming service will not now be run.
The SOLUTION is to get Gaming Service working and starting with MSFS, as it should - but (again, as far as I can see) nobody has found out how to do that. Obviously, the ultimate responsibility for this lies with Microsoft (and their representation on here) but they seem more interested in shutting down any threads about this, with dismissive posts that imply “this is solved, you just didn’t search hard enough” and then pointing to this thread - whereas, in truth, they are as clueless as the rest of us.