Ganradlogin

FIXED !! A suggestion on Steam worked: Deleted Logbook.BIN in Documents>Flight Simulator X Files

First, the FSUIPC4.ini has now turned up. I'm positive it wasn't in the Modules folder when I looked and a full search of the C drive didn't find it. It now does. I've tried John's advice to disable weather. No fix. I've now renamed FSUIPC4.ini to $FSUIPC4.ini. Again no fix. Is there a way of enabling controllers again without opening FSX? PS I now see that a new FSUIPC4.ini file is created presumably when attempting to open FSX

Prior to your reply I removed all traces of FSUIPC4. Game not fixed. Within Steam I verified integrity of game files which were OK. Reinstalled FSX_SE. Still not fixed. Cleaned registry. Still not fixed so gave up, waiting your reply. Re-ran FSUIPC4 installer (with admin rights). Appeared to run OK, but after searching for FSUIPC4.ini on C drive, it COULD NOT BE FOUND. Tried launching FSX. OK'ed security warning about FSUIPC4.dll. Back to stuck splash screen and 55% CPU usage. Note I've used FSX for over 250 hrs with no problems. The first install of FSUIPC4 without validation worked, and FSUIPC was visible in the FSX pull-down menu. It was only after the second install of FSUIPC4 with validation that the problem occurred. PS. During the first working install I went to FSX Settings-Controls and unchecked 'Enable Controller(s)'. could that have caused a problem? DLL.XML

FSX-SE was running fine (Windows 10). Just installed FSUIPC4. Ran first without validation. All OK. Ran install again to validate. No errors. Now FSX won't launch beyond the splash screen. FSX is running 55% CPU! Rebooting makes no difference. Log files attached. FSUIPC4_prev.log FSUIPC4.log FSUIPC4 Install.log