WP8.1 GDR1 - update downloaded couldn't be opened

[helyzy]

Guys, just a quick update: clearly something has happened, because today, after 3 days of random attempts the update was succesful. I 8-10x got the 8018830f error same as everyone else here, and did nothing extraordinary (no deleting files in order to make some free space, no soft or hard reset or such nonsense).
The problem was literally solved from one minute to the next: at 8:30pm local time I got the dreaded "8018830f", at 8:38pm I got a message like "the update is ready to be served" et cetera, et cetera.

I guess you just have to be patient.

 

[MilanMilan]

I tried three times, with the error, and now every time it says that phone is updated (but, it's not)! How to fix this ?

 

[MilanMilan]

I tried three times, with the error, and now every time it says that phone is updated (but, it's not)! How to fix this ?

I disabled Preview for developers, while trying something, sorry.

 

[Andre Coelho]

The issue has been fixed!!!! yay!!! Just got this from the MSFT forum thread.

Hello hitmanmcc,

A thread that you are following on Microsoft Community has received a reply from Eli A..
Title: Update 1 - Error 8018830F -> Update was downloaded but could not be opened

Reply
Hello Folks,
We have resolved this issue with the error 8018830F. You can now simply go to Phone Update and check for updates to install the latest version.
Thank you for the information to help us investigate this issue further.
Thank you again,
Eli A.

1 phone already updated and the other one nearly finished.

 

[ducmans]

Looks like Microsoft has fixed it. I have it another try and suddenly it works fine. Go give it a try.

 

[Big-M]

I have same problem,L925 ea,true to download 4 times.!☹
Sent from my RM-892_im_mea3_230 using Tapatalk

 

[Mochammad Reza]

So,how about 80188308 "the update couldn't complete"...i was tried 20 times....sadly
My device Samsung Ativ S

 

[Martynas Zlatkus]

IMPORTANT!!!!!!

I have Nokia Lumia 925 with wp8.1 DP + Cyan .. I wasn't able install GDR1 because of that error some of you are getting.. BUT NOW IM AT COGWHELLS!!! This what i did (NO HARD RESET!!):

Before checking for updates i turned mobile internet off, leaving just wi-fi..
When download of update completed and 'preparing to install 0%' showed up, i immediately turned off wi-fi, leaving my phone with no internet connection..
Then, for some reasons, 'preparing to install' part didnt threw an error and just continued..

GIVE IT A GO SOMEONE IT WORKED FOR ME

Never mind it was just a coincidence MS just fixed this problem Update your Lumias to GDR1

 

[MilanMilan]

It works now !

 

[IlkkaV]

It works now !

Indeed! Can't remember when I was this glad to see the rolling gears.

 

[LillWicke]

Yes, they have solved the problem.
The new update1 downloads and works like a charm.

 

[Noob1ee]

I'm still getting error 80188308.

 

[jcinoz]

Error 80188308 still on Lumia 920.

 

[P48dy]

I hard reset my Ativ S on O2 to get back all the space the system files were taking up. After a restore from back up the update installed and everything works fine. Apps installing now but Cortana and folders work well. Not sure if the reset was necessary but the restore from back up is pretty painless so why not give it a try.

 

[Mahmoud Hussein]

that crossed my mind too...but i won't hard reset until i'm sure

I have updated my 1020 and 1520 -both without cyan- successfully. and I have the same error on my 925 with Cyan. so I think it's probably has something to do with Lumia Cyan

 

[Toby Naude]

I tried 5 times and they all failed with the ***F error. I tried today and it worked perfectly. Lumia 925 with cyan.

 

[baja_2012]

Just to inform, I got it yesterday.
Universe is in equilibrium again.

 

[takthetank]

I'm still having the 80188306 error too.
Lumia 630 with battery at 100% and 3,16GB free space.

 

[Andrew Rossiter]

space is not an issue, have 11 gigs free...... get the damm error every time i try to update.....

 

[Andrew Rossiter]

still getting the same error in Australia.. (0x80188308) .. not fixed here... grrr