[DISCUSSION] Windows 10 Final Build 19041>>>19045 (PC) [20H1>>>22H2 vb_release]

Windows 10 pro en-gb was installed earlier. I chose the same while installing. That's the one I always use.

 

You need to login to view this posts content.

 

Error: 0x803F7001 On a computer running Microsoft Windows non-core edition, run slui.exe 0x2a 0x803F7001 to display the error text.

 

MAS 1.4 check activation status says 0xC004F034 I looked it up:
The mentioned error code usually means that the user entered the wrong license key. However, Microsoft admitted that the problem is more often at Microsoft’s server’s end, which may get too overloaded after the release of updates and other Microsoft support products.
Therefore, if you cannot activate Windows due to the 0xC004F034 error, we would recommend postponing the activation for at least a couple of hours or the whole day.

 

So @Enthousiast was right afterall
the new 21H2 EP KB5003791 is now versioned 19041.1237 (up from 19041.1019)

that's actually the only difference, package content is not changed

 

Maybe you installed a different version, like factory was Home and installed Pro?

 

I've always used Pro - haven't used Home since 2009 (Vista).

 

Seems my activation is gone for good. Should I go for that MAS thing?

 

Yep, if you want HwID or KMS38.

 

You need to login to view this posts content.

 

At that time I had only used the option to check activation status. On a system with non-genuine Windows I'd have just run the activation without bothering you, but this laptop had genuine Windows and I wanted to see if recovery was possible from whatever error that caused it to lose activation. I still don't know for sure what happened. Anyway, now MAS did the job.

Thank you so much for jumping in and helping out with suggestions and tools to try. I really appreciate it.

 

Actually, by default, the DISM 10.0.19041.1019 Package Identity doesn't exist. By default, DISM does not use the mum2:customInformation substring to create a Package Identity for the EP. Instead, DISM uses the assemblyIdentity substrings.

To get the Package Identity list for Windows 10, open a command prompt window and run:
DISM /Online /Get-Packages /Format:Table

This is the relevant MUM entry for the 06/29/21 EP:
<assemblyIdentity name="Package_for_KB5003791" version="10.0.1.2" language="neutral" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" />

DISM parses the MUM entry and creates the following Package Identity:
Package_for_KB5003791~31bf3856ad364e35~amd64~~10.0.1.2 <---Valid

The following is not a DISM default Package Identity
10.0.19041.1019 <---Not Valid

The Package Identity for the new 09/24/21 EP is:
Package_for_KB5003791~31bf3856ad364e35~amd64~~19041.1237.1.3 <---Valid
10.0.19041.1237 <---Not Valid for this package