• Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning old domain name stealing credentials

  • Special Server Maintenance

    Just when you think you have everything running some what better...

    You get a message from the Hosting company. Short story they need to move us to a new server. I have been working with them to plan a good date for all concerned. Here is what we have come up with as a schedule.

    1. November 4th 17:00 -5UTC shut off the forums and start backup proceedures. During this time there will be no access to the forums or the Resource Section.
    2. November 5th Continue with Backups and download same until complete.
    3. November 6th 7:00 turn over server to hosting company to move system to new server
    4. November 7th - 8th restore backups and upgrade forum software.

    If all goes well we should be back online on November 8th.

    To keep you updated we will post updates on AVSIM forums.

    Thank you for your support.

Damn you Microsoft!

A thread about the issue at Avsim mentioned that PMDG communicated the error to Microsoft and that the Windows team is working on an update with an ETA before December.
Can't find the source in the PMDG forums, so don't quote me on it.
 
Take a look here: https://www.avsim.com/forums/topic/...d-windows-10-fall-creators-update-build-1709/. Despite what PMDG are saying about it being "wholly a Microsoft/Windows issue", most people who've updated to the Fall Creators Update don't seem to be having this problem. The majority of users (all?) who have the problem seem to have PMDG aircraft installed. One work around which appeared to be successful for some was to load a flight with a default aircraft and then load the aircraft you actually want and the problem seemed to go away. There have also been reports that this problem affects A2A aircraft as well but they seem to work fine for me after the 1709 update.
 
I'm going backwards. FS9 works great & looks great (with many addons), doesn't have this child window issue and all my Saitek panels work with it. This is not something that can be said of P3Dv4, So, I have all this equipment which is now redundant. It's not even that pretty to look at imo. FSXSE crashes if I so much as look at it presently. I am at breaking point. :pop4:
 
I allowed Win 10 to update at the W/E and I have no problems in FSX-SE or FSW.

Naismith: Perhaps a re-install of SE unless you've already done it.
 
My system updated this afternoon. I've never had a screen/system freeze since I built this box. Since update, I've had three. All while doing Megascenery installs. The freezes each occurred about 15 minutes after booting. I rolled my system back to before the update, and no freezes since. Was able to finish installing the Megascenery, and do some other stuff, without a screen freeze.


My notebook warned me about the update being ready to install, and I said "no." Rescheduled for 2 weeks from now.
 
rcbarend said:
From the "horses mouth":

https://support.microsoft.com/en-us...ll-creators-update-calls-createwindowex-for-s

Allthough FSX isn't mentioned specifically, at least now a statement from MS that it IS a problem caused by the Fall Creators Update (1709).

Rob
Click to expand...

Thanks for that Rob.

At least the issue has now been acknowledged by MS.

I had contacted Dovetail support who are aware of the child window issue, and they have been in contact with MS about the problem.

So hopefully a fix will be issued in a forthcoming Windows update.

Cheers

Paul
 
I have found through much searching a semi solution. By that I mean 90% of the time it seems to work OK but will crash upon selecting end flight. It does still manage (in my case) to log any flight made. Occasionally it will still crash upon requesting a 2D pop up still but it is rarer and seems restricted to long flights, which for me would be over 400 miles in a twin prop for example.

Anyway it is a simple as Setting compatibility to W7 and running as admininstrator.

There was a big MS update Tues p.m. but alas the fix was not included...... perhaps next week :a1310:
 
directx may be the problem

win 10 doesnt seem to like directx'that i have noticed
if thats the problem?:banghead:h
 
I've reinstalled the DirectX package included in the FSXSE folder (_CommonRedist\DirectX\Jun2010) after receiving the "child window" error once and no matter how many menus or windows I've opened since (a whole damn lot), I've yet to see that message again.
Not that this is a definite fix, but it might be worth a shot, especially for those getting the error more often. (Don't forget to report back whether it has helped or not.)
 
I have installed W10 3times now and when i insert the FSX disc,the install shield wizzard comes up,i can select the path to where install FSX.
Then it hangs and i get the error 1603.
The latest Update is installed.
Where can i find Version 1703?
Game over
 
Microsoft-Windows-10.jpg
 
big-mike said:
I have installed W10 3times now and when i insert the FSX disc,the install shield wizzard comes up,i can select the path to where install FSX.
Then it hangs and i get the error 1603.
The latest Update is installed.
Where can i find Version 1703?
Game over
Click to expand...

Tried this?

https://answers.microsoft.com/de-de...ler-1603/70388717-d7ea-43d0-8f7f-238e08ff0670

Or google: https://www.google.de/search?q=fsx+1603+fehler

There are also ISOs for 1703 out there, from which you can install from:
http://windowsiso.net/windows-10-is...0-creators-update-1703-iso-download-standard/
 
Bjoern said:
This brand new update is supposed to fix the error:
https://support.microsoft.com/en-us/help/4051963/windows-10-update-kb4051963
Click to expand...

Not this update sadly Bjoern!

Those affected will have to wait a little longer by the looks of things.

I had re-ran the DX package that came with FSX SE on my old Windows 10 1709 installation (via windows update), and for me it didn't cure the issue.

(But glad it worked for you!)

I'm now running a fresh install of 1709, but still having the same problem.

Interesting how some people seem to be running the 1709 build of Win 10 and FSX/ FSX SE with no problems, whilst others aren't!

Cheers

Paul
 
Yip! still getting the error. One positive though, at least the sim crashes this way long before I run out of VRAM. :biggrin-new:
 
Well, my good luck finally ran out. Quite possibly it was my fault, but my computer "bricked" last night. I was updating WIN 10 to 1709. After a couple hours, following several re-boots in the process, my monitor's screen was black, unchanging for over a half hour. I rebooted. Would go to the "Welcome" screen, and then nothing. Black screen again.

I tried using my Win 10 recovery disc, but Win 10 would not boot successfully.

Dead 'puter.

Took it to repair shop this morning. Thank goodness for my external drives and online email receipts for payware, eh?

By coincidence, I had ordered 2 500gb SSDs a couple days ago. The SSDs currently installed are almost four years old. I figured it was just a matter of time, but I hadn't planned on changing them this quick. Stuff happens, eh?

Also bought a two TB external drive. When I get my system back in about a week, I am hoping things will work a helluva lot better!

NC
 
Well, Chief, your brick...errr...computer, yeah, computer can't work a whole lot worse!
If it works at all, in any way, shape, or form, it's working better :encouragement:

Let's see, 2 500Gb SSD's, and a 2Tb external. Yup almost enough for the sim, all the add-on planes, scenery, etc.
No matter how much storage you've, it seems to expand to fill it up eventually. I think it's the Unwritten Law of the Simulator. Maybe it's written some place. I dunno. Still...

I wish you good luck, and good fortune!
Have fun
Pat☺
 
You must log in or register to reply here.
Back
Top