A program or firewall is not compatible with Windows Vista - wscript.exe

I get this error on two Vista machines here at work.  Not sure what could be causing it other than our domain login script.  I've found no more in depth information in the event logs on these two boxes either.. Also our default domain gpo turns off windows firewall.

Anyone else run into this problem?
LVL 14
Ben HartAsked:
Who is Participating?
Ben HartConnect With a Mentor Author Commented:
I've taken your comment and I'm throwing it to a local resource that's more knowledgable in how to accomplish this than I am.  I'm thinking that we're going to have to alter or "convert" the wscript portions of our login script to cscript but whether or not that includes syntax or layout changes to the file is beyond me.  I will post back with some findings..
If this is happening on the machines as somebody is logging in then this makes me think there is one of two things happening.
1. The script is executing a vb/vbs file and it is trying to do something that Vista will not allow.   Assumes that you have no other Vista machines or that they are not running the same login script.
2. since wscript appears to be causing the error ... this might be a problem with the script association.
Typically in a batch environment (such as a logon script) you would execute a vb script using cscript ... the problem could be that the reference to the script executable is not defined on these machines and it is defaulting to wscript and not cscript and wscript has some issue with what ever is being executed.

In the case of issue number 2, either fully qualify the use of cscript in the login script when executing the script or make cscript the default association for vb script files on the machines that are having problems.
Ben HartAuthor Commented:
That all sounds like exceptional information.  Almost all of it over my head ;p

Ok so maybe this will help, what we've got is a batch file calling a VB Script.  Now I've looked through the contents of the vbs and I do see a couple commands such as "Dim wshell" and "Set wshell = CreateObject("WScript.Shell")"  Which I will assume tthose might be the problem.

Let me ask though since I have no clue.. Was there a version difference between XP and Vista's WSH?  

And while I've heard of WScript before I have no heard of CScript.. is that built into Windows as well? Or the support for such?
yes, both wscript and cscript come with the OS.
w = windows (produces alert boxes and does windows stuff)
c = command line (for use in batch scripts and such)

The version of the WSH (Windows Scripting Host) that ships with Vista is a newer version than the default that is on XP.  There appear to be bug fixes but I'm not reading anything about enhancements made in this version, unless you are using an older version than 5.6 on the XP machines.  Here is a link to the release notes for v 5.7 http://download.microsoft.com/download/f/f/e/ffea3abf-b55f-4924-b5a5-bde0805ad67c/Windows%20Script%20Release%20Notes.rtf

Here is the page where I got the link, you can also download v5.7 of WSH for XP and other platforms.  This might let you test and fix the problem by being able to reproduce it on an XP machine.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.