Windows Script Host Errors on Windows 10 Start-up

bedouinbro

Well-Known Member
Joined
Feb 6, 2024
Messages
44
im getting Windows Script Host Errors on Windows 10 Start-up. followed this guide and ran the Autoruns


but the file isn't appearing on the list, also tried enabling and disabling Windows Script Host in Win10 from these guides no fix !


so there's one shell file with the same name "config" deleted it and restarted to get the same error,
did the whole

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

but it didn't solve it
what's causing this error ?
should I try changing the file type of config to .vbe and see what happens ? lol ! found malware execution like this



I also ran the Malwarebytes but it didn't showed any related results
how do I fix the error ?
[ATTACH type="full" align="right" alt="An image from 'Windows Script Host Errors on Windows 10 Start-up'. 1. Windows error: missing Config.vbe script file.
2. Autoruns tool shows no Config.vbe startup entry.
3. File Explorer shows Config PowerShell script in Local folder.
4. Task Manager Startup tab lists enabled/disabled startup apps."]43796[/ATTACH]

[ATTACH type="full" align="right" alt="An image from 'Windows Script Host Errors on Windows 10 Start-up'. 1. Windows error: missing Config.vbe script file.
2. Autoruns tool shows no Config.vbe startup entry.
3. File Explorer shows Config PowerShell script in Local folder.
4. Task Manager Startup tab lists enabled/disabled startup apps."]43799[/ATTACH]
[ATTACH type="full" align="right" alt="An image from 'Windows Script Host Errors on Windows 10 Start-up'. 1. Windows error: missing Config.vbe script file.
2. Autoruns tool shows no Config.vbe startup entry.
3. File Explorer shows Config PowerShell script in Local folder.
4. Task Manager Startup tab lists enabled/disabled startup apps."]43797[/ATTACH]
[ATTACH type="full" align="right" alt="An image from 'Windows Script Host Errors on Windows 10 Start-up'. 1. Windows error: missing Config.vbe script file.
2. Autoruns tool shows no Config.vbe startup entry.
3. File Explorer shows Config PowerShell script in Local folder.
4. Task Manager Startup tab lists enabled/disabled startup apps."]43798[/ATTACH]
 


Attachments

  • Capture.webp
    Capture.webp
    24 KB · Views: 0
  • Screenshot (16).webp
    Screenshot (16).webp
    154.6 KB · Views: 0
  • Capturedgdg.webp
    Capturedgdg.webp
    49.7 KB · Views: 0
  • Capturerfhrh.webp
    Capturerfhrh.webp
    44.5 KB · Views: 0
Last edited by a moderator:
Solution
I've encountered similar problems before. If you encounter Windows Script Host errors while starting Windows 10, it is most likely due to corrupted system files or conflicting scripts. Try running a thorough antivirus scan to rule out malware. Additionally, you can use the System File Checker tool to repair any corrupted system files. If the problem persists, consider checking your startup programs for suspicious scripts. For more detailed help, professional term paper writing services such as MasterPapers can offer customized solutions. You can also always buy custom coursework online at a good price. I've tested this several times now and have always been happy with the results.
Pretty much anything can call wscript. I would grab a copy of procmon, set a filter to 'command line' contains config.vbe.
Then under options 'enable boot logging'.
Reboot the computer and open procmon again it should capture the calling process.
 


I've encountered similar problems before. If you encounter Windows Script Host errors while starting Windows 10, it is most likely due to corrupted system files or conflicting scripts. Try running a thorough antivirus scan to rule out malware. Additionally, you can use the System File Checker tool to repair any corrupted system files. If the problem persists, consider checking your startup programs for suspicious scripts. For more detailed help, professional term paper writing services such as MasterPapers can offer customized solutions. You can also always buy custom coursework online at a good price. I've tested this several times now and have always been happy with the results.
 


Last edited:
Solution
Pretty much anything can call wscript. I would grab a copy of procmon, set a filter to 'command line' contains config.vbe.
Then under options 'enable boot logging'.
Reboot the computer and open procmon again it should capture the calling process.

solved it here
 


Back
Top