Announcing Windows 10 Insider Preview Build 15055 for PC and Mobile Insider

dencal said:

I find it difficult to understand the obsession members have regarding clean installs, thinking it helps M$ with their Insider development.

Since its inception I have stuck rigidly to updating as a principal, not once needing to create an ESD ISO.

Of course as it has for all Insiders, problems have arisen, my idea being try to solve them and report either successfully solved or not in Feedback.

Can't beleive, MS listened to my feedback about how Edge sort history entries.

It is now listed by time inside any selected period versus the name as it was before. Hope I didn't ruined anyone's habit.

dencal said:

I find it difficult to understand the obsession members have regarding clean installs, thinking it helps M$ with their Insider development.

Since its inception I have stuck rigidly to updating as a principal, not once needing to create an ESD ISO.

Of course as it has for all Insiders, problems have arisen, my idea being try to solve them and report either successfully solved or not in Feedback.

More often than not, those of us Insiders that push the envelope as far as we can (read: Install lots of different software to test *specifically* with IP builds) will eventually run into a problem that either continues to manifest itself across multiple build updates and / or hoses the system enough so that it is just as easy to clean install as it is to attempt to fix the problem.

The above coupled with the fact that clean installs are not that hard these days, coupled with the fact that more than a few of us actually make system images *post-install* means that we're back up and running with a very minute amount of downtime.

Sure, we could go back and install the original Window s10 release and then let it upgrade to the current IP build, but that was well over a year ago (coming up on 2, actually) and things could have changed since then. Since we expect to have problems, we also are prepared to handle them with things like full system images, installation .ISOs with pre-installed software, and other tools to make our lives that much easier.

And some of us live on the bleeding edge, such as myself - I run the IP build as my default OS - which, thankfully, is not a production level machine, but my own personal machine used for a slew of activities, including but not limited to work, personal business, and personal endeavors. I, personally, have always lived on the bleeding edge of most things - a full >50% of my installed software is categorized as ßeta software, which I make no qualms about using as it is my choice to do so. And, since I make that choice, I also make sure I am covered so that, in the event of catastrophic failure of some sort, I am able to quickly get my system back up and running. And then am able to jump right back in to my testing.

My backup system also runs IP builds, but other than the OS itself, I keep that machine clean, for those moments when I need to do something but am unable to on my main machine for whatever reason.

JLG.
I smile having just read your post, you think you are the only one really testing.

Your post suggests you are testing for your benefit, not I think as an Insider.

Not wishing to appear vain at least according to M$ and Feedback I must be doing something right.

Dracolord said:

Howdy So I am trying to use uup to iso and I can only find a professional_en_us.esd file and I am having issues. Is there a reason yall might know why I am not getting the traditional uup files?

f14tomcat said:

UUPtoISO seems broken again.....

Attachment 124504

fdegrove said:

Precisely. No way to build an ISO file.
Sloppy MS.

This is 10th UUP upgrade, 3rd that does not allow making ISO. I have nothing else to say, no tools, no workarounds other than getting ESD upgrade instead.

Edwin said:

Just under an hour to upgrade, everything seems normal.

- it's too quiet, I don't like it..

I'm completely in accord with JLG's post. I'm glad I seem to have induced M$ to fix one glaring error - the time sync problem. I use SuMO to keep all my software current and am using the Beta releases of FF and Chrome among other betas. Perform a system backup which includes both Windows 10 and Windows Server 2106 (I've decided not to fight with BCD and using BTBM to boot either Windows or openSUSE Tumbleweed). This means some extra boots to get to Windows Server 2016 but that is OK since I have 2 VMware WS 12.5.3 (latest release) Windows 10 VMs as well as 2 Virtualbox 5.16 (latest release) Windows 10 VMs. I autostart one VMware and one Virtualbox VM Using a Hyper-V VM in Windows 10 and I will autostart that after updating to build 15055. One openSUSE Tumbleweed I'm now running kernel 4.11 RC1 and can only compile Virtualbox 5.16. So this is my test system. On my HP server , the host is Windows Server 2016 essential and I have 1 VMware and 1 Virtualbox Windows 10 VM. Most of the VMs are activated. I've been beta testing PC software since the early '90's.

This build still has the watermark