Good day everyone–this is Nathan, long-time listener, first time in a long while poster.
As @tkoch posted earlier, Epicor ERP support has created and published a knowledge article that provides information regarding the preview fix from Microsoft intended to address the performance concerns introduced by a number of Windows updates that were published between February 2021 and April 2021.
The members of my ERP technical support teams have already started providing updates to the EpicCare cases that have been associated with this MS update concern with information regarding this preview fix and the knowledge article on how to apply it if one so chooses. As soon as I hit the reply button on this post I’ll be working on a report to identify any other open EpicCare cases that might be related to this concern so we can reach out to those customers as well.
The mandate that was given to my team was to provide this information for any open case tied to this concern, even if this information may have been provided to company/customer contact via another case already–so, my apologies if you are one that does. We’re implementing some automation this weekend that will let Support know if a customer account has already been sent this MS fix KB.
There is also an EpicCare alert that will be published shortly mentioning this MS fix for those that log into the EpicCare portal for those that may be impacted, so we can try to draw attention to this situation for those that may not have an open Support case tied to the MS updates in question at the moment.
*start disclaimer that my views may not be those of my employer*
My apologies for the way that information regarding this preview fix from Microsoft occurred. I have been assisting @Epic_Santiago internally on this concern since the beginning, and the impact was absolutely understood by everyone. As soon as the preview fix was validated by our internal testing and by a small customer testing group (which started on Wednesday and concluded yesterday), I started developing the documentation and process to disseminate this information in a way that could lead to the greatest potential success for all of our impacted customers within my ability. There was obviously pressure for Support to provide and release something/anything the moment we could, even if that something/anything was going to likely cause more questions or issues than deal with but I simply couldn’t do that. Those that have been following this thread closely may have caught that the formal Epicor communication to this preview MS fix was accelerated (and the overall Epicor response was really only waiting for the knowledge article that I created on this topic). If anyone feels that our response to this fix was slower than it should have been–that’s on me, no one else.
In closing (this is a really long post), I’m not a hyperbolic person, so when I say that the effort that the team involved with this internally at Epicor has been extraordinary (not sure I’ve used that word in a professional context before) I mean it. I’m one of those very unfun people that believes words should mean what they mean. As you all probably know by now, this wouldn’t have been possible without the amazing @Epic_Santiago.
Link to the KB on how to apply the preview MS fix:
https://epicorcs.service-now.com/epiccare?id=epiccare_kb_article&sys_id=abdb5c9bdb972410a587ef0705961996