Search Results
6/14/2025, 4:41:16 PM
>>105582566
>Could've sworn it was already off by default in NT 10, but I guess the schneegans kraut was actually right.
It's actually been off since Windows 8.0, when MS finally combed through the Windows codebase and removed all dependencies on 8.3. The problem is, the two GUI formatters (Disk Management and the Format Disk UI) leave it on for backcompat; Windows Setup will format a drive with 8.3 off (but let's be fair, not many people actually USE that to format their drives), and of course format.com lets you choose.
>Speaking about krauts
Yeah, there isn't a lot in his rant I disagree with. I do have my own thoughts on a few points, though:
>Short 8.3 filenames are a (completely superfluous) cruft from the past of MS-DOS
And Win9x. You'd be surprised how many programs from that age - which still run fine on Windows 11 - go a bit bonkers when fed long paths (as opposed to long file NAMES), even below MAX_PATH. There were also a lot of COM servers that registered themselves via 8.3 name back then, too. I have a number of utilities from the 90s that I still use daily. As usual, it is a backcompat thing. But, to be completely honest, for the hoi polloi, it can go.
>No qUACkery any more
There's more to UAC than just elevation. Another anon righteously said a thread or two back that people forget about the FS and registry virtualisation it offers. It's also the bedrock the AppX security model is built on: only since Windows 11 can AppX function with UAC disabled (for example, when running in the context of the RID 500 Administrator). Thankfully, this guy "disables" UAC "the right way" by not actually disabling it at all (which a lot of memescripts do, causing much mayhem among Dunning-Kruger sufferers), and just doing the RegEdit equivalent of whacking all the sliders up to the max.
(cont'd)
>Could've sworn it was already off by default in NT 10, but I guess the schneegans kraut was actually right.
It's actually been off since Windows 8.0, when MS finally combed through the Windows codebase and removed all dependencies on 8.3. The problem is, the two GUI formatters (Disk Management and the Format Disk UI) leave it on for backcompat; Windows Setup will format a drive with 8.3 off (but let's be fair, not many people actually USE that to format their drives), and of course format.com lets you choose.
>Speaking about krauts
Yeah, there isn't a lot in his rant I disagree with. I do have my own thoughts on a few points, though:
>Short 8.3 filenames are a (completely superfluous) cruft from the past of MS-DOS
And Win9x. You'd be surprised how many programs from that age - which still run fine on Windows 11 - go a bit bonkers when fed long paths (as opposed to long file NAMES), even below MAX_PATH. There were also a lot of COM servers that registered themselves via 8.3 name back then, too. I have a number of utilities from the 90s that I still use daily. As usual, it is a backcompat thing. But, to be completely honest, for the hoi polloi, it can go.
>No qUACkery any more
There's more to UAC than just elevation. Another anon righteously said a thread or two back that people forget about the FS and registry virtualisation it offers. It's also the bedrock the AppX security model is built on: only since Windows 11 can AppX function with UAC disabled (for example, when running in the context of the RID 500 Administrator). Thankfully, this guy "disables" UAC "the right way" by not actually disabling it at all (which a lot of memescripts do, causing much mayhem among Dunning-Kruger sufferers), and just doing the RegEdit equivalent of whacking all the sliders up to the max.
(cont'd)
Page 1