Today we have a solution for this, however making sure that we don’t break anything currently working.
Basically the registry issue comes down to the following;
v1.0, v1.1, and v2.0 framework installation folder registry keys are located under the respective registry platform version. i.e. the locating of the 64 bit installation folder is a 64 bit registry entry, where the 32 bit installation directory is a 32 bit registry key.
v3.0, v3.5, v4.0 framework installation folders have 32 bit installation folder and 64 bit installation folder in both the 32 bit and 64 bit registry keys. This makes things simple enough for these versions. Just read the key and your right.
v4.5, v4.5.1 framework installation folders seem to only exist under a 32 bit registry key. Even though there is a 64 bit installation the registry key only exists under the 3264WoW node, which means you have to read it like your a 32 bit application.
Big disclaimer here is that we are still testing this update. Its needlessly complex to make sure the correct SDK’s are used for each platform, and I haven’t mentioned the handling of the in-place updates. Nevertheless we will get this tested and right. Hope this helps clear things up a little as well.
Also if anyone believes the above is incorrect feel free to say. Haven’t found a definitive source on this as of yet.
This issue has been solved with build:
http://downloads.finalbuilder.com/downloads/finalbuilder/700/FB700_2424.exe