Latest Windows Update crashes LiveResponse

[angel_2_0]

Originally Posted by Roger Clark

We are sorry for the inconvenience. It is sometimes impossible to predict the results that patches and Windows Updates will have on any given application; we will work hard to correct any issues as soon as possible.

Im sure we all understand

[paysite-cash]

Originally Posted by angel_2_0

Im sure we all understand

yes, thanks microsoft

[John Haugeland]

It's worth noting that mission critical systems should never be set to automatic updates. If you cannot tolerate an outage, manually run update two days after the automatic date, once you can see that nobody else has gone down. Updates like the ones Microsoft and Red Hat distribute are by definition unsafe; this applies to every mission critical system.

Leaving a computer set to automatic update means it will always be up to date, but mysterious failures can begin due to outside influence.

If you're running mission critical systems, accepted best practice is to run several client machines in parallel, and to leave one of them on automatic update. That way, you have a strong indicator of when things blow up, and you can upgrade the others safely every Thursday. (If you only have one client computer, an acceptable similar option is free virtualization software, which lets you run several simulated machines side by side.)

For a lot of people, it's better to just leave upgrades on and take a hit of a couple hours once every year or two. But, if you cannot tolerate occasional downtime, that also means you cannot tolerate automatic upgrade systems.

[keola]

Wow, I posted this and the end of my work day yesterday, I must say that I am highly impressed on how fast this community has responded! Thank you all for all the help in getting this issue resolved. I look forward to the new bits of software that aim to fix this.

And thank you for finding the temporary fix.

[craigbrass]

It's worth noting that mission critical systems should never be set to automatic updates. If you cannot tolerate an outage, manually run update two days after the automatic date, once you can see that nobody else has gone down. Updates like the ones Microsoft and Red Hat distribute are by definition unsafe; this applies to every mission critical system.

There we go Jamie. Exactly the point I was trying to get across

[Jamie Edwards]

What you said was still not a solution.

To quote what John said:

If you're running mission critical systems, accepted best practice is to run several client machines in parallel, and to leave one of them on automatic update. That way, you have a strong indicator of when things blow up, and you can upgrade the others safely every Thursday. (If you only have one client computer, an acceptable similar option is free virtualization software, which lets you run several simulated machines side by side.)

For a lot of people, it's better to just leave upgrades on and take a hit of a couple hours once every year or two. But, if you cannot tolerate occasional downtime, that also means you cannot tolerate automatic upgrade systems.

Thanks ,

[keola]

Originally Posted by cwudarski

We found that the IE 7 patch KB944533 is what broke it for us. Uninstalling this update fixed our problem with the Windows app not opening.

Just had a chance to try this fix, and found that I don't have KB944533 installed, I believe that this update is a cumulative one and after looking at the summary for KB944533 I could see why that update would/could have affected the client (lots of stuff got patched). For those of us who don't have that update, it's probably a combination of several updates (which I have neither the time nor the patients to hunt down atm) so if anyone can figure it out (not that I'm holding my breath or anything as it sounds like we all have other duities to attend to) please post here.

Originally Posted by AnnS

I too hit this this morning, but am up and running again now.

Started by uninstalling LiveResponse using the Windows add/remove facility, didn't delete anything manually, then reinstalled - still errored.
Used System Restore to roll back to pre-windows upgrade, LiveResponse still failed to load but with a different error (something relating to a language pack?).

Ran the installer again, over the existing installation, and it now runs fine - hope this helps someone...

Oddly I tried this yesterday, and after reading your post I tried again with renewed hope, but sadly, it didn't work, but it seems to have worked for someone else.

Hopefully this will be fixed by the powers that be, and we can all be up to date and on our way breaking other thing =)

Just for the sake of wondering, how many incident reports do you think Microsoft got because of this? I know I sent at least 30 lol

[keola]

Originally Posted by John Haugeland

It's worth noting that mission critical systems should never be set to automatic updates. If you cannot tolerate an outage, manually run update two days after the automatic date, once you can see that nobody else has gone down. Updates like the ones Microsoft and Red Hat distribute are by definition unsafe; this applies to every mission critical system.

Leaving a computer set to automatic update means it will always be up to date, but mysterious failures can begin due to outside influence.

If you're running mission critical systems, accepted best practice is to run several client machines in parallel, and to leave one of them on automatic update. That way, you have a strong indicator of when things blow up, and you can upgrade the others safely every Thursday. (If you only have one client computer, an acceptable similar option is free virtualization software, which lets you run several simulated machines side by side.)

For a lot of people, it's better to just leave upgrades on and take a hit of a couple hours once every year or two. But, if you cannot tolerate occasional downtime, that also means you cannot tolerate automatic upgrade systems.

This is true folks, I am only one of 2 people that were affected here... Why you may ask, well we're the guinea pigs (actually we just like breaking stuff) now everyone here knows not to do these updates (as well as KB944533) so we're still up and running, sans two, but we'd rather be doing other things anyways...

[Roger Clark]

This updated build should work for all of you who have experienced this issue. Please let us know if you experience any problems.

http://67.228.88.247/download/lr/3.1...5-UNSTABLE.exe

[paysite-cash]

Originally Posted by Roger Clark

This updated build should work for all of you who have experienced this issue. Please let us know if you experience any problems.

http://hotfix.kayako.com/download/lr...5-UNSTABLE.exe

file has 340 bytes....it is not well uploaded it seems

[Roger Clark]

We have recently moved the hotfix server, so the new DNS has apparently not been updated.

You can download it from here:

http://67.228.88.247/download/lr/3.1...5-UNSTABLE.exe

Sorry about that!

[paysite-cash]

thanks

now it worth...impossible to connect to support...operation time all the time, same on 2 tested computers

[Roger Clark]

It's an issue related to the proxy code. I will have it fixed within the hour.

I apologize. It's difficult having to try to get a fix out this quickly using code that is in the middle of development.

EDIT: Previous fix is back.

[paysite-cash]

Originally Posted by Roger Clark

It's an issue related to the proxy code. I will have it fixed within the hour. I have deleted the fix above.

I apologize. It's difficult having to try to get a fix out this quickly using code that is in the middle of development.

ok we wait so...

[Roger Clark]

The bug that cropped up in this version causes SOCKS to be selected as your proxy type by default. You can change this in the Network options tab and you should be able to connect fine after that.