What the fuck is up with this file path?

>>58581840
Defenestrate.

>>58581840
what's the problem? "C:\Program" is a valid file path

>>58581840
What version?
If you uninstall and reinstall does it still do it?

>>58582029
The thing is that this is a desktop. Why would it have laptop drivers?

>>58581982
Until you're told the path is invalid

>>58582091
Do you have a synaptics folder in program files?

>>58582109
No.
Odd. My "program files" folder WAS listed, now it's not. I can still manually type the path though

Virus bruh. Delete everything.

>>58581840
It's a classic windows exploit. You put a virus named Program, and then when someone tries to run C:\Program Files\thing, first it checks if C:\Program exists, then it tries to run C:\Program Files/thing. Normally C:\Program doesn't exist so this exploit stays hidden, but crackers and skiddies exploit this by putting a C:\Program on your machine
>hurr durr let's use backslashes instead of forward slashes
>hurr durr let's use spaces in one of the important directory names

Hi Brandon :^)

>>58582264
>hurr durr let's use spaces in one of the important directory names
Holy fuck this has always triggered me

>>58584897
Then how does "let's use the escape character to separate folder names" not trigger you?

>>58582264
>puts spaces in paths without escapes, allowing ambiguity

lol windows

File: Taskmgr_2017-01-21_15-39-22.png (989B, 174x33px) Image search: [Google]

989B, 174x33px

>>58581840
>that BIOS time
christ my dude