[Solved] Some 14271 & Samsung Magician info to pass on...

Discussion in 'Windows 10' started by WaltC, Mar 3, 2016.

  1. WaltC

    WaltC MDL Addicted

    Mar 8, 2014
    518
    123
    30
    #1 WaltC, Mar 3, 2016
    Last edited: Mar 4, 2016
    Build 14271--A recent problem I've had with this build is that when Secure Boot is enabled it interferes with the Samsung Magician software for my EVO 850 250GB boot drive, so that even though AHCI mode is selected for in the bios and supported through Windows, the Samsung Magician software claims it cannot detect any AHCI in the system or read any SATA device information. This started happening just yesterday. The event log identified the problem as the Samsung drivers in Magician being unsigned and as such Secure Boot will not permit the Magician software (4.9.5--the most recent from Samsung) to run its SATA detection routines--so Magician thinks there is no SATA or AHCI in the system. I restored 14271 from a backup to a freshly formatted c:\ (EVO 850) and found that measure ineffective (IE, proving it wasn't malware or damaged files, etc,.) Only thing that works is disabling secure boot--but since I know what the trouble is and that it is superficial (AHCI & Sata are functioning fine in my system) I'll ignore it until the next build. Seems to be a definite bug, though. Weird, how it only just started happening out of the blue...! I gave 'em Feedback on this...

    Edit: I am happy to report that build 14276 has resolved this little problem!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. LatinMcG

    LatinMcG Bios Borker

    Feb 27, 2011
    5,356
    1,446
    180
    hmm and it wasnt signature related ?
    sometimes bios is looking for specific.. remove and re add efi entry ? :confused:
     
  3. SpeedDream

    SpeedDream MDL Addicted

    Feb 20, 2012
    620
    121
    30
    thanks for your post, I discovered the same with and happened with ltsb too,
    hardware:

    h97m-e
    samsung 850 drive
    magician 4.9.5

     
  4. dwarfer66

    dwarfer66 MDL Novice

    Jun 1, 2015
    44
    7
    0
    I have the exact same problem mate.
     
  5. WaltC

    WaltC MDL Addicted

    Mar 8, 2014
    518
    123
    30

    I don't think it was...many times the component that an OS identifies as the cause of a bug actually isn't, I've found...;) Sometimes it is right on the money sometimes it is way off. If it had been a genuine signature problem it would have manifested all along--which it didn't. Probably some garbage related to UWP, I'll guess.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...