[wombatpandaa]

Hey all, I've recently run into an issue where I'll attempt to open the command prompt and it'll immediately close on me. This happens whether I open it as an administrator or not, and I've tried a few fixes I found online, including editing its registry entry and running the disc image repair stuff in Powershell. I'm rather at a loss as to how to fix this now.

The issue popped up sometime today or possibly last night, and I know this because I used the Anaconda environment command prompt to completely uninstall Anaconda last night, which I reinstalled this morning. In the course of reinstalling Anaconda, I also uninstalled and reinstalled PyCharm, Python, and Atom. I recall that I didn't allow Anaconda to do anything with my PATH variable, but I did tell PyCharm to add its bin library to PATH.

I'm running up-to-date Windows 11 Home Insider Preview as of two seconds ago when I checked for updates again. I also just barely finished a system scan using Malwarebytes Free and found nothing problematic. I'm at a loss, and hoping you smart people can help me resolve this issue.

 

[spunk.funk]

Can you press the Windows key +X and choose Terminal (Admin) or Powershell (Admin)
copy and paste or type DISM /Online /CLEANUP-IMAGE /RestoreHealth and press Enter. When that is done type
SFC /scannow and press Enter, this will replace any missing system files

 

[wombatpandaa]

Alright, I'm running those now. I actually had done this before and got no results, but it doesn't hurt to try again right?

Also, just in case it matters, I found that when I run the Terminal with a Powershell tab open (and I'm pretty sure this happened when I ran Powershell by itself too), it tells me this:

. : File C:\Users\chadj\Documents\WindowsPowerShell\profile.ps1 cannot be loaded because running scripts is disabled
on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3

• . 'C:\Users\chadj\Documents\WindowsPowerShell\profile.ps1'
• ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : SecurityError: ) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess

I went to that link and viewed my execution policy, and it's listed as "Undefined." Also, if I open a command prompt in the Terminal, it'll immediately print "[process exited with code 1]" and take no more commands. Maybe some of this is useful in determining the cause?

Anyways, I'll post the results of the commands you told me to execute once they're done.
Edit: the smiley is supposed to be a ( and a : but I can't get it to change
Edit 2: I finished both of those processes, no change. Scan says there were no integrity violations found.

 

[spunk.funk]

Try this: https://stackoverflow.com/questions...se-running-scripts-is-disabled-on-this-system

 

[wombatpandaa]

Okay, so that worked to fix the issue with Powershell (there's no error message about being unable to load scripts anymore), but I still have the same problem with command prompt.

 

[spunk.funk]

Press the Windows key +X and choose Terminal (Admin) Here type or copy and paste
DISM.exe /Online /Cleanup-image /Restorehealth and press Enter. When that completes type
SFC /scannow and press Enter. Which restores the Windows System Files
You can also add the missing Environment Variable Path

 

[wombatpandaa]

I've run those (again) and nothing changed. I also changed the Environment Variable Path according to that website's instructions and nothing changed.

Here's the readout of my commands and their output:
(base) PS C:\Users\chadj> DISM.exe /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.22483.1000

Image Version: 10.0.22483.1011

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
(base) PS C:\Users\chadj> SFC /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

 

[spunk.funk]

If you can run Terminal (the replacement for Command Prompt) and Powershell, then I would just leave it alone.
I'm out of ideas, except to do a Repair Install

 

[wombatpandaa]

Okay, thank you for your help. I am able to perform the same tasks in the Terminal, so I suppose that'll have to suffice.