Skip to main content

Windows Live Writer Becomes Open Live Writer

Last week, Blogger turned off their workaround from June 2015, that was allowing Windows Live Writer, and other third party editors and auxiliary Blogger services, to access Blogger.

All week, we saw various reports of problems, reminiscent of the problems that we saw in June 2015, in Blogger Help Forum: Get Help with an Issue. Yesterday, Blogger Engineering provided a status announcement.
We would like to let all users of Windows Live Writer know that Microsoft has made the application open source and it’s now a different application called Open Live Writer (you will need to download it here).

A few months ago, the Windows Live Writer and Blogger integration stopped working for a few days due to improvements in Google’s authentication systems. We agreed to keep the old authentication systems for a few more months but starting December 11th, they will be retired and Windows Live Writer will stop working.
The Open Live Writer team is now working on making OLW use ClientLogin aka OAuth 2.0, to access Blogger.

Windows Live Writer is now Open Live Writer - and the OLW team is now making OLW able to access Blogger.

The final version of WLW will never use the upgraded Blogger client login.

Scott Hanselman notes, in his blog,
Soon, Google and Blogger will finally shut down this older authentication system. Blogger will use the more modern OAuth 2 and Open Live Writer will be updated to support OAuth 2. Windows Live Writer will never support this new OAuth 2 authentication system, so if you use Blogger, you'll need to use Open Live Writer.

We will now have to wait until OLW uses the upgraded Blogger client login.

Blogger having shut down OAuth 1.0 last week, Windows Live Writer is now out of service for direct use with Blogger. Blog owners who wish to use Live Writer will now have to wait, until OLW is upgraded to support Blogger Login.

OLW is a pretty complex project - and it has a number of open issues, which we can observe. Issue 63 is Blogger login.

If you try using OLW, and it does not work, check the open issues log. You'll probably find your problem - and maybe a solution - in there.

Some blog owners may try a workaround which uses WLW and email.

There is a possible workaround, to use WLW to compose post content, and then use email to actually send content to Blogger. Other than that possibility, we'll all have to be patient.
(Update 12/16 17:00): We're told that OLW has been updated for Blogger, and is now available for download, at


KC Bob said…
Thanks Chuck. Any suggestions on using OLW, something like it, on my Chromebook?
Chuck Croll said…
Hi Bob,

Thanks for the question - and one which I have mulled over too.

I hate to be facetious - but I am pretty sure that "Windows Live Writer" means "Publishing software that only runs under Microsoft Windows". I suspect that "Open Live Writer" means "Open Source publishing software that still only runs under Microsoft Windows".

I don't think either of us will be using OLW any time soon, with a Chromebook.
KC Bob said…
Thanks again. On occasion I do find Blogger a bit frustrating. Would be great if I could figure out how to maintain the formatting when I paste things into the Blogger editor copied from Google Docs.
Marie Bulatao said…
Open Windows Live Writer and the Windows Live Writer are both not working...Do you have any idea when they will fix this?
Chuck Croll said…
Hi Bob,

That's an intriguing idea, isn't it? You might start by learning how to use the Chrome Inspector tool (Ctrl+Shift+C) and see what CSS rules apply, in Google Docs.
Chuck Croll said…
Hi Marie,

Thanks for the question. Per Scott Hanselman's blog post, WLW will never work, with Blogger, again.
"Windows Live Writer will never support this new OAuth 2 authentication system"

OLW will work, when the OLW team makes OLW use OAuth 2, successfully - which is what most Blogger blog owners now await.
KC Bob said…
Maybe it is a Docs thing but when I am in Google Docs in Chrome, pressing Ctrl+Shift+C gives me the Word Count popup.
Chuck Croll said…
Yeah Bob, for Docs / Drive displays, you gotta use F12 (which may be hard to find on a Chromebook) to open the Console - then you have to find the "Select an element" icon at the far left corner of the upper toolbar.

Try doing "Ctrl+Shift+C" when you're looking at a website, to see what you get, first.

Also, you can use "Developer tools" from the Chrome "More tools" menu, to open the Console.
You're a life saver!!! Thank you thank you! I just downloaded Open Live and made my posts that have been sitting on my computer for a month now. Thank you!

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: