Remember “Download and install now” – the big reason to upgrade to 1903? Yeah. Not so much.

Topic

New Reply

I have high hopes for “Download and install now,” the new feature in Win10 version 1903, just out. Six weeks ago I wrote about it, saying: By the time
[See the full post at: Remember “Download and install now” – the big reason to upgrade to 1903? Yeah. Not so much.]

2 users thanked author for this post.

abbodi86, Elly

Reply | Quote

Replies

Upgraded from 1809 to 1903. Remote desktop now shows a black screen on computers with older Intel embedded video cards. My Hauppauge tuners are no longer accessible via the browser (not working on 1809 or 1803 after updates on the 14th.). My version of Macrium Reflect errors out with VSS issues.

ms-resource:appDisplayName and ms-resource:AppName/Text errors in the start menu. TileDataLayer\Database\EDB.log errors. Too many errors in the Event Viewer too even think about chasing them down. AND the Action Center will drive you over the edge with notifications on how to reduce notifications!

1 user thanked author for this post.

doriel

Reply | Quote

This entire mess reeks of a bait-and-switch.

“From now on, we won’t push the newest feature update until your current build is near the end of its service life.”

Meanwhile, in the super-secret MS conference room:

“So, how soon after we release a new build are we going to deem the old version ‘near end of service?’  How about two weeks?”

“Sounds good to me!”  Cheers all around the room.

This is just the highest order of BS imaginable.  Give everyone hope they’ll have some control over their own computers, but then caveat it in such a way that MS still can just yank the rug out from under you, and surprise install the newest version whenever they  feel like it.

To be fair, this wouldn’t sound like such a sneaky move if 1809 hadn’t crashed and burned, and more people would have been on that one.

But saying a build with upwards of 5 months of real support left is “near end of life” just makes everything about this supposed effort to put control back into the hands of users seem like a bold-faced lie.

1 user thanked author for this post.

woody

Reply | Quote

Thank you for your post. This upgrading havoc is terrible. Not only Windows, but all software went crazy recently.. I choose not to upgrade even in bussiness. Our firewall should do the work we payed for. Everything “checks for updates” and changes constantly. Which also mean slowing your network connection, but arent these upgrades great target for hackers in the end? Cant they “send you malicious upgrade”, nobody tested this possibility?
Why we cant have ONE FULLY FUNCTIONAL PRODUCT? That we payed for, by the way.. I dont wanna constantly solve problems caused by upgrades. Other thing I dont understand, how is it possible, that there are so many security problems? Seems to me, that Widows are some sort of Emmentaller cheese.
And one question.. What is the ratio of problems caused by hackers and by microsoft updates globally?
I think its like”
95% microsoft : 5% hackers

Something positive? We have open source calculator on github, hooray!!! Microsoft, you absolutely rock!

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

1 user thanked author for this post.

glnz

Reply | Quote

https://support.microsoft.com/en-us/help/4497934/windows-10-update-kb4497934 

Okay I don’t get the download and update now feature release option.  Do you see it when your system is deemed worthy?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Susan:

It seems the link the the MS “support” page you posted is either incomplete, or MS has pulled the page.

All I get when I click on the link in your post is an error page, the main message is: “An error has Occurred” Please try your request again.

Reply | Quote

It works for me. Try again.

Reply | Quote

I believe @photm had the same experience, and queried if it might be related to Group Policy settings, as it showed as being “Some settings are managed by your organization”.

Reply | Quote

Ok, I’m just a simple home user, not some big-time IT type.  So explain it to me, if 1903 should NOT be uploaded and installed why is the Defcon at level 3?

Reply | Quote

The DEFCON level was set for XP, Win7/8.1 – please see the blogpost explaining the reason.

1 user thanked author for this post.

woody

Reply | Quote

I installed KB4497934 on 1809 and within 24 hours I got the “download and install now” option for 1903.

Thanks, but I’ll pass for now…

Reply | Quote

Hey, I’ve got a quick question (sorry if it sounds dumb): since I do plan to continue using 1803 until it dies in November, what exactly do I need to proactively block 1903?

So far, I have set my connection to metered, I’m avoiding like a plague any release of KB4023057 (hid them in wushowhide and uninstalled the one version that managed to get installed) and of course I’m not actively seeking for updates. Also, I plan to hide the feature update to 1903 in wushowhide whenever it pops up. Will this suffice to block 1903? Or is there anything else I should consider?

Also, does anyone know if wushowhide will still allow to hide feature updates after installing KB4499183? I’m yet to see KB4499183 available for installation on my system, but I suppose it will appear sooner or later.

