In defense of Andrew, until windows 10 never had I ever installed a program that made it’s own files untouchable unless you did some real fuckery with permissions.

As soon as they introduced that little warning screen in program files it was clear shit was going downhill for power users.

[–] DudeDudenson@lemmings.world 10 points 3 months ago (3 children)

I discovered basic versions of windows are even more restrictive when I was unable to install my favorite lightweight pdf reader in a friend's laptop because Windows home just said that for my safety I wasn't allowed. With no option to bypass this limitation being hinted at.

Ended up installing it anyways but had to run the installer from an admin terminal (luckily it was windows 7 so it was a local account with admin rights instead of a bullshit Microsoft one)

[–] urshanabi@lemmygrad.ml 2 points 3 months ago

basic windows... does that entail windows N by any chance?

[–] laughterlaughter@lemmy.world 1 points 3 months ago

This has to be some sort of policy being enabled. I have seen that window, but there are ways to bypass it - though in hindsight, they are not as evident. For example, right-click then choose "Open."

[–] gwen@lemmy.dbzer0.com 0 points 3 months ago

drop the pdf reader. libreoffice makes the pdfs look horrific and apache doesnt work

[–] laughterlaughter@lemmy.world 4 points 3 months ago (1 children)

that made it’s own files untouchable

that made its* own files untouchable

[–] yuri@pawb.social 2 points 3 months ago

I make that same mistake enough that at this point I figure I’m just contributing to the paradigm shift of modern english grammar.

Making the oxford comma mandatory is my next big target.