Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
George_Ellis
Advisor

R82 SmartConsole (1063) won't start - "Could not load file or assembly..."

I just started a Diamond case, but...
I have some folks getting this error message trying to start the SmartConsole thick app (R82, Build 1063).

Could not load file or assembly
'CP.Management.Objects.Schema.ManagementBl
ade, Version=0.0.0.0, Culture=neutral,
PublicKeyToken=null' or one of its dependencies.
Operation is not supported. (Exception from
HRESULT: Ox80131515)

Has anyone encountered and solved this one?

TIA

Edit - Grok AI says this is probably a Win 11 issue and suggests this command via power-shell

Get-ChildItem -Path "C:\Program Files (x86)\CheckPoint\SmartConsole\R82" -Recurse | Unblock-File

Waiting for one of the folks with the issue to respond.

(1)
4 Replies
the_rock
MVP Diamond
MVP Diamond

I see chatgpt also points to that command as recommended method.

Best,
Andy
"Have a great day and if its not, change it"
George_Ellis
Advisor

Best part is we now have it here in CheckMates.  So if someone has a similar issue, Search at Support should get a hit.

(1)
Lesley
MVP Gold
MVP Gold

Sounds like a local issue. To be sure make sure your account works on other system that have console installed. 

You can try to reinstall SmartConsole. Or clearup some cache:

To resolve the problem, rebuild the local client cache:
Rename the local client cache folder:
For R81 and R81.10 Version:
'%localappdata%\Check Point\R81\SmartConsole\UserSettings' to
'%localappdata%\Check Point\R81\SmartConsole\UserSettings.old'.

For R81.20 Version:
C:\Users\user_name\AppData\Roaming\Check Point\R81.20\SmartConsole\UserSettings to
C:\Users\user_name\AppData\Roaming\Check Point\R81.20\SmartConsole\UserSettings.old
Note - This clears cached settings in the client such as username, server IP address, certificate trust etc.
Relaunch SmartConsole and log into the affected domain server.

-------
Please press "Accept as Solution" if my post solved it 🙂
0 Kudos
George_Ellis
Advisor

It was Windows 11 (2H25) blocking execution as the files were marked as untrusted/blocked during installation.  A reinstall or a change in the permissions fixes it.  It is not cached credentials.

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events