Windows 10: The Windows PowerShell and Command prompt needs be fixed to allow pipe working properly

For Windows systems with WSL, by installing our software in WSL can make Windows file encryption, gpg significantly more secure, make remote task automation through ssh significantly more secure, make file transfer automation through sftp significantly more secure.For Windows program that generates the sensitive info to be able to make info more secure, using the pipe to our fcrypt program is the best way, as that way you don't need to save sensitive info to a file first, then use our fcrypt program to encrypt it, so using pipe can make the info immediately encrypted. But the current PowerShel

:)

 

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:

 

Installation media boots to command prompt

I've just booted from known working install media to see exactly what it does when booting. The sequence of events is...

1. Windows logo on a black screen
2. circling dots appear beneath the logo
3. light blue 'Please wait' screen with circling dots
4. a command prompt window (very briefly)
5. the initial Setup page appears

Do you see steps 1-3? If so, it appears you have stopped at step 4, suggesting that something on the disc cannot be read.

Does the disc boot properly in another machine? If so, try cleaning the laptop's drive lens then try booting from the disc again.

If not, make new install media with Microsoft's Media Creation Tool, either as a bootable USB, on an ISO that you can burn to another disc. At Step 8 in Option One of this tutorial you can choose between making a USB or an ISO.

Download Windows 10 ISO File

 

command prompt will not open in safe mode with command prompt

Would I just follow the same steps within safe mode after hooking up to the other system?