Sign in to follow this  
flor4s

FSX exit after splash screen

Recommended Posts

About month-month and a half ago FSX was working correctly and it was working since a year or two. I decided to install this: https://flyawaysimulation.com/downloads/files/3041/fsx-szd-30-pirat/ yesterday and after doing the install I run the FSX to see splash screen and that's it. Nothing in the process list etc. I uninstalled Pirat and tried again - still same issue. What I verified already:

- no crash in event viewer

- uninstalling pirat didn't help

- removing fsx.cfg, scenery.cfg, dll.xml, exe.xml didn't help

- running as an admin didn't help

- changing logbook.bin file name didn't help

- I don't have any scenery from Dreamteam

- I've run sfc/scannow

- I installed FSX SE from steam - it's also not working (same issues observed)

 

Does any anyone have any ideas? I have no issues with any other game.

Thanks!

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

FSX loads every module in your dll.xml and exe.xml at startup.  So, if your sim crashed after the splash screen, it is likely a module that caused the crash.  Every module you have in the FSX main folder (a module is a file ending with .dll) loads too.  Any file in your main directory that has a .ini extension will also load.  I do not know if this program loaded a module in your main folder but you might take a look for recent installation of modules.  When you install a product and a module is installed in your main FSX directory, it should show in Windows Explorer when that module was installed.  That could give you a clue. 

 

Even though you uninstalled the product, remnants of the prior installation may still exist that is causing the issues.  I do not think it could be the aircraft you installed as aircraft are not loaded at startup other than the default.  After you select the aircraft, then FSX will begin loading the aircraft and the components.  Most add-on programs have a poor uninstall procedure and not all components are uninstalled.  I still doubt the addon from FlyAwaySimulations is the cause of your crashes even though the crashes started right after installation of the add-on. 

 

Still you did remove the fsx and scenery config and let those configs rebuild and moved the dll.xml and exe.xml to a temporary folder and you still had the crashes.  The dll.xml and exe.xml are not installed by default and are not rebuilt.  Only commercial add-on users use the dll.xml and exe.xml.  If you have an outdated fsuipc.dll, that could cause a crash too after the splash screen.  You have done everything possible to investigate and diagnose your crash and FSX still does not work.  If none of the suggestions above work, I would uninstall FSX-SE completely and then reinstall as something got corrupted.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thanks Jim for suggestions. I ended up uninstalling FSX-SE. After that I manually removed the entire folder as there were still some left overs. I did fresh install from steam but still no luck. Any other ideas?

Share this post


Link to post
Share on other sites

Thanks Jim for suggestions. I ended up uninstalling FSX-SE. After that I manually removed the entire folder as there were still some left overs. I did fresh install from steam but still no luck. Any other ideas?

Well, that wasn't one of my suggestions.  FSX (and FSX-SE) leave a lot of files after it is uninstalled, including registry entries.  In other words, it does a lousy job.

 

