Win 10 KB4038788 Update crashes my P3D v3

[Rob McCarthy]

Microsoft is still actively investigating this issue and we are working closely with their developer support team. The crash tends to only happen when loading more complex aircraft which is why you won't see it in most default aircraft or many freeware planes. I want to thank everyone again for their patience and also want to thank the users who have been able to find workarounds and help others until the problem is resolved.

Regards,
Rob McCarthy

[Tregarth]

To prevent KB4038788 installing on my FS PC I have checked the update list to verify it was not there. It wasn't. I then went into "Stop Auto Updating" and turned it off, closed and restarted the PC.

I have re-activated my copy of P3Dv3.4 which is now running OK with the IRIS Texan Driver (the FSX version which I manually installed into P3D) at ORBX Southampton airport. But when I closed the PC it said I had to wait for an update to install. After the PC had closed and restarted I checked the update and found KB4038788 had installed, despite Auto Updates being turned off.

So turning off Auto Update might not give the protection expected. This concerns me since he Win10 Fall Update is not very far away so I may find the problem update has been bundled into the Fall update and I will find out the hard way.

[McFriday78]

At the moment, I only can use P3Dv4 when running it in Windows 8 compatibility mode.
The sim would take forever to load (like 10-15 minutes), but I am able to fly.

When running it without Windows 8 compatibility, it still crashes upon loading ANY flight - ANY scenery, ANY aircraft, no matter if it's freeware, payware or default aircrafts.
When I load the flight, it would crash immediately with an ntdll.dll error (I do not even get the loading bar). Debugging the crash dump in visual studio shows it has something to do with corrupt heaps.

It is like that since KB4038788 was deployed - this update altered ntdll.dll in C:\windows\system32
Uninstalling the patch did not help - the ntdll.dll version stayed the same.

I temporarily tried to replace the ntdll.dll with a previous version (while having installed the patch).
P3Dv4 worked fine, but it would crash my system with a couple of bluescreens, requiring Windows to repair the whole system upon bootup, everything was just unstable, so I had to discard these changes. I hoped this would be a great workaround, but I was wrong.
Well - hope there will be a fix soon :)

[corvettepilot]

Microsoft is still actively investigating this issue and we are working closely with their developer support team. The crash tends to only happen when loading more complex aircraft which is why you won't see it in most default aircraft or many freeware planes. I want to thank everyone again for their patience and also want to thank the users who have been able to find workarounds and help others until the problem is resolved.

Regards,
Rob McCarthy

Load the default F-22 and select any payware scenery and it will crash.

[delfin8896]

The workaround is to uninstall KB4038788 and block it from installing again. As uninstalling results in a state without any security updates you have to install the latest before KB4038788. It was KB4034674 as mentioned before. To block KB4038788 I used this tool https://www.oo-software.com/en/shutup10 blocking Windows 10 Auto-Updates. I have done this successfully on two machines.

[gianfranco19]

Microsoft is still actively investigating this issue and we are working closely with their developer support team. The crash tends to only happen when loading more complex aircraft which is why you won't see it in most default aircraft or many freeware planes. I want to thank everyone again for their patience and also want to thank the users who have been able to find workarounds and help others until the problem is resolved.

Regards,
Rob McCarthy

Hi Rob,
no entirely true. Load default scenario with default vehicle and it crashes. This happens at second flight. After clean installation, no addons installed, P3d v3.4 loads ok. Close the flight and start it again and it crashes. I repeat, clean installation and no addons installed.
Gianfranco

[fsfan]

[that is my question, which I can't find out. How can I disable the Windows Update Service in Windows 10. I can't find it, even with Windows support. Several times I uninstalled KB4038788 and it comes back every time.]

Hello everybody,

I did experience similar results with the latest MS Win10 KB4038788 update. Also uninstalling that update and disabling the Windows Update service makes it WORK again.

I experienced this crash like 10 times out of 10 with the PMDG NGX 737-600 v1.20.8413, the NGX 737-8900 (base pack) crashed like 5 times out of 10. The default A/C work just fine. The scenery did not matter.

Faulting application name: Prepar3D.exe, version: 3.4.9.18400, time stamp: 0x57d9b14e
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000cdd00
Faulting process id: 0x980
Faulting application start time: 0x01d32fe060c0fcec
Faulting application path: K:\Lockheed Martin\Prepar3D v3\Prepar3D.exe
Faulting module path: unknown
Report Id: 7a68c54c-87ac-48c0-a5f0-bb66011ced0b
Faulting package full name:
Faulting package-relative application ID:

Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 000CDD00
Stack:
at MS.Win32.UnsafeNativeMethods.IntGetMessageW(System.Windows.Interop.MSG ByRef, System.Runtime.InteropServices.HandleRef, Int32, Int32)
at MS.Win32.UnsafeNativeMethods.GetMessageW(System.Windows.Interop.MSG ByRef, System.Runtime.InteropServices.HandleRef, Int32, Int32)
at System.Windows.Threading.Dispatcher.GetMessage(System.Windows.Interop.MSG ByRef, IntPtr, Int32, Int32)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at Views.AlertBox.P3DAlertBox.ProcessPendingWorkItems()
at Views.AlertBox.P3DAlertBox.OnProgressPercentChanged(System.Object)
at MenuModels.AlertBox.AlertData.set_ProgressCurrent(Double)
at <Module>.P3DAlert.SetCurrent(P3DAlert*, Int32)
at <Module>.P3DAlertSystem.UpdateModeless(Void*, Int32)

I run P3D v3.4.9.18400
Win 10 Home 64bit v1703

Regards,
[/quote]

[CaptainBen]

