Windows 11 24H2 Update is corrupting P3D V5.4 and causing CTDs with the Aerosoft Airbus Pro Series

Question

Windows 11 24H2 Update is corrupting P3D V5.4 and causing CTDs with the Aerosoft Airbus Pro Series

Danny Evans 0

Hi There,

After updating Windows 11 to 24H2, I am unable to launch Prepar3d V5.4 when selecting Aerosoft Airbus pro series aircraft. The simulator experiences a CTD upon loading in. There is also nothing registered in the event viewer. It seems to be some issues with XML file reading and the kernel base from what I can tell.

The program was working fine with version 23H2, this issue only occurs in 24H2. From reports from other colleagues who are part of the Windows Insider program, 24H2 build 27774 and build 27788 via the Canary channel resolves this issue. I however cannot risk my computer and would prefer the fix be addressed via a stable build.

Link to another thread with no resolution yet from Microsoft:

https://learn.microsoft.com/en-us/answers/questions/3931737/windows-11-24h2-update-corrupting-p3d-v5-4-aerosof?page=2#answers

Any help would be greatly appreciated!

Ryan F 0 Reputation points

2026-01-23T19:37:44.6+00:00

Hello there,

With the release of 25H2, this issue still rears its ugly head and makes several Aerosoft products unusable. Other uses have rightly noted that some Canary builds appear to fix the issue stemming from the 24H2 build, however these fixes were not present in the 25H2 release. Is this something that will be fixed in an update in the not-too-distant-future for 25H2?
Clary-N 16,010 Reputation points Microsoft External Staff Moderator

2026-01-24T08:43:26.33+00:00

Hi Ryan F,

Based on how these changes are typically delivered, it’s expected to be addressed in a future 25H2 update, though there’s no confirmed timeline at this stage.

Since I'm just a forum moderator, I don’t have visibility into Microsoft’s release plans. I really appreciate your patience and encourage submitting feedback directly to Microsoft development team, as user reports help with prioritization.
Leslie Jarrett 0 Reputation points

2026-07-31T10:08:01.06+00:00

so much for Aerosoft and Microsoft according to Aerosoft adverts

"The project is a development for 64-bit platforms and uses the very latest of technology and compilers making it highly future proof and as light as possible on your system. It is not a recompiled 32-bit product." especially now it does not work on Windows 11 , that is hardly future proof then
Stephen Wagner 0 Reputation points

2026-09-12T23:58:08.75+00:00

