Microsoft has released a new version of its Groove Music app (version 3.6.1210.0) for Windows 10. They’ve also introduced yet another bug into it, a showstopper, as far as I’m concerned.
Groove keeps losing my entire album collection, and trying to rebuild it in a never-ending cycle.
I have 1,000+ albums stored on a Windows Home Server 2011 system, and connected to it are four Windows PCs (desktop, laptop, a Windows Tablet and a Surface 3), all running Groove and Windows 10. On each of the connected devices, the root music folder on the WHS2011 system is defined as a music library (and hence defined as a watched folder – in my case, \\DEGAS\Music – within Groove on each system).
Now that all the instances of Groove have been updated to version 220.127.116.11.0, what will happen is that when I’m viewing my Albums, the albums will suddenly disappear, Groove will say there are zero albums available offline, and display the “Get some music” message.
After some time (30 minutes?), or a restart of the app, Groove will start re-indexing the music folders and albums will start appearing.
This goes on (slowly!) until all the albums have been scanned from the WHS2011 folders, at which point they will all suddenly disappear again and the process starts over.
This is happening on
three all four of the PCs. Interestingly, the Surface 3 is not losing the albums. However, it’s also not displaying the correct number of albums held in my music library. I have 1,103 albums in my collection; according to Groove on the Surface 3, I only have 1,084. I suspect that this instance of Groove isn’t actually watching my watched folders… Addendum: I forced the Groove on the Surface 3 to rebuild its index, and now the same thing is happening on the Surface 3 as on the other PCs.
The 18.104.22.168.0 version of Groove is also not always displaying the “Adding music” notification when music is being added.
I feel that Microsoft is not testing this app sufficiently well; I wonder whether anyone on the testing team bothers to test it with a library held on a Windows Home Server 2011 system.
I don’t mind being a beta tester when software is in beta; but Windows 10 and the Microsoft apps are now released. Groove is still not fit for purpose.
I have also sent this information in as feedback to Microsoft via the Windows 10 Feedback app. Whether this will result in a fix remains to be seen.
Apparently, Microsoft has stated that for Windows 10 Home users, all operating system and app updates will be automatically installed, and this cannot be overridden by the user. That’s a bit worrying, since a bug in a new component can cause immediate damage. We don’t get the option to delay updates and check whether it’s safe to let installations proceed.
Addendum 18 August 2015: Groove is now up to version 3.6.1239.0, but the issue is still present…
Other people are also reporting this issue occurring for music collections held on both WHS 2011 and Windows Server 2012 systems, so I’m not the only one for whom this is a showstopper.
Addendum 19 August 2015: This latest version of Groove running on my Surface 3 refuses to find any local files (including the collection on WHS 2011) at all. And it’s a hit and miss affair on my other systems as well. Groove on my desktop claims my collection has 1,109 albums available offline; on my Yoga 3 Pro, Groove says I have 1,112 albums, and on my ThinkPad 10, Groove says I have just 644 albums.
Addendum 20 August 2015: after 36 hours(!) of adding files, Groove on my ThinkPad 10 now says I have 1,108 albums available offline. So what’s it to be? 1,109, 1,112, or 1,108? All instances of Groove are looking at exactly the same collection; one might think that they could agree on the correct total of albums. Oh, wait a minute, Groove on the Desktop PC has just lost the index again, and has restarted to index the collection, While Groove on the Surface 3 still resolutely refuses to see any albums at all…
I’m sorry, but this software is absymal.