This is a known issue, so I doubt it has anything to do with the update. Unless, of course, they tried to fix it and broke something else.
Since release, I have experienced it three times on two different USB controllers, so it seems to happen rarely enough that it could be a coincidence that you get it now.