Hey Fellow simmers,I hope I can get some help from this post!EDIT: I'm SORRY for the wall of text ...A little backstory:About two weeks ago, I got invited to a beta based on a plane I fly, so I got back into simming after a 2 year break due to real world flying. So, I set out and bought FSX Standard and a joystick. I installed FSX from the disks with no problems whatsoever. I was able to start it, and enter my code, and fly. Then I installed SP1, SP2, all of the C++ files, and the .Net 4.0 framework. I installed and tested the beta plane I was working on, and then installed my copies of CS 757/767X and ran multiple 5-6 hr flights. Then, realizing I had missed out on the PMDG MD-11, I picked it up and started flying that too! After several test flights and patterns and the like, I started an "around the world tour" consisting of PHNL-KLAX-PHNL-YSSY-VHHH-UUDD. I planned to continue to EDDF, and then KJFK or something, and then PANC, and finally back to my home base PHNL. After a successful VHHH-UUDD flight, I hit "end flight". On the main menu I went to look at "logbook" to make sure it entered. FSX froze (mind you, the first time in 50-60 hrs of activity). I didn't think much of it, and based on my fondness of the PMDG MD-11, decided to pick up the J41. I then installed it and wanted to start flying. Starting FSX, the Win 7 Ult blue spinning wheel came up and never stopped spinning. After multiple restarts and attempts, FSX never started.So, I attempted the following.I repaired FSX via the install diskI re-ran SP1 and SP2 (which only asks to uninstall)I repaired/re-ran all C++ and .Net framework filesAfter a restart, I got nothing. In fact, FSX began giving me a fatal error, which turned out to be simprop.dll. SO...I decided to uninstall everything.I uninstalled FSX, deleted everything in the root folder and restarted. I then in this order installed:FSX via the install discs - restartFSX SP1 via the exe - restartFSX SP2 via the msi (only had option to uninstall. I uninstalled) - restart -->when I rebooted Win 7 Ult said "you're copy of Windows 7 is not genuine, please get genuine". All this was because of uninstalling SP2.FSX SP2 with success -restartAll C++ and .Net 4.0 files restartThen, going to start FSX and enter my code it kept saying "cannot connect to authorization website". I tried to do by phone and it said "can not find the install ID" or something like that.Now I'm trying this:uninstalled SP2uninstalled FSX via discI tried to look in the Registry to see if I could find FSX files. After no joy, I started a reinstall.I'm going to:Install FSX via disc and then start and try to register - restartInstall FSX SP1, try and start and use - restartInstall FSX SP2, try to use - restartThen install all of the C++ and .Net files. If successful, then I'll install the MD11, J41, and other files.Any thoughts, comments, suggestions?! They will be much appreciated!KE

Originally, I can tell you that your logbook (logbook.bin file) wass corrupt. Deleting the file, and then restarting FSX would have fixed the issue. FSX will build a new one on restart. On Win7 the file is locate in X:\Users\USERNAME\Documents\Flight Simulator X Files. You can also download a utility from the AVSIM file library called fsxlogrecovery11.zip that can in most instances recover a corrupt logbbook. I would also recommend searching the library for logbookedit-0411062225.zip which will allow you to make edits to the logbook if need be. NEVER use the FSX facilities to correct logbook entries. There is a bug with it and if you edit anything other than the last flight it WILL corrupt your logbook.Regards,Bob

Thanks for the info Bob! I ended up installing Windows, and then FSX and it worked very smooth like! This is great information though!

Also remember there's a Windows 7 - FSX flaw. Most people (not all, including meself not having the problem) have a fatal error if they enter the FSX menus too much (such as right clicking, using the top menu containing Flights, World, etc.) Solution for this is the Vista 32bit UIAutomationCore.dll, Google it and you'll come up with your solution to that little bug in Windows 7 :D