Windows 10: MSERT Microsoft Safety Scanner Mistake

So I recently installed Microsoft Safety Scanner, MSERT, for a full scan. During the scan, it said “files infected: 4” but after it said no malicious software was detected. Is this because it thinks a program is malware, but after checking again for malicious scripts, it turns out to be safe? I’m a little paranoid. I’ve ran a full scan with Windows Security and Malwarebytes and neither of them found threats. I think it was a false alarm but im also concerned it could be sneaky malware that is designed to not be detected by regular antivirus. I’m just a little unsure

:)

 

Problem With Microsoft Safety Scanner (MSERT)

Hello all! I have an HP Omen desktop with Win10 Home and my OS Build is 19045.2673. There appears to be a problem with the latest builds of Microsoft Safety Scanner (MSERT) 64 and 32 bit. I have downloaded this several times today and each time I try to open it I get this error below. I have ran SFC, DISM with no corrupt files found. Thinking I may have malware I ran Malwarbytes and Norton 360 scans and all are clean. I ran update troubleshooter and it was fine. My Event viewer had no errors.





I went to

How to troubleshoot an error when you run the Microsoft Safety Scanner - Microsoft Support as suggested but was not much help except that I did open the Run Box as suggested and entered %systemroot%\debug which took me to windows >>Debug. I selected MSERT from the debug log and opened it to notepad and scrolled down to the last entry. There I found the below entry which was causing MSERT not to open.



----------------------------------------------------------------------------------------------------------------------

Upon further investigation on the web about this problem there was a discussion in Reddit

Reddit - Dive into anything concerning the same thing. It was good to know that I was not the only one experiencing this and my machine was fine. I would like to point out as well that I still had an MSERT in my download folder I had installed on 3/1/23 and this opened fine and ran perfectly with nothing found. It seems clear the MS is putting out bad builds of MSERT for some computers and it needs to be fixed as it is useless the way it is now for me and other users.

Respectfully

 

Problem With Microsoft Safety Scanner (MSERT)

Yes, I saw some other threads on same topic:

Safety Scanner download 64bit not working

Last reply 4 hours 56 minutes ago by Ramesh Srinivasan | Created 5 hours 15 minutes ago by cweisner

Error when trying to run MSERT

Last reply 6 hours 32 minutes ago by par_0511 | Created March 12, 2023 by Jan Philips

MSERT cant even start since today (trying to find unknown APT)

Last reply 2 hours 27 minutes ago by Nathan Roberts (SN) | Created March 8, 2023 by hypnologic

Also mentioned here:

Defender Update KB2267602 (v1.383.1400.0 and above) drops install error 0x80070643 - reports low memory

 

Problem With Microsoft Safety Scanner (MSERT)

Tested the 64-bit build listed below. It works for me

Microsoft Safety Scanner v1.385, (build 1.385.312.0)

Started On Fri Mar 17 14:21:18 2023



Engine: 1.1.20100.6

Signatures: 1.385.312.0

MpGear: 1.1.16330.1