Windows 10: Trying to update powershell, error only

trying to solve this issue I'll post the error in ps not sure what it means. Turning here for answers. Thank you.Set-Location : A positional parameter cannot be found that accepts argument 'Defender'. At line:1 char:1 + cd %ProgramFiles%\Windows Defender + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: : [Set-Location], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.SetLocationCommand

:)

 

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:

 

the witcher demo

^ what they said will both work. i suggest updating directX, and in the future please try and list the exact error message... and i want a muffin.

 

How to fix Powershell with error 80070002

Hi Caleb Cleavinger，

Welcome to Microsoft Community

The error you're experiencing with PowerShell, Visual Studio 2022, and JetBrains IDE terminals seems to be related to an issue with the loading of managed Windows PowerShell, indicated by the error message "Internal Windows PowerShell error. Loading managed Windows PowerShell failed with error 80070002".

Error 80070002 generally points to a missing file or a file not found error, which could be a result of the LockDown Browser installation altering or interfering with certain system files. Here are a few steps you could take to troubleshoot and potentially resolve the issue:

1. System File Checker (SFC): Run the System File Checker to repair missing or corrupted system files. Open Command Prompt as an administrator and run the command sfc /scannow. This process will scan for and attempt to fix any corrupted files.
   
2. DISM Tool: Deployment Image Servicing and Management (DISM) is another tool you can use to fix Windows corruption errors. Run DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt.
   
3. Reinstall PowerShell: If PowerShell itself is corrupted, consider reinstalling it. You can download the latest version of PowerShell from the official Microsoft website.
   
4. Check for Windows Updates: Ensure that your Windows is up to date, as some updates might contain fixes for your issue.
   
5. Create a New User Account: Sometimes, creating a new user account can resolve such issues, as it creates a fresh user profile with default settings.
   
6. Registry Check: Be cautious with this step. Check the registry for any paths related to PowerShell and ensure they are correctly set. If you're not comfortable with this, it might be better to seek professional help.
   
7. Backup and Reinstall Windows: As a last resort, backing up your important files and performing a clean installation of Windows might be necessary. This will remove any residual files or settings left by the LockDown Browser.
   
8. Professional Assistance: If you're not comfortable performing these steps, it might be best to seek professional IT assistance.
   

*To check the Windows Registry for potential issues related to PowerShell, you can follow these detailed steps. Please be aware that editing the registry can have significant impacts on your system if done incorrectly, so proceed with caution and consider backing up the registry before making any changes.

Steps to Check the Registry for PowerShell Issues:

1. Open Registry Editor:
   
   • Press Win + R to open the Run dialog.
     
   • Type regedit and press Enter. This opens the Registry Editor.
     
2. Backup the Registry:
   
   • In the Registry Editor, click on File and then Export.
     
   • Choose a location to save the backup, ensure 'All' is selected under 'Export range', and save the file.
     
3. Navigate to PowerShell Registry Keys:
   
   • PowerShell settings can be found under different keys depending on what exactly you're looking for. Common locations include:
     
     • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell
       
     • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1
       
     • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\3
       
   • Expand these keys and look for any subkeys or values that seem out of place or corrupted.
     
4. Look for Inconsistencies:
   
   • Check for any paths that are incorrect or point to locations that don’t exist.
     
   • Look for any values that seem out of place. Be cautious not to change anything unless you're sure it's related to your issue.
     
5. Consult Online Resources:
   
   • If you find something suspicious, search online to see if it's related to your problem. Microsoft documentation or forums might have specific instructions.
     
6. Restoring Defaults (if necessary):
   
   • If you find a key or value that is clearly related to your issue and know what the default should be, you can modify it. Be extremely cautious with this step.
     
7. Restart Your Computer:
   
   • After making changes, restart your computer to see if the issue is resolved.
     

Disclaimer: Generally, modifying registry subkeys or work group is intended for advanced users, administrators, and IT Professionals. It can help fix some problems, however, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For further protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click How to back up and restore the registry in Windows - Microsoft Support to view the article.

Thank you for your patience and understanding! If you have any questions, feel free to leave us a message.

Sincerely

Manson | Microsoft Support Specialist