[GH-ISSUE #268] Failed HWID activation [Error 0x803F7001] #187

Closed
opened 2026-02-27 10:10:04 +03:00 by kerem · 20 comments
Owner

Originally created by @JulianGR on GitHub (Sep 29, 2023).
Original GitHub issue: https://github.com/massgravel/Microsoft-Activation-Scripts/issues/268

Hi,

Was just trying to activate latest Windows 10 LTSC freshly downloaded from https://massgrave.dev/windows_ltsc_links.html (es-es language) with latest MAS script and it fails. What I've tried:

  • Disabling Windows defender
  • Going through the Fix Licensing menu (it says succesful, see screenshot)

KMS38 works just fine. I'm opening this issue just in case HWID activation is a general problem.

Here is the error:
2023-09-29_16-42

Here is the Fix licensing menu: (no errors, after going through it still can't activate with HWID)
image
image

any hint? Keep it up with the fantastic work!

Originally created by @JulianGR on GitHub (Sep 29, 2023). Original GitHub issue: https://github.com/massgravel/Microsoft-Activation-Scripts/issues/268 Hi, Was just trying to activate latest Windows 10 LTSC freshly downloaded from https://massgrave.dev/windows_ltsc_links.html (es-es language) with latest MAS script and it fails. What I've tried: + Disabling Windows defender + Going through the Fix Licensing menu (it says succesful, see screenshot) KMS38 works just fine. I'm opening this issue just in case HWID activation is a general problem. Here is the error: ![2023-09-29_16-42](https://github.com/massgravel/Microsoft-Activation-Scripts/assets/53094530/0a19e0e0-db05-4c12-b341-79276fcb310b) Here is the Fix licensing menu: (no errors, after going through it still can't activate with HWID) ![image](https://github.com/massgravel/Microsoft-Activation-Scripts/assets/53094530/de469fa1-f71c-492c-b7cf-a023c5f6e5a4) ![image](https://github.com/massgravel/Microsoft-Activation-Scripts/assets/53094530/7261745b-ddf5-4c44-a503-260b913fa010) any hint? Keep it up with the fantastic work!
kerem closed this issue 2026-02-27 10:10:04 +03:00
Author
Owner

@EndlessFractal commented on GitHub (Sep 29, 2023):

Known issue.

https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade

Until a workaround is found, HWID activation will not work.

<!-- gh-comment-id:1741018469 --> @EndlessFractal commented on GitHub (Sep 29, 2023): Known issue. https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade Until a workaround is found, HWID activation will not work.
Author
Owner

@JulianGR commented on GitHub (Sep 29, 2023):

Allright, thanks for the quick response!

<!-- gh-comment-id:1741019937 --> @JulianGR commented on GitHub (Sep 29, 2023): Allright, thanks for the quick response!
Author
Owner

@ghost commented on GitHub (Sep 30, 2023):

just happened to me.

Known issue.

https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade

Until a workaround is found, HWID activation will not work.

kms38 it is then

<!-- gh-comment-id:1741687626 --> @ghost commented on GitHub (Sep 30, 2023): just happened to me. > Known issue. > > https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade > > Until a workaround is found, HWID activation will not work. kms38 it is then
Author
Owner

@Copy2Translator commented on GitHub (Sep 30, 2023):

I'm having this problem too.
20230930140707

<!-- gh-comment-id:1741691072 --> @Copy2Translator commented on GitHub (Sep 30, 2023): I'm having this problem too. ![20230930140707](https://github.com/massgravel/Microsoft-Activation-Scripts/assets/75414580/39cf2ff7-7c4c-48c6-ad6f-bb804ea4fb4e)
Author
Owner

@thecatontheceiling commented on GitHub (Sep 30, 2023):

I'm having this problem too.
20230930140707

we state on our website that HWID is not working right now. Microsoft patched it. Use KMS38 for now until we find a fix.

<!-- gh-comment-id:1741693585 --> @thecatontheceiling commented on GitHub (Sep 30, 2023): > I'm having this problem too. > ![20230930140707](https://github.com/massgravel/Microsoft-Activation-Scripts/assets/75414580/39cf2ff7-7c4c-48c6-ad6f-bb804ea4fb4e) > we state on our website that **HWID is not working right now. Microsoft patched it.** Use KMS38 for now until we find a fix.
Author
Owner

@hoang-himself commented on GitHub (Sep 30, 2023):

I just downloaded stock Windows 10 and 11 ISOs from Microsoft's website and installed the Pro edition in Hyper-V, and I also get error code 0x803F7001. Is this the same as https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade?

image

image

<!-- gh-comment-id:1741724141 --> @hoang-himself commented on GitHub (Sep 30, 2023): I just downloaded stock Windows 10 and 11 ISOs from Microsoft's website and installed the **Pro** edition in Hyper-V, and I also get error code 0x803F7001. Is this the same as [https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade](https://devicepartner.microsoft.com/en-us/communications/comm-windows-ends-installation-path-for-free-windows-7-8-upgrade)? ![image](https://github.com/massgravel/Microsoft-Activation-Scripts/assets/10150902/f39b4d2c-0a87-4036-8a22-b781371ade91) ![image](https://github.com/massgravel/Microsoft-Activation-Scripts/assets/10150902/971d3b9f-c7e5-418e-970f-cc3229327a81)
Author
Owner

@ghost commented on GitHub (Sep 30, 2023):

guys please crop the images (or even better don't send them at all) so that the thread doesn't get cluttered

<!-- gh-comment-id:1741728265 --> @ghost commented on GitHub (Sep 30, 2023): guys please crop the images (or even better don't send them at all) so that the thread doesn't get cluttered
Author
Owner

@thecatontheceiling commented on GitHub (Sep 30, 2023):

I'm having this problem too.
20230930140707

we state on our website that HWID is not working right now. Microsoft patched it. Use KMS38 for now until we find a fix.

<!-- gh-comment-id:1741818749 --> @thecatontheceiling commented on GitHub (Sep 30, 2023): > > I'm having this problem too. > > ![20230930140707](https://github.com/massgravel/Microsoft-Activation-Scripts/assets/75414580/39cf2ff7-7c4c-48c6-ad6f-bb804ea4fb4e) > > > > we state on our website that **HWID is not working right now. Microsoft patched it.** Use KMS38 for now until we find a fix.
Author
Owner

@thecatontheceiling commented on GitHub (Sep 30, 2023):

it's patched. patched

it does not work anymore.

stop trying. they know it doesn't work

<!-- gh-comment-id:1741818813 --> @thecatontheceiling commented on GitHub (Sep 30, 2023): it's patched. **patched** it does **not** work anymore. **stop** trying. they know it doesn't work
Author
Owner

@GTE2232 commented on GitHub (Sep 30, 2023):

I think your Windows 10 edition is old and it is not updated 19044.3448.
I think the old version of MAS will work in case you do not want to update.(check the changelog also)
(try separate file version if aio does not work)

<!-- gh-comment-id:1741848286 --> @GTE2232 commented on GitHub (Sep 30, 2023): I think your Windows 10 edition is old and it is not updated 19044.3448. I think the old version of MAS will work in case you do not want to update.(check the changelog also) (try separate file version if aio does not work)
Author
Owner

@onlyspxctre commented on GitHub (Sep 30, 2023):

Is there hope for HWID Activation in the future, or will it just not be possible anymore?

<!-- gh-comment-id:1741885664 --> @onlyspxctre commented on GitHub (Sep 30, 2023): Is there hope for HWID Activation in the future, or will it just not be possible anymore?
Author
Owner

@ghost commented on GitHub (Oct 1, 2023):

Is there hope for HWID Activation in the future, or will it just not be possible anymore?

worst case scenario is doing a kms every 180 days after 2038 lol. it's fine.

<!-- gh-comment-id:1742073172 --> @ghost commented on GitHub (Oct 1, 2023): > Is there hope for HWID Activation in the future, or will it just not be possible anymore? worst case scenario is doing a kms every 180 days after 2038 lol. it's fine.
Author
Owner

@thecatontheceiling commented on GitHub (Oct 1, 2023):

Is there hope for HWID Activation in the future, or will it just not be possible anymore?

worst case scenario is doing a kms every 180 days after 2038 lol. it's fine.

let's not rule out kms38 being patched at some point, I do not expect it to actually work until 2038

<!-- gh-comment-id:1742074657 --> @thecatontheceiling commented on GitHub (Oct 1, 2023): > > Is there hope for HWID Activation in the future, or will it just not be possible anymore? > > worst case scenario is doing a kms every 180 days after 2038 lol. it's fine. let's not rule out kms38 being patched at some point, I do not expect it to actually work until 2038
Author
Owner

@ghost commented on GitHub (Oct 1, 2023):

Is there hope for HWID Activation in the future, or will it just not be possible anymore?

worst case scenario is doing a kms every 180 days after 2038 lol. it's fine.

let's not rule out kms38 being patched at some point, I do not expect it to actually work until 2038

then lets hope react os gets 1.0.0 before that happens

provided no other crack is made during that period, of course

<!-- gh-comment-id:1742075553 --> @ghost commented on GitHub (Oct 1, 2023): > > > Is there hope for HWID Activation in the future, or will it just not be possible anymore? > > > > > > worst case scenario is doing a kms every 180 days after 2038 lol. it's fine. > > let's not rule out kms38 being patched at some point, I do not expect it to actually work until 2038 then lets hope react os gets 1.0.0 before that happens provided no other crack is made during that period, of course
Author
Owner

@griffster94 commented on GitHub (Oct 1, 2023):

I think the fact that they’re starting to patch this stuff is a shore sign that it’s coming that you soon won’t be able to crack windows. I mean all they have to do is remove the KMS abilities and make all activations go through Microsoft. That would probably do it. It makes sense if they did that because then they would have complete and under control over all licenses, including Company ones.

<!-- gh-comment-id:1742084831 --> @griffster94 commented on GitHub (Oct 1, 2023): I think the fact that they’re starting to patch this stuff is a shore sign that it’s coming that you soon won’t be able to crack windows. I mean all they have to do is remove the KMS abilities and make all activations go through Microsoft. That would probably do it. It makes sense if they did that because then they would have complete and under control over all licenses, including Company ones.
Author
Owner

@ghost commented on GitHub (Oct 1, 2023):

I think the fact that they’re starting to patch this stuff is a shore sign that it’s coming that you soon won’t be able to crack windows. I mean all they have to do is remove the KMS abilities and make all activations go through Microsoft. That would probably do it. It makes sense if they did that because then they would have complete and under control over all licenses, including Company ones.

they'd have to somehow port all the billions of licenses to this new method and try to guess the ones that are cracked. that would also render millions if not billions of windows users without a license, mostly in the 3rd world.

<!-- gh-comment-id:1742124466 --> @ghost commented on GitHub (Oct 1, 2023): > I think the fact that they’re starting to patch this stuff is a shore sign that it’s coming that you soon won’t be able to crack windows. I mean all they have to do is remove the KMS abilities and make all activations go through Microsoft. That would probably do it. It makes sense if they did that because then they would have complete and under control over all licenses, including Company ones. they'd have to somehow port all the billions of licenses to this new method and try to guess the ones that are cracked. that would also render millions if not billions of windows users without a license, mostly in the 3rd world.
Author
Owner

@griffster94 commented on GitHub (Oct 1, 2023):

I agree. But why change the setting with Windows digital activation that has been working for many years. They had already changed it so it was hard to upgrade from Windows 7 or Windows 8.1. Both operating systems had been discontinued for ages. So why change that setting now. it seems to me like for many years they haven’t cared, but CARE now. So I have a feeling that it’s coming. Sent from my iPhoneOn 2 Oct 2023, at 3:02 am, cyberhardt @.***> wrote:

I think the fact that they’re starting to patch this stuff is a shore sign that it’s coming that you soon won’t be able to crack windows. I mean all they have to do is remove the KMS abilities and make all activations go through Microsoft. That would probably do it. It makes sense if they did that because then they would have complete and under control over all licenses, including Company ones.

wouldn't that invalidate billions of licenses? they'd have to somehow port all the licenses to this new method and try to guess the ones that are cracked. that would also render millions if not billions of windows users without a license, mostly in the 3rd world.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

<!-- gh-comment-id:1742182065 --> @griffster94 commented on GitHub (Oct 1, 2023): I agree. But why change the setting with Windows digital activation that has been working for many years. They had already changed it so it was hard to upgrade from Windows 7 or Windows 8.1. Both operating systems had been discontinued for ages. So why change that setting now. it seems to me like for many years they haven’t cared, but CARE now. So I have a feeling that it’s coming. Sent from my iPhoneOn 2 Oct 2023, at 3:02 am, cyberhardt ***@***.***> wrote: I think the fact that they’re starting to patch this stuff is a shore sign that it’s coming that you soon won’t be able to crack windows. I mean all they have to do is remove the KMS abilities and make all activations go through Microsoft. That would probably do it. It makes sense if they did that because then they would have complete and under control over all licenses, including Company ones. wouldn't that invalidate billions of licenses? they'd have to somehow port all the licenses to this new method and try to guess the ones that are cracked. that would also render millions if not billions of windows users without a license, mostly in the 3rd world. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
Author
Owner

@ghost commented on GitHub (Oct 2, 2023):

if only LTSC licenses had a reasonable price.

<!-- gh-comment-id:1742270906 --> @ghost commented on GitHub (Oct 2, 2023): if only LTSC licenses had a reasonable price.
Author
Owner

@yotoprules commented on GitHub (Oct 3, 2023):

HWID is now working again.

<!-- gh-comment-id:1745724296 --> @yotoprules commented on GitHub (Oct 3, 2023): HWID is now working again.
Author
Owner

@epman100 commented on GitHub (Oct 5, 2023):

HWID is now working again.

only working with a new method. the "old" method of hwid no longer works

<!-- gh-comment-id:1749389902 --> @epman100 commented on GitHub (Oct 5, 2023): > HWID is now working again. only working with a new method. the "old" method of hwid no longer works
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Microsoft-Activation-Scripts#187
No description provided.