Rob, you may want to reopen topic KB4038788

[Bingo41]

Here is the text I posted on AVSIM a few minutes ago (I am running P3D v3.4):

Hi All,

I just completed downloading the Latest Microsoft "Creative Update," or what ever it is called, and it DID NOT fix the issue I had experienced with the last security update. Instead, it gets thru the start up phase, but once you select the A/C and airport, it begins to load, but at the 80% point it stops with the following window message:



Lockheed Martin @ Prepare 3D

"Got Error Creating Child Window"





When I click ok, acknowledging the error, the error window closes as it attempts to complete the loading process, but then crashes. This happens consistently with the default A/C I have chosen which is the Extra 300 sport plane. However, when I load the PMDG 737-700, it freezes at the 80% loaded part. There is no crash in this instance, it just sits there at 80%. I also noticed my GoFlight radios never lite up like they usually do.

All the years I have been simming, I have never had so many issues with the MS operating system updates, than I have with Windows 10.

I will be interested to hear if others were more successful than me, or experienced similar results?

Bill Clark

[Clifton Crane]

Are you able to successfully start Prepar3D without any USB devices plugged in? If so, you may want to try switching to the Direct Input API. If this cannot be done via the UI, you would have to manually add the following to the [CONTROLS] section of the Prepar3D.cfg:

Code: Select all

EnableDirectInput=True

The Prepar3D.cfg file can be found in %%%APPROAMING%%%\Lockheed Martin\Prepar3D v4.

Thanks.

[Bingo41]

Hi Clifton,

I added the EnableDirectInput=True but the GoFlight radios did not illuminate.

I did not try disconnecting the Goflight hardware or TrackIR.

However, It now loads to 100%, but still crashes.

Bill Clark

[Bingo41]

Clifton,

I disconnected all my USB devices, except my USB Mouse and Keyboard, and p3D v3.4 crashes.

Bill

[MikeB54]

Those of us on the Windows Fast Ring started getting the "Error Creating Child Window" errors shortly after the Creator's Update was released last spring and we started receiving the Redstone 3 builds that were destined to become the Fall Creator's Update. Now that's it out I expect many more of these reports.

Mike

[zap737]

Guys, can anyone confirm if V4 is affected or not with the Fall Creators Update installed.
If not can you post symptoms with V number clearly indicated.

[72westy]

It was mentioned earlier that the new Creators update will NOT include a fix but MS is aware of it and are working with LM for a resolution.

[Rob McCarthy]

That is correct, Microsoft confirmed that the issue will still be present in the Fall Creator's update. Microsoft is actively working the issue. I will update the original topic as soon as I have more information.

Regards,
Rob McCarthy