Windows error after PUP removal

[userZ]

I am not sure if this is the correct section for this. I ran a scan and it found a PUP.Optional.Slimware at the following location C:\Windows\Microsoft.NET\ASSEMBLY\CAG_64\SYSTEM.DATA\V4.0_4.0.0.0_B77A5C561934E089\SYSTEM.DATA.DLL 

I quarantined it and then restarted the computer. At restart there was a blue error screen saying there was a code error and another restart is being attempted. It passed too quickly to write down any details. The laptop started again without any problems this time. I restored the file and ran an antivirus scan which did not detect any problem with this file. 

Is this actually a PUP or is MBAM making a false positive detection?

Thanks for any help.

[userZ]

I ran another threat scan and this time the file was not flagged. So I am confused now

[Porthos]

29 minutes ago, userZ said:

I ran another threat scan and this time the file was not flagged. So I am confused now

Could you post the log showing the detection please.

[Porthos]

@userZ

You can find Scan and Protection logs within the Malwarebytes 4 program in the following location

 

 

RTP stands for Real-Time Protection and is where automatic protection operations would normally be logged

 

 

If you click on the View option you should get something similar to the following with other options available.

 

 

 

 

Thank you

[userZ]

5 hours ago, Porthos said:

@userZ

You can find Scan and Protection logs within the Malwarebytes 4 program in the following location

 

 

RTP stands for Real-Time Protection and is where automatic protection operations would normally be logged

 

 

If you click on the View option you should get something similar to the following with other options available.

 

 

 

 

Thank you

Thanks for the reply. I have attached the log file

PUPlog.txt

[shadowwar]

This was probably a fluke. This def is really old and maybe having rootkit on might have had something to do with it. Rootkit should only be used when a infection is present. It also lowers some whitelisting settings as this file is normally set to not detect. The def triggers on avast driver updater as pup.