NP350V5C Windows 8.1 Secure Boot Update Problem

Hi all, I am literally at my wits end in trying to sort out a problem that I was wondering if any one else has come across (apologies in advance for the long explanation).

I accidentally visited a phishing site recently that was absolutely filled with malware and was apparently run by a notorious group of hackers. After this I noticed my mouse cursor became very jerky and despite running a few malware scans which came up blank I was a spooked so I deleted all HDD partitions and reinstalled windows.

Cue the problem, every Windows update installs fine EXCEPT for KB3172729 which which fails with the error code 800F0922. This update relates to the Secure Boot blacklist and the failure is meant to indicate that there are non-compliant modules present in the UEFI. I tried re-flashing the UEFI and restoring all settings to factory defaults but the update still keeps failing. The thing that has me paranoid is that it had no issues before!

There is a workaround where you can disable secure boot and then install the update but seeing there was never any issues before it's sort of raised a red flag for me as apparently UEFI rootkits are a thing now and I don't see why it should suddenly fail to install.

So I was wondering for anyone with a Samsung notebook and Windows 8.1, have you had any issues with this (or similar) updates? Or any tips as to what to do? Thanks!!

 

Did your NP350V5C original ship with Windows 7 or Windows 8. The former (BIOS number AA***) did not have UEFI enabled and it is best to not enable it as it was very buggy. The Windows 8 notebooks were shipped with a new BIOS (AB***) with an improved (but still buggy) UEFI. The worst bugs were gradually removed by a series of BIOS updates. You can check if you are up to date using the advice here. Or it may be that you have found a new incompatibility bug.

John

 

Hi John, thanks for responding.

My laptop came with Windows 8 and the current bios is P09ABE which appears to be the latest one according to the Samsung Software Update...

I also tried running an Intel utility called CHIPSEC which scans UEFI for vulnerabilities and it came up with:

Variables with attributes that differ from UEFI spec: ErrOut, SignatureSupport, SetupMode, SecureBoot

It would make sense if it was just Samsung's bad implementation that was causing issues, (or as you said it could be buggy) but it's still odd that the update worked before with no issues