Update:
Seems while error #8018830f has been fixed and it has confirmed by many of our readers now, the error 0x80188308 is still giving trouble to some of the users.
Thanks Brian for the screenshot!
Microsoft had earlier confirmed that they are working to fix these issues and since it has been confirmed by more than one of you, so we can assume it to be working for more of you.
Thanks everyone who tipped us!!