Privatus claimed as damaged after reboot, works well otherwise.

[macpingel]

Hi,
I am using Privatus 6.6.2 (AppStore) on macOS 13.6.5. Privatus is set to start up at login.
When I boot up the Mac, I get a message that Privatus is damaged, and needs to be reloaded from the AppStore.
I did this about a dozen times, but the error message on boot persists. When I start Privatus manually after boot, it works as expected with no error messages at all.
When I log out and back in, Privatus starts up as expected.
Only from a cold boot or restart I get the error message.
Any ideas how to fix this?

[macpingel]

I forgot: Safari is 17.4, but I think this doen't matter for this problem.

[SweetP]

hmm, that's strange

[macpingel]

It seems to happen when PrivatusHelper tries to start Privatus itself, as I find PrivatusHelper running in Activity Monitor.

[SweetP]

I’ll see if I can recreate this. Is your Mac Intel, or Apple silicon?

[macpingel]

Sorry, very obvious info: It's a mini M2 Pro.

[SweetP]

Ah good, I have a MacBook Air M2.. That will rule out any processor differences. Although I’m running macOS 14.4. If I see no issues in Sonoma, I’ll install macOS 13 in a virtual machine and see if it makes a difference

[macpingel]

Thanks for the quick response. I run the same Version of Privatus on 14.4 without any problem.

[SweetP]

Interesting, thanks

[macpingel]

It just leaves the Cache Data in Safari, will that be fixed by Privatus 7?

[SweetP]

Oh,
I missed that this was Privatus 6…
yeah Privatus 7 has support for Safari 17.

[macpingel]

So I should try to Update first?

[SweetP]

V7 was a paid upgrade.

I’ll still take a look, but if I can reproduce it, I will only apply the fix to Privatus 7. Privatus 6 isn’t in the App Store anymore.

[macpingel]

I know I tried to find clear info if v7 was necessary, but didn't find any. I'll be back in 5 Minutes.

[macpingel]

Funny thing, same error with 7.0.2
The difference between the 14.4 and the 13.6.5 machines is that the machine with the error (13.6.5) is set to auto-login.

[SweetP]

im install macOS 13 now.
ill see if I see any problems

[SweetP]

I don't get any issues on macOS 13, with Privatus 7....
although I am testing the trial version.

• what are your Privatus settings?
• how are you configuring start at login - via Privatus settings, or using System settings?

[macpingel]

All set in Privatus. Checked in system settings that they are enabled.

[SweetP]

strange,

ok, ill try the App Store version now

[macpingel]

After reboot