Issue in Windows 10 Build 10130 prevents detection of new preview builds

[allheart55 (Cindy E)]

After all the confusion about Windows 10 upgrades over this past weekend things have been very quiet on the Ring Master front.

Many times over the course of the development of Windows 10 we have attempted to infer certain outcomes/actions around build releases based on the Twitter presence and activity of Gabe Aul.

He has been quiet for the last 18 hours as of this articles posting. It has also been over three weeks since Microsoft released the last build of Windows 10, 10130, to Windows Insiders.

With the availability date of Windows 10 just over a month away time is getting tight to close out the development of Windows 10 so it can go RTM and be prepared for its arrival to Windows 7 and 8.1 users on 29 July 2015.

I wrote last week that I believed Microsoft had just two more builds of Windows 10 to provide to Insiders before that happens.

Over on social media many of us thought that new build would come out late last week or even early this week but it is yet to materialize.

Could it have been delayed because of all the blogging and editing that occurred to try and set things right concerning who gets Windows 10 for free?

Maybe.

However, it now appears that an issue with Windows 10 Build 10130 being unable to scan with Windows Update and recognize a new build of Windows 10 might be the cause of the delay.

Today Microsoft released KB3070677 on Windows Update to address this very issue.

Windows Update might not detect new builds on Core Editions of Windows 10 Insider Preview

Symptoms Consider the following scenario:

• You install a Core Edition of Windows 10 Insider Preview.
• You are running Build 10130 of this Core Edition of Windows 10 Insider Preview.
• There are new preview builds available for your current preview build settings.

In this scenario, when you scan for new preview builds, Windows Update does not detect the available preview builds.

This update will resolve the issue and allow Microsoft to push the publish button on the next Windows Insider Fast Ring build.

Source : winsupersite

 

[AWS]

I am not seeing the update. I tried to update twice and only pulled down a update to MSE database.

 

[starbuck]

I am not seeing the update. I tried to update twice and only pulled down a update to MSE database.

Same here.
Also when I check the advanced options, they are set for 'Slow' build.
They are meant to be 'Fast' build.
If I change it to fast build, it alters back as soon as i come out of the advanced options screen.

 

[AWS]

Mine was always on fast, but, that could be because I started on the developer previews and updated to public preview.

 

[starbuck]

Mine was always set to fast and worked fine until the last but one preview update.
M$ did say there was a problem with the fast build being reset to slow.... but that was meant to be addressed in the last preview build.
Seems mine didn't get fixed though

 

[allheart55 (Cindy E)]

I've been in the fast ring since the beginning too.
I haven't had a problem.

 

[starbuck]

After checking on the 'Insider Hub'... seems there's a few having this problem.
Tried the typical suggestions from the M$ Team:
Troubleshoot Windows Update
Run SFC /Scannow

still no joy.

 

[starbuck]

Back on the fast ring now.

Even editing the registry entry for the slow/fast option didn't help.
Tried plan B...... recover back to the previous build.
Big mistake!
Rolled back Ok, but also removed the wifi drivers and usb drivers in the process.
Just left plan C..... Download a fresh ISO for Build 10130 .
Not a big problem as I have hardly any software installed on the Win10 partition.

All worked fine and is still on the fast ring after 24 hours.
Now where is Build 10158 ... am waiting patiently.

 

[AWS]

Now where is Build 10158 ... am waiting patiently.

I got the build yesterday so it is there.

 

[starbuck]

For some reason it passed me by.......
But today it did download 10162

 

[AWS]

I got 10162 this morning. Didn't install first time. Got stuck at 32%. Second attempt went of without a problem.