Cool!  Test flight #1 was flawless, not a hint of an audio-video cutout and CapFrameX corroborated it bigtime!  This being said I've had a rare perfect flight during this issue but overall almost all end up with many of these stammer cutouts.   About to start test flight #2 and if this one holds up I can be pretty certain it was 24H2 that caused this...it's been a couple of months of troubleshooting and I think it may well be over!  And I learned how to prevent 24H2 from being offered again yeah!  Thankfully I did the clone in October '24.

Thanks for the testing and confirmation Noel, going to be interesting to see if any upcoming updates will solve it or we'll all be considering rolling back. 

Halfway thru flight #2 and this would have teased out this issue:  TO out of KDEN in rain and wind thru clouds and not a hint of cutouts we'll see if it holds up on descent into KSFO.  If so I think the troubleshoot is over thankfully it's been a mysterious nuisance.   As for rolling back--do you have an image to restore or what have you?  Just lucky I had done that clone operation in October.   I really wish I had looked into motherboards that support BIOS control over m.2 slots enable/disable this would make the issue much easier to grapple with.  Next time! 

Right now I'll just wait it out with Windows updates (new one coming on the 14th) and see. If any issues persist in a month, I'll just find the 23H2 clean ISO and kill updates or get back on Ghost Spectre, should be easy to find a fresh 23H2 version of that. 

Edited January 9, 20251 yr by Sethos

I had kind of settled on waiting it out too but lost patience ultimately.  Let us know if you believe the issue is solved and I can always put the other 24H2 m.2 drive back in and go from there.  That said total performance is better now and is probably why I cloned when I did.  Often at KDEN I can dip below 45fps but didn't get close to that this time in the PMDG 738.