Windows 10: When accessing vbs files windows script host appears in task manager

Hi!I have issue!I run automactic program . The program runs in continuous loops with vbs files. After 13 hours of continuous running, an error occurred when accessing vbs files, a window script host error occurred in task manager without notification. Please explain this issue to me

:)

 

Windows Script Host

Hi Tiara,

The message "Windows Script Host access is disabled on this machine. Contact your administrator for details" is usually occurring if a program that does not require the feature of Windows Script Host is running on a Windows PC. For us to provide an accurate
solution, we would need you to answer the following questions:

• Which build, version and edition of Windows is installed on your computer?
• Does the message appear when you are launching a specific application?
• What changes were made to the device before this issue happened?

For initial troubleshooting, we suggest following the steps provided by
Ramesh Srinivasan in this thread.

We are looking forward to your response.

 

Running a VB Script File Using Windows 10 Task Scheduler

You can invoke VB scripts through the Task Scheduler, same as batch files or .exe files. What problem do you actually have? What is the script you run? Is it supposed to be interactive?

There is little difference between cscript.exe and wscript.exe. When you run cscript.exe you will open a black Command Processor window (cmd.exe). With wscript.exe you won't. Furthermore, the instruction wscript.echo will do different things:

• Under cscript.exe: Write a line of text in the Command Processor window.
• Under wscript.exe: Generate message box.

This difference is important for scripts being invoked by the Task Scheduler.

 

How can I resolve the error of Windows Script Host which shows .vbs file not found?

As I turn on the system everytime, a sudden pop-up message shows Windows Script Host error which shows .vbs file not found. Is there any solution to resolve this issue? I had googled this but could not find the necessary steps to resolve this issue.