Windows 10: Unknown Folder

I was searching the program filesx86 folder to delete a programBecause the program uninstaller won't work, neither the control panel or the settings appBut I came across this fileGreenetworksKitemuI never installed this program before, and never saw it as a Windows ProcessSo I tried deleting it but it keeps me from doing itBecause it is running on my computerCan anyone help me to identify this folder?And help me kill all of the processes because it always run while in startupAlthough I set the settings to disable all apps running while in start up

:)

 

Folder appears unknown

2 New folders have appeared unknown source, and will not delete.

Admin (PC) and bev (joe-pc).

They also appear under software in device manager. What gives? I have Bitdefender AV. I cannot ID which folder they are under. Listed under "This PC"

 

Trying to get more space on HDD...found UNKNOWN area?

Ok here is what it says....the <Unknown> area is on the C: root....no sub folder and it is 3.7 gig. I also have a pagefile.sys at 2.5 gig and a hiberfil.sys at 1 gig.

Any suggestions?????

 

Quick Access not searching Pictures folder

Summary, that last suggestion didn't work.

• I moved the pictures to another folder temporarily.

• Then I tried to remove the Pictures folder with option one at Add or Remove Folders from This PC in Windows 10 | Windows 10 Tutorials. Even after rebooting, the Pictures folder remained.
• So I tried using option two. Same thing: reboot >> Pictures folder still there.

• Since there were no troubleshooting steps for this scenario, just for the heck of it, I ran through the restore steps. Copied some pictures into the Pictures folder, ran a Quick Access search and initial problem remains: Searching all of QA doesn't find any files in Pictures folder, running search on just the Pictures folder does. I want to run a global search and find matching files in any/all of the Documents, Music, Videos, and Pictures folders.

That article dates from 2015 and I'm guessing is out of date. I hope it didn't create potential future problems in my registry.

Bottom line: I'm still looking for a fix.