The leaker of Win8 kms? Are you talking about that activation SDK or whatever a long time ago that the one website owner turned the guy in for stealing from MS? I don't remember the website owner's name or the leaker's name unfortunately. I think he was a black french guy or something. I remember how people went about actually working on the disassembly to actually make a working activator. Pre-8 originally it was a cracking group. Then in 8 I think mikmik38? and others worked on it. I just watched from the sidelines. I didn't do anything myself until 8.1 when we ran into the localhost ban. Then we had to get sneaky. It was actually pretty fun and it was one of my favorite times on MDL.
Before your (how many years?) absence there were people posting FUD (as i remember you calling it), seems you now are on your way there too. Stuff has changed since then.
Why even bring up RTM? Couldn't any build be worthy of RTM? For a new Operating System, the answer is NO. There has to be a final product to start from. It is technically possible to patch Windows Vista into an amazing operating system with an extra 6 gigabytes of patches so that the entire base operating system is replaced. MS has never done that. They have never shown any evidence that they have any intention of doing that. These refresh builds we get are to satisfy the end users who download images with all of the updates included. They are to put people like me out of work. And it worked. I stopped. It's what I wanted and we got it. But they're not RTM. They are not final products. They are not new builds. New builds include all of the security updates that the refresh build update code includes. The only reason MS doesn't constantly do new builds is because it resets the clock on hardware compatibility. They also include any possible kernel code modifications, system process code modification, procedural handling changes, etc. So they have to start from the beginning with testing hardware and having the hardware manufacturers develop proper drivers. If there were no hardware compatibility concerns, new builds would be superior in every single way.
There are very few times I ever addressed FUD. One was that FaiKee guy that Daz banned and I was kind of upset. I thought it was a bit extreme. I don't spread misinformation, Enth. I certainly don't spread fear uncertainty and doubt.
Wait wasn't canouna the guy who turned him in? I recognize the name. Didn't he run a website about win8 or something?
Just re-read what everyone is telling you is gonna happen and accept it. We're not in the Vista/7 era anymore.
Yeah...he also have a website where many users migrated from here...before he had his source jailed. :-/
And what is everyone telling me going to happen? That MS is going to release a bloated ISO with half of a 7gb iso full of cumulative update based on this 22000 build? Not going to happen, period.
Things get interesting when converting from .WIM to .ESD still violates the FAT32 file size limit. I am testing Windows 11 on a NUC11PHKi7C and the default drivers for Windows 11 are hugely out of date. If they address this when the first public build drops, the WIM/ESD file is going to be pretty gigantic.
If they delete the drivers for all the old hardware Windows 10 currently supports, that should free up some space. That would really suck, though, and make it difficult to even install Windows 11 on older systems.
I haven't been paying attention on the MS end of this problem. The ISO files have had wim files over 4gb for a while. I think the way they have been getting around this is by recommending people use esd files with their media creation tool. They could technically change the efi loader to allow exfat or ntfs loading at any time. I'm not entirely sure why they haven't.
Ryzen 7 has TPM 2 on the chip doesn't it? My Ryzen 5 does, no need for the extra TPM module. Just needs to be enabled in Bios.