12 Dec 2017 Win 10 Update experiences?

[Bob Scott 7,715]

Rob McCarthy at Lockheed Martin is reporting that the 12 Dec 17 update (KB4054517) to Win 10 version 1709 (Fall Creator's Edition) has finally solved the "Error creating child window" problem on 32-bit versions of P3D running under Win 10 64.

Any other experiences (good or bad) after installing this update?  Are FSX, FSX-SE, and/or P3Dv3 working again after several months of butt pain surrounding these errant Win 10 updates?

Inquiring minds want to know...

Regards

[Jim Young 2,356]

I downloaded and installed this afternoon and immediately ran a flight in the PMDG737 from FSDT KLAX to FB KSFO.  Previously, I got an almost immediate creating child window crash while the 737 was loading.  If not, I clicked on the FMC and it was an immediate crash.  I had also a message in the 737 FMC that the Nav data was out of date.  Well, today, all of these issues went away with the update. I tried my hardest to create a crash by clicking on the menu items and the 737 FMC and other things that caused the crash 100 % of the time but could not get it to crash.  I did note a couple of anomalies during the flight in that a couple of times the sim appeared to be crashing, went white, and froze with the rotating icon and then suddenly, in seconds, continued with the flight.  It was like Windows 10 was accessing the freeze, found a solution, and fixed it so the sim could still continue on its flight.  I do not recall ever seeing this before.  I always got the rotating icon, the screen went white, and then crashed with the ntdll.dll as the faulting module.  So happy to see this update.  Hopefully they will not break it again.

Best regards,

Jim

[webranger 186]

Great to hear!

[Bob Scott 7,715]

1 hour ago, Jim Young said:

I downloaded and installed this afternoon and immediately ran a flight in the PMDG737 from FSDT KLAX to FB KSFO.  Previously, I got an almost immediate creating child window crash while the 737 was loading.  If not, I clicked on the FMC and it was an immediate crash.  I had also a message in the 737 FMC that the Nav data was out of date.  Well, today, all of these issues went away with the update. I tried my hardest to create a crash by clicking on the menu items and the 737 FMC and other things that caused the crash 100 % of the time but could not get it to crash.  I did note a couple of anomalies during the flight in that a couple of times the sim appeared to be crashing, went white, and froze with the rotating icon and then suddenly, in seconds, continued with the flight.  It was like Windows 10 was accessing the freeze, found a solution, and fixed it so the sim could still continue on its flight.  I do not recall ever seeing this before.  I always got the rotating icon, the screen went white, and then crashed with the ntdll.dll as the faulting module.  So happy to see this update.  Hopefully they will not break it again.

Best regards,

Jim

Was this using P3Dv3, FSX, or FSX-SE?

 

[dgraham1284 92]

Just fine here. P3D 4.1

[Jim Young 2,356]

9 hours ago, w6kd said:

Was this using P3Dv3, FSX, or FSX-SE?

 

FSX (boxed). 

 

[spearmint_flyer 579]

Working great. Took P3Dv3 out to fly on the Level D 767 and CS757 and the child window error is now gone. 

[MDFlier 2,031]

Working fine for me. FSX-SE

[raymie 81]

The comments posted here seem to be very positive so far regarding the latest MS OS update. I too experienced the "Child Window" error via version 1709 update. For that reason, I rolled back to Win 10 version 1703 and disabled the update function. Because of that, I was able to enjoy a stable P3D version 3.xx sim experience.

I am still somewhat "Gun shy" to enable the update function and let this latest MS update install. I may wait for a while and monitor this topic for further "reassuring" comments noting this latest MS update is user friendly for us who still sim in the 32 bit environment. 

[JamesVic 0]

I'm running FSX boxed with 1709 update and all seems well with one exception - feel there/wilco ERJ145.  FPS around 5 to 10 while PMDG/A2A planes run no problem 20 plus.  I recognize the 145 is old and support is long gone but just thought I'd throw this issue out to masses in case anyone has any thoughts/experience.

thanks