Just wondering if anyone else has seen this, You click schedule updates on a Windows 10 image and shows no updates available. I know have approved Windows 10 updates as I have several clients getting this updates.

I think this may be in the culprit as why no updates show up.  If I look in the SMSProv.log I see this line which may be the culprit

"ExecQueryAsync: COMPLETE select * from SMS_UpdateCategoryInstance where LocalizedCategoryInstanceName like '%Windows vNext Preview%'"

Just wondering if anyone else has seen this next step is most likely calling support.

Yes, known issue. 

If you are able to change entries in SCCM database called "SupportedProductsForOfflineServicing", replace value "Windows Next Preview" with "Windows 10" which should enable finding updates for Windows 10 when scheduling offline servicing updates

If you are able to change entries in SCCM database table called "SupportedProductsForOfflineServicing", replace value "Windows Next Preview" with "Windows 10" which should enable finding updates for Windows 10 when scheduling offline servicing updates

• Edited by Vladimir Sorokin 12 hours 4 minutes ago

If you are able to change entries in SCCM database table called "SupportedProductsForOfflineServicing", replace value "Windows Next Preview" with "Windows 10" which should enable finding updates for Windows 10 when scheduling offline servicing updates

• Edited by Vladimir Sorokin Friday, August 21, 2015 7:44 PM

If you are able to change entries in SCCM database called "SupportedProductsForOfflineServicing", replace value "Windows Next Preview" with "Windows 10" which should enable finding updates for Windows 10 when scheduling offline servicing updates

... which is an unsupported database modification. 

Any word if they are working on a fix? Seems like a big bug.

Also experiencing the same bug here - and waiting for any official announcement for a fix

Looks a hotfix has been released for this issue. https://support.microsoft.com/en-us/kb/3089193

Looks a hotfix has been released for this issue. https://support.microsoft.com/en-us/kb/3089193

• Proposed as answer by Torsten [MVP]MVP 18 hours 41 minutes ago
• Marked as answer by Joyce LMicrosoft contingent staff, Moderator 2 minutes ago

Looks a hotfix has been released for this issue. https://support.microsoft.com/en-us/kb/3089193

• Proposed as answer by Torsten [MVP]MVP Thursday, September 03, 2015 1:09 PM
• Marked as answer by Joyce LMicrosoft contingent staff, Moderator Friday, September 04, 2015 7:48 AM

I applied this hotfix in my environment and it does resolve the issue.

Thanks! It did solve the problem here too