The WebProxy property may not exist

[re3turn]

#4 has not fixed #3

That's the webProxy of the failed EC2 instance

PS C:\Users\Administrator\Documents> $objSession = New-Object -ComObject "Microsoft.Update.Session"
PS C:\Users\Administrator\Documents> $objSession | Format-List


ClientApplicationID :
ReadOnly            : False
WebProxy            :
UserLocale          : 1033



PS C:\Users\Administrator\Documents> $objSession.WebProxy
PS C:\Users\Administrator\Documents> 

That's the webProxy of the my local Windows OS

PS C:\Users\Administrator\Documents> $objSession = New-Object -ComObject "Microsoft.Update.Session"
PS C:\Users\Administrator\Documents> $objSession | Format-List


ClientApplicationID :
ReadOnly            : False
WebProxy            : System.__ComObject
UserLocale          : 1041

PS C:\Users\Administrator\Documents> $objSession.WebProxy

Address            :
BypassList         : System.__ComObject
BypassProxyOnLocal : False
ReadOnly           : False
UserName           :
AutoDetect         : True

[ceshihao]

It looks like that error comes from oleutil.GetProperty(updateSessionDisp, "WebProxy")

windowsupdate/iupdatesession.go

Lines 45 to 48 in 94efa1c

	webProxyDisp, err := toIDispatchErr(oleutil.GetProperty(updateSessionDisp, "WebProxy"))
	if err != nil {
	return nil, err
	}

The function returns Exception occurred. (<nil>) but not nil IDispatch.
Could you please help to dig more, why it happens on EC2 instance? I do not have much experience on EC2 Windows.

[re3turn]

It was found that some ComObject could not be accessed when connecting remotely.

https://stackoverflow.com/questions/7078958/powershell-remote-microsoft-update-session-access-denied-0x80070005

PS C:\Users\Administrator> $objSession = New-Object -ComObject "Microsoft.Update.Session"
PS C:\Users\Administrator> $objSession | Format-List


ClientApplicationID :
ReadOnly            : False
WebProxy            : System.__ComObject
UserLocale          : 1033



PS C:\Users\Administrator> Set-ExecutionPolicy RemoteSigned -Force
PS C:\Users\Administrator> Set-WSManQuickConfig -Force
WinRM is already set up to receive requests on this computer.
WinRM has been updated for remote management.
Configured LocalAccountTokenFilterPolicy to grant administrative rights remotely to local users.

PS C:\Users\Administrator> Enter-PSSession -ComputerName localhost
[localhost]: PS C:\Users\Administrator\Documents> $objSession = New-Object -ComObject "Microsoft.Update.Session"
[localhost]: PS C:\Users\Administrator\Documents> $objSession | Format-List


ClientApplicationID :
ReadOnly            : False
WebProxy            :
UserLocale          : 1033



[localhost]: PS C:\Users\Administrator\Documents> $objSession.WebProxy
[localhost]: PS C:\Users\Administrator\Documents>