[Q] kb3058163 causing Windows RT to loose activation

domboy

Senior Member
Jul 10, 2013
147
22
0
Has anyone else's Surface RT (or other RT device) installed kb3058163 and then lost it's activated state?? Supposedly this update (released this week) is supposed to fix such an issue, but on mine it seems to break something not broken to begin with. With this update installed it will not re-activate, saying my key is not valid. If I uninstall this update I can plug the key back into the activation wizard and it will activate (if it doesn't automatically activate).

I noticed this issue when I saw a "Windows RT Build 9200" watermark on the desktop above the clock, and investigated. Very odd.
 

domboy

Senior Member
Jul 10, 2013
147
22
0
With this update installed it will not re-activate, saying my key is not valid. Uninstall the update and I can re-activate. First time I manually re-activated it. The second time I installed and then uninstalled this update my Surface re-activated itself automatically once the offending update was gone.
 

mtullius8

New member
Aug 7, 2015
1
0
0
Haven't had much luck finding a solution. Looks like it may just be a bad update. Guess I'll have to block it.
THANK YOU! I've been looking for the solution to this for days. I had become convinced there was a file corruption affecting the authentication process or a bad bios. I considered trying to update to 8.1 or 10 or going to Ubuntu. Then I found this thread. I removed the offending update and VOILA! All is good.

Running Window 8 64 bit on a Samsung NP300E5C-AO
 

domboy

Senior Member
Jul 10, 2013
147
22
0
THANK YOU! I've been looking for the solution to this for days. I had become convinced there was a file corruption affecting the authentication process or a bad bios. I considered trying to update to 8.1 or 10 or going to Ubuntu. Then I found this thread. I removed the offending update and VOILA! All is good.

Running Window 8 64 bit on a Samsung NP300E5C-AO
You're quite welcome! Sorry you had trouble with it too, but I'm glad my posting about it helped somebody else. No offense, but I'm also kind of glad to hear it's not just me having this issue. ;)

Interesting to also learn that it's not just an RT or Surface issue.