michael_lee3

Mark - I hadn't thought of trying that. Indeed, when I had attempted to use EOS Utility it would hang, and then not completely transfer all the RAW files on the card. File Explorer is absolutely consistent, in that it does not recognize the CR2 files (as shown in that screenshot). I'm thinking more and more that it is a 50D and Windows 10 UDMA 7 compatibility thing, and not something that can be fixed (as far as a direct USB connection is concerned). Thanks.

Marcus - Yes, with non-UDMA 7 cards Windows 10 sees the RAWs via USB from the camera. While I've always just had to carry along a USB cable to transfer files wherever I am, it looks like I'll have to also carry a card reader from now on. This was the first UDMA 7 card I ever purchased, and this is strange behavior for sure, but nothing surprises me much any more with Windows 10. Thanks for your input and suggestion.

I have a strange issue which neither Canon or SanDisk customer support can explain or help me with. I work on a Windows 10 Pro machine. I just yesterday purchased a 32GB SanDisk Extreme UDMA 7 Enabled CF card. I shot several RAW & JPEG photos and connected my camera to my computer with a USB cable and opened File Explorer. When viewing the files on the card NO CR2 files were present, only JPEG files. There were indeed other files which should have been the CR2 files, but Windows showed them as 0 byte files, without a name or file extension. These "0 byte" files can not be moved or copied. If I place the card in a card reader the CR2 files are present as they should be. I can connect the camera to a Windows 7 machine with a USB cable and Windows Explorer sees the CR2 files properly. Has anyone else noticed such behavior with a UDMA 7 card and Windows 10? Oh, and I do have the latest 1.0.9 firmware installed. The screenshot shows what should be IMG_0190.CR2. I use FastStone as my default JPG viewer, hence the "FastStone JPG File".