New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update-Help fails for WindowsUpdateProvider #139
Comments
I have the same error message. It has been going on for a couple of months now. Has anyone found a fix? or is there no update file for that particular module at the moment? I should mention I am completely new to PowerShell and IT in general. Any help would be appreciated. I am troubleshooting myself but I can not find anything related to "windows update provider" specifically. I have found some forums on other modules with similar errors. |
No, there isn't a fix for the missing help yet. However, most of the cmdlets in this module don't have any real options and just return a true/false or a date time. |
dsolodow, |
I don't normally post any comments in GH, but I thought I would since Don Jones convinced me to become a "Master" (in the sense that if you learn something....share it). Let me preface my comments below that in this case I am strictly referring to the issues with Windows PowerShell 5.1 and other than the issue issue with updating the local Help file content for the WindowsUpdateProvider, all other help content was successfully updated. I also noticed on PowerShell Core 6.0 Prev, there is no module name WindowsUpdateProvider. My thought was to see if that module was available for Core 6.0 and then borrow the updated URI from the manifest in Core and then replace the URI in the manifest in Windows PowerShell 5.1 (make logical sense?). This was my first attempt in quickly resolving the issue (after skimming through other blogs online where other admins were running into this issue). Regarding the particular issue, I located the HelpURI that is referenced in the manifest file for the WindowsUpdateProvider module. I then copied that URI into a browser which I suspect may redirect to a resource under docs.microsoft.com. Well long story short, it's a dead link (which is what POSH was trying to tell me in the console when it failed to update the help file). In summary, I suspect (just 'suspect'), at the moment, that not a whole lot of development efforts are allocated to update the module manifest for WindowsUpdateProvider given the fact that the evolutionary movement is toward POSH Core development. That said, I know folks can contact the specific MS Engineering groups and request edits/new features so that may be a option for resolving the bad URI in the WindowsUpdateProvider manifest. |
Minor rantovani: Could the error message tell us a little more? Or at least, from the answer to this thread we know where the issue is, and quickly move on? |
A year later this was not resolved PS C:\Windows\system32> update-help
Unbelievable... |
Same for de-DE:
|
Same for me. |
+1 |
Ran into this today |
same. |
Well, the Module Manifest for WindowsUpdateProvider on this machine doesn't give any attribution beyond "Microsoft Corporation", but it does specify a |
Same here; I see that I haven't any *HelpInfo.xml in Do you think this is correct?? Plus: do you know why I see more files in those dirs within CLI as compared to File Explore??? |
Same for me.
|
My Windows 10 system with latest updates:
Every now and then, for over a year, I pop into PowerShell on Windows 10 and I even see people saying that they just run the following instead, as their default, any time they use
Yes, this workaround works. But, if people are moving toward running a built-in command by suppressing error output and moving on, that's bad customer experience (and maybe not the best practice to teach people, in the event that some other errors are occurring?). That response is a popular answer on a few sites I've looked at, and even here from 2016 where it is the highest up-voted answer: Note that the marked accepted answer for the update error related to the
Crazy stuff! I hope the guy didn't go through some re-install because of a @SamB is right about what needs to be addressed:
If you run the following on a system where this error appears, you should see the output:
With the source module manifest, as referenced by @SamB, being:
Microsoft could definitely redirect the link to a working HelpInfoUri, which would mean zero-change on the client end. On a side-note, people using
Welcome to a sea of red These should be fixable by Microsoft, with whatever tooling they have around their link forwarding. Questions:
|
My contribution of failed updates. Searched for a solution (after a long time of failures which I've ignored). Also, read above about support suggesting a Windows re-installation. Poor guy.
|
My results are the same as @gemzon after having installed PowerShell 7 RC1 and performing |
thank for @ScriptAutomate 's solution, this work around works:
|
That's just ignoring the error. It's not a workaround unless you just don't want the error output. |
How can this happen that they ignore this since the mass occurrence of the issue? |
So frustrating!? How can this still be an issue YEARS later? |
Without the help files is pretty hard to understand what's going on. |
||EDIT: I wrote the comment below without reading related thread about the issues related to scripting Windows Updates. Apologies if I came across as antagonistic or rude, that certainly wasn’t my intent! I’ll see myself out. /EDIT||
My guess is that not enough people are actually using the modules listed here and having issues, so this stays at a very low priority for the dev team: ConfigDefender, Defender, Microsoft.PowerShell.Operation.Validation, UEV, Whea, WindowsDeveloperLicense But with this being open source, someone could tackle writing all of this documentation and fixing the URI, LOL =) |
It is working if you fo The real issue is that it won't pull updates consistently, no driver updates, no supplemental updates, no matter how Start-WUScan is called, there is no way to completely automate this. |
This is the result (after deleting the repeated Start-WUScan): Install-WUUpdates -Updates (Start-WUScan -SearchCriteria "IsInstalled=0 AND IsHidden=0 AND IsAssigned=1")
Start-WUScan : Scan hit error: .ReturnValue
Install-WUUpdates : Cannot validate argument on parameter 'Updates'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
|
For those interested, PowerShell/PowerShell#13591 is looking at the same problem, but from the perspective of modifying PowerShell's behavior. I suggest taking a look and providing input :) |
I'm running Windows 10 20H1 and 20H2 and I can't find the WindowsUpdateProvider module anymore. I had it and used it in 19H2 but now it's gone. Copying it from a 1909 desktop won't work either because the CIM namespace root/Microsoft/Windows/WindowsUpdate isn't there anymore. Without documentation I have no clue how to get it back. |
The commentary in this issue has diverged widely from the original problem report about Update-Help. The Update-Help issues have already been reported many times. We are in the process of fixing these issues but it will be a few months before we can implement the final fix. The other issues with specific cmdlet behavior should be reported as product issues at: https://windowsserver.uservoice.com/forums/301869-powershell. Documentation issues about specific cmdlets should be added to the repository with separate issues for each cmdlet. |
@sdwheeler UserVoice is no longer used by Microsoft. Do you know where users may be able to raise issues regarding built-into-Windows PowerShell modules, that don't have public repos, such as the other ones listed here (outside of
I was able to find this page here, Microsoft Support: UserVoice Pages:
It looks like the tech community space that may be most relevant is Microsoft Tech Community: PowerShell. Would this then be the best place to raise issues and bring attention to internally-sourced PowerShell modules, broken |
@ScriptAutomate Most of the docs pages for cmdlets have a feedback button on the bottom of the page. You can start there. The core set of modules that ship with PowerShell are supported by the PowerShell team. The product feedback button on the docs page takes you to the New Issues page in the PowerShell source repo in GitHub. For the Windows management modules, like ActiveDirectory or Hyper-V (and others), the product feedback button on the docs page still points to UserVoice. But the docs feedback button points to the docs repo in GitHub. You can leave feedback in the docs repo but it is better to use Windows Feedback Hub or the PowerShell Tech Community. |
@ScriptAutomate In response to your final point, you don't need to bring attention to the internally-sourced PowerShell modules. We are well aware of the problems and are working to fix them. We have fixed this (for 90%) of the modules for the Server 2022 and Windows 11 release. The harder part is to fix this for old versions of Windows. We hope to have fixed this by the end of the calendar year. |
@sdwheeler Awesome! Thanks for the info, for the blog posts, and for the other work I've seen you involved in across discussions/issues :) It's appreciated, and looks to be quite a lot of wrangling |
Can @ScriptAutomate, @sdwheeler, or anyone else on this thread provide a working link to track the progress of the WindowsUpdateProvider module being unavailable in newer versions of Windows? Suggestions have been provided, but they are either dead links or not relevant. This thread is linked in one of the top hits on Google: https://docs.microsoft.com/en-us/answers/questions/212035/start-wuscan-cmdlet-is-not-avialble-to-run-on-few.html To avoid further off-topic posting here, any help with a legitimate destination for seekers would be beneficial for all and greatly appreciated. |
please bring back the "WindowsUpdateProvider" module |
A third party module PSWindowsUpdate is not a great replacement for basic inbuilt functionality |
A year later & still not fixed |
Hi, any possible update on this specific module for Windows 11? It would seem it would be important to be able to update the operating system via the command line, in a consistent way without 3rd party libraries. |
I actually made a powershell script to update hosts without the use of any modules. If I get time, I will remove any system specific hard coded items and publish on my GitHub. Basically reads AD and gives you a list of enabled windows machines, allows you a choice. And updates and reboots the machine remotely. |
Hi, does this do optional updates? Can you please post what you have working? |
This does not update the operating system but rather updates the PowerShell help files. |
Has anyone gotten any solution to the original problem?
My system:
|
@walthar The problem is in the module listed. That module is not owned by the PowerShell team. It is a Windows component. For modules that ship in Windows, use the Windows Feedback Hub. For more information, see Send feedback to Microsoft with the Feedback Hub app. |
Thanks @sdwheeler . Will do. |
@MiladZarour These are all known issues for those modules. The module owners have to fix those. |
thank for @ScriptAutomate 's solution, this work around works: Update-Help -Verbose -Force -ErrorAction SilentlyContinue |
Newly installed Windows 11 (22H2) and still getting this problem....
then, of course...
Next step is to try
....and it worked
|
It looks like you're just silencing the error messages |
Could be. But, at least, now I have all the help up-to-date. More likely, with the arguments, the update runs and do not stop under any circumstances. It is better to have something up-to-date then the update stopping becasue of an error. |
I understand that this mutes error messages about help files not getting updated. Are you sure you're all updated now? |
This does not solve the problem I agree. Any real help on this topic maybe? Such a shame really we still have no proper answer. |
From @dsolodow on February 9, 2018 15:44
update-help : Failed to update Help for the module(s) 'WindowsUpdateProvider' with UI
culture(s) {en-US} : Unable to retrieve the HelpInfo XML file for UI culture en-US. Make sure the HelpInfoUri property
in the module manifest is valid or check your network connection and then try the command again.
At line:1 char:1
Copied from original issue: MicrosoftDocs/PowerShell-Docs#2117
The text was updated successfully, but these errors were encountered: