startupScan full

[artc]

I am unable to set the startupScan property to 'full' permanently.

I set the MinimServer startupScan property to 'full'. I use MinimWatch to rescan the content.

Subsequently, the startupScan property has changed to 'true'. This is not what I expected or want to happen. I don't have confidence that tags I am trying to get rid of are not being processed out of the cache and I must repeatedly rechange the property to full.

Can you shed any light on this?

Thanks.

[simoncn]

This is by design. There is no need to do a full scan every time. This increases rescan times for no benefit. A full rescan should only be needed in exceptional situations. Please explain in more detail your scenario that requires a full scan.

[artc]

(24-08-2025 17:39)simoncn Wrote:  This is by design. There is no need to do a full scan every time. This increases rescan times for no benefit. A full rescan should only be needed in exceptional situations. Please explain in more detail your scenario that requires a full scan.

I don't require a full scan. I had been trying to eliminate possible reasons I could not get rid of erroneous tags that I had added at some point. I saw them in writeAllTags output. I removed the albums in question but the tags remained. So I used full scans to get writeAllTags output that reflected what was on the disk in the extremely unlikely event that the cache did not reflect changes I made to the disk data. After I made a change to my data library, I expected the writeAllTags output to change. When it didn't and the property reverted to 'true' it compounded my confusion.

(My extra tags were caused by an erroneous drag and drop that duplicated the album to an unexpected folder.)

Thanks for your attention.