Cannot find script file run.vbs error at logon in Windows 11/10

In today’s post, we will attempt to resolve the issue as it relates to the error message Can not find script file C:\WINDOWS\run.vbs at logon in Windows 11/10. This Windows Script Host is shown, in a blank screen with a black background. This happens if malware has modified the Userinit registry value, replacing the Windows default value data with a VBScript filename.

Userinit.exe is the file responsible for executing logon scripts, reestablishing network connections and then starting Explorer.exe, and is a safe file for your PC. Winlogon is an essential component of the Windows series of operating systems that handle the secure loading of a user profile at the time of login.

Can not find script file run.vbs

You can encounter a black screen when trying to log in to the computer as the malicious program manipulates Userinit registry value and changes Windows default value data with Vbscript filename. Since this virus deletes or moves the .vbs file from the common System32 folder, users receive the error as shown above.

Usually, malware causing the issue spreads via spam email attachments, Peer-to-Peer (P2P) networks or malvertising – infecting computer users who tend to download music or movies illegally, click on suspicious online ads, or open spam emails.

It’s noteworthy that malware which is leading to “Can not find script file C:\Windows\run.vbs” error can be programmed to perform other malicious actions on your system, including the following:

Logging keystrokes
Infiltrating potentially unwanted programs (PUPs) or malware
Creating a backdoor by connecting the PC to the remote server.

There are two ways to fix “Can not find script file C:\Windows\run.vbs” error on Windows 10, viz:

1. Edit the Userinit registry value
2. Change the Registry value of .vbs key

These two methods can help you fix the run.vbs error fix and thereby regaining access to your user profile.

Before you begin, it’s recommended, you run a full system antivirus scan with Windows Defender or any reputable third-party AV product.

To proceed with the registry tweak solution, you’ll first need to backup the registry or create a system restore point in case the procedure goes south.

Once you have done either of the actions, you can now begin as follows;

1] Edit the Userinit registry value

After typing the login credentials, the system may stall at Preparing to log in screen. Press CTRL+ALT+DEL, and click Task Manager (if Task Manager doesn’t open due to DisableTaskMgr Policy enabled by the malware, you’ll need to edit the registry offline via Windows Recovery Environment).

When the above error message dialog is visible, dismiss the dialog and switch to the Task Manager window. The file referenced in the Userinit registry value is run even before the user interface loads. To start the Explorer shell, switch to the Task Manager window, click File, and select Run new task. Type explorer.exe and hit Enter.

Launch Registry Editor.

Navigate to the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon

Double-click on Userinit item.

Change the value data from

wscript C:WINDOWS\run.vbs

to the following:

C:\Windows\system32\userinit.exe

Click OK.

Take special care when entering. You need to remove the wscript part. And also include the trailing comma (,) as shown above. Typing an incorrect filename or path will prevent you from logging on to any user account.

Log off and log in again.

Check to see if the run.vbs issue is resolved.

Read: Fix Cannot find script file errors