Windows 10 and FSX

Windows 10 latest update and FSX

 

Ok I loved Windows 10, spoke about and wrote about how great it would be for us as a community.

 

It ran smoothly and without any real faults or crashes that were not “Operator Caused” till this latest update #1709 now it has me rethinking that Microsoft is taking a good thing and making it unpalatable.

 

They are making it impossible to navigate through the faults that are starting to present themselves causing my FSX – Acceleration Game Play to crash and just go “Wonky”.

 

Here is what is happening:

 

1. Error: “Error Creating Child Window”

2. Error: “Unable to Load”

3. Error: “Unable to save flights”

4. Error: “Unable to Escape or End Simulation”

5. Error: “Invalid Commands”

6. Error: “Unable to Start”

 

Feature update to Windows 10, version 1709

Successfully installed on ‎12/‎7/‎2017

 

• FSRecorder – 12/10/2017 20:16:35 I had to delete and remove all files and folders related to this program, which is BAD! I always recorded every flight for future reference and video recording! Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: RecorderFSX.dll

Report Id: 115a9f61-c142-406e-8129-0778ee16b63b

 

• UNKOWN FAULT! – 12/9/2017 20:41:48 What the “frig” is this? There is no way to trace this one down. Where do I search for remedy or where do I go to resolve?

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: unknown

Report Id: b28b8e8e-5f6b-4aff-88da-5834bac94052

 

• MFC80.DLL – 12/9/2017 22:09:28 OK this is repairable I just opened MSCONFIG and turn off all Microsoft apps that use this .DLL and was able to reload and actually fly for a 45 minutes. Then we started with the Error messages again.

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL

Report Id: 4b50d187-1d3f-4951-9e07-4ec1f6cb5cbc

 

So What Now? Do I keep fighting these faults? Or go back to Windows 7? Which would require building a dedicated stand alone system disconnected from the web for just FSX nothing else.

 

If you are having issues with this latest update start a support ticket with Microsoft. If you take the time to actually chat with the Representative maybe we will get the attention of Microsoft and maybe they will resolve these issues the link is listed below. If you’re not having issues with Windows 10 consider yourself lucky, but as Windows 10 grows and updates it will push older programs to the invalid box.

 

Personally I feel Microsoft was trying to hypothetically rebuild a classic car and forgot to put the fuel injectors in before releasing to the public.

 

Be aware that Microsoft no longer Officially Supports FSX so you need to be tactful and diplomatic with the Rep.

 

https://support.microsoft.com/en-us

 

Get past the Virtual Agent, and go to “Contact Us” and start chat.

 

I have the full fault list printed below so maybe someone, more intelligent than me can see how to resolve these issues.

 

Respectfully:

 

David

 

 

 

Log Name: Application

Source: Application Error

Date: 12/9/2017 22:09:28

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-2T98K66

Description:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: MFC80.DLL, version: 8.0.50727.6195, time stamp: 0x4dcdeca2

Exception code: 0xc000041d

Fault offset: 0x0005a6f1

Faulting process id: 0x285c

Faulting application start time: 0x01d37161dd18b42d

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL

Report Id: 4b50d187-1d3f-4951-9e07-4ec1f6cb5cbc

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

1000

2

100

0x80000000000000

717

Application

DESKTOP-2T98K66

fsx.exe

10.0.61637.0

46fadb14

MFC80.DLL

8.0.50727.6195

4dcdeca2

c000041d

0005a6f1

285c

01d37161dd18b42d

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL

4b50d187-1d3f-4951-9e07-4ec1f6cb5cbc

 

//##################################################################################

//##################################################################################

//##################################################################################

 

 

Log Name: Application

Source: Application Error

Date: 12/9/2017 20:41:48

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-2T98K66

Description:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc00000fd

Fault offset: 0x703f71cd

Faulting process id: 0x1780

Faulting application start time: 0x01d3715d1110bef0

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: unknown

Report Id: b28b8e8e-5f6b-4aff-88da-5834bac94052

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

1000

2

100

0x80000000000000

708

Application

DESKTOP-2T98K66

fsx.exe

10.0.61637.0

46fadb14

unknown

0.0.0.0

00000000

c00000fd

703f71cd

1780

01d3715d1110bef0

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

unknown

b28b8e8e-5f6b-4aff-88da-5834bac94052

 

//##################################################################################

//##################################################################################

//##################################################################################

 

Log Name: Application

Source: Application Error

Date: 12/10/2017 20:16:35

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: DESKTOP-2T98K66

Description:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: RecorderFSX.dll_unloaded, version: 1.3.0.0, time stamp: 0x4772d03d

Exception code: 0xc0000005

Fault offset: 0x0000ca90

Faulting process id: 0x1fd0

Faulting application start time: 0x01d37211ef937ced

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: RecorderFSX.dll

Report Id: 115a9f61-c142-406e-8129-0778ee16b63b

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

1000

2

100

0x80000000000000

890

Application

DESKTOP-2T98K66

fsx.exe

10.0.61637.0

46fadb14

RecorderFSX.dll_unloaded

1.3.0.0

4772d03d

c0000005

0000ca90

1fd0

01d37211ef937ced

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

RecorderFSX.dll

115a9f61-c142-406e-8129-0778ee16b63b

 

//##################################################################################

//##################################################################################

//##################################################################################

This is a known problem for many users, including myself, after 1709 was installed. There's supposed to be a Windows update coming out tomorrow which will hopefully fix the problems with not just FSX but other 32 bit programs as well.

 

If it's been less than 10 days since 1709 was installed on your system then you can roll back to 1703.

 

Go to Start\Settings\Update And Security\Recovery and see if the option is there for you.

Thanks!

I thought a update was longer on the wait, so if it doesn't fix tomorrow on the new update then i'll see about rolling back.

Maybe, don't know since I'm using the box version.

 

https://steamcommunity.com/app/314160/discussions/0/530646080866199615/

 

Good luck and cheers,

Just got the newest Win10 update released today and problems seem to be solved with FSX boxed.

I'm running FSX boxed edition and for the last month (since the Windows 1709 update) the screen capture key (v) and downloaded weather haven't been working. Windows updated yesterday and all seems to be running smooth as butter now. checked the weather with the Aeroweather app on my phone for various airports and it matches perfectly. took several selfies using the V key and it's working flawlessly.

so far, so good here..