Skip to main content

Windows LiveWriter, And A Less Secure Login Option

Some blog owners, who use Windows LiveWriter, may still be seeing the signs of the recent security update by Blogger.
I get an error saying that it cannot log into remote server, and that my password/username are incorrect - although I have re-entered and they are correct.
It appears that Blogger may have created a backdoor, to allow LiveWriter client access - which requires a new Google setting.

One forum post suggests a backdoor setting, in Google Security, which appears to enable LiveWriter to login to Blogger.
IT'S WORKING AGAIN!!! With a caveat - you'll get an error message about not being able to log in. After you do, check the Gmail account associated with your Blogger. Open the link to control your access security settings ( and allow "Access for less secure apps." Then click the back arrow. Quit LW, then open & try again.

Click here for the "LessSecureApps" wizard, in Google Security.

The setting provided appears to be global. If you have other apps which use ClientLogin, this may or may not provide a complete and safe solution.
Some apps and devices use less secure sign-in technology, which makes your account more vulnerable. You can turn off access for these apps, which we recommend, or turn on access if you want to use them despite the risks. Learn more

It's your option, to allow all applications which use Google to authenticate, to use the less secure "ClientLogin" process.

If you are using Google 2-Step Verification, you can't use this new option.

Some third party offline editors may still need to be upgraded - as it does not appear that the "Less Secure Apps" option is a built in feature in OAuth 1.0. Your experience, and feedback, is welcome.
(Update 2015/12/16): Windows Live Writer has been replaced by Open Live Writer, an Open Source project. OLW will only work with OAuth 2.0, and is available for download.


P. C. Poppycock said…
I continue to experience this problem. And it is slowing down my blogging efforts a great deal.

I have tried toggling the Google security settings, both the "two step" setting, and the "allow less secure apps access."

Nothing changes my results.

In an earlier attempt to fix things, I upgraded from Live Writer 2011 ti Live Writer 2012.

Should I dump the newer version and go back to 2011?

P. C. Poppycock said…
Just converted back to WLW 2011 in place of WLW 2012, and performance is exactly the same: NO GO.

I'm really frustrated at this point. Convinced there is no solution to resolve the anomaly on my machine.

I'm really angry, but I don't know who to direct the anger to.
Chuck Croll said…

If you're still unable to use WLW, you need to be posting in Blogger Help Forum: Get Help with an Issue, so we can try to diagnose.

We have no ability to cross reference your Blogger profile with your forum identity - so your best chances for solving the problem lie with you posting in the forum.
Ed Dylan Goff said…

Just to recap- you went through the "less secure app" process, obtained a password and typed it as your new password when trying to access WLW. It worked for me without a hitch so it seems like

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: