New Windows 10 Insider Preview Slow Build 18342.8 (19H1) - Feb. 27 Insider

slicendice said:

Alrighty! Upgraded with no issues. Have not yet found anything out of the ordinary to report. Maybe I should install ALL Windows features and see what breaks?

The mkv issue seems to be fixed.

kado897 said:

The mkv issue seems to be fixed.

That's good to hear. That bug is really an odd one, that makes no sense in the first place.

slicendice said:

That's good to hear. That bug is really an odd one, that makes no sense in the first place.

Looks like it was a codec issue. They are specific to container type.

Took the normal 3 hrs to install'

Did notice that on the settings page it lost My Phone, still got rewards and Updates.
Still no big loss havnt got a phone linked to it anyway

Roy

Didn't see this till I quit for the day yesterday. This morning, the initial download and install were already complete, and I saw the restart message in Windows Update. The X220 Tablet is now in the post-GUI update phase ("Working on updates") at 27% complete. Hopeful all will complete without issue. Should issues present, I will post a follow-up here.
Best wishes & fingers crossed,
--Ed--

24c said:

Wasn't it mentioned somewhere that once you went to Skippy, you could not return to fast?

I don't think so, 24c. When Skip Ahead was first announced, I signed up for it. There weren't many Builds coming through, so I opted out. I was told at that time if I opted out, I couldn't get back in. That may be what you're thinking about . . .

Fast forward to the current Skippy; I signed up again and tried to stick. I had so many GSODs on the next to last two Builds, I was forced to go back to 18305 and was put back on the Slow, then the Fast Ring. I was given an ISO, reinstalled the latest Skippy and it still wouldn't let me go back to Skippy, although it was a selection in Windows Insider Program in Update & Security.

Although I don't normally use these types of workarounds, I'm a legitimate Skippy participant, and was "thrown out" through no fault of my own and couldn't get back into Skippy, so I used Shawn's workaround. I'm back in so far . . .