Just now, Anders Bermann said:

Aren't the Fall Creators Update being released next tuesday, the 17th of October?

Yes, but it was a joke!

s.

30 minutes ago, Greggy_D said:

Not really. Again, since it is false information.

I take offense at that. 

Go to the LM forums, read through all 15 pages of forum posts (as of this moment) as I did, and you will see that there are indeed P3D v4 users also reporting problems after one/both of these updates (4038788 and 4040724) were installed. 

https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=126667

 

1 minute ago, w6kd said:

you will see that there are indeed P3D v4 users also reporting problems after one/both of these updates (4038788 and 4040724) were installed. 

These are false-positives.  For instance, I (and many others) have P3DV4 and have the updates and no crashes related to the updates.  If you look in our CTD Forum you will see a long thread and it is all related to P3Dv3.4 users or all of them are reporting this crash with the Windows Update.  No problems for us V4 users.  People will report crashes and blame it on anything.

1 minute ago, Jim Young said:

These are false-positives.  For instance, I (and many others) have P3DV4 and have the updates and no crashes related to the updates.  If you look in our CTD Forum you will see a long thread and it is all related to P3Dv3.4 users or all of them are reporting this crash with the Windows Update.  No problems for us V4 users.  People will report crashes and blame it on anything.

When someone posts that he removed the Win10 update and things returned back to normal--in P3D v4--I find that compelling enough to listen.  Yes, *most* of the issues are related to P3D v3.  Not all, however.

Reports in the AVSIM CTD forums are not a complete dataset, and sometimes the people trying to help in there jump to conclusions far too early.

At any rate, folks should proceed with caution.

I can confirm that my P3D V4.0 and V4.1 installations were impacted by KB4038788.  Security user account permission problems can impact more than just P3D (any version), it can impact XP11, FSW, and any other applications/games/sims one might have installed on a Win10 PC.  Does this mean that everyone was impacted by KB4038788, NO!  Many users were not impacted at all, there is obviously a specific set of conditions an end user's PC might be set to that KB4038788 fails to identify and work correctly with that condition.  This is not uncommon of Microsoft or anyone producing software to miss specific "valid" end user configurations.

But either way, you can get P3D V4.x working with the KB4038788 installed IF one is impacted by the KB.  LM are aware, Microsoft are aware, Microsoft will hopefully get a fix out soon.  The work around for me was to re-establish permissions (in my case P3D V4.x, XP11, and FSW were all impacted on my main FS PC, Visual Studio was impacted on my development PC, no impact on my other Test PC).  Unfortunately, many users will report CTDs that really have nothing to do with KB4038788 and entirely to do with other issues (hardware, OC, add-ons, etc.) ... so this issue becomes somewhat of a "grab bag" of toss unrelated problems into the mix.

Bob's (OP) post didn't suggest the "sky is falling", just a word of caution about MS Windows10 updates.

Cheers, Rob.

Just now, w6kd said:

When someone posts that he removed the Win10 update and things returned back to normal--in P3D v4--I find that compelling enough to listen. 

I fully agree Bob but, when you uninstall something in Windows or go to another restore point and then run your V4 application and there are no crashes, it does not mean that necessarily fixed the crashes.  Everyone looks for that "holy grail of a fix for their crash" and, when they hear about their crashes being fixed when they remove a Windows Update, they figure this is the fix.  Personally I do not even think the removal of the Windows Update for P3Dv3 users fixed their crashes as many removed the updates but subsequently got crashes again.  This is why it is so frustrating for LM techs as they tried to replicate and could not or not 100% of the time.  We had this same issue in FSX a few years back and removing an update to IE11 stopped the crashes.  Forget how it was fixed (going back to IE10?) but it wasn't FSX as there was no one to update FSX.  I doubt P3D will be able to fix this issue too.

 

3 minutes ago, Rob Ainscough said:

I can confirm that my P3D V4.0 and V4.1 installations were impacted by KB4038788. 

How come I and many hundreds of other users of V4 are not having crashes caused by this KB?  I think someone better look into this more as something is wrong.  Either I'm wrong and my P3DV4 is crashing or you are wrong.  I have not removed any updates and I have them installed.  Could it be an add-on not fully compatible with P3D? 

12 minutes ago, Rob Ainscough said:

The work around for me was to re-establish permissions (in my case P3D V4.x, XP11, and FSW were all impacted on my main FS PC, Visual Studio was impacted on my development PC, no impact on my other Test PC). 

Rob--could you elaborate on this a bit?  What permissions needed restored to get things working again?

Regards

 

11 minutes ago, Jim Young said:

How come I and many hundreds of other users of V4 are not having crashes caused by this KB?

Most likely because our environments and what we have installed in Win10 vary considerably.  Do most users install Visual Studio in their flight sim PC?  Do most users disable EDGE/IE11 in favor of another browser?  Does everyone run the same AV software that could have interfered with KB process?  Is their a BIOS/EFI setting that tripped up an the KB installer?  Is there a specific driver than caused issues with a KB?

7 minutes ago, w6kd said:

What permissions needed restored to get things working again?

To be clear, P3D V4.x didn't stop working due to KB4038788, I did however start to get frequent CTDs (in P3D V4, FSW, XP11, VS, etc.) as a result of KB4038788 with OS event log errors that I never experience before that all seemed to be permissions related.

Uninstalling the KB didn't solve the problem entirely, setting up a new user account didn't solve the problem entirely either.  Setting the appropriate application EXE's to Windows 8 compatibility, run the app, then set the compatibility option back to "normal" did resolve the problem.

Cheers, Rob.

What the OP (Bob) and Rob Ainscough posted is accurate information in that this has been reported frequently in the P3D Forums.  We may not know if the problem is really with the Windows Updates or not but, right now, there is a problem.  As reported, LM is working with Microsoft on the issue and, if they do find an incompatibility, I'm sure it will be fixed.  As least this is not like back when the Window Updates were crashing FSX and we could do little as there was no one working on FSX to issue a Hotfix.  I thank Bob and Rob for the information as it has not been totally proven false and it is something that all of our members and users of P3D should be aware.

I apologize to Bob and Rob for my potentially condescending comments as I know they are trying to keep our community informed.  I just wanted everyone aware it is not happening to every user and I probably did it in the wrong way (again, as usual).

No apology needed for me, all good here Jim - the objective for those involved has always been to help.  I doubt we'll ever find out the exact issues around KB4038788, but in the meantime I enjoy all my flight sims and have them working just fine, fast, and furious.

Cheers, Rob.

I'm a little late to this party but I also had the problem with V4 on my main system. Interesting also that on my secondary system where I have both V3.4 and V4.0 - I had the problem with V3.4 but NOT with V4. SO there is definitely a system component aspect to the issue .

Vic

7 hours ago, B777ER said:

A simple setting change shuts off W10 auto update. 

There were many P3D Facebook Group users that had troubles with Version 3 and a few with version 4 right after the windows update KB 4038788. Almost everyone that uninstalled that update and then hid it so it would not reinstall, had their P3D immediately return to normal/ Amazing!!  

Maybe that's naive, but what I don't understand is, if this is a Win10 update/P3D issue why don't all (or most) of us suffer on it?

15 hours ago, Nemo said:

Maybe that's naive, but what I don't understand is, if this is a Win10 update/P3D issue why don't all (or most) of us suffer on it?

Exactly! The bottom line is that there can't be any fundamental problems with the Windows 10 updates, otherwise everyone would be having issues and, clearly, most are not. The problem must be caused by some other piece of software on the affected systems which doesn't react well to the update.