Introduction

You are facing an issue where Windows command-based script host "cscript" is not functioning properly. This causes the *.vbs and *.js scripts, which detect the applications, to not work properly.

Troubleshooting

First of all, make sure *.js and *.vbs scripts work on your machine:

Step 1

To check *.js scripts:

1. Create a *.txt file with the following text: WScript.Echo ("Hello, World");
2. Save it as *.js script, for example: test.js
3. Open command line as Administrator: Start -> Run -> cmd
4. Go to the directory where you have saved the script: cd <path-to-file>
5. Execute the following command: cscript test.js
6. The output should be the text, you've put in the script body: Hello, World

Step 2

To check *.vbs scripts:

1. Create a *.txt file with the following text: WScript.Echo "Hello, World"
2. Save it as *.vbs script, for example: test.vbs
3. Open command line as an Administrator: Start -> Run -> cmd
4. Go to the directory where you have saved the script: cd <path-to-file>
5. Execute the following command: cscript test.vbs
6. The output should be the text, you've put in the script body: Hello, World

If both scripts output the correct "Hello World" messages you can skip the current article since you do not have the problem described here. 

If you receive the error "Error: there is no script engine for file extension ".vbs(.js)"", do the following:

1. Type cmd in the Start, Run box, right-click on Command Prompt, click on Run as Administrator.
2. Type Regsvr32 vbscript.dll in order to insure, that it's registered correctly.
3. Type Regsvr32 jscript.dll in order to insure, that it's registered correctly.
4. Type cscript.exe //H:WScript to make wscript.exe process scripts by default. 
5. Type assoc .vbs=VBSFile to associate .vbs scripts with wscript.exe
6. Type assoc .js=JSFile to associate .js scripts with wscript.exe
7. If scripts execution returns correct text, restart Acronis Managed Machine Service.

More information

If you need further assistance, please collect System Information and contact Acronis Support with the reference to this article.