Win 10 KB4038788 Update crashes my P3D v3

[FLYING TIGER]

Hello,
2 days ago I posted a question (see below) somewhare else on the forum. Martyson adviced me to post my problem here because this issue has already your full attention. I can add this to what I have written below: the Ezdok problem is fully solved (uninstal+reinstal) and it is not sure that that problem had anything to do whit the "child window" problem. Perhaps it was just a coincidence.

Here below my OP , and after following the advice from Martyson to read about this threat here, I replyed to him and that reply is posted here also at the bottom of this post. I anyway thanks in advance to read this and starting to help me out. Remember please that I'm not good in all this stuff (comes with the age I geuss :-) )


Hi,
After having a little trouble with Ezdok v2 many things start to go wrong. P3Dv3 doesn’t work after
selecting an aircraft (or later on in the proces)
It goes like this:
I start P3D and the normal “Scenario Setup” screen appears. I select an airplane, click OK. Sometimes it goes already wrong here and the message “Error creating child window” appears. https://www.dropbox.com/s/f9v7734bik4cw ... 0.jpg?dl=0
Then 2 things can happen. Either the next screen appears (so far so good), or P3D closes with the message “P3D doesn’t work anymore (Free translation from Dutch-don’t know if this is what you see in English)
https://www.dropbox.com/s/7kykzkmrkghur ... r.jpg?dl=0
In the first case I click Ok and then it takes some time until I’m in the cockpit of the selected plane (in this case it’s the new Alabeo Moony). Or sometimes P3D shuts down, its different all the time.
Normaly, when in the cockpit, I can click on Shift + a number key (above the caracter keys) and then a little should pop up where I can select a few things fort he set up of the cockpit. Also in the A2A aircraft, and others, you could do those things. But eacht time I do so the same message appaers “Error creating child window”.
https://www.dropbox.com/s/clf00d8768wmn ... t.jpg?dl=0
Somethimes when I click Ok in this message the message disappaers with no further outcome (except that I can’t use the shift + ? possibility) but sometimes P3D will shut down with the message “P3D doesn’t work anymore” once again. What can I do about this issue? Anybody have a solution? Or is it possible to reinstall P3D without having to uninstall P3D and all addons (ORBX,GTN750,FSUIPC4,EZDOK etc.) and then to reinstall all addons again after installing P3D? Not looking foreward to this because it takes a whole lot of time, and many things can go wrong during this process.
It is also impossible to select another plane once I’m in a scenario. Then the same error message appears without anymore I can do. Sometimes when clicking OK in that message P3D shuts off.

I hope my request for help is clair, because I’m not a well seasoned simmer and certainly no computer wizzard!
Awaiting a positive reply,
Kind regards,
Eddy Vandenberghe, The Netherlands


2nd reply to Martyson:
Hello Martyson,
thanks for replying. I did have a quick look, no..I had a long look :-) But as I mentioned I'm a total computer no-no and everything in those posts is hocus-pocus for me. They are talking aabout things I even never heard of. Sorry to say but it's the thruth. Many of the posts are refering to something called WIN 10 KB 4038788 and user.dll 10.0.16299.64.
I wanted to check whats on my system but haven't got a clue where to look. The only thing I could find via the control panel (I think that's wath it is called in Englisch) is the following. Can somebode tell me where I have to look for checking these 2 indications please?
https://www.dropbox.com/s/h6kg40shkcguj ... o.jpg?dl=0

Thanks in advance,
Regards, Eddy

[ScottG]

Thankfully I'm using Windows 10 Version 1703. I applied all the recent updates and I seem to be back in business with my Oculus Rift. I'll be avoiding Version 1709 for the time being. I spotted this on the Avsim forums, hope it might help get folks up and running...

https://www.avsim.com/forums/topic/5244 ... ld-window/

Also has anyone tried Hugo's work-around

Hello,

I found a temporary solution , with update KB 4048955 having a flight for about 40min. ELLX-EBBR.

