[GUIDE] [DISCUSSION] Windows Editions Reconstructions

The OneCore-Win3 package-26100.1742 requires a monumental amount of work. 29531.1000

 

You need to login to view this posts content.

 

It is not allowed. Learn to make it yourself with OP or member scripts.

 

You need to login to view this posts content.

 

[26100.2 Dev Preview]
26100.2 + 26100.1743 Baseline CU + 26100.XXXX Patchline CU + 26300 Enablement

 

What is the difference between 26100.1 and 26100.32230?

Microsoft-Windows-Server-Features-Package016~31bf3856ad364e35~amd64~~10.0.26100.32230


</update>
<update name="63896c80f38f66aad3625b4cae05d917">
<package integrate="hidden">
<assemblyIdentity name="Microsoft-Server-MonthlyBundle-26200-Package" version="10.0.26100.32230" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="0e568f3744c24c448f94104b940012c7">
<package integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-All-Server-Ge-Beta-Version-EKB-Package" version="10.0.26100.32230" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>
</update>
<update name="3437a08417ab5cfbe3160ddd78f6390b">
<package integrate="hidden">
<assemblyIdentity name="Microsoft-Windows-All-Server-Ge-Consolidated-Version-EKB-Package" version="10.0.26100.32230" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
</package>

 

upgrade from 19045.6456 serverrdsh to 22000.3260 also works on sl7 intel (without drivers, without internet)

unfortunately same 0x800f0923 with 22000.3260 serverdsh on sl7 intel with bigger system reserved partition, when try to enable hyperv

how to fix 22000.3260 microsoft-hyper-v-hypervisor-package on sl7 intel?

 

The serverstandard SKU 29531.1000 is larger than all other SKUs. If it is deleted, the OS will not boot. The solution is...

 

That's the difference, a good pair of glasses is recqyui lol

 

You need to login to view this posts content.

 

No, except for a severe rebuild.
The driver.inf file and Defender are in the Desktop Feature Pack client.

 

Code:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v3" manifestVersion="1.0" copyright="Copyright (c) Microsoft Corporation. All Rights Reserved.">
  <assemblyIdentity name="Windows-Defender-Server-Core-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
  <package identifier="Windows-Defender-Server-Core-Package" releaseType="Feature Pack">
    <parent integrate="delegate">
      <assemblyIdentity name="Microsoft-Windows-ServerCore-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    </parent>
    <update description="Microsoft Defender Antivirus helps protect your machine from malware." displayName="Microsoft Defender Antivirus" name="Windows-Defender">
      <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3">
        <ServerComponent Description="Windows Defender Antivirus helps protect your machine from malware." DisplayName="Windows Defender Antivirus" Id="1003" Type="Feature" UniqueName="Windows-Defender" />
      </mum2:customInformation>
      <selectable disposition="staged">
        <detectNone default="true" />
      </selectable>
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Windows-Defender-Server-Service-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
    <update name="Windows-Defender-Server-Service-WOW64-Package">
      <applicable disposition="detect">
        <detectUpdate>
          <update name="Windows-Defender" />
        </detectUpdate>
      </applicable>
      <package contained="false" integrate="hidden">
        <assemblyIdentity name="Windows-Defender-Server-Service-WOW64-Package" version="10.0.26100.1" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
      </package>
    </update>
  </package>
</assembly>

 

I'm gradually dismantling 29531.1000 towards a minimal OS and desktop version. Messages like the serverstandard SKU are part of the long process.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Enterprise G policy on windows 11 are partial you need extra setting because windows 11 have news features

 

You need to login to view this posts content.

 

upgrade from 19045 to 22000.3260 serverrdsh pl-pl on sl7 intel is the only way to avoid stuck at windows logo

how to fix stuck at windows logo at 22000.3260 pl-pl with hyperv-hypervisor on sl7 intel (0x800f0923)?
1904x pl-pl boots with hyperv on sl7 intel. why 22000 pl-pl doesn't?

 

My daily OS got stuck at 19044.3488. For what? For some driver which is Incompatible with "psfextract.py". I use it to extract packages.