I have a pretty high end system, with windows 10, and about a week or so ago the above error message appeared everytime I clicked on a guage or function in an fsx steam edition flight.  Everything freezes after that. 

If I don't touch anything I can continue flying!  No problem with flight sim world.  There is some mention about a windows update that may have caused this problem but nothing definitive.

Would appreciate any advice that might be out there.

Richard

Well how about that. I was just looking around the forums and I saw your post here.  I have been having the same problem lately and I might say it is annoying. It would sure be nice if anyone had a fix.

We'll have to wait and see Clayton.  Still I'm glad you are having similar problems; if you know what I mean

Now that you have mentioned the windows update it makes a lot of sense. I didn't even consider that but it may be the case. Maybe it will get fixed soon.

Guy's, the above may enlighten you (It's not just PMDG Aircraft).

My biggest problem is in fact with the PMDG 747. I hope this can get fixed soon.

I also had this error - after installing the W10 Creators update - for FSLabs A320, PMDG 737NGX and PMDG 744 (interestingly the MD11 and 777 were not affected) and each time had a CTD with that error message when loading any one of these airplanes.

Without me doing anything else than re-starting FSX several times, that error disappeared on its own and I made since several flights with each of these aircraft without any issues at all. 

I made sure I had the latest Nvidia graphics drivers and Windows update released after the so-called "Creators" version. 

Since I own a number of sceneries linked to FSDT scenery manager plus GSX, I ensured that all FSDT updates were downloaded and properly installed.

Good luck!

3 hours ago, ClaytonYosten said:

My biggest problem is in fact with the PMDG 747. I hope this can get fixed soon.

To blame PMDG for an Windows Update is wrong.  Microsoft has admitted they screwed up and will issue a fix soon.  You can also to to Windows Update and click on Recovery and go back to the previous version until Microsoft can provide a fix.

Hi all,

Go Back to a prious version is no option if the upgrade is more than 10 days ago. It's a blame on the MicroSOF update policy and and the time needed for a correction. 
FSX - error: creating childwindow
Prepar3dV4; Creating childwindow
Prepar3dV4 and FSL A320; NTDLL.DLL fail

For me a very good reason to say goodbay MicroSOF and make the change to X-PLANE 11 on my iMac
I spent a lot of money on all the MicroSOF stuff so i can put it through the drain :-((

Regards
Jo va Bra

1 hour ago, Jim Young said:

To blame PMDG for an Windows Update is wrong.  Microsoft has admitted they screwed up and will issue a fix soon.  You can also to to Windows Update and click on Recovery and go back to the previous version until Microsoft can provide a fix.

Hi Jim,  sorry if it sounded like I was blaming PMDG. I know it was Microsoft's problem. 

 

By the way, thanks for telling about the recovery. I didn't know it was possible. 

 

Edit: Apparently you can't backtrack. 

I just updated on Nov 22d so can roll back and then set my update settings to a "metered connection".   That way Windows Update won't reinstall the update immediately (this 'trick' may change soon as Microsoft looks for tricks people play on them and removes that trick). If longer than 10 days, you can try reinstalling Windows or making sure you a full backup of Windows before installing a Windows Update and restore the backup.  I personally am not going to roll back to a previous version as my P3DV4.1 works without any issues and I have had errors with FSX but only the unsupported operation error.  Only saw the creating child window once in FSX.

1 hour ago, Jim Young said:

I just updated on Nov 22d so can roll back and then set my update settings to a "metered connection".   That way Windows Update won't reinstall the update immediately (this 'trick' may change soon as Microsoft looks for tricks people play on them and removes that trick). If longer than 10 days, you can try reinstalling Windows or making sure you a full backup of Windows before installing a Windows Update and restore the backup.  I personally am not going to roll back to a previous version as my P3DV4.1 works without any issues and I have had errors with FSX but only the unsupported operation error.  Only saw the creating child window once in FSX.

It has been less than 10 days so I'll try that out when I get back home. Thanks for the help!

I had the same problem with this error window in P3D 3.4. It was happening when I used "Shift +" to open up a pop up windows or Shift + E for entry door.

I was fortunate enough to learn about "rolling back" to the previous windows build. I believe there was an update 11-25-17 tripping this error. Once I did the recovery, no more error.

I wish our flight sim environments were compatible with Linux OS as I am also getting very tired of dealing with "MicroSOF" as noted earlier. For now, I have disabled the update function. Don't really like doing so but I am tired of trying to find "work around" solutions to what the updates do to mess things up in my flightsim.

3 hours ago, raymie said:

I had the same problem with this error window in P3D 3.4. It was happening when I used "Shift +" to open up a pop up windows or Shift + E for entry door.

I was fortunate enough to learn about "rolling back" to the previous windows build. I believe there was an update 11-25-17 tripping this error. Once I did the recovery, no more error.

I wish our flight sim environments were compatible with Linux OS as I am also getting very tired of dealing with "MicroSOF" as noted earlier. For now, I have disabled the update function. Don't really like doing so but I am tired of trying to find "work around" solutions to what the updates do to mess things up in my flightsim.

It is truly frustrating. Hopefully Microsoft can find a way to not mess things up more. They might be digging a hole they can't get out of.

Clay

16 hours ago, Jim Young said:

I just updated on Nov 22d so can roll back and then set my update settings to a "metered connection".   That way Windows Update won't reinstall the update immediately (this 'trick' may change soon as Microsoft looks for tricks people play on them and removes that trick). If longer than 10 days, you can try reinstalling Windows or making sure you a full backup of Windows before installing a Windows Update and restore the backup.  I personally am not going to roll back to a previous version as my P3DV4.1 works without any issues and I have had errors with FSX but only the unsupported operation error.  Only saw the creating child window once in FSX.

Thanks for the help again. I rolled back and all of the problems went away. Everything is working just like it's supposed to.

Clay