FSX-SE Quality Wings Dispatcher Error on Startup

[Niku 0]

Just got my hands on the Quality Wings 787's. Unfortunately, I have been unable to install liveries for these aircraft due to the Dispatcher error. Whenever I launch QW Dispatcher, I get the same error every time (Microsoft FSX or P3D path could not be found). I have seen many fixes for this problem for P3D, but not FSX-SE as of yet. I know that it's a registry issue, so any help would be much appreciated.

Thanks!

[charliearon 3,017]

Try a Google search for Quality Wings 787 Hot Fixes.  I found it but it seems to be on a Facebook site.  One of the fixes is for FSX-SE and for the Dispatcher error.

[Niku 0]

The problem is still persisting after downloading both hotfixes. Most of the solutions for the P3D version of this was to do with changing the registry. Any ideas? 

[Niku 0]

Ok, so from my very limited knowledge of the registry, it seems to me like the dispatcher is looking for fsx in LOCAL_MACHINE, when for every other add on I have it looks in CURRENT_USER. If I'm correct here (which I'm guessing I'm not), how can I make dispatcher look for fsx at that location? Any further help would be greatly appreciated.

[Jim Young 2,356]

I found the following on the Quality Wings website - http://qwsim.flight1.net/forums/qw146-dispatcher-path_topic6481.html

[Niku 0]

This is for P3D, I've tried this earlier and it doesn't work. I'm at a loss as to how to fix this.

[Jim Young 2,356]

1 hour ago, Niku said:

This is for P3D

P3D is based from FSX.  In any case, when you own a product that requires you to go into the registry to fix it so it will run properly, and you have all of the updates/hotfixes installed, then it tells me the product is not compatible.  Messing with EULA's is not tolerated here.  If Quality Wings cannot fix it then you are evidently messing with their EULA.