{"id":14612,"date":"2020-06-03T00:01:00","date_gmt":"2020-06-02T22:01:00","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=14612"},"modified":"2020-07-29T00:45:51","modified_gmt":"2020-07-28T22:45:51","slug":"windows-10-version-2004-forced-upgrade-without-user-consent","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/06\/03\/windows-10-version-2004-forced-upgrade-without-user-consent\/","title":{"rendered":"Windows 10 Version 2004: Forced upgrade without user consent"},"content":{"rendered":"

[German<\/a>]The new Windows 10 May 2020 Update (Version 2004) has been generally available since May 27, 2020 and is being rolled out only slowly. But I have already seen reports that systems are automatically updated to Windows 10 Version 2004 without any user interaction.<\/p>\n

<\/p>\n

Feature update: This is how it should work<\/h2>\n

\"\"Since Windows 10 version 1903, feature updates should be offered as optional. The user must explicitly trigger the download and installation, as shown in the following screenshot for version 1903.<\/p>\n

\"Feature
\n(Feature updates in Windows 10 May 2019 Update, Source: Microsoft)<\/p>\n

Starting with Windows 10 May 2019 Update, Version 1903, Microsoft grants users in all versions a possibility to postpone quality updates by 5 x 7 days (35 days). I had described this in the article Windows 10 May 2019 Update brings back Update control<\/a>. At the same time Microsoft has introduced a second, positive innovation. Functional updates can be postponed by the user until shortly before the end of the support period of the installation (see Windows 10 V1903: Update Control Inconsistencies \u2013 Part 2<\/a>).<\/p>\n

A reader's feedback<\/h2>\n

End of May 2020 German blog reader H.v.H. contacted me and reported a strange observation (thanks for that). He writes:<\/p>\n

Hello G\u00fcnter,<\/p>\n

without any action on my part, MS installed the 2004 update.
\nOnly the reboot was still pending.<\/p>\n

Procedure:<\/p>\n

within 6 min 2 reboots
\nblue screen with \"Updates for you are being prepared
\nafter 7:30 min in total (SSD hard disk)
\nstarted Edge on my normal screen view
\nFirefox remained the default browser
\ntested the scanner: ok (driver works)
\nof the 86 installed programs, 35 got the current installation date (4 of them from MS)
\nEverything seems to be going as usual.<\/p><\/blockquote>\n

At the same time I received this comment<\/a> here in my blog. EP refers to a discussion at askwoody.com<\/a> where the same thing happened to a user. And Susan Bradley also puts together some observations of this kind in this askwoody short article<\/a>. This is addressed also here<\/a>.<\/p>\n

Another reader observation about defer update<\/h2>\n

In the blog post Windows 10 Version 2004\/Windows Server 2004 released<\/a> I wrote that all feature updates are optional, and that the user need to click the Download and install <\/em>link, to triger an upgrade. Blog-reader Martin responded with the following observation.<\/p>\n

Yes and no… this is only true (at least according to my tests 1903->1909) if the setting \"Delay function updates and\/or quality updates\" is set
\nis not used – i.e. remains at 0 days. If this is not the case (1 day delay is enough) a new version will be installed automatically.<\/p><\/blockquote>\n

This may have been an explanation, but it doesn't quite fit together. Some users were probably with delay 0 in Windows 10 Home V190x.<\/p>\n

Have update defer options been removed?<\/h2>\n

On reddit.com there is this post<\/a> where someone asks if the delay options for feature updates in Windows 10 version 2004 have been removed.<\/p>\n

Has MS removed option to defer feature updates for 365 days from Pro 2004?<\/p>\n

I have just clean installed Pro 2004 (new iso today) on a pc and the option to defer feature updates for 365 days is missing.<\/p>\n

Comparing registry with 1909, it is quite different and I have a suspicion you can now only defer feature updates on enterprise as the deferfeaturesupdate keyword has moved into a folder that seems only to apply for business users<\/p><\/blockquote>\n

Although one respondent explains that delay options for feature updates have not been required since the 1903 version, the answer is no longer necessary. But the experiences outlined above show me a different picture. Something doesn't fit together anymore. Do you have had similar experiences or have an explanation?<\/p>\n

Similar articles:
\n<\/strong>Windows 10 Version 2004\/Windows Server 2004 released<\/a>
\nWindows 10 Mai 2020 Update released at MSDN & for OEM<\/a>
\nRefreshed Windows 10 V2004 ISOs released on MSDN\/MVS<\/a>
\nWindows 10 Version 2004: Deprecated\/removed features<\/a>
\nUpgrade Block to Windows 10 2004 for devices with Core isolation (HVCI)<\/a><\/p>\n

Windows 10: Issues with update options \u2013 Part 1<\/a>
\nWindows 10 V1903: Update Control Inconsistencies \u2013 Part 2<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

[German]The new Windows 10 May 2020 Update (Version 2004) has been generally available since May 27, 2020 and is being rolled out only slowly. But I have already seen reports that systems are automatically updated to Windows 10 Version 2004 … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22,2],"tags":[41,2451],"class_list":["post-14612","post","type-post","status-publish","format-standard","hentry","category-update","category-windows","tag-upgrade","tag-windows-10-2004"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/14612","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=14612"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/14612\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=14612"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=14612"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=14612"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}