Failed to open the FL Studio audio engine, Another instance may already be running, if not, try to reset the FL settings .

I am on a budget financially so I had 2K to upgrade my rampage iii 980x pc. I brought a z800 with dual x5690 and PCIe with Samsung 950 pro nvme.
Anyways I have loaded win 10 on latest build , and the first program I loaded was sonar and all cakewalk products. The next program I loaded was fl studio latest build which by default installed to program files x86\Image-line .... anyways I Opened sonar and clicked fl studio rewire and a window popped up = failed to open the FL Studio audio engine, Another instance may already be running, if not, try to reset the FL settings .

To cut the solution short I uninstalled fl studio and re installed it into program files\image-line ....
( NOT program files x86 )
and did the same rewire and it works perfectly .

So besides helping anyone with this issue and there's a lot on google but no answers, my main reason for this thread is the impact of sonar + win 10 ( latest build ) + permissions between
A) program files folder
B) program files x86 folder

What other effects / instruments / daws (rewire) that have been installed to ( Program files x86 -by default )are having these security issues ( SILENTLY) between ( Program Files ) which maybe the cause of some crashes etc etc .

If this permission problem exists because of permissions between these 2 folders , I am now going to install all of my vst effects and instruments SOLEY on ( Program Files) ONLY .
I know that everyone here needs to know this and I am absolutely sure that if this is happening between these 2 programs (DAWS) then it will also have impacts on other programs or effects or anything communicating with sonar between the 2 main folders( x86-x64 program files )keeping in mind that the new latest win 10 build is built around SECURITY /FULL STOP .

Anyways obviously it's something because there's proof of it . So to be sure my fresh install is done to my best ability , I will install all my effects , instruments, daws, anything sonar uses to ( Program Files ) .

Good Luck everyone hope this helps ....

Do want to add - Even though I cut the solution short , when I initially installed fl studio to ( c:program files x86 ) and was troubleshooting this : failed to open the fl studio engine........, one of the steps I tried was ( besides always installing programs as a admin ) I also right clicked the fl studio.exe's and splats.exe to make sure they were aeministrised. This had no impact on win 10 allowing permission to let splat open the fl studio engine.
So I guess there is no higher permission then programs installed to the same program files folders .

I will update when I have installed EVERYTHING to c: program files and have tested splat with my big projects, though I am sure I am onto something that can help splat run a little better .