Imagine they skip 12 and call it 13 like they did with W10
With as little sense as Microsoft makes most of the time, that decision actually does make sense. A lot of programs and scripts were lazy about checking the Windows version and just checked for the presence of a ‘9’ in the version string to determine if they were running on Windows 95/98.
A bunch of shit would have broken if they had released Windows 10 as Windows 9, which is what it should have been semantically.
I’m not talking that old programs can be run. I’m talking if you dig into the settings deep enough, a Windows 2000 looking screen will pop up out of nowhere.
It’s the same thing. Stuff relies on it. And some stuff is just there from laziness. The only Windows being reskinned is 10. That’s what 11 is underneath.
You can easily schedule it yourself but I wouldn’t. I have used sfc /scannow about 10 times. It did fix an issue once - a VM repeatedly locking up doing Windows updates.
I wish they would make their configuration better. At this point even MacOS easier in that regard. And that is saying something. I constantly find myself googling how to open the old configuration pages because it’s either impossible to find where some of the configuration options went or they don’t exist on the new UIs in the first place. It’s a real down grade. They are trying to go the MacOS route but stopped half way through. Windows 11 feels like a real downgrade compared to Windows 10.
I wish they release a tool for their system to work properly. Like connecting to Bluetooth headphones or no full cpu load out of nowhere.
Those are premium windows 14 features.
Imagine they skip 12 and call it 13 like they did with W10
Microsoft always has such a weird relationship with naming conventions… just look at Xbox and all of its descendants.
Can’t wait for Windows 720 X Series XS.
You forgot “One”.
One can’t wait for Windows 720 X Series XS.
Indeed.
pwilrgc_Win* wPtr = CONSTANT_MACRO_MAP.GetHandle();
With as little sense as Microsoft makes most of the time, that decision actually does make sense. A lot of programs and scripts were lazy about checking the Windows version and just checked for the presence of a ‘9’ in the version string to determine if they were running on Windows 95/98.
A bunch of shit would have broken if they had released Windows 10 as Windows 9, which is what it should have been semantically.
Never knew that, and it makes total sense.
That’s not how it works. It started as a joke, until someone took it at face value and started spreading it as a fact. Like the flat earth
A Microsoft dev literally gave that as the reason, my man.
Can I ask you for a source then? If it’s true I’ll re-evaluate my life choices
They are more likely to skip Windows 13 due to “triskaidekaphobia” (fear of the number 13) though, like they did with internal versions for Office:
But I imagine it will be something more stupid like Windows L or Windows One.
The next version will clearly be Windows 11 Series W.
For some reason Windows L sounds like the worst possible name for a Windows version.
Hey that’s why I wrote 14. Because I think they will
Windows 9 was a real thing.
Instructions unclear, advertisements added to start menu 
That “system interrupts” is extremely important.
Time to collect and send that snap shot to mircoshit so daddy satya nadella can inspect, you know for the children.
I think either I’m having a stroke or you’re having a stroke, because I don’t understand what’s written here.
Whole thing has to get thrown out and rebuilt, its an ancient bloated mess underneath, but they waited too long and now the entire world relies on it.
Am I crazy or are they just reskinning old windows? Go deep enough and old windows things pop up in a disjarring manner.
That’s by design. One of windows core features is it’s backwards compatibility.
I’m not talking that old programs can be run. I’m talking if you dig into the settings deep enough, a Windows 2000 looking screen will pop up out of nowhere.
It’s the same thing. Stuff relies on it. And some stuff is just there from laziness. The only Windows being reskinned is 10. That’s what 11 is underneath.
It’s probably because of compatibility. Who knows, maybe that’s the loadbareing UI. It all falls apart if they change it.
It blows my mind that system file checker isn’t just a scheduled task that works during idle time. Same with DISM.
You can easily schedule it yourself but I wouldn’t. I have used sfc /scannow about 10 times. It did fix an issue once - a VM repeatedly locking up doing Windows updates.
Yeah even as a technician that’s one I run on the off chance that it actually does something.
Which, sometimes it does, just often enough that I wouldn’t call it useless.
You don’t need to check fs with NTFS.
My Bluetooth headphones work just fine. Except every time the connect the automatically set the volume to 100%.
I wish they would make their configuration better. At this point even MacOS easier in that regard. And that is saying something. I constantly find myself googling how to open the old configuration pages because it’s either impossible to find where some of the configuration options went or they don’t exist on the new UIs in the first place. It’s a real down grade. They are trying to go the MacOS route but stopped half way through. Windows 11 feels like a real downgrade compared to Windows 10.
They’ve been trying to kill Control Panel since 2012 bahahahaha
Ah sudden background updates, how I hate them.