So you're doing both NTFS compression and the LZX also? I assume you mean you're booting the host from a VHDX also. That's an idea.
Yes because the modern LZX doesn't inherit the compressed status. (change a bit in a txt file and it becomes uncompressed. The ntfs compression mitigates that. With my way modified LXZ compressed becomes NTFS compressed, bigger than the original but not as big as the uncompressed one. Obviously once in some months I recompress the whole partition to recover what went lost (because updates temporary files, user profiles and so on. That's not an idea, that's the best thing that MS did in the past two decades, it made old school bacups, ISOs , setup.exe, and so on obsolete overnight. But people is so stuck in the past that didn't notice in 15 years
Windows Server 2025 will also enable Bitlocker when installing OS. Will it encrypt all disks without a user if you want to be able to choose as in 11 24h2?
Native vhdx and mbr partitions here as well, but Android enforces that since android 7 or so (if you don't use a custom rom and /or a patched kernel), so it's matter of time before MS start copying yet another idiotic Apple's idea.
I'm afraid doesn't work this way. Just like the last round the final Server will not be on the same build as the final LTSx. If you want a final Server 11 the only way yet is to use 25398, but that isn't a ready meal.
@abbodi1406 If you are right, usually you are, would be a very odd scheme. Where is the value in QC of releasing publicly builds past 26100, but keeping the final version behind a curtain? Maybe may memory is failing butI don't remember a previous windows release where they followed that path
this year build 26100 is for client Windows 11 24H2, client Windows 11 LTSC 24H2 (also called 2024 but it says 24H2 in About menu), Server 2025 and Azure Stack HCI 24H2 also Dev channel is 26120 (26100 + EP) Xbox should get build 26100 in august as well for example build 26100.553 is available as internal for both server editions: [Internal Corpnet Required] Windows Server 2025 (26100.553) [Internal Corpnet Required] Feature update to Azure Stack HCI, version 24H2 (26100.553) they didn't released 26100 ISO for both client and server builds and just moved on to the new canary updates available server editions for en-us lang: ServerDatacenterCore_en-us.esd ServerDatacenter_en-us.esd ServerStandardCore_en-us.esd ServerStandard_en-us.esd ServerTurbineCore_en-us.esd ServerTurbine_en-us.esd ServerAzureStackHCICor_en-us.esd
Ok. But while I understand the "how" part, I still miss the "why" In server 2022 they released the .1 build labeling it as "preview", giving the opportunity to guinea pigs to spot any evident last minute bug, then they released officially the 20348.169. Which was a good way to both please the early adopters, and to mark as release a fairly robust and bug free build. It made sense
is there notes about the updates in that channel like what needs fixing and what got fix wondering if it close to be ready
only filenames with file sizes and sha-1 checksums are available metadata can't be downloaded without their VPN as for the changelogs, I've never seen them build 26100.1 is pretty rough, I think they want to release some huge LCU first
In a sane developent cycle, supposedly, almost everything is fixed during the long phase before the final major build number. Roughness should be ironed out in latest major builds 26040, 26067 and so on, then the changes from last preview like 26085 to 26100 should be practically just the build number. In the way they are following, instead the major and minor build numbers are completely meaningless. At this point just forget release cycles, and make windows a Arch like full rolling release.
remember oem's and major enterprise already have for testing as they come first; us lurkers rely on leaks and hackers