vbScript on VISTA Problems?

Are there major problems with using vbScripts in my application
installation on VISTA systems? I've searched the net and basically
found that the the vbscript.dll is included with that operating
system, but is not registered. It seemed from the various posts that
simply registering the .dll solved the problem.

Is there a reason this .dll is included and not registered or was this
just an oversight by Microsoft? If an oversight, are there plans to
remedy this by registering it in the future or including registration
of it in a hotfix or service pack?

If there are any other problems outside of this information, which may
cause problems with including vbScripts in installations that may be
run on VISTA, please let me know.

THANKS in advance for any and all information you may provide.

J
Thu May 10 12:37:13 CDT 2007

i have no clue what youre talking about. vista runs vbscript just fine
without having to register anything



"Superfreak3" <Matt.Walker@synergis.com> wrote in message
news:1178808047.663195.217770@y5g2000hsa.googlegroups.com...
> Are there major problems with using vbScripts in my application
> installation on VISTA systems? I've searched the net and basically
> found that the the vbscript.dll is included with that operating
> system, but is not registered. It seemed from the various posts that
> simply registering the .dll solved the problem.
>
> Is there a reason this .dll is included and not registered or was this
> just an oversight by Microsoft? If an oversight, are there plans to
> remedy this by registering it in the future or including registration
> of it in a hotfix or service pack?
>
> If there are any other problems outside of this information, which may
> cause problems with including vbScripts in installations that may be
> run on VISTA, please let me know.
>
> THANKS in advance for any and all information you may provide.
>

Richard
Thu May 10 12:40:00 CDT 2007

Superfreak3 wrote:

> Are there major problems with using vbScripts in my application
> installation on VISTA systems? I've searched the net and basically
> found that the the vbscript.dll is included with that operating
> system, but is not registered. It seemed from the various posts that
> simply registering the .dll solved the problem.
>
> Is there a reason this .dll is included and not registered or was this
> just an oversight by Microsoft? If an oversight, are there plans to
> remedy this by registering it in the future or including registration
> of it in a hotfix or service pack?
>
> If there are any other problems outside of this information, which may
> cause problems with including vbScripts in installations that may be
> run on VISTA, please let me know.
>

I bought a new system with Vista pre-installed and have had no problems
running VBScript programs. I can't imagine why the dll would not be
registered. I don't recall seeing any similar reports. If a script (or any
program) attempts to do something requiring administrative privileges on a
Vista machine, it will not work unless you do something to elevate the
privileges. The fact that you are using an account with administrative
privileges on the machine to run the program does not help. Also, I note
that some virus software blocks scripts.

Do you get an error message? Are you running the script at a command prompt
with the cscript host?

--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
--

Superfreak3
Thu May 10 13:25:11 CDT 2007

On May 10, 1:40 pm, "Richard Mueller [MVP]" <rlmueller-
nos...@ameritech.nospam.net> wrote:
> Superfreak3wrote:
> > Are there major problems with using vbScripts in my application
> > installation on VISTA systems? I've searched the net and basically
> > found that the the vbscript.dll is included with that operating
> > system, but is not registered. It seemed from the various posts that
> > simply registering the .dll solved the problem.
>
> > Is there a reason this .dll is included and not registered or was this
> > just an oversight by Microsoft? If an oversight, are there plans to
> > remedy this by registering it in the future or including registration
> > of it in a hotfix or service pack?
>
> > If there are any other problems outside of this information, which may
> > cause problems with including vbScripts in installations that may be
> > run on VISTA, please let me know.
>
> I bought a new system with Vista pre-installed and have had no problems
> running VBScript programs. I can't imagine why the dll would not be
> registered. I don't recall seeing any similar reports. If a script (or any
> program) attempts to do something requiring administrative privileges on a
> Vista machine, it will not work unless you do something to elevate the
> privileges. The fact that you are using an account with administrative
> privileges on the machine to run the program does not help. Also, I note
> that some virus software blocks scripts.
>
> Do you get an error message? Are you running the script at a command prompt
> with the cscript host?
>
> --
> Richard Mueller
> Microsoft MVP Scripting and ADSI
> Hilltop Lab -http://www.rlmueller.net
> --- Hide quoted text -
>
> - Show quoted text -

I haven't actually experienced problems yet. I was just going by what
I was reading in posts (Shouldn't believe everything I read, I
guess!). Maybe there were problems with early/beta versions of VISTA
or something. I feel better just reading your posts! I'm just trying
to prepare myself for changes I might have to make to our Windows
Installer based installations.

