Is anybody having this Powershell "Update-Help" command, issue?

Question

I am trying to download and install Help files for all the commands but it won't work. I am using Powershell 7.1.1 inside the Windows Terminal.

Update-Help: Failed to update Help for the module(s) 'ConfigDefender, PSReadline' with UI culture(s) {en-US} : One or more errors occurred. (Response status code does not indicate success: 404 (The specified blob does not exist.).).

English-US help content is available and can be installed using: Update-Help -UICulture en-US.

This is exactly what the out-put looks like

Overexpose

Nope, Update-Help works fine on my Raspberry with Powershell 7.1.1. Did you try the suggestion: Update-Help -UICulture en-US? – Altigraph

[1] i vaguely recall reading that the help for PSReadLine is case sensitive ... and they changed the case of the module name. [sigh ...] lookee ... >>> Updating help for the PSReadLine module | PowerShell — devblogs.microsoft.com/powershell/… <<< ///// [2] some modules simply don't have working update functions ... some don't have any at all. your other module[s] may be such. – Tica

Thanks a lot, mate. This just solved one of the problems. I have one more module. The "ConfigDefender" module. Look : "Update-Help: Failed to update Help for the module(s) 'ConfigDefender' with UI culture(s) {en-US}" – Overexpose

Does this answer your question? Powershell fails with Update – Vladamir

Answer 1

Solved, thanks to another post I've found on stackoverflow. According to this Microsoft Forum, the below command should bypass any errors and give you a successful run of cmdlet Update-Help

 Update-Help -Verbose -Force -ErrorAction SilentlyContinue

Overexpose

There's no indication Nathan works at MS, @robinhood. Personally, I'd run it as Update-Help -UICulture en-US -Force -ErrorAction SilentlyContinue. Probably doesn't solve the issue--neither does Nathan's suggestion!--but at least, it doesn't spit out as much garbage. – Whispering

Yours would work as well. Well, either way. And I don't know of which Nathan are you taking about? :smile – Overexpose

The one signing the highlihgted answer there, @robinhood 😉 – Whispering

The issue wasn't if he works or not at MS. The command above solved the issue I had. That's all I wanted to show here. – Overexpose

Ok. So the fix was to hide the errors underneath the carpet (-ErrorAction SilentlyContinue)? lol – Emancipate

The Windows way @sotn, and it works actually!! :) – Overexpose

"According to Microsoft" is misleading. This guy is not a representative of Microsoft but just a user answering on a Microsoft's site. Furthermore, this command line doesn't fix anything. It just don't display the errors (AKA "safely ignore"). – Wrestling

Answer 2

The issue is the capitalization of PSReadline, which changed to PSReadLine with PowerShell 6.

Fix is easy:

1. Close all PowerShell windows
2. From TaskMgr make sure to kill any remaining PowerShell processes.
3. Open Admin Cmd prompt (not PowerShell) and run the following:

ren "C:\Program Files\WindowsPowerShell\Modules\PSReadline" PSReadLine
ren "%APPDATA%\Microsoft\Windows\PowerShell\PSReadline" PSReadLine

That's it. Now you can close the Cmd prompt window, open a PowerShell window and do a normal Update-Help.

See this blog for some additional context: https://devblogs.microsoft.com/powershell/updating-help-for-the-psreadline-module-in-windows-powershell-5-1/

Khufu

Wow! That's the stuff, and not a single upvote. Have mine ;) – Rationale

Answer 3

it solve mine Update-Help -Verbose -Force -ErrorAction SilentlyContinue powershell version 5.1.0

Nehemiah

is this AI generated? – Overexpose