Forum Discussion
Upgrade Windows Server 2019 Evaluation Issue
- Dave,
So this command:
Dism /online /Set-Edition:ServerDataCenter /ProductKey:WMDGN-G9PQG-XVVXX-R3X43-63DFG /AcceptEula
is the same thing as downloading the Windows Server 2019 iso and running it on the computer.
I downloaded that iso, ran it, installed the Windows Server 2019 Datacenter (Desktop Experience) and kept files and apps.
The server went through the upgrade process.
I then used the slmgr /ipk and slmgr /ato command and everything was fine.
Thank you again for assisting me in finding the resolution.
Ok, well also note that Error: 14081 == The referenced assembly could not be found. So not a good start for this one. A repair install may sort it but time may be better spent standing up a new one, patch fully, activate and move on.
How did you ascertain
“The reference assembly could not be found”?
This is the first time I am seeing that, also, what does that mean exactly? Something important is missing? The DISM and CBS logs lead me down a path of trying to fix update components.
Glad to hear, you're welcome, not sure why your own reply is now marked as the answer though.
- Dave,
So this command:
Dism /online /Set-Edition:ServerDataCenter /ProductKey:WMDGN-G9PQG-XVVXX-R3X43-63DFG /AcceptEula
is the same thing as downloading the Windows Server 2019 iso and running it on the computer.
I downloaded that iso, ran it, installed the Windows Server 2019 Datacenter (Desktop Experience) and kept files and apps.
The server went through the upgrade process.
I then used the slmgr /ipk and slmgr /ato command and everything was fine.
Thank you again for assisting me in finding the resolution. Sounds good, please don't forget to close up the thread here by marking helpful replies.
I appreciate the help.
This was a 'project' that my boss gave to me because it stumped him.
He was kind of resigned to the rebuild but thought maybe an extra set of eyes might yield results.
I'll try the resolutions you suggested and see if anything works.
Thank you!
Most likely is a broken dontnet framework, you can try other things like installing windows updates or resetting windows update. Additional resources for Windows Update - Windows Client | Microsoft Learn and the repair install, then beyond that it may be time to clean install it.
