[Windows 10] Digital License (HWID) & KMS38™ Generation

[s1ave77]

The contents of this section are hidden

You have No permissionsSorry, where's the log?

[Skunk1966]

The contents of this section are hidden

You have No permissions
Attaching log didn't work but prisim just fixed that.
It's in my post now

[s1ave77]

RELEASE: v6.77

--expaded the log for better troubleshooting

[Skunk1966]

  HWID(1).log (Size: 997 bytes / Downloads: 1)
New log in Attachment

---

@s1ave77 I found out what the problem was.
I control updates with WUMT and had the update service stopped. Now I activated the service and LTSB is showing activated after running your tool again :-)

This tool is absolutely brilliant!

[s1ave77]

Ahh, that dreaded 'couldn't strat service error'. This implies some a service is set to disabled which is crucial. Had this on one VM.

Open Settings/Update & Security/Activation, it should show 'Can't contact Activation Server' (or similiar).

Check the Windows Services and dort them by status. Check for disabled ones, especially TCP and similiar related.

Use the troubleshooter till it is able to activate correctly. Make sure system is online.

[Skunk1966]

The contents of this section are hidden

You have No permissions
In this particular case the culprit was Windows Update Service which I disabled by using WUMT + wrapper script. After enabling the service everything went smooth and activation wasn't a problem anymore

Thanx for this wonderful tool!

[Skunk1966]

one more question;
the tool is AIO so does it mean that KMS solution is included in the tool or do we first have to activate Windows with KMS solution before applying the tool?
I'm asking because my LTSB was already activated with KMSpico

EDIT: I checked without KMS and it's activating just fine

I did get some reports from a friend who tested as well and he had to set Windows Update Service to automatic before activation was successful. Setting on manual Windows refused to activate.
I'm waiting for his logs but when I get them (probably tomorrow-->Friday) I'll send them to you so you can check the logs

EDIT 2: unfortunately he threw away the logs that could show what went wrong so it's not possible to find out what went wrong. I know he has uefi BIOS so maybe that's what made a difference

[s1ave77]

RELEASE v7.77

--implemented disabled WU handling.

[s1ave77]

RELEASE v7.99

v7.99 added last checks and some code cleanup

[l33tissw00t]

Well done @s1ave77