patchwork_gnome Posted October 6, 2023 ID:1593561 Share Posted October 6, 2023 Malwarebytes version: 4.6.2.281 Update Package: 1.0.75995 Component package: 1.0.2131 Visual Studio 2022 17.7.4 I am using Visual studio Pro. Everyday, every time I rebuild\build\dotnet ef. Malwarebytes quarantine my needed files that Visual Studio needs. Example: Exploit.PayloadFileBlock - .\Microsoft Visual Studio\Installer\vswhere.exe Exploit.PayloadFileBlock - .\VisualStudio\IDE\Common7\Tools\VsDevCmd.bat Exploit.PayloadFileBlock - .\VisualStudio\IDE\MSBuild\Microsoft\VisualStudio\NodeJs\node.exe Exploit.PayloadFileBlock - .\VisualStudio\IDE\MSBuild\Microsoft\VisualStudio\NodeJs\node_modules\npm\bin\npm-cli-js These files are vital for my projects, yet each time I do a repetitive action that needs to happen, Malwarebytes deletes it. I am then forced to reboot so that I can restore the file. "The restore operation cannot be performed until the pending reboot has been completed" YES! I have added the files and the entire directory to the allowed list, and I have turned on "Beta Updates" I am wondering if there a way to fix this issue, I will have to uninstall the product so I can keep working until there is a fix. Link to post Share on other sites More sharing options...
Solution Porthos Posted October 6, 2023 Solution ID:1593563 Share Posted October 6, 2023 @patchwork_gnome Download the following MB installer and install over what you have and restart the computer. https://www.malwarebytes.com/mwb-download/thankyou This should correct your issue. 1 Link to post Share on other sites More sharing options...
patchwork_gnome Posted October 6, 2023 Author ID:1593574 Share Posted October 6, 2023 Well, I'll be dog gone! Looks like that worked. I am not sure how manually installing an updated version fixed it, but running "Check for updates" to make sure I was up to date, didn't?!?!?! Either way, thank you ! Link to post Share on other sites More sharing options...
Porthos Posted October 6, 2023 ID:1593575 Share Posted October 6, 2023 1 minute ago, patchwork_gnome said: I am not sure how manually installing an updated version fixed it, but running "Check for updates" to make sure I was up to date, didn't?!?!?! Some users with 4.6.2 were/are stuck on a damaged install. You were one of them. Link to post Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now