BTW, I find it plain crazy that MS wants people to upgrade from 1803 to 1903 in June when 1803 still has around 6 months worth of support and 1903 has been available to the public at large for no more than roughly 1 month. I certainly do not feel like playing guinea pig to assist figuring out whatever bugs still plague 1903…

Reply | Quote

You don’t say whether you have the Home version of Win10 or Pro. If you have Pro, there are ways to block Feature Updates.

KB4499183 is not being offered through Windows Update unless you are a “Seeker.” In other words, you have to turn off Metered connections and “Check for Updates.” You may see it or not immediately, just keep trying.

Reply | Quote

Thanks for your reply PKCano!

Sorry, my bad: I forgot to mention I have Win10 Home version, so I can’t use the Pro features to block feature updates. Sounds like there is nothing more that I can do right now to stay away from 1903 other than what I’m already doing.

And thanks for the input regarding KB4499183: guess that for the moment I will not install it given that it requires turning off Metered connections and doing a “Check for Updates”.

Reply | Quote

You can try downloading from the update catalog – https://www.catalog.update.microsoft.com/Search.aspx?q=KB4499183

JUst be sure to get the one appropriate for your machine (x86 or x64).

--Joe

Reply | Quote

See https://www.computerworld.com/article/3232632/how-to-block-the-windows-10-may-2019-update-version-1903-from-installing.html

Reply | Quote

I have Win 10 Pro 64-bit (version 1803).  I went to MS Catalog and downloaded and installed KB4499183 earlier today.  (Settings- System-About shows I’m still version 1803.)

When I go to Settings – Update & Security, it looks the same as before.  I don’t see any new controls or options.

What am I missing?

Thanks.

Reply | Quote

“Download and install now” won’t appear until there’s something new to download and install.

Reply | Quote

b – Ok.  So I’m not seeing “Download & Install” for 1809 or 1903 because in Advanced Options, I have Feature Updates deferred for 365 days and Quality Updates deferred for 30 days?

A)  Right now, with these settings and the KB4499183 , what would happen if I pushed the Check for updates” button.

B)  If I were to put both settings to 0 (zero) and did NOT push the button, what would I see?

C) If I were to put Feature Updates deferred to 90 and Quality Updates deferred to 0 (zero) and did NOT push the button, what would I see?

Seems silly that MS would put us through this matrix.

Thanks.

Reply | Quote

b – Ok.  So I’m not seeing “Download & Install” for 1809 or 1903 because in Advanced Options, I have Feature Updates deferred for 365 days and Quality Updates deferred for 30 days?

A)  Right now, with these settings and the KB4499183 , what would happen if I pushed the “Check for updates” button.

B)  If I were to put both settings to 0 (zero) and did NOT push the button, what would I see?

C) If I were to put Feature Updates deferred to 90 and Quality Updates deferred to 0 (zero) and did NOT push the button, what would I see?

Seems silly that MS would put us through this matrix.

Thanks.

Reply | Quote

A) Nothing (probably).
B) 1903, with “Download and install now” option (possibly).
C) 1809, with “Download and install now” option (probably).

What silly matrix?

“If it works as expected, it’ll be the best new feature to arrive in Windows 10 ever. …

“Download and install now” has the potential to improve Win10 for everybody.”

Win10’s new “Download and install now” option

Reply | Quote

Link to ghacks.net on the subject, appears the new update is still not ready for prime time.
Assume this also applies to the 1803 and 1809 update enhancements?

https://www.ghacks.net/2019/05/28/windows-10-1903-the-case-of-the-missing-update-deferral-options/

Admin Note: There are now three (3) Topic threads going on regarding this new way to Update Windows 10 versions 1903, 1809, and 1803. Any way to get them together so all relevant commentary is in one place? It is hard to decide where to best comment any longer.

Windows 11 Pro v24H2 and Windows 10 Pro x64 v22H2

1 user thanked author for this post.

CADesertRat

Reply | Quote

According to that article, at least Group Policy is still in play for W10 Pro and above. I was curious about whether MS would remove that option.

Don't take yourself so seriously, no one else does
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

Reply | Quote

Can someone clarify that IF I’m W10 Home and want to allow 1903 – I CANNOT have a usual Bkup-to-USB  plugged-in – OR – Will MS Fix that issue First so that it won’t matter?

Many Thanks!

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

Reply | Quote

That issue should be fixed in the June Patch Tuesday update.

1 user thanked author for this post.

CraigS26

Reply | Quote