[ARCHIVED] Windows Editions Reconstruction Project

You need to login to view this posts content.

 

.

 

You need to login to view this posts content.

 

Something wrong with 19042 as a whole, it increases setup duration considerably vs 2004. ChrEdge is to blame I guess and the idiots that packaged it.

 

Then it is even worse, 'cause I installed 20H2Enablement without ChrEdge.

 

You need to login to view this posts content.

 

Good. Keep a-goin'.

 

Lol... just realize that...
I'll playing again later.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

PS.
The replace.vbs is very convenient in changing string in a text.

Code:

Const ForReading = 1    
Const ForWriting = 2

strFileName = Wscript.Arguments(0)
strOldText = Wscript.Arguments(1)
strNewText = Wscript.Arguments(2)

Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objFile = objFSO.OpenTextFile(strFileName, ForReading)
strText = objFile.ReadAll
objFile.Close

strNewText = Replace(strText, strOldText, strNewText)
Set objFile = objFSO.OpenTextFile(strFileName, ForWriting)
objFile.Write strNewText  'WriteLine adds extra CR/LF
objFile.Close

[Usage]

Replace A with B

Code:

cscript replace.vbs *.* "A" "B"

or

Delete A

Code:

cscript replace.vbs *.* "A" ""

*.* = editable file (.txt, .mum, .xml...)

e.g.

Code:

%WinDIR%\system32\cscript //nologo Files\replace.vbs C:\1.txt "old" "new"

I have a pair of old shoes
-->
I have a pair of new shoes

 

Who will be the first to migrate LTSB updates to unsupported SAC editions?

 

Export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages to a reg file
Replace all CoreEdition with EnterpriseSEdition
Import the reg
Install updates
Mount Registry
Delete all items involving EnterpriseSEdition in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages

just using nsudo to do these

This is my assumption, and I haven't practiced it. Why use the outdated version?

 

A1: Why not have a go?

A2: Because my PC works fine with the old version. And some still use XP.

 

Because there are still millions of devices that cannot run Windows 10 properly above 1507, or above 1607, or above 1703, due to drivers.
And most people in the world do not have disposable income to buy new hardware, so they will run old devices until going out in flames.
Even companies engage in this practice, because of software and hardware interfaces dependency out of support / with defunct manufacturers.
I've seen plenty examples, and this in UK, money was not even the first reason, but the fear of losing the trusted old accounting software or marine route planner and then having to buy new overpriced stuff and learning new software with dumb ui and less functionality because that's the global trend..

 

tonight i saw the deskommder chef, comes with a program and no idea, is so stupid, says it would be same haha

 

You need to login to view this posts content.

 

Let's see how your assumption goes:

 

You need to login to view this posts content.

 

I guess that this method is applicable to all versions below 18362
for I don’t know much about PSFX patches
It is a good thing not to modify the patch package to achieve the goal