When will MS start pushing the update to Win10 1809 on machines set for the SAC “branch”?

Topic

New Reply

It’s a simple question. I have my Win1803 machine set up with my recommended Windows Update advanced options: Microsoft says it’s getting rid of “Semi
[See the full post at: When will MS start pushing the update to Win10 1809 on machines set for the SAC “branch”?]

5 users thanked author for this post.

abbodi86, Fred, Great Lake Bunyip, PhotM, GreatAndPowerfulTech

Reply | Quote

Replies

Good question.

One of my machines got the update. It was set to SAC (targeted).
My other machine was changed to targeted and the update happened.

M$ has so many sticks in the fire, they probably forgot about SAC.

 

Byte me!

Reply | Quote

woody wrote:

Perhaps, as @b says, they’ll do the same to 1803.

Not 1803 or 1809, just 1903.

Reply | Quote

Soooooo… you’re saying that if my 1803 machine is set up as in the screenshot, 60 days after 1903 is released + my deferral days (which is 120) = 180 days after 1903 is released, my machine will be updated from 1803 to 1903?

Yep, that makes sense. In a convoluted way.

Every time MS changes its terminology, I’m left scratching my head.

(NOTE: Microsoft says that it will do that to an 1809 machine with the settings in the screenshot – upgrade it 60 + 120 days after 1903 hits RTM. They haven’t said a peep about 1803 machines.)

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

As if it weren’t confusing enough trying to decide which upgrade to install, now that my 1709 is running out of time and I had hoped 1809 would actually get the SAC blessing, I’m again left wondering what to do. Microsoft saying that they “recommend” 1809 but at the same time avoiding calling it SAC doesn’t instill confidence in the product. On top of it’s tarnished reputation.

Frankly, the twice yearly upgrades are exhausting. Since mid 2017 running Windows 10 I’ve had several clean reinstalls required simply to fix upgrade issues (some issues with drivers were never resolved) not counting the half dozen other people I’ve helped who also required clean reinstalls. In 7 years using Windows 7 I only required clean reinstalls when I installed a new motherboard or bought a new system, never from installing Service Packs, and that’s on a dozen different machines over the 7 years between me and my associates I helped with installs.

It’s now to the point where upgrading Windows 10 is far more disruptive than running and upgrading Linux with all it’s geeky idiosyncrasies. With this latest Windows 10 confusion, I’ll be pulling my 1709 system off the internet completely when MS starts to force upgrading to 1809/1903 and run Linux only on an internet facing system. I’ll see how Windows 10 evolves over 2019 before I go with another upgrade.

1 user thanked author for this post.

teuhasn

Reply | Quote

In a strange, mealy-mouthed way, 1809 has received a kinda SAC-style blessing.

More accurately, Microsoft is hinting that they won’t give a SAC-style blessing for 1809, and it’s becoming increasingly clear that what we’ve got is all we’re going to get.

1 user thanked author for this post.

Great Lake Bunyip

Reply | Quote

They released refreshed ISO files for Enterprise LTSC edition few days ago, maybe the business-ready declare is close

3 users thanked author for this post.

woody, b, PKCano

Reply | Quote

I hope they do something….

Reply | Quote

Apologies if this is the wrong place, and I’ll move this if suggested.

I have Win 10 Pro 64-bit version 1709, for which security updates end very soon. How can I move now to 1803 and NOT to 1809? (FYI – I delay updates as much as possible, thanks to the great tips here.)

IMPORTANT – my PC dual boots Win 7 Pro 64-bit and Win 10 Pro 64-bit (currently 1709). Will the technique for upgrading 1709 to 1803 wipe out my Win 7 partition?

Thanks.

Reply | Quote

@glnz-

Probably best to start your own support topic. Check out Forums in the top bar. AskWoody Support… Windows… Windows 10 version 1803?

Hint for the future- If you download an ISO of each version, just before the next version is issued, from Microsoft, you will have a copy of the version if and when you need it.

