This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have Windows 10 Cloud-Only computers in Intune. Update rings are enabled (defer=0) and Feature updates are set to 2004. I stopped seeing 2004 availability this week maybe on my 1909 computers. It was there at some point, but not anymore. I then changed by update ring to be more manual, to be able to scan and check itself without enforement, but still nothing. Now I can't upgrade my 1909 computers to 2004. Regular updates work, like 1909's CUs and stuff.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 98%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
I have deployed update rings and feature updates on the client devices, and the 2004 feature update is available on the client devices.
Please see the following screenshot.
AI also have Hyper-V clients in the same state, they don't see, 2004, so I doubt it is about any hardware compatibility.
I don't think it's about hardware compatibility.
Just in case, please make sure you assign the feature update policy to the device groups, not user groups.
In addition, please check the enrollment status of the devices, and make sure it can communicate with Intune service correctly.
Yes sure, Feature Update policy is applied to Devices and Update rings also. When 2004 was released, sometime in May I did see its offering but not anymore, it was gone in July.
I found 1709 from a closet, installed 3 years ago. 1909 is offered to it, not 2004.