Thanks all!

Richard
Thu May 10 14:04:24 CDT 2007


> I haven't actually experienced problems yet. I was just going by what
> I was reading in posts (Shouldn't believe everything I read, I
> guess!). Maybe there were problems with early/beta versions of VISTA
> or something. I feel better just reading your posts! I'm just trying
> to prepare myself for changes I might have to make to our Windows
> Installer based installations.
>
> Thanks all!
>

The one issue to be concerned about is installation programs. All of my
setup programs (VBScript or VB) fail under Vista. This is due to the new
security features, in particular User Account Control (UAC). My VBScript
programs that write to the registry, for example, fail.

I use InstallShield to create many setup programs. This had to be upgraded
to a new version that handles Vista. Setups created with previous versions
of InstallShield all fail.

One solution for VBScript programs is to run them in a command window
launched with "Run as Administrator", but the user will get a screen asking
them to confirm (and provide admin credentials if they are not admin).
Another solution is to provide something called a manifest. I have not
investigated this yet.

Writing to the registry is especially tricky. You may think you have written
to HKLM, but instead the OS has written to a new virtual location in the
registry. The setting is only available to you (the user that ran the
program), not other users.

My solution so far has been to use a new version of InstallShield. Any
programs you write need to be tested. I would research manifests.

--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
--

Superfreak3
Thu May 10 14:20:03 CDT 2007

On May 10, 3:04 pm, "Richard Mueller [MVP]" <rlmueller-
nos...@ameritech.nospam.net> wrote:
> > I haven't actually experienced problems yet. I was just going by what
> > I was reading in posts (Shouldn't believe everything I read, I
> > guess!). Maybe there were problems with early/beta versions of VISTA
> > or something. I feel better just reading your posts! I'm just trying
> > to prepare myself for changes I might have to make to our Windows
> > Installer based installations.
>
> > Thanks all!
>
> The one issue to be concerned about is installation programs. All of my
> setup programs (VBScript or VB) fail under Vista. This is due to the new
> security features, in particular User Account Control (UAC). My VBScript
> programs that write to the registry, for example, fail.
>
> I use InstallShield to create many setup programs. This had to be upgraded
> to a new version that handles Vista. Setups created with previous versions
> of InstallShield all fail.
>
> One solution for VBScript programs is to run them in a command window
> launched with "Run as Administrator", but the user will get a screen asking
> them to confirm (and provide admin credentials if they are not admin).
> Another solution is to provide something called a manifest. I have not
> investigated this yet.
>
> Writing to the registry is especially tricky. You may think you have written
> to HKLM, but instead the OS has written to a new virtual location in the
> registry. The setting is only available to you (the user that ran the
> program), not other users.
>
> My solution so far has been to use a new version of InstallShield. Any
> programs you write need to be tested. I would research manifests.
>
> --
> Richard Mueller
> Microsoft MVP Scripting and ADSI
> Hilltop Lab -http://www.rlmueller.net
> --

Thanks for the information. I wonder if my scripts will run on VISTA
if I'm only checking a web extension in one of the scripts and
extracting an .rtf file from the Binary table of my .msi and printing
it in the other script? I guess when we start testing on that
platform we'll see.

Richard
Thu May 10 19:03:09 CDT 2007


"Superfreak3" <Matt.Walker@synergis.com> wrote in message
news:1178824803.935859.304960@e51g2000hsg.googlegroups.com...
> On May 10, 3:04 pm, "Richard Mueller [MVP]" <rlmueller-
> nos...@ameritech.nospam.net> wrote:
>> > I haven't actually experienced problems yet. I was just going by what
>> > I was reading in posts (Shouldn't believe everything I read, I
>> > guess!). Maybe there were problems with early/beta versions of VISTA
>> > or something. I feel better just reading your posts! I'm just trying
>> > to prepare myself for changes I might have to make to our Windows
>> > Installer based installations.
>>
>> > Thanks all!
>>
>> The one issue to be concerned about is installation programs. All of my
>> setup programs (VBScript or VB) fail under Vista. This is due to the new
>> security features, in particular User Account Control (UAC). My VBScript
>> programs that write to the registry, for example, fail.
>>
>> I use InstallShield to create many setup programs. This had to be
>> upgraded
>> to a new version that handles Vista. Setups created with previous
>> versions
>> of InstallShield all fail.
>>
>> One solution for VBScript programs is to run them in a command window
>> launched with "Run as Administrator", but the user will get a screen
>> asking
>> them to confirm (and provide admin credentials if they are not admin).
>> Another solution is to provide something called a manifest. I have not
>> investigated this yet.
>>
>> Writing to the registry is especially tricky. You may think you have
>> written
>> to HKLM, but instead the OS has written to a new virtual location in the
>> registry. The setting is only available to you (the user that ran the
>> program), not other users.
>>
>> My solution so far has been to use a new version of InstallShield. Any
>> programs you write need to be tested. I would research manifests.
>>
>> --
>> Richard Mueller
>> Microsoft MVP Scripting and ADSI
>> Hilltop Lab -http://www.rlmueller.net
>> --
>
> Thanks for the information. I wonder if my scripts will run on VISTA
> if I'm only checking a web extension in one of the scripts and
> extracting an .rtf file from the Binary table of my .msi and printing
> it in the other script? I guess when we start testing on that
> platform we'll see.
>

