gordiani Posted October 11, 2017 Share Posted October 11, 2017 Periodically I reinstall my OS. I like clean restarts. My HP allows me, with a few clics, to reinstall Windows 10 from scrap. Recently, unfortunately, I am unable to load FSX (original cd's). I even tried with another copy. Same result. Never had this problem in the past. Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. ...and... Error: - 1603 Fatal error during installation. Consult Windows Installer Help (Msi.chm) or MSDN for more information. Any suggestions? Link to comment Share on other sites More sharing options...
il88pp Posted October 12, 2017 Share Posted October 12, 2017 Use resetsldl.exe explained here for example: https://www.flightsim.com/vbfs/showthread.php?306205-FSX-installation-problem [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
gordiani Posted October 12, 2017 Author Share Posted October 12, 2017 Thank you for you suggestion, but my problem is different than the one you mentioned. I'm talking about a "clean" start that will not load FSX anymore (with original cd's and another copy lent to me). Link to comment Share on other sites More sharing options...
il88pp Posted October 12, 2017 Share Posted October 12, 2017 Same problem. Remove registry entry's wit resetsldl.exe then reinstall. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
gordiani Posted October 12, 2017 Author Share Posted October 12, 2017 Same problem. Remove registry entry's wit resetsldl.exe then reinstall. I tried, but no change. We are talking about a clean start from scrap and original game cd's. Link to comment Share on other sites More sharing options...
okdaley Posted October 12, 2017 Share Posted October 12, 2017 Error 1722 in Google Search results: Check if the Installer Service is running. Click Start, Click Run and type “Services.msc†(without quotes) and press Enter . . etc. Link to comment Share on other sites More sharing options...
gordiani Posted October 12, 2017 Author Share Posted October 12, 2017 Error 1722 in Google Search results: Check if the Installer Service is running. Click Start, Click Run and type “Services.msc†(without quotes) and press Enter . . etc. I probably sound boring because I keep repeating the same things. We are talking about a procedure that I have already done "successfully" in the past. Reinstalling from scrap Windows 10 using the HP F11 procedure. And then reinstalling FSX. It has always worked up until this time. It sounds to me as if the Windows original installer is corrupted. Link to comment Share on other sites More sharing options...
mrzippy Posted October 12, 2017 Share Posted October 12, 2017 Reinstalling from scrap I hope you mean installing from scratch! Scrap=junk Are your discs in good shape with no marks, fingerprints, or other damage? Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
gordiani Posted October 12, 2017 Author Share Posted October 12, 2017 I hope you mean installing from scratch! Scrap=junk Are your discs in good shape with no marks, fingerprints, or other damage? Sorry, from scratch... I had that same doubt, so I got a hand on two other copies of FSX. Same response... Link to comment Share on other sites More sharing options...
napamule2 Posted October 12, 2017 Share Posted October 12, 2017 When you have FSX installed and re-install the OS (Win 10 in this case) the registry will not have the FSX entries. When you install FSX the OS will write those entries. Best to un-install FSX. Use the above 'reset' tool. Then re-install FSX. Otherwise you will have a mess (if you don't already). FSX writes to C drive even if you install FSX to D drive. When you re-install the OS those files will no longer be there. Garbage in-Garbage out. Do it right. Chuck B Napamule i7 2600K @ 3.4 Ghz (Turbo-Boost to 3.877 Ghz), Asus P8H67 Pro, Super Talent 8 Gb DDR3/1333 Dual Channel, XFX Radeon R7-360B 2Gb DDR5, Corsair 650 W PSU, Dell 23 in (2048x1152), Windows7 Pro 64 bit, MS Sidewinder Precision 2 Joy, Logitech K-360 wireless KB & Mouse, Targus PAUK10U USB Keypad for Throttle (F1 to F4)/Spoiler/Tailhook/Wing Fold/Pitch Trim/Parking Brake/Snap to 2D Panel/View Change. Installed on 250 Gb (D:). FS9 and FSX Acceleration (locked at 30 FPS). Link to comment Share on other sites More sharing options...
gordiani Posted October 12, 2017 Author Share Posted October 12, 2017 When you have FSX installed and re-install the OS (Win 10 in this case) the registry will not have the FSX entries. When you install FSX the OS will write those entries. Best to un-install FSX. Use the above 'reset' tool. Then re-install FSX. Otherwise you will have a mess (if you don't already). FSX writes to C drive even if you install FSX to D drive. When you re-install the OS those files will no longer be there. Garbage in-Garbage out. Do it right. Chuck B Napamule Foregive me Chuck, if I'm not very clear when I try to describe the situation. When I start from scratch, the C drive of mu portable PC gets erased completely. No files remain, not even FSX. As I said, I've done this before. So when I go tio install FSX it is as if it were installed for the first time ever... There is nothing to delete anymore, no hidden files or whatever... Link to comment Share on other sites More sharing options...
jorgen.s.andersen Posted October 12, 2017 Share Posted October 12, 2017 Grasping for a straw, but have you tried formatting this drive before installing the OS? Jorgen Link to comment Share on other sites More sharing options...
il88pp Posted October 12, 2017 Share Posted October 12, 2017 Cleared system, fine, irrelevant. you then tried to install fsx, installer stalled, correct? you cancelled the installer, correct? you then tried running it again, correct? When yo do that, the installer already writes in the registry entries the first time, before the installer stalled. So the second time, install does not work. As the registry entries are there already. You then get 1722 and 1603 Microsoft had a fix for that, kb928080. Removes the registry entries. Microsoft no longer offers that fix file. But it is still available on FlyAwaySimulation. As resetsldl.exe. You need to run that exactly following the included instructions. ...Exactly! (Including using an "Administrator Command Prompt".) There's a bit more to it then simply running resetsldl.exe and sitting back. That removes the registry entries, so you can try again. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
il88pp Posted October 12, 2017 Share Posted October 12, 2017 To stop the installer from stalling again, uninstall your CD/DVD burner program. Or uncheck it's applications in the list of programs that start up automatically with your pc and reboot. Then re-enable it after everything (including acceleration / SP2) is installed. [sIGPIC][/sIGPIC] Link to comment Share on other sites More sharing options...
longbreak754 Posted October 12, 2017 Share Posted October 12, 2017 Two things to try....... Option 1 - Try unregistering/re-registering Windows Installer as follows...... Open the Run command and in the 'Open' box type msiexec /unreg (note the space between msiexec and /) and then click OK. Once it has run open a new Run command and type msiexec/regserver (again, note the space between msiexec and /). Option 2 - Run the System File Check (SFC) utility. SFC can be used to scan the integrity of all protected operating system files and replaces incorrect, corrupted, changed, or damaged versions with the correct versions where possible. To run SFC open Run command and type CMD and then click OK. The resulting window should show an entry similair to this - C:\Users\youracctname> Type cd\ and hit enter - this will take you back to the C:\ prompt To start SFC type one of the command lines listed below and hit enter If you just want to verify only type sfc /verifyonly (note the space between sfc and "/") - using this option no changes will be made if errors are found and when it has finished it will display a list of any errors found. If you want to find and repair errors type sfc /scannow (again note the space between sfc and /) - using this option the program will automatically attempt to repair any errors found. At the end of the process one of the following messages will be displayed: Windows Resource Protection did not find any integrity violations. Windows Resource Protection found corrupt files and repaired them. Windows Resource Protection found corrupt files but was unable to fix some (or all) of them. Note: The process can take a long while to run and may seem to have stalled - it hasn't just wait until you get the one of the messages stated above. If is also worth noting that you may have to run the utility several times to fix all the problems. If the first run found multiple problems and states that it was unable to fix some of them, rerun SFC again. This is because one or more of the un-repaired problem file(s) probably relies on one of the now fixed files to be running correctly to run itself. Regards Brian Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.