Windows 10: Can't ever update to Windows 1903 since it was released

ShehabMahmoud · Aug 14, 2019

In the update and security section I always have that "Download and install now" button about the May update whenever I click on it it starts downloading until like 98 or something then it always crashes with an error, last time was 0x80240034, before that one was 0x80246007, there's always an error!! I tried the update assistant, crashes. the media center, not working. how do i solve this problem?

:)

neilpzz · Aug 14, 2019

When is there going to be an update to 1903 that works with Radeon drivers? Either from Microsoft or Radeon?

The list of known issues seems to suggest the listed graphics problem is resolved.

Windows 10, version 1903 and Windows Server, version 1903 - Windows Release Information

Brink · Aug 14, 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

MJLONGLEY · Aug 14, 2019

Windows 10 1903 update - resulting problems

Hi Vijay,

Thank you for the rapid response.

Your suggested actions are very technical - hardly for 'the man in the street'

'

If I understand correctly, in simple terms, you are suggesting changing the path/method of obtaining the 1903 update but still installing it anyway -

Surely if the problem is actually with the 1903 update then the result will be the same problems irrespective of how it is applied?

Please could you clarify in simple terms, step by step, what your suggested actions actually do and how this may solve the problem.

Thanks,

Mike Longley.

Windows 10: Can't ever update to Windows 1903 since it was released

Can't ever update to Windows 1903 since it was released

Can't ever update to Windows 1903 since it was released

Can't ever update to Windows 1903 since it was released

Can't ever update to Windows 1903 since it was released - Similar Threads - Can't ever update

NIGHT LIGHT CAN'T BE ENABLED EVER SINCE UPDATING TO WINDOWS 11

NIGHT LIGHT CAN'T BE ENABLED EVER SINCE UPDATING TO WINDOWS 11

BSOD ever since update drivers

BSOD ever since update drivers

BSOD on laptop ever since update

BSOD on laptop ever since update

Windows update to 1903 since 1809

Can't Connect Remote Desktop Since Update 1903

Can't update Windows 10 to version 1903 since it came out

Users found this page by searching for:

cant update to 1903

windows 1903 not getting deplozed automaticallz

why cant I update to 1903