I've had this problem before, but only occasionally, so always thought it was just a hiccup at that moment in time during an OSD.
However, MS released a couple of weeks ago a hotfix to resolve this issue:
This is a client patch that you install on the site server and then edit your task sequences that have the client install step to add the following to the Installation Properties section:
Where <Package_ID> should be replaced with the ID of your SCCM client install package.
One thing to note is the client version is increased to 4.00.6487.2188, so any reports/queries/health scripts you have that reference the client version should be updated to reflect this hotfix.