Windows 11 Bug Resurrects Vista's 2006 Boot Sound in Latest Preview Builds (windowscentral.com) 20
Microsoft's latest Windows 11 preview builds contain a bug that replaces the operating system's startup sound with Windows Vista's iconic boot chime from 2006. Microsoft acknowledged the bug in its release notes -- describing it as a "delightful blast from the past" -- and said it was working on a fix.
Obviously not a bug (Score:3)
Someone was just being cute.
But next time, to make it really fun, use a fart, or maybe the sound of someone vomiting.
Re: Obviously not a bug (Score:3, Funny)
Assuming this is a bug... (Score:2)
... and not one of the devs dicking about, why is the Vista sound still being installed at all? Makes me wonder how much other disused junk the windows installer dumps onto the drive because MS can't be bothered to audit whats still in use and what isn't.
Re: (Score:2)
Could this be why my windows folder on my work laptop is 65+ GB? Maybe that Weezer video from Windows 95 is in there too.
Re: (Score:1)
Re: (Score:2)
Even still, 55+ GB for Windows is insane.
Re: Assuming this is a bug... (Score:3)
It needs the space for 10 different versions of .NET framework.
Re:Assuming this is a bug... (Score:5, Informative)
A lot of stuff is there 'in case SOMETHING is still using it'
Microsoft has always touted backward compatibility as major selling point of Windows, although they seem more willing to make some potentially breaking changes then they were a decade ago.
A lot of current Windows software has a lot of legacy code in it too. So MS can't actually remove things because some program somewhere might *assume* that %SYSTEMDRIVE%\%WINDIR%\chime.wav is a going to be there and behave badly if it is not. To that end Microsoft has to at least keep *a* wav file at that path.
Because Windows isnt a standard, everything they did in all previous versions is the standard and that ties their hands in a lot of ways. People still ask why 64-bit Windows won't run 16 bit code when FOSS stuff can let it do it. I strongly suspect it isn't because Microsoft thought they'd have some problem doing it, but rather because they wanted to create a clear dividing line where they could manage expectations about legacy support and free themselves to finally abandon various Windows 1.x-3.11 resources, APIs, and behaviors, they no longer use themselves for anything or would rather do differently at this point.
Re: (Score:1)
Would be so easy under Linux.
Re: (Score:2)
Just a piece of trivia. I'm not a Windows expert, but NTFS also has an equivalent of symlinks, and a command to go along with it. I'll let the experts chime in on what those commands are. I don't think I've ever seen it used, though. For most home users on GUI, shortcuts are "close enough".
Re: (Score:1)
Re: (Score:2)
People still ask why 64-bit Windows won't run 16 bit code when FOSS stuff can let it do it.
There is no profit in emulation. In the short term, you do whatever hacks are necessary to run things natively, and in the long term, you just dump support.
If they really wanted to, Microsoft and Apple could make a clean break for 64-bit and still let people run legacy applications.
forgot to edit (Score:2)
obviously some one forgot to edit the copy paste of "new" windows code update
Delightful? (Score:3)
Anything that reminds me of Vista is pretty much the opposite of delightful. Offensive and repulsive would be more apt.
Re: (Score:2)
Windows 11 reminds me of Vista, and yes, it's offensive and repulsive too. Chime in if you agree.
What operating system does it use? (Score:3)
https://youtu.be/FxIUs-pQBjk?s... [youtu.be]
We're all gonna die!
Well... (Score:2)
Iconic? (Score:1)
https://www.youtube.com/watch?... [youtube.com]
Re: (Score:1)
Christ, I meant to say, the PSX was iconic, not posting an old youtube link.