Personally, I am 100% grateful for this correction, because I didn’t know and since I’ve heard the less accurate ragebait version dozens of times at this point I would have been confused, next time I have to spin up a Win11 image, why I couldn’t replicate the spike I’ve heard so much about. The fact that it’s tied to a particular UI component, one of many that machine provisioning scripts and playbooks commonly disable, means it would have remained a bothersome unresolved mystery to me forever if not for your comment. So thanks.
Oh it still spikes without the recommendations lmao at least my work laptop was because I, too, have all the bullshit registry entries to make Start Menu usable and resource monitor was showing 10% spikes on average each time I opened the start menu. Wild.
Personally, I am 100% grateful for this correction, because I didn’t know and since I’ve heard the less accurate ragebait version dozens of times at this point I would have been confused, next time I have to spin up a Win11 image, why I couldn’t replicate the spike I’ve heard so much about. The fact that it’s tied to a particular UI component, one of many that machine provisioning scripts and playbooks commonly disable, means it would have remained a bothersome unresolved mystery to me forever if not for your comment. So thanks.
Oh it still spikes without the recommendations lmao at least my work laptop was because I, too, have all the bullshit registry entries to make Start Menu usable and resource monitor was showing 10% spikes on average each time I opened the start menu. Wild.