Your clarification does not help actually. But any way, deleting any object, leave just ID on a link, and again, everything here depends on your application. In most cases it could cause for some different issues, when application have not expected deleted object. And I would recommend to use some flag like "isDeleted", which can help to hide such objects in most of places, and still have an access to the content of this object, to show if it would be needed. Completely delete object recommended only in case when no any other objects has links to this one. 

It is completely depends on application which you use. Some developers create their own table for users independent from Caché users.

Or maybe you talking about  HealthShare or TrakCare?

While your code interrupted when server shutdown, you can't do it directly. But I think you can try to call restart service of cache. So you should look at possiblilties OS, which you use for this server.

all links fixed.

    set url="http://www.intersys.com/main.csp?a=b&QUERY=abc&QUERY=xyz"
    Do ##class(%Net.URLParser).Parse(url, .aComponents)
    
    set query=$lfs($get(aComponents("query")),"&")
    for i=1:1:$ll(query) {
        set $lb(name,value)=$lfs($lg(query,i),"=")
        set index=$order(data(name,""),-1)+1
        set data(name,index)=$g(value)
        set data(name,index,"O")=i
    }
    zwrite data

data("QUERY",1)="abc"
data("QUERY",1,"O")=2
data("QUERY",2)="xyz"
data("QUERY",2,"O")=3
data("a",1)="b"
data("a",1,"O")=1

I think you can create some issue in this repo
you can also look at my example of Dockerfile, when I delete installation folder in the same command RUN with installation, which should became in the same layer

Have you tried it in cmd.exe instead of PowerShell, or the same troubles there ?
Please show screenshots from page Securty, Services

I've just updated from 245 to 255 but on macOS, and everything is OK.

Ok, Is terminal working well ?

and command 

..\bin\cache -s.

Sorry my mistake, I don't have widows system currently, for windows you should change %Service_Console

to check access, you may use this command

..\bin\cache -s.

Powershell or cmd does not matter.

Ok, looks like, it does not matter who tried to connect to cache, any terminal access is forbidden. 

You should allow Password or Unauthenticated method for %Service_Terminal.

first sample is correct, but depends on what is login.scr contains. This file should only contains 'answers' for login.

so, it is a plain file, with login and password, in each line, and last empty file.

login<\n>
password<\n>

<\n> - it is just a line break, which is required