[SOLVED] Windows Server 2022 Standard not installing KB5031364 with error 0x800f0905

[Gary R]

My colleague informs me that we've seen a number of cases with Server 2022 machines, where the activation key has produced the problem you're experiencing, so we think that by resetting and re-installing it, it might resolve things.

IMPORTANT

Before proceding further, please create a backup image, or snapshot, of your Server, that we can restore to should anything go awry. (Not that I'm particularly expecting it to, but always best to be cautious)


So, once you've created your backup, please do the following ....

You'll need to reactivate the license with your own 25 digit product key later, so to get it ...

• Open an elevated Command Prompt.
• Type or Copy/Paste in turn, the command below, hitting Enter after.

wmic path SoftwareLicensingService get OA3xOriginalProductKey

Next ...

• Open an elevated Command Prompt.
• Type or Copy/Paste in turn, each of the commands below, hitting Enter after each.

net stop sppsvc
ren %SystemRoot%\system32\spp\store\2.0\tokens.dat tokens.bkp
net start sppsvc
cscript.exe %SystemRoot%\system32\slmgr.vbs /rilc

This will re-install your licenses.


Next ...

• Open an elevated Command Prompt.
• Type or Copy/Paste in turn, each of the commands below, hitting Enter after each.

slmgr /ipk ABCDE FGHIJ KLMNO PQRST UVWXY
slmgr /ato

(Where ... ABCDE FGHIJ KLMNO PQRST UVWXY ... are replaced by your own 25 digit product key. )

Please note ... the key used cannot be a KMS generic key, as listed ... HERE

Please let me know if everything proceeded successfully.

 

[farazhkhan]

I opened elevated Command Prompt and used following command

wmic path SoftwareLicensingService get OA3xOriginalProductKey

It came back with blank rows for the key as follows



I think it is happening cause key stored in the BIOS settings in the hardware as described here

Just in case I went ahead and following the instructions which re-installed licenses

net stop sppsvc
ren %SystemRoot%\system32\spp\store\2.0\tokens.dat tokens.bkp
net start sppsvc
cscript.exe %SystemRoot%\system32\slmgr.vbs /rilc

But unfortunately, even after doing all this when I tried to update Windows I still see same 0x800f0905 error

I also tried to uninstall keys completely by following commands and rebooted the system

slmgr /upk
slmgr /cpky

But still same 0x800f0905 error on Windows update for KB5031364.

I'm not sure if this information will be of assistance, but during my search, I encountered an identical issue here where numerous other users have reported problems with Windows Server Standard edition 2022 for cumulative update. The update process gets stuck at around 21% during installation, then jumps to 100% for 1-2 minutes, and finally concludes with an error. If you refer to the last question on page 2 asked by SER71 on October 16, 2023, at 11:24 AM, please also note that the machine handles all updates except the monthly cumulative ones.

Also on same page 2 in reply to SER71 question, Daryl James mentioned

One thing to mention, this server was built with the Server 2022 Evaluation build and then converted to licensed Standard 2022 Server with a product key after the server was built. Could this be how the issue arises?

It's worth noting my server was also initially set up using the Server 2022 Evaluation build and was later converted to a licensed Standard 2022 Server. Could this conversion process be related to the issue I am experiencing?

 

[Gary R]

Sorry to be so late getting back to you. Again I did not get a notification that you'd replied.

Yes, as far as we can see, your problem seems to be one that is related to servers that are initially installed as Evaluation builds, which is why we tried resetting the Product Key.

I'm going to have to consult again with my colleagues, and see if we have any further ideas, because at this point I have to admit that personally I don't.

 

[Gary R]

Can you please tell me what method you used to "upgrade" your Server from the Evaluation version to a fully validated version.

For example .... Did you use a Personal Key, or an OEM license, or maybe perhaps a Microsoft Action Pack subscription.

 

[farazhkhan]

We converted the Evaluation version to the Standard edition via the command line using the following command

DISM /Online /Set-Edition:ServerStandard /ProductKey:xxxxx-xxxxx-xxxxx-xxxxx-xxxxx /AcceptEula

The product key used is an OEM key provided by Dell (the one that is physically printed on the machine itself).

Ultimately, it seems that the issue I encountered is related to the conversion from Evaluation to Standard. I suspect that Microsoft might have detected the key being used twice, or there might be some unusual activity triggering the block on Windows cumulative system updates which are critical to system.

FYI, After spending a considerable amount of time troubleshooting this issue, over the weekend, I had to gather all the data into a separate drive and reinstalled Windows Server 2022 Standard using the official ISO (not the evaluation version). I reached out to Dell, and they provided a link to download the official ISO. Fortunately, the process was smoother for me since the server in question wasn't a domain controller or assigned to any crucial roles. However, I can empathise with those encountering this issue on a critical server that cannot afford downtime.

Finally, I want to extend my thanks to you and your team for standing by with me throughout the process of resolving this issue on this fantastic forum. I truly appreciate all the efforts you've put in.

 

[Gary R]

Thanks for getting back to me . Glad to hear you've been able to resolve your problem, only wish there had been a simpler and more straightforward solution.

Yes, the problem does appear to be an issue with the transition from Evaluation to Standard with Server 2022 machines. We're seeing a few cases where this is the case, and unfortunately there doesn't appear to be just one straight forward reason, but a number of "variations on a theme" each requiring a different solution.

I appreciate you sticking with me whilst I tried to find a fix, as it has highlighted areas for us to explore further, and in time maybe that will help us help others more efficiently.

I'll mark this topic as resolved.