At least I did not have to resort to reinstalling Windows 10.
The Windows desktop that I never put the CREDANT EMS 64-bit encryption on, was the one that I used to setup my bcd536hp with. Originally, that desktop had Windows 8 until I did the Windows 10 upgrade last year. I did remember trying to install the encryption program after the Windows 10 upgrade and it was not compatible with Windows 10 at that time so I never tried to install it anymore.
I had installed it on the other desktop before I upgraded it to Window 10 and apparently it stayed there, which was the same issue with my laptop when I upgraded it from Windows 7 to Windows 10. Basically it was leftover from the previous version of Windows prior to upgrading all of them to Windows 10. And somehow Windows 10 left it there. That's why I figured it had to be doing something with permissions.
Talk about an interesting challenge for sure and the moment of success when I figured out that my two Windows 10 computers that I was having the issue access the SD card, both had the CREDANT EMS 64-bit encryption program on them.
When I removed it from the laptop first, I was also making sure the Sentinel program permissions were the same as the only working Windows desktop. So I made two changes and when I was able to access the card, I thought, what did I just do that fixed it? Then I went over to the other desktop and started adjusting permissions first, trying to recreate the correct fix. Once I removed the encryption program.......SUCCESS!. everything worked like it should.
So, feel free to to add any of this information to the BCDx36HP or any Home Patrol series scanner wiki's regarding... that some encryption programs can interfere with, and cause permission problems for Sentinel tying to access the micro SD card even if the SD card is in a card reader.
It has been a very interesting few weeks since my first post about this issue on July 6th figuring out what was causing the problem.
I hope this information will help others.
Thanks again,
Ed Taylor, ka4vmp