Sounds shady to me. It's sitting there "dormant" until you perform a future update that "unlocks it" / "enables it". aka, "Enablement Package".
DOH! Thanks you LTSC-Ten! You're absolutely right! Didjoo ever figure out what's slowing down the Chrome launch? I'm sorry I was referring to this post -- as this is doable with UUP Dump, I thought there should be a way with Slimdown10 as well but I don't actually know how to use a "ConvertConfig.ini" with UUP Dump, and UUP Dump created ISO often raise heck with Slimdown10 and other slop removers, and even has issues all its own -- so I've just been using MSDN official ISOs only...
It's not Chrome. Firefox and a dozen different forks of both Firefox and Chrome all do it also! It's only the first launch after reboot or the first launch after resume from hibernate. And only on one of my computers (Dell XPS 8700). Does it in XP x64. Does it in 2015, 2016, 2019, and 21H2 versions of Win10. Does it in 24H2 Win11. The only thing it does NOT do that on is SINGLE-PROCESS browsers which ain't worth sh#t to keep around despite solving that first launch.
When using uup-converter-wimlib to create the image, the SkipWinRE=1 option will not add WinRE.wim to the image. In the Slimdown10 script, there is an option to remove WinRE.wim from an already created image, which will achieve the same result.
I didn't click it. I always out of habit look at the URL before ever clicking any links. Can we classify that as a "phishing attack", an attempt to get folks to visit that website under false pretense?
SD10_Renewed_1.74 Both scripts (Custom and Default) include this option for whether or not to remove WinRE.wim.
I think BetaTesta will be pretty pleased too! Don't know if he's fallen in love with Slimdown10 yet or not, but this might get him there as he asked about this here a while ago... Well that's... Interesting... In your post here, on the Windows 10 forum (which is probably why you only got one reply), it was all about Chrome, and nothing else, in fact you were very emphatic that no one should even consider talking to about any other browser... I think your only reply there has the most likely paths to finding out why that's happening... Two people I know with a more resource constrained version of the Dell 8700 (half the RAM) don't see anything like this happening with any spin or fork of Chrome, Geko, Goanna, LibWeb engine browsers...
Post #2 cites FIrefox, in bold, in red. It's only on that one machine. I cannot even replicate the behavior on my other DOZEN machines. Just going to have to be one of those "it is what it is" things.