Resolved Intego Virusbarrier fix......!

[MarkC426]

Any bright sparks know what this actually turns off?
Just checking it doesn’t turn off any security features.

chflags restricted /V*/*/private/var/db/KernelExtensionManagement

Intego recommend running this until Apple issue a fix.

 

[bousozoku]

Isn't that for macOS Big Sur?

 

[MarkC426]

It’s supposed to be for High Sierra and Mojave users.

Error: Real-Time Scanning Failed To Load

Note: Please make sure your VirusBarrier software is up to date. The most common cause for this issue is running outdated versions of Intego software:Checking For Updates to Intego SoftwareWhat is...

support.intego.com

 

[casperes1996]

The "restricted" flag puts

Isn't that for macOS Big Sur?

The relevant flag is already set on Big Sur - I googled and Intego talks about this for 10.13 and 10.14

The restricted flag puts something under System Integrity Protection.

* is a wildcard that matches against anything. In this case just used to make it easier for people to run from the Recovery shell. On your actual booted system, the relevant folder is just /private/var/db/KernelExtensionManagement

 

[casperes1996]

As to why this has any influence on Intego's ability to function I have no idea though.
The restricted flag should lock things down further, making it so the root user on the system cannot even modify the data marked with the flag, only the kernel

 

[MarkC426]

Is there any issue running this in Terminal.
Would this affect any other system operation.

 

[bousozoku]

It’s supposed to be for High Sierra and Mojave users.

Error: Real-Time Scanning Failed To Load

Note: Please make sure your VirusBarrier software is up to date. The most common cause for this issue is running outdated versions of Intego software:Checking For Updates to Intego SoftwareWhat is...

support.intego.com

I remember having so much trouble with their software the first couple of releases that I gave up. That was around 2006, maybe.

 

[bousozoku]

The "restricted" flag puts


The relevant flag is already set on Big Sur - I googled and Intego talks about this for 10.13 and 10.14

The restricted flag puts something under System Integrity Protection.

* is a wildcard that matches against anything. In this case just used to make it easier for people to run from the Recovery shell. On your actual booted system, the relevant folder is just /private/var/db/KernelExtensionManagement

I looked also, but it didn't make any sense to me, except to think "Yeah, that's Intego."

 

[MarkC426]

I remember having so much trouble with their software the first couple of releases that I gave up. That was around 2006, maybe.

I have been using Intego since forever and only had an issue 6 months back after a SU.

As for my question, is this command safe to run?
Also can you revert to normal with an nvram reset?

 

[casperes1996]

I have been using Intego since forever and only had an issue 6 months back after a SU.

As for my question, is this command safe to run?
Also can you revert to normal with an nvram reset?

Read what I wrote above about the command.
To revert you would not reset NVRAM, but run the same command again with “unrestricted” instead of restricted

 

[MarkC426]

Thanks dude, I will give it a go...... 👍

Edit: No joy unfortunately, couldn’t get to recovery screen....
screen stays black (non efi gpu).

 

[MarkC426]

edited:
Can you run terminal commands from a different version of MacOS recovery partition.
I have another ssd with HS which has recovery partition, but my main system is Mojave.

Is this command mac level or os level?

 

[casperes1996]

edited:
Can you run terminal commands from a different version of MacOS recovery partition.
I have another ssd with HS which has recovery partition, but my main system is Mojave.

Is this command mac level or os level?

The answer is not straight yes or no in a way.
You're setting a "flag" on the file system. As long as the recovery system knows the flag and can read/write the file system it should all work

Whether chflags can set it on HS I don't know actually

 

[MarkC426]

After swapping drives and rebooting, my ‘other‘ drive looked like no recovery volume.

After some further reading on macrumors forums, I discovered Terminal command diskutil list, which listed all my volumes. My boot drive DOES have a recovery volume......but in ‘not mounted’.

Am I just not waiting long enough after command r restart....?

 

[casperes1996]

After swapping drives and rebooting, my ‘other‘ drive looked like no recovery volume.

After some further reading on macrumors forums, I discovered Terminal command diskutil list, which listed all my volumes. My boot drive DOES have a recovery volume......but in ‘not mounted’.

Am I just not waiting long enough after command r restart....?

The recovery volume is not supposed to be mounted when you’re not booted into it. I would hold cmd-r until something boots. If there’s a recovery it will boot. If there is not macOS will boot eventually

 

[MarkC426]

Success, it took about 10 mins for Recovery screen to appear....🙂
After entering commands in Terminal, Virusbarrier is working normal again.
Many thanks...👍

 

[casperes1996]

Success, it took about 10 mins for Recovery screen to appear....🙂
After entering commands in Terminal, Virusbarrier is working normal again.
Many thanks...👍

Cheers, mate