[ARCHIVED] Windows Editions Reconstruction Project

Have you ever seen discussion on following 10586 Server licenses?

Windows\System32\spp\tokens\addons

Code:

C:\windows\system32>dir /b /s Z:\addons
Z:\addons\APPXLOB-Client
Z:\addons\APPXLOB-Server
Z:\addons\OCUR

Z:\addons\APPXLOB-Client\APPXLOB-Client-ppdlic.xrm-ms
Z:\addons\APPXLOB-Client\APPXLOB-Client-Volume-MAK-1-pl-rtm.xrm-ms
Z:\addons\APPXLOB-Client\APPXLOB-Client-Volume-MAK-1-ul-oob-rtm.xrm-ms
Z:\addons\APPXLOB-Client\APPXLOB-Client-Volume-MAK-1-ul-phn-rtm.xrm-ms
Z:\addons\APPXLOB-Client\APPXLOB-Client-Volume-MAK-1-ul-store-rtm.xrm-ms

Z:\addons\APPXLOB-Server\APPXLOB-Server-ppdlic.xrm-ms
Z:\addons\APPXLOB-Server\APPXLOB-Server-Volume-MAK-1-pl.xrm-ms
Z:\addons\APPXLOB-Server\APPXLOB-Server-Volume-MAK-1-ul-oob.xrm-ms
Z:\addons\APPXLOB-Server\APPXLOB-Server-Volume-MAK-1-ul-phn.xrm-ms
Z:\addons\APPXLOB-Server\APPXLOB-Server-Volume-MAK-1-ul-store.xrm-ms

Z:\addons\OCUR\OCUR-ppdlic.xrm-ms
Z:\addons\OCUR\OCUR-Retail-1-pl-rtm.xrm-ms
Z:\addons\OCUR\OCUR-Retail-1-ul-oob-rtm.xrm-ms
Z:\addons\OCUR\OCUR-Retail-1-ul-phn-rtm.xrm-ms
Z:\addons\OCUR\OCUR-Retail-1-ul-store-rtm.xrm-ms

C:\windows\system32>

 

Frankly, NO

My TP4 server VM is still alive and kicking in 2022 (turned to hypercore)

 

Perhaps if you switch it to Hypercore, customize the thing you need and then you switch it again to Server Standard, nothing happens.

No shutdown, no nag screen, no watermark, you just loose the activation, and get the sku rearm = -1

TP4 was one of the best windows of its days.

 

I found that all you do is "Quick-Switch". It's really convenient.

 

Reconstruction=nice to learn

Quick Switch=practical (two minutes of time the first time, then 1 second to switch (almost) anything to (almost) anything else.

A combination of the two leads to even more possibilities.

 

Tested staging Windows 10 10540 with 10546 servicing stack

Code:

C:\Users\Administrator>dism /image:D:\1\mount /apply-unattend:D:\1\10540.xml /logpath:D:\1\mount\1.log

部署映像服务和管理工具
版本: 10.0.22000.652

映像版本: 10.0.10546.0

[==========================100.0%==========================]
操作成功完成。

错误: 5

关闭映像中正在服务的组件时出错。
请等待几分钟，然后再次尝试运行该命令。

可以在 D:\1\mount\1.log 上找到 DISM 日志文件

C:\Users\Administrator>dism /image:D:\1\mount /get-currentedition

部署映像服务和管理工具
版本: 10.0.22000.652

映像版本: 10.0.10546.0

以一种访问权限不允许的方式做了一个访问套接字的尝试。


Current Edition : Starter

操作成功完成。

C:\Users\Administrator>dism /image:D:\1\mount /get-packages

部署映像服务和管理工具
版本: 10.0.22000.652

映像版本: 10.0.10546.0

Packages listing:

Package Identity : Microsoft-Windows-DiagTrack-Internal-Package~31bf3856ad364e35~amd64~~10.0.10540.0
State : Install Pending
Release Type : Feature Pack
Install Time : 2022/9/12 11:24

Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.10540.0
State : Install Pending
Release Type : Foundation
Install Time : 2022/9/12 11:24

Package Identity : Microsoft-Windows-Prerelease-Client-Package~31bf3856ad364e35~amd64~~10.0.10540.0
State : Install Pending
Release Type : Feature Pack
Install Time : 2022/9/12 11:24

操作成功完成。

C:\Users\Administrator>

Still Install Pending. Why?

 

Test reconstructing standalone 10240.19360 Windows 10 Core with .NET4.8 amd64 en-US

Code:

For LCU to winre.wim and install.wim.
Manually: Yes.
Script: No. Why?

Code:

------------------------------------------------------------
Add LCU to Winre image
------------------------------------------------------------

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.10240.19291

Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~10240.19360.1.5
[==========================100.0%==========================]
An error occurred - Package_for_RollupFix Error: 0x800f0922

Error: 0x800f0922

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

------------------------------------------------------------
Reset Winre base
------------------------------------------------------------

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.10240.19291

[==========================100.0%==========================]

Error: 0x8000ffff

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

Press any key to continue . . .

 

Using fewer packages to test helps troubleshoot problems.

 

Using a separate script, will errors still occur?
On some versions, adding a new LCU to a WinRE / PE that has integrated LCU and runs cleanup will cause errors.

 

Oh. But it is 10240.16384 + LCU. By hand, OK, together with .NET48. (This is the very first time I use script for it.)

10240.16384 is really weird.

 

10240.19291? SafeOS Update?

 

Try adding LCU first.

 

I don't test them.

 

It's OK for 10240.19360 LCU. But I use to add SSU firstly.

Code:

    <installerAssembly name="Microsoft-Windows-ServicingStack" version="6.0.0.0" language="neutral" processorArchitecture="amd64" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" />

 

You need to login to view this posts content.

 

However, the kernel version of the image is 10240.19291, which can only be caused by LCU or SafeOS update.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.