Issues uninstalling Windows Server 2012 R2 Key

Markferron

Trying to fix an issue with one of my Server 2012 R2 Enterprise servers. For some reason the key kicked itself out. Last time this happened I just open CMD with administrator and run slmgr.vbs /cpky and slmgr.vbs /upk and then manually reinstall the key. The /cpky command runs just fine but /upk gives me an "0x80070005 Access denied: the requested action requires elevated privileges" error. I've tried running this on local admin and domain admin accounts and sfc /scannow ran with no issues. Any suggestions?

ITivan80

@Markferron Have you tried rearming the original key using the following command on CMD slmgr.vbs -rearm. Please run CMD as administrator maybe that might help as well.

Markferron

@ITivan80 Hmm...nope didn't work. Still giving me the 0x80070005 Access denied error. Oh I forgot to mention that I was running cmd as administrator as well.

Dashrender

Try running a chkdsk on the system drive, who knows, there might be some corruption.

Grey

@Dashrender said in Issues uninstalling Windows Server 2012 R2 Key:

Try running a chkdsk on the system drive, who knows, there might be some corruption.

You mean sfc /scannow? Or DISM.exe /Online /Cleanup-image /Restorehealth?

@op Check your event logs for more information, and try running the commands above.

Dashrender

@Grey said in Issues uninstalling Windows Server 2012 R2 Key:

@Dashrender said in Issues uninstalling Windows Server 2012 R2 Key:

Try running a chkdsk on the system drive, who knows, there might be some corruption.

You mean sfc /scannow? Or DISM.exe /Online /Cleanup-image /Restorehealth?

@op Check your event logs for more information, and try running the commands above.

Nope, not what I meant... but those would be great additional tools to run.

Markferron

@Grey said in Issues uninstalling Windows Server 2012 R2 Key:

You mean sfc /scannow? Or DISM.exe /Online /Cleanup-image /Restorehealth?

@op Check your event logs for more information, and try running the commands above.

Ran both, so far nothing, but I will run chkdsk tonight to see if that fixes anything. So far I can't find anything in the logs but I'll keep looking.