Non-techy Win 10 Pro and Linux Mint experimenter

Reply | Quote

Elly – you are right, but I just completed the update to 1803 (and not 1809).

Elsewhere, it was suggested to change our “Defer Feature Update” setting from 365 days to a lower number that would pick up the 1803 update but not the more recent 1809, and so I picked 250 days.  That got me the update to 1803, which took a LOOOONG time to finish, but all looks good.  After the update, I set it back to 365 days.

1 user thanked author for this post.

Elly

Reply | Quote

You’ve solved your problem, glnz, but I’ll add this for anyone else. There are several methods to obtain the ISOs directly.

1803 and 1809 ISOs are both available in the “Select Edition” dropdown at the Microsoft Windows 10 ISO webpage using:

1) a browser under native Linux (I haven’t tested it in a VM), or

2) I successfully tested a change in the about:config settings in my Windows 10 1709 Firefox 65, that sets a new string, general.useragent.override, with the value of a generic Linux browser.

This method of spoofing the browser agent is explained here, with a link to a list of possible browser values.

https://www.howtogeek.com/113439/how-to-change-your-browsers-user-agent-without-installing-any-extensions/

Just remember to reset general.useragent.override after your done.

3) Previously I have used a user-agent-spoofer addon in Firefox under Windows for this, but the addon I used wasn’t updated for Quantum and I haven’t tested any alternatives. Quick reviews indicate the ones available now are a bit leaky/buggy.

Reply | Quote

JimmyJames and the Flames – Your post above is very interesting, but please check it.  I think you have some posting-code problems.  I think this forum uses [bb code] in brackets.

Reply | Quote

Wow, you’re fast, I edited it within a minute or two. Thanks!

Reply | Quote

Thanks – but what again is the link to “Microsoft Windows 10 ISO webpage” that has the dropdown if I’m looking at it from a genuine Linux browser?

Would this work if I use genuine Safari on my wife’s iMac?

Reply | Quote

Sure does – on my Macs
Even from Firefox on my Macs.

Reply | Quote

The ISO page is the main download link for Windows 10, but under Linux it redirects to the ISO dropdown options instead of the Download Tool option.

https://www.microsoft.com/en-us/software-download/windows10

Reply | Quote

Fascinating.  Interesting that an Apple person can get this but not a MS person.  Well, I also use my wife’s Prime.

If only I could get it to download across my home network onto my PC instead of into the iMac, or even onto a USB stick.

UPDATE – I was able to pull it from my XP machine and its Firefox – go figure!

Reply | Quote

Windows 10/8.1 IOS files can be downloaded from Microsoft using Fido (powershell script)

https://github.com/pbatard/Fido/releases

Reply | Quote

Hm. I wonder what build versions they have up there… I suppose I should just download and check…

Distinctly recall that at some point those versions were older builds than what the Media Creation Tool produced.

 

Edit, checked. Yes, at least the 1803 is the original April general release version.

Which reminds me, should remember to use the MCT again to get an up-to-date 1809 .iso before 1903 is released and the MCT switches to that. … though as of today, MCT produces 17763.253 still.

 

Oh yeah, the web page is funny if you use Windows Subsystem for Linux. With the w3m browser from the WSL command line, it’ll offer the Media Creation Tool… but at least the Midori browser (using VcXsrv for graphics) gives you the dropdown menu for downloadable .iso files.

Reply | Quote

hi woody.

you may want to read Bogdan’s recent article from Softpedia news:
https://news.softpedia.com/news/microsoft-says-some-devices-still-blocked-from-getting-windows-10-version-1809-525326.shtml

MS will still block or not offer the 1809 upgrade for those using the bad or faulty Intel display drivers; THAT “block” is still in place

Reply | Quote

I use the latest Intel DCH drivers (i7-8750H) on my 1803 Windows 10 with the same settings as the OP, and still no 1809.

Reply | Quote