- 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” This happens when the malware has changed the.
- Userinit. value and replaced the default Windows data with the.
- script file name.
Using virtualization-based security, or VBS, Windows 11 isolates unsafe code from a secure memory enclave. VBS is also used to prevent unsigned or questionable software and drivers from entering memory through a feature called Hypervisor-Enforced Code Integrity (HVCI). Despite the fact that malware can get past your antivirus software, VBS and HVCI together provide a layer of protection against damage.
During today’s post, we will try to resolve an error message in Windows 10 referring to the run.VBS script not finding the script file at logon. This Windows script host displays a blank screen with a black background. Malware changes the Userinit registry value and replaces default Windows data with the name of the VBScript file.
Can Not Find Script File Startupcheck Vbs
StartupCheckLibrary does not provide any information about the producer.
The error appears when AppDataLocalUpdatesRun.vbs is run from a Windows Script Host. How can I fix it?
It executes login scripts, restores network connections, and launches Explorer.exe after executing login scripts. In Windows operating systems, Winlogon is an integral part of the secure loading of a user profile during login, making it a crucial part of ensuring a secure user experience.
What is the cause of the “Could not find the script file run.VBS” error when logging in?
The malware manipulates the Userinit registry value and changes the Windows default values with a name that sounds like Vbscript, which can cause a black screen to appear when attempting to log on to your computer. Users receive an error message “The C: Windows script file Vbs cannot be found” when deleting or moving the .vbs file from the System32 shared folder.
It is most common for malware to spread by unsolicited email attachments, peer-to-peer networks (P2P), or malicious ads to cause the “C: Windows Script File. Un.vbs can’t be found” problem. The risk of infection with this and other cyber threats increases for users who download illegally music or movies, click on suspicious online advertisements, or open unsolicited emails.
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:
- Keystroke recording.
- PUPs and malware can be injected into your computer.
- Through remote connection, you can create a backdoor on your computer.
To solve the problem “Cannot find script file run.VBS” error when logging in
Execution Of The Windows Script Host Failed Access Is Denied
After some Googling, someone suggested that I set HKLM/SOFTWARE/Microsoft/Windows Script Host/Settings/UseWINSAFER to 0 in the registry. That did not fix it however.
Use Windows Restore Point
You should use a system restore point to restore your operating system to a time when there was no malware on your computer that caused booting problems.
The following steps will guide you through restoring your system:
- Enter %systemroot%system32rstrui.exe in the Run dialog box by pressing Windows + R.
- By pressing Next, you will be able to select a different restore point.
- Select the desired recovery point from the menu, being sure to note the time and date of the recovery point. Now click on Next to proceed.
- The recovery process can be completed by following the instructions on the screen.
Perform the following commands
These troubleshooting steps are for computers that don’t have a system restore point:
- Run the command line as administrator by typing cmd in the search menu.
- It means “Reg Add “HKLMSoftwareMicrosoftWindows NTCurrentVersionWinlogon” /v “Shell” /t REG_SZ /d “explorer.exe” /f “explorer.exe”.
- The following registry entry is needed to add HKLMSoftwareMicrosoftWindows NTCurrentVersionWinlogon” /v “Userinit” /t REG_SZ /d “C:WindowsSystem32userinit.exe,” /f
- Registry editing “HKLMSoftwareWow6432NodeMicrosoftWindowsNTCurrentVersionWinlogon” . This code is only applicable to Shell.
You will need to restart your computer after you have run all the commands.
Perform a detailed system scan
Your computer may have a malware problem. Malware can modify your registry and cause the run.VBS error.
How To Open A Vbs File
The default settings for “txt” or text files in Notepad are “.txt” or text files. Select “All Files’ from the “File” menu to view VBS files.
Our top antivirus utilities can help ensure your system is free of malware. Rather than just relying on your firewall, it’s crucial to run a full system scan with your antivirus program.
You may encounter malware in the form of a script.vbs.js or.wsf when you run windows scripts with wscript.exe or cscript.exe errors.
The problem should be resolved completely after removing all malware from your PC through a full system scan.
Edit your registry
It is possible that your registry may be causing the run.VBS error. A malicious application can modify your registry, causing this problem. Nonetheless, by making some changes to your registry, you can easily fix the issue. Simply follow these steps to accomplish this:
- Enter Regedit or press Enter or OK after pressing Windows + R.
- Double-click the Userinit value in the right pane of the registry editor after you open it. You will see it under HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon on the left.
- Click OK to save your changes after setting the values to C:Windowssystem32userinit.exe.
Depending on the cause of the problem, the problem may be completely resolved after modifying the registry.
Perform SFC and DISM scans
In order to resolve the run.VBS error on your computer, you will need to run an SFC and DISM scan. The following steps will guide you through this process:
- You can access the PowerShell or Command Prompt (Admin) menu by pressing Windows + X together.
- SFC / scan now should be executed when you are prompted by the command line.
- You may need to wait 15 minutes for the SFC scan to begin. Do not interrupt the scan at any time.
It is highly recommended that you perform a DISM scan after completing the SFC scan if the problem persists. To do this, follow these steps:
- Make sure you are logged in as an administrator when running the command line.
- Make sure you have DISM /Online /Cleanup-Image / RestoreHealth enabled before proceeding.
- There may be a delay of up to 2 hours during the DISM scan, so do not interrupt it during this period.
In case there is a problem after the DISM scan is completed, enter the following commands at the command line:
- Using the Task Manager requires pressing Ctrl+Shift+Esc.
- You can now run a new task by clicking File – New Task.
- Then click OK or press Enter after typing cmd and selecting Create this task with administrator privileges.
- The SFC and DISM scans can be run once the prompt is running.
Going to Safe Mode
For problems such as run.VBS, enter Safe Mode, which runs with default settings.
- It is a good idea to reboot the computer several times while it is booting.
- Then select Troubleshooting – Advanced – Boot Settings and click Restart.
- If the computer is restarted, press the appropriate key on the keyboard to select one of the Safe Mode versions.
In Safe Mode, you can determine if the problem still exists or if it has been resolved.
RECOMMENATION: Click here for help with Windows errors.
Frequently Asked Questions
- Check the property of the script.
- Reinstall the program.
- Restore win login entry in the registry.
- Restore the .vbs entry in the registry.
- 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.
- Run the Microsoft Safety Scanner.
- Run SFC.
- Change the value of .vbs
- Delete entries after Userinit.exe.
- Try to repair installation.
- Click Start > Run > cmd or hit Search and type cmd.
- Press Enter.
- On the command line, type assoc .vbs, which will result in .vbs=VBSFile.
- Type f type VBSFile at the command line.
Mark Ginter is a tech blogger with a passion for all things gadgets and gizmos. A self-proclaimed "geek", Mark has been blogging about technology for over 15 years. His blog, techquack.com, covers a wide range of topics including new product releases, industry news, and tips and tricks for getting the most out of your devices. If you're looking for someone who can keep you up-to-date with all the latest tech news and developments, then be sure to follow him over at Microsoft.