Use caution! This is a 32bit/64bit issue. If you run a 64bit windows, you have two versions of RegEdit.exe available. One for the 32bit registry and one for the 64bit registry. The manipulation within Wow6432Node has a lot of trap doors. Since FSX is 32 bit application, you should use the 32 bit Regedit.exe to search for Microsoft Games. Wow6432Node was introduced for cross compatibility between 64bit applications and 32bit applications. Its usage is not all the time straight forward.
Regards
Mike
+1 here
Using search for Regedit on 64bit OS, it defaults to the 64bit located in c:\windows.
64-bit:
C:\Windows\regedit.exe
32-bit:
C:\Windows\SysWOW64\regedit.exe
The display for 64bit regedit, all 32bit keys/values will be under HKEY_LOCAL_MACHINE\Software\WOW6432Node
Other directories will be 64bit.
WOW64 if I correctly recall stands for Windows32 On Windows64 but dont quote me on this.
Go here for a little more info on it. It applies to Win XP SP3 but is relevant to all 64bit Windows versions.
http://support.microsoft.com/kb/305097
On a minor note, there are actually 3-5 instances of regedit on your machine. You may have more with some program installations, however these would usually be malicious.
Thanks for the clarification. I found what I was looking for under "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator X SDK".
What were you trying to resolve? You indicated the 'missing file' error but never stated what the file was, and why you needed to get into the registry to find it. The gamepack is basically a drag-n-drop set of files into the GMAX directory. If the gmax files counldnt be found, then a file may have been overwritten that shouldnt have been or a file may have changed or become corrupted. At this point reinstalling would have been my recommendation, then reapplying the gamepack. Editing the registry is usually a rarely needed thing by end users. Doing some of the things we developers do, it is needed more often that average users would need. Always use caution in the registry. Make sure to backup the registry before changing or exporting, never load a hive of an actively logged in user, and always properly unload to close them. Using editor to view shouldnt be an issue. Making changes can have adverse consequences and cause additional computer issues if you do not know or understand what you are doing. I have a good knowledge of it and quite a few years experience under my belt but some area's I still take caution.
Example: Moving a program manually sounds as easy as drag and drop. It usually will work with a few changes in the registry regarding this application. It can be complex when other applications point to the modified application or it is using other areas and uses additional entries/keys for cross checking and validations that you may not have been aware of. That's why registry cleaners can cause issues. They dont always know if an application still uses an entry, even when logical.
Im pretty tired and if anything Ive said is wrong, correct it if you know, otherwise I will review this when Ive had some sleep.