I encountered this issue with any new account logging on, ie. one that was not already cached.
The solution was to use Windows Easy Transfer from another PC where the user had already logged on.
This "fooled" the problem PC into thinking the account was already cached and the profile already...