all 36 comments

sorted by: hot top controversial new old
[+] 45 points 3 months ago (1 child)
  • [–] 64 points 3 months ago (1 child)

    "4GB RAM is enough for anyone!"
    - hardware manufacturers, 2026

  • source
  • hideshow 1 child comment
  • [+] 31 points 3 months ago (3 children)
  • [–] 31 points 3 months ago (2 children)

    why the fuck system32 is 64bits and syswow64 is 32bits, i hate microsoft

  • source
  • hideshow 2 child comments
  • [–] 7 points 3 months ago

    Because 16 bit reasons. Also a lot of Windows API is called Win32 regardless of the used bits, as it was the API created for Windows 95 and NT 4.0 originally, with some things added onto it later, and even some kind of deprecated parts

  • source
  • parent
  • [–] 67 points 3 months ago (7 children)

    This is also a reminder that Windows and the NT kernel have been so neglected and underdeveloped that it's a technical house of cards.

    Blame Microsoft for firing their NT kernel team and QA teams in the Windows 9 era to instead automate testing and development.

    In fact, if Europe could just generalise and open source the NT kernel, Windows could actually be usable again.

  • source
  • hideshow 7 child comments
  • [–] 16 points 3 months ago (1 child)

    if Europe could just generalise and open source the NT kernel, Windows could actually be usable again.

    I guess it would be useful just for running software that only works on Windows but I can't think of any other actual benefits to NT when compared to any Unix/Unix-like kernel

  • source
  • parent
  • hideshow 1 child comment
  • [–] 12 points 3 months ago (9 children)

    Will Windows even let you do that?

  • source
  • hideshow 9 child comments
  • [–] 22 points 3 months ago (8 children)

    I don't think so anymore. You could probably do some damage if you clicked through the hundred warnings but I don't think you can remove the whole directory anymore.

    Windows has a secret "System" user which owns most if not all if that, and permissions are now set up such that not even Administrator can touch it. From what I understand those are now hardcoded into the system.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 19 points 3 months ago (1 child)

    God I hate that System user. Somehow, back when I used Windows, it granted System the ownership of a bunch of folders in my D: that even as an admin I couldn't delete-- I think because of Microsoft store?

    It wasn't until I started playing with Linux (Manjaro at the time) that I was able to clean it up. Something like 600gb of game files, lol.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 8 points 3 months ago

    fuck, i wish i knew all this in highschool

    There are some super homophobic dudes i would've put gay porn on their desktop and in their documents then made it only system owned with deny delete.

  • source
  • parent
  • [–] 1 point 3 months ago

    They're not hardcoded, you can take ownership of the files with commands (takeown and icacls). As some other user already mentioned, there are ways to start a command prompt as the SYSTEM user. Windows will still not let you delete them however, because most of them are being used by processes.

  • source
  • parent
  • [–] -1 points 3 months ago (1 child)

    The system user is part of Dos like root is part of Unix. I think what you're referring to is how the whole OS runs in a virtualization layer because Microsoft doesn't trust its own kernel. This also disallows a lot of folders from being deleted or modified. I'm not sure if system32 is included.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 7 points 3 months ago (3 children)

    Why did Windows name it with 32? Always confused by that

  • source
  • hideshow 3 child comments
  • [–] 18 points 3 months ago (2 children)

    That folder (or rather whatever serves its purpose) has been around since the beginning, so all the 16-bit applications at the time would look for OS libraries in C:\WINDOWS\SYSTEM\.

    Then 32-bit comes along, and you can't exactly drop 2 files with the same name in the same folder, so the 32-bit ones got put in their own named folder.

    Then 64-bit comes along, and it turns out way too many applications hardcoded the System32 path to change it, so they kept the name the same and inserted a filesystem redirection for legacy 32-bit apps so when they try to read from System32 the kernel redirects that to SysWoW64.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 3 months ago (1 child)

    My work laptop doesn't allow me to do this. Shall I open a ticket to IT support?

  • source
  • hideshow 1 child comment
  • [–] 11 points 3 months ago