The issue is resolved in MR5.
The issue was with MR4MP1
High Explorer.exe CPU usage when touching exported SEP client package
This issue still occurs with an unmanaged SEP client. *Managed* clients don't
seem to have a problem.
I tested with XP Pro SP1 and an unmanaged SEP 11 MR4 MP1 client, updated with
current definitions. I exported a client setup.exe from two other SEPMs (MR4 and
MR4 MP1). In the XP client, right-clicking these packages and choosing
properties results in a delayed response. Explorer.exe doesn't max out, but CPU
usage stays around 30%.
When I convert the XP client to managed (by SEPM MR4 MP1), the issue does not
re-occur -- the properties dialog for both packages appears immediatly. The XP
client didn't receive any updated content from the SEPM -- it already had latest
updates, so I'm puzzled by the difference in behavior.