PowerShell Hide-WUUpdate to Hide specific KB update - powershell

Question

Trying to hide a specific KB update with Hide-WUUpdate Here is what I am trying
Hide-WUUpdate –KBArticleID “KB4034664” -ComputerName PCNAME –Confirm:$false
I get the following output
WARNING: You haven't privileges to make this. Try start an eleated Windows PowerShell console
I have tried with an "Elevated Powershell" Any ideas?
After running this as suggested
Hide-WUUpdate –KBArticleID “KB4034664” -ComputerName PCNAME –Confirm:$false -Debuger
I got the following output.
DEBUG: STAGE 0: Prepare environment
DEBUG: Check if ComputerName in set
DEBUG: STAGE 1: Get updates list
DEBUG: Create Microsoft.Update.Session object for PCNAME
DEBUG: Create Microsoft.Update.Session.Searcher object for PCNAME
DEBUG: Set source of updates to default (for PCNAME) Windows Update
DEBUG: Set pre search criteria: IsInstalled = 0
DEBUG: Search criteria is: IsInstalled = 0
DEBUG: Set post search criteria: Dell Inc. - Bus Controllers and Ports, Display - Dell 1907FP(Analog)
DEBUG: Set post search criteria: KBArticleIDs = 'KB4034664'
DEBUG: UpdateAccess: false
DEBUG: Set post search criteria: LSI - Storage - Dell SAS 6/iR Integrated Workstation Controller
DEBUG: Set post search criteria: KBArticleIDs = 'KB4034664'
DEBUG: UpdateAccess: false
DEBUG: Set post search criteria: Update for Windows 7 for x64-based Systems (KB2574819)
DEBUG: Set post search criteria: KBArticleIDs = 'KB4034664'
DEBUG: UpdateAccess: false
DEBUG: Set post search criteria: Update for Windows 7 for x64-based Systems (KB2592687)
DEBUG: Set post search criteria: KBArticleIDs = 'KB4034664'
DEBUG: UpdateAccess: false
DEBUG: Set post search criteria: Update for Windows 7 for x64-based Systems (KB2830477)
DEBUG: Set post search criteria: KBArticleIDs = 'KB4034664'
DEBUG: UpdateAccess: false
DEBUG: Set post search criteria: Update for Windows 7 for x64-based Systems (KB3080079)
DEBUG: Set post search criteria: KBArticleIDs = 'KB4034664'
DEBUG: UpdateAccess: false
DEBUG: Set post search criteria: Update for Windows 7 for x64-based Systems (KB3102429)
DEBUG: Set post search criteria: KBArticleIDs = 'KB4034664'
DEBUG: UpdateAccess: false
DEBUG: Set post search criteria: 2017-08 Security Monthly Quality Rollup for Windows 7 for x64-based System
s (KB4034664)
DEBUG: Set post search criteria: KBArticleIDs = 'KB4034664'
DEBUG: Convert size
DEBUG: Convert KBArticleIDs
WARNING: You haven't privileges to make this. Try start an eleated Windows PowerShell console.
DEBUG: Set post search criteria: August, 2017 Preview of Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.
6, 4.6.1, 4.6.2, 4.7 on Windows 7 and Server 2008 R2 for x64 (KB4035036)
DEBUG: Set post search criteria: KBArticleIDs = 'KB4034664'
DEBUG: UpdateAccess: false
DEBUG: Set post search criteria: 2017-08 Preview of Monthly Quality Rollup for Windows 7 for x64-based Syst
ems (KB4034670)
DEBUG: Set post search criteria: KBArticleIDs = 'KB4034664'
DEBUG: UpdateAccess: false'
Powershell remote IS enabled on the remote computer.

Answer 1

Assuming this is the script you're using, it looks like the error message is from line 550. That warning message is from an error trap that's concealing the actual error. I'd recommend changing the code to something like this:
If ($pscmdlet.ShouldProcess($Computer, "$StatusName $($Update.Title)?")) {
Try {
$Update.IsHidden = $HideStatus
}
Catch {
Write-Warning "You haven't privileges to make this. Try start an eleated Windows PowerShell console."
throw ($_)
}
} #$pscmdlet.ShouldProcess($Computer,"Hide $($Update.Title)?")
Now you should be able to see the actual error message instead of the friendly, non-informative warning the script author decided you should get.

Answer 2

After analyzing all the information, I believe you do not have the required permissions/access to perform this operation remotely.
Your script is a 3rd party script. The debug info is not specially informative. All that can be said is that the script fails on setting the hidden property on the update.
The best shot you have is to enable Powershell Remoting to make sure you have the remote access you need to run this. Nevertheless there is a chance that it still may not work due to some Microsoft security restrictions. In that case I'd advise you to install and configure Microsoft Windows Server Update Services which will enable you to perform this task.