Jump to content
Sign in to follow this  

shell.windows can't see IE windows on fresh Win2008 install

Recommended Posts



I have a fresh Win2008 x64 install.

I then start a couple file explorer and internet explorer windows.

I then run the example script for ObjCreate:

$oShell = ObjCreate("shell.application")    ; Get the Windows Shell Object
$oShellWindows=$oShell.windows          ; Get the collection of open shell Windows
if Isobj($oShellWindows) then
  $string=""                    ; String for displaying purposes
  for $Window in $oShellWindows         ; Count all existing shell windows
    $String = $String & $window.LocationName & @CRLF
  Msgbox(0,"Shell Windows","You have the following shell windows:" & @CRLF & @CRLF & $String);

Result, only the file explorer windows are listed. The internet explorer windows are ignored.

The weird thing is that I have another Win2008 machine for which it works perfectly, the example scripts lists any IE windows running.

That 2nd machine has a couple more features installed, a IIS running compared to my fresh Win2008 install.

Does anyone know why IE is ignored by $oShellWindows=$oShell.windows on a fresh Win2008 install?


Share this post

Link to post
Share on other sites

Suggest you add a COM error handler just to be certain you are not being fooled by an early termination of your script. See ObjEvent


Free Internet Tools: DebugBar, AutoIt IE Builder, HTTP UDF, MODIV2, IE Developer Toolbar, IEDocMon, Fiddler, HTML Validator, WGet, curl

MSDN docs: InternetExplorer Object, Document Object, Overviews and Tutorials, DHTML Objects, DHTML Events, WinHttpRequest, XmlHttpRequest, Cross-Frame Scripting, Office object model

Automate input type=file (Related)

Alternative to _IECreateEmbedded? better: _IECreatePseudoEmbedded  Better Better?

IE.au3 issues with Vista - Workarounds

SciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=Y Doesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead?

Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this