dpc and Mig-29,Well I spent a couple hours looking at both of you log files. I even uninstalled my FSX demo and reinstalled with the log file option turned on for comparison. Unfortunately, I don't think I can be of much help. There's no obvious, at least to me anyway, error or problem that I can pin point. You both receive a return value of 2 from the InstallFinialize operation, meaning failure I presume, where as I get a value of 1. From that point on both of your logs contain info about the removal of the FSX Demo, due to the failure.dpc,I didn't find any errors in your install log that would explain the problem but I am curious about one item I noticed. Your computer name is ****-VIRTUAL. The "VIRTUAL" part would seem to suggest that your trying to install this in a Virtual PC environment. If that's the case I wouldn't be surprised if I doesn't install or doesn't work even after it installs. If that's not the case I have no idea why it doesn't work for you. Mig-29,I did find one error in you install log that, MAY, be the culprit but I can't say for sure. The error is: "DwSens: Failed CoCreateInstance on EventSystem. hr: -2147220986"Unfortunately, I have no idea of what DwSens is and Google didn't know either. If I had to guess I'd say it has something to do with Dr. Watson (an application installed in Win XP) but that's just a guess and I can't tell you where to begin to try to fix it.Sorry I wasn't able to be of much help guys, but I did the best I could for not being an ACES team member. If your lucky Mike (tdragger) will find this thread and, if he has time, he can help you out. In a last ditch effort to help you get this Demo working here's what I would do:1)You now have the decompressed FSX Demo installer files. I would try to run the prerequisites individually then the FSX installer and see what happens. Try the following order:a) WindowsInstaller-KB893803-x86.exe:( vcredist_x86.exec) msxml.msid) DirectX9dxsetup.exee) setup.exe2)Do a complete format and reinstall of Windows XP and SP2Good luck guys, I hope you get a chance to run the FSX Demo. Its going to be one amazing release especially when the DX10 update is available. You just not believe what your seeing! :-)-Thad

Thad,Again, I appreciate you looking over the log. My machine name is just the name. I'm not running a virtual machine. This is frustrating. I hope that I don't see this issue on the release. There is no way I'm going to format and re-install windows to run a demo. If I were the only one having this problem, I might think about it. But there are others having exactly the same problem so I think I'll hold off on such a drastic step.Dave________________________________________AMD Athlon 64 4000+ San Diego @ 2.6MhzNForce4-A939 mobo 1G FSB2x1G Cosair XMS Ram on dual channelsSapphire Radeon X1900XT Video Card @ XTX23" Apple Cinema Display @ 1920X1200Soundblaster Live24Saitek Cyborg EVO TrackIR4

Okay guys, after a good nights sleep I just couldn't help but take another look at your logs. With my fresh perspective I noticed something that seems to suggest a problem in both of your logs. First, a question; Are you both running Windows XP Home Edition? If so I do believe, as you were thinking, that this has something to do with SP2 and security issue durring install. I need to run a few errands this afternoon but in the meantime I'd like you both to download and install the Windows 2003 Resource Kit Tools from:http://www.microsoft.com/downloads/details...&displaylang=enThere's a tool in that package we may be able to use to evaluate and fix this problem. After you install the resource kit you need to open a command prompt window. Click START then Run. In the open box type "cmd". Now enter the following EXACT command:showpriv.exe SeImpersonatePrivilegePlease copy that info and include it in your response.I'm guessing that you won't see your User Account in that list. So try to add it with the following EXACT command. (Be sure to replace USERNAME with your user account)Ntrights.exe -u USERNAME +r SeImpersonatePrivilegeAgain, run the following command and make sure your user acount is in that list.showpriv.exe SeImpersonatePrivilegeAfter that try to run the FSX Demo (with logging again please) and see if it works this time.I'll check on this thread later this afternoon to see how you're doing or if you run into problems or have additional questions.Hope this works for ya. Keep me posted...-Thad

I'm using XP Pro. I still tried what you suggested. It showed my account with SeImpersonatePrivilege user right. Still no install. I've sent the log file again.Dave

Hmm, Ok, Yes try it, it could be a permission problem on XP Pro as well.-Thad

I found a solution..at least it allows me to finally get the demo installed ! Did a google search for installshieldwizard and found a link that described the error I was seeing "Prouduct installation fails with the message "Installshield wizard was interrupted... system was not modified." Here's the link-- http://www.winway.com/Main3/support/Resume...nterrupted.aspxI followed the instructions and Ta Da !! (oh, and I did the windows update also). Hope this helps you guys. I know how frustrated you are/were as I was also !!

