This project is read-only.

Does not work in Windows 7 RC


I've tried to execute wlwbackup as administrator and using compatibility mode with Vista SP2 or WinXP Sp3 and still does not work. There is an unhandled exception as soon it starts.

file attachments


ScottIsAFool wrote Aug 6, 2009 at 6:24 PM

Hi, is this Win7 x86 or x64? And what version of WLWBackup is this? Can you please email your log file to so that I can try and establish what is going on. To get your log file, please click on the about button and then show logfile.

albertop wrote Aug 6, 2009 at 11:35 PM

The app does not open at all. I'm using Win7 x86 RC Build 7100

wrote Aug 6, 2009 at 11:35 PM

ScottIsAFool wrote Aug 7, 2009 at 8:16 AM

Go to Start > Run (or press Windows Key + R if Run isn't in your start menu), and type "%localappdata\Windows Live Writer Backup\" and press ok (without the quotes). In there should be a log file, if you can send that to, hopefully that should let me see what's going on.

albertop wrote Aug 19, 2009 at 2:08 PM

The path provided does not exists and in the path C:\Program Files\ScottIsAFool\Windows Live Writer Backup there isnt a log.

ScottIsAFool wrote Aug 19, 2009 at 3:24 PM

Sorry, I missed a % out. It should be %localappdata%\Windows Live Writer Backup. This will take you to your local appdata folder. The log file is in there, not in the program files folder.

JulieLerman wrote Jan 2, 2010 at 2:39 PM

Hi Scott,
I'm having this problem also (win7 x64). I'm attaching the log file (wer from event viewer). Let me know if you needed a different one.
There is no WLW folder inside of appdata local or local low or roaming folders.


wrote Jan 2, 2010 at 2:39 PM

JulieLerman wrote Jan 3, 2010 at 2:15 PM

AHA! Figured it out. FInally took a hint from the XAMLParser error. This was a new computer and I was trying to import the settings from another copmuter before starting up LiveWriter. This was the reason WLWBakup was throwing the error. Once I opened WLW and configured a blog then tehre was some XAML for WLW Backup to read. So the problem is that WLW's settings file didn't exist.



wrote Feb 13, 2013 at 9:43 PM