this post was submitted on 27 Jun 2025
1174 points (99.5% liked)
memes
15799 readers
3169 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
One time Windows told me I needed admin privileges to edit s file. I had admin privileges.
You needed permission from the SYSTEM or TrustedInstaller account.
Which you can give to yourself if you are admin.
Last time I did that it didn't work so I figured I will restart and it will recognize then. Windows got a 30 minute update.
When I logged back in my account was gone and still asked for a password. My old password didn't work.
Recovery option also fucked my grub. (Probably just the EFI now that I think about it.)
That last bit about GRUB is why I never put Windows on the same drive as my Arch, btw install. If they both have their own EFI partitions, Windows doesn't mess with Linux.
Just because you have admin rights doesn't mean the process you've invoked does. Unless you specifically elevate it or the process asks to elevate, it'll run unprivileged.