Windows 10: Piping Powershell output fails

I'm in the Admin Powershell window. I'm trying to install azure modules on my Windows 10 Enterprise workstation, version 10.0.18362.778

The install fails and I want to capture the output so I go (at the powershell prompt):

Install-Module -name -Az -Verbose -Force | Out-File C:\powershell\errors.txt

But errors.txt is of 0 length.

Just to test the system I did:

Get-Process | Out-File c:\powershell\processes.txt

and that file was 58,820 bytes long, so the syntax seems OK.

What's wrong?



RON

:)

 

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:

 

Pipe file content into PowerShell command without loading the entire file to memory

Check my answer to this question: PowerShell's pipe adds linefeed

 

How to factory reset Cisco 1700 Router

Hopefully I can help you here....its a very common thing to happen.


First, I take it you dont know the passwords for console access or telnet/ssh?

I will assume that these devices belong to you.

step 1. Plug a cisco console cable into a serial port on your pc
step 2. Plug other end into Cisco console port
step 3. Using hyperterm or putty or similar connect to the serial port
step 4. boot router, and make sure you clearly can see the output (this confirms you have good serial comms)
step 5. if this fails, adjust the comm port settings (9600, 8,1,n are the default)
step 6. now you have to do the only hard part...send the break command:

Break command list: Break Commands

Go down the list and match your OS and SW and try the sequence suggested.

If this fails several times do what I do: Install putty (free) and then to send a break so you can get into rommom just hit "ctrl-a b".