Hey,
Today I installed the new Windows 10 update (KB4040724), and the flight sim still crashes with the same error :(

Prepar3D.exe
3.4.14.18870
581239e2
unknown
0.0.0.0
00000000
c000041d
07f4dd09
193c
01d33e810bc72ea7
C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
unknown
7ce8ea0c-4efa-4397-8785-5faf42830158

[Robau]

This has developed into a Major problem for us P3D users, let's hope a fix comes soon.

[McFriday78]

At the moment, I only can use P3Dv4 when running it in Windows 8 compatibility mode.
The sim would take forever to load (like 10-15 minutes), but I am able to fly.

When running it without Windows 8 compatibility, it still crashes upon loading ANY flight - ANY scenery, ANY aircraft, no matter if it's freeware, payware or default aircrafts.
When I load the flight, it would crash immediately with an ntdll.dll error (I do not even get the loading bar). Debugging the crash dump in visual studio shows it has something to do with corrupt heaps.

It is like that since KB4038788 was deployed - this update altered ntdll.dll in C:\windows\system32
Uninstalling the patch did not help - the ntdll.dll version stayed the same.

I temporarily tried to replace the ntdll.dll with a previous version (while having installed the patch).
P3Dv4 worked fine, but it would crash my system with a couple of bluescreens, requiring Windows to repair the whole system upon bootup, everything was just unstable, so I had to discard these changes. I hoped this would be a great workaround, but I was wrong.
Well - hope there will be a fix soon :)

Ok, this issue seems to be resolved for me. I changed the system locale to English (I'm running Windows 10 in German and had set the locale to German before). Fired up P3D, loaded a flight -> no problem. Double-checked it by switching back to German -> ntdll.dll crash, back to English -> works perfectly.

Strange thing is, that the problem occured after the Windows update, but at the moment I'm not really sure it has something to do with it. I'm confused, but happy I can use the sim again :)

[FlyboyNK]

Greetings,
I am using Win 10 and P3D v4, a few days ago I started getting a shutdown of P3D about 15 minutes into running the sim (on ground, in air and different airports) I uninstalled the latest addons I had. Same shut down. I decided to reinstall P3d v4 and I'm still getting these constant shut downs with no addons. Never had any issues with P3D any version until this week.

[w6kd]

Hey,
Today I installed the new Windows 10 update (KB4040724), and the flight sim still crashes with the same error :

Same here. The d***** auto-update installed 4040724, and that broke P3Dv3 (3.4.22). I uninstalled that one and used the M$ "Show or hide updates" troubleshooter to hide that update, at which time WIndows Update auto-installed 4038788, which broke P3Dv3 again. I uninstalled that, and Windows promptly reinstalled it at the next boot, and the show/hide troubleshooter would not even list 4038788, much less allow me to hide it. So I uninstalled 4038788 again after using the OO-Shutup utility mentioned above to stop all Windows auto-updating (for the time being at least).

This is maddening. I may have to go back to my i7-4790K with Win7, since my Z270/7700K does not have driver support for Win7. This represents a critical reliability challenge for this platform going forward...who really wants to depend on a training system that MS can repeatedly force its way into and break?? There needs to be a solution, not just for the current problem, but to ensure that some future MS update doesn't force its way in and do the same thing all over again.

Regards

Bob Scott
Col, USAF (ret)

[delfin8896]

Hey,
Today I installed the new Windows 10 update (KB4040724), and the flight sim still crashes with the same error :

Same here. The d***** auto-update installed 4040724, and that broke P3Dv3 (3.4.22). I uninstalled that one and used the M$ "Show or hide updates" troubleshooter to hide that update, at which time WIndows Update auto-installed 4038788, which broke P3Dv3 again. I uninstalled that, and Windows promptly reinstalled it at the next boot, and the show/hide troubleshooter would not even list 4038788, much less allow me to hide it. So I uninstalled 4038788 again after using the OO-Shutup utility mentioned above to stop all Windows auto-updating (for the time being at least).

This is maddening. I may have to go back to my i7-4790K with Win7, since my Z270/7700K does not have driver support for Win7. This represents a critical reliability challenge for this platform going forward...who really wants to depend on a training system that MS can repeatedly force its way into and break?? There needs to be a solution, not just for the current problem, but to ensure that some future MS update doesn't force its way in and do the same thing all over again.

Regards

Bob Scott
Col, USAF (ret)

You are absolutely right here Bob. The user should have full control over his own machine. But this is gone with Windows 10!

73 de Detlef

[RossG]

First thing I want to say about my post is use at your own risk.

Now, the way I fixed this in Windows 10 is I actually turned OFF the windows 10 update service. You will not be able to get any updates of any kind while this is disabled but you can then remove the offending update and it will not come back.

One the issue is fixed with Microsoft you will need to re-enable the service to get any new updates you have missed.

This is not the best solution but it is one that works and I have not had a problem since doing this. You may want to book mark the page below if you do this so you will remember what to turn back on once the problem has been corrected with Microsoft.

Go here: http://www.thewindowsclub.com/turn-off- ... windows-10

[Robau]

Well another week gone by and still have to do a work around to fly my favorite, the PMDG B737-800.
I would like to purchase their B777 but unfortunately, not till this is all finished with.

Is it possible to have v3 and v4 working properly before V4.1 is released in a few days and is 4.1 not going to have the same problem, if it does not have this update problem I will buy it and carry on happy flying.

My work around with v3 at present to fly my B737 is to select any freeware FSX or P3D aircraft, if you don't have one then download one, any aircraft will do.

Next select your departure airport and gate, weather, time of day etc.
Press the okay button and let the sim load up with your selection.

Once all that is on your screen, go to the top menu bar, press vehicle and select the actual aircraft you wish to fly.
The sim will reload and your selected aircraft will appear at the gate.

There are no guarantees but this works on my rig every time with no CTD.