Microsoft is doing the right thing this time around and blocking the Widows 10 May 2020 Update on a lof of PCs. If yours is one of them – don’t worry, be happy.<\/span><\/strong><\/p>\n If you’ve been trying to install the May 2020 Update for Windows 10 without success – you’re not the only one. Many Windows 10 users are seeing a notification that their device is not compatible with the latest feature upgrade (Windows 10 May 2020 Update – version 2004). <\/span><\/p>\n If you’re getting a “your device is not compatible” notification when trying to install the Windows 10 May 2020 update, don’t worry. This time Microsoft is not pushing the new feature update on Windows 2010 users. This time the company appears to be taking a more conservative and more sensible approach. This hopefully, will result in fewer problems for Windows 10 users and fewer public relations nightmares for Microsoft.<\/span><\/p>\n The May 2020 Update is the first of two major (version) upgrades for Windows 10 scheduled for this year. It is already rolling out to\u00a0 Windows 10 Users. This time, Microsoft is throttling back the rollout speed and not pushing it out to machines that may not currently be compatible. <\/span><\/p>\n Microsoft seems to be slowing down this version update rollout to avoid the widespread problems that have caused so many problems for so many Windows 10 users.<\/span><\/p>\n From what I’ve been able to certain through my research, a significant number of Windows 10 users are getting notifications that their “device is not quite ready” for Windows 10 version 2020.\u00a0<\/span>The Windows notification says:<\/span><\/p>\n “The Windows 10 May 2020 Update is on its way. We\u2019re offering this update to compatible devices, but your device isn\u2019t quite ready for it. Once your device is ready, you\u2019ll see the update available on this page. There\u2019s nothing you need to do at this time. “<\/span><\/p><\/blockquote>\n The notification is, I believe, intentionally vague. But the cautious approach and the slower rollout that Microsoft is using this time, in my opinion, are the right ways to do things. It is much better than the ways of the past where Microsoft seemed to rush things out, pushing users to install the feature update and then letting the users deal with the problems. <\/span><\/p>\n In fairness to Microsoft, it’s important to remember that Windows has to work on a multitude of hardware combinations and trying to rush the rollout only brings a lot of grief to Windows 10 users — not to mention a lot of bad press for Microsoft. Microsoft, at least this time around, acknowledges that Windows 10 version 2004 has several known issues<\/a><\/span> that they are currently investigating.<\/span><\/p>\n I have Windows 10 2004 installed on one of my laptops. It’s the one that I use for testing. But I’m in no rush to install the Windows 10 May 2020 update (version 2004) on my other laptop until Microsoft has had plenty of time to work out the bugs. So far, I have had no major problems with the new update on my test computer, nevertheless, I’m going to wait for a few weeks before I install it on my other laptop.<\/span><\/p>\n If if you are one of the many Windows 10 users who are getting the notification that your device isn’t quite ready for the May 2020 Update (version 2004). Don’t worry, be happy. It will all work out for the best.\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":" Problems Installing the Windows 10 May 2020 Update? Don’t Worry, Be Happy Microsoft is doing the right thing this time around and blocking the Widows 10 May 2020 Update on a lof of PCs. If yours is one of them – don’t worry, be happy. If you’ve been trying to install the May 2020 Update for\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":17517,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,2366],"tags":[3946,3939,3884],"_links":{"self":[{"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/posts\/19454"}],"collection":[{"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/comments?post=19454"}],"version-history":[{"count":3,"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/posts\/19454\/revisions"}],"predecessor-version":[{"id":19458,"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/posts\/19454\/revisions\/19458"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/media\/17517"}],"wp:attachment":[{"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/media?parent=19454"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/categories?post=19454"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thundercloud.net\/infoave\/new\/wp-json\/wp\/v2\/tags?post=19454"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Cloudeight](\"https:\/\/www.thundercloud.net\/infoave\/new\/wp-content\/uploads\/2020\/06\/may2020.png\")
<\/span><\/p>\n