Fixed the error "Can`t find script file run.vbs" at logon

Fixed the error “Can`t find script file run.vbs” at logon

In today’s post, we will try to solve the problem related to the error message “Can`t find script file run.VBS at logon” in Windows 10. This Windows script host is displayed on a blank screen with a black background. This happens when the malware has changed the Userinit registry value and replaced the default Windows data with the VBScript file name.

Userinit.exe is the file responsible for executing login scripts, restoring network connections, and then launching Explorer.exe. It is a secure file for your PC. Winlogon is an integral part of a series of Windows operating systems that manage the secure loading of a user profile during login.


What is the cause of the “Could not find the script file run.VBS” error when logging in?

What is the cause of the "Could not find the script file run.VBS" error when logging in?

A black screen may appear when you try to log on to your computer because the malware manipulates the Userinit registry value and changes the Windows default values with the Vbscript file name. As users delete or move the .vbs file from the System32 shared folder, they receive an error message “The C: Windows script file Vbs cannot be found.”

In general, the malware causing the “C: Windows Script File. Un.vbs can’t be found” problem is spread via unsolicited email attachments, peer-to-peer (P2P) networks, or malicious ads. Users who tend to illegally download music or movies, click on suspicious online advertisements, or open unsolicited emails risk infecting their computer with this and other cyber threats.

Note: that the malware that results in the error message “Script file C: Windows VBS cannot be found” can be programmed to perform other malicious actions on your system, including the following:

  • Recording keystrokes.
  • Injecting potentially unwanted programs (PUPs) or malware.
  • Creating a backdoor by connecting your PC to a remote server.


To solve the problem “Cannot find script file run.VBS” error when logging in

To solve the problem "Cannot find script file run.VBS" error when logging in

Use Windows Restore Point

Because of the black screen, it is difficult to find and remove the malware that causes booting problems. Therefore, you should use a system restore point and restore your operating system to the point where you do not have this malware on your computer.

To restore your system, follow these steps:

  1. Press the Windows + R key to open the Run dialog box. Now type %systemroot%system32rstrui.exe and press Enter or OK.
  2. Select Select a different restore point and press Next.
  3. Now check the Show other recovery points checkbox and select the desired recovery point from the menu. Note the date and time section and select the time when the problem did not exist on your PC. Now click on Next to continue.
  4. Follow the instructions on the screen to complete the recovery process.
Perform the following commands

If your computer does not have a system restore point, follow these troubleshooting steps:

  1. Type cmd in the search menu -> run the command line as an administrator.
  2. Enter the following commands:
  • reg add “HKLMSoftwareMicrosoftWindows NTCurrentVersionWinlogon” /v “Shell” /t REG_SZ /d “explorer.exe” /f
  • reg add “HKLMSoftwareMicrosoftWindows NTCurrentVersionWinlogon” /v “Userinit” /t REG_SZ /d “C:WindowsSystem32userinit.exe,” /f
  • reg add “HKLMSoftwareWow6432NodeMicrosoftWindows NTCurrentVersionWinlogon” /v “Shell” /t REG_SZ /t REG_SZ /d “explorer.exe” /f

After running all the commands, restart your computer.

Perform a detailed system scan

It is very likely that the run.VBS error is caused by malware on your computer. Sometimes malware modifies your registry and causes this problem.

To make sure that your system is free of malware, we recommend running a full system scan with your antivirus program. It’s important to note that not all antivirus utilities are equally effective, so we recommend you check out our top antivirus utilities.

Once you have performed a full system scan and removed all malware from your PC, the problem should be completely solved.

Edit your registry

If you are getting run.VBS error on your computer, the problem might be in your registry. Sometimes, malicious applications can modify your registry and cause this problem. However, you can easily fix the problem by making some changes to your registry. To do this, simply perform the following steps:

  1. Press the Windows + R key and type Regedit. Now press Enter or OK.
  2. When the registry editor opens, go to the left pane of HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon. In the right pane, double-click the Userinit value.
  3. Make sure that these values are set to C:Windowssystem32userinit.exe are set and now click OK to save your changes.

Sometimes your PC may be infected with malware that changes the username value in the registry. However, after modifying the registry, the problem should be completely solved.

Perform SFC and DISM scans

If you have run.VBS error on your computer, the cause may be a corrupted system file. However, you can easily solve this problem by running an SFC and DISM scan on your PC. To do this, do the following steps:

  1. Press the Windows + X key to open the Win + X menu. Select Command Prompt (Admin) or PowerShell (Admin).
  2. When the command line starts, type and execute the SFC / scan now command.
  3. The SFC scan will now begin. Keep in mind that the scan may take about 15 minutes, so do not disrupt it in any way.

Once the SFC scan is complete, the problem should be resolved. If the problem persists, a DISM scan should be performed. To do this, perform the following steps:

  1. Run the command line as an administrator.
  2. Execute the command DISM /Online /Cleanup-Image / RestoreHealth.
  3. The DISM scan will now start. This scan may take about 20 minutes or more, so do not interrupt it.

After the DISM scan is complete, check if there is a problem. If you see nothing but a black screen you should go to the command line as follows:

  1. Press Ctrl + Shift + Esc to launch the Task Manager.
  2. Now go to File -> Run New Task.
  3. Type cmd and make sure that the Create this task with administrator privileges option is checked. Now click OK or press Enter.
  4. Once the prompt is running, run the SFC and DISM scans.
Going to Safe Mode

Safe Mode is a segment of Windows that runs with default settings, making it ideal for problems like run.VBS. To enter Safe Mode, follow these steps:

  1. Reboot your computer several times during the boot process.
  2. You will see three options. Select Troubleshooting -> Advanced -> Boot Settings. Click the Restart button.
  3. Your computer will restart. Once your computer has booted, select any version of Safe Mode by pressing the appropriate key on your keyboard.

After entering Safe Mode, check to see if the problem exists. If the problem does not occur in Safe Mode, you can use it to solve it.


Frequently Asked Questions

  1. Check the property of the script.
  2. Reinstall the program.
  3. Restore win login entry in the registry.
  4. Restore the .vbs entry in the registry.
  5. Run a virus scan.

A permanent solution. Right-click on Octave GUI, properties, check target location. Change it from the octave. VBS to Octave for the first time.

  1. Run the Microsoft Safety Scanner.
  2. Run SFC.
  3. Reboot.
  4. Change the value of .vbs
  5. Delete entries after Userinit.exe.
  6. Try to repair installation.

  1. Click Start > Run > cmd or hit Search and type cmd.
  2. Press Enter.
  3. On the command line, type assoc .vbs, which will result in .vbs=VBSFile.
  4. Type f type VBSFile at the command line.

Leave a Reply

Your email address will not be published. Required fields are marked *