Posted On February 19, 2020

WGET Error on Windows and Its Quick Resolution

kimconnect 0 comments
blog.KimConnect.com >> Windows >> WGET Error on Windows and Its Quick Resolution
Error:
PS C:\temp> Invoke-WebRequest -Uri $file
Invoke-WebRequest : The response content cannot be parsed because the Internet Explorer engine is not available, or
Internet Explorer's first-launch configuration is not complete. Specify the UseBasicParsing parameter and try again.
At line:1 char:1
+ Invoke-WebRequest -Uri $file
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotImplemented: (:) [Invoke-WebRequest], NotSupportedException
+ FullyQualifiedErrorId : WebCmdletIEDomNotSupportedException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Resolution:
Invoke-WebRequest -Uri $file -UseBasicParsing

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Post

Active Directory Group Policy – HIPPA Auditing

The Health Insurance Portability and Accountability Act of 1996 (HIPAA) is a federal law that required the…

PowerShell: Quickly Test Connectivity from a List of Sources toward a Destination on a Specific Port

# testRemotePort.ps1 $connectFrom=@' windows1 windows2 '@ $connectTo=@' \\servername\sharename '@ $testPort=445 $sources=@($connectFrom -split "`n")|%{$_.Trim()} $destinations=@($connectTo -split…

Remediate IE Vulnerabilities

<# PowerShell Script to Secure Internet Explorer & Memory Operations reg add "HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PRINT_INFO_DISCLOSURE_FIX" /v…
Other project: DragonCoin.com