Same here. Get the error occasionally on two Win 10 computers, several times a day. It seems to depend on if, and what kind of updated content, is present at the time om the update, whether the error occurs or not. So a bit hard to reproduce in a controlled way.
After the error occurs (auto update initiated) I can manually trigger updates 0 – ~6 times before the update finally succeeds.
Both computers are recently updated to "Windows 10 Fall Creators Update" as opposed to several other Win 10 machines not getting this error. But we also have a third Win 10 machine updated to "Fall..." that as far as I know don't get this error, so...
All these Win 10 machines runs latest Endpoint Security 6.6.2064.0.
I have traced file access with Process Monitor during a failed update. I filtered the output like this:
The lines I've found interesting looks like this:
Unfortunately the Update engine advanced logging wasn't activated at the time, but I'll send you the collected logs anyway.
You'll get the ELC and PML files mentioned in a PM.
If you also need Update engine advanced logging, let me know.
/ Håkan