That sounds ok. If you can perform the task manually on a Vista computer
without getting the User Account Control dialog asking for your permission
to continue, you should be fine.

--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
--

r
Tue May 22 17:50:44 CDT 2007

The VBScript error shows up under Vista when you try to install either
Quicktime or ITunes+Quicktime for Windows as downloaded from Apple's
site. The error dialog is as follows: "iTunes could not be installed
because Visual Basic Script (VBScript) is not installed or has been
disabled. Make sure VBScript is installed, turn off script blocking
in anti-virus and personal firewall software, re-register VBScript,
and then install iTunes." I did try to shut down my Norton Firewall
for 15 minutes and to run the .exe as administrator. No luck. Unlike
some posters to this issue, I do not know how to "re-register
VBScript" but I will continue searching. Interestingly, the first
dialog put up by Microsoft Expression Media is a message that
Quicktime is not installed and this message sends you to Apple's site
to download and install Quicktime. It would be nice if one of the
frequent security updates from Windows Update would quietly fix this
problem. Hence, it is not clear how I run Windows Expression Media
until I can install Quicktime.

r
Wed May 23 05:13:46 CDT 2007

On another post, this problem was solved. I quote:

In my case I opened a command prompt and changed to the \windows
\system32
directory. Then I entered 'regsvr32 vbscript.dll' (without the
quotes).

The command prompt shoud be opened with "Run as adminstrator". In my
case,
the command prompt opened in C:\Windows\System32 which is where the
file
vbscript.dll resides. Hence the command

regsver32 vbscript.dll

could be executed immediately.

After that iTunes+Quicktime installed with no hassle and then
Expression Media
also ran properly.

craigatmetrol
Wed Jun 06 06:40:43 CDT 2007

On 10 May, 20:04, "Richard Mueller [MVP]" <rlmueller-
nos...@ameritech.nospam.net> wrote:
> > I haven't actually experienced problems yet. I was just going by what
> > I was reading in posts (Shouldn't believe everything I read, I
> > guess!). Maybe there were problems with early/beta versions ofVISTA
> > or something. I feel better just reading your posts! I'm just trying
> > to prepare myself for changes I might have to make to our Windows
> > Installer based installations.
>
> > Thanks all!
>
> The one issue to be concerned about is installation programs. All of my
> setup programs (VBScript or VB) fail underVista. This is due to the new
> security features, in particular User Account Control (UAC). My VBScript
> programs that write to the registry, for example, fail.
>
> I use InstallShield to create many setup programs. This had to be upgraded
> to a new version that handlesVista. Setups created with previous versions
> of InstallShield all fail.
>
> One solution for VBScript programs is to run them in a command window
> launched with "Run as Administrator", but the user will get a screen asking
> them to confirm (and provide admin credentials if they are not admin).
> Another solution is to provide something called a manifest. I have not
> investigated this yet.
>
> Writing to the registry is especially tricky. You may think you have written
> to HKLM, but instead the OS has written to a new virtual location in the
> registry. The setting is only available to you (the user that ran the
> program), not other users.
>
> My solution so far has been to use a new version of InstallShield. Any
> programs you write need to be tested. I would research manifests.
>
> --
> Richard Mueller
> Microsoft MVP Scripting and ADSI
> Hilltop Lab -http://www.rlmueller.net
> --

That works thanks. But is there anyway of setting up a vbscript so it
will run automatically as an administrator, without such a
workaround? I know there is a way of setting an exe file so it will
run as administrator but this option does not seem to apply to
vbscripts.
from
Craig