Unable to use IHTMLDocument2

My friend and I were trying to nail down this issue. We kept getting this error on his machine while the same script worked on mine, (same Windows 10 build version on both).

Method invocation failed because [System.__ComObject] does not contain a method named 'IHTMLDocument2_write'.At <script_path\script_name>:184 char:1+ $HTML.IHTMLDocument2_write($content)+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    + CategoryInfo          : InvalidOperation: (IHTMLDocument2_write:String) [], RuntimeException    + FullyQualifiedErrorId : MethodNotFound

We found that on his computer the $html object had ie9 properties and on mine it had IHTML properties. He identified that my computer had MS Office installed, but his did not. He tried the code on another of his computers running Server 2008 that did have Office (even an old version like 2010) installed and our script worked fine.

Proposed solution:

$HTML = New-Object -Com "HTMLFile"try {    # This works in PowerShell with Office installed    $html.IHTMLDocument2_write($content)}catch {    # This works when Office is not installed        $src = [System.Text.Encoding]::Unicode.GetBytes($content)    $html.write($src)}

Updated:

Ironic, how I ran into a similar issue years later, came across this post and went "hey I asked this question".

l0wm3mory's answer is now the correct answer.

Original:

Question that helped: Can't use InternetExplorer.Application object?

Copied Microsoft.mshtml.dll from my machine that worked to the server in C:\Program Files (x86)\Microsoft.NET\Primary Interop Assemblies. Then added Add-Type -Path "C:\Program Files (x86)\Microsoft.NET\Primary Interop Assemblies\microsoft.mshtml.dll" at the beginning of my script.

I also noticed some IE security boxes appear (when running my script) and it's possible the IE security settings of a Windows server would interfere (being it's much higher than a client would be). Perhaps if my settings were lowered, this would be resolved without copying the .dll. However, I think upgrading to PSv5 was crucial (as even enum wasn't recognized).

I dont't know why,but after installed microsoft office on the computer,everything works fine for me. Tried on two different computer.