FIX: Windows Can not find script file "C:Windowsrun.vbs" [2021 Tutorial]

Windows Script Host is an administration tool built in every Windows operating system. Its main function is the scripting abilities like batch files. The Windows Script Host error may appear on your Windows 10/8/7 computer due to virus invasion, registry errors, or VBS script file.

A Windows Script Host error can often be mistaken for a virus or malware. While that’s possible, there are still a few things we can try to stop this error from appearing.

When you log in to the computer and you see a message box with an error message saying “Can not find script file C:\Windows\run.vbs” error on Windows. More specifically, when users try to log in, a pop-up window appears on a black screen, informing users that the script file run.vbs is missing. This error occurs when a malicious program modifies your computer’s registry. Fortunately, there is one easy workaround that you can use to fix this problem, so let’s get started!

Just follow these easy steps:
A FRIENDLY REMINDER: PLEASE DO A BACKUP OF YOUR REGISTRY!
1. Open the Registry Editor and navigate to: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon
2. On the right pane, scroll down to Userinit. The default value of the string is “C:Windowssystem32userinit.exe,” so if there is anything else than that, make sure to change it to default value. When ready, click the OK button.
3. Restart your PC to apply changes.

SCAN YOUR PC WITH SYSTEM FILE CHECKER (SFC /SCANNOW)
System File Checker (SFC) is a command-line tool designed to scan the integrity and restore missing or corrupted system files with working replacements.

To repair a Windows 10 installation using the SFC command tool, use these steps:
1. Open Start.
2. Search for Command Prompt, right-click the top result, and select the Run as administrator option.
3. Type the following command to repair system files and press Enter: sfc /scannow
4. Confirm result:
Windows Resource Protection did not find any integrity violations – indicates that the system doesn’t have any missing or corrupted files.
Windows Resource Protection could not perform the requested operation – indicates that a problem was detected during the scan, and an offline scan is required.
Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log %WinDir%LogsCBSCBS.log – indicates that SFC detected and was able to fix the problem.
Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log %WinDir%LogsCBSCBS.log – indicates that you have to repair the corrupted files manually.

Once you complete the steps, the System File Checker command will scan, detect, and try to fix problems with system files on Windows 10.

If the tool has detected an issue, it’s recommended to run the command at least three times to ensure that all the problems have been corrected.