Windows 10: PowerShell 1 Execution policy is bad in registry

it was detected as bad by dell who used Norton power eraser to locate the issues in my computer, Norton says they can not fix it, that Microsoft needs to fix it , I came to micorosoft to get help a tech, tried to reinstall Microsoft windows, after the computer restarted a windows said failed contoll access, blocked c memory, I came back to Microsoft and a guy in support got into my computer and made a mess of it, he shut down programs without reinstalling them, tried to open mic which was also a blocked action, never tried to fix the powershell, but shut down all os security and killed Malwarebytes and dell support and assist, then he restarted my computer quickly after closing LogMeIn, it restarted very slowly, was horrible, many icons missing on task bar, I was in shock, I came back to Microsoft and asked again for help, the third guy tell me the second one was a scammer, and I showed him all three from same support page chat in Microsoft, he gets my phone number, calls me while on the phone while another guy on that chat gets into my computer and shut off every service, dell, intel, diagnotics, events, etc, now this time I am terrified to use support at Microsoft and am asking for help from the Microsoft community, not one of those guys fixed the registry error the first one it seemed tried tho and I am horrified by what has happened to me, now I repaired as much as I could the system as it was before coming here this time for help but the registry powershell is still bad and the control access is still blocking any attempt to fix anything, can someone who is a real tech help to fix this nightmare please



***Modify title from : hkey machine powershell 1 shell id microsoft executionpolicy is bad and i dont know how to repair it ***

:)

 

Set Execution Policy in Powershell

I set the Execution Policy in Powershell to unrestricted to run a couple of command lines and then set the policy back to restricted. Does setting the policy to unrestricted for a small period of time harm Windows 10? Does one have to set the policy back
to restricted or does closing Powershell and relaunching Powershell put the policy back to restricted?

 

Set Execution Policy in Powershell

Hi,

Thank you for posting your query in Microsoft Community.

I will surely assist you with your query.

The execution policy is part of the security strategy of Windows PowerShell. It determines whether you can load configuration files (including your Windows PowerShell profile) and run scripts, and it determines which scripts, if any, must be digitally signed
before they will run.

Please refer to the link below to know more about Set Execution policy.

https://technet.microsoft.com/en-us/library/hh849812.aspx

Hope the above information helps.

Thank you.

 

Set Execution Policy in Powershell

Thanks for the link that helps me understand the execution policy