So far I tried repairing the application but that has not helped. I have also gone through similar questions but with much newer versions of SSMS, but my version does not have the files they mention, for example:
One solution was the find a file called “ssms.exe.config”,which in my case is called “ssmsee.exe.”, to remove a line that my config file does not have.
Another solution was to copy a file from the directory: CProgram Files(86)….IDEPrivateAssembliesInterop to a different folder, but I do not have folder PrivateAssemblies or even the file they mentioned.

I managed to locate the log file but I could not make sense of it myself , see below

    Dec 10 2010 10:56:29 
    Copyright (c) 1988-2005 Microsoft Corporation
    Express Edition on Windows NT 6.2 (Build 9200: )

2024-07-03 11:17:58.51 Server      (c) 2005 Microsoft Corporation.
2024-07-03 11:17:58.51 Server      All rights reserved.
2024-07-03 11:17:58.51 Server      Server process ID is 4140.
2024-07-03 11:17:58.51 Server      Authentication mode is MIXED.
2024-07-03 11:17:58.51 Server      Logging SQL Server messages in file 'c:Program Files (x86)Microsoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'.
2024-07-03 11:17:58.51 Server      This instance of SQL Server last reported using a process ID of 4396 at 7/3/2024 11:17:14 AM (local) 7/3/2024 9:17:14 AM (UTC). This is an informational message only; no user action is required.
2024-07-03 11:17:58.51 Server      Registry startup parameters:
2024-07-03 11:17:58.51 Server        -d c:Program Files (x86)Microsoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf
2024-07-03 11:17:58.51 Server        -e c:Program Files (x86)Microsoft SQL ServerMSSQL.1MSSQLLOGERRORLOG
2024-07-03 11:17:58.51 Server        -l c:Program Files (x86)Microsoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf
2024-07-03 11:17:58.54 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2024-07-03 11:17:58.54 Server      Detected 12 CPUs. This is an informational message; no user action is required.
2024-07-03 11:18:00.61 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2024-07-03 11:18:00.80 Server      Database mirroring has been enabled on this instance of SQL Server.
2024-07-03 11:18:00.82 spid5s      Starting up database 'master'.
2024-07-03 11:18:00.85 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2024-07-03 11:18:00.91 spid5s      SQL Trace ID 1 was started by login "sa".
2024-07-03 11:18:00.91 spid5s      Starting up database 'mssqlsystemresource'.
2024-07-03 11:18:00.91 spid5s      The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
2024-07-03 11:18:00.96 spid8s      Starting up database 'model'.
2024-07-03 11:18:00.96 spid5s      Server name is 'ZAFSIZ-W002SQLEXPRESS'. This is an informational message only. No user action is required.
2024-07-03 11:18:00.96 spid5s      Starting up database 'msdb'.
2024-07-03 11:18:00.99 spid8s      Clearing tempdb database.
2024-07-03 11:18:01.13 Server      A self-generated certificate was successfully loaded for encryption.
2024-07-03 11:18:01.15 spid8s      Starting up database 'tempdb'.
2024-07-03 11:18:01.16 Server      Server is listening on [ 'any' <ipv6> 62548].
2024-07-03 11:18:01.16 Server      Server is listening on [ 'any' <ipv4> 62548].
2024-07-03 11:18:01.16 Server      Server local connection provider is ready to accept connection on [ \.pipeSQLLocalSQLEXPRESS ].
2024-07-03 11:18:01.16 Server      Server named pipe provider is ready to accept connection on [ \.pipeMSSQL$SQLEXPRESSsqlquery ].
2024-07-03 11:18:01.16 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2024-07-03 11:18:01.18 Server      The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2024-07-03 11:18:01.18 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2024-07-03 11:18:01.18 spid5s      Recovery is complete. This is an informational message only. No user action is required.
2024-07-03 11:18:01.18 spid11s     The Service Broker protocol transport is disabled or not configured.
2024-07-03 11:18:01.18 spid11s     The Database Mirroring protocol transport is disabled or not configured.
2024-07-03 11:18:01.19 spid11s     Service Broker manager has started.
2024-07-03 11:23:00.75 spid11s     Service Broker manager has shut down.
2024-07-03 11:23:00.80 spid5s      SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2024-07-03 11:23:00.82 spid5s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.```