Before starting P3d Delete Vehicle Favorites
Default.xml
Default .wx

Start P3D Default aircraft
select small aircraft

select saved Boeing IFLY

This is working for the time being , request confirmation from other simmers ?

Hugo

[Martyson]

" I spotted this on the Avsim forums, hope it might help get folks up and running..."

It was also posted on page 21 (previous page) of this topic.

[Alexis_67]

For my part, I will reinstall the 1703 version. I am tired of all the problems. The time to wait for a corrective update of microsoft we will be more alive ..

[Erni49]

For me the AVSIM post 'removing the .NET 4.7'did NOT work.

I have tested in the past days with and without several add-ons, and as mentioned in my post earlier this week, my add-on aircrafts Aerosoft A320 and CRJ700 are having the Child Window Error. But I could also CTD, with the 'child window error' the default F22 Raptor selecting it after an addon aircraft.
My current procedure, that is partly based upon Hugo's post, (thanks Hugo) is now as follows:
- Load the default scenario, with the F22 at Eglin on Rwy 19, Weather: Fair, Graphics: Default, Time Reset to System Time
- Change the vehicle to my addon aircraft
- Change the location to my Airport and Gate
- (Optional) I open now a new view -outside-spot, undock that view and move it to my second screen, so I can save it in the scenario
- Change panels/views in the Virtual Cockpit of your aircraft, you probably will get the 'Error can not create child window', but not a CTD. I got for the AS-A320 6 popups with the error and then it was gone.
- Save this in a scenario (I name it for example EHRD_A320_D2, or EHRD_CRJ700_B3, so I can recognize it later.
Close P3D and start it again to make your next scenario.
Do not switch vehicles, after you have loaded an addon aircraft, because that will lead often to the error and a CTD

For flying you start P3Dv3(.4) again with the default scenario, F22 ath Eglin Rwy 19.
Then load one of your scenarios as created/saved earlier, reset the time if you wish and you can fly (I hope you can) I could and made yesterday my first flight with the AS-Airbus320, since September 13, the KB4038788update from KLAX to KMRY, with addons EFB, GSX, SODE and RAASPRO.
I still need to test with FSUIPC, ASN and STB, and other graphic settings, but that will come later. First I will (again) completely remove/clean/reinstall the P3Dv3 folders as advised in the debugging instructions on top of this forum. I advise also to clean the P3Dv3 folder in your documents before setting up the scenarios as described above.

I hope this will work for others to.

I do have P3D4.1 also, that works fine for now. But my favorite Airports and Aircrafts are not yet available for 4.1, so I will keep my P3Dv3.4 alive, for the time being.

I am currently on WIN 10, 1709 with all the updates, see spec below

OS Windows 10 Pro
Version 1709
Build 16299.64
Updates KB4041994 25-Oct-17 Update for Windows 10 Version 1709 for x64-based Systems
KB4048955 14-Nov-17 Cumulative Update for Windows 10 Version 1709 for amd64-based Systems
..\SysWOW64\user32.dll - version 10.0.16299.64; date modified 25-Oct-17, date created 14-Nov-17

Prepar3D Prepar3D v3 Academic 15-nov-17 28.6 Gb 3.4.18.18870
Prepar3D v3 Academic Client 15-nov-17 418 Mb 3.4.22.19868
Prepar3D v3 Content 15-nov-17 11.7 GB 3.4.22.19868
Prepar3D v3 Scenery 15-nov-17 24.9 Gb 3.4.22.19868
Prepar3D v3 SDK 3.4.22.19868 14-sep-17 438Mb 3.4.22.19868

Best regards
Reinier

[jdlinn]

FYI - If any scenery dev's are stuck because they can't use IS3 in V3.4 (we've been out of business for almost 2 months now) ... I've found a solution, but it is not a pretty process, but you can use IS3.

Temporary Fix for IS3 until next windows update...
Restart computer
Delete /documents/Prepar3d V3 Files
Delete /users/[your name]/Apps/Local/Lockheed Marting/Prepar3d
Run the IS3 ModuleInstaller.exe from IS3
Uninstall then
Re-Install
Run P3D V4 use Run as Administrator
After initial data setup ... you get a window asking you to check
Online for IS3 Update (click check online) ... OK on confirm
You will only have the Lockheed Martin Jet (Default Scenario)
Go to 2D cockpit so you can see without the panel
Click on Addon Tools ... and select IS3
Let it do its thing to start up
Recheck libraries
Select the bgl you want

This may also help people get a handle on this problem with P3D/Win 10. If I don't follow this exactly, it does not work.

[ianor]

A quick update from my perspective:

Win10 64 bit v1709 KB4041994 / SysWOW64\user32.dll - version 10.0.16299.64

P3Dv3.4.22.19868

I have just completed a successful 2 hour flight with add-on a/c and airports.

I always start P3D at the default location (Eglin) and default F-22. Reset the time, move to departure airport of choice, select add-on a/c of choice (Aerosoft Airbus).

I had only one "Child Window" error message when, in flight, I went to the ADD-ONS in the menu bar. Closed the error message and the flight continued normally. Could not access the Add-On menu thereafter.

[MartinP3Duser]

This below I wrote just urlier:

A few months ago the problems occur, the software crashed at start-up after selecting a PMDG vehicle.
Sometimes a message occurs: “/!\ Error creating child window”. Than it crashed.

I looked in the forum and saw something about disconnecting the USB control sticks. Also this is not working.
Also waited for de Windows update last week (nov 2017) but that also did not work.

Struggling to long now with it.

Can you help me?

I use:
Windows 10 Home 64bit version 1709 build 16299.64
Intel Core i7-6700 CPU @ 3.40 GHz 64bit
16Gb RAM
NVIDIA GeForce GTX 970 (4GB GDDR5)
Norton Security up-to-date (Prepar3D is in the Firewall list to allow internet access)
Prepar3D_v3_Professional_3.4.22
#

[SWA555]

Hello,

I tried al lot of trics from this site, even my own tric is unreliable, i regret .

I give up, gonna wait for update in december.

Hugo

[kerberos42]

Today I tried the following:
- Uninstalled all addons and Prepar3d
- Deleted all Lockheed Martin folders in \Program Files, %username%\AppData, and \ProgramData
- Scanned the registry, and deleted all orphan entries relating to Prepa3d

Reinstalled Prepar3d 3.4

Everything worked fine for a couple of hours without issues including creating several different scenarios

Reinstalled PMDG 737 base package

Loaded the default flight (F-22 @ Elgin), switched vehicle to PMDG 737, no issue. Selected New Scenerio and received an instant Error creating Child Window error, followed by CTD.

I uninstalled PMDG and the issues went away. I'm going to try the same thing with Aerosoft A320.

Maybe this gives some insight into the issue, possibly its more an addon issue, or at least now P3d deals with addons.

[kerberos42]

Finished trying with Aerosoft A320 and the behavior is slightly different. P3d is loading to the scenario screen by default. I can select the A320 there and load a flight without issue. I can also load the default F22 flight, then select the A320 without issue. But going from the loaded A320 to the New Scenerio window or to the Change Vehicle causes the Child Window Error.

[Kayla Dillon]

Hello all,

Is anyone able to reproduce this crash with the default F-35?

Regards,
Kayla

[MartinP3Duser]

My experience:
P3D: no problem
P3D+ASN: no problem
P3D+PMDG: errors

[Livingston]

After uninstall v3.4 (full) and install v3.4 full and hotfix 1 2 3, P3d works fine (no addon installed).
After Install just one addon VRS A/C (tacpack + SB), P3d doesn't work anymore (error child window).
Maybe somethinjg to do with the management of addons ?
Hope that helps

[BoeingG]

Hello all,

Is anyone able to reproduce this crash with the default F-35?

Regards,
Kayla

Yes ma’am.