Help / Troubleshooting

The app says Not Responding during a scan or a big job

Windows has greyed out the window and marked it "Not Responding" in the taskbar while a scan is running. Almost every time, the job is still going and nothing has been lost.

The short answer

The work is not happening in the window. When you start a scan, Vesari Stylus hands it to a background thread and the window's only job is to report on it. "Not Responding" is what Windows says about a window that has not answered it quickly enough, and a window busy taking in a large batch of results can miss that beat while the scan underneath carries on.

The likeliest moment for it is the end of a scan, when the app hands the whole updated library across in one go and then tidies up track titles straight afterwards. On a big collection that is a lot to absorb at once. Wait it out. It comes back.

Your music keeps playing throughout. The scan writes to the library on its own connection, separate from the one browsing and playback use, so neither has to queue behind it. Playback is never put on hold in Vesari Stylus.

Where to see that it is still working

The progress toast, bottom right: the folder being read, how many tracks are indexed, the total, and a bar. The count moves in steps rather than smoothly, because tracks are written in batches of around 500. One larger write instead of thousands of tiny ones saves minutes on a NAS.
Tools: the card for the running job (Add Folder, Rescan Library, Super-Tag and the rest) carries a live count and bar. It reads from the shared job list, so it keeps ticking if you navigate away and come back.
Library Health: the same live bar appears on whichever box you started a fix from.
Settings, in the Application Logs panel: filter to Library, or search for "Scan". Every line is timestamped, and new lines appearing means work is happening even when nothing on screen moves.

Stopping a scan on purpose

Open Tools.
On the card for the running job, choose Stop.
The card reads Stopping… until the job winds down.

Stop is a request, not a kill. It raises a flag the scan checks between saved batches and at each folder boundary, so it finishes what it is holding and stops at a safe point. Everything indexed up to that moment is kept.

A stopped scan also never removes anything from your library. A scan that runs to the end compares what it found on disk against what is in the library and clears out what has genuinely gone. An interrupted scan has not seen your whole collection, so the app skips that comparison rather than treat unvisited folders as missing. The follow-up passes are skipped for the same reason: duplicate marking, artwork, cover thumbnails, and the ReplayGain pass if you have the automatic one switched on. A later Rescan Library picks all of it up.

The same Stop control appears on the other long jobs, including Super-Tag, ReplayGain, WAV repair and lyrics fetching.

Why one job looks blocked by another

By default the heavy jobs run one at a time. A second one shows Queued… and starts when the first finishes, so that several heavy passes at once cannot bring an older machine to its knees. If you have a fast multi-core PC and would rather they overlap, turn on Allow concurrent scans in Settings.

A sense of scale

Vesari Stylus is built for libraries in the tens of thousands of tracks. The first pass reads every file once, so minutes rather than seconds is normal, and a NAS is slower than a local drive. After the walk there is a tail of work (duplicates, artwork, thumbnails) during which the counter can sit still while the app is still busy.

When it genuinely is stuck

Two things together are the real signal: the count has not moved, and no new library lines are appearing in the log for a long stretch.

Before assuming a fault, check two common causes:

A folder that is offline. If a drive or NAS root cannot be reached, Tools shows an offline banner, and a dropped share is named in a banner across the top of the app. Each unreachable location is probed a few times before the app gives up, so a couple of dead roots can hold up the start of a scan by about ten seconds each.
Running as administrator. An elevated app cannot see your mapped network drives. Vesari Stylus recognises this and shows a message saying what to change. Run it normally rather than as admin.

If neither fits, press Stop, or close the window. Closing while work is running asks first: Close while work is running?, with Close anyway and Keep working. Reopen, run Rescan Library, and carry on. Everything already indexed is still there.

If a scan hangs on the same folder every time, that is worth telling us about. See Is this a bug? How to report it, and mention the folder and roughly how many tracks it holds.

← All help articles