• Windows 10 Version 1507 (RTM) to stop getting updates March 26th
    44 replies, posted
[quote] The first release of Windows 10, known as 1507, is the version that Microsoft will no longer update after March 26, 2017. The other two versions of the product in market -- the November update (1511) from November 2015 and the Anniversary Update (1607) -- will continue to get regular security and feature fixes and updates. The 1507 release won't just stop working, but it won't get updates of any kind after March 26. This is all part of Microsoft's grand Windows as a Service plan. No updates is one way of getting users to move to a more recent release. Microsoft designated Windows 10 version 1607 as the Current Branch for Business at the end of November 2016. Businesses were free to move to that version manually at that time. But as of Jan. 19, Microsoft made the updated media for 1607 available for those using Windows Update for Business, Windows Server Update Services (WSUS), and MSDN. Microsoft also will release Windows 10 version 1607 to the Volume Licensing Service Center (VLSC) on Jan. 26, 2017. Business customers already running 1607 plus the December Cumulative Update don't need to do anything, as they're already running what's effectively the Current Branch for Business. [/quote] [img]https://upload.teknik.io/LPtxv.png[/img] Source: [url]http://www.zdnet.com/article/reminder-microsoft-to-no-longer-update-original-windows-10-release-after-march-26/[/url] Further Reading: [url]https://blogs.technet.microsoft.com/windowsitpro/2017/01/19/windows-10-v1607-media-now-available/[/url] In short; Since the current business branch has been changed, Microsoft has no need to maintain the older version, as they only update the two latest 'business branch' versions. This means, the Anniversary update (1607) from 2016, and the Threshold 2 (1511) update from 2015 be the only versions to still receive security updates and bugfixes ZDNet goes further into explaining the Unified Update Platform, which is good for users with limited bandwidth
well, can't really argue with that. i haven't really found anything terrible with anniversary since i updated to it.
Just got updated to the anniversary update (didn't do it when it came out for some reason I can't quite remember), and windows changed my default audio output for some reason. Wasn't really an issue for me, but if that had happened to some whatever average Joe, that's quite a headache.
[QUOTE=GoDong-DK;51708681]Just got updated to the anniversary update (didn't do it when it came out for some reason I can't quite remember), and windows changed my default audio output for some reason. Wasn't really an issue for me, but if that had happened to some whatever average Joe, that's quite a headache.[/QUOTE] It's now easier than ever to change audio output [t]https://upload.teknik.io/BnAkZ.gif[/t] I wouldn't see this issue as a headache though, as in this day of age, it's also very easy to find the answers to problems online. A google search for 'Windows 10 audio not coming out of headphones' gives appropriate results for solving this problem, as with a lot of other simple problems
I'm still waiting for the day where I can route specific apps to other sound devices without software
[QUOTE=GoDong-DK;51708681]Just got updated to the anniversary update (didn't do it when it came out for some reason I can't quite remember)[/QUOTE] I haven't done it to this date either and I also cannot remember why I've been avoiding it. I get a couple of pop-ups every day prompting me to update. Are there any reasons not to that I have forgotten or should I finally get it over with?
[QUOTE=Scratch.;51708708]It's now easier than ever to change audio output [t]https://upload.teknik.io/BnAkZ.gif[/t] I wouldn't see this issue as a headache though, as in this day of age, it's also very easy to find the answers to problems online. A google search for 'Windows 10 audio not coming out of headphones' gives appropriate results for solving this problem, as with a lot of other simple problems[/QUOTE] Yeah sure, I had no trouble, but my mom or dad would've. Googling a problem is not something many people are very good at, believe it or not. If you have no idea what an audio output in windows and all you know is suddenly you get no sound, that's a headache for some people. Thing is, it shouldn't happen. Windows 10 has duly preserved my lockscreen picture, background pictures etc. from my old Windows 8 installation, it shouldn't start switching between my audio devices for no apparent reason.
If only I could get the anniversary update, it just fails to install for me.
[QUOTE=GoDong-DK;51708837]Yeah sure, I had no trouble, but my mom or dad would've. Googling a problem is not something many people are very good at, believe it or not. If you have no idea what an audio output in windows and all you know is suddenly you get no sound, that's a headache for some people. Thing is, it shouldn't happen. Windows 10 has duly preserved my lockscreen picture, background pictures etc. from my old Windows 8 installation, it shouldn't start switching between my audio devices for no apparent reason.[/QUOTE] Utter incompetence is a bad reason for something as minor and easily fixed as this. Bugs tend to happen in complex software solutions. People should learn to deal with that rather than ranting about this. If your parents are so bad they can't even google this, you or someone else should consider teaching them. This is literally basics of computer use.
I'm still on 1511
[QUOTE=rndgenerator;51708849]If your parents are so bad they can't even google this, you or someone else should consider teaching them. This is literally basics of computer use.[/QUOTE] There are no losers on the information superhighway
[QUOTE=Painseeker;51708724]I haven't done it to this date either and I also cannot remember why I've been avoiding it. I get a couple of pop-ups every day prompting me to update. Are there any reasons not to that I have forgotten or should I finally get it over with?[/QUOTE] There's really no reason not to tbh. I've been on it since the hour it was available in the UK, and I can't say it's caused any problems. I didn't even have the fuck ups from Threshold 2 occur where my settings were changed seemingly randomly.
I'm still on like 1510 or something and I've disabled updating. I think I was worried about the newer updates fucking with my regedit configs.
Snip
[QUOTE=redBadger;51709007]You can it's called a patch bay[/QUOTE] Not what I mean't. I have Spotify running and the only way to get it to my headphones is to change the default device which isn't what I want. CheVolume does this but costs money. Most programs don't have the option to change the output device which is why I use CheVolume
[QUOTE=GoDong-DK;51708681]Just got updated to the anniversary update (didn't do it when it came out for some reason I can't quite remember), and windows changed my default audio output for some reason. Wasn't really an issue for me, but if that had happened to some whatever average Joe, that's quite a headache.[/QUOTE] It changed my output, made the app that I use to change outputs not work (although granted it now works from the volume control so I don't need it anymore), added Edge, Cortana, and the Store back to the taskbar, reactivated Cortana, reinstalled Skype Preview, broke my taskbar layout (outer edges of dual screens, now the left one doesn't work), and forgot my wifi settings so it was impossible to log in with a PIN and I had to look up my long random password on my phone. I mean I appreciate the update and all but come on, you can't say it was impossible for Microsoft to do a little routine saying "okay, save all of this shit temporarily in a file so we can load it back in after the update".
[QUOTE=TheJoker;51709015]Not what I mean't. I have Spotify running and the only way to get it to my headphones is to change the default device which isn't what I want. CheVolume does this but costs money. Most programs don't have the option to change the output device which is why I use CheVolume[/QUOTE] Have you tried [url]http://vb-audio.pagesperso-orange.fr/Voicemeeter/banana.htm[/url] ? It's free and works great though it is a bit more complex than Che
I'm still looking for a way to get 1511. The ISO files Microsoft puts out are for 1607. [editline]22nd January 2017[/editline] Nevertheless I'm happy with 8.1 and Classic Shell, with most Metro gestures (Charms, etc) disabled
[QUOTE=rndgenerator;51708849]Utter incompetence is a bad reason for something as minor and easily fixed as this. Bugs tend to happen in complex software solutions. People should learn to deal with that rather than ranting about this. If your parents are so bad they can't even google this, you or someone else should consider teaching them. This is literally basics of computer use.[/QUOTE] Or maybe... Microsoft shouldn't change the default audio device for no reason? I'm not saying it's a disaster and trust me I have no larger point with this, but if Microsoft wants to deliver a good product, they shouldn't release an update that changes users' configurations for no reason. That's all. You'd be surprised how little some people know, and some may simply assume their laptop's speakers broke or whatever. If you didn't know how Windows handles sound devices, that's a reasonable assumption to make. And some people put up with it, just like they never quite go through with uninstalling McAfee even though it bothers them every day telling them to buy their product. I'll defend changes in Windows if I see a purpose for them - I was a proponent of the Windows 8.1 start screen after all - but there's no reason an update should switch away from your default audio output. What's the better scenario: Microsoft doesn't change the default audio output for no reason, or I have to take my mom through the process of changing it back over the phone for no good reason? [editline]22nd January 2017[/editline] [QUOTE=Snowmew;51709099]It changed my output, made the app that I use to change outputs not work (although granted it now works from the volume control so I don't need it anymore), added Edge, Cortana, and the Store back to the taskbar, reactivated Cortana, reinstalled Skype Preview, broke my taskbar layout (outer edges of dual screens, now the left one doesn't work), and forgot my wifi settings so it was impossible to log in with a PIN and I had to look up my long random password on my phone. I mean I appreciate the update and all but come on, you can't say it was impossible for Microsoft to do a little routine saying "okay, save all of this shit temporarily in a file so we can load it back in after the update".[/QUOTE] Yeah it also forgot my Wi-Fi password, and thanks for the heads up about the apps. I can [I]kinda[/I] understand Microsoft putting "Get Office" on my machine the first time I install Windows, but they should probably get the hint when I've had it uninstalled since then and because... well I already have Office 365, Microsoft, thank you very much. I also have Skype. But thanks.
[QUOTE=Snowmew;51709099]It changed my output, made the app that I use to change outputs not work (although granted it now works from the volume control so I don't need it anymore), added Edge, Cortana, and the Store back to the taskbar, reactivated Cortana, reinstalled Skype Preview, broke my taskbar layout (outer edges of dual screens, now the left one doesn't work), and forgot my wifi settings so it was impossible to log in with a PIN and I had to look up my long random password on my phone. I mean I appreciate the update and all but come on, you can't say it was impossible for Microsoft to do a little routine saying "okay, save all of this shit temporarily in a file so we can load it back in after the update".[/QUOTE] It's actually a lot more complicated than that. Microsoft apparently did a pretty good job at decieving people how the process worked. The anniversary update isn't just a service pack. It is a literal reimage of the OS. That's why it's so huge and that's why apps get reinstalled, set to default etc. Its a non destructive reinstall of Windows. Given that, it makes complete and total sense. Now as to why I'm not sure, but I'm guessing that it was less error prone than the old service pack way.
Anyone remember windows ME or 2000? Pretty sure I had both when upgrading from 95 and 98. In 2000's case there was a critical error that fucked the installation. Its the only time I experienced a windows crash that wasnt caused by some sort of virus. At the time they were quickly replacing it with windows XP, which was being sold at retail in canada for hundreds of dollars. BUT, they had an "upgrade version" for existing windows owners for something like 200 instead. I remember a friend gave us a burnt copy of 95 which I installed, with the upgrade over top of it. Its funny that they got away with selling them at seperate prices when what was on the disc was essentially the same.
[QUOTE=Demache;51709233]It's actually a lot more complicated than that. Microsoft apparently did a pretty good job at decieving people how the process worked. The anniversary update isn't just a service pack. It is a literal reimage of the OS. That's why it's so huge and that's why apps get reinstalled, set to default etc. Its a non destructive reinstall of Windows. Given that, it makes complete and total sense. Now as to why I'm not sure, but I'm guessing that it was less error prone than the old service pack way.[/QUOTE] MS did say they were planning to move to a more rolling release cycle, not too dissimilar to that of OS X, where "updates" can be more than just delta patches for existing files. Re-imaging the OS may be the safest way to perform these updates for all we know. Considering it changed a lot of features in quite drastic ways, I'm not too surprised that the Threshold and Anniversary updates were re-images. [editline]22nd January 2017[/editline] [QUOTE=AetherSolace;51709236]Anyone remember windows ME or 2000? Pretty sure I had both when upgrading from 95 and 98. In 2000's case there was a critical error that fucked the installation. Its the only time I experienced a windows crash that wasnt caused by some sort of virus. At the time they were quickly replacing it with windows XP, which was being sold at retail in canada for hundreds of dollars. BUT, they had an "upgrade version" for existing windows owners for something like 200 instead. I remember a friend gave us a burnt copy of 95 which I installed, with the upgrade over top of it. Its funny that they got away with selling them at seperate prices when what was on the disc was essentially the same.[/QUOTE] You were never paying for what was on the disc in the first place. You were paying for the license to use what was on the disc. Hence the upgrade editions, MS assumed you'd be moving from a copy of Windows that either shipped with your hardware or you bought already, so they already had your money for the most part. The charge was for the right to convert that existing license into an XP one.
The only problems I had with the Anniversary update was Windows resetting my driver options (so that they would not download and install on their own) and on the process screwing up the Intel HD driver, which caused BSOD's
[QUOTE=AetherSolace;51709236]Anyone remember windows ME or 2000? Pretty sure I had both when upgrading from 95 and 98. In 2000's case there was a critical error that fucked the installation. Its the only time I experienced a windows crash that wasnt caused by some sort of virus. At the time they were quickly replacing it with windows XP, which was being sold at retail in canada for hundreds of dollars. BUT, they had an "upgrade version" for existing windows owners for something like 200 instead. I remember a friend gave us a burnt copy of 95 which I installed, with the upgrade over top of it. Its funny that they got away with selling them at seperate prices when what was on the disc was essentially the same.[/QUOTE] That's a pretty cool backstory to the upgrade processes we've had ever since, since we've had upgrade versions for every operating system since useless to those who skipped Vista! :v: [editline]23rd January 2017[/editline] [QUOTE=hexpunK;51709416]I'm not too surprised that the Threshold and Anniversary updates were re-images. [/QUOTE] All the insider builds have just been "Here's a 2gb installation" and 40 minutes of upgrading like you would any old to new version. I'm interested if UUP will change this though, as it is a 'update only what's changed' update method They say it's in use, but I'm still maxing out my bandwidth for ~15 minutes for the current builds install times have shortened to 16 minutes which is nice
[QUOTE=AetherSolace;51709236]Anyone remember windows ME or 2000? Pretty sure I had both when upgrading from 95 and 98. In 2000's case there was a critical error that fucked the installation. Its the only time I experienced a windows crash that wasnt caused by some sort of virus. At the time they were quickly replacing it with windows XP, which was being sold at retail in canada for hundreds of dollars. BUT, they had an "upgrade version" for existing windows owners for something like 200 instead. I remember a friend gave us a burnt copy of 95 which I installed, with the upgrade over top of it. Its funny that they got away with selling them at seperate prices when what was on the disc was essentially the same.[/QUOTE] You're not paying for the software, you're paying for the licensing of the software. The upgrade versions are a lot cheaper because they assume you have purchased a legal version of the old OS (by disc or through OEM) and you're not installing on bare metal.
I didn't have any issues yay. Frankly its handled poorly though and there's a reason why macs have the reputation of being hands free. Any time you get a new computer/big update there's a near guarantee of having to fiddle with it some. [editline]22nd January 2017[/editline] For example, I shouldn't have to edit the registry to turn off Cortana. That's quite needless.
[QUOTE=Mobon1;51709796]I didn't have any issues yay. Frankly its handled poorly though and there's a reason why macs have the reputation of being hands free. Any time you get a new computer/big update there's a near guarantee of having to fiddle with it some. [editline]22nd January 2017[/editline] For example, I shouldn't have to edit the registry to turn off Cortana. That's quite needless.[/QUOTE] Why would you disable it in the first place? Isn't it just a plain windows/web search?
[QUOTE=plunger435;51710381]Why would you disable it in the first place? Isn't it just a plain windows/web search?[/QUOTE] Because he wants to and it's his computer. That's all the reasoning he needs to turn any subsystem he wants to off.
[QUOTE=chipsnapper2;51709192]I'm still looking for a way to get 1511. The ISO files Microsoft puts out are for 1607. [editline]22nd January 2017[/editline] Nevertheless I'm happy with 8.1 and Classic Shell, with most Metro gestures (Charms, etc) disabled[/QUOTE] If you have Win10 then you can use the Windows Upgrade Assistant to forcibly update when the 'check for updates' thing can't find it.
[QUOTE=hexpunK;51709416]MS did say they were planning to move to a more rolling release cycle, not too dissimilar to that of OS X, where "updates" can be more than just delta patches for existing files. Re-imaging the OS may be the safest way to perform these updates for all we know. Considering it changed a lot of features in quite drastic ways, I'm not too surprised that the Threshold and Anniversary updates were re-images. [/QUOTE] Re-imaging the OS is not the safest way to perform updates, although one could consider the fact that Windows might still not have infrastructure to allow incremental and atomic OS updates without doing a re-imaging or even anything like it. Other systems, such as Linux server distributions, don't need to make use of unsafe upgrade options either.
Sorry, you need to Log In to post a reply to this thread.