Stuck on 4.7.3

[Bull_007 1]

I just noticed I'm still on 4.7.3 and there is an update to apply.  I restart to apply, still comes back to 4.7.3 even though the alerts say Emby Server has been updated to 4.7.11.0 and then has the restart the server to finish applying updates.

I downloaded the latest version and was going to update that way, but I'm getting an error that's posted.

Any thoughts? 

[pwhodges 2012]

This usually means a file is being held open, preventing the update from being completed.  The easiest solution is to reboot the host server - is that something you are in a position to do?

Paul

[Bull_007 1]

1 hour ago, pwhodges said:

This usually means a file is being held open, preventing the update from being completed.  The easiest solution is to reboot the host server - is that something you are in a position to do?

Paul

Already rebooted and made sure Emby was fully stopped.

[Happy2Play 9783]

@Bull_007 Do you have any browser links open to Emby while it is shut down?

But you will have to figure out what is holding Emby "system" folder not allowing it to be renamed.

You can get the update from GitHub but will run into the same issues until you figure out what is holding the folder.

Release 4.7.11.0 · MediaBrowser/Emby.Releases (github.com)

 

[Bull_007 1]

Kids were chomping at the bit to watch so my ability to diagnose had to wait.  Turns out it was a single file in the system.old folder for whatever reason it couldn't delete, but I was able to delete it and kick off the upgrade.  Feels silly really, I diagnose better than that when I'm at work.   Maybe this will help someone else that gets a similar error.

[Luke 42083]

3 hours ago, Bull_007 said:

Kids were chomping at the bit to watch so my ability to diagnose had to wait.  Turns out it was a single file in the system.old folder for whatever reason it couldn't delete, but I was able to delete it and kick off the upgrade.  Feels silly really, I diagnose better than that when I'm at work.   Maybe this will help someone else that gets a similar error.

Thanks for the update.