[GUIDE] [DISCUSSION] Windows Editions Reconstructions

Installed running ok, Restore Health command fails because of Microsoft-Windows-EnterpriseGEdition.cat & Microsoft-Windows-EnterpriseGEdition.mum, not sure if CU will work...

 

You need to login to view this posts content.

 

@xinso
https://forums.mydigitallife.net/th...struction-project.80939/page-451#post-1750606
https://forums.mydigitallife.net/th...ns-reconstructions.88605/page-54#post-1865135
https://forums.mydigitallife.net/th...struction-project.80939/page-451#post-1750612

 

Thanks. For the peach of my little brain, I had determined not to touch it.

 

You need to login to view this posts content.

 

[27913.1000]
Microsoft.WindowsAppRuntime.x64.1.4
Microsoft.WindowsAppRuntime.x64.1.5
Microsoft.WindowsAppRuntime.x64.1.6

 

How to calculate hash in manifest for inf_amd64_xxxxxxxxxxxxxxxx?

Code:

<registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverInfFiles\c_net.inf">
  <registryValue name="" valueType="REG_MULTI_SZ" value="&quot;c_net.inf_amd64_f48947d0ff620b87&quot;" />
  <registryValue name="Active" valueType="REG_SZ" value="c_net.inf_amd64_f48947d0ff620b87" />
  <securityDescriptor name="62791918C58049A69FA4D51EF72F68381DD90E4C" />
</registryKey>
<registryKey keyName="HKEY_LOCAL_MACHINE\SYSTEM\DriverDatabase\DriverPackages\c_net.inf_amd64_f48947d0ff620b87">

 

[Test if 27909.1000 would be compatible with 27913.1000]

Code:

C:\windows\system32>dism /english /logpath:Z:\1.log /image:K: /apply-unattend:Z:\WinSxS\1.xml

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.27909.1000

Applying package servicing unattend
[==========================100.0%==========================]
The operation completed successfully.

--->

Code:

C:\windows\system32>dism /english /image:K: /get-currentedition

Deployment Image Servicing and Management tool
Version: 10.0.19041.844

Image Version: 10.0.27913.1000

Current edition is:

Current Edition : Enterprise

The operation completed successfully.

C:\windows\system32>

 

So what's stopping us from copying Windows folder DLLs, INF files, etc., directly from build 20348.3932 (Server) into Client 20348.1? Can't we track which files in the Windows directory (System32, SysWOW64, etc.) get changed by the update? Couldn't we just replace those files, essentially updating every file in 20348.1 with the corresponding updated version from 20348.3932? In other words, performing a manual update by replacing all outdated files with the updated ones? Does this transform the client into a server, or is it actually a possible, just unorthodox, way of updating client version 20348.1 to 20348.3932

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

i know this is offtopc, but after lgpo use, how can i check that my pC doesnot srnding telemetry.

 

Can you try it and let us know ? - will not work. UBR will not match. This is not how windows works.

 

You need to login to view this posts content.

 

Add this and the corresponding client language files to easily get driver updates and program compatibility:
Microsoft-Windows-Client-Desktop-Required-Package
Microsoft-Windows-Client-Desktop-Required-WOW64-Package
Microsoft-Windows-Client-Features-Package
Microsoft-Windows-Client-Features-WOW64-Package
Microsoft-Windows-Common-RegulatedPackages-Package
Microsoft-Windows-Common-RegulatedPackages-WOW64-Package

As a bonus, this also adds full audio Bluetooth capability to Server 20348.

 

I prefer using it as ServerRdsh for both Client and Server 2-in-1 workstation.

 

Yes that's the best way for 20348 and 20349

It's the best operating system ever.

 

unfortunately quick assist doesn't work on server. serverrdsh (which xinso wrote about https://forums.mydigitallife.net/th...s-reconstructions.88605/page-124#post-1885884) would be great.

packages (desktop, features and regulated) are in .1 version.
for example on my surface laptop 7 (intel) touchpad doesn't work on 1904x builds unless .3031 update or above - audio needs at least .1503, so .3031 is enough for both

that is why gailium119 and zwl29017 custom client updates are worth to wait

20349 is azurestackhci only - does reconstruction script exist?

 

Well take the touchpad driver from the 3031

GUI must be added to 20349 - search the old reconstruction thread

 

input.inf points to hidclass, hidparse and hidusb. 1904x versions don't work with 20348