Windows Script Host Error may seem like a virus or malware infection to the inexperienced eye, However, it's nothing but a bug with the VBScript file. Appears with all versions of the operating system, and it does not depend on any specific software that can activate it.
If this error occurs, people may advise you to scan your system for malware, but some users have even reported that their antivirus cleaned the virus but left the entry intact to activate the .vbs file and still got the error.
Even so, there are a few things you can try to solve this problem, and different users have reported that they all work, which means it may take a bit of trial and error to get it right, but the methods are guaranteed to help you. .
Method 1: Run the System File Checker to scan the system
This is a solution for a number of problems, and has been reported to work with this one too.
-
Open an elevated command prompt. This is done by pressing the Windows key on the keyboard, typing cmd, by right-clicking on the result and then choosing Run as administrator.
-
From elevated command prompt, type sfc / scannow and hit Enter on the keyboard. The command will scan the entire system integration and also fix any damage found inside. Later, shouldn't have this problem.
Method 2: use Registry Editor to solve the problem
Option 1: return the default value of .vbs to the VBS file
-
Simultaneously press the Windows and R keys on the keyboard to open the Run dialog box. Type regedit and hit Enter to open the Registry Editor.
-
In the left navigation panel, expand the HKEY_CLASSES_ROOT folder and click on the .vbs folder inside.
-
On the right side, double click the key (Predetermined) and set its value in VBSfile. Close the registry editor and your system should work fine now.
PROFESSIONAL SUGGESTION: If the problem is with your computer or laptop, you should try using Reimage Plus, which can scan repositories and replace damaged and lost files. This works in most cases, when the problem originates due to system corruption. You can download Reimage for By clicking here
Option 2: delete the entries after userinit.exe
-
Open Registry Editor as described in Step 1 from the previous method.
-
From the left navigation panel, expand the following folders: HKEY_LOCAL_MACHINE, then SOFTWARE, then Microsoft, then Windows NT, followed by CurrentVersion, At the end, click winlogon.
-
In the right window, remove all entries after userinit.exe. This will probably include wscript.exe and NewVirusRemoval.vbs. Close Registry Editor when done, and everything should work again.
Option 3: delete entry * .vbs that appears at the beginning
This method requires you to boot into Safe Mode, which is done by pressing F8 when you turn on your computer, just before Windows starts and choosing the Safe Mode option from the menu on a Windows Vista system and 7.
For Windows 8 Y 10, see the steps in »start Windows 8 O 10 in safe mode «
-
Once you have started in safe mode, open Registry Editor again as described above.
-
Press the Ctrl and F keys on your keyboard simultaneously to open the search menu. In the frame, type the name of the file that appears at startup and click the Find Next button.
-
This search will end in a folder with the key userint. Double click and you will see a series of paths, separated by commas. Look for the routes of “the VBS file” and delete the path. Be careful not to change any of the other paths.
-
Press F3 on your keyboard to see if the path is also somewhere else in your registry. If so, remove it by following the instructions in the previous step. Repeat this process until you receive a message saying the search is over. Close Registry Editor.
-
Press Windows and E at the same time on the keyboard to open File Explorer. Run a search for the VBS file, which appeared at the beginning on the partition where your operating system is installed, and delete that file too.
At the end of the day, this problem can be a tedious task to solve. However, if you just follow the instructions of the mentioned methods, get rid of it and never have to treat it again.
SUGGESTION: If none of the methods have solved your problem, we recommend that you use the Reimage repair tool, which can scan repositories to replace damaged and lost files. This works in most cases, when the problem originates due to a system corruption. Reimage will also optimize your system for maximum performance. You can download Reimage for By clicking here
