Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by kevinh

  1. Yes I'm sorry, I should have read all the other posts. But it wasn't actually a repeat of my earlier post. I'm glad you've found the cause of the problem and look forward to being able to download the 64 bit installer. Thanks for your support Kevin
  2. Hi Pete, Thanks for the reply. The problem is when the installer crashes it doesn't produce a log file, so I can't send you a copy. With previous versions I've been able to run the installer from another drive on my PC (where I keep backups of all installers), or the desktop after a download. I just tried running the installer again and get the same problems. Installer crashes if I run it from a different drive to P3D. Installer crashes if I run it from desktop or downloads folders (and probably from any folder in my User area). Installer works successfully if run from an ordinary folder on C drive (but doesn't produce an install log file there). The install log file is in the P3Dv4 modules folder. The only thing of interest in there is that I can see is it can't find a SimConnect.XML file. The log says "this is okay" but is it normal? Something fails very early in the installer process after it starts looking for the P3D registry entry and the install path. I've attached a screenshot of this. Obviously installing from a standard folder on the same drive is a workaround, but it's odd that all my other FSX and P3D addon installers run from anywhere on my system, and when I initially ran the installer for version 5.102 from my desktop it worked prefectly. Could it be related to running the installer when FSUIPC is already present? Thanks Kevin
  3. Thanks for explaining the version checking requirements of the installer. So it can't be that, I agree. I downloaded the installer afresh and put it in a lower level folder where all my other installers are (on a separate fixed hard drive). I disabled the AV. The installer still crashed when I ran it (as admin). The only thing I hadn't tried was running it from a folder on the same drive as P3D. This time it ran and installed as normal. I've never seen this type of thing before, as I've been routinely running installers from my backup disk with no problems at all. I'm happy to admit I was wrong and you were right, but I'm at a loss to understand why, with nothing obvious having changed, I can now only install FSUIPC from the same disk P3D is on, and not from the desktop at that. Yet I was able to reinstall my PMDG 747 and 777 addons today, running them from the desktop with no issues. Thanks for your help Kevin
  4. My backup disk is a fixed installed drive. Why would the AV software be a problem now when it has never been a problem with FSUIPC installers before? If it was blocking things it would be flagging it up as suspicious activity. Anyway I've tried installing with the AV disabled and it made no difference. I always install software with admin rights and AV software active. I installed the hotfix after installing FSUIPC5.102 in P3D.Now the same installer will not run and the only thing that has changed is the P3D version (because of the hotfix).
  5. The 102 installer is extracted and on my backup drive. I ran it from there and that won't install either. I'm becoming convinced this is related to the hotfix.
  6. I tried the installer with AV disabled. No change. Both FSUIPC and P3D installed by running as admin. Also v5.102 installer worked previously, so why not v5.103?
  7. Yes, true, I didn't extract it this time, but yesterday I did and it still failed. I've just retried with the unzipped installer and here is the event log: Faulting application name: Install FSUIPC5.exe, version:, time stamp: 0x59515139 Faulting module name: Install FSUIPC5.exe, version:, time stamp: 0x59515139 Exception code: 0xc0000005 Fault offset: 0x0000b5c4 Faulting process id: 0x1db4 Faulting application start time: 0x01d2f728409fe23d Faulting application path: C:\Users\Kevin\Desktop\FSUIPC5\Install FSUIPC5.exe Faulting module path: C:\Users\Kevin\Desktop\FSUIPC5\Install FSUIPC5.exe Report Id: 7f5401d2-631b-11e7-9475-d050999d682b
  8. Hi Thomas, Sorry for posting in the wrong forum. My mistake, I should have checked where I was in the forum. When I got the "two versions running" error I had not previously run P3D since starting my PC that day. So it can't have been in already memory. I had deleted the existing FSUIPC v5.102 files in an attempt to get the latest installer to work. I have since restored them to the modules folder and deleted the ini file so it would be renewed. I restarted P3D and FSUIPC5 v5.102 (unlicenced) is running without any obvious problems. If I try and install v5.103 (P3D definitely not running) no new log file is created so I cant upload anything of use. It clearly isn't getting very far. The files for 5.102 remain. I'm running the installer as admin. Kevin Edit, here is what I found in event viewer. Faulting application name: Install FSUIPC5.exe, version:, time stamp: 0x59515139 Faulting module name: Install FSUIPC5.exe, version:, time stamp: 0x59515139 Exception code: 0xc0000005 Fault offset: 0x0000b5c4 Faulting process id: 0x970 Faulting application start time: 0x01d2f7100d93c4ad Faulting application path: C:\Users\Kevin\AppData\Local\Temp\Temp1_FSUIPC5.zip\Install FSUIPC5.exe Faulting module path: C:\Users\Kevin\AppData\Local\Temp\Temp1_FSUIPC5.zip\Install FSUIPC5.exe Report Id: 4c0608d4-6303-11e7-9475-d050999d682b
  9. Moved to Main Forum. Please ask questions always in Main Forum ! I successfully installed FSUIPC5 in the initial release of P3dv4. Subsequently I installed hotfix 1 when it was released. Today P3D reported two copies of FSUIPC were running when I loaded it. So I decided to rerun the FSUIPC installer I used originally (v5.102), to try and repair the installation. The installer window reported that it was looking for the P3D registry entry and setup path. Then it crashed, reporting it had to close. I found an updated installer on the website but this also crashed at the same point. Regedit shows the P3Dv4 entry is there and the setup path is correct. Could the problem be due to hotfix 1? Kevin
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.