Groove Music not finding local files

I had the same problem, however, I started windows media player and it found my files! After playing awhile, groove started butting in playing random songs intermittently with WMP. I guess Groove is a slow learner by example of big brother(WMP).

Thanks JuanMiguel! Adding a music folder to onedrive, copying one mp3 to it, adding the folder to where groove looks for music, then restarting groove worked for me. Thanks a bunch Microsoft!!!!

Uhh Guys...

I don't if this will help but...

try removing all the folders in "choose where we look for music"

then re-add them.

After i did that, it starts detecting all of my music

My Groove Music app was working fine until earlier today.  I had it open, as well as Musixmatch Lyrics & Music Player at the same time.  When Musixmatch was updating it's catalog, suddenly the song that Groove was playing stopped and claimed it was not accessible anymore ... then, all songs were not available (all local files on HD) within the Groove Music app.  All other music applications worked fine and all of the music files played if opened individually from the File Explorer.

I tried several of the suggestions from this community feed, among other support sources (i.e.: properties/sharing of folders; resetting app; resetting where Groove looks for files; delete/reinstate music library at OS level; many troubleshooter programs, etc.) ... with no success.  Hours wasted attempting to solve what should be a simple issue fix.

What finally worked for me, is adding one single song to my OneDrive\Music folder ... and my entire Groove Music app catalog re-populated/refreshed instantly and it was fully operational again.  Normally I do not store any music on OneDrive (to reduce downloading/data usage), but, this may be a way to resolve the issue until Microsoft updates the Groove app to include an "Force Update" music catalog button within its settings section.

Hope this work-around offers a resolution for some users.

Thanks & Cheers!

Nope - it worked for a while (several days!) then reverted to the behaviour being described here. Oh well, Windows Media Player works for me, so no really big deal, but kinda scary that Microsoft seems to have no interest in fixing whatever the problem is.