Sorry you keep having these unfortunate experiences with your phone & computer RedBar. However, most everyone has installed the latest Window's phone updates without issue.

The Lumia 950 XL, while a couple years old, is a great phone and should not of had a problem unless there wasn't enough memory or possibly an interrupted internet connection during download/installation. However, AFAIK there are safeguards against incomplete downloads with OS updates.

Have you spoken with your carrier? The update comes from them.

What really annoys me is the fact I selected later and then it decided to say GOODBYE, in capitals, and that's been it. So far this morning it's been running for over an hour with the MS logo intermittently going on and off therefore I assume it's trying to do something.

This is a ridiculous situation whereby an OS can simply go AWOL.

From now on when I'm travelling I am going to have to take my old faithful Nokia 3720 with me, that's never, ever let me down once.

And for those who say get an Android, a friend of mine has a state of the art smartphone that went down for 4 days and no one knew why, not even the manufacturer, it simply came back by itself, yeah, awesome technology that only works when it wants to.

Had you skipped an update previously? (Later, for example and then didn't get it done)

Reason why I ask, the next update will recognize that some files expected to be there aren't and will take the time to download and install those first before completing its task.

How fast this happens depends on your connection and account data plan.

It was completely up-to-date and always switched on and on wifi.

What puzzled me was that it was a Friday night.

I'm currently checking all my other Win 10 devices.

So far 2 hours and still churning along with the MS logo going on and off which has to be a sign of something. I'm fairly sure this is the first downtime for this phone and I'm lovin' using my old 1520, which by the way, runs Win 10 perfectly.

Checked 3 Lumia phones and an Acer laptop, all up-to-date, no issues, 31/2 hours and 950xl still no joy.

So, I gave it 7 hours, still stuck on the logo, I've done the power button/volume down together soft reset, nothing, I've taken the battery out for 15 mins put it back in and nothing, still the MS logo.

Anyone with any more suggestions? If these were a cheap phone, well I could maybe understand, but they ain't and this is putting me off using this OS altogether, I'm beginning not to trust Win 10 whatsoever.

I am not alone:

[answers.microsoft.com...]

FWIW Redbar

While looking for something entirely different I came across this page:

Windows Phone Recovery Tool for Windows 10 Technical Preview for Phones

[winsupersite.com ]

I immediately thought of your situation. Might be of some help - then again perhaps not.

That's the saviour IanCP:-)

I had completely forgotten about that until I went to the MS site I linked to above. For some reason it doesn't work the first time, it does everything however when coming to installing it fails however simply clicking on it again it installs correctly.

I see that there have already been 200+ views of this issue and I am guessing that they are all Windows Insider members since I don't think I have that enabled on other devices. I did not register for the Windows Insider programme this time! This seems to be a major fubar by MS.

FWIW fortunately I had everything backed-up but so far I have spent 6 1/2 hours rebuilding my phone since it takes it back to its original Win 10 state then all the updates have to be reinstalled but at least it works as it should now.

I think its terrific that MS has a Windows Phone Recovery Tool for things like this.

When my LG Android phone bricked last year (3 weeks past the one year warrantee) there was nothing I could do. I did back up most data to an external disk but like RedBar, I spent hours redoing all the settings on my new phone.

but at least it works as it should now.

I love happy endings.

There's some benefit in starting from scratch .... you will make different choices. At least you won't spend time trying apps and finding they weren't quite what you wanted since you probably know exactly what you want.

That's the saviour IanCP:-)

You just started my Sydney morning with happy bliss.

It's always nice to repay folks who have helped in the past.

Wow, wow, wow, wow ... an unscheduled release offically acknowledged by Microsoft!

The 16212 build problem is not model or platform specific, this was an unscheduled release of an internal build.

1,000+ views, how to recover, that's a lot of very angry insiders:

[answers.microsoft.com...]

Anyone for a demotion?

Anyone for a demotion?

As I had said earlier

While looking for something entirely different I came across this page:

I actually came across the above link when trying to unbrand a Nokia 6120C mobile phone for a family member. I have done this in the distant past with a firmware update.

The latest efforts are the "Hall of Horrors". Why? Mr. Microsoft took over Nokia, which became Microsoft Phones.

In typical Microsoft fashion they intentionally or otherwise messed up all the links to software updates for the old Nokia files. Updating firmware at the best of times can be a thrilling exercise frought with many dangers - mostly irreversible. That's from the experience of the update process being interrupted by a million to one power outage.

Armed with the latest, even old Nokia tools I get this [look at the second graphic down]

Nokia Software Recovery Tool update makes it (partially) functional again

"...As you may know, Microsoft closed down all Nokia websites including firmware repository earlier this year. This blackout rendered all Nokia firmware downloading softwares (like Navifirm, Nokia Suite, NDPM, Nokia Care Suite) useless. However the new NSRT update makes it clear that (fortunately) Microsoft has not deleted the Nokia firmware files altogether. Rather they have just shifted the files to their own servers. This shift resulted in change of firmware file URLs which can be accessed via new NSRT now..." - Not my ones though]

[digipassion.com ]

Grrrr... As you said "Anyone for a demotion?"

There are some back door methods, but these are even more dangerous - I even yesterday encountered a site redirect which aggressively tried to ransom my PC [true].

EDIT - Typos

I even yesterday encountered a site redirect which aggressively tried to ransom my PC [true].

Being the curious person that I am, I decided I would WhoIs the domain. Just Google the Registrant phone number:

phone <snip>

As they say - Far Out!

[edited by: engine at 7:58 am (utc) on Jun 6, 2017]
[edit reason] phone number obfuscated [/edit]

Leaving ransomeware in the dust [Task Manager/End Task killed that to death]

Back to Windows Phones formerly Nokia. Well I did unearth later version firmware files V7.20 versus V4.51. So far so good. Major obstacle overcome.

Fire up Phoenix, connect phone via USB, follow strict procedures, yes there is the firmware folder RM-243 - click "Refurbish"...

INSTANT BLUE SCREEN OF DEATH - Instant automatic restart - no questions asked - no choice at all.

OK maybe doing it with admin priv might make a difference - again more BSOD... Windows 10 Pro?

Several hours of cussing, fruitless research then lateral thinking about a 2007 phone etc. maybe it's a 32 bit versus 64 bit thingy - why not fire up an old Win XP Toshiba Notebook. Move data files, programs etc. over once I got Notebook going.

This time no BSOD - just a complaint an important data file couldn't be found. It's there in the proper folder, proper location, I can see it in "My Computer". C:\Program Files\Nokia\Phoenix\Products\RM-243

I leave it until today - this time meticulously checking every step of the way - then I noticed:

...\Nokia\Phoenix\Products\RM-243\RM-243

Transferring folders over, I had put a folder within a folder instead of just files. Careless mistake...

Ten minutes later - HAPPY DANCE - completely unbranded phone with updated software. Waiting on new SIM card in the mail.

All a matter of perseverance.

Good work IanCP