Windows 10 Insider Preview Fast/Slow/RP Build 17134.5 - April 27 Insider

slicendice said:

This is where the judgement has failed. Take Edge for instance. It has been buggy, or at least functions around it has been buggy since Windows 10 initial release. It has taken years to get it even remotely reliable and it still has a long way to go.

In my eyes, this is a really bad business decision, since MS has been aware of this from the start and the fix is easy really compared to other more complex things going on in Windows.

You are ignoring the simple fact that you do not have to use Edge. Most Edge bugs are irritating - not showstoppers. I certainly do not want development held up because of irritating bugs.

I am very happy for you to hold back on upgrading whilst I use it asap, and report significant issues, so when you finally upgrade, then you get the benefit of my (and other trailblazers) unselfish efforts on your behalf, and you will be happy as we will have picked up issues that would not have manifested until much later if the release was held up :).

kado897 said:

Finally made it to the desktop. Took 4 hours altogether.

That is real Progress..When they first started this program it was faster. Mine only tool a little over 2 hours with 4 failures. I would still like to know what the known issues were that were fixed in this build. Maybe Zac Bowden knows?

Josey Wales said:

That is real Progress..When they first started this program it was faster. Mine only tool a little over 2 hours with 4 failures. I would still like to know what the known issues were that were fixed in this build. Maybe Zac Bowden knows?

When they first started the program it took less than an hour and never failed.

kado897 said:

When they first started the program it took less than an hour and never failed.

Some interesting info here..

Microsoft delays major Windows 10 update over Blue Screen of Death issues - The Verge

The new build is available to Windows Insiders in the Fast Ring, and will be made available to Slow Ring and Release Preview shortly. Sources familiar with Microsoft’s plans tell The Verge that this build (version 17134) has now been marked as the final version of the next major update.

Microsoft has still not officially named this update, despite the company using the Spring Creators Update naming multiple times. It now appears Microsoft will choose “Windows 10 April 2018 Update” as the final name for Redstone 4. Microsoft watcher WalkingCat has discovered a video referencing this name, but the blocking bug delay could push the release of this update into May — further complicating the naming of this update.

Video: hear Microsftie say "Windows 10 April 2018 Update" pic.twitter.com/H4WPkCC3sA

@cereberus

Don't make this personal by making it sound like I don't test and report bugs, OK.

I DO use the latest builds released, and there are a lot of bugs to report, which I also do report. Only difference is that I don't install on physical hardware until I can verify that the most breaking bugs are fixed. I use Windows as it comes from MS, as much as possible to reveal issues that comes from MS itself.

Since Edge for Android(BETA) works like a charm, I assume the issues in Edge on Windows are in Windows itself and not in Edge. Right now I use that browser on all my devices 99.9% of the time and only use another browser to reveal possible site bugs rather than browser bugs.

Found out that System Recovery partition became OEM partitions in this build (anybody else?)

AndreTen said:

Found out that System Recovery partition became OEM partitions in this build (anybody else?)

I do not have an OEM Machine so no.

slicendice said:

@cereberus

Don't make this personal by making it sound like I don't test and report bugs, OK.

I DO use the latest builds released, and there are a lot of bugs to report, which I also do report. Only difference is that I don't install on physical hardware until I can verify that the most breaking bugs are fixed. I use Windows as it comes from MS, as much as possible to reveal issues that comes from MS itself.

Since Edge for Android(BETA) works like a charm, I assume the issues in Edge on Windows are in Windows itself and not in Edge. Right now I use that browser on all my devices 99.9% of the time and only use another browser to reveal possible site bugs rather than browser bugs.

The Hub as of now does not even show this build at all.

Wow! Just saw the notice now. Completely missed it yesterday. My Dell Venue Pro was already updated with no issues, just fired off the Surface Pro 3. Here's what diskmgmt says about the Boot/sys drive on that machine:

Indeed, what had been Recovery is now labeled OEM here as well.
Will report back if any issues pop up on my Surface. At 7% installing right now.
Interesting info/admissions in the Release blog/notes for ...134, too.
--Ed--

Josey Wales said:

The Hub as of now does not even show this build at all.

That is probably because most breaking things are already in previous builds.

If I find a bug, I continue to use my old or someone elses bug-report until the issue is fixed. If the bug returns after being already fixed, I open a new issue.