Windows 10: Everytime on startup powershell command promt comes up and wont go away

Everytime on startup powershell command promt comes up with:Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Anattempt was made to load a program with an incorrect format."At line:1 char:91+ ... se$bytes; [System.Reflection.Assembly]::Load$bytes.EntryPoint.Inv ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: : [], MethodInvocationException + FullyQualifiedErrorId : BadImageFormatExceptionEverytime I try to close the window it will pop back up, this

:)

 

Settings and command promt not working

I recently made changes to my computer by accidentally selecting hidden in attributes of I think my Program files and after I did that my settings and command promt stopped working. All files are back to normal but my settings and command promt still wont
work. Command promt wont open with the hot keys and I cant search it in the search bar cause my search bar wont open(deleting cortana messed that up my search bar ..which is a different issue). As far as settings go I can pull up the settings but nothing shows
up only the options on the left of the menu. Here is an Example, I can click on settings and click on apps or security but nothing shows up just A white screen with the menu options on the left and settings freezes, In tast manager it says "application frame
host" not responding.

Currently I have ran the troubleshooter for windows apps which said it fixed some corrupt file but had no effect on settings or command promt.

The issues started when I made those file changes.

 

Locked Powershell startup command in context menu

Hi

I had thought it had resolved the problem of the 2 PowerShell scripts as I was able disable them in the context menu of startup. Unfortunately I'm not able to delete them, either in CCleaner or in the registry even though I set permissions to full control.
That said CCleaner shows them as disabled.

Have I missed something?

Hi

I had missed the section on applying full control to the command folder beneath the PowerShell one in regedit. Since I changed the permissions on the command folder as well I have now deleted the two scripts from the startup program list in the context menu.

Many thanks for your help.

K

 

PowerShell instead of Commandline in Creators Update

Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

Edit: Not that it matters...I use both regularly. *Toast :toast: