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

Hi,

I don't really care about the ISOs themselves, it's about testing and feedback really.
They enroll us for help but cut us off.

Cheers, *Wink

 

I think they want you to clean install using a released .ISO which is readily available from Microsoft, just a few builds old.

 

I think that after all the problems MS have had with users installing updates it's a priority for them to get the update structure correct. Disregarding all of us here who like to do clean installs most of the users will be updating. Keep the masses happy and MS life will be a lot easier. The insiders will be looked after later *Smile

 

Hi,

You're way too smart not to see the flaw in your own logic.

Cheers, *Wink

 

Agreed.....will be interesting and exciting to see...when and if it come to fruition the way I think it may. Personally I liked it just the way it was.

 

And, the update is done. Holy friggin cow, it really is done already.

 

- still can't make Edge work in Continuum..
- I'm just getting bored, now...*Sleepy

 

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.

 

*Ditto

 

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.

*Thumbs

 

This build is not playing nice with my hardware. It is VERY, VERY hard to wake up. It takes several minutes to wake up each time.

 

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.

 

Just under an hour to upgrade, everything seems normal.

 

Let it do the update while my wife and I went out to supper. Was doing the restart when we left. Got home and windows was up on my second monitor, first monitor not available, and my gpu drivers not reading any gpu's. No Nvidia control panel. First time that ever happened.

The gpu drivers show in the programs and features tab in the CP but for all practical purposed they are not there. Will reinstall gpu drivers and see what is going on. Weird.