SOLVED

Unable to update Powershell Help

%3CLINGO-SUB%20id%3D%22lingo-sub-144748%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20update%20Powershell%20Help%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-144748%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20PowerShell%20modules%20don't%20support%20updatable%20help%2C%20which%20was%20really%20designed%20for%20%22air-gap%22%20scenarios%2C%20such%20as%20servers%20that%20aren't%20allowed%20to%20access%20the%20Internet.%26nbsp%3B%20We're%20a%20cloud%20service%2C%20so%20that%20scenario%20doesn't%20apply.%26nbsp%3B%20Instead%20of%20supporting%20a%20single%20URL%20to%20download%20an%20updated%26nbsp%3Bhelp%20file%20for%20all%20the%20cmdlets%2C%20each%20cmdlet%20has%20its%20own%20URL%26nbsp%3Bto%20get%20the%20latest%20help%20online.%26nbsp%3BBecause%20it's%20online%2C%20we%20can%20update%20it%20much%20more%20easily%2Ffrequently%20(and%20I%20do!).%26nbsp%3B%20Use%20%22Get-Help%20%3CCMDLET%20name%3D%22%22%3E%20-online%22.%26nbsp%3B%20Any%20updates%20made%20online%20automatically%20go%20into%20the%20help%20file%20that%20ships%20with%20the%20next%20release%20of%20the%20module.%3C%2FCMDLET%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20module%26nbsp%3Bdoesn't%20handle%20the%20update%20command%20well%20-%20it%20should%20fail%20more%20%22gracefully%22%20than%20the%20error%20you%20see.%26nbsp%3B%20So%20it's%20a%20bug%2C%20but%20a%20low%20priority%20bug%2C%20given%20that%20it%20doesn't%20impact%20functionality.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-143585%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20update%20Powershell%20Help%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143585%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20think%20so%2C%20apparently%20that%20is%20intentional%2C%20but%20I%20don't%20understand%20why.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-143529%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20update%20Powershell%20Help%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-143529%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20exact%20same%20problem.%20Is%20microsoft%20going%20to%20provide%26nbsp%3B%20a%20fix%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-91795%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20update%20Powershell%20Help%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91795%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%20Yes%2C%20I%20asked%20there%20also%20and%20%26nbsp%3BCarol%20told%20me%20that%20it%20does%20not%20support%20updateable%20help%20(%3A.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-91790%22%20slang%3D%22en-US%22%3ERe%3A%20Unable%20to%20update%20Powershell%20Help%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91790%22%20slang%3D%22en-US%22%3E%3CP%3EI%20guess%20so%3F%20On%201.7.210.0%2C%20the%20HelpInfoUri%20is%20listed%20as%3A%20%3CA%20href%3D%22https%3A%2F%2Fmsdn.microsoft.com%2Flibrary%2Fmt433195.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmsdn.microsoft.com%2Flibrary%2Fmt433195.aspx%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhich%20then%20redirects%20to%20the%20docs.com%20URL%2C%20and%20breaks.%20It%20also%20seems%20to%20be%20missing%20the%20helpinfo.xml.%20Not%20sure%20if%20it%20even%20supports%20updateable%20help.%20Did%20you%20ask%20on%20the%20Yammer%20network%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-91647%22%20slang%3D%22en-US%22%3EUnable%20to%20update%20Powershell%20Help%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91647%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20run%20update-help%2C%20I%20get%20the%20following%20error.%20Does%20anyone%20else%3F%20Is%20this%20a%20known%20issue%3F%3C%2FP%3E%3CP%3EFailed%20to%20update%20Help%20for%20the%20module(s)%20'AzureInformationProtection'%26nbsp%3BThe%20value%20of%20the%20HelpInfoUri%20key%20in%20the%20module%20manifest%20must%20resolve%20to%20a%20container%20or%20root%20URL%20on%20a%20website%20where%20the%20help%20files%20are%20stored.%20The%20HelpInfoUri%20'%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2FRMSProtection%2F%3Fview%3Dazureipps%26amp%3BviewFallbackFrom%3Dazureipps%253Fview%253Dazureipps%253Fview%253Daz%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2FRMSProtection%2F%3Fview%3Dazureipps%26amp%3BviewFallbackFrom%3Dazureipps%253Fview%253Dazureipps%253Fview%253Daz%3C%2FA%3E%3CBR%20%2F%3Eureipps%253Fview%253Dazureipps%3Fview%3Dazureipps%3Fview%3Dazureipps%3Fview%3Dazureipps%3Fview%3Dazureipps'%20does%20not%20resolve%20to%20a%20container%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-91647%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EInformation%20Protection%20%26amp%3B%20Governance%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Information%20Protection%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Respected Contributor

When I run update-help, I get the following error. Does anyone else? Is this a known issue?

Failed to update Help for the module(s) 'AzureInformationProtection' The value of the HelpInfoUri key in the module manifest must resolve to a container or root URL on a website where the help files are stored. The HelpInfoUri 'https://docs.microsoft.com/en-us/powershell/module/RMSProtection/?view=azureipps&viewFallbackFrom=az...
ureipps%3Fview%3Dazureipps?view=azureipps?view=azureipps?view=azureipps?view=azureipps' does not resolve to a container

5 Replies
Best Response confirmed by Dean Gross (Respected Contributor)
Solution

I guess so? On 1.7.210.0, the HelpInfoUri is listed as: https://msdn.microsoft.com/library/mt433195.aspx

 

Which then redirects to the docs.com URL, and breaks. It also seems to be missing the helpinfo.xml. Not sure if it even supports updateable help. Did you ask on the Yammer network?

Thanks, Yes, I asked there also and  Carol told me that it does not support updateable help (:.

I have the exact same problem. Is microsoft going to provide  a fix?

I don't think so, apparently that is intentional, but I don't understand why.

Our PowerShell modules don't support updatable help, which was really designed for "air-gap" scenarios, such as servers that aren't allowed to access the Internet.  We're a cloud service, so that scenario doesn't apply.  Instead of supporting a single URL to download an updated help file for all the cmdlets, each cmdlet has its own URL to get the latest help online. Because it's online, we can update it much more easily/frequently (and I do!).  Use "Get-Help <cmdlet name> -online".  Any updates made online automatically go into the help file that ships with the next release of the module.

 

The module doesn't handle the update command well - it should fail more "gracefully" than the error you see.  So it's a bug, but a low priority bug, given that it doesn't impact functionality.