Powershell wont run "restricted by admin"

Hi. Before using "Software restriction policys" in Secpol i could open powershell, now even after deleting the powershell disallow in "Software restriction policys" i get the message that its been blocked! How do i enable so i can use powershell temporarily before disallowing it again?

BlackVen0m said:

Hi. Before using "Software restriction policys" in Secpol i could open powershell, now even after deleting the powershell disallow in "Software restriction policys" i get the message that its been blocked! How do i enable so i can use powershell temporarily before disallowing it again?

Well, what do you want to do?

Basically speaking, you have to set the execution policy in PS, when you want to execute a script.

do you want to know more?

Buster Friendly said:

Well, what do you want to do?

Basically speaking, you have to set the execution policy in PS, when you want to execute a script.

do you want to know more?

I cant even open PS to execute anything

- - - Updated - - -

TairikuOkami said:

Try to remove the whole key.

Code:

reg delete "HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\DisallowRun" /f

Hi. This key doesn't even exist for me

- - - Updated - - -

Is there anywhere in the Even Log that can help pinpoint the problem?

- - - Updated - - -

Oh i found the key, what do i do with it. How do i unblock it?

- - - Updated - - -

should i delete those 2 keys?

- - - Updated - - -

Problem solved, i needed to find all those entries and delete them all.

what the heck are you doing?
going around, deleting RegKeys without a plan... well, have lots of fun now with your system.

Really sad that you could not explain what you wanted to do in the first place.

Paul Black said:

Hello @BlackVen0m,

I agree with @Buster Friendly.

You should NEVER muck around with the Registry unless you know what you are doing, and you certainly should NOT do ANYTHING without creating a Registry Backup FIRST.

hell yeah.

He also didn't explain his basic problem, and to "support" by telling he should delete some RegKeys.... that's not really a reliable support.

that's really bad and can frakk up his whole system.
That happens when people give support without knowing what they actually do.
I don't get such behavior... I will never.

Well, just to tell to delete some RegEntries without knowing what the User wanted to do in the first place... that is the total opposite of being very capable. That's a very dangerous "tip".

And still, we don't know what the User wanted to do with his Script.
And so, its putting the cart before the horse, this won't help to find a solution.

Buster Friendly said:

what the heck are you doing?
going around, deleting RegKeys without a plan... well, have lots of fun now with your system.

Really sad that you could not explain what you wanted to do in the first place.

Hi friend. Its no problem i did a backup, and this reg key was the settings that was blocking it, so it was no problem deleting it. It should be deleted when i remove the software block but it did not remove it self so i had to do it manually i saw it on another forum

- - - Updated - - -

Buster Friendly said:

Well, just to tell to delete some RegEntries without knowing what the User wanted to do in the first place... that is the total opposite of being very capable. That's a very dangerous "tip".

And still, we don't know what the User wanted to do with his Script.
And so, its putting the cart before the horse, this won't help to find a solution.

What i wanted to do was to software block powershell as a safety measure for it not to run without my knowledge as i read somewhere on a security site. But the problem was that when i wanted to use powershell and unblock restriction, it never unblocked it, it got stuck in the registry.