I installed both and I still have the same issue.
Edit: Also looks like it is a widespread problem with Samsung Magician and the Anniversary Update (and later of Windows 10 versions...). Take a look here and here and here. Even TenForums has a post about this issue:
Widespread bug FYI - https://forums.whirlpool.net.au/foru....cfm?t=2556634 - see UPDATE paragraph at bottom!
Just after I updated my Asus laptop from Windows 10 1511 to Windows 10 1607 (1 year anniversary update) a virus was detected by Windows Defender, so I immediately shut down and performed a reformat via Windows-10-install USB stick, as I was going to reformat anyway. I wish I noted down now what it detected because i've had an issue since.
Samsung Magician v4.9.7 now reports 'AHCI mode disabled/deactivated' and 'unable to detect SATA' (I use a Samsung 850 PRO SSD). After much testing, I found what makes it report this is when in my Asus laptop UEFI BIOS I have 'secure boot' enabled. When secure boot in BIOS is disabled, AHCI mode and SATA detect reports working normally again.
Error - AHCI disabled/deactivated and SATA not detected/EUFI BIOS secure boot enabled - Imgur: The most awesome images on the Internet
No error - AHCI enabled and SATA detected/UEFI BIOS secure boot disabled - Imgur: The most awesome images on the Internet
Samsung driver not digitally signed error that began at same time - Imgur: The most awesome images on the Internet
I've tried many MBR fixes via command line via repair your computer when booting from Windows install USB but it seems after much reading that my UEFI laptop uses something different and I can't modify it?
I have secure boot enabled whenever the laptop might be online so it would have been enabled when the virus alert popped up, so in theory the boot sector should have been protected?
So i'm not sure if I might have an infected or invalid boot sector, if the Windows 1607 anniversary update did something, Samsung Magician is misreporting, or something else is causing this.
Note that my Windows copy is legit/has a legit key stored in BIOS (for laptop) which came with the laptop purchase. It's not recommended nor a solution to simply leave secure boot disabled (eg: reason above) so i'm not sure how to proceed from here...
UPDATE: Ahh, looks like others with Samsung Magician v4.9.7 who have installed the 1-year anniversary update for Windows 10 have also suddenly started getting the same issue. So looks like it's up to Microsoft and/or Samsung to rectify. I'm just very happy that it has turned out to be an issue not at my end. See results at Google