Can you check the Win32:Ransom [Trj] signature that is being flagged for days in the memory blocks of Google Desktop.
Can I discover with “indexed file” (maybe) is the culprit?
Memory Scan? 
So, it looks like Desktop has indexed a file that avast doesn’t like?
How does it store the indexed content?
Extensionless archives into C:\Users<user>\AppData\Local\Google\Google Desktop
Hmm…I don’t think you could generate an alert via those…since they probably contain the paths to files (or whatever format it uses)
Does it not show up in a scan of the machine? (the actual indexed file).
OR
It could be an alert on the actual desktop process…some detection there, not really sure with memory scans.
I suggest to just ignore the memory scan detections…! 
No, nothing is shown, just the memory block alert since 30 days ago… It was not corrected as I’ve thought, so I’ve posted.