[ARCHIVED] Windows Editions Reconstruction Project

many thanks for everything:
1.- for listening
2.- to verify
3.- for contributing
4.- for keeping this thread friendly

ps: Can you indicate how you achieved Snipping of results?

 

You need to login to view this posts content.

 

What is the list of the more interesting* build numbers for each major version of Windows (including alpha, beta, ...) starting from 5.1 ?

(*) By interesting, I mean the ones with the candidate builds offering the more possibilities in terms of versatility for construction/reconstruction/unstaged/repair content packages/.... and availably in many flavours on Windows (client, server, winPE, Validation OS, Factory OS, ....)

 

Congratulations!

In follow-up two questions :
a) Coud it be converted back to ServerDatacenterCor ?
b) Could a fresh Windows 11 Professional amd64 be also converted to a ServerDatacenterCor ?

 

You need to login to view this posts content.

 

What did you do, you built 25398.1_ServerDatacenterCor_to_Client_amd64.7z with at least three errors, you claim these fixes are not needed, even when these files are added by stageSxS-principalis method for Pro, you claim you don't use these fixes, but you don't post how you fix, at the end of the day you built ServerDatacenterCor_to_Client_amd64.7z with errors, i try to help someone fix, you attack the working method without proof it is wrong.

P.S the Fixes are from C:\Windows\Logs\DISM\dism.log, NOT ME, how do i tell my computer it is wrong ???

 

You need to login to view this posts content.

 

Proof? #14105 did not do what you did.

 

No scripts needed, only commands and .logs when building for myself, i use yours scripts to see errors for myself, so i can help someone else fix them.

 

No one is blaming you, you are blaming me for what you build, because you don't like to be wrong...

 

Right.

Ps: I'm sorry if I've caused this problem.

 

Please test Professional en-us

 

You have caused NO problems, you asked for help and for the most part all you got was word games, i try to help using C:\Windows\Logs\DISM\dism.log, i get attacked by xinso.

 

You should be arguing your point with dism .logs NOT ME.
I will use what ever script is causing errors, if and when i am trying to help someone else.

 

This is what i have learned from all this, when using

Code:

Dism /Image:C:\mount /Cleanup-Image /RestoreHealth

just because there are no errors in "Command Prompt" screen doesn't mean there are no errors.


Tip: So after using

Code:

Dism /Image:C:\mount /Cleanup-Image /RestoreHealth

check C:\Windows\Logs\DISM\dism.log for the facts.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

SSU 25398.640
Microsoft-Windows-Container-Win3CtrRuntime-Payload-FOD-Package -> Deployment-F8C15055775C4BE150D6D78F9ED4AC4AFDB66D015E08B3276BD649554F619AD6
Other Edition Package -> Shared-0AE5C5555511179C5D0A440DA88E85192FA07375600983885944E8DF0E9C5320

 

You need to login to view this posts content.

 

Hello
for rebuilding and updating windows 25398.1.
I follow this forum, two opinions are better than one

//vn-z.vn/threads/windows-10-enterprises-g-non-official-project.39535/page-540