Forum Discussion
Alpha45
Sep 17, 2022Brass Contributor
I installed Windows Terminal which was not installed before, but PowerShell it gives me this error!
WMF 5.1 cannot be installed S.o. Windows 11 pro build 21H2 22000.978 DISM and Sfc no error! Thank you
- Sep 19, 2022Does import-module appx -UseWindowsPowerShell work in PowerShell 7?
Sep 19, 2022
Looks like the path is not in your system settings. Could you check? (https://github.com/microsoft/terminal/issues/6039)
Alpha45
Sep 19, 2022Brass Contributor
In fact there was no the environment variable
% systemroot%\System32\WindowsPowerShell\v1.0, I added it but it still didn't work.
- Sep 20, 2022No problem and good to hear!
- Alpha45Sep 20, 2022Brass ContributorAfter installing all the updates, everything works normally!
Thank you for your cooperation. - Sep 19, 2022Does import-module appx -UseWindowsPowerShell work in PowerShell 7?
- Alpha45Sep 19, 2022Brass Contributor
Reinstall IN PLACE build 22000.194 , but the problem is reversed ..
PS: After installing all the updates, everything works normally!
Thank you for your cooperation.
- Sep 19, 2022Hmmm, perhaps this is an indication of the issue... Could you try the dotnet repair tool from the link above
- Alpha45Sep 19, 2022Brass Contributordotnet: The term 'dotnet' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again. - Sep 19, 2022I don't know, but what DotNet versions do you have installed? (dotnet --list-runtimes) You could use the repair tool to fix issues if any https://www.microsoft.com/en-us/download/details.aspx?id=30135
- Alpha45Sep 19, 2022Brass Contributor
- Sep 19, 2022There's something wrong with your DotNet Framework installation perhaps, could you reinstall dotnet 4.5.2 or higher?
- Alpha45Sep 19, 2022Brass Contributor
C:\Windows\system32> powershell.exe -noprofile
Windows PowerShell internal error. Managed Windows PowerShell loading failed with error 80070002. - Sep 19, 2022Ok... It's not a profile thing? Could you start a Command-Prompt and run 'powershell.exe -noprofile' ?