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

WMIC alternatives #465

Open
TK50P opened this issue Jun 5, 2024 · 9 comments
Open

WMIC alternatives #465

TK50P opened this issue Jun 5, 2024 · 9 comments

Comments

@TK50P
Copy link

TK50P commented Jun 5, 2024

Screenshot 2024-06-05 161253
Is there a way?
OS Version is Windows 11 24H2, 26100.712

@thecatontheceiling
Copy link

Just use HWID activator

@WindowsAddict
Copy link
Member

@TK50P
26100.712 update removed wmic.exe from the system. You can enable it back from the optional features or by using the below command as admin

DISM /Online /English /Add-Capability /CapabilityName:WMIC~~~~

You can use the check activation status VBS option in the extras section as an alternative.
I'll update MAS soon accordingly.

@TK50P
Copy link
Author

TK50P commented Jun 5, 2024

I already know it, now I fixed it.
image

@TK50P
Copy link
Author

TK50P commented Jun 5, 2024

Just use HWID activator

I need to run sysprep and needs to use KMS. because SetupComplete.cmd doesn't work with OEM keys (which HWID Activation uses OEM Activation).

@WindowsAddict
Copy link
Member

Just use HWID activator

I need to run sysprep and needs to use KMS. because SetupComplete.cmd doesn't work with OEM keys (which HWID Activation uses OEM Activation).

You got that wrong, key in the script doesn't matter for SetupComplete.cmd

@TK50P
Copy link
Author

TK50P commented Jun 5, 2024

What I wanted to say:

  1. I used HWID activation to activate permanently.
  2. I wan Sysprep to capture image.
  3. I used Dism to integrate SetupComplete.cmd
    Note: the script contained additional software
  4. I installed it with customized windows and it stuck at "Just a Moment......"
  5. I thought HWID Activation uses OEM, which it caused it
    image

@WindowsAddict
Copy link
Member

That warning is for those editions that have OEM keys installed by default and don't have any other license type.
The key in question here is the key that is installed by default, not the key in the script.

@WindowsAddict
Copy link
Member

HWID activation didn't cause that.

@TK50P
Copy link
Author

TK50P commented Jun 5, 2024

I think it's build issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants