Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Windows 10 Enterprise Eval license expired directly after install #1508

Open
1njected opened this issue Mar 25, 2023 · 4 comments
Open
Assignees
Labels
Stale The item has been there for a while and not updated. Quite soon it will be closed.

Comments

@1njected
Copy link

Description

Windows 10 Enterprise Eval license is expired right after install. Tried removing the base image and recreating. Windows 10 Pro works as expected. If I setup a HyperV VM with Win10 Enterprise Eval manually, I get 30 day eval.

Steps to reproduce the issue

Download Windows 10 Enterprise ISO to ISOs folder:
19045.2006.220908-0225.22h2_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso

Run:
New-LabDefinition -Name Win10Ent -DefaultVirtualizationEngine HyperV
Add-LabMachineDefinition -Name WKST88 -Memory 1GB -OperatingSystem 'Windows 10 Enterprise Evaluation'
Install-Lab

Login - License is expired.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      5.1.22621.963
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.963
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

AutomatedLab Version

Name                      Version
----                      -------
AutomatedLab              5.47.7
AutomatedLab              5.47.0
AutomatedLab.Common       2.3.5
AutomatedLab.Recipe       5.47.7
AutomatedLab.Ships        5.47.7
AutomatedLabDefinition    5.47.7
AutomatedLabDefinition    5.47.0
AutomatedLabNotifications 5.47.7
AutomatedLabNotifications 5.47.0
AutomatedLabTest          5.47.7
AutomatedLabTest          5.47.0
AutomatedLabUnattended    5.47.7
AutomatedLabUnattended    5.47.0
AutomatedLabWorker        5.47.7
AutomatedLabWorker        5.47.0
@stale
Copy link

stale bot commented May 21, 2023

This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.

@stale stale bot added the Stale The item has been there for a while and not updated. Quite soon it will be closed. label May 21, 2023
@nyanhp
Copy link
Member

nyanhp commented Jun 26, 2023

I haven't seen that happen yet. I'll try downloading an eval ISO matching your description in order to recreate the issue. Out of curiosity, what happens if you do an invoke-labcommand {slmgr.vbs /rearm} ?

@nyanhp nyanhp self-assigned this Jun 26, 2023
@stale stale bot removed the Stale The item has been there for a while and not updated. Quite soon it will be closed. label Jun 26, 2023
@1njected
Copy link
Author

1njected commented Jun 27, 2023

Running Invoke-LabCommand does not return anything:

 Invoke-LabCommand -ComputerName WKST -ScriptBlock {slmgr.vbs /rearm}
23:08:58|00:18:25|00:00:00.000|     - Executing lab command activity: '<unnamed>' on machines 'WKST'
23:08:58|00:18:25|00:00:00.000|       - Waiting for completion
23:09:01|00:18:28|00:00:03.173|       - Activity done

If I run the command in an elevated prompt in the VM I get:

---------------------------
Windows Script Host
---------------------------
Command completed successfully.

Please restart the system for the changes to take effect.
---------------------------

But after restart the system still shows "Windows license is expired".

@stale
Copy link

stale bot commented Aug 12, 2023

This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.

@stale stale bot added the Stale The item has been there for a while and not updated. Quite soon it will be closed. label Aug 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stale The item has been there for a while and not updated. Quite soon it will be closed.
Projects
None yet
Development

No branches or pull requests

2 participants