Microsoft hate thread - I just want to rant about Microsoft

[ZMOT]

You're expected to put global program files that you are going to be modifying in ProgramData at the root, user specific stuff goes into the user's AppData folder. Neither of which require elevation. Not sure why ProgramData is hidden though.

program data is shared, thus requires elevation. appdata is in your user folder, might as well put that shit under my documents, it's equally retarded.

 

[the rat]

program data is shared, thus requires elevation. appdata is in your user folder, might as well put that shit under my documents, it's equally retarded.

Really? Seems like standard users should have permission to write to that folder (see bottom entry).

 

[Slav Power]

Really? Seems like standard users should have permission to write to that folder (see bottom entry).

View attachment 7509492

Bottom entry doesn't include files, so it's still read only permissions for regular users.

 

[the rat]

Bottom entry doesn't include files, so it's still read only permissions for regular users.

It means you can write to a folder/subfolder? I actually bothered to create a standard account to test this and yes you can in fact write files to ProgramData without UAC elevation so idk wtf either of you are talking about. (see the lack of Administrator under "Local Account"). When I try to create a folder in the Windows directory it asks for my Admin user's password so UAC is working properly.

 

[Linksys WRT]

>Let me ping my new Windows Server VM to make sure I can hit it

ping server

>No response
>Silly me, almost forgot I was dealing with Microsoft

nmap -Pn server

I do this every time I install Windows VMs.

 

[ZMOT]

Really? Seems like standard users should have permission to write to that folder (see bottom entry).

https://stackoverflow.com/questions/26798832/cannot-create-files-in-c-programdata-even-after-granting-users-group-full-perm

might work now (if you're ok with users having access to shared configuration files and praying the app isn't developed by retards), but was exactly the windows permission shit I was talking about.

 

[Spud]

Just had to upgrade the work laptop to Win 11. What sick twisted fuck thought it'd be a good idea to not let users move the taskbar around the screen, I can't even flatten it to get more screen space back.

 

[Slav Power]

Just had to upgrade the work laptop to Win 11. What sick twisted fuck thought it'd be a good idea to not let users move the taskbar around the screen, I can't even flatten it to get more screen space back.

The 'jeets. They were the ones to throw out the taskbar as it evolved ever since it was first introduced in Windows 95 and replace it with some piece of shit written in React that doesn't have the feature parity with the fucking Windows 95 taskbar, because the 'jeets know better what you need and they need to change shit just to change it to make the stockholders happy. 99% of people use the default Win10 taskbar settings? Okay, no need to give the user the choice he had for 26 fucking years then.

Oh yeah, the most infuriating thing?

https://devblogs.microsoft.com/oldnewthing/20230324-00/?p=107966

Raymond Chen, the guy that worked on Windows 95, and still works at Microsoft, when encountering people having issues due to them using ExplorerPatcher just to unfuck the 'jeetified taskbar, his first thought wasn't "oh people use it because our taskbar is bad and we should improve it so that there's no reason to use it". No, his reaction was "oh people shouldn't be using this tool because it does things that it shouldn't". Not even the guy who worked on the fucking taskbar as we know it could tell that the new taskbar is so bad it forces people to use tools that break Windows.

 

[the rat]

https://stackoverflow.com/questions/26798832/cannot-create-files-in-c-programdata-even-after-granting-users-group-full-perm

might work now (if you're ok with users having access to shared configuration files and praying the app isn't developed by retards), but was exactly the windows permission shit I was talking about.

(link)

What a headache. So I guess the expected behavior is to make a sub-folder with lax permissions at the installer level to avoid having to run UAC every fucking time you start the application? Not too bad considering you need UAC to even write to Program Files to begin with.