Some folks with wav files on CF and SD media are experiencing problems with Windows 10 corrupting files making them unusable and/or destroying the metadata. Microsoft isn't being much help.

http://answers.microsoft.com/en-us/windows/forum/windows_10-files/transferring-wav-audio-files/50bbf42f-84a7-44b9-ab57-8784b5606d09?msgId=f1d49ae7-d869-49a5-baa4-82582882e9bf&page=1

windows 7 still rules...

I miss Paper Clip Man

Thanks for the heads up, Jim.

I have a similar problem with a usb 3 card reader corrupting video on exFAT sd cards. I wouldn't have believed the act of reading a card could destroy the data on it.

More horror stories...

https://www.gearslutz.com/board/11260477-post8.html

You would have had the card in there for the purpose of reading the data (and not saving anything to it), but the operating system will pro-actively index the content of the files. Some of this information will be written to hidden files to minimise this processing the next time the media is added. This writing back to the media (in order to store these cache information files) could be how the errors are being introduced.

Disclosure: I don't use Windows 10 and will stay with Win 7 until they pry it from my cold dead hands. It simply works.

Andrew

Is this like the Star Trek movies where only the odd-numbered ones were good?
(Or was it the even-number movies?)

I have found what appears to be a legitimate source of information for removing the "entangled" built-in Windows 10 apps (including Groove Player, aka. "Zune")

https://thomas.vanhoutte.be/miniblog/delete-windows-10-apps/

I followed the directions for:
"Remove Groove Music and Film & TV from Windows 10" and
"Remove Solitaire Collection from Windows 10"
and they appeared to complete without anything that looked like an error message.

When I did...
"Remove Xbox from Windows 10"
it showed a big mess of error messages in red, however the Vanhoutte instructions say those "error messages are normal"

Note that this appears to remove the alleged offender (Groove Player aka. Zune).
HOWEVER, I have not seen the problem and have NOT been able to test whether it may prevent the reported problem.

The Vanhoutte website also contains other useful things like "Find your Windows 10 product key" which I plan to investigate.

Info from someone at Microsoft...

https://www.gearslutz.com/board/11262573-post18.html

They would like details so they can reproduce the problem and then fix it.

Latest word from the guy at Microsoft....
Update on this. It's definitely not Groove or anything related to scanning music files or similar. It's also not necessarily related to any specific card reader. We're working with Sound Devices to come up with a fix here. More on that as we have something more concrete to share.
https://www.gearslutz.com/board/11268471-post39.html

They have isolated it (at least one identifiable case) to files written by Sound Devices gear. SD is working with MS to identify the problem so it can be fixed.

Pete who works with Microsoft is keeping this GearSlutz thread updated...
https://www.gearslutz.com/board/remote-possibilities-acoustic-music-location-recording/1024804-windows-10-corrupting-audio-files.html

Also on this Microsoft forum...
http://answers.microsoft.com/en-us/windows/forum/windows_10-files/transferring-wav-audio-files/50bbf42f-84a7-44b9-ab57-8784b5606d09

Posted on the SoundDevices website....

Sound Devices Technical Alert
We have confirmed user reports of a serious issue with Windows 10 and removable media formatted as FAT32. Users are experiencing corruption of .wav media files by simply inserting FAT32 formatted SD or CF cards into a Windows 10 computer. Files do not need to be opened or accessed in order for them to become corrupt.

This problem has been reported to Microsoft. If we learn of any new information we will share it at the earliest. Thank you for your continued support!

Sound Devices Technical Alert - Sound Devices, LLC | Audio Production Products (http://www.sounddevices.com/news/sound-devices-news/sound-devices-technical-alert)

It's all sorted (or being sorted) now.

It seems Sound Devices set a Microsoft only bit at "1" when it should have been "0".

Microsoft, starting with Windows 10, set this bit at "1" to denote an encrypted file - which is whare the problem started with Sound Devices files.

Windows are doing a modificationto W10 so it won't happen in the future - I think they will do a double-check to make sure the file is encrypted.

Sound Devices have all the info now so they can do a fix from their end and set the bit correctly to "0".

Windows is working on a program that will fix damaged files - but only to be used after the update to W10 is launched.

Full details are on Gearslutz as the guy from Mirosoft has been posting there.