Jump to content

Recommended Posts

This is not a ORBX problem, but is anyone having issues with the latest update from Microsoft concerning update #1709 for Windows 10 and FSX/P3D?

Several forum members on other sites are reporting major issues on this latest build from Microsoft, I feel that it will effect our little realm and do some serious damage to the flight sim world.

I am placing the faults that have occurred to my system for you to review, and compare if you are having the same issues or even different issues.

Remember that ORBX and all other vendors are also victim's of this bad update, if you can't fly on Windows 10 then why buy anything that relates to flight simulation?

If you or the ORBX team are working on the 1709 update and all of it's issues then I thank you ahead of time. If you know a fix then please tell me. As for now "I'M GROUNDED!"

 

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

 

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.

 

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

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:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-12-10T04:09:28.118617800Z" />

    <EventRecordID>717</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-2T98K66</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb14</Data>

    <Data>MFC80.DLL</Data>

    <Data>8.0.50727.6195</Data>

    <Data>4dcdeca2</Data>

    <Data>c000041d</Data>

    <Data>0005a6f1</Data>

    <Data>285c</Data>

    <Data>01d37161dd18b42d</Data>

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

    <Data>C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL</Data>

    <Data>4b50d187-1d3f-4951-9e07-4ec1f6cb5cbc</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

 

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

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:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-12-10T02:41:48.656010300Z" />

    <EventRecordID>708</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-2T98K66</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb14</Data>

    <Data>unknown</Data>

    <Data>0.0.0.0</Data>

    <Data>00000000</Data>

    <Data>c00000fd</Data>

    <Data>703f71cd</Data>

    <Data>1780</Data>

    <Data>01d3715d1110bef0</Data>

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

    <Data>unknown</Data>

    <Data>b28b8e8e-5f6b-4aff-88da-5834bac94052</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

 

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

 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:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2017-12-11T02:16:35.757312200Z" />

    <EventRecordID>890</EventRecordID>

    <Channel>Application</Channel>

    <Computer>DESKTOP-2T98K66</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61637.0</Data>

    <Data>46fadb14</Data>

    <Data>RecorderFSX.dll_unloaded</Data>

    <Data>1.3.0.0</Data>

    <Data>4772d03d</Data>

    <Data>c0000005</Data>

    <Data>0000ca90</Data>

    <Data>1fd0</Data>

    <Data>01d37211ef937ced</Data>

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

    <Data>RecorderFSX.dll</Data>

    <Data>115a9f61-c142-406e-8129-0778ee16b63b</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

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

Respectfully:

 

David

 

 

 

Share this post


Link to post
Share on other sites
44 minutes ago, Nick Cooper said:

Hello,

apparently there will be a Windows update tomorrow, 12th December, that will cure all of these problems.

We shall see.

"We shall see "Indeed Nick. Hope they do fix things as I had to roll back to my previous build.

 

Among other things the update introduced terrible screen tearing to P3D & clicking on the SPAD desktop icon invoked attempted installation of MS Office 2010 (which is already installed).

 

Very weird. The rollback seems to have worked fine & fixed these issues so you may want to try doing that David if the update doesn't do the trick.

 

Of course will have to update Win10 at some stage, like death & taxes the update will claim you someday!:lol:

Share this post


Link to post
Share on other sites

Beware

 

For me:

Deleted several of the Orbx scenery files

Made everything dark

Removed Nvidia Profile and I cant reimport it

 

Takes a loooong time to install and acts like a new windows version

Share this post


Link to post
Share on other sites

My problems with the 1709 update of Windows 10 were:

horizontal lines that flowed on P3D images especially in side views and
the update of Nvidia drive of the GTX 1070 gave an error and did not perform the installation.


Returning to Windows 1703 everything was regularly reworked.
 

Share this post


Link to post
Share on other sites

I am on Prepar3d v4.1. Not. a. single. problem. with the 1709 update from Windows except some simming unrelated, minor stuff. Might be time to put this 11 year old simulator away, no? I mean, you also do not expect that IE6, Firefox 20, Word 2006 and other software from 2006 still work without any issue, no? So why do you expect this from FSX? I always wonder...

Share this post


Link to post
Share on other sites

Haven't seen if there was any FS related issues (running P3D) but I did the update last night and when I checked on it this morning the fans were running constantly when typically they are off unless under heavy load.  So something is up there....I haven't had time to investigate

Share this post


Link to post
Share on other sites
Guest Colin M

Todays Microsoft Tuesday update

December 12, 2017—KB4054517 (OS Build 16299.125)

has fixed these problems at last for me using my 32 bit FSX, update became available about an hour ago, reading on LM's forums its fixed the P3Dv3 problems too.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...