User documents folders in Windows 10 randomly being moved to the Recycle bin

The past month, my laptop with Windows 10 version 1803 has randomly been moving folders from my C:\Users\profile\ to the Recycle bin. I have performed a full system scan (high-sensitivity) with Avast Internet Security but nothing suspicious was found. Could there be remaining viruses hiding on my PC? Or is this something else?

If you believe any other anti-virus scanners might find a virus, please recommend me and I’ll try running another scan!

This sounds like the windows oktober update bug ?

See here from page 119 > Reply #1777
https://forum.avast.com/index.php?topic=156141.1770

However, soon after Microsoft announced the availability of its second and final major update this season, users started reported several wide-ranging issues. [b]These included events like lost files,[/b] issues with CPU usage, and reduced battery life post-update.
[b]Microsoft pulls the Windows 10 October Update[/b] https://news.thewindowsclub.com/microsoft-pulls-windows-10-october-2018-update-93457/

Users are reporting BSODs with the latest patch for Windows 10
https://www.neowin.net/news/users-are-reporting-bsods-with-the-with-latest-patch-for-windows-10

If you want a malware expert to check your computer, attach requested logs

Instructions >> https://forum.avast.com/index.php?topic=194892.0

I believe my Laptop is having this problem. I suspected $Recycle.Bin Virus and I can’t seem to get rid of it. I bought AVAST based on a recommendation from a friend.
Even AVAST and another AV brand couldn’t detect this VIRUS/TROJAN.
Please help, every time I click the folder or file goes to the Recycle Bin.

$Recycle.bin is a folder that ought not to be removed. It’s your recycling bin… The operating system will not allow for it to be removed, as it’s considered a protected system file. Are you still using the October Update?

You can check via running dxdiag (installed by default). Operating System will say something along the lines of Windows 10 Home 64-bit (10.0, Build XXXXX). Alternatively, run the scans posted in Pondus’ reply (found here >> https://forum.avast.com/index.php?topic=194892.0)