Windows 10: Windows Script Host error on startup about a file "adhsvc.vbs" not being found.

I've been getting this error on every startup. When I go to the path described in the Script line and double click "adhsvc.vbs" which is not missing, I get the same error, upon every attempted opening. I've run Windows Security scans, I've tried using Windows Update, but to no avail.


Opening the script reveals this string:

Set WshShell = WScript.CreateObject"WScript.Shell"​

WshShell.Run """C:\Users\Joel\FXSCOVER\asferror.exe"""​

I don't know much about code, but it seems that the file missing is "asferror.exe". Again, no amount of scans or update or command-prompt integrity checks or even DISM commands finds either this error, nor this file, nor anything else.​

:)

 

Script host error after startup

Hi Luis,

To address script host errors, visit this article for step by step:

https://appuals.com/how-to-fix-windows-script-h...

You may also try to use Task Scheduler to view scheduled tasks at startup to isolate what causes this error.

Disclaimer: This is a non-Microsoft website. The page appears to be providing accurate, safe information that might solve your current issue.

Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products).

Thoroughly research any product advertised on the site before you decide to download and install it.

Let us know if this helped you out.

Your feedback is much appreciated.

Thanks and regards,

 

WINDOWS SCRIPT HOST ERROR on startup

when i start up my laptop i get this specific error from windows script host: c\users\shimon\appdata\roaming\3808.vbs the question is if this thing can affect my computer? and the other question is how to fix it.

 

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.