[SOLVED] Unable to Activate Server 2019 from Eval

Let me know if it's an OEM or RETAIL (MSDN) ISO. And unfortunately you can't use the evaluation version because it will not ask for the 25 digit product key during the first steps of the installation / in-place-upgrade.

And how many times the evaluation period is extended, the command slmgr -dlv will show the rearm count.

 
Still looking for a Disk, attached the slmgr cmd output
 

Attachments

  • Screenshot 2024-12-09 081458.webp
    Screenshot 2024-12-09 081458.webp
    29.4 KB · Views: 2
I can provide a link for the MSDN ISO (Build: 17763.107), but I'll have to upload it to a private source...
 
Thank you Maxstar, Truly appreciate all the effort and time you are giving me to try fix my issue.
 
I'm uploading the ISO now, and will send the download link for my PCloud drive in a private message when ready. Let's hope you can fix this install with this ISO + product key and in-place-upgrade. In the meantime please make a full backup / snapshot of the current state.
 
I've just sent the download link for the ISO, please try to perform an in-place-upgrade with your 25 digit license code during the installation process.
 
For anyone following this thread, I downloaded the ISO, mounted and attempted an in place upgrade. It hung up at 30% and never got further. After about 10 hours or so I restarted the VM to reverted any changes and Just for shits I ran the dism upgrade cmd again to see, it failed again.

Maxstar alerted me to the fact i could extend the evaluation by using the "slmgr" cmd. Prior to running cmd it had 2 days left.
dlv.webp
So now I'm not so panicked !
That said, @Maxstar Do you think there is anything left to try or is it a lost cause at this stage?
 
Hi

Glad to see you were able to extend the evaluation period. Please run the System File Checker first to see if it will complete.

Run the System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 
Hi Maxstar,
SFC cmd ran successfully. Attached CBS logfile as requested.
C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
 

Attachments

Run the following DISM command again and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 
C:\Windows\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.5830

Image Version: 10.0.17763.6532

[==========================100.0%==========================]
Error: 0x800f0954

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 

Attachments

Hi,

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

DISM cmd completed successfully.


C:\Windows\system32>DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.5830

Image Version: 10.0.17763.6532

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.


, Logs attached
 

Attachments

Please try the following DISM command again and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /Set-Edition:ServerStandard /ProductKey: XXXX-XXXX-XXXXX-XXXX-XXXX /AcceptEula
 
Deployment Image Servicing and Management tool
Version: 10.0.17763.5830

Image Version: 10.0.17763.6532

Starting to update components...
Starting to install product key...
Finished installing product key.

Removing package Microsoft-Windows-ServerStandardEvalEdition~31bf3856ad364e35~amd64~~10.0.17763.1
[==========================100.0%==========================]

Error: 14003

An error occurred while operating system components were being updated. The upgrade cannot proceed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 

Attachments

Please try to upgrade the license again with Process Monitor running.

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try to upgrade the license just like you have in the past.
3. Stop Process Monitor a minute after it fails, just to be sure everything is logged. You can simply do this by clicking the capture icon (CTRL +E) on the toolbar as shown below.

Process-Monitor.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer | Send Large Files Fast - Up To 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top