It looks like the new version of Live Sync (I was prompted to install it
this morning, but only on one of my computers) has the same broken computer
name problem that an older update also had. There's no known fix other than
deleting the computer that's now "dead" and re-linking all your libraries. I
know, it sucks. :-(
Jason Dunn
www.digitalhomethoughts.com
>On Tue, 23 Feb 2010 15:39:43 -0700, "Jason Dunn"
><www.digitalhomethoughts.com> wrote:
>
>>> I upgraded my WLSync build, and now my Win7 machine has forgotten its
>>> identity, thinking it's called OldName1. The options dialog won't let me
>>> change this, so I tried changing the installName field in the settings
>>> file
>>
>> It looks like the new version of Live Sync (I was prompted to install it
>> this morning, but only on one of my computers) has the same broken computer
>> name problem that an older update also had.
>
>Is this prompting an invitation that one may decline?
>
>Tony
Odd.
I've got Live Sync installed on a variety of machines and none of them were
offered an update at all. What version do you see in Help/About, Jason?
14.0.8089.0726 is what I see on my Vista machine that just took several Windows
Updates within the last hour, rebooted, and reconnected to Live Sync.
-steve
--
Stephen Boots
MVP Windows Live
Windows Live OneCare/Live Mesh/MSE Forums Moderator
sbo...@mvps.org
Nope. Live Sync simply stopped working. The process went a little like this:
Install fresh Windows 7
Install Live Sync
everything working great
Install Live software suite to get Windows Live Mail
prompted to upgrade Live Sync
partnership terminated
Pretty frustrating.
That's the version I have right now - I'm not sure what version it was
before...would have been good to check!
"Jason Dunn" <www.digitalhomethoughts.com> wrote:
--
I went to sync.live.com and downloaded it from here:
https://sync.live.com/clientdownload.aspx
> Is there a record of the install in the
> Windows Event Logs perhaps?
I spent a few minutes poking around the event logs and couldn't find it...
Is there a known fix for this yet?
Ed <E...@discussions.microsoft.com> wrote:
--