[SOLVED] Unable to Activate Server 2019 from Eval
- Thread starter Tones
- Start date
Hi,
Step 1. Download
Acelogix RegBak (Portable) to create a backup of the registry.
Step 2. Download
SFCFix and save it to your desktop.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 3. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Step 1. Download
- Extract RegBak.zip and right-click regbak64.exe and select "Run as administrator".
- Click on the button New backup and choose the location where you want to save the backup.
- Optional: enter a description for this backup.
- Now click on the option "Click here to view details".
- Ensure the option Select hives not loaded by Windows is checked, to be sure the following items are included in the backup.
- Click Ok to save these settings and press Start to create the backup.
- When completed you will see the message: Finished succesfully.
Step 2. Download
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 SFCFixScript.txt and save it to your desktop.
- Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
- 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 3. 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 /RestoreHealthHi Followed instructions and attached log file. DISM 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.
I will await your further instructions before attempting the activation again.
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.
I will await your further instructions before attempting the activation again.
Hi,
Great, please run the following command again, if it fails post the latest CBS logs.
Great, please run the following command again, if it fails post the latest CBS logs.
Code:
DISM /online /Set-Edition:ServerStandard /ProductKey: XXXX-XXXX-XXXXX-XXXX-XXXX /AcceptEulaCrap, Failed again...attached new CBS
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: 14081
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
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: 14081
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
Here's the next fix.
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command again and post the result. If it fails attach a new copy of the CBS log.
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.
- 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 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 /AcceptEulaPlease attach the previous Cbs_Persist log as well.
Here's the next fix.
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command again and post the result. If it fails attach a new copy of the CBS log.
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.
- 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 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 /AcceptEulaHere's the next fix.
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command again and post the result. If it fails attach a new copy of the CBS log.
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.
- 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 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 /AcceptEulaHere's the next fix.
Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command again and post the result. If it fails attach a new copy of the CBS log.
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.
- 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 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 /AcceptEulaPlease upload a new copy of the COMPONENTS hive.
Upload your COMPONENTS hive.
Upload your COMPONENTS hive.
- Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
- Please copy this file to your desktop.
- Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
- Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
- If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
Hmm, it seems all the missing registry keys are restored! So please reboot the server first and try to upgrade to ServerStandard again and post the new CBS logs when it fails.
Unfortunately the same result, so please try to upgrade to ServerStandard 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.
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.
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.
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!