Is there a way to close IE browser programmatically?
blabla12345
satisfactory.
What I'd like to do is for a software installation package to start IE
and run the final configuration and close the browser.
Just searched for "launch IE quietly/silently" for a possible to no
avail, so, the question stand.
Many thanks as usual.
foxidrive
What if IE is running on the PC before your installation start? The
user wouldn't appreciate it being closed.
You can do this in batch
1) detect if MSIE is open and store the info
2) do your install
3) if MSIE was started by your install then close MSIE
The tool to find out if MSIE was running is tasklist.exe but it is not
available on all OS. Ditto with taskkill.exe which you would use to
close MSIE.
--
Regards,
Mic
blabla12345
> On Tue, 13 Jul 2010 17:50:07 -0700 (PDT), blabla12345
>
Great, thank you very much, Mic.
Don
blabla12345
But Mic, there's an issue. When the batch script has something like
the following the taskkill.exe utility did not kill the loaded IE:
1) launch IE, do some stuff;
2) Wait for 40 second for IE to do its job (ping -n 40 >nul)
3) close IE (taskkill -im iexplore.exe)
My testing with my Vista Pro box last night did not seem to complete
the above 2) and 3). And it seems rightly so because batch is
procedural. So, is there a way to solve this problem with batch?
Thanks.
Don
foxidrive
<tatat...@gmail.com> wrote:
>> > What if IE is running on the PC before your installation start? The
>> > user wouldn't appreciate it being closed.
>>
>> > You can do this in batch
>>
>> > 1) detect if MSIE is open and store the info
>> > 2) do your install
>> > 3) if MSIE was started by your install then close MSIE
>>
>> > The tool to find out if MSIE was running is tasklist.exe but it is not
>> > available on all OS. Ditto with taskkill.exe which you would use to
>> > close MSIE.
>>
>But Mic, there's an issue. When the batch script has something like
>the following the taskkill.exe utility did not kill the loaded IE:
>1) launch IE, do some stuff;
>2) Wait for 40 second for IE to do its job (ping -n 40 >nul)
>3) close IE (taskkill -im iexplore.exe)
>
>My testing with my Vista Pro box last night did not seem to complete
>the above 2) and 3). And it seems rightly so because batch is
>procedural. So, is there a way to solve this problem with batch?
Try it from the command line. Here is what happens in XP Pro and note
the /f in the second invocation.
===[paste]===
M:\>taskkill /im iexplore.exe
SUCCESS: The process "iexplore.exe" with PID 4192 has been terminated.
SUCCESS: The process "iexplore.exe" with PID 6316 has been terminated.
M:\>taskkill /f /im iexplore.exe
SUCCESS: The process "iexplore.exe" with PID 3068 has been terminated.
SUCCESS: The process "iexplore.exe" with PID 7768 has been terminated.
===[paste]===
--
Regards,
Mic
blabla12345
Mic,
I'm on Vista Pro, the 2 command sets made no difference. Both closed
IE respectively. I understand the /f switch is a forced kill. I was
concerned that batch stops after IE launch.
Thanks.
Don
foxidrive
<tatat...@gmail.com> wrote:
>> >But Mic, there's an issue. When the batch script has something like
>> >the following the taskkill.exe utility did not kill the loaded IE:
>> >1) launch IE, do some stuff;
>> >2) Wait for 40 second for IE to do its job (ping -n 40 >nul)
>> >3) close IE (taskkill -im iexplore.exe)
>>
>> >My testing with my Vista Pro box last night did not seem to complete
>> >the above 2) and 3). And it seems rightly so because batch is
>> >procedural. So, is there a way to solve this problem with batch?
>>
>> Try it from the command line. Here is what happens in XP Pro and note
>> the /f in the second invocation.
>>
>> ===[paste]===
>> M:\>taskkill /f /im iexplore.exe
>> ===[paste]===
>
>I'm on Vista Pro, the 2 command sets made no difference. Both closed
>IE respectively. I understand the /f switch is a forced kill. I was
>concerned that batch stops after IE launch.
So it works ok. Your batch file will work too - but your ping command
had incorrect syntax.
Try this:
@echo off
start "" "%ProgramFiles%\Internet Explorer\iexplore.exe"
ping -n 40 localhost >nul
taskkill /f /im iexplore.exe
--
Regards,
Mic
blabla12345
I just looked at my batch file, it did have a target (localhost), my
bad, for the omission in previous posting.
As I recall my installation launched IE and did a bit of work (will
always be less than 1 minute I can almost guaranttee it) and then
stayed that way for about 2 minutes then I closed it. I don't
understand why. Thanks tho.
Esra Sdrawkcab
wrote:
Works here (XP Pro)
--
Nuns! Nuns! Reverse
Todd Vargo
======================
You didn't say what IE does. Have you tried including /T to the taskkill
command?
taskkill /f /im iexplore.exe /t
--
Todd Vargo
(Post questions to group only. Remove "z" to email personal messages)
--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---
Todd Vargo
Ditto. Note, OP did not comment on running the test batch exactly as posted.
OP commented on their installer instead using the phrase, "as I recall".
I recommend the OP post their batch code exactly as used when it fails.
Also, post any output displayed too. Taskkill should be displaying some
output.
ten.n...@virgin.net
You could, (depending upon some factors), use WMIC for the opening and
closing of IE.
::----- START -----
@Echo off & Setlocal enableextensions
For /f "tokens=2*" %%a In ('Reg query^
"HKLM\SOFTWARE\Classes\Applications\iexplore.exe\shell\open\command"^|^
Find "_SZ"') Do Call :Sub %%b
Goto :Eof
:Sub
For /F "usebackq tokens=2 delims==; " %%# In (
`Wmic Process CALL Create '%~1'^|Find "ProcessId"`) Do Set "_=%%#"
Ping -n 40 127.0.0.1 1>NUL
Wmic Process WHERE "ProcessId='%_%'" CALL Terminate 1>NUL
::------ END ------
The idea of this is that it uses the process handle of the instance of IE
opened in order to closes that same instance. This means that if you
already have an instance of IE open then it should be left untouched by
this process.
foxidrive
This has an issue that taskkill also has: When MSIE starts the next time
it gives me a warning message box that "the last session terminated...
restore your last session?" type thing.
On my machine the code above also fails to start MSIE because the output
from reg.exe must be different in XP.
! REG.EXE VERSION 3.0
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\iexplore.exe\shell\open\command
<NO NAME> REG_SZ "C:\Program Files\Internet Explorer\IEXPLORE.EXE" %1
--
Regards,
Mic
ten.n...@virgin.net
This is my reg.exe output on Vista:
::----- CONSOLE -----
C:\Users\TenNigriv>reg query
"HKLM\SOFTWARE\Classes\Applications\iexplore.exe\shell\
open\command"
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Applications\iexplore.exe\shell\open\command
(Default) REG_SZ "C:\Program Files\Internet
Explorer\iexplore.exe" %1
::-------------------
It doesn't output the top line but the important line appears to be the
same.
*, in this case %%b should still be set to:
"C:\Program Files\Internet Explorer\iexplore.exe" %1
I would think that the message box is a 'feature' which if bypassed would
probably, in the main, be a bad idea.
ten.n...@virgin.net
Not that all of this matters very much because I've just had an opportunity
to test it and it appears that with another instance of IE already open,
the script fails to terminate the newly created window!
foxidrive
>>> <NO NAME> REG_SZ "C:\Program Files\Internet Explorer\IEXPLORE.EXE" %1
>> (Default) REG_SZ "C:\Program Files\Internet
>> It doesn't output the top line but the important line appears to be the
>> same.
>> *, in this case %%b should still be set to:
>> "C:\Program Files\Internet Explorer\iexplore.exe" %1
No, the line from mine on XP has an extra token because of the space in
the first term.
>> I would think that the message box is a 'feature' which if bypassed would
>> probably, in the main, be a bad idea.
True. It's just that these methods adds something that the user may not
expect.
>Not that all of this matters very much because I've just had an opportunity
>to test it and it appears that with another instance of IE already open,
>the script fails to terminate the newly created window!
Confirmed.
--
Regards,
Mic
Esra Sdrawkcab
Given these difficulties can I suggest a scripted keypress solution?
(i.e. use a known, hopefully unique name for the iexplorer window and send
Alt-F4 to it.)
Scriptit I used to use. I don't know if there are newer better ones around
now.
{scroogle search}. Apparently Autoit is the one.
--
Nuns! Nuns! Reverse
blabla12345
Guys, thank you all for the efforts.
Here's some more details.
I use a zip to exe utility called winRar
to turn the zip file to an exe installer.
And the last batch file has the following routine for launching
IE to do the last leg of a little configuration.
:launch
REM regardless launch IE for the installation
"C:\Program Files\Internet Explorer\iexplore.exe"
http://127.0.0.1:8600/KNB2/verifyAccessDB.cfm
REM give it 40 seconds to do its work
ping -n 40 localhost >nul
REM close IE
taskkill /im iexplore.exe
Comment:
I could have added the /f switch for the taskkill.exe for the last
line above but I forgot, not sure it would make the critical
difference.
Oddity (my observation):
For the last test installation (7/14/2010), the installer put
KnowledgeNoteBook directory under "Program Files" but by design and in
the past, it was directly under C:\ drive. I'm not sure if MS or
something else is messing me up, not making an accusation but
speculating.
blabla12345
Oh, in case some of you would want to see EXACTLY how the installer
would work with your box, here's the URL to try it,
http://www.knowledgenotebook.com/
(I use the root URL for additional information such as installation
instructions). Thanks.
As for the alternate key or the like, I'm a bit concerned that it's an
extra step... many users under 20 are spoiled...
foxidrive
<tatat...@gmail.com> wrote:
>Oddity (my observation):
>For the last test installation (7/14/2010), the installer put
>KnowledgeNoteBook directory under "Program Files" but by design and in
>the past, it was directly under C:\ drive. I'm not sure if MS or
>something else is messing me up, not making an accusation but
>speculating.
It's my observation that newer versions of windows don't like
users/programs writing to the root or anywhere except their user
folders.
--
Regards,
Mic
blabla12345
> On Fri, 16 Jul 2010 08:11:46 -0700 (PDT), blabla12345
>
> >Oddity (my observation):
> >For the last test installation (7/14/2010), the installer put
> >KnowledgeNoteBook directory under "Program Files" but by design and in
> >the past, it was directly under C:\ drive. I'm not sure if MS or
> >something else is messing me up, not making an accusation but
> >speculating.
>
> It's my observation that newer versions of windows don't like
> users/programs writing to the root or anywhere except their user
> folders.
>
> --
> Regards,
> Mic
Ok, thanks, Mic.
Don