Launchbox 13.12 error during game import

[John Manseau]

Upgraded to windows 10 recently but this error happens when starting Launchbox.

It moves to auto import and gets to the end of the import and fails with this error.

‌

Collection was modified; enumeration operation may not execute.

App: LaunchBox
Version: 13.12
Theme: Default
Type: System.InvalidOperationException
Site: Void ThrowInvalidOperationException_InvalidOperation_EnumFailedVersion()
Source: System.Private.CoreLib

at System.Collections.Generic.List1.Enumerator.MoveNextRare() at System.Linq.Enumerable.SelectListIterator2.MoveNext()
at Unbroken.LaunchBox.Windows.Desktop.MenuActions.ImportRomFilesMenuAction.ReadObservableStatus(Object res, IEnumerable1 pred, Object pool, Boolean ignoreresult2) at UtilsGetter.ChangeTraversalStub(RomImportTask res, IEnumerable1 pred, String pool, Boolean ignoreresult2, UtilsGetter )
at Unbroken.LaunchBox.Windows.Desktop.MenuActions.ImportRomFilesMenuAction.StopObservableStatus(Object last)
at WrapperGetter.ChangeTraversalStub(RomImportTask last, WrapperGetter )
at Unbroken.LaunchBox.Windows.Desktop.MenuActions.ImportRomFilesMenuAction.Finish(RomImportTask task, Boolean autoImported)
at ValGetter.ChangeTraversalStub(RomImportTask task, Boolean autoImported, ValGetter )
at Unbroken.LaunchBox.Windows.Desktop.MenuActions.ImportRomFilesMenuAction.RunExternalTask(RomImportTask task)
at ProcRegistry.ChangeTraversalStub(RomImportTask task, ProcRegistry )
at Unbroken.LaunchBox.Windows.Desktop.LaunchBoxAppSpecific.RunRomImport(RomImportTask task)
at FilterSchemaAttribute.CalcIterableRegistry(Object , RomImportTask task, FilterSchemaAttribute )
at Unbroken.LaunchBox.Windows.Monitoring.GameDirectoryMonitor.ConcatTransactionalSetter()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

Recent Log:

5:06:48 PM Exception

[brian]

Thanks for the report. This should be fixed in the latest beta. You can choose to download the beta and let us know whether that solves the issue for you, or you can wait for the official release.