Well, that still doesn’t help (at all, I’m afraid).
- We don’t know what’s inside x64.bfswd
- We don’t know what your script is doing. The return code “1” is not being created by BigFix, that’s what cscript.exe is giving. And we have no way to know what the cscript.exe is doing because you haven’t posted the content of your script. (except that maybe I do see what’s happening)
Unbelievably, I think I actually do have a tip. Since you’re running ‘cscript /nologo “c:\install\uninstall\uninstall_x64”’ …well … cscript requires that the parameter have a script-type extension. Is that supposed to be uninstall_x64.vbs ? Uninstall_x64.js ?
If you had tried to run these command lines manually, you’d probably get something like
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Input Error: There is no file extension in "c:\install\uninstall\uninstall_x64"