Win 10 KB4038788 Update crashes my P3D v3

[kuhdan]

Just a few minutes ago, I've installed the new 2017-11 Updates KB4048954 and KB4049011. The CTD problems if loading another scenario then the P3D default one, is finally gone!

However the creating child window error is back again!!!!! This Problem was obviously solved before with the build 1709 but came back with the most recent updates which Microsoft released today!

I'm running P3D v3.4. Will now try to install my v4.1 Version and test it with various add-ons.

[Alexis_67]

Re hello,

I fly with the Fslabs Concorde during 30 minutes, I had no error. Then I choose A340 from BBS, and I had " error creating child Windows " and crash..

then I also had this:

[Livingston]

Hi
I think you may be correct Livingston. My problems essentially started with the Fall Creators update. I think Microsoft need to take a good look at what that might have caused, or maybe it just compounded an earlier problem that just did not show up until that significant update. Sadly, P3D v3.4 is unusable for me.
Regards
Keith

same for me : V3.4 is unusable.

[Pete_H]

It seems to work fine for me. I tried all scenarios that previously would CTD at 100%, and they now load fine. I haven't encountered any "error creating child window" instances either, even when opening 2D panels, which previously would cause the error.

[gary20]

So disappointing. Especially after waiting a month for the fix.
I too get the child window error and other flights just CTD ...

It's coming off of my hard drive as it's next to useless now.
Could almost cry at the money wasted on add-ons ...

[UAL1035]

updated and just started the Sim with default F18 and default field. Will check a flight with Addons later on and report back.

[Erni49]

Today updated Win 10 Pro v1709 OS Build 16299.64, with KB4048955 'delete this post update for W10 version 1709 for amd64-based systems'. Unfortunately no solution for the CTD's and 'Error creating child window' on P3Dv3.4.22.19868 client. Spent whole afternoon and evening with debugging (switching off and on various add-ons), but am still not sure what is causing the problem.
Looks like it is NOT (in combination with LM aircraft), FSUIPC, LINDA, RAASPRO, SODE or GSX, as I thought first. Add-on airports, I tested 2 from AS(EHRD and EHBK) seem ok to, in combination with LM aircraft
However add-on aircrafts like AS Airbus320 or CRJ700, seem to trigger the 'Error creating child window' the moment you start changing panels/views. Then even selecting another vehicle gives the error and a CTD.
I hope someone else can confirm if my findings are correct.
My conclusion is that the last Microsoft update did NOT solve the problem with P3Dv3.4

Regards
Reinier Nieuwboer

[g-bobb]

for info ref child window errors.

(im on win 10 64 bit. graphics 980ti)
ive not uninstalled any addons or reinstalled p3d ver 3.4

im having the same ctd and child window errors as others have posted.
i installed the latest update today (14 nov 2017) and win10 is fully up to date (with no updates disabled.)
results:
p3d will now load ok every time.
however trying to change aircraft still results in the child window error and p3d shuts down.
a temporary work around i found is:
go to options, settings, general
tick the box 'show scenario start up screen'.
restarting p3d will now allow me to select aircraft ok by using the scenario screen. :-)
all runs ok.
but, if the sim is already running, and with an aircraft parked at any airport,
if i click vehicle,select, i always get the child window error and the sim shuts down. :-(
i wonder if lockheed will allow a discounted upgrade for ver 3 (32bit) users to upgrade to v4(64bit) which apparantly does not suffer this problem.
or do we have to wait for microsoft to bring out another update?
but at least i can now get p3d to run .

[kbowman61]

In all my years flightsimming, I can't remember a time when a Microsoft update has caused such a bad failure of FS as with this latest issue. If it was not for the appearance of P3D v4 this year, I think there would be greater anger about this problem, but a lot of folks have moved to 64 bit. However, it is still galling to have paid for add-ons which can no longer be used, not to mention the native aircraft which also fail.
Keith

[NEPTUNE]

I'm waiting for this update to finaly use my sim normaly , i read your comments ...........

I'm poor boy with my P3Dv3.4 and ADDON don't work the most the 767 LVLD was upgrade for this version and can't be use for a long time . And now i can't fly ...

Waiting for a new update but ist's far away to use it ...

Patrick

[Direct-To]

I'll add my update using 3.4,

I just installed the update and I still get the child window problem but it only crashed whenever I try and switch planes or locations after loading the default scenario but in the cockpit it will not crash if I click for a 2d fms or panel screen.

Whatever update windows came out with a few weeks ago after 8788 my 3.4 was able to run again without the consistent CTD problems but that's also when I started getting the child window problem.

[72westy]

After a 1 month wait I believe Microsoft needs to step up to the plate for a quicker fix. Clearly this can't be just affecting the P3D platform.

[Agent X20]

I have create window errors before and after today's MS fix.

P3D V3 is unusable and has been since the fall creators update.

[ollie]

P3D 3.4 unusable!
One flight after MS update and Child Window again.

[sincedric]

Installed the latest windows update KB4048955 on my laptop:

1. First time loading P3D, FSLabs A320, Aerosoft Zurich, no error prompts, loading successful.

2. Following 1, changed aircraft to PMDG 777-300ER, no error prompts, loading successful.

3. Restarted P3D, PMDG 747-400, T2G Hong Kong, no error prompts, loading successful.

4. Restarted P3D, PMDG 747-400, Orbx Melbourne, no error prompts, loading successful.

5. Restarted Windows, FSLabs A320, FlyTampa Amsterdam, no error prompts, loading successful.

6. Following 5, changed aircraft to PMDG 747-400, no error prompts, loading successful.

Again I might just be lucky here but it works for me. Haven't done any takeoff and landings though.