Hot answers tagged

7

Very interesting question. I've seen some DEP faults from cscript.exe before. It's annoying. VBScript predates DEP in Windows, and as such it was not originally developed with DEP in mind. Furthermore when you start interacting with old, third-party COM and OLE interfaces in your scripts, they can cause NX faults and cscript.exe takes the blame for it. The ...


2

Yeap, this is a PITA and I ran into this when moving to 64 bit too. For me, I changed out the source path for cscript to: %windir%\syswow64\cmd.exe /C "cscript.exe <scriptname>.vbs" Basically cscript won't run unless you launch a 32bit version of the command line interpreter. Don't ask me why Redmond puts the 32bit one in the syswow64 folder. in ...


Only top voted, non community-wiki answers of a minimum length are eligible