Since the implementation of W10 V2004, Windows Defender has now been defaulted to identify
PUPS as a threat. As a result, many are now made aware of their presence. And they are "remediated",
on the spot, to prevent them from causing any mischief.
The problem occurs on the subsequent scans with Windows Defender. It identifies the same PUP again, and again.
It has been determined that this is caused by the presence of the PUP in Protection History.
It appears that the default remediation that Windows Defender applies to PUPs is to Block them, then leave
them in Protection History .
Windows Defender is defaulted to scan its own "Scans/History". Resulting in the discovery of the PUP over and
over again. Even though, other scanners see no evidence of the PUP on the PC.
Until Microsoft sees fit to Quarantine the PUPs, you can prevent the repeating error indication, by deleting them.
They are described in Windows Defender Protection History. You can delete them by accessing their files, that
are located in C:\Program Data\Microsoft\Windows Defender\Scans\History\Service.
Note: Program Data is a hidden file. In order to access it, the "Hidden Files" option in "File Explorer" must be
chrcked. Find the "Hidden Files" check box under the "View Tab".
In the "Service" folder, delete any file that references the PUPs (PUA). They should be in "Detection History".
If you can not see your PUP (PUA), just delete "Detection History".
Restart and try another scan. Notifications for the current PUPs should stop.
However, this program miscue will probably reoccur, when the next PUP is encountered.
Glen
Thank you, THANK YOU, for real
I've deleted a pup exe file from downloads ( I haven't opened it at all) and it kept saying it was still there, even in the details. I looked for it in the task manager and even in the extra apps and uninstalls but it didn't exist, strangely it said that it was currently running and active but since I did what was above, it resolved the issue with a full system scan.
I think its a bug for removing certain pups since it said it was a win32 install core pua. I haven't opened it like I said again. Perhaps its a problem with the file running from the security history, because once I've deleted the folders inside the detection history, it was resolved.
Like I've said, thank you
It was a hassle to deal with using malware bytes as I was all like "Strange, it doesn't exist, I've even made sure in the settings to check everywhere" but Windows security kept duplicating it and showing me that file extension to downloads file.
I hope that bug can get fixed in later updates, even an "override" function would help so that it can sweep through the system for that file.