Do you have User Access Controls disabled?  Did you make sure the folder in which you were installing FSX was temporarily exempt from scanning in any anti-virus or anti-malware program (including MS Defender)?  Did you go to the FSX-SE folder and right click on FSX.exe and select properties and, under the compatibility tab, made sure it shows at the bottom to run the program for ALL users (not just you)?  This is all in the AVSIM CTD Guide (because you did get a CTD as you cannot get past the splash screen).  I also recommend using the uninstall/reinstall guide for FSX as published by PMDG - (link in the AVSIM guide but here it is - http://support.precisionmanuals.com/kb/a87/how-to-uninstall-and-reinstall-fsx.aspx).

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I followed the instruction from PMDG but instead removing the FSX I removed FSX-SE as this is the one I'm trying to run right now. But just to be sure the FSX directories are not the reason why FSX-SE is not starting I changed their names to "FSX.bak". I've run the ccleaner to clean the registry.
I've checked if I have all visual c++ redistributable packages.I've downloaded the FSX-SE again, I've disabled the antivirus and UAC. In the compatibility tab I set to run the app as an administrator for all the users. I've run the simulator but still no luck. I see that the minidumps are being created in the FSX-SE folder but nothing is in the event viewer.

Share this post


Link to post
Share on other sites

What are you seeing in the windows logfiles?

It happened to me yesterday and reported ai.dll, In the end, it turned out that the simmconnect bug for FSUIPC was at fault.

If you get a popup to allow certain modules to be marked as "Trusted", say no, and see if FSX starts up.

Share this post


Link to post
Share on other sites

He said there is nothing in the Event Viewer in his last sentence.  As I stated in the second post, anything in the dll.xml loads at startup but he reinstalled FSX-SE so there was no dll.xml installed.  The way I read it all is that he has a default installation of FSX-SE.  No addons.  No FSUIPC.  No AI as he uninstalled FSX-SE and then reinstalled it after cleaning the registry.  The only thing I can see that would cause the sim to stop at the splash screen is a bad installation of FSX-SE where the anti-virus or anti-malware program decided to quarantine a couple of files that are needed to startup FSX-SE.  I see no solution to the problem.  I recommend OP reinstall Windows and then install FSX-SE.  Something got corrupted in the registry or in his Users files.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Jude - there were no errors in the event viewer. Although when I changed the app to run in windows xp/7/8 compatibility mode I'm getting ntdll.dll crash in the event viewer. I took a look on the CTD guide and ntdll.dll section. My drivers for video card are from november last year so I've played at least dozen times on those drivers. I already did sfc /scannow with no luck, I don't think the issue is with overheating/wrong voltates as the FSX is not starting and I can play plenty of games for few hours with no issues. There's no UIAutomationcore.dll, any sceneries or addon aircraft as it is a fresh install. I haven't done any drivers update for last few months and the FSX was working last month. Since my last FSX play I see that there were some windows updates installed:
KB3189866

KB3176936
Should I update drivers? Are you guys running FSX in compatibility mode with some windows version?

Here is the data from the AppCrashView.
Version=1
EventType=APPCRASH
EventTime=131186774303119769
ReportType=2
Consent=1
UploadTime=131186774304269912
ReportIdentifier=5730bb62-7da0-11e6-85c1-90e6ba25842d
IntegratorReportIdentifier=ff2776ef-61d3-437a-ae71-8785caac9bce
WOW64=1
NsAppName=fsx.exe
AppSessionGuid=000038fc-0001-0054-abc0-c418ad11d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!fsx.exe
TargetAppVer=2015//07//10:10:12:42!2ac31c!fsx.exe
BootId=4294967295
Response.BucketId=e65e1c44fe01af26ae6498e9b7f076f5
Response.BucketTable=1
Response.LegacyBucketId=108367820884
Response.type=4
Sig[0].Name=Nazwa aplikacji
Sig[0].Value=fsx.exe
Sig[1].Name=Wersja aplikacji
Sig[1].Value=10.0.62615.0
Sig[2].Name=Sygnatura czasowa aplikacji
Sig[2].Value=559f9a9a
Sig[3].Name=Nazwa modułu z błędem
Sig[3].Value=ntdll.dll
Sig[4].Name=Wersja modułu z błędem
Sig[4].Value=10.0.14393.103
Sig[5].Name=Sygnatura czasowa modułu z błędem
Sig[5].Value=57b7e09e
Sig[6].Name=Kod wyjątku
Sig[6].Value=c0000005
Sig[7].Name=Przesunięcie wyjątku
Sig[7].Value=00058662
DynamicSig[1].Name=Wersja systemu operacyjnego
DynamicSig[1].Value=10.0.14393.2.0.0.256.48
DynamicSig[2].Name=Identyfikator ustawień regionalnych
DynamicSig[2].Value=1045
DynamicSig[22].Name=Dodatkowe informacje 1
DynamicSig[22].Value=1f2e
DynamicSig[23].Name=Dodatkowe informacje 2
DynamicSig[23].Value=1f2e5719a17a400ee7bcef9c38011573
DynamicSig[24].Name=Dodatkowe informacje 3
DynamicSig[24].Value=ba48
DynamicSig[25].Name=Dodatkowe informacje 4
DynamicSig[25].Value=ba4803f2d0f202ebc1746e0ba78f0e3c
UI[2]=F:\Steam\steamapps\common\FSX\fsx.exe
UI[3]=Program Microsoft Flight Simulator® przestał działać.
UI[4]=System Windows może wyszukać rozwiązanie tego problemu w trybie online.
UI[5]=Wyszukaj rozwiązanie w trybie online i zamknij program
UI[6]=Wyszukaj rozwiązanie w trybie online później i zamknij program
UI[7]=Zamknij program
LoadedModule[0]=F:\Steam\steamapps\common\FSX\fsx.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\system32\apphelp.dll
LoadedModule[5]=C:\WINDOWS\AppPatch\AcLayers.DLL
LoadedModule[6]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[7]=C:\WINDOWS\System32\USER32.dll
LoadedModule[8]=C:\WINDOWS\System32\win32u.dll
LoadedModule[9]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[10]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[11]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[12]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[13]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[14]=C:\WINDOWS\System32\combase.dll
LoadedModule[15]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[16]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[17]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[18]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[19]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[20]=C:\WINDOWS\System32\sechost.dll
LoadedModule[21]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[22]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[23]=C:\WINDOWS\System32\shlwapi.dll
LoadedModule[24]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[25]=C:\WINDOWS\System32\shcore.dll
LoadedModule[26]=C:\WINDOWS\System32\profapi.dll
LoadedModule[27]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[28]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[29]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\sfc.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[33]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\sfc_os.DLL
LoadedModule[35]=C:\WINDOWS\AppPatch\AcSpecfc.DLL
LoadedModule[36]=C:\WINDOWS\System32\ole32.dll
LoadedModule[37]=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule[38]=C:\WINDOWS\System32\IMM32.dll
LoadedModule[39]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[40]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.0_none_88fef4c26039fb25\COMCTL32.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\mscms.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\DDRAW.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\msi.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[48]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\SortWindows61.dll
LoadedModule[50]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[51]=F:\Steam\steamapps\common\FSX\steam_api.dll
LoadedModule[52]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCP80.dll
LoadedModule[53]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCR80.dll
LoadedModule[54]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[55]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[56]=F:\Steam\steamapps\common\FSX\language.dll
LoadedModule[57]=F:\Steam\steamclient.dll
LoadedModule[58]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[59]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[60]=C:\WINDOWS\System32\imagehlp.dll
LoadedModule[61]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[62]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
LoadedModule[63]=F:\Steam\tier0_s.dll
LoadedModule[64]=F:\Steam\vstdlib_s.dll
LoadedModule[65]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[66]=C:\WINDOWS\SYSTEM32\Secur32.dll
LoadedModule[67]=F:\Steam\steam.dll
LoadedModule[68]=F:\Steam\Steam2.dll
LoadedModule[69]=F:\Steam\DbgHelp.dll
LoadedModule[70]=F:\Steam\CSERHelper.dll
LoadedModule[71]=F:\Steam\gameoverlayrenderer.dll
LoadedModule[72]=F:\Steam\steamapps\common\FSX\API.DLL
LoadedModule[73]=F:\Steam\steamapps\common\FSX\ablscpt.dll
LoadedModule[74]=F:\Steam\steamapps\common\FSX\acontain.dll
LoadedModule[75]=F:\Steam\steamapps\common\FSX\ai_player.dll
LoadedModule[76]=F:\Steam\steamapps\common\FSX\atc.dll
LoadedModule[77]=F:\Steam\steamapps\common\FSX\controls.dll
LoadedModule[78]=F:\Steam\steamapps\common\FSX\demo.dll
LoadedModule[79]=F:\Steam\steamapps\common\FSX\facilities.dll
LoadedModule[80]=F:\Steam\steamapps\common\FSX\fe.dll
LoadedModule[81]=F:\Steam\steamapps\common\FSX\flight.dll
LoadedModule[82]=F:\Steam\steamapps\common\FSX\fsui.dll
LoadedModule[83]=F:\Steam\steamapps\common\FSX\g2d.dll
LoadedModule[84]=F:\Steam\steamapps\common\FSX\g3d.dll
LoadedModule[85]=F:\Steam\steamapps\common\FSX\gps.dll
LoadedModule[86]=F:\Steam\steamapps\common\FSX\livingwater.dll
LoadedModule[87]=F:\Steam\steamapps\common\FSX\main.dll
LoadedModule[88]=F:\Steam\steamapps\common\FSX\multiplayer.dll
LoadedModule[89]=F:\Steam\steamapps\common\FSX\panels.dll
LoadedModule[90]=F:\Steam\steamapps\common\FSX\sim1.dll
LoadedModule[91]=F:\Steam\steamapps\common\FSX\simprop.dll
LoadedModule[92]=F:\Steam\steamapps\common\FSX\simscheduler.dll
LoadedModule[93]=F:\Steam\steamapps\common\FSX\sound.dll
LoadedModule[94]=F:\Steam\steamapps\common\FSX\symmap.dll
LoadedModule[95]=F:\Steam\steamapps\common\FSX\terrain.dll
LoadedModule[96]=F:\Steam\steamapps\common\FSX\fs-traffic.dll
LoadedModule[97]=F:\Steam\steamapps\common\FSX\ui.dll
LoadedModule[98]=F:\Steam\steamapps\common\FSX\util.dll
LoadedModule[99]=F:\Steam\steamapps\common\FSX\visualfx.dll
LoadedModule[100]=F:\Steam\steamapps\common\FSX\weather.dll
LoadedModule[101]=F:\Steam\steamapps\common\FSX\window.dll
LoadedModule[102]=F:\Steam\steamapps\common\FSX\xuipc.dll
LoadedModule[103]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll
LoadedModule[104]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll
LoadedModule[105]=C:\WINDOWS\SYSTEM32\DINPUT8.dll
LoadedModule[106]=C:\WINDOWS\SYSTEM32\d3dx9_34.dll
LoadedModule[107]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.187_none_bab139cc35912856\gdiplus.dll
LoadedModule[108]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[109]=C:\WINDOWS\SYSTEM32\d3dx10_34.dll
LoadedModule[110]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[111]=F:\Steam\steamapps\common\FSX\sdkencryptedappticket.dll
LoadedModule[112]=C:\WINDOWS\SYSTEM32\DSOUND.dll
LoadedModule[113]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[114]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[115]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[116]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[117]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[118]=C:\WINDOWS\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[119]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[120]=C:\Windows\System32\urlmon.dll
LoadedModule[121]=C:\Windows\System32\iertutil.dll
LoadedModule[122]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[123]=C:\WINDOWS\SYSTEM32\d3d10.dll
LoadedModule[124]=C:\WINDOWS\SYSTEM32\d3d10core.dll
LoadedModule[125]=C:\WINDOWS\SYSTEM32\d3d11.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Zatrzymano działanie.
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=F:\Steam\steamapps\common\FSX\fsx.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=381DF571ED60C2BD257C942B863BDC44
MetadataHash=-1006629128

Share this post


Link to post
Share on other sites

 

 


Are you guys running FSX in compatibility mode with some windows version?

 

You should never tick anything in the compatibility boxes other than all the way down and make sure always run in administrative mode for ALL users is checked.

 

Since you have no addons installed, I highly suspect a cpu voltage issue.  If you system is overclocked, try moving your it down by two.  For instance, if it is overclocked to 4.4GHz, move it down to 4.2GHz.  You can also go to the optimal defaults in your BIOS too.  I get the ntdll.dll error almost every day but it is mostly at shutdown.  I get it occasionally at startup and the sim crashes to desktop but, when I restart the sim, it starts up normally again.  I have a feeling it does not like my overclock at 4.2GHz.  NTDLL.dll is connected to memory and a computer system problem (FSX-SE only causes the system to demand more from your CPU or your memory modules creating the issue.)

Share this post


Link to post
Share on other sites

The ntdll.dll errors occurs only when I tick "run in compatibility mode with Windows 8". When I have only ticked "run in administrative mode" there's no errors at all - it's just not starting after the splash screen.

I've disabled OC and checked voltages/temperatures using HWmonitor. Voltages are within limit of my CPU (I'm observing 0.92-1.192V and the specs said 0.6500V-1.4000V) and same for temperatures (max = 65 degrees). Not sure what are the limits for 3.3V,5V and 12V, I have; 3.376, 5.064 and 11.933V. Without the OC it still doesn't work.

