P3D3.4 "Error creating child window"

[RobWhight]

Hi,

I've done a search and see that this is not an entirely new issue though it is new to me.

Background
I had P3D 3.3 installed with a significant number of updates (Aerosoft, PMDG, ORBX, etc.) and the whole installation had become a bit messy and unstable. As a result, I spent a fair bit of time on things other than flying. V3.4 came out and I left off downloading the full suite of files until about a week ago when I wanted to get back into some stable sim flying so though it was worth reinstalling everything (Truth be known I'm sort of waiting for the 64bit version but that isn't the point of this thread !)

What happened
I did a full uninstall of all the add-ons and P3D in accordance with the various instructions (cleared out %programdata%, %appdata%, etc., etc.), formatted the SSD that I dedicate to P3D, rebooted, ran CCleaner, tidied everything up etc. Then did the reinstall of V3.4 from the new downloaded files.

Issue
I keep getting "Error creating child window" crashes. I can't seem to tie it down to a specific event (e.g. changing aircraft in the sim, changing location, etc.) - the timing seems to be a bit random. I haven't reinstalled much by way of add-ons yet.

Some things that *could* be relevant:
- I do have a Saitek X52 joystick
- logitech mouse (runs a driver system called overwolf)
- two GTX 780Tis in SLI with NVidia surround on across three monitors (5040x1050)
- ASUS Xonar soundcard

All this stuff worked fine before so not sure if they really have any relevance.

Running i7-4770K @4.1MHz, ASUS Z87-Pro, 16Gb RAM and Windows 10 Build 170414-1642

Any suggestions gratefully received.

Thanks,
Rob

[MikeB54]

I started having that issue about a week ago. It started about the same time the Windows 10 Redstone3 builds started hitting the Windows Insider Fast Ring. I think that's where the problem is. Like you, I am also on Build 16179.rs_prerelease.170414-1642.

Mike

[RobWhight]

Mike,

Good to hear in an odd way - at least it is starting to look like it isn't something I've "done" :-)

Let's see if others also appear and whether some one clever has a solution :-)

Cheers,
R

[dwadsworth]

I've had the problem and solved it by rolling back to 16170. It stated failing when MS started changes for OneCore. Seems to be related to external processes like PMDG aircraft use.

Dave

[CptVince]

I just started to get this problem! Build 16176.

I get the error everytime I start the sim and I can't use GSX and many other things anymore.

Vincent

[FireRx]

I've check my error logs and this seems to be a script error in the logs. I'm wonderw the move to .NET 4.7 is the cause of this. Problem is still present in Windows 10 Build 16179 also.

[FireRx]

nothing from LM???
problem is still unresolved

[FireRx]

okay ,

So far I'm finding this could be a C++ issue. Any fixes would be helpful please. :(

[RobWhight]

All,

I notice that my windows 10 updated to Build 16184 (dated 170424.2211) this morning. I haven't flow much since but when I did, I did NOT get the child window error. Not conclusive yet and I'll keep you posted.

R

[FireRx]

yeah it's something definantly affect any add on's on Prepar3D. I reinstalled AS16+ASCA my PMDG Aircraft, and my other high end airport sceneries from FSDT, and FlightBeam. I had to reinstall GSX to get it to function almost after each successful load in Prepar3D

The old nVidia Drivers must be removed via DDU to get a clean installation of the new GPU driver. Otherwise your asking for Artifacts and occasional black screens with the new driver with just upgrading them. I got all that working good now. Reinstalled all of the Prepar3D component to the latest update. Hopefully, LM will come up with a solution to this. the only thing I see new on the OS since the Windows update is MS Visual 2015 was added.

[HGGS Hornet]

Hello I keep on getting this Error Creating Child Window error every time now is there any fix to it?

[dwadsworth]

There are several other active threads discussing this. Win 10 Insider Updates starting at 16176 through 16184 have this problem. It affects any add-on that wants to open a window on top of the sim. I've managed to roll back to 16170 and do not have the problem. It started when MS went to OneCore for the Redstone release. LM will probably have to solve this issue.

Dave

[HGGS Hornet]

how do you roll back to 16170 and will i have to reinstall anything?

[HGGS Hornet]

I really hope they fix this soon

[FireRx]

Bad news if you have a UEFI installed the 16184 , we're stuck until we have an Iso or a new build that address these issues. I've already posted a number of feed backs this weekend to Microsoft. I don't believe it's anything on Prepard 3D's side. I've had to reinstall GPU drivers, add ons like MT6, and GSX several times to get them to work on just one flight properly. I will be patient. Getting silly anomilies I haven't seen in years. and never on P3D. DGXI failures, Black screens, visual tearings. it's all bad. Microsoft usually have 1-5 builds in a series that are just unusable. skip/Avoid Windows 10 16184 if you can.