Please run this fixlist.
- Download fixlist.txt
- Save Fixlist.txt in the same folder where EnglishFRST64.exe is.
- Close all program windows.
- Launch the Farbar Scanner tool and click "Fix".
- Upload the output log file (FixLog.txt) to your OneDrive.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello everyone. After scorching the internet in a pursuit to find an answer I am now resorting to asking my question here. The error popped up not that long ago. A month at best. I also realized that it's only happening when the laptop is plugged in. And it seems that I am the only one with this very issue since most of other users had an error with "Run.vbs". At least I couldn't find any. Does anyone have any solution to this?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
Please run this fixlist.
A scheduled task may be executing the script when the computer is running on AC power. This could indicate a miner infection. Please run the Farbar Scanner and share your logs.
(How-To: Share OneDrive files and folders - Microsoft Support)
Note: If Microsoft Edge or Chrome mislabels the Farbar Scanner executable as PUA/malware, choose to keep it by tapping … in the bottom bar, choosing Keep, and then choosing Keep anyway in the dialog that appears.
Glad the error is resolved now. A scheduled task triggered the script file C:\Users\arsho\Documents\task.vbs. The task.vbs was already deleted from your system, so I don't know what it contained. The fixlist removed the orphaned task.
To remove files/folders created by the Farbar scanner, rename FRST64.exe to Uninstall.exe and run it. The procedure requires a reboot.
(If your issue is resolved, please consider closing this question by marking helpful posts as answers. How to mark Your question as "Answered")
This is it. Thank you. The problem no longer exists after I ran the scanner. What seemed to be the problem?