Share this post


Link to post
Share on other sites

 

 


The ntdll.dll errors occurs only when I tick "run in compatibility mode with Windows 8".

 

Yes, I told you not to check this compatibility box and only the Administrative Mode should be checked.

 

There is one other reason why I know FSX will not start up and that's if you do not have Microsoft.net 2.2 and Microsoft Visual C++ 2005 but I see those programs are installed.  If you had MyTrafficX or MyTraffic6 installed, that would cause ntdll.dll errors too but at least you would be able load FSX-SE.  

 

Make sure you do not have any dll.xml or exe.xml left over from a previous installation left in your folder (they are located in the same folder as your fsx.cfg).  Make sure you do not have the fsuipc.dll in your Modules folder (or anything in the Modules folder).  Even if you had bad voltages and your system was overheating, FSX-SE would still load.  You cannot get past the splash screen.  So it is something in your fsx-se directory.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I know you wanted me to check only administrative mode - with that it was not working. Suggestion to reinstall windows is not possible for me so I started exploring any other ideas I had - one was for running with compatibility mode set to windows 8. Sorry if that brought confusion. I thought it's worth a shot to check it.

If there were some issues in my FSX-SE directory I would removed them while I deleted the FSX-SE. I deleted everything based on the PMDG instruction you provided. After that I did a clean install of FSX so there are only defaults.

