Windows 10: Windows 10 1903 Update your device isn't quite ready

pjscott51 · Jun 27, 2019

I'm trying to update to 1903 but I get the message your device isn't quite ready.

I'm not sure why I'm getting this message since the PC is up to date with all the Windows updates.

Is there something else that I need to do to get the PC ready for 1903?

Thank,

Paul

:)

Sigurdur WilliamBrynjarsson · Jun 27, 2019

Printer isn´t working after latest update.

After the latest update from Windows, my Canon Pixma ip6600 printer isnt working. In Device Manager it shows up as working properly but when I go to print it isn´t listed as an option in any programs. Troubleshoot suggests it´s a USB 2 printer on a USB
3 port and that that´s the problem but that cant be since it worked fine before the update. I´ve tried to uninstall and plug it back in but that doesn´t work either.

Ramesh.Kumar · Jun 27, 2019

windows 10 "the device is not ready"

Hi,

If your device is working fine in Windows 7/8/8.1, I would suggest you to try the steps provided in the article mentioned below and see if it helps you to fix the issue. Though the article is for Windows 8.1 but steps holds good for Windows 10 too.

Get your apps and devices working in
Windows 8.1

Do keep us updated.

Regards,

Brink · Jun 27, 2019

Windows Update for Business and the retirement of SAC-T in Windows 10

In my post last May on Windows 10 and the “disappearing” SAC-T,I explained how we simplified and aligned our Windows servicing terminology with Office, reflecting that there are two Semi-Annual Channel (SAC) releases each year. I also explained that with Windows, there was never actually a Semi-Annual Channel (Targeted), or SAC-T, release; rather, SAC-T merely reflected a milestone for the semi-annual release. Unless you were using Windows Update for Business, the SAC and SAC-T designations had no impact on when your devices would be updated. At the time, we had not yet completed the work necessary to deliver the changes needed for Windows Update for Business to reflect the alignment with Office so we continued to show dates for both the SAC and SAC-T milestones on the Windows 10 release information page.

We have now completed that work. Beginning with Windows 10, version 1903 (the next feature update for Windows 10), the Windows 10 release information page will no longer list SAC-T information for version 1903 and future feature updates. Instead, you will find a single entry for each new SAC release. In addition, if you are using Windows Update for Business, you will see new UI and behavior to reflect that there is only one release date for each SAC release. If you use System Center Configuration Manager, Windows Server Update Services (WSUS), or other management tools, there will now only be one feature update published to WSUS, and this will occur at the time of release.

With this upcoming change, Windows Update for Business customers may have a few questions and I’ll try to address those now. To restate what I said above, unless you are using Windows Update for Business, the changes discussed below have no impact on when your devices get updated.

With the release of Windows 10, version 1903, how will my Windows Update for Business configuration and execution reflect the removal of SAC-T?

For releases prior to version 1903, Windows Update for Business customers had two settings they could utilize to designate when feature updates should be installed on their devices. The first was the branch readiness level (SAC or SAC-T), and the second was the deferral period, which specified the number of days after the branch readiness level-based date before an update was offered to a device.

Once your organization’s devices have been updated to Windows 10, version 1903, the configuration of Windows Update for Business will be simpler, enabling you to choose a single deferral value based solely on the SAC release date. That means, if you are trying to set up validation flights in your environment using Windows Update for Business, or stage updates in waves, you will do so from a common release start date, which should simplify the deployment process overall.

I want to clarify; with these changes, we will not change your deferral value. Instead, it will remain as it was configured following the update to version 1903. In addition, while all Windows Update for Business device deferrals will now be based on the release date (you will no longer have to configure this), you will continue to have the option to enroll devices in the Windows Insider Program and choose a pre-release ring, such as Slow, Fast, or Release Preview.

*Arrow How to Defer Feature and Quality Updates in Windows 10

The image below shows the Settings panel as it looks today with Windows 10, version 1809.

When version 1903 is released, it will look like this:

As you can see, it shows only pause and deferral settings; Semi-Annual Channel (Targeted) is no longer presented as an option. Again, this change will only be seen once you have deployed Windows 10, version 1903 and will only impact future feature updates after version 1903. Devices enrolled in the Windows Insider Program; however, can already see these changes.

How is Microsoft going to handle the transition to Windows 10, version 1903 for customers who have their branch readiness level configured for SAC?

As I said above, with version 1903, we will cease to publish both SAC and SAC-T dates. Each release will have a single SAC release date so we will handle this one-time transition in the following manner:

Windows Update for Business customers who have configured a deferral based on the SAC-T branch-readiness level (remember, this really is the actual release date), devices will be offered the update once the configured number of deferral days have passed. Thus, no change from previous releases.

For devices that have been configured with a branch readiness of SAC, for the upgrade to version 1903 only, we will add an additional 60 days to the configured deferral. This will simulate the delay previously experienced when Microsoft declared the SAC milestone. For example, if your device is currently configured to defer updates 30 days from the SAC release date, for the upgrade to version 1903 (and this time only), we would append a 60-day delay to that configured 30-day deferral–meaning that the device would be upgraded 90 days (60+30) after version 1903 is released. (Note that the additional 60 days will be handled on our service side, and will not be reflected in your device configuration.)

For subsequent feature updates after version 1903, your Windows Update for Business configuration deferral value will be whatever it was before version 1903; we are not modifying that value.

For future upgrades beyond Windows 10, version 1903, to establish an additional delay and recreate your deployments rings on the schedule you want, you will need to update your deferral value. Using the same example above, you would change the deferral value from 30 to 90 days. Or, if you want to create a three-ring deployment model, you could have three groups of devices, designated simply with deferral values from the single release date, perhaps 30, 60, and 90 days.

If you’re interested in learning more, or would like to see how you can use tools like Configuration Manager, WSUS, or Windows Update for Business to manage updates, see the Quick guide to Windows as a service. To learn more about Windows as a service, check out the Windows as a service gateway on Docs.
Click to expand...

Source: Windows Update for Business and the retirement of SAC-T - Microsoft Tech Community - 339523

Windows 10: Windows 10 1903 Update your device isn't quite ready

Windows 10 1903 Update your device isn't quite ready

Windows 10 1903 Update your device isn't quite ready

Windows 10 1903 Update your device isn't quite ready

Windows 10 1903 Update your device isn't quite ready - Similar Threads - 1903 Update device

"Device isn't quite ready" for 1903 update in 2021?!

An update is being prepared for your device, but it's not quite ready yet. We'll keep...

An update is being prepared for your device, but it's not quite ready

An update is being prepared for your device, but it's not quite ready

How to solve "an update is being prepared for your device, but it's not quite ready yet" issue?

Device not quite ready for Windows 2004. Why?

Your device isn’t quite ready for it. 2020 Update

An update is being prepared for your device, but it’s not quite ready yet

Device not ready to update to 1903

Users found this page by searching for:

device not quite ready for 1903

windows 10 1903 your device isnt quite ready

windows 1903 device not quite ready