-
Attempting to recreate the error after reboot on my end didn't work, either. I suppose it might've been a one-time issue? I'm certainly a little more relieved that other people are seeing this at the same time and in the same manner - Unless the latest update was hijacked from SpyBot and a SubSeven trojan was delieved with the autoupdate (possible), I'm hoping this is just a one-off fluke.
And, I will note, I noticed exactly the same behavior as NotGeordie.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules