Damn you Microsoft!

Too little, too late for me. Yesterday I decided to bite the bullet and reload my PC with an Acronis backup image I took at the end of September with 1703 on it. Before I reconnect ths PC to the network, I disabled Windows updates. Still recovering my system for changes I'd made since the backup, but that's it for me. No more Windows 10 updates.
 
Good news.

It seems that the 2017-12 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4054517) that was released today, has fixed the 'error creating child window' problem an subsequent crash of FSX.

(Confirmed by others elsewhere as well!)

Cheers

Paul
 
Except that the damned thing refuses to install, third time trying and counting.

Jesus Christ MS, get your #### together.

There's also no mention of the problem on the release notes.
 
​With update 4054517 and the JustFlight Turbo Arrow, I have mixed results so far.


Upsaide: Loading the aircraft doesn't crash FSX anymore.


Downside: Calling up the 2D panel windows freezes FSX or at least makes it respond VERY slowly.


- Edit:

False alert. It was an aircraft problem. Deactivating Compatibility Mode for fsx.exe solved the freezing issue and the Turbo Arrow works just fine now! So yes, the update fixes FSX!
 
By Jove - it seems fixed. Did much in the way of plane hopping and inside outside pfaffing about also calling up 2D panels etc.... no crashes. Well done MS it only took 2 months or so to sort it out. :biggrin-new:
 
I have had failed update installs for the past week or so. 88% and then "ERROR"(After 1:30hrs. Darn Update assistant. I keep uninstalling the darn thing so it does not hog my resources.

Maybe I will give today's update one more chance.
 
Any idea how long it takes for MS to slipstream this update into the official ISO? Looks like I'll have to install windows again.

"We couldn't complete the updates. undoing changes."

Fantastic.
 
Just for the record, after trying to fix windows update in every conceivable way, I updated through the media creation tool and all is fine.

Had to clean the ssd afterwards though, as the windows.old folder was taking 25gb while being useless.
 
Well, gave it another try last night.......

1:30hr and at 88% installed, and..... "AN Error occurred". I am done wit these updates.
 
Well, the update worked ok in here and since that, no more "child window" error for me. I think it´s perfect now. (win10 64bits 1709)
 
You must log in or register to reply here.
Back
Top