P3D v5.4 and Windows 11 24H2 update issues

[Juliet Oscar Echo]

Hi all,

Last week, my Windows 11 update was indicating that 24H2 update was available.

Naturally, I did this update and all was good. First flight I did was on PMDG 777 and no issues there.

However, firing up Aerosoft A3XX Professional, it just CTD upon loading.. Further investigation into Aerosoft and P3D forum suggests Windows 11 24H2 update ruins some XML files. This seems to cause some issues.

Trying to get Aerosoft to investigate is a roadblock. They are quoting to me that A3xx professional was built for Windows 10... So good luck and **** you pretty much. 

https://forum.aerosoft.com/index.php?/topic/178450-p3d-54-and-windows-11-24h2-aerosoft-a3xx-crash/

Also trying to get P3D to investigate.. but seems to me they are not willing to help much.

https://prepar3d.com/forum/viewtopic.php?t=151166

I've opened a feedback support ticket at Microsoft.. but I'm not too sure how much support I will get from them.

I've managed to roll back to 23H2 and all of them are back to normal. No CTD at all.

I'm just wondering... is there anything else I'm missing with this? Anyone found any solution to this at all?

[blaunarwal]

How about just reinstalling the Airbusses?

[d.tsakiris]

Yes, this. I have found that the AS Airbusses often fail to load after Windows updates (even the monthly one), and re-installing them helps. I have the A318/319, the A320/321, and the A330, and I only have to re-install ONE of those packages for all Airbusses to return to normal.

[Ray Proudfoot]

I updated Windows yesterday. Found two problems.

1) GoFlight GF166 units remain blank. Other GF kit is fine. Uninstalling and reinstalling GF setup program resolved things.

2) Steam Lossless Scaling stopped working. New version installed. Stopped using RTSS for fps limiter and switched to Nvidia Control Panel instead. DXGI no longer supported. Alternative option fine.

I’ve only flown FSL Concorde and that was fine. Testing other 3rd party aircraft today.

[Juliet Oscar Echo]

18 minutes ago, blaunarwal said:

How about just reinstalling the Airbusses?

That was the first thing I tried. Uninstall the entire A3xx professional, including the A330 series.

Same issues. Only solution is to roll back 23H2 for now.

 

[sloppysmusic]

I've done one flight in pmdg 747 and no issues since update. I will test an a2a plane next. I don't have any buses. Is that the voice of pmdg in as support? 🤔

[Hauer]

I've encountered exactly the same issues with the Airbus Pro series... did a complete reinstall of Windows 11 Pro and several installations of the Aerosoft Airbus Pro series... no luck!

Hope Aerosoft/ PREPAR3D look into it as for me it would finally be a pushover to MSFS.

Cheers,

Herman

[G-RFRY]

I have found after updating W11 I had redo my program exclude again, this tends be to down to windows updating your security back to default on some programs. 

[Hiroshi_Igami]

More stupid bugs of Windows 11 24H2

Windows 11 24H2  destroyed  MS's XML  's string function.
"sstr"  .. Search string   ... Now broken
"symb" .. Get 1 character from the string  ... Only 8 character from the top is correct
"uc" "lc"  .. Upper case and lower case   .. Now destroys the string

Under explains a bit more.
Those functions are used to read the string which is written in "title=" line of aircraft.cfg

https://www.facebook.com/photo/?fbid=10227509579349317&set=gm.2523375564534587&idorvanity=152608834944617

On Windows 11 23H2 .. there is a report that no problem.
Problem started from  24H2.

So far only way is roll back to 23H2.

Edited January 1 by Hiroshi_Igami

[blaunarwal]

On 12/25/2024 at 9:59 PM, Hauer said:

Hope Aerosoft/ PREPAR3D look into it as for me it would finally be a pushover to MSFS.

That is exactly what they want, that we buy the next crappy product.

I think we have to hope and wait for the next W11 update.

[spilok]

On 12/31/2024 at 7:56 PM, Hiroshi_Igami said:

More stupid bugs of Windows 11 24H2

Windows 11 24H2  destroyed  MS's XML  's string function.
"sstr"  .. Search string   ... Now broken
"symb" .. Get 1 character from the string  ... Only 8 character from the top is correct
"uc" "lc"  .. Upper case and lower case   .. Now destroys the string

Under explains a bit more.
Those functions are used to read the string which is written in "title=" line of aircraft.cfg

https://www.facebook.com/photo/?fbid=10227509579349317&set=gm.2523375564534587&idorvanity=152608834944617

On Windows 11 23H2 .. there is a report that no problem.
Problem started from  24H2.

So far only way is roll back to 23H2.

You're right.  Unfortunately, if you don't "roll back" within 10 days, you cannot roll back at all.  It's greyed out.  I want to roll back too because I have been posting in this and other forums about missing wings in TDS planes.  The problem was explained to me just as you say above.  

For me, it's too late.

 

 

[Nicholas5112]

Hi, just to let you guys know that the 5.3.17.28160 works just fine on the 24H2 with the all the Aerosoft A3XX Professional, there is something wrong with the 5.4 build itself, if you are not using anything that depends on this verion just use the older one.

[spilok]

1 hour ago, Nicholas5112 said:

Hi, just to let you guys know that the 5.3.17.28160 works just fine on the 24H2 with the all the Aerosoft A3XX Professional, there is something wrong with the 5.4 build itself, if you are not using anything that depends on this verion just use the older one.

I love 5.4.  Hate to go back to 5.3, but that is indeed interesting.

[Hauer]

 

 

Hi guys, It is definitely a Microsoft 24H2 update issue... have rolled back to Windows 11 Pro 23H2 (entirely new re-installation). 

Found a link on YT as how to prevent the latest 24H2 from installing.

Link: https://youtu.be/nEjkPacrJ00?si=9dZsN0cn8VNSTK6A

It has solved the CTD issue in my case. I can now operate my Airbus Pro series as previous.

Microsoft certainly know how to frustrate folks!

Cheers - Herman

[spilok]

Is there any POSSIBLE WAY to find a link that allows us to REVERT back to 23H2?  As I've mentioned, Microsoft won't allow this after 10 days have elapsed since the upgrade.  

I would pay to be able to go back!