# modified but not rescaned. will try later... again
**URL:** https://forum.syncthing.net/t/modified-but-not-rescaned-will-try-later-again/11280
**Category:** Support
**Created:** [February 13, 2018, 9:41am UTC](https://forum.syncthing.net/t/modified-but-not-rescaned-will-try-later-again/11280 "2018-02-13T09:41:50Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@jgomila](https://forum.syncthing.net/u/jgomila)
#### Post date: [February 13, 2018, 9:41am UTC](https://forum.syncthing.net/t/modified-but-not-rescaned-will-try-later-again/11280/1 "2018-02-13T09:41:51Z")
There is a recent post closed. It was published with v0.14.40 version.
> [@finisher: file modified but not rescanned; will try again later](https://forum.syncthing.net/t/finisher-file-modified-but-not-rescanned-will-try-again-later/10916):
>
> Coming from [https://github.com/syncthing/syncthing/issues/4353#issuecomment-341660539](https://github.com/syncthing/syncthing/issues/4353#issuecomment-341660539), I installed v0.14.40-rc.4. I removed my synced folder and added it again. I constantly get following output: finisher: file modified but not rescanned; will try again later However, the file named is not modified on either side.
The last message sais to wait the new version that will fix the error.
I was experiencing this issue since v0.14.43, now I am using v0.14.44 and I have the same error in all my windows servers, with diferent files in diferent folders. I already have 2 linux servers that are up to date.
In all windows servers I have this message at the dashboard with diferent files numbers. |Out of Sync Items|38 items, ~9.51 MiB| |Failed Items|38 items|
Looking at Failed items. For each file: file modified but not rescanned; will try again later
I have 7 servers with 25.000 folders and 640.000 files. I think that change manualy file by file is not the correct solution.
---
### Author:  [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [February 13, 2018, 9:43am UTC](https://forum.syncthing.net/t/modified-but-not-rescaned-will-try-later-again/11280/2 "2018-02-13T09:43:13Z")
Anything particular about those 38 files? Screenshot?
---
### Author:  [@imsodin](https://forum.syncthing.net/u/imsodin)
#### Post date: [February 13, 2018, 9:46am UTC](https://forum.syncthing.net/t/modified-but-not-rescaned-will-try-later-again/11280/3 "2018-02-13T09:46:06Z")
Also mandatory point as you have both windows and linux devices in the same cluster: Did you check the affected paths for case only differences? E.g. device A has /foo/bar/baz and device B /foo/Bar/baz. That badly confuses a windows node and you will need to rename the affected file/dir to resolve the problem.
---
### Author:  [@calmh](https://forum.syncthing.net/u/calmh)
#### Post date: [February 13, 2018, 9:49am UTC](https://forum.syncthing.net/t/modified-but-not-rescaned-will-try-later-again/11280/4 "2018-02-13T09:49:34Z")
… and by “renaming”, that means to something _entirely different_ (not just differing in letter case), _letting it sync_, and then renaming it back to what you want it to actually be called.
---
### Author:  [@jgomila](https://forum.syncthing.net/u/jgomila)
#### Post date: [February 13, 2018, 10:26am UTC](https://forum.syncthing.net/t/modified-but-not-rescaned-will-try-later-again/11280/5 "2018-02-13T10:26:33Z")
Sorry, its a case sensitive problem.
I need to remove all windows servers!!
---
### Author:  [@system](https://forum.syncthing.net/u/system)
#### Post date: [March 15, 2018, 10:26am UTC](https://forum.syncthing.net/t/modified-but-not-rescaned-will-try-later-again/11280/6 "2018-03-15T10:26:47Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.