New
#11
Sorry to reply to such an old thread, but this registry setting is still relevant.
Setting "AllowExperimentation" to 0 breaks the "Known Issue Rollback" (KIR) feature. I mean this as an FYI. I'm not taking a stance or making any claims or pronouncements here. Just pointing out something I think is worth being aware of.
In a nutshell, when the user updates its computer and installs monthly patches or other types of updates, Windows keeps the old code as a backup for an emergency. Known Issue Rollback works seamlessly and quietly, and it does not require any actions from the user side. It has already proved its effectiveness in a number of cases. Recently, Microsoft used KIR to fix performance issues in games after rolling out another monthly update. Still, Known Issue Rollback has one questionable disadvantage.
As Microsoft started using Known Issue Rollback more actively, users noticed that KIR depends on their privacy preferences. To be precise, it requires turning on a feature called Experimentation. Experimentation is a policy Microsoft uses to remotely change some settings in your computer. Some users consider this a privacy invasion and use registry tweaks or third-party tools to disable Windows Experimentation. When you turn off the AllowExperimentation key in Windows Registry, Known Issue Rollback stops working.
Disabling Experimentation in Windows 10 also breaks Known Issue Rollback
Paul,
charlotte_tang (MSFT CSG) in that TechNet thread said experimentation was just setting a feedback level.
But the setting's definition in MSDocs says it permits MS to make changes on the device.
These WinAero articles are consistent with that - they say that experimentation is linked to Known issue rollback [KIR] & that MS has used KIR to alter/remove some dodgy updates.
Disabling Experimentation breaks KIR - WinAero
Known Issue Rollback - WinAero
The active nature of this facility is also endorsed by Known Issue Rollback Helping you keep Windows devices protected and productive - Microsoft Tech Community
Denis