I had (because it's now deleted) a folder containing some bad FLAC rips. I keep all of my FLAC files in a separate folder (each artist/album in a sub folder). When I use the regular desktop application it imports everything nicely but with a message saying it is unhappy with some files. But when I try the scan with the Metro app it simply crashes - returns to the start page - when it encounters those files. When I deleted the bad files the scan worked well.

Any resolution to this?

I had similar crash when scanning a large library from a NAS (network drive).

Same exact setup worked fine in Desktop MM in Windows 7.1 for many years.

It scans alphabetically, or in the natural order of the album folders. So if you go to the last file, you will probably see a partial album. I don't know why a bad or missing file should stop it, it should just go on . It's unlikely to be a memory issue, I've used two different machines to rule it out.

You can show progress when tap on ring indicator.

I'm not sure what the file is that causes the crash. I couldn't see any indication of how far it got in scanning my library.

I'll try the next version.

Is there any particular file that causes the crash (i.e. some sample mp3 or so)? If not, please wait for the next update, there will be several fixes in the area of memory utilization (and others) which could be the reason for this problem.

Jiri

I have a large external USB drive added to my Music library. It contains about 30,000 tracks. When I scan it for tracks, MM crashes. This still happens with te updated version available on the Windows Store today.

Log Name: Application
Source: Application Error
Date: 12/02/2013 11:25:41
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: HP-TM2-WIN8
Description:
Faulting application name: MediaMonkey.exe, version: 0.0.0.0, time stamp: 0x511563d7
Faulting module name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098858e
Exception code: 0xc0000409
Fault offset: 0x000748e8
Faulting process ID: 0xe44
Faulting application start time: 0x01ce091209daaa5b
Faulting application path: C:\Program Files\WindowsApps\F9C317A9.MediaMonkey_1.0.1.27_x86__6npfwtawc6s18\MediaMonkey.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.110.00_11.0.51106.1_x86__8wekyb3d8bbwe\MSVCR110.dll
Report ID: eeb1d586-7506-11e2-be78-002713594a8c
Faulting package full name: F9C317A9.MediaMonkey_1.0.1.27_x86__6npfwtawc6s18
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-02-12T11:25:41.000000000Z" />
<EventRecordID>2382</EventRecordID>
<Channel>Application</Channel>
<Computer>HP-TM2-WIN8</Computer>
<Security />
</System>
<EventData>
<Data>MediaMonkey.exe</Data>
<Data>0.0.0.0</Data>
<Data>511563d7</Data>
<Data>MSVCR110.dll</Data>
<Data>11.0.51106.1</Data>
<Data>5098858e</Data>
<Data>c0000409</Data>
<Data>000748e8</Data>
<Data>e44</Data>
<Data>01ce091209daaa5b</Data>
<Data>C:\Program Files\WindowsApps\F9C317A9.MediaMonkey_1.0.1.27_x86__6npfwtawc6s18\MediaMonkey.exe</Data>
<Data>C:\Program Files\WindowsApps\Microsoft.VCLibs.110.00_11.0.51106.1_x86__8wekyb3d8bbwe\MSVCR110.dll</Data>
<Data>eeb1d586-7506-11e2-be78-002713594a8c</Data>
<Data>F9C317A9.MediaMonkey_1.0.1.27_x86__6npfwtawc6s18</Data>
<Data>App</Data>
</EventData>
</Event>