@Mooniversal 20348.1 -> EnterpriseS Can you tell me, how do you make this? A step-by-step instruction would be nice.
for error: 000003ba Couldn't find the hash of component: Windows-ContainerOSPlus-EditionOnly-merged-Deployment, version 10.0.22000.1 you need to mount vhdx factorys os and assign partitions with diskpart
the missing file rename 1.txt amd64_microsoft-container..mersiveshell-config_31bf3856ad364e35_10.0.22000.1_none_148c8725ca081d38.manifest
Code: 2025-02-10 08:24:25, Info CSI 6d444c-56d8-11d5-882d-0080c847b195} name: [l:117]'Microsoft-Windows-Servicing-Full-merged-Package~31bf3856ad364e35~amd64~~10.0.22000.1.6a9f224c0a41a43e5742096214545f9d' ncdata: [l:0]'') thumbprint: [l:64 ml:65]'09c5640cc0266a2bf2ced4fad7748a8371fb39d90f7516b3301cb3cadd4c064c' (696) Pin: flags: 0 tlc: [Microsoft-Windows-Servicing-Core-Deployment, version 10.0.22000.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) ref: ( flgs: 00000000 guid: {d16d444c-56d8-11d5-882d-0080c847b195} name: [l:110]'Microsoft-Windows-Servicing-Core-Package~31bf3856ad364e35~amd64~~10.0.22000.1.f6fc440d056d4070a624760bad45c490' ncdata: [l:0]'') thumbprint: [l:64 ml:65]'58ee3398b5a9a72129030f1d3a4419d1a710cb1714ba1459c9d957bee359ed24' (697) Pin: flags: 0 tlc: [Microsoft-Windows-Servicing-Core-X86-Deployment, version 10.0.22000.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) ref: ( flgs: 00000000 guid: {d16d444c-56d8-11d5-882d-0080c847b195} name: [l:114]'Microsoft-Windows-Servicing-Core-X86-Package~31bf3856ad364e35~amd64~~10.0.22000.1.e23bad2c310d11d079b4e7de1b023e40' ncdata: [l:0]'') thumbprint: [l:64 ml:65]'876bf68477b8334964f667130d3e5ae7f160e4eb0832c417783c23f437184154' 2025-02-10 08:24:25, Info CBS FLOW: Enter Installation Stage: Closure Analysis, Current Operation Stage: Resolving 2025-02-10 08:24:29, Info CSI 00000273 Couldn't find the hash of component: Windows-ContainerOSPlus-EditionOnly-merged-Deployment, version 10.0.22000.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the catalog \??\X:\Windows\WinSxS\Catalogs\0773b2e681e4dc3f3aa778a28f0e24a9fbb2e8630ae8040f7ef11d75468f46b6.cat. 2025-02-10 08:24:29, Error CSI 00000274@2025/2/10:00:24:29.811 (F) onecore\base\wcp\componentstore\csd_winners.cpp(1683): Error 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] originated in function Windows::ComponentStore::Rtl::VerifyFileAgainstCatalog expression: (null)
Let me test and see. It works. Code: WIM XML Information: --------------------------- <WIM> <TOTALBYTES>3919243985</TOTALBYTES> <IMAGE INDEX="1"> <DIRCOUNT>20839</DIRCOUNT> <FILECOUNT>107419</FILECOUNT> <TOTALBYTES>16446228138</TOTALBYTES> <HARDLINKBYTES>7952476969</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01DB7B7D</HIGHPART> <LOWPART>0x569E250E</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01DB7B7D</HIGHPART> <LOWPART>0x70903C02</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <WINDOWS> <ARCH>9</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>ServerStandard</EDITIONID> <INSTALLATIONTYPE>Server</INSTALLATIONTYPE> <SERVICINGDATA> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> <GDRDUREVISION>0</GDRDUREVISION> <PKEYCONFIGVERSION>10.0.26100.1;2016-01-01T00:00:00Z</PKEYCONFIGVERSION> </SERVICINGDATA> <PRODUCTTYPE>ServerNT</PRODUCTTYPE> <PRODUCTSUITE>Enterprise</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>en-GB</LANGUAGE> <FALLBACK LANGUAGE="en-GB">en-US</FALLBACK> <DEFAULT>en-GB</DEFAULT> </LANGUAGES> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>26100</BUILD> <SPBUILD>1</SPBUILD> <SPLEVEL>0</SPLEVEL> <BRANCH>ge_release</BRANCH> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows Server 2025 SERVERSTANDARD</NAME> <DESCRIPTION>Windows Server 2025 SERVERSTANDARD</DESCRIPTION> <FLAGS>ServerStandard</FLAGS> <DISPLAYNAME>Windows Server 2025 Standard (Desktop Experience with Edge without Store)</DISPLAYNAME> <DISPLAYDESCRIPTION>26100.1 Windows Server 2025 Standard (Desktop Experience with Edge without Store)</DISPLAYDESCRIPTION> </IMAGE> </WIM> [Credits] Ace2
Delete C:\Windows\Logs\CBS\cbs.log Try to install wireless display. Upload the cbs.log for us to check.
You could try changing the edition to Server, then try installing optional features, then change edition back to client.
В списке такие только файлы Microsoft-Windows-WirelessDisplay-FOD-Package-amd64.cab Microsoft-Windows-WirelessDisplay-FOD-Package-amd64_bc08a9d9.cab Microsoft-Windows-WirelessDisplay-FOD-Package-amd64-en-us.cab Microsoft-Windows-WirelessDisplay-FOD-Package-amd64-en-us_11cb9aaf.cab Total volume 1MB This is clearly not enough for Wireless Display to work. On Win11, when installing Wireless Display, the download traffic is higher than 100 MB. Server does not support Wireless Display
Q: Is Server Desktop Experience' "WirelessNetworking" applicable to Client? It has more functions than Client one. A: No. Flashing away.
In client versions there is a standard Wireless, it is no different from the server "WirelessNetworking", made a separate component and the possibility of its removal if unnecessary. In general, in servers, the Wireless functions are very limited, WirelessDisplay and Mobile hotswap (WiFi hotspot) do not work If attach the client functions WirelessDisplay and Mobile hotswap to the server, that would be valuable.