Question / Help Update failing -- ?

[Chromatic]

Hi,

I am using OBS 0.542b -- This is the last version that updated.

I am using Windows 7 - 64 Bit OS, on an Intel i5 processor if it is relevant.

Now, when I load it, it prompts for update -- it downloads the update,.. and installs and gets to the very end 100%, then the progress bar goes RED and says something like failed to update, cannot move something (or it may say cannot write) something to that extent.

I would post the exact message, but I run a 24/7 stream and cannot take it down.

If I must take down the stream to get the update message I will.. but does anyone have any experience with this, and any ideas as how to resolve it? So I can update ? I don't know what improvements have been made since 0.542b -- (anywhere I can find a list of what the updates did?) But, I love the software, and it is Genius! So I like to keep it updated.

If I can get around this error by manually downloading and updating that way I will..

It updated just fine up until this version, and nothing has changed whatsoever on the computer that OBS is on.. I can verify this as it is used as a server to stream .. so nothing is ever added to it, nor any remote processes, firewalls, or antivirus runs.

I don't have any file permission problems, so not real sure why there would be a problem here.

All I have done to try and remedy this in the past is to shut down the computer entirely.. and reboot, have no other software open and then opening OBS and doing the update that way "cleanly" .. but same problem.

Not a major ordeal,.. but of course I would like to stay current.

Thanks for any ideas/help!

 

[R1CH]

You can't update OBS while it is running, you will need to take your stream down to update. The updater shouldn't even let you try to update if OBS is open.

 

[Chromatic]

You can't update OBS while it is running, you will need to take your stream down to update. The updater shouldn't even let you try to update if OBS is open.

Perhaps I just wasn't clear enough in my initial post,.. I apologize.

I am not trying to update with it running. I shutdown completely and restart the computer itself,.. and just open OBS which will prompt the update.. and say Yes to update (no stream running).. and it will fail as I reported.

 

[Xphome]

While it doesn't solve your updater issues, can't you just download the latest version from the website?

 

[R1CH]

You can't update OBS while it is running, you will need to take your stream down to update. The updater shouldn't even let you try to update if OBS is open.

Perhaps I just wasn't clear enough in my initial post,.. I apologize.

I am not trying to update with it running. I shutdown completely and restart the computer itself,.. and just open OBS which will prompt the update.. and say Yes to update (no stream running).. and it will fail as I reported.

Can you include the exact message you get?

 

[Chromatic]

I will have to drop my stream. I will do so,.. as I am more interested in resolving a potential problem/bug than just getting around it with a manual download. I will do this when the stream isn't in primetime.

Thanks for the help so far.

Also -- Any links, etc that show exactly what has changed since my current: OBS 0.542b version?

Take care,

 

[Chromatic]

Well... it completely stopped trying to auto-update. No idea why. So I couldn't pull the error message it was giving me,.. go figure.

Where do I go to change the .ini settings that aren't in the regular setting options in the program GUI?

I looked through the changelog to see the changes.

So using OBS 0.571b at the moment.

 

[Krazy]

0.571b is the latest version.

For future reference, if the auto updater thing fails to prompt, you can go to global.ini in %appdata%\obs and remove the numbers next to "LastUpdateCheck64" and "LastUpdateCheck" to force it to check again.

Though, I do believe R1CH has added an option to manually check for updates somewhere in the OBS menus. Should be in for next version.

 

[Chromatic]

Thank you, Krazy.

 

[R1CH]

It's possible if your system clock jumped somehow that the update check might not run, but it sounds like your issue is the updater didn't actually update after running. I'd need to see the actual error though to find out why.

 

[Chromatic]

Thanks for replying and staying on top of things.

I manually upgraded to 0.571b -- We will see how the auto update goes from here on out. If it is a system problem then it should have the same issue when the next auto-update comes around. If it's something with the program (which I think is unlikely given the isolation of my issue) .. maybe we can figure that out.

Curious.. does 0.571b have the auto-update working? I remember reading that one of these versions had it non functional and would be re-added in the next.

Thanks.

 

[Krazy]

It was only 553b that accidentally disabled the auto-updater.

 

[Chromatic]

Gracious.