hoakley July 30, 2019 Macs, Technology

SilentKnight Support

This page is for your support questions and comments on my free tool SilentKnight.

Full details, current versions, known issues, and much more about SilentKnight, its command tool equivalent silnite, LockRattler and SystHist are on this page.

Please read the SilentKnight and silnite: FAQ.

You can also email me if you prefer: my address is given in the About page for this blog.

9Comments

Add yours

1

siglidne müller on July 31, 2019 at 5:42 pm

hey! there is a difference in gatekeeper version. newest version from apple is 175 but silentnight means it is 173. unfortunately i can´t send an attachment here.

siglidne

LikeLiked by 1 person
- 2
  
  hoakley on July 31, 2019 at 5:54 pm
  
  Thank you – I was updating the database as you were writing your comment!
  Actually, this is more complex: as I noted in the posting about the update, the installer claims it’s version 174, but the update itself brings the bundle to 175. Anyone relying on the installer version is going to be mighty confused.
  Howard.
  
  LikeLike
3

richardiproctor on August 1, 2019 at 3:08 am

When firing up SilentKnight it starts automaticially and starts looking for updates, which i don’t have problem with. Once it’s finished and you want to see if the uppdate(s) have been installed, you have to close the app and fire it up again, so what is the “Ckeck” buttom for. It doesn’t seem to do anything.

LikeLiked by 1 person
- 4
  
  hoakley on August 1, 2019 at 5:49 am
  
  Thank you.
  This is documented in the Help book. The issue is a ‘feature’ in macOS which I have been trying to work around for over a year, and frankly it’s just an insurmountable bug in macOS. So yes, to see updated version numbers after an update has been installed, you have to quit the app and open it again. I’m sorry – I can’t fix bugs in macOS!
  Howard.
  
  LikeLike
5

richardiproctor on August 1, 2019 at 10:46 am

Thanks for the answer.

LikeLiked by 1 person
- 6
  
  hoakley on August 1, 2019 at 4:18 pm
  
  No problems – hopefully today’s FAQ has explained a bit more. I’ve wasted a great deal of time trying to find a way around this, and was thinking about using the installer version as a temporary substitute, although I know it’s unreliable. Then last night Apple released that Gatekeeper update with the wrong installer version number, and I realised that sticking to my guns was irritating to users but actually most accurate. This bug even affects the Finder’s version display of version numbers.
  Howard.
  
  LikeLike
7

Ingo on October 4, 2019 at 3:15 pm

Hi, I think I observed a bug in SilentKnight 12 which I try to explain by an example:

“Automatically Check for Updates” was unchecked on my MacBook Air since mid of September. So the latest updates for XProtect and MRT were not installed when I called SilentKnight a few days ago.

Though SilentKnight identified XProtect Version 2103 correctly as one of the latest updates installed on my computer it said “XProtect 2104 should be 2106” (see the report down below). Lockrattler421 made a similar error.
By the way: Has XProtect 2104 ever been delivered to Macs with macOS 10.14.x?

SilentKnight V12 Check Result 2019-10-02, 20:17 UTC
✅ System Integrity Protection status: enabled.
✅ XProtect assessments enabled
⚠️ FileVault is Off.
macOS Version 10.14.6 (Build 18G103)
Latest updates installed:
XProtect 2019-05-02 06:31:44 +0000 : 2103
Gatekeeper 2019-08-28 12:48:32 +0000 : 181
MRT 2019-09-12 23:12:29 +0000 : 1.49
TCC 2019-06-04 22:11:55 +0000 : 17.0
KEXT block 2016-11-03 20:40:07 +0000 : 12.1.2
Mac model MacBookAir6,2
EFI version found 117.0.0.0.0
✅ EFI firmware appears up to date.
❌ XProtect 2104 should be 2106
✅ Gatekeeper 181 should be 181
❌ MRT 1.49 should be 1.50
✅ TCC 17.0 should be 17.0
✅ KEXT 14.5.1 should be 14.5.1
⚠️ Software Update Tool

Finding available software
Software Update found the following new or updated software:
* XProtectPlistConfigData_10_14-2106
XProtectPlistConfigData (2106), 68K [recommended]
* MRTConfigData_10_14-1.50
MRTConfigData (1.50), 4100K [recommended]

LikeLiked by 1 person
- 8
  
  hoakley on October 4, 2019 at 3:22 pm
  
  Thank you.
  No, that’s not a bug at all. Apple delivered XProtect 2104 within the 10.14.6 update, bundled within the main install. So you won’t see it listed separately, as (unusually) it wasn’t provided as a separate installer package, and doesn’t appear in SystHist, for example. However as you applied that update, the XProtect version number reported is correct.
  Sorry – sometimes updates confuse.
  Howard.
  
  LikeLike
  - 9
    
    Ingo on October 5, 2019 at 12:18 pm
    
    Ah, OK. Thank you, Howard.
    Ingo
    
    LikeLiked by 1 person

·Comments are closed.

Share this:

Related