I always check event viewer after updates to see if errors appear. Twice the User.dat (Event 4 hive recovery) recovered from an error at boot. Took almost a minute for system to react. It does not always happen but does happen on a regular basis since update. The other is a known DCOM error. It's a permission issues that MS won't fix. I always fix that issue on new install. Error reappeared either because DLL was updated or other.
So dcom is not a new issue (it's even known by msft and prolly by design) and the ntuser.dat corruption error message i didn't even get. As you state yourself it can simply be something local on your system. And even in win 7 after clean install the eventviewer reports similar errors as i show in my clean MSDN install.
Yes for DCOM not the event 5 user.dat issue. Other users have spotted that issue after 594 update. Is it software compatibility or Windows related, too soon to know. Let's just wait and see.
Screenshot or it didn't happen, we also didn't get one from zardoc (yeah one without even the normal info).
It's pretty simple. I fixed the problem. I can always rollback the machine and post picks to entertain you , but I hope that you'll take my word for it. It means that there is a fix for those who encounter the hiccup and I wanted those affected to know it. Cheers.