stopcrazypp
Well-Known Member
Well I'm talking about the latest rash that happened immediately after the recent updates. Some were able to get the error to clear (at least temporarily) with a reboot, plus their devices worked anyways regardless of the error. Plenty of people didn't try a reboot as their first thing, but rather went to try replacing devices. Obviously there are other different cases that have nothing to do with the recent update.Rebooting does not solve the issue. It has existed for well over a year now, and rebooting is one of the first things everybody tries.
just got this alert, not sure what it means