dpc,I took a look at your 2nd log file and the same issue is still present. Here's the part of the log file that shows the problem:MSI (s) (6C:74) [17:12:24:625]: Executing op: ActionStart(Name=OnMoved,,)MSI © (F0:A4) [17:12:24:625]: Entering MsiProvideComponentFromDescriptor. Descriptor: ^$~S7yG4-?-g`k@g_,R=core>M5KDYSUnf(HA*L[xeX)y, PathBuf: 3B7F4F4, pcchPathBuf: 3B7F4F0, pcchArgsOffset: 3B7F450MSI © (F0:A4) [17:12:24:625]: MsiProvideComponentFromDescriptor called for component {997FA962-E067-11D1-9396-00A0C90F27F9}: returning harcoded oleaut32.dll valueMSI © (F0:A4) [17:12:24:625]: MsiProvideComponentFromDescriptor is returning: 0I'm fairly ceritan we're on the right path. The most likely cause for this issue is a security problem that occurs during the install on a Win XP SP2 machine. From the research I've done the steps you took should have resolved security issue. Can you verify some info using the following steps:Program:START -> Control Panel -> Administrative Tools -> Local Security PolicyTree:Local Policies -> User Rights AssignmentPolicy:Impersonate a client after authenticationThat policy should contain at least: Administrators and SERVICES groups.It should also now include your user account since you added it via the steps taken earlier. If any of these groups or your're user account isn't present here, add them.Questions:Did you reboot after making the suggested changes?You're user account is an Admin privelages account, correct?Are you on a DOMAIN?Let me know what you find.UPDATE: See lasso's link in his post. It also describes the steps I'm talking about. Good link lasso :-)-Thad

>Okay guys, after a good nights sleep I just couldn't help but>take another look at your logs. With my fresh perspective I>noticed something that seems to suggest a problem in both of>your logs. First, a question; Are you both running Windows XP>Home Edition? If so I do believe, as you were thinking, that>this has something to do with SP2 and security issue durring>install. I need to run a few errands this afternoon but in the>meantime I'd like you both to download and install the Windows>2003 Resource Kit Tools from:>>http://www.microsoft.com/downloads/details...&displaylang=en>>There's a tool in that package we may be able to use to>evaluate and fix this problem. After you install the resource>kit you need to open a command prompt window. Click START then>Run. In the open box type "cmd". Now enter the following EXACT>command:>>showpriv.exe SeImpersonatePrivilege>>Please copy that info and include it in your response.>>I'm guessing that you won't see your User Account in that>list. So try to add it with the following EXACT command. (Be>sure to replace USERNAME with your user account)>>Ntrights.exe -u USERNAME +r SeImpersonatePrivilege>>Again, run the following command and make sure your user>acount is in that list.>>showpriv.exe SeImpersonatePrivilege>>After that try to run the FSX Demo (with logging again please)>and see if it works this time.>>I'll check on this thread later this afternoon to see how>you're doing or if you run into problems or have additional>questions.>>Hope this works for ya. Keep me posted...>>-ThadThad,Thanks very much. :-jumpy In your last thread you mentioned rebooting after these instructions. I had not. Before starting on the next batch of instructions, I decided to reboot and that took care of the issue. So the instructions in the post that I am replying to were the ones that corrected the issue for me. Hopefully others as well. Thanks very much. Your efforts are greatly appreciated. Now, off to try this demo out!:-beerchug Dave________________________________________AMD Athlon 64 4000+ San Diego @ 2.6MhzNForce4-A939 mobo 1G FSB2x1G Cosair XMS Ram on dual channelsSapphire Radeon X1900XT Video Card @ XTX23" Apple Cinema Display @ 1920X1200Soundblaster Live24Saitek Cyborg EVO TrackIR4

AWSOME!!!!!!!!You're welcome, dpc. I'm glad I was able to help after all.I hope you enjoy the demo as much as I have. Maybe we'll fly online together sometime after the offical release. :-)-Thad

Hi Thad,first of all a very BIG (!!!) "Thank You" for your help.I have not tried your last suggestions because I am on a different timezone here in Germany, but I will give it a try the next morning (of cause I will let you know...)Cheers :-),Michael

Hi Thad,YOU DID IT !!! :-jumpy :-yellow1 :-jumpyagain a big Thank You for helping us :-). I was able to install the demo on my XP-Home system with the Windows 2003 Resource Kit Tools you suggested. I followed all the steps you mentioned above and the install problems were gone...Thanks again and Greetings from Germany :-waveMichael

That's good news!Your welcome, Michael, I'm glad the fix worked for you too.Hopefully our time and effort will benifit others who come across this issue.-ThadP.S. If the mods are watching and want to make a sticky topic, something like "FSX Install Issues and Solutions", I'll write an article detailing the problem, cause and solution for this problem that they can put in that thread.