John Walker
asked on
Error 800A01AD ActiveX Component can't create object
Error: ActiveX cannot create object (800A01AD)
Creation of a shell object is blocked on some of the systems managed by a third party that are under my control. I've attempted to automate some scripting in VBS and in PowerShell (see snippets below) that works just fine in win7 and win10. The snippets are geared at logging the URL or Title of any website in any active ie11 window and continue logging (date / time and URL) until all instances of ie11 are closed.
The scripting works just fine on my test environment, other systems under my control that are not managed by third parties, and every where i can test it. The wording, spelling, grammar, etc are all correct so there is a security setting on the system that is prohibiting the use of objShell.windows. Under VBS, it gives the error message above and in Powershell, it says object not registered. Both scripts error out on the last line of the snippet. The remainder would work but something is blocking the creation of "windows" object.
Any input would be appreciated. I have a security flaw in internet explorer that i need to cover by logging URLs and cannot use third party software or complex coding (long story). To note: this is being deployed in win32 instances of win7. i have test ran this with win32 and win64 versions of cscript and it works fine in the test environment. But on those systems managed by the third party, it's only win32 instance.
VBS:
dim objShell
dim objShellWindows
dim fileStr, tempStr
dim actWindCnt, timeCnt
Set objFileToWrite = CreateObject("Scripting.Fi leSystemOb ject").Ope nTextFile( "C:\Script Files_HSMI \iExplore. log",8,tru e)
set objShell = CreateObject("shell.applic ation")
set objShellWindows = objShell.Windows
Powershell:
$IEObjs = @()
$IECnt = 0
$ShellWindows = (New-Object -ComObject Shell.Application).Windows ()
Creation of a shell object is blocked on some of the systems managed by a third party that are under my control. I've attempted to automate some scripting in VBS and in PowerShell (see snippets below) that works just fine in win7 and win10. The snippets are geared at logging the URL or Title of any website in any active ie11 window and continue logging (date / time and URL) until all instances of ie11 are closed.
The scripting works just fine on my test environment, other systems under my control that are not managed by third parties, and every where i can test it. The wording, spelling, grammar, etc are all correct so there is a security setting on the system that is prohibiting the use of objShell.windows. Under VBS, it gives the error message above and in Powershell, it says object not registered. Both scripts error out on the last line of the snippet. The remainder would work but something is blocking the creation of "windows" object.
Any input would be appreciated. I have a security flaw in internet explorer that i need to cover by logging URLs and cannot use third party software or complex coding (long story). To note: this is being deployed in win32 instances of win7. i have test ran this with win32 and win64 versions of cscript and it works fine in the test environment. But on those systems managed by the third party, it's only win32 instance.
VBS:
dim objShell
dim objShellWindows
dim fileStr, tempStr
dim actWindCnt, timeCnt
Set objFileToWrite = CreateObject("Scripting.Fi
set objShell = CreateObject("shell.applic
set objShellWindows = objShell.Windows
Powershell:
$IEObjs = @()
$IECnt = 0
$ShellWindows = (New-Object -ComObject Shell.Application).Windows
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.