# Syncthing v0.14.22 & v0.14.23

**URL:** https://forum.syncthing.net/t/syncthing-v0-14-22-v0-14-23/9182
**Category:** Release
**Created:** [February 7, 2017, 9:44am UTC](https://forum.syncthing.net/t/syncthing-v0-14-22-v0-14-23/9182 "2017-02-07T09:44:04Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![calmh](https://forum.syncthing.net/user_avatar/forum.syncthing.net/calmh/32/15311_2.png) [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [February 7, 2017, 7:39pm UTC](https://forum.syncthing.net/t/syncthing-v0-14-22-v0-14-23/9182/6 "2017-02-07T19:39:06Z")

</div>

I pulled back this release due to

> [@Exit after update](https://forum.syncthing.net/t/exit-after-update/9188):
>
> Hello, Today Syncthing was not running on my servers, found this in logs 2017/02/07 11:39:30 INFO: Automatic upgrade (current "v0.14.21" \< latest "v0.14.22") 2017/02/07 11:39:34 WARNING: Automatically upgraded to version "v0.14.22". Restarting in 1 minute. 2017/02/07 11:40:34 INFO: Exiting Manual start was necessary. No errors found, all seems to work as usual, no prior changes in config/network/user permissions, etc. Happened on multiple computers (one of them with manual update) Only simila…

and will post a v0.14.23 once this is solved. It “only” affects users running syncthing manually, without a service manager. Nonetheless, it’s better to pause the upgrading for those not yet on v0.14.22 and allow them to get a fixed version directly.

Man, auto upgrade issues are the worst. Sorry.

---

_[View the full topic](https://forum.syncthing.net/t/syncthing-v0-14-22-v0-14-23/9182)._