Author Topic: Prepar3D "Windows Fix KB4048955" installed  (Read 123 times)

Doug

  • Misty Moorings Site Admin
  • Hero Member
  • *
  • Posts: 3,018
    • View Profile
    • Return to Misty Moorings
Prepar3D "Windows Fix KB4048955" installed
« on: November 14, 2017, 02:04:34 PM »
Per my News Notam:

New Win 10 Update released 1:26pm 11.14.2014
Update KB4048955

Good News:  This is the update we've been waiting for. Prepar3d V3.5 now starts up without a CTD, and is fly-able.

Bad News: There is a new error (Error creating Child Window ... attached).  Not sure what that error means yet. Another MAJOR problem is when you initiate IS3 (Instant Scenery 3), the whole thing crashes to desktop. I've got a trouble ticket in to Flight1 on this problem.

Bottom line ... we are not "back in business" yet with Scenery development and re-configuration for V4.1.  Sorry, we just have to wait until THEY get THEIR ducks in a row! I'll keep you posted.

I thought I would make a thread on this so you can add any information you come across on this subject.

Doug

Update: Re-Installing Instant Scenery 3 does not fix the problem. It begins to loading process for IS3, then just quits. Windows event log says faulting app is P3D, faulting path is MSVCR120.dll. 
« Last Edit: November 14, 2017, 03:29:41 PM by Doug »

corbu1

  • RTMM Team Test Pilot
  • Hero Member
  • *
  • Posts: 1,654
    • View Profile
Re: Prepar3D "Windows Fix KB4048955" installed
« Reply #1 on: November 14, 2017, 03:24:53 PM »
Some users already posted the issue (error creating child window) on the LM P3d forums.
Some got a ctd with it others were able to fly ....

Anyway it seems MS did not solve the problem.....
Regards from Munich, Germany



P3Dv4.1,FlyInsideP3d4,OpusFSI,REX4
i76700K 4Ghz;16GB RAM;Asus 2xGTX1080 SLI;SSD:Evo850 256GB Win10Pro64;Evo850 512GB P3D;HDD:1TB;27" Monitor;HTC Vive HMD;HOTAS Warthog;X52;VBS ProAT Pedals;iGMapHD;F1GTN750/650

Doug

  • Misty Moorings Site Admin
  • Hero Member
  • *
  • Posts: 3,018
    • View Profile
    • Return to Misty Moorings
Re: Prepar3D "Windows Fix KB4048955" installed
« Reply #2 on: November 14, 2017, 03:28:12 PM »
Thank you ... my sound did come back on, so that works now (3 restarts), but the child window error is still there. Where I saw someone talking about it, it had to do with the joystick. Mine works fine, no problems. The only problem I seem to have is the IS3 won't work.

jeff3163

  • Misty Moorings Team
  • Hero Member
  • *
  • Posts: 3,079
  • Troubleshooting & Help
    • View Profile
Re: Prepar3D "Windows Fix KB4048955" installed
« Reply #3 on: November 14, 2017, 08:08:59 PM »
It strikes me as funny that people thought M$oft would fix it.   ;D    ...  :-\  ...   :(  ...   >:(  ...   :'(

Win10Pro64, P3Dv4.1.7.22841, AMD Ryzen7 1800X@4.0 GHz , 32Gb RAM, NVidia GTX 1080 Ti, 1T/1T SSD's for Sims/OS, 3x42" Vizio Monitors, HTC Vive VR HMD, Saitek Yoke/Pedals/trim wheel, XBox360 Controller, G27 steering wheel w/shifter+pedals. :P

Doug

  • Misty Moorings Site Admin
  • Hero Member
  • *
  • Posts: 3,018
    • View Profile
    • Return to Misty Moorings
Re: Prepar3D "Windows Fix KB4048955" installed
« Reply #4 on: November 14, 2017, 09:06:15 PM »
Well it fixed the P3D V3.4 ... still is not working correctly, and IS3 sure isn't right yet. Can't figure out why it didn't fix "both" ... I'm waiting for others to discuss it on the forums. V3.4 will be giving you "Child Window" errors.  These happen when you try to save a scenario or a flight plan, etc. So something is still wrong. This new update didn't fix it.
« Last Edit: November 17, 2017, 05:20:33 PM by Doug »

Doug

  • Misty Moorings Site Admin
  • Hero Member
  • *
  • Posts: 3,018
    • View Profile
    • Return to Misty Moorings
Re: Prepar3D "Windows Fix KB4048955" installed
« Reply #5 on: November 17, 2017, 05:18:58 PM »
There is some GOOD new information here if you are having the "Child Window" problem with P3D V3.4.  It's not us, Windows has struck again:

https://www.avsim.com/forums/topic/524385-cannot-create-child-window/?_fromLogin=1

https://www.avsim.com/forums/topic/524283-fsx-se-no-longer-compatible-with-windows-10/

If anyone is interested, I have found a way to use IS3 (barely) with V3.4 (until they have a fix of some kind). It is clunky, but it works. Let me know if you want it.

rgerdes

  • Jr. Member
  • **
  • Posts: 78
    • View Profile
Re: Prepar3D "Windows Fix KB4048955" installed
« Reply #6 on: November 17, 2017, 08:07:58 PM »
Think I'll wait for the 64 bit version  :)
I'm in the process of recovering from a ssd crash that completely wiped me out..
So far I have installed p3d4.1 Tongass,  SAK, Juneau and HD trees.
Oh and the PTA for 4.1 and Adams preset.
 Going to let it sit for awhile before I tackle any more - what a pain; this "hobby" is starting to wear thin....
Bob

Doug

  • Misty Moorings Site Admin
  • Hero Member
  • *
  • Posts: 3,018
    • View Profile
    • Return to Misty Moorings
Re: Prepar3D "Windows Fix KB4048955" installed
« Reply #7 on: November 17, 2017, 08:12:46 PM »
I'm feeling the same way. Every time I turn a corner, something different. In 4.1, no wheels on the cars at Misty's Place tonight ... I just put that rascal up there today ... oh well, that's why they call them UPdates! Going to put another one up tomorrow when I figure it out. 

But we darned sure didn't need this windows problem. Dieter just warned me that supposedly there is another "Fall" update coming from Windows that could knock out 4.0 .. Maybe its time to turn of the automatic windows updates! 

I figured it was Windows, I did everything I could here ... and everything was working FINE before that first update. This latest let us turn 3.4 back on, but it is really screwed up.  If they screw up "4" ... then we should all go back to FS2000 and fly SIRP! :-)  I could always crank up the old MistyMoorings site.

UPDATE: I found the wheels ... you can get a great deal on new tires to replace the missing ones by going to the RTMM FAQ page and looking under "V" (Vehicles) ... the fix is there for you. (Rod reminded me).
« Last Edit: November 17, 2017, 08:32:52 PM by Doug »