Sudden drop Epicor speed caused by Microsoft Updates -> (KB4601319, KB5000802, KB5000808,KB4601382,KB4601383) +

Has anyone tried the 2021-03 Cumulative Update for Windows 10 on a machine yet and confirmed if there is a performance hit. I’m still experimenting, but I think applying it to my laptop (as KB5000802) just made the performance drop in Job Entry again. :sob: Trying to expand my testing a bit, but figured I would get a little group consensus as well, thanks.

My updates get applied Wed at noon… I’m sure I’ll find out tomorrow if this is a major issue or not… I’m not looking forward to that.

Just read this article

At the bottom it states…

Some users have also reported that Microsoft has temporarily halted the rollout of the March 2021 cumulative update, while others said that they’re still seeing the cumulative update on the Windows Update page.

I do not see the update installed or available on my machine and I just checked for new updates.

2 Likes

Spoke too soon… It’s showing as available on my machine now and installing.

I will report my results after testing.

I just confirmed that on my HP laptop with Windows 20H2, uninstalling this KB5000802 my performance in Job Entry in Epicor is back to ~2 seconds to switch between jobs, rather than 6-10 seconds. So uninstalling the update restored performance. Darn! Is Epicor working with Microsoft at all to ensure at some point we’ll be able to update our Windows clients without crippling Epicor?

2 Likes

FYI:
2W Technologies, Inc. (both a Microsoft Partner and an Epicor Partner) is actively working with Microsoft and Epicor ERP to try to help bring a beneficial resolution for everyone.

Any suggestions on best steps (inside of Epicor ERP) to most effectively demonstrate this performance degradation is appreciated.

Just open job entry, search for a Job number and try to load it to the form, it takes 10+ seconds to load. Then try to close the window. Do this on a machine with the update installed and one without it. It’s night and day difference.

3 Likes

I can also confirm, installed KB5000802 at around lunch. Same performance hit as 4601319. Job Entry loads the same job in 15 sec with the patch and 3 without, same as after removing 4601319.

2 Likes

It would be good to have client/server tracing to see if everything is affected the same or just some parts are slower.

3 Likes

I don’t have the trace anymore but with one client we ran a trace on searching on AP Tracker and then selecting one record from the results to view in AP Tracker.
I think it was a GetByID that was the longest @ 700.
The Search was long too.

any open with screen, try Job Manager then open Job or PO with and see the bad performance in launchiny screens and loading data

I would need to know exactly what you want before I try to start anything. I’m the only IT individual on staff here and I don’t have much spare time to try out some traces to find out it’s not what you’re looking for. As many have noted here all you need to do is run Epicor on a machine with these updates installed and you’ll experience the 10+ sec of load time when retrieving any record into Job Entry, Part Entry or Order Entry… and I’m sure it happens elsewhere too since the entirety of my Epicor users were complaining about the slowness of the system.

This performance hit is not something that takes a novel of special reproduction steps to get it to happen. It’s cut and dry… W10 machine with Feb or March Security update installed… run Epicor, and cry every time you see the blue circle.

3 Likes

@Vitesse - is there any Epicor or Microsoft case number or somewhere where we can follow along and maybe get an idea of if this will be resolved before the April cumulative updates? I really don’t want our organization to start falling that far behind, but we also don’t want Epicor to be 2-3 times slower at loading data. :frowning:

1 Like

Epicor CS0002466257 . Microsoft 2103040040006613.

Worked (yesterday) with Microsoft to provide diagnostic trace information on a Win2019 1809 Server with/without the (Feb 16 Preview Update) KB4601383. In my testing, it appears that the normal patch Tuesday Feb 9th update (KB4601345) did not affect performance. Just the Feb “Preview” update did…which includes (depending on OS and version) KB4601319, KB4601383 (and maybe a couple others, but it depends on your version of Windows 10 or Server 2019). The normal March 9th Patch Tuesday KB5000822 update did not seem to affect performance, in my testing.

We turned off updates on my dev server and then manually installed and uninstalled these specific updates to test their effect with and without them. We focused on the times it took to open a record in Job Entry, and then going to the Part Field to say OPEN WITH > Part Entry, as the example. This is not to point to the finger of blame at either the Microsoft Updates or the Epicor ERP software at this point. This is to say that we are attempting to help them gather the data that the developers can use to determine specifically what is happening and what needs to change to remedy this.

1 Like

As was noted a while back, none of us have seen the Feb update to slow performance at the server location. The only situation that is showing a performance decrease is a Windows 10 Client with the respective KB4601319 and now KB5000802 updates applied. Please move away from testing at the server level and move to client side testing, that’s where the performance drop is happening.

3 Likes

Did you test it on a Win10 PC build 20h2? That is the build that is causing the problems with everyone. We have a bunch of PCs still on Win10 1909 and those are unaffected by the updates.

It appears to equally affect Windows 10 and Windows 2019 Server when the equivalent update is installed. (It only appears to affect the Epicor ERP client, not the Epicor server components.)

Noted here too.

It’s also affecting Build 2004. All of my machines are at that level and it showed significant speed decrease when those updates were installed.

3 Likes

I’ll take your word for it @Vitesse, but for us the BIG impact to our organization is Windows 10 version 2004 and Windows 10 version 20H2 client PCs. These will ALL experience the performance hit badly if we install the February or March cumulative updates pushed out via our WSUS server with the KB listed in the title of this thread (which have now been DECLINED). And the rest of this thread seems to indicate that is the big impact for other organizations as well.

3 Likes

Yes, sorry, 2004 and 20h2. Nearly all of my 2004 computers were upgraded to 20h2 but I did decline the updates to 2004 as well as 20h2 in my WSUS.

1 Like