Hebeoy wrote: ↑Wed Nov 15, 2017 7:17 pm
It was never a problem with 1703. The problem began with 1709 Creator and for at least 14 days we have all been waiting for the fix update from MS around November 14th. This we were told in this thread.
Now we have to wait again for how long...........
I think there's some confusion - the issue for me was ever since the 1703 update around Sept. 1709 was the big Nov 14 update that was supposed to fix the CTD, which it did, but I guess introduced new issues.
Let me help you,
1703 had no issues with P3D/FSX (Most users said so) but I am seeing a few posts here claiming they had issues with 1703. (I had no problems with 1703 either)
1709 was the Fall Creator Update and almost everyone with P3D/FSX are claiming they had issues (Including myself)
1709 with Tuesday Patch KB4048955 - Did not fix the problems with 1709 but apparently fixed the problems with 1703 as per Kayla's post. So 1709 users still have to wait now the question is how long :(
Hebeoy wrote: ↑Wed Nov 15, 2017 7:17 pm
It was never a problem with 1703. The problem began with 1709 Creator and for at least 14 days we have all been waiting for the fix update from MS around November 14th. This we were told in this thread.
Now we have to wait again for how long...........
I think there's some confusion - the issue for me was ever since the 1703 update around Sept. 1709 was the big Nov 14 update that was supposed to fix the CTD, which it did, but I guess introduced new issues.
Let me help you,
1703 had no issues with P3D/FSX (Most users said so) but I am seeing a few posts here claiming they had issues with 1703. (I had no problems with 1703 either)
1709 was the Fall Creator Update and almost everyone with P3D/FSX are claiming they had issues (Including myself)
1709 with Tuesday Patch KB4048955 - Did not fix the problems with 1709 but apparently fixed the problems with 1703 as per Kayla's post. So 1709 users still have to wait now the question is how long :(
Okay, so it seems the confusion was mostly on my part then. I did a bit of googling to get it right, and I was mixing up "hotfixes" with "updates".
I thought 1709 was the promised fix from MS, as it did not show up in my updates until last night but its been out for a while now. I understand the CTD issue was introduced in a hotfix a sometime in Sept, but I thought that was 1703. Now that I have 1709, I don't get the CTD, but I do get the Child window issue, but only when accessing menu options.
Few months ago, when the all thing started, I wrote my disappointment in this forum because LM moderators were removing posts of mine because i complained, not offending or using bad language, about the fact that people like me are investing $$$ on this hobby and still not getting the attention deserved. Nevertheless, I waited, as most of us did, for this so-promised Nov 14 update though having the feeling that it was not resolving anything at all and more time would be needed to get to the bottom of this. Simply because LM is collecting information from many users and not testing themselves what the actual cause may be thus reporting it to MS. And we all know, all systems are not the same so one may experience issues different from others but having in common the crash.
Well, after all the money I invested in FS98, FS9, FSX and finally P3D, I think I am now ready to move to a different platform. Too many inconveniences for me to handle when the only thing I and everyone of us wishes is spending sometime in front of his/her own PC enjoying the SIM.
I am really sorry and mostly disappointed. I wish I could get my money back.
No confusion!
Win 10 v. 1703 is from april 2017. I had no problems with P3D v 3.4
Until
Win 10 v. 1709 is from october 2017. Here all the problems began: crashes and child window errors.
Many of us believed that the MS update 14th November would solve the problems.
Now we are told that this update only adresses the 1703 version for those users who apparently have had problems for a longer time than “only” one month.
Looking forward to a solution.
Luckily I am also a user of P3D v 4.1 which has no problems being 64 bit.
gianfranco19 wrote: ↑Wed Nov 15, 2017 10:25 pm
I am really sorry and mostly disappointed. I wish I could get my money back.
Gianfranco
I feel you man, I feel your pain. I am doing my A320 type rating in a real A320 aircraft and I need FSLabs A320X to help me with my training and prepare my mind for sessions in the real simulator. I have already paid for P3D , FSX SE and 108,899 USD for all my real world flight training so far.
I am just so lost now. I've spent almost two days look into issues how to fix my simulators I lost two days of my study time!
Looks like a quick downgrade to Windows 7 will do all of us the best.
Sorry to hear that.
For me downgrading to W7 is no longer an option. Too many things have happened since W10 release and I am sure eventually you must upgrade again. Honestly, I would not go to all the troubles of OS switching just for 1 software.
I hope you would get your course back on track. Have you tried X-plane11? Beside the limited number of addons available, it is totally a better and more immersive experience than what we had. Especially for a real pilot like yourself you will notice the difference. Much more realistic. I wish all the major software houses would start developing on it.
Cheers
Gianfranco
[/quote]
I feel you man, I feel your pain. I am doing my A320 type rating in a real A320 aircraft and I need FSLabs A320X to help me with my training and prepare my mind for sessions in the real simulator. I have already paid for P3D , FSX SE and 108,899 USD for all my real world flight training so far.
I am just so lost now. I've spent almost two days look into issues how to fix my simulators I lost two days of my study time!
Looks like a quick downgrade to Windows 7 will do all of us the best.
[/quote]
Kayla Kinzel wrote: ↑Wed Nov 15, 2017 6:41 pm
Hello all,
I reached out to Microsoft pertaining the issue.
It appears that as of right now, the fix was only applied for 1703 users. I will let everyone know when the fix for 1709 will be pushed out.
Thanks for all your help/feedback,
Kayla
Hi Kayla,
I don't think anyone actually had a problem with 1703. Personally 1703 and the earlier versions worked perfectly for me. 1709 was the main problem so I don't think Microsoft actually fixed anything.
So do we have to wait a whole month to get the next fix? That's too long! It's been 3 months now without P3D.
I understand and appericiate your team efforts and your efforts as well but for some of us we are really being patient but this is taking way too long :(
The problem started with update KB4038788 (build 1703). This is the build I'm still with (Win 10 pro 1703 OS build 15063.0) minus the update which I uninstalled to resolve the issue. This issue is clearly a result of a MS update. LM should not feel/be obligated to patch anything.
The easy fix? Microsoft should revert/remove ALL .NET patches since the plagued version (KB 4038788) was released then fix them completely before pushing their update/s out.
gianfranco19 wrote: ↑Wed Nov 15, 2017 10:25 pm
Few months ago, when the all thing started, I wrote my disappointment in this forum because LM moderators were removing posts of mine because i complained, not offending or using bad language, about the fact that people like me are investing $$$ on this hobby and still not getting the attention deserved. Nevertheless, I waited, as most of us did, for this so-promised Nov 14 update though having the feeling that it was not resolving anything at all and more time would be needed to get to the bottom of this. Simply because LM is collecting information from many users and not testing themselves what the actual cause may be thus reporting it to MS. And we all know, all systems are not the same so one may experience issues different from others but having in common the crash.
Well, after all the money I invested in FS98, FS9, FSX and finally P3D, I think I am now ready to move to a different platform. Too many inconveniences for me to handle when the only thing I and everyone of us wishes is spending sometime in front of his/her own PC enjoying the SIM.
I am really sorry and mostly disappointed. I wish I could get my money back.
I figured I'd have nothing to lose so thought I'd mess around a bit with the intention of eventually doing a clean reinstall under 1709 and see what happens.
First I uninstalled UT2 and all my Orbx scenery, leaving just my addon aircraft. After doing that, its been running fine with no Child Window errors. I just completed 2 short flights in both the 737NGX and Aerosoft A320, as well as messing around in the F22. No issues going in and out of windows or creating scenerios. I know that didn't seem to fix it for others, but it seems to have at least made it usable, other than my scenery textures look straight out a bad LSD trip.
