Jump to content

Emby Won't Restart To Finish Installing v. 3.2.31.0


Go to solution Solved by Luke,

Recommended Posts

Posted

I click restart and it shuts down the server but it doesn't come back.  If I manually start it back up it shows that it still hasn't installed the downloaded V 3.2.31.0

 

I tried what was suggested in the other thread buy deleting: C:\Users\gen_m\AppData\Roaming\Emby-Server\data\notifications.db.  That did not work...

Posted

Mine also didn't restart properly after the update. But now that I've manually started it it is on the latest version.

Posted

No such luck for me.  I tried shutting down and restarting the PC as well as installing it directly from the website on top of my installation and it still won't work.  I get the "Could not move system directory to backup" Error.

Posted

Try installing the latest from the website on top of your current version. Thanks.

Posted

What does "didn't work" mean? What exactly happened?

Posted

No such luck for me.  I tried shutting down and restarting the PC as well as installing it directly from the website on top of my installation and it still won't work.  I get the "Could not move system directory to backup" Error.

Posted

Where did you get that error? Did you get a message box? Thanks.

Posted

Yes the dialog box opened up when it was trying to extract the package

  • Solution
Posted

Try rebooting your machine again, make sure the server isn't running when you try and do this. Most likely you either have the server running, or you have a windows explorer window open in the folder that needs to be updated and this is causing a lock.

  • Like 1
Posted

Manually rename your system.old to system.older and then reinstall.

Posted

Manually rename your system.old to system.older and then reinstall.

 

No, we don't want users to have to undertake procedures like this. Please do not do this. Thanks.

Posted

Well the error was "Could not move system directory to backup", which is when the "system" gets renamed as "system.old”.

 

Just thought it was having an issue doing the rename.

Posted

Well either way, I did both suggestions and the install went through. Thanks guys

  • Like 1
Posted

Try rebooting your machine again, make sure the server isn't running when you try and do this. Most likely you either have the server running, or you have a windows explorer window open in the folder that needs to be updated and this is causing a lock.

Just had this problem, too, and this was the reason.

 

Posted

Right, we can't delete the folder if you've got it open in windows explorer. 

 

Best thing to do - just trust the process and avoid poking around the folders with the executables.

Posted (edited)

Just a short comment - I've seen the same when upgrading to 3.2.30.24 and 3.2.31.0.

And I have never seen it before, so "something" is different.

 

I do a manual update by exit'ing Emby Server via the systray icon and then running setup.exe.

I had nothing open in the GUI or elsewhere. 

My guess was that I had not given Emby Server application/Windows sufficient time to close all handles.

For me the problem was no bigger than running setup.exe again after a moment.

 

Does Emby setup check for running instances?

Edited by pju
Posted

The installer might not. The uninstalled does.

  • 3 months later...
Posted (edited)

I just noticed I am stuck on 3.2.36 with a similar problem. It says 3.2.60 is installed and to restart to finish the install. When I do, emby stops but won't restart. I have tried many different iterations of shutting down/restarting emby and rebooting the PC (with emby shut down) but nothing fixes this. Any new ideas? I know Luke said not to mess with things and trust the process -- but that isn't working.

Edited by bcm00re
Posted

Thanks Luke! Is there a way to setup to have my emby server email me when it gets stuck on a version? I didn't even know this was happening until I started seeing missed recording. Sadly I missed the first episode of this latest season of X-Files...really bummed about that!

Posted

Apologies. This was a one-time problem due to a major internal change within the server. Future updates will not be as dramatic. Thanks.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...