Installed running ok, Restore Health command fails because of Microsoft-Windows-EnterpriseGEdition.cat & Microsoft-Windows-EnterpriseGEdition.mum, not sure if CU will work...
@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
[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=""c_net.inf_amd64_f48947d0ff620b87"" /> <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
1. Server Desktop Experience is based on top of Client EnterpriseS which is maily composed in Microsoft-Windows-Server-Shell-Package. 2. The package structures are different between Client and Server Desktop Experience. Long in short. e.g. Microsoft-Windows-EnterpriseSEdition. An Edition. In Server? Microsoft-Windows-Server-Shell-Package. A package. The others are Server Roles and Features. EnterpriseS + Server Roles + Server Features = Server Desktop Experience