I have the same problem of Aerosoft Airbus not running. I just purchased a new computer and it has Windows 11 (25H2.

My iFly 747 and FSCommander no longer work. But here is something that I have noticed.

If I load the Aerosoft Pro Airbus series into Prepar3d V4 on 25H2 they work flawlessly. They will not work in Prepar3d V5.

Put that in your hat and smoke it.

Don't kill the messenger. I'm just reporting what goes on my system. The whole thing is to get us to switch to MSFS. Can't do that. I have hundreds and hundreds of dollars invested in P3D aircraft, scenery and utilities. I went down the Microsoft flight simulator path before and got burnt. (FSX). Not again.
Clary-N 16,010 Reputation points Microsoft External Staff Moderator

2026-09-15T10:30:35.95+00:00

Hi Stephen,

Thanks for sharing what you found. I understand why switching to another simulator isn’t really an option after everything you’ve invested in your current setup.

Since the Aerosoft Airbus is working well with Prepar3D v4, I’d stick with that combination for now. For the programs that still don’t work with Prepar3D v5 on Windows 11 25H2, please report them through Feedback Hub by pressing Windows key + F. If you find an existing report for the same issue, add your feedback there as well.

I appreciate you sharing your findings. They may also help others running into the same problem.

2 answers

Your answer

Ryan F 0 Reputation points

2026-01-23T19:37:44.6+00:00

Hello there,

With the release of 25H2, this issue still rears its ugly head and makes several Aerosoft products unusable. Other uses have rightly noted that some Canary builds appear to fix the issue stemming from the 24H2 build, however these fixes were not present in the 25H2 release. Is this something that will be fixed in an update in the not-too-distant-future for 25H2?
Clary-N 16,010 Reputation points Microsoft External Staff Moderator

2026-01-24T08:43:26.33+00:00

Hi Ryan F,

Based on how these changes are typically delivered, it’s expected to be addressed in a future 25H2 update, though there’s no confirmed timeline at this stage.

Since I'm just a forum moderator, I don’t have visibility into Microsoft’s release plans. I really appreciate your patience and encourage submitting feedback directly to Microsoft development team, as user reports help with prioritization.
Leslie Jarrett 0 Reputation points

2026-07-31T10:08:01.06+00:00

so much for Aerosoft and Microsoft according to Aerosoft adverts

"The project is a development for 64-bit platforms and uses the very latest of technology and compilers making it highly future proof and as light as possible on your system. It is not a recompiled 32-bit product." especially now it does not work on Windows 11 , that is hardly future proof then
Stephen Wagner 0 Reputation points

2026-09-12T23:58:08.75+00:00

I have the same problem of Aerosoft Airbus not running. I just purchased a new computer and it has Windows 11 (25H2.

My iFly 747 and FSCommander no longer work. But here is something that I have noticed.

If I load the Aerosoft Pro Airbus series into Prepar3d V4 on 25H2 they work flawlessly. They will not work in Prepar3d V5.

Put that in your hat and smoke it.

Don't kill the messenger. I'm just reporting what goes on my system. The whole thing is to get us to switch to MSFS. Can't do that. I have hundreds and hundreds of dollars invested in P3D aircraft, scenery and utilities. I went down the Microsoft flight simulator path before and got burnt. (FSX). Not again.
Clary-N 16,010 Reputation points Microsoft External Staff Moderator

2026-09-15T10:30:35.95+00:00

Hi Stephen,

Thanks for sharing what you found. I understand why switching to another simulator isn’t really an option after everything you’ve invested in your current setup.

Since the Aerosoft Airbus is working well with Prepar3D v4, I’d stick with that combination for now. For the programs that still don’t work with Prepar3D v5 on Windows 11 25H2, please report them through Feedback Hub by pressing Windows key + F. If you find an existing report for the same issue, add your feedback there as well.

I appreciate you sharing your findings. They may also help others running into the same problem.

Answer 1

Domic Vo 33,190 Independent Advisor

Dear Danny Evans,

You've reported that after updating to Windows 11 version 24H2, Prepar3D v5.4 crashes to desktop (CTD) when loading Aerosoft Airbus Pro Series aircraft. The issue did not occur on version 23H2, and no errors are logged in Event Viewer. Based on your observations and community feedback, the problem may be related to XML file parsing and kernel base behavior introduced in 24H2.

The issue appears to be specific to the interaction between Prepar3D’s XML-based aircraft configuration and changes introduced in the 24H2 update.

Notably, users participating in the Windows Insider Canary channel have reported that builds 27774 and 27788 resolve the crash behavior.

Here are some interim steps you may consider:

Roll Back to Windows 11 Version 23H2 If stability is critical, reverting to 23H2 may restore full functionality until a fix is released in a stable build.

Reinstall Aerosoft Airbus Pro Series Some users have reported success by reinstalling the aircraft package after the OS update.

Monitor Insider Build Release Notes Keep an eye on Windows Insider release notes for confirmation of fixes being rolled into production builds.

Submit Feedback via Feedback Hub If you haven’t already, please submit a report through the Windows Feedback Hub under “Apps > Prepar3D” to help prioritize resolution.

I hope this helps. Just kindly tick Accept Answer that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

Best regards,

Domic Vo

Danny Evans 0 Reputation points

2025-08-23T02:55:19.34+00:00

Hi Domic,

Thanks for your reply I appreciate it, but as noted above by your colleague Clary, those replies were already suggested and I responded as to why it was not viable.

I will however submit the request via the windows feedback hub as you had suggested. In the meantime is there any other way to find out exactly how exactly the different versions windows are causing the XML/Kernel issue? I am hoping for a hotfix or an update that can fix this issue potentially.

At the very least is there any ETA on when those builds that resolve the issue will be released in a stable update?
Clary-N 16,010 Reputation points Microsoft External Staff Moderator

2025-08-23T08:27:41.5933333+00:00

Hi Danny,

It's confirmed that the XML/Kernel issue is affecting multiple Windows versions due to inconsistencies in update packaging and metadata. Microsoft is aware of the problem and has started rolling out Known Issue Rollbacks (KIRs) to fix critical errors like SECURE_KERNEL_ERROR 0x18B.

For most devices, the fix is automatic. In enterprise environments, it may require manual setup via Group Policy: How to use Group Policy to deploy a Known Issue Rollback

Besides, there’s no confirmed release date for a permanent fix yet, but updates are being rolled out gradually. Some devices may be temporarily blocked from receiving updates to avoid further issues.

You can track progress and official guidance here at: Windows Release Health Dashboard

If you have any other question or need further help, I'm always here to support.

Answer 2

Clary-N 16,010 Microsoft External Staff Moderator

Hi Danny Evans,

Welcome to Microsoft Q&A.

Thank you for your patience and for reporting the issue regarding Prepar3D v5.4 crashing when loading Aerosoft Airbus Pro Series aircraft after updating to Windows 11 version 24H2.

I understand how disruptive this can be, especially when the simulator was functioning correctly under version 23H2. Based on internal testing and community feedback, the issue appears to stem from changes in XML file handling and kernel-level behavior introduced in the 24H2 update.

If you are currently on 24H2 and experiencing this issue, I highly suggest that:

Reinstalling the Aerosoft Airbus Pro Series

This may help reset XML dependencies. Some users have reported success with this approach.

If you purchased the product directly from Aerosoft:

-Go to: https://www.aerosoft.com/en/account

-Log in with the email used for your purchase

-Navigate to “Instant Downloads” to find your installer and license key

Rolling back to Windows 11 23H2

This version is confirmed to be stable with P3D v5.4.

If you're within 10 days of the update:

Open Settings → System → Recovery
Click “Go back” under Recovery options
Follow the prompts to restore Windows 11 23H2

Please let me know if you need further assistance or have any other questions. I'm here to help.

Danny Evans 0 Reputation points

2025-08-19T07:08:11.55+00:00

Hi Clary,Thanks for your response. I have previously tried installing the Aerosoft product a few times while following the recommended installation process. Unfortunately this did not resolve the issue for me, or for many of the others I’ve spoken to on various forums.

Additionally, In trying to troubleshoot the issue initially, I have passed the 10-day rollback period on my PC and am now unable to reverse this update back to 23H2.

I suspect the only way forward now will be to wait for a future build to resolve this issue. Seeing as how 24H2 build 27774 and build 27788 via the Canary channel seem to have resolved this XML based issue, is there any way for the product team to implement this in the next stable update?

Thank you for taking the time to read this, hopefully there’s a way to fix this!
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Clary-N 16,010 Reputation points Microsoft External Staff Moderator

2025-08-19T07:53:09.57+00:00

Hi Danny Evans,

Thank you for your detailed message about what have been taken and for highlighting the potential fix observed in builds 27774 and 27788.

For better visibility and to support future improvements, I highly recommend submitting your feedback directly through the Feedback Hub. This allows the engineering team to track and prioritize issues based on real user impact.

Although I can’t confirm timelines for when this might be addressed in a stable release, your input is valuable and contributes to future improvements.

Additionally, I’ll do my best to keep you posted if there are any updates.

In case you have any other question or need further help, I'm always here to support.

To assist others who might have similar questions and to help us improve our support system, we kindly encourage you to "Accept the answer" if it successfully addressed your concern. Accepting an answer lets other users know that this solution worked for you, and it also helps us track the effectiveness of our support efforts.