Is it possible that some of the VC++ redistributables are broken? Would it help for me to reinstall them? I tried Microsoft .NET Framework Repair Tool - it didn't changed anything. Thanks for all help so far, I really appreciate that.

Share this post


Link to post
Share on other sites

The AVSIM CTD Guide provides locations of all of the files too, including the location of the hidden folders (right after the guides intro).  The dll.xml goes in the same folder as the fsx.cfg.  When you uninstall FSX-SE, this folder will not be removed and you have to manually remove it.  If you do not manually remove it, the fsx.cfg will be overwritten but not the dll.xml when you reinstall FSX-SE.  So, if there is a dll.xml still located there, it will load when you first startup FSX and try to load modules.  If it cannot find the modules, it will crash (in some cases).  The reason I asked for you to check to make sure fsuipc.dll is not installed in the modules folder or on your computer, is that the version installed may not be compatible with your brand new installation of FSX-SE.

 

This is about it.  One more suggestion - You don't want to reinstall Windows and I don't blame you.  The guide provides a way where you can fix a corrupted User and this would definitely wipe out any remnants of your current user file.  Look on page 21.  Click on corrupted user profile and it will take you to the Microsoft website to provide you with instructions on how to fix a user profile.  Look under 'Repair and Recovery'.  I did it once and it give my system a breath of fresh air like a new installation.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I have some progress. The link to corrupted user redirected me to default windows 10 support site but I found that: http://www.techbout.com/fix-corrupt-user-profile-windows-10-9139/ I modified the registry keys - no luck. So I created a new user and started the FSX from that user (before copying any data - this way I was sure everything is fresh with no configuration) and it worked.

So I thought - OK, let's copy everything from AppData\Local\FSX and AppData\Roaming\FSX from the old user to the new user. I first removed all directories from new user (which were created when I run the FSX) and after that copied them from old user. Run FSX again - still working. It looks like there's no issues with my configuration and the user profile got corrupted somehow.

 

Thank you very much for your help I'm very happy that I have everything working correctly again I just have to move all the data to new user and that's it.

Share this post


Link to post
Share on other sites

Glad you might have found a fix.  Be careful moving the old files over.  Sounds like your System Registry was pointing to another user.  I had to do this once before too.

 

As far as the corrupted user redirecting you to Windows 10 support, it sent me to Windows 7.  It has an option to indicate the Windows version.  In any case, it is pretty much the same routine for Windows 7 and above.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this