Windows live writer wont connect to blogger

Anonymous
2015-05-26T22:10:34+00:00

I have been using the windows live writer for years and today it wont let me post into my blogger blog. 

The first error was stating that my user name and password was incorrect so I changed it. It still didn't work and still stating the same issue. I clean/repaired up the windows essentials like other forms said. Now the error message I get is blogger return the following error: Notfound: not found. I uninstalled and reinstalled and it keeps saying the same issue.

Thanks.

Windows for home | Other | Email and communications

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2015-06-02T01:38:24+00:00

please make sure that you use the following steps

  1. Verify you are using http or https for you website.
  2. Add ' @gmail.com ' at the end of your user name.
  3. If your account has 2-step verification enabled then see the following guide to use app specific password rather than your original password.

App specific password generation

Was this answer helpful?

0 comments No comments

185 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-12-12T10:42:53+00:00

    Yes same has happened again when I tried to post this morning. I posted successfully on 6th december at 11:25  , but today 12 december at 10:42 it fails exactly as before. 

    The best workaround  I found for text which still works this morning is to mail a post - go to Settings in Blogger, Mobile and email, set up an email address for your blog and send the post that way :)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-12-12T05:09:25+00:00

    Same thing is happening to me.  I'm going to find out how to report it to OLW.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-12-12T05:05:37+00:00

    The issue originally occurred in May, was fixed in June, and now, December 12, 2015, it is happening again!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-12-11T19:45:52+00:00

    Same here!

    Was this answer helpful?

    0 comments No comments