I never had this happen before with a firmware update. I might try an older firmware to see if it's giving me the same problem.