Customise Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.

No cookies to display.

Grabbing Windows 10 2004 – Device Not Ready?

Share this post:

Trying to get the new 2004 Build on you device & running in to this screen on your updates?

‘Your device isn’t quite ready’

This means there’s a reason to temporarily block you from getting the new build. (This is good! You’ve just been saved from possible compatibility issues with your current setup)

These reasons are listed here: Windows 10 Release Health (tip: on the page hit CTRL+F & look for hold)

What should you do?

  • Option A (recommended): Get all your drivers & software updated to be sure you get the build as soon as possible & wait for the fixed drivers or patches from Microsoft
  • Option B (if you feel like taking a risk): Head over to the Update Assistant or media creation tool this will upgrade your build but you will be taking the risk to run into one of the earlier listed issues, so if you’re taking this road, make sure you read through the possible issues you might be facing 1st.

In both cases, keep an eye on the Windows 10 Release Health page for fixes & Workarounds, as soon as your hold reason is fixed it will be updates to a Mitigated state.

Share this post:

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.