Before I learned of this relevation, I rebooted my PC thinking the firewall options in WISC would maybe show up. I'll never know because now I CAN'T LOG IN TO MY COMPUTER!. Same pw as I've been using for 3 weeks yet now all of a sudden I get the "wrong password" message. Yet I can still log in w/that pw everywhere else. Even still, I reset my pw via MS live but I still can't log in to my computer.
I did some Google searching and came across two posts:
- "Samsung NP300E5C-A07US
- Intel Core i3-2370
- Intel HD Graphics 3000
- Runs native on Windows 8
- Genuine Windows 8
- Webroot SecurityAnywhere: ISS 2013
"interesting.... I'm (or was) running Webroot security too. It was working fine yesterday untill I rebooted. Came across a number of internet posts talking about issues with passwords longer then 16 chars but like I said it was working fine yesterday, and my password isn't 16 chars long."
2 other people with this issue that I know of. This is bad. Really bad. After talking with MS, I now have to literally completely reinstall Windows 8 and may lose everything. I"m going back to Kaspersky as fast as I can. Their Russian suppot is awful but they never locked me out of my own computer, including Windows 8. I LOVE Webroot support but this lockout is just absolutely unnaceptable. If anyone has another explanation, I'm all ears. Thanks.
Best answer by JimMView original
It appears the problem has been solved. Now I can login into the Admin account and install applications that require elevation.
Thanks to Microsoft and Webroot for fixing the issue. And Webroot, please be more careful next time ;)
Late last night, a build was released that contains a fix for the Windows 8 login problem. The link in my post from above now contains new information regarding this fix. Here is the link again for your convenience.
In short, if you have a local login, you can update WSA to resolve the problem. If not, a system restore or refresh will still be a necessary step to obtain the installer, which, once it's run, will prohibit the issue from occurring again.
Identifying details about the cause of this issue was a group effort, and we extend our thanks to Microsoft and GeekSquad support teams for helping to expedite a fix. 😃
Do you have an ETA for the new build, I don't want to perform a system restore/resfresh as I have access to a local account and don't want to install drivers and so on.
More on this solution can be found here:
That page will be updated with additional information as more becomes available.
We would like to extend our thanks to Microsoft and GeekSquad for collaborating with us behind the scenes in identifying the root cause. Thank you! :catvery-happy:
Can you PM the details on the 3 files? Would really appreciate it.
Nice to see that you posted over here also as you did at Wilders! 😉 Just follow the advice from Jim and the support inbox staff and they will help you get it sorted!
I already contacted the support but so far I got no response, and yes I would like support to contact me in order to diagnose this issue.
I'm using the local account so far, if you're willing to help please contact me asap.
I moved your post into a related thread where we already have a discussion going on about the issue. I'd encourage you to please read this thread.
Please note as well that this issue is addressed in our Top Issues article here.
The pertinent content on that page reads:
"The quick fix for this issue is a system restore or refresh. However, support would like to look at more cases of this at a deeper level to determine if Webroot is the cause of the issue or is related in some way. if you are willing to volunteer to let support take a longer period of time for analysis, please open a support case."
To answer your question, a list of all Webroot files and locations can be found here. However, we don't recommend ripping out all of the files by hand on your own under any circumstances, and we would very much prefer that you go through support since we are still investigating this issue. Even if you delete all of the files, you're not reverting the registry. If you are going to do it anyway, you would be doing it at your own risk. You will probably be happy to know that support is also equipped with a bootable Linux distro with remote access capabilities that they could use for similar purposes in troubleshooting. It sounds like you might be just the case we're looking for if you wouldn't mind setting up an appointment please. That way, the knowledge we may gain would help not only you, but potentially others as well, and from your perspective, you get the peace of mind that any actions that are taken in troubleshooting are safe ones.
First, this is my post in Windows official forum:
If you take your time to read, basically my admin Windows Live account can not be accessed, some users are experiencing that problem, but when the problem started (last Thursday), only a handful were experiencing that same problem. I've changed several messages with a forum Admin and Friday Microsoft sent me a Pen Drive, which arrived today, in order to help diagnosing the problem.
I'm reading their forums and they say the problem may be related with Webroot products --> http://answers.microsoft.com/en-us/windows/forum/windows_8-security/why-cant-i-sign-into-windows-8-with-my-microsoft/7662ea57-c321-4bfe-84e9-fc9ebb87a44b?page=6&tm=1355192298401
Now here is the deal, I need to uninstall Webroot, the problem is that I've checked the option that does not allow users without admin access to uninstall the security software.
I've a Linux Live CD ready so I can erase webroot files in order to at least make it non functional so I can further troubleshoot the issue, but in order to do so I need to know which files to remove.
Can you provide assistance?
Just to clarify, my initial theory on this issue from page one turned out not to be the case, which is why we're still investigating. Based on everything I've seen so far regarding this issue, I'm in agreement with AgentMike that this is starting to look less and less like a Webroot-specific issue. We'll continue investigating though.
Umbra, I can't PM you a procedure, because the investigation has to go through the support system, which is better equipped than Community to conduct an investigation of this nature. If you click the link in my post above, it will take you to the support system.
NOTE TO PEOPLE READING THIS THREAD IF YOU WANT SAFE MODE
Dell Tech Service directed me to do the following to restart in safe mode (Note that Shift-F8 did not work for me):
1. On the login screen click power button
2. Hold shift key, click restart
3. you may see the safe mode option after you do this.
Please put in a support ticket from the computer having the issue as well so we can collect some logs for investigation.
I did a security scan on WSE and restarted my computer, then i can no longer login, even if i reset my password...any help would be more than appreciated. thanks.
I've been taking a look at your keycode, and I identified one abnormality in how we were treating a particular file on your system. That file had to do with internet connectivity. My initial theory is that you had a Live logon set up, which would be trying to validate your password with Microsoft, rather than a local logon set up like older versions of Windows. Possibly, you ran into this issue due to the handling of that file. The file has been recategorized now, so that if I'm right in my theory about the cause of the issue, it will not happen again. I'd like to invite you to try again please by reinstalling Webroot, allowing the first scan to complete, and restarting your computer thereafter. I suspect you will not run into the same problem again. However, in the event it happens again, I've followed up with you via the support system, and we will continue investigating if necessary.