{"id":1666,"date":"2016-02-20T20:28:21","date_gmt":"2016-02-20T14:58:21","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=1666"},"modified":"2023-02-08T16:03:20","modified_gmt":"2023-02-08T10:33:20","slug":"cannot-find-script-run-vbs-logon","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/cannot-find-script-run-vbs-logon\/","title":{"rendered":"Fix “Can not find script file C:\\WINDOWS\\run.vbs” at Logon"},"content":{"rendered":"

When you log on to your computer, the error “Can not find script file C:\\WINDOWS\\run.vbs” with Windows Script Host in the title is shown on 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.<\/p>\n

Important #1:<\/b> This post explains how to fix the Userinit value and thereby helps you get access to your user profile. At the same time, the malware that caused the problem in the first place might still be active and lurking in the system. And in this case, the problem seems to have been caused by a complex malware that adds core components to the system making the removal process difficult. So, it’s highly advisable<\/b><\/u> to get your system professionally checked for malware and eliminate them entirely.<\/p>\n

<\/p>\n

Fix the Run.vbs error by correcting the Userinit value<\/h2>\n

Note:<\/b> If Task Manager doesn’t open due to DisableTaskMgr Policy enabled by the Malware, carry out the following procedure via Recovery Environment. Check out the article How to Edit the Registry Offline Using Windows Recovery Environment?<\/a> for more information.<\/i><\/p>\n

    \n
  1. After typing the login credentials, the system may stall at Preparing to the login<\/em> screen. Press Ctrl + Alt + Del, and click Task Manager.<\/li>\n
  2. When the above error message dialog is visible, dismiss the dialog and switch to the Task Manager window.<\/li>\n
  3. The file referenced in the Userinit<\/code> 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<\/b> and press ENTER.<\/li>\n
  4. Start Registry Editor (Regedit.exe) and go to:\n
    HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\Winlogon<\/pre>\n<\/li>\n
  5. Double-click Userinit<\/b> value and change the value data from:\n
    wscript C:\\WINDOWS\\run.vbs,<\/pre>\n
    to the following: [Caution:<\/b> Take special care when entering. You need to remove the wscript<\/b><\/span> part.]<\/p>\n
    C:\\Windows\\system32\\userinit.exe,<\/pre>\n
    *Important #2*:<\/b> If Windows is installed in a different<\/span> drive than C:\\, type the actual drive letter and path<\/u>. Also, include the trailing comma (,<\/b>) as shown above. Take extreme<\/b> care when typing the Userinit value, as typing an incorrect filename or path will prevent you<\/span> from logging on to any user account. I’m not responsible if you type a wrong path and lock yourself out of your user account.
    \n
    \n<\/i><\/li>\n
  6. Exit the Registry Editor.<\/li>\n
  7. Log off and login back in so that the Userinit.exe loads correctly and does the initialization or preliminary jobs like running logon scripts etc.<\/li>\n<\/ol>\n