Known Issue Rollback: Helping you keep Windows devices protected and productive

Published Mar 02 2021 08:00 AM 129K Views
Microsoft

Today I'm sharing details about Known Issue Rollback (KIR), a new capability that can quickly return an impacted device back to productive use if an issue arises during a Windows update. In this blog, my engineering partner, Vatsan Madhavan, and I will walk you through this new capability.

In today’s digital world, we you know you rely on trustworthy systems and services to stay ahead of potential security threats to your enterprise environments. At the same time, you strive to sustain the productivity of your work forces. We know you need both: security and productivity.

The Windows Servicing & Delivery team works to help keep Microsoft customers protected and productive by continuously building and delivering updates to the intelligent cloud and intelligent edge. Over the past year, we have been working on improvements that help you ensure uninterrupted productivity even when rolling out critical updates to prevent or address potential issues.

Introducing Known Issue Rollback

Known Issue Rollback is an important Windows servicing improvement to support non-security bug fixes, enabling us to quickly revert a single, targeted fix to a previously released behavior if a critical regression is discovered.

Built in direct response to your feedback, the pieces that make Known Issue Rollback work came together in a functionally complete system beginning in Windows 10, version 2004. Every month, we release monthly updates with many of quality changes “contained” using the Known Issue Rollback capability.

While Known Issue Rollback was originally designed for user-mode processes, we have made phased improvements over the last year to the OS kernel and the boot loader to support this capability in kernel mode. Some versions of Windows 10 prior to version 2004, for example versions 1909 and 1809, have partial support for Known Issue Rollback built into the OS and we leverage that support whenever possible when shipping updates for those versions.

At the code level

When Windows developers code a non-security bug-fix, they keep the old code intact and add the fix.

Eric_Vernon_1-1614669786001.png

The Known Issue Rollback infrastructure in the OS provides developers with a method that evaluates a policy to determine the execution path. This policy tells the OS whether a fix should remain enabled or not. If the policy states that the fix is enabled, then the new code runs; and if the policy says that the fix is disabled, then the OS falls back to the old code-path.

Today, fixes in our monthly updates are enabled by default -- i.e., the old code is disabled, and the new code is enabled. If a fix turns out to have a serious problem, Azure hosted services and Windows work in tandem to update this policy-setting on the device and disable the problematic fix. Enterprises will be able to exercise control over this policy.

Note: As mentioned earlier, we only use Known Issue Rollback with non-security fixes. Using this coding scheme retains the old code. In the context of security fixes, older code is typically more vulnerable or exploitable; this is why we don't use Known Issue Rollback with security fixes today.

How Known Issue Rollback works for the end user

When Microsoft decides to rollback a bug fix in an update because of a known issue, we make a configuration change in the cloud. Devices connected to Windows Update or Windows Update for Business are notified of this change and it takes effect with the next reboot.

end-user-microsoft-managed.png

Microsoft Privacy Statement on Windows Diagnostics

Once this happens, the Know Issue Rollback infrastructure will start reporting that the fix - the new code that has a problem - is no longer enabled. From this point on, the OS will fall back to the previous code that had a bug albeit a much more benign issue than the new code that has a problem.

While these devices would still require a reboot, in most cases we have identified and published a rollback before most end user devices would have had the chance to even install the update containing the issue. In other words, most end users will never see the regression!

Devices that have opted into providing Microsoft with diagnostic data then send very scoped information about which code path is being exercised. This data helps us learn how well the rollback is succeeding in the ecosystem.

Putting enterprises in control

Enterprise devices are typically behind a Network Address Translation (NAT) and a firewall, which means they tend to be part of an Active Directory forest and are often managed using Group Policy. For a Know Issue Rollback, Microsoft publishes a specific Group Policy on the Download Center that can be used to configure and apply a rollback policy (rolling back the code in the latest cumulative update or LCU) within an enterprise. A link to the Group Policy is included in the Windows Update KB article and release notes as mitigations for a “Known Issue.”

enterprise-rollback.png

Microsoft Privacy Statement on Windows Diagnostics

In the KB article, we describe the issue and related information to help you and your IT administrators make informed choices. Our customer service teams are also aware of the Known Issue Rollback system and will be able to work with customers to identify problems with monthly updates and in turn coordinate a rollback if necessary.

Similar to the end-user scenario, devices that have opted into providing Microsoft with diagnostic data send specific information about which code-path is being exercised. This data helps us learn how well the rollback is succeeding in the ecosystem.

An example of Known Issue Rollback in action

We have been using the Known Issue Rollback since late 2019 to contain non-security fixes. Today, about 80% of fixes shipped on Windows 10, version 2004 (and later in-market versions), ship using Known Issue Rollback containment. Like most mitigation solutions, the real value of the Known Issue Rollback does not become truly apparent until you need it, and it works! Here’s an example.

The April 2020 preview non-security release (KB4550945) for Windows 10, version 1903 had a regression in a fix for the Microsoft Store. For gamers who had purchased in-app content (like PC game add-ons) from the Microsoft Store prior to the April update, that in-app content would no longer appear licensed once the OS was updated with this release. The net result was that the games would not run.

Fortunately, the Microsoft Store team used Known Issue Rollback.

On April 27th, a pattern indicating that a regression might be emerging was noticed by our social media monitoring team. With just over 110,000 devices updated, around a dozen tweets/reddit etc. posts indicated the following:

  • A consistent description of the problem (“Trial Period”, “App won’t run”, “App crash”, etc.)
  • Keywords that suggested that a Windows Update may be at fault (“KB4550945”, “1903”, “Latest Windows Update” etc.)

Internally, we created a post-release incident report to research, identify, and confirm the root cause. By April 29th, 170,000 devices had installed the April update and we had pinpointed the code change in the release that was problematic.

At 7:40 PM PST on April 29th, we made the decision to initiate a Known Issue Rollback. By 10:00 PM PST, we had kicked off the Known Issue Rollback process through our Azure configuration service and began configuring Windows 10, version 1903, devices to remedy the Microsoft Store issue. By 6:00 PM PST on April 30th, 145 million Windows 10, version 1903 devices had been configured to roll back the Microsoft Store regression. By May 3rd, after only 72 hours, 236 million devices had been rolled back.

In this example, we were able to deploy a Known Issue Rollback mitigation within 24 hours of identifying the root cause of a problem. The result is that the overwhelming majority of Windows users never saw the regression. For them, the problem never existed; their machines quietly updated and there was no visible issue.

The Known Issue Rollback lifecycle

Known Issue Rollback configurations have a limited lifespan—a few months at most—because we expect to solve the underlying problem quickly and re-issue the fix. Once the underlying problem has been fixed, the Group Policy has outlived its usefulness. It becomes a benign setting and can be undeployed safely.

It’s worth noting that each Known Issue Rollback Group Policy is unique to a specific issue, i.e. a regression, and, as such, these policies are not cumulative in nature.

Conclusion

Today, Windows runs on over a billion devices spanning industries and countries around the globe. At Microsoft, we have been cultivating a service mindset in our journey to continuously improve our engineering and software update experience.

With Known Issue Rollback, your organization can remain secure and productive. We understand that the size of our ecosystem and the scale of our service requires a service maturity mindset. Known Issue Rollback is a great capability that can enable you to quickly recover from regressions without the risks associated with rolling back critical security protections.

Vatsan and I are happy to be on the team leading these innovations to keep you, our customers, secure while you also stay productive.

To learn more

For more information on Known Issue Rollback, watch this video:

 

63 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-2176831%22%20slang%3D%22en-US%22%3EKnown%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2176831%22%20slang%3D%22en-US%22%3E%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EToday%20I'm%20sharing%20details%20about%20%3CSTRONG%3EKnown%20Issue%20Rollback%20(KIR)%3C%2FSTRONG%3E%2C%20a%20new%20capability%20that%20can%20quickly%20return%20an%20impacted%20device%20back%20to%20productive%20use%20if%20an%20issue%20arises%20during%20a%20Windows%20update.%20In%20this%20blog%2C%20my%20engineering%20partner%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F961463%22%20target%3D%22_blank%22%3EVatsan%20Madhavan%3C%2FA%3E%2C%20and%20I%20will%20walk%20you%20through%20this%20new%20capability.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EIn%20today%E2%80%99s%20digital%20world%2C%20we%20you%20know%20you%20rely%20on%20trustworthy%20systems%20and%20services%20to%20stay%20ahead%20of%20potential%20security%20threats%20to%20your%20enterprise%20environments.%20At%20the%20same%20time%2C%20you%20strive%20to%20sustain%20the%20productivity%20of%20your%20work%20forces.%20We%20know%20you%20need%20both%3A%20security%20and%20productivity.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EThe%20Windows%20Servicing%20%26amp%3B%20Delivery%20team%20works%20to%20help%20keep%20Microsoft%20customers%20protected%20and%20productive%20by%20continuously%20building%20and%20delivering%20updates%20to%20the%20%3CA%20href%3D%22https%3A%2F%2Fazure.microsoft.com%2Fen-us%2Foverview%2Ffuture-of-cloud%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Eintelligent%20cloud%20and%20intelligent%20edge%3C%2FA%3E.%20Over%20the%20past%20year%2C%20we%20have%20been%20working%20on%20improvements%20that%20help%20you%20ensure%20uninterrupted%20productivity%20even%20when%20rolling%20out%20critical%20updates%20to%20prevent%20or%20address%20potential%20issues.%3C%2FP%3E%0A%3CH2%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2020px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%20id%3D%22toc-hId--522254640%22%3EIntroducing%20Known%20Issue%20Rollback%3C%2FH2%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EKnown%20Issue%20Rollback%20is%20an%20important%20Windows%20servicing%20improvement%20to%20support%20%3CSTRONG%3E%3CEM%3Enon-security%20bug%20fixes%3C%2FEM%3E%3C%2FSTRONG%3E%2C%20enabling%20us%20to%20quickly%20revert%20a%20single%2C%20targeted%20fix%20to%20a%20previously%20released%20behavior%20if%20a%20critical%20regression%20is%20discovered.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EBuilt%20in%20direct%20response%20to%20your%20feedback%2C%20the%20pieces%20that%20make%20Known%20Issue%20Rollback%20work%20came%20together%20in%20a%20functionally%20complete%20system%20beginning%20in%20Windows%2010%2C%20version%202004.%20Every%20month%2C%20we%20release%20monthly%20updates%20with%20many%20of%20quality%20changes%20%E2%80%9Ccontained%E2%80%9D%20using%20the%20Known%20Issue%20Rollback%20capability.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWhile%20Known%20Issue%20Rollback%20was%20originally%20designed%20for%20user-mode%20processes%2C%20we%20have%20made%20phased%20improvements%20over%20the%20last%20year%20to%20the%20OS%20kernel%20and%20the%20boot%20loader%20to%20support%20this%20capability%20in%20kernel%20mode.%20Some%20versions%20of%20Windows%2010%20prior%20to%20version%202004%2C%20for%20example%20versions%201909%20and%201809%2C%20have%20partial%20support%20for%20Known%20Issue%20Rollback%20built%20into%20the%20OS%20and%20we%20leverage%20that%20support%20whenever%20possible%20when%20shipping%20updates%20for%20those%20versions.%3C%2FP%3E%0A%3CH3%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2017px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%20id%3D%22toc-hId-168306834%22%3EAt%20the%20code%20level%3C%2FH3%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWhen%20Windows%20developers%20code%20a%20non-security%20bug-fix%2C%20they%20keep%20the%20old%20code%20intact%20and%20add%20the%20fix.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22An%20example%20of%20bug%20fix%20code%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F259564iBCBBC3FD49065CF8%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Eric_Vernon_1-1614669786001.png%22%20alt%3D%22Eric_Vernon_1-1614669786001.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EThe%20Known%20Issue%20Rollback%20infrastructure%20in%20the%20OS%20provides%20developers%20with%20a%20method%20that%20evaluates%20a%20policy%20to%20determine%20the%20execution%20path.%20This%20policy%20tells%20the%20OS%20whether%20a%20fix%20should%20remain%20enabled%20or%20not.%20If%20the%20policy%20states%20that%20the%20fix%20is%20enabled%2C%20then%20the%20new%20code%20runs%3B%20and%20if%20the%20policy%20says%20that%20the%20fix%20is%20disabled%2C%20then%20the%20OS%20falls%20back%20to%20the%20old%20code-path.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EToday%2C%20fixes%20in%20our%20monthly%20updates%20are%20enabled%20by%20default%20--%20i.e.%2C%20the%20old%20code%20is%20disabled%2C%20and%20the%20new%20code%20is%20enabled.%20If%20a%20fix%20turns%20out%20to%20have%20a%20serious%20problem%2C%20Azure%20hosted%20services%20and%20Windows%20work%20in%20tandem%20to%20update%20this%20policy-setting%20on%20the%20device%20and%20disable%20the%20problematic%20fix.%20Enterprises%20will%20be%20able%20to%20exercise%20control%20over%20this%20policy.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CTABLE%20style%3D%22background-color%3A%20%23deeaf6%3B%22%20width%3D%22100%25%22%3E%0A%3CTBODY%3E%0A%3CTR%3E%0A%3CTD%20width%3D%22100%25%22%3E%3CP%20style%3D%22margin%3A%2010px%3B%22%3E%3CSTRONG%3ENote%3A%3C%2FSTRONG%3E%20As%20mentioned%20earlier%2C%20we%20only%20use%20Known%20Issue%20Rollback%20with%20non-security%20fixes.%20Using%20this%20coding%20scheme%20retains%20the%20old%20code.%20In%20the%20context%20of%20security%20fixes%2C%20older%20code%20is%20typically%20more%20vulnerable%20or%20exploitable%3B%20this%20is%20why%20we%20don't%20use%20Known%20Issue%20Rollback%20with%20security%20fixes%20today.%3C%2FP%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3CH3%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2017px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%20id%3D%22toc-hId--1639147629%22%3EHow%20Known%20Issue%20Rollback%20works%20for%20the%20end%20user%3C%2FH3%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWhen%20Microsoft%20decides%20to%20rollback%20a%20bug%20fix%20in%20an%20update%20because%20of%20a%20known%20issue%2C%20we%20make%20a%20configuration%20change%20in%20the%20cloud.%20Devices%20connected%20to%20Windows%20Update%20or%20Windows%20Update%20for%20Business%20are%20notified%20of%20this%20change%20and%20it%20takes%20effect%20with%20the%20next%20reboot.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22A%20diagram%20of%20what%20the%20end%20user%2C%20Microsoft%20managed%20scenario%20looks%20like%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F259570i7544C84623CD8248%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22end-user-microsoft-managed.png%22%20alt%3D%22end-user-microsoft-managed.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%3CFONT%20size%3D%222%22%3E%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fprivacy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20Privacy%20Statement%20on%20Windows%20Diagnostics%20%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EOnce%20this%20happens%2C%20the%20Know%20Issue%20Rollback%20infrastructure%20will%20start%20reporting%20that%20the%20fix%20-%20the%20new%20code%20that%20has%20a%20problem%20-%20is%20no%20longer%20enabled.%20From%20this%20point%20on%2C%20the%20OS%20will%20fall%20back%20to%20the%20previous%20code%20that%20had%20a%20bug%20albeit%20a%20much%20more%20benign%20issue%20than%20the%20new%20code%20that%20has%20a%20problem.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWhile%20these%20devices%20would%20still%20require%20a%20reboot%2C%20in%20most%20cases%20we%20have%20identified%20and%20published%20a%20rollback%20before%20most%20end%20user%20devices%20would%20have%20had%20the%20chance%20to%20even%20install%20the%20update%20containing%20the%20issue.%20In%20other%20words%2C%20most%20end%20users%20will%20never%20see%20the%20regression!%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EDevices%20that%20have%20opted%20into%20providing%20Microsoft%20with%20diagnostic%20data%20then%20send%20very%20scoped%20information%20about%20which%20code%20path%20is%20being%20exercised.%20This%20data%20helps%20us%20learn%20how%20well%20the%20rollback%20is%20succeeding%20in%20the%20ecosystem.%3C%2FP%3E%0A%3CH3%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2017px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%20id%3D%22toc-hId-848365204%22%3EPutting%20enterprises%20in%20control%3C%2FH3%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EEnterprise%20devices%20are%20typically%20behind%20a%20Network%20Address%20Translation%20(NAT)%20and%20a%20firewall%2C%20which%20means%20they%20tend%20to%20be%20part%20of%20an%20Active%20Directory%20forest%20and%20are%20often%20managed%20using%20Group%20Policy.%20For%20a%20Know%20Issue%20Rollback%2C%20Microsoft%20publishes%20a%20specific%20Group%20Policy%20on%20the%20Download%20Center%20that%20can%20be%20used%20to%20configure%20and%20apply%20a%20rollback%20policy%20(rolling%20back%20the%20code%20in%20the%20latest%20cumulative%20update%20or%20LCU)%20within%20an%20enterprise.%20A%20link%20to%20the%20Group%20Policy%20is%20included%20in%20the%20Windows%20Update%20KB%20article%20and%20release%20notes%20as%20mitigations%20for%20a%20%E2%80%9CKnown%20Issue.%E2%80%9D%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22A%20diagram%20of%20what%20the%20enterprise%20rollback%20scenario%20looks%20like%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F259571iEA8BA1002259555C%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22enterprise-rollback.png%22%20alt%3D%22enterprise-rollback.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%3CFONT%20size%3D%222%22%3E%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fprivacy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20Privacy%20Statement%20on%20Windows%20Diagnostics%20%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EIn%20the%20KB%20article%2C%20we%20describe%20the%20issue%20and%20related%20information%20to%20help%20you%20and%20your%20IT%20administrators%20make%20informed%20choices.%20Our%20customer%20service%20teams%20are%20also%20aware%20of%20the%20Known%20Issue%20Rollback%20system%20and%20will%20be%20able%20to%20work%20with%20customers%20to%20identify%20problems%20with%20monthly%20updates%20and%20in%20turn%20coordinate%20a%20rollback%20if%20necessary.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3ESimilar%20to%20the%20end-user%20scenario%2C%20devices%20that%20have%20opted%20into%20providing%20Microsoft%20with%20diagnostic%20data%20send%20specific%20information%20about%20which%20code-path%20is%20being%20exercised.%20This%20data%20helps%20us%20learn%20how%20well%20the%20rollback%20is%20succeeding%20in%20the%20ecosystem.%3C%2FP%3E%0A%3CH2%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2020px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%20id%3D%22toc-hId-837862100%22%3EAn%20example%20of%20Known%20Issue%20Rollback%20in%20action%3C%2FH2%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWe%20have%20been%20using%20the%20Known%20Issue%20Rollback%20since%20late%202019%20to%20contain%20non-security%20fixes.%20Today%2C%20about%2080%25%20of%20fixes%20shipped%20on%20Windows%2010%2C%20version%202004%20(and%20later%20in-market%20versions)%2C%20ship%20using%20Known%20Issue%20Rollback%20containment.%20Like%20most%20mitigation%20solutions%2C%20the%20real%20value%20of%20the%20Known%20Issue%20Rollback%20does%20not%20become%20truly%20apparent%20until%20you%20need%20it%2C%20and%20it%20works!%20Here%E2%80%99s%20an%20example.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EThe%20April%202020%20preview%20non-security%20release%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4550945%2Fwindows-10-update-kb4550945%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EKB4550945%3C%2FA%3E)%20for%20Windows%2010%2C%20version%201903%20had%20a%20regression%20in%20a%20fix%20for%20the%20Microsoft%20Store.%20For%20gamers%20who%20had%20purchased%20in-app%20content%20(like%20PC%20game%20add-ons)%20from%20the%20Microsoft%20Store%20prior%20to%20the%20April%20update%2C%20that%20in-app%20content%20would%20no%20longer%20appear%20licensed%20once%20the%20OS%20was%20updated%20with%20this%20release.%20The%20net%20result%20was%20that%20the%20games%20would%20not%20run.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EFortunately%2C%20the%20Microsoft%20Store%20team%20used%20Known%20Issue%20Rollback.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EOn%20April%2027%3CSUP%3Eth%3C%2FSUP%3E%2C%20a%20pattern%20indicating%20that%20a%20regression%20might%20be%20emerging%20was%20noticed%20by%20our%20social%20media%20monitoring%20team.%20With%20just%20over%20110%2C000%20devices%20updated%2C%20around%20a%20dozen%20tweets%2Freddit%20etc.%20posts%20indicated%20the%20following%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%20margin-top%3A%2020px%3B%22%3EA%20consistent%20description%20of%20the%20problem%20(%E2%80%9CTrial%20Period%E2%80%9D%2C%20%E2%80%9CApp%20won%E2%80%99t%20run%E2%80%9D%2C%20%E2%80%9CApp%20crash%E2%80%9D%2C%20etc.)%3C%2FLI%3E%0A%3CLI%20style%3D%22margin-bottom%3A%208px%3B%22%3EKeywords%20that%20suggested%20that%20a%20Windows%20Update%20may%20be%20at%20fault%20(%E2%80%9CKB4550945%E2%80%9D%2C%20%E2%80%9C1903%E2%80%9D%2C%20%E2%80%9CLatest%20Windows%20Update%E2%80%9D%20etc.)%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EInternally%2C%20we%20created%20a%20post-release%20incident%20report%20to%20research%2C%20identify%2C%20and%20confirm%20the%20root%20cause.%20By%20April%2029%3CSUP%3Eth%3C%2FSUP%3E%2C%20170%2C000%20devices%20had%20installed%20the%20April%20update%20and%20we%20had%20pinpointed%20the%20code%20change%20in%20the%20release%20that%20was%20problematic.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EAt%207%3A40%20PM%20PST%20on%20April%2029%3CSUP%3Eth%3C%2FSUP%3E%2C%20we%20made%20the%20decision%20to%20initiate%20a%20Known%20Issue%20Rollback.%20By%2010%3A00%20PM%20PST%2C%20we%20had%20kicked%20off%20the%20Known%20Issue%20Rollback%20process%20through%20our%20Azure%20configuration%20service%20and%20began%20configuring%20Windows%2010%2C%20version%201903%2C%20devices%20to%20remedy%20the%20Microsoft%20Store%20issue.%20By%206%3A00%20PM%20PST%20on%20April%2030%3CSUP%3Eth%3C%2FSUP%3E%2C%20145%20million%20Windows%2010%2C%20version%201903%20devices%20had%20been%20configured%20to%20roll%20back%20the%20Microsoft%20Store%20regression.%20By%20May%203%3CSUP%3Erd%3C%2FSUP%3E%2C%20after%20only%2072%20hours%2C%20236%20million%20devices%20had%20been%20rolled%20back.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EIn%20this%20example%2C%20we%20were%20able%20to%20deploy%20a%20Known%20Issue%20Rollback%20mitigation%20within%2024%20hours%20of%20identifying%20the%20root%20cause%20of%20a%20problem.%20The%20result%20is%20that%20the%20overwhelming%20majority%20of%20Windows%20users%20never%20saw%20the%20regression.%20For%20them%2C%20the%20problem%20never%20existed%3B%20their%20machines%20quietly%20updated%20and%20there%20was%20no%20visible%20issue.%3C%2FP%3E%0A%3CH2%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2020px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%20id%3D%22toc-hId--969592363%22%3EThe%20Known%20Issue%20Rollback%20lifecycle%3C%2FH2%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EKnown%20Issue%20Rollback%20configurations%20have%20a%20limited%20lifespan%E2%80%94a%20few%20months%20at%20most%E2%80%94because%20we%20expect%20to%20solve%20the%20underlying%20problem%20quickly%20and%20re-issue%20the%20fix.%20Once%20the%20underlying%20problem%20has%20been%20fixed%2C%20the%20Group%20Policy%20has%20outlived%20its%20usefulness.%20It%20becomes%20a%20benign%20setting%20and%20can%20be%20undeployed%20safely.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EIt%E2%80%99s%20worth%20noting%20that%20each%20Known%20Issue%20Rollback%20Group%20Policy%20is%20unique%20to%20a%20specific%20issue%2C%20i.e.%20a%20regression%2C%20and%2C%20as%20such%2C%20these%20policies%20are%20not%20cumulative%20in%20nature.%3C%2FP%3E%0A%3CH2%20style%3D%22margin-top%3A%2036px%3B%20margin-bottom%3A%2020px%3B%20font-family%3A%20'Segoe%20UI'%2C%20Segoe%2C%20Tahoma%2C%20Geneva%2C%20sans-serif%3B%20font-weight%3A%20600%3B%20font-size%3A%2020px%3B%20color%3A%20%23333333%3B%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%20id%3D%22toc-hId-1517920470%22%3EConclusion%3C%2FH2%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EToday%2C%20Windows%20runs%20on%20over%20a%20billion%20devices%20spanning%20industries%20and%20countries%20around%20the%20globe.%20At%20Microsoft%2C%20we%20have%20been%20cultivating%20a%20service%20mindset%20in%20our%20journey%20to%20continuously%20improve%20our%20engineering%20and%20software%20update%20experience.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EWith%20Known%20Issue%20Rollback%2C%20your%20organization%20can%20remain%20secure%20and%20productive.%20We%20understand%20that%20the%20%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2018%2F11%2F13%2Fwindows-10-quality-approach-for-a-complex-ecosystem%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Esize%20of%20our%20ecosystem%20and%20the%20scale%20of%20our%20service%3C%2FA%3E%20requires%20a%20service%20maturity%20mindset.%20Known%20Issue%20Rollback%20is%20a%20great%20capability%20that%20can%20enable%20you%20to%20quickly%20recover%20from%20regressions%20without%20the%20risks%20associated%20with%20rolling%20back%20critical%20security%20protections.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3EVatsan%20and%20I%20are%20happy%20to%20be%20on%20the%20team%20leading%20these%20innovations%20to%20keep%20you%2C%20our%20customers%2C%20secure%20while%20you%20also%20stay%20productive.%3C%2FP%3E%0A%3CP%20style%3D%22margin-top%3A%2020px%3B%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2176831%22%20slang%3D%22en-US%22%3E%3CP%3ELearn%20about%20this%20new%20Windows%2010%20servicing%20capability%20and%20how%20you%20can%20utilize%20it%20in%20your%20organization.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Diagram%20of%20a%20sample%20enterprise%20rollback%20scenario%22%20style%3D%22width%3A%20640px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F259572i2F680681684DB2B5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22kir_blog.png%22%20alt%3D%22kir_blog.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2176831%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EServicing%20and%20updates%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2181719%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2181719%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F702597%22%20target%3D%22_blank%22%3E%40Eric_Vernon%3C%2FA%3E!%3C%2FP%3E%3CP%3EThanks%20for%20the%20blog%20post%2C%20it's%20nice%20to%20have%20a%20word%20from%20the%20PG%20on%20top%20of%20personal%20guesswork%20based%20on%20the%20MSKB%20article.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20got%20a%20couple%20of%20questions.%3C%2FP%3E%3CP%3E1.%20Is%20KIR%26nbsp%3Brelated%20in%20any%20way%20to%20the%26nbsp%3B%3CSPAN%3EWindows%20Feature%20Store%20%2F%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EWindows%20Notification%20Facility%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E2.%20Is%20KIR%20related%20to%20another%20approach%20of%20fixing%20issues%20via%20the%20WU%20troubleshooter%3F%20E.g.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4570336%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fkb%2F4570336%3C%2FA%3E%26nbsp%3BCan%20you%20shed%20some%20light%20on%20this%20method%20anyway%3F%20E.g.%20whether%20it's%20still%20in%20use%2C%20when%20it's%20used%20instead%20of%20KIR%2C%20etc.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3CBR%20%2F%3EVadim%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2183434%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2183434%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Vadim%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20your%20interest%20in%20Known%20Issue%20Rollback%20(KIR)%20and%20your%20questions.%20KIR%20is%20somewhat%20related%20to%20the%20troubleshooters%20from%20the%20standpoint%20that%20both%20are%20trying%20to%20solve%20customer%20issues.%20Troubleshooters%20tend%20to%20focus%20on%20a%20class%20of%20issues%20such%20as%20Activation%2C%20Networking%2C%20Microphone%20etc.%20Known%20Issue%20Rollback%20is%20much%20more%20targeted%20however%3B%20it%20deals%20with%20a%20specific%20issue%20that%20is%20a%20result%20of%20a%20specific%20code%20fix%20that%20shipped%20in%20a%20monthly%20Latest%20Cumulative%20Update%20(LCU).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20not%20sharing%20other%20information%20about%20the%20internals%2Fimplementation%20details%20about%20KIR%20at%20this%20time.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEric%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2191425%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2191425%22%20slang%3D%22en-US%22%3E%3CP%3EEric%2C%20will%20known%20issue%20rollback%20also%20be%20available%20on%20the%20windows%20server%20platform%2C%26nbsp%3B%20or%20for%20other%20Microsoft%20products%20such%20as%20Office%20or%20.net%20framework%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2193340%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2193340%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F702597%22%20target%3D%22_blank%22%3E%40Eric_Vernon%3C%2FA%3E%3A%20Great%20stuff.%3CBR%20%2F%3E%3CBR%20%2F%3ELike%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9626%22%20target%3D%22_blank%22%3E%40will%20nimmo%3C%2FA%3E%26nbsp%3BI'd%20be%20interested%20to%20know%20if%20this%20is%20a%20thing%20that%20will%20impact%20the%20server%20OS%20where%20the%20criticality%20is%20often%20a%20bigger%20deal.%26nbsp%3B%20Though%20you%20could%20argue%20that%20on%20the%20server%20side%20there's%20probably%20less%20of%20a%20chance%20that%20a%20non-security%20update%20breaks%20critical%20functionality.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20other%20feedback%20I'd%20give%20is%20KIR%20GPO%20bloat.%26nbsp%3B%20I%20can%20promise%20you%20that%20most%20orgs%20are%20just%20going%20to%20add%20a%20KIR%20to%20the%20policy%20and%20never%20think%20of%20it%20again.%26nbsp%3B%20While%20on%20the%20individual%20level%20that's%20probably%20not%20a%20huge%20problem%2C%20if%20each%20KIR%20is%20it's%20own%20policy%2Fwhatever%20that%20you're%20publishing%20then%20overtime%20that's%20going%20to%20create%20bloat%20that%20will%20impact%20GPO%20processing%20times.%26nbsp%3B%20GPO%20is%20the%20poster%20child%20for%20'set%20it%20and%20forget%20it'%20until%20a%20new%20admin%20comes%20in%20and%20asks%20what%20these%202000%20policies%20do%20and%20why%20they%20were%20set.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2196781%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2196781%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F9626%22%20target%3D%22_blank%22%3E%40will%20nimmo%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F265903%22%20target%3D%22_blank%22%3E%40bdam55%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%3E%0A%3CP%3E%3CSPAN%3EThanks%20for%20your%20interest%20in%20KIR%20and%20your%20questions.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThis%20technology%20works%20on%20Windows%20Server%20the%20same%20way%20as%20it%20works%20on%20Windows%20Client%20Editions%20i.e.%26nbsp%3Bnewer%20versions%20such%20as%20Windows%20Server%202004%20have%20fully%20functional%20support%20for%20KIR%20today%20while%20older%20versions%20have%20limited%20support.%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EAt%20this%20time%2C%20.NET%20Framework%20and%20other%20Microsoft%20products%20like%20Office%20do%20not%20have%20support%20for%20Known%20Issue%20Rollback.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThe%20concerns%20you've%20raised%20about%20GPO%20bloat%20and%20the%20consequent%20impact%20on%20processing%20times%20is%20valid%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F265903%22%20target%3D%22_blank%22%3E%40bdam55%3C%2FA%3E%26nbsp%3B%20-%20thanks%20for%20bringing%20these%20up!%20This%20is%20something%20we%20hope%20to%20address%20in%20the%20future%20as%20we%20continue%20to%20make%20improvements%20to%20KIR.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThanks%2C%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F961463%22%20target%3D%22_blank%22%3E%40Vatsan_Madhavan%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2196915%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2196915%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F961463%22%20target%3D%22_blank%22%3E%40Vatsan_Madhavan%3C%2FA%3E%2C%20that's%20great%20info!%26nbsp%3B%20I%20should%20have%20specified%20though%3A%20can%20you%20describe%20the%20support%20for%20Server%20LTSC%20(2012%2C%202016%2C%20and%202019)%3F%26nbsp%3B%20I'm%20sure%20there's%20large%20farms%20of%20SAC%20out%20there%20somewhere%20but%20I've%20not%20seen%20them%20in%20the%20enterprises%20I%20interact%20with.%3CBR%20%2F%3E%3CBR%20%2F%3E%22Not%20happening%22%20is%20a%20perfectly%20fine%20answer%20and%20kind%20of%20what%20users%20signed%20up%20for%20but%20I'd%20love%20to%20be%20surprised.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2197385%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2197385%22%20slang%3D%22en-US%22%3E%3CDIV%3EThanks%20for%20the%20clarification%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F265903%22%20target%3D%22_blank%22%3E%40bdam55%3C%2FA%3E.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EAs%20I%20mentioned%20previously%2C%20there%20is%20partial%20support%20for%20KIR%20in%20versions%20older%20than%20Windows%20Server%202004.%3CBR%20%2F%3E%3CBR%20%2F%3ESpecifically%2C%20we%20have%20some%20support%20for%20KIR%20in%20each%20of%20Windows%20Server%202019%20LTSC%20(1809)%20and%20Windows%20Server%202016%20LTSC%20(1607)%2C%20though%20the%20extent%20of%20capability%20in%20each%20version%20varies%20(in%20general%2C%20newer%20versions%20of%20the%20OS%20have%20more%20refinements%2Fcapabilities).%20There%20is%20no%20support%20for%20KIR%20in%20Windows%20Server%202012.%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2217979%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2217979%22%20slang%3D%22en-US%22%3E%3CP%3EPoint%20of%20clarification.%20Is%20this%20feature%20is%20limited%20to%20Windows%20in%20a%20business%20setting%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20Windows%20Home%20users%20are%20left%20out%20in%20the%20cold%2C%20with%20broken%20machines%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2218018%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2218018%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1532%22%20target%3D%22_blank%22%3E%40ron%20S.%3C%2FA%3E%26nbsp%3BThis%20is%20not%20limited%20to%20the%20business%20setting.%20Group%20Policy%20is%20the%20KIR%20business%20setting%20solution.%20For%20other%20versions%20of%20Windows%20outside%20of%20a%20business%20setting%20AND%20are%20connected%20to%20Windows%20Update%2C%20KIR%20is%20implemented%20from%20our%20cloud%20service.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2220085%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2220085%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20timing.%26nbsp%3B%20I'm%20sure%20this%20isn't%20the%20right%20place%20for%20a%20request%20like%20this%2C%20but%20I'm%20not%20sure%20where%20else%20to%20request%20it.%26nbsp%3B%20Maybe%20report%20as%20an%20issue%20on%20M365%20Admin%20Portal%3F%26nbsp%3B%20Can%20we%20can%20a%20KIR%20policy%20for%20this%20issue%20in%26nbsp%3BKB5000802%3F%26nbsp%3B%20It's%20been%20a%20known%20issue%20for%20several%20days%20and%20still%20no%20fix.%26nbsp%3B%20The%20barcodes%20on%20our%20college%20ID%20cards%20are%20not%20getting%20printed%20until%20I%20uninstall%20this%20update.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22x-hidden-focus%22%3EAfter%20installing%20updates%20released%20March%209%2C%202021%20or%20March%2015%2C%202021%2C%20you%20might%20get%20unexpected%20results%20when%20printing%20from%20some%20apps.%20Issues%20might%20include%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CP%3EElements%20of%20the%20document%20might%20print%20as%20solid%20black%2Fcolor%20boxes%20or%20might%20be%20missing%2C%20including%20barcodes%2C%20QR%20codes%2C%20and%20graphics%20elements%2C%20such%20as%20logos.%3C%2FP%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2220176%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2220176%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F399619%22%20target%3D%22_blank%22%3E%40Brian_Klish_work%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%20Microsoft%20doesn't%20have%20a%20mechanism%20for%20handling%20feedback%20from%20IT%20professionals%2C%20they%20want%20us%20to%20use%20the%20Feedback%20Hub%20too%2C%20which%20is%20about%20the%20same%20as%20writing%20a%20note%20on%20toilet%20paper%20and%20flushing%20it.%20My%20feedback%20would%20be%20that%20Microsoft%20needs%20to%20up%20their%20game%20in%20regards%20to%20testing%20updates.%20The%20past%20several%20years%20have%20proven%20that%20their%20current%20testing%20process%20is%20totally%20inadequate%20and%20demonstrates%20incompetence%20at%20the%20highest%20levels.%20There%20is%20not%20a%20day%20that%20passes%20that%20I'm%20not%20fighting%20a%20bad%20Windows%20(or%20Office365)%20update%20somewhere.%20I'd%20like%20to%20sugar%20coat%20this%2C%20but%20the%20there%20is%20not%20enough%20lipstick%20produced%20on%20the%20planet%20to%20make%20this%20Microsoft%20pig%20look%20good.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2220594%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2220594%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F399619%22%20target%3D%22_blank%22%3E%40Brian_Klish_work%3C%2FA%3E%26nbsp%3BSorry%20to%20hear%20you%20are%20having%20issues%20with%20printing.%20Take%20a%20look%20at%20the%20Windows%20Release%20dashboard%20(%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fwindowsreleasehealth%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fwindowsreleasehealth%3C%2FA%3E)%20for%20details%20of%20the%20issue%20and%20when%20the%20fix%20will%20be%20released.%20Unfortunately%20in%20this%20particular%20instance%2C%20KIR%20could%20not%20be%20used.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2220691%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2220691%22%20slang%3D%22en-US%22%3E%3CP%3EHelp%20us%20understand%20when%20KIR%20can%20and%20cannot%20be%20used%20so%20we%20know%20when%20(or%20if)%20to%20expect%20things%20to%20be%20handled%20in%20this%20manner%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2220696%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2220696%22%20slang%3D%22en-US%22%3E%3CP%3EP.S.%20The%20dashboard%20at%20this%20time%20just%20says%20you%20are%20working%20on%20the%20fix%20so%20there%20is%20not%20ETA%20at%20this%20time%20of%20when%20to%20expect%20the%20fix%20for%20the%20image%20printing%20problem%20and%20the%20Dymo%20label%20issue%20so%20at%20this%20time%20the%20only%20workaround%20is%20to%20uninstall%20the%20update.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2221193%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2221193%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11042%22%20target%3D%22_blank%22%3E%40Susan%20Bradley%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20question.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20are%20several%20considerations%20for%20when%20KIR%20can%20be%20used%20(today)%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EUsed%20only%20for%20non-security%20fixes.%3C%2FLI%3E%0A%3CLI%3EMore%20recent%20platforms%2C%20Windows%2010%202004%20and%20newer%2C%20leverage%20KIR%20more%20fully.%20Older%20platforms%20have%20limited%20KIR%20support.%3C%2FLI%3E%0A%3CLI%3EEach%20fix%20is%20evaluated%20by%20the%20developer%20prior%20to%20release%20to%20see%20if%20KIR%20is%20feasible.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EToday%20we%20don%E2%80%99t%20publish%20KIR%20usage%20for%20each%20fix%20that%20goes%20into%20a%20monthly%20update%20(LCU).%20KIR%20is%20part%20of%20a%20larger%20strategy%20to%20improve%20customer%20confidence%20in%20the%20LCU.%20The%20callout%20to%20the%20Windows%20Release%20dashboard%20is%20to%20highlight%20that%20this%20is%20where%20Microsoft%20will%20communicate%20-%20not%20only%20information%20about%20issues%20but%20also%20whether%20an%20issue%20is%20solved%20with%20KIR.%20KIR-mitigated%20issues%20typically%20release%20much%20more%20quickly%20than%20updates%20to%20solve%20regressions%2C%20and%20we%20are%20working%20to%20expand%20KIR%20usage%20in%20Windows%20platforms.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2221809%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2221809%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F399619%22%20target%3D%22_blank%22%3E%40Brian_Klish_work%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnother%20out%20of%20band%20update%20out%20tonight%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Frelease-health%2Fwindows-message-center%231574%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Frelease-health%2Fwindows-message-center%231574%3C%2FA%3E%26nbsp%3BI%20think%20your%20fix%20might%20in%20that%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2223072%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2223072%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20the%20post%2C%20it%20is%20very%20valuable%20%2C%20however%20I%20see%20one%20minor%20issue%20here.%20It%20will%20work%20if%20update%20has%20been%20installed%20and%20Windows%20have%20been%20boot%20and%20while%20inside%20the%20Windows%20environment%20it%20is%20able%20to%20send%20a%20diagnose%20report%20%2C%20however%20consider%20the%20case%20where%20update%20affect%20the%20Network%20Driver%20or%20Reporting%20Mechanism%20so%20no%20report%20will%20be%20sent%20or%20the%20update%20caused%20failure%20in%20booting%20of%20the%20operating%20system%20where%20no%20report%20will%20be%20sent%20too.%3C%2FP%3E%3CP%3EIn%20this%20case%20we%20are%20in%20state%20where%20systems%20are%26nbsp%3B%3CSTRONG%3Enot%26nbsp%3B%3C%2FSTRONG%3Ereporting%20and%20it%20might%20be%20valid%20like%20user%20turn%20off%20their%20device%20or%20they%20are%20not%20connected%20to%20the%20internet%20or%20there%20is%20network%20connection%20issue%20(internet%20failure%20and%20so%20on)%20or%20it%20could%20be%20a%20failure%20like%20update%20failure.%20I%20am%20wondering%20is%20there%20any%20solution%20for%20such%20scenarios%20too%20or%20we%20should%20leave%20it%20to%20the%20expertise%20of%20the%20administrator%20to%20identify%20whether%20not%20reporting%20status%20of%20the%20update%20is%20due%20to%20failure%20or%20update%20installed%20successfully%20with%20no%20issue%20and%20there%20is%20only%20a%20connectivity%20problem.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2228326%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2228326%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F702597%22%20target%3D%22_blank%22%3E%40Eric_Vernon%3C%2FA%3E%26nbsp%3BIn%20your%20response%20to%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F399619%22%20target%3D%22_blank%22%3E%40Brian_Klish_work%3C%2FA%3E%2C%20when%20he%20asked%20whether%20KIR%20is%20in%20effect%20for%20the%20current%20printing%20issues%20from%20the%20March%202021%20patches%2C%20you%20mentioned%20%22%3CSPAN%3EUnfortunately%20in%20this%20particular%20instance%2C%20KIR%20could%20not%20be%20used%22%2C%20however%20in%20your%20video%20in%20this%20blog%20at%20around%20marker%2000%3A30%2C%20you%20describe%20the%20issue%20with%20a%20printing%20issue%20caused%20by%20a%20patch%20in%20September%202020%2C%20and%20KIR%20came%20to%20the%20rescue.%20So%2C%20why%20doesn't%20it%20work%20for%20the%20current%20printing%20issues%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2231554%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2231554%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1423%22%20target%3D%22_blank%22%3E%40Harjit%20Dhaliwal%3C%2FA%3E%26nbsp%3BEach%20fix%20is%20evaluated%20individually%20based%20on%20the%20component%2C%20the%20risk%20of%20the%20change%2C%20fix%20type%2C%20the%20platform%20etc.%20In%20the%20case%20of%20the%20print%20issue%20mentioned%20by%20Brian%2C%20this%20was%20a%20security%20fix%20that%20had%20issues%20and%20KIR%20currently%20only%20supports%20non-security%20fixes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2242666%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2242666%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F702597%22%20target%3D%22_blank%22%3E%40Eric_Vernon%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20in%20AD%20environment%20-%20we%20should%20check%20regularly%20release%20notes%20to%20see%20if%20some%20regression%26nbsp%3B%20is%20confirmed%20%2C%20check%20does%20it%20affect%20our%20environment%20and%20if%20yes%20then%20apply%20related%20GPO%3F%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20question%20-%20approx%20when%20it%20will%20Intune%20include%20this%20functionality%3F%20Azure%20Arc%20(for%20Servers)%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2242817%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2242817%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F32395%22%20target%3D%22_blank%22%3E%40Andres%20Pae%3C%2FA%3E%26nbsp%3BYou%20are%20correct%20about%20your%20AD%20environment.%20If%20you%20are%20not%20seeing%20the%20issue%2C%20there%20is%20no%20need%20to%20apply%20the%20GP.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20working%20on%20integration%20with%20Intune%20and%20other%20management%20solutions%20but%20I%20don't%20have%20an%20eta%20to%20share%20at%20this%20time.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2287193%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2287193%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20having%20issues%20with%20the%26nbsp%3BKB5001330%20security%20update.%20You%20guys%20said%20that%20this%20is%20Fixed%20using%20the%20Known%20Issue%20Rollback%20but%20this%20blog%20here%20says%20it%20only%20works%20for%20non-security%20updates.%20So%2C%20Microsoft%20are%20Lying%3F%20I%20have%20installed%20the%26nbsp%3BWindows%2010%20(2004%20%26amp%3B%2020H2)%20Known%20Issue%20Rollback%20042121%2001.msi%20but%20when%20I%20go%20to%20gpedit.msi%20I%20can%20see%20a%20%3CSTRONG%3E%22KB5000842%20Issue%20001%20Rollback%22%26nbsp%3B%3C%2FSTRONG%3Enot%20a%20%3CSTRONG%3E%3CU%3EKB5001330.%3C%2FU%3E%3C%2FSTRONG%3E%20So%20Microsoft%20are%20telling%20everyone%20that%20the%20problem%20is%20FIXED%2C%20but%20It%20is%20not!%20Just%20Lies.%20I%20Use%20SSD%20so%20a%20frequently%20erase%20Windows%20Update%20files%20and%20I'm%20unable%20to%20uninstall%20KB501330.%20Lot%20of%20Games%2C%20Programming%20Codes%2C%20Certificates%20and%20etc.%20doesn't%20allow%20me%20to%20Easily%20uninstall%20or%20reinstall%20Windows.%20So%20we%20are%20here%2C%20with%20a%20broken%20windows%20and%20no%20visible%20REAL%20fix%20or%20update.%20I%20aways%20keep%20my%20devices%20updated%20to%20the%20latest%20version%20but%20after%20this%20i%20will%20NEVER-EVER%20again%20keep%20my%20windows%20update%20turned%20on.%26nbsp%3BDisrespectful%20and%20unacceptable.%20Stopped%20for%20almost%202%20weeks.%20Ho%20will%20pay%20that%20bill%3F%20Me%2C%20of%20course.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2288273%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2288273%22%20slang%3D%22en-US%22%3E%3CP%20data-unlink%3D%22true%22%3EI%20think%20this%20article%20should%20add%20information%20for%20consumer%20devices%2C%20considering%20a%20lot%20of%20home%20end-users%20like%20me%20learned%20about%20KIR%20because%20of%20the%20bug%20which%20happenned%20with%20KB5001330.%20I%20found%20this%20page%20thanks%20to%20the%20following%20article%3A%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fapril-13-2021-kb5001330-os-builds-19041-928-and-19042-928-cead30cd-f284-4115-a42f-d67fec538490%2C%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Ftopic%2Fapril-13-2021-kb5001330-os-builds-19041-928-and-19042-928-cead30cd-f284-4115-a42f-d67fec538490%2C%3C%2FA%3E%20which%20I%20found%20on%20%3CA%20href%3D%22https%3A%2F%2Fwww.pcgamer.com%2Fthe-windows-10-update-thats-been-trashing-framerates-has-been-fixed%2F%23comment-jump%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3EPCGamer%3C%2FA%3E.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2291474%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2291474%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22VIiyi%22%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EWhat%20are%20you%20doing%20my%20God%3F%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EI%20have%20this%20problem%20for%20half%20a%20month%20now%2C%20I%20can%20neither%20delete%20this%20update%20of%20yours%20nor%20roll%20back%20the%20update!%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EI%20have%20not%20solved%20the%20problem%2C%20help%20me%20my%20God.%20How%20upset%20I%20am%20about%20you%20and%20your%20update%20KB5001330%20KB5000802.%20Because%20of%20you%2C%20I%20cannot%20fully%20enjoy%20my%20favorite%20games%20because%20of%20this%20update%2C%20there%20are%20strong%20FPS%20drawdowns%20WHAT%20DO%20I%20DO%20%3F%3F%3F%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EHOW%20TO%20CLEAN%20THIS%20UPDATE%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2291480%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2291480%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22VIiyi%22%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EWhat%20are%20you%20doing%20my%20God%3F%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EI%20have%20this%20problem%20for%20half%20a%20month%20now%2C%20I%20can%20neither%20delete%20this%20update%20of%20yours%20nor%20roll%20back%20the%20update!%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EI%20have%20not%20solved%20the%20problem%2C%20help%20me%20my%20God.%20How%20upset%20I%20am%20about%20you%20and%20your%20update%20KB5001330%20.%20Because%20of%20you%2C%20I%20cannot%20fully%20enjoy%20my%20favorite%20games%20because%20of%20this%20update%2C%20there%20are%20strong%20FPS%20drawdowns%20WHAT%20DO%20I%20DO%20%3F%3F%3F%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EHOW%20TO%20CLEAN%20THIS%20UPDATE.%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22VIiyi%22%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3E%3CSPAN%20class%3D%22VIiyi%22%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3EI%20removed%20this%20update%2C%20but%20it%20is%20not%20completely%20removed%20from%20my%20pc%20and%20I%20can%E2%80%99t%20roll%20back%20the%20update%20either%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298099%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298099%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20today%2C%2024apr2021%2C%20I%20learnt%20about%20KIR%20and%20the%26nbsp%3B%3CSPAN%3EKB5001330%26nbsp%3Bdebacle.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EFor%20what%20I've%20read%20I'm%20concluding%20KIR%20hasn't%20acted%20upon%20my%20system.%20I%20mean%20I%20don't%20have%20this%20on%20my%20regedit%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EHKEY_LOCAL_MACHINE%20%5C%20SYSTEM%20%5C%20CurrentControlSet%20%5CControl%20%5C%20FeatureManagement%20%5C%20Overrides%20%5C%204%20%5C%201837593227%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EI'm%20on%20Windows%2010%20(Pro)%2020H2%20(19042.928%2C%20Windows%20Feature%20Experience%20Pack%20120.2212.551.0)%2C%20so%20KIR%20should%20have%20acted%20upon%20my%20system%2C%20but%20as%20I%20said%20it%20seems%20it%20is%20not%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20that%20reason%2C%20I'm%20asking%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EHow%20do%20I%20enable%20KIR%20on%20my%20system%3F%20and%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EHow%20do%20I%20know%20a%20fix%20for%26nbsp%3BKB5001330%20is%20correctly%20applied%20to%20my%20system%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJ.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298153%22%20slang%3D%22fr-FR%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298153%22%20slang%3D%22fr-FR%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F731356%22%20target%3D%22_blank%22%3E%40phimo%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20feedback.%20There%20is%20a%20section%20about%20how%20KIR%20works%20for%20Consumer%20devices.%20To%20simplify%20the%20process%2C%20we%20push%20a%20change%20to%20the%20cloud%20and%20is%20reflected%20on%20an%20Internet%20connected%20customer%20usually%20within%2024%20hours.%20It%20does%20require%20a%20reboot%20most%20times.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1038466%22%20target%3D%22_blank%22%3E%40jeansagi%3C%2FA%3E%26nbsp%3BThere%20should%20be%20no%20action%20you%20need%20to%20take%20except%20for%20a%20reboot.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2299666%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2299666%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F702597%22%20target%3D%22_blank%22%3E%40Eric_Vernon%3C%2FA%3EThanks%20(Merci!%20I'm%20French%20Canadian)!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20one%20thing%20that%20isn't%20clear%20about%20KIR%20and%20KB5001330%20is%20whether%20everyone%20will%20get%20the%20KIR%20prompt%20or%20only%20some%20of%20us...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20we%20100%25%20sure%20that%20everyone%20in%20need%20of%20a%20rollback%20will%20indeed%20get%20the%20rollback%3F%20What%20if%20someone%20doesn't%20want%20to%20take%20any%20chance%20and%20want%20to%20use%20the%20KIR%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2299892%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2299892%22%20slang%3D%22en-US%22%3E%3CP%3E%26gt%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1038466%22%20target%3D%22_blank%22%3E%40jeansagi%3C%2FA%3E%3CSPAN%3E%26nbsp%3BThere%20should%20be%20no%20action%20you%20need%20to%20take%20except%20for%20a%20reboot.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20users%20are%20basically%20%3CSTRONG%3Eblind%3C%2FSTRONG%3E%26nbsp%3Bon%20this%20fix%3F%3C%2FP%3E%3CP%3EI%20mean%20there%20is%20no%20other%20way%20to%20know%20that%20a%20KIR%20fix%20for%20the%20KB5001330%20is%20in%20place%20apart%20than%20an%20obscure%20register%20in%20regedit%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJ.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2302341%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2302341%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%20class%3D%22VIiyi%22%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3Ewhy%20do%20you%20share%20my%20comments%20and%20the%20comments%20of%20people%20who%20were%20not%20helped%20by%20your%20advice%3F%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EWhy%20should%20I%20and%20other%20users%20try%20hard%20because%20of%20your%20mistakes%3F%3C%2FSPAN%3E%3C%2FSPAN%3E%20%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3E%3CSPAN%3EI%20am%20still%20experiencing%20problems%20due%20to%20the%20recent%20update%20and%20everything%20you%20say%20here%20is%20contrary%20to%20reality%20you%20did%20not%20solve%20the%20problems%20of%20updating%20KB5001330%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2302658%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2302658%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F702597%22%20target%3D%22_blank%22%3E%40Eric_Vernon%3C%2FA%3E%26nbsp%3B%3CSPAN%20class%3D%22VIiyi%22%3E%3CSPAN%20class%3D%22JLqJ4b%20ChMk0b%22%3Ewhether%20an%20update%20will%20be%20released%20in%20the%20near%20future%20that%20will%20correct%20the%20current%20situation%3C%2FSPAN%3E%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2316125%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2316125%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20configured%20Windows%20Update%20to%20prompt%20me%20to%20download%20updates%20and%20to%20neither%20automatically%20download%20nor%20install%20updates.%20This%20KIR%20system%20bypasses%20my%20configuration%20of%20Windows%20Update%20and%20makes%20automated%20changes%20to%20my%20system%20without%20my%20knowledge%20which%20is%20very%20upsetting%20for%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2317235%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2317235%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20observed%20the%20same%20thing%20here%20on%20individual%20clients.%20KB5001330%20has%20been%20installed%20on%20clients%20by%20itself%20although%20we%20have%20deactivated%20all%20automatic%20updates%20via%20GPO.%20We%20use%20a%203rd%20party%20patch%20management.%20This%20has%20noticed%20that%20an%20update%20has%20been%20installed%20which%20has%20not%20yet%20been%20released%20internally.%3C%2FP%3E%3CP%3EHow%20can%20we%20ensure%20that%20only%20we%20and%20not%20Microsoft%20can%20distribute%20updates%20directly%20to%20the%20clients%3F%20What%20mechanism%20did%20the%20client%20use%20to%20detect%20and%20download%20the%20update%3F%20As%20I%20said%2C%20%22Check%20for%20Updates%22%20and%20%22automatic%20Updates%22%20are%20deactivated.%3CBR%20%2F%3EAnd%20how%20did%20it%20happen%20that%20only%20a%20few%20clients%20received%20this%20update%20directly%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2324328%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2324328%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F827269%22%20target%3D%22_blank%22%3E%40Nicholas_Steel%3C%2FA%3E%26nbsp%3B%20%26amp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F112962%22%20target%3D%22_blank%22%3E%40GerritEllmer%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20are%20a%20couple%20of%20topics%20that%20you%20are%20bringing%20up%20so%20let%20me%20try%20to%20address%20them.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EToday%20KIR%20is%20a%20separate%20service%20from%20Windows%20Update.%20KIR%20only%20makes%20configuration%20changes%20as%20noted%20in%20the%20blog.%20It%20does%20not%20push%20Windows%20Update%20packages%20to%20machines.%26nbsp%3BIf%20a%20WU%20package%20was%20pushed%20without%20your%20knowledge%20to%20your%20environment%2C%20pls%20contact%20Microsoft%20Support%20to%20see%20how%20to%20get%20that%20addressed%20and%2For%20send%20feedback%20through%20the%20Feedback%20application.%20This%20should%20not%20happen.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20answer%20the%20question%20of%20going%20around%20your%20Windows%20Update%20restriction%2C%20because%20it%20is%20a%20separate%20service%2C%20it%20is%20not%20controlled%20by%20Windows%20Update%20settings.%20KIR%20targets%20all%20machines%20for%20a%20Windows%20version(s)%20that%20is%20either%20having%20the%20issue%20or%20could%20have%20the%20issue%20regardless%20of%20whether%20the%20actual%20update%20has%20been%20installed%20eg.%20all%20Windows%2010%20version%202004%20machines.%20This%20means%20that%20if%20a%20user%20has%20the%20update%20KB%20in%20question%20installed%20and%20is%20experiencing%20an%20issue%2C%20KIR%20will%20mitigate%20that%20issue%20i.e.%20the%20user%20will%20stop%20seeing%20problems%20after%20a%20reboot.%20If%20a%20user%20has%20not%20YET%20installed%20the%20update%20KB%2C%20the%20KIR%20configuration%20will%20sit%20dormant%20on%20the%20machine%20until%20the%20update%20is%20installed%20at%20which%20point%20the%20issue%20will%20be%20automatically%20mitigated%20without%20the%20user%20ever%20knowing%20there%20was%20a%20problem.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20investigating%20the%20creation%20of%20some%20UI%20to%20help%20users%20know%20when%20the%20KIR%20has%20been%20configured%20on%20the%20machine.%20We%20don't%20have%20this%20capability%20today%20unfortunately.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2339185%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2339185%22%20slang%3D%22en-US%22%3E%3CP%3Eand%20the%20solution%20is................................%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2356448%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2356448%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20I%20started%20reading%20this%20article%20I%20thought%20%22What%20a%20fantastic%20idea!%22%20but%20by%20the%20time%20I%20got%20to%20the%20end%20I%20felt%20very%20sad.%20It%20seems%20that%20the%20great%20power%20of%20such%20a%20feature%20is%20that%20consumers%20would%20be%20able%20to%20pick%20which%20individual%20updates%20they%20want%20to%20roll%20back%20to%20try%20and%20resolve%20issues%20by%20themselves.%20However%2C%20Microsoft%20still%20controls%20it%20for%20everyone.%20Where%20are%20the%20instructions%20for%20how%20I%20can%20choose%20what%20updates%20to%20rollback%3F%20And%20also%20what%20happens%20if%20a%20security%20update%20breaks%20something%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2356542%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2356542%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F796484%22%20target%3D%22_blank%22%3E%40rocifier%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20feedback.%20As%20noted%20in%20the%20blog%2C%20this%20only%20applies%20to%20non-security%20fixes%20today.%20We%20are%20exploring%20solutions%20for%20security%20fixes%20in%20the%20future.%20For%20consumers%2C%20you%20are%20correct%20there%20is%20no%20choice%20in%20the%20same%20way%20that%20there%20is%20no%20choice%20when%20we%20push%20updates%20out%20for%20the%20monthly%20patch%20Tuesday.%20We%20push%20the%20KIR%20update%20to%20mitigate%20the%20issue%20that%20is%20affecting%20consumers.%20If%20a%20consumer%20is%20not%20experiencing%20the%20issue%2C%20for%20example%20the%20issue%20is%20a%20gaming%20issue%20and%20the%20individual%20isn't%20a%20gamer%2C%20there%20is%20no%20affect%20to%20their%20system%20unless%20they%20start%20gaming%20and%20run%20into%20the%20issue.%20For%20individuals%20experiencing%20the%20issue%2C%20the%20configuration%20change%20from%20the%20cloud%20solves%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2356694%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2356694%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F702597%22%20target%3D%22_blank%22%3E%40Eric_Vernon%3C%2FA%3E%26nbsp%3Bthanks%20for%20replying.%20The%20problem%20I%20have%20with%20that%20architecture%20is%20the%20following%20example%3A%20Let's%20say%20user%20A%20(an%20avid%20audio%20listener%2C%20but%20not%20a%20gamer)%20received%20a%20Windows%20update%20which%20fixed%20an%20issue%20they%20were%20having.%20Meanwhile%20user%20B%2C%20who%20doesn't%20use%20surround%20sound%20but%20is%20an%20avid%20gamer%20receives%20the%20same%20update.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20update%20had%20a%20problem%20where%20it%20means%20user%20B%20cannot%20play%20their%20games%20in%20an%20optimally%20performant%20way%20under%20common%20setups.%20Microsoft%20decides%20to%20push%20a%20KIR%20update%20which%20allows%20the%20gamer%20audience%2C%20such%20as%20user%20B%2C%20a%20less%20interrupted%20experience%20by%20rolling%20back%20the%20sound%20feature%20from%20the%20windows%20update.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20in%20the%20present%20process%2C%20user%20A%20now%20does%20not%20benefit%20from%20the%20released%20surround%20sound%20fix.%20In%20an%20improved%20architecture%2C%20they%20would%20have%20fully%20benefitted%20from%20the%20fix%20early%20while%20not%20caring%20about%20games%20being%20affected%20at%20all%20-%20and%20choosing%20not%20to%20receive%20the%20rollback.%20I%20do%20understand%20though%20that%20this%20is%20perhaps%20an%20ideal%2C%20but%20as%20a%20regular%20user%20of%20Windows%20I%20would%20like%20to%20know%20that%20there%20is%20at%20least%20the%20option%20to%20opt%20in%20or%20out%20of%20specific%20KIR%20rollbacks%2C%20as%20it%20suits%20my%20usage%2C%20though%20may%20prefer%20to%20receive%20Microsoft%20appointed%20KIR%20updates%20if%20I%20take%20no%20action.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2357120%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2357120%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20all%20my%20games%20are%20still%20having%20problems%20since%20KB5001330.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20tried%20the%20suggested%20group%20policy%20fix%20but%20that%20didn't%20work.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20restarted%20my%20computer%20several%20times.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20problem%20is%20mostly%20with%20game%20menus%20and%20some%20other%20fps%20slowdowns%20which%20are%20not%20as%20severe%20as%20the%20menu%20problems.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2357221%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2357221%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F827269%22%20target%3D%22_blank%22%3E%40Nicholas_Steel%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F796484%22%20target%3D%22_blank%22%3E%40rocifier%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20feedback.%20As%20noted%2C%20we%20are%20evaluating%20a%20variety%20of%20UI%20affordances%20to%20notify%20users.%20At%20the%20present%20time%2C%20we%20do%20not%20have%20that%20capability.%20We%20do%20post%20changes%20on%20the%20Windows%20Health%20Dashboard%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Frelease-health%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EWindows%20release%20health%20%7C%20Microsoft%20Docs%3C%2FA%3E)%20with%20a%20pointer%20to%20details%20in%20the%20release%20notes%20at%20present.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2356729%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2356729%22%20slang%3D%22en-US%22%3E%3CP%3EI'd%20just%20like%20KIR%20updates%20to%2C%20at%20minimum%2C%20notify%20me%20before%20performing%20their%20action%20and%20give%20me%20an%20opportunity%20to%20choose%20when%20they%20are%20installed...%20like%20I've%20already%20got%20set%20up%20for%20regular%20Windows%20updates%20(The%20WU%20UI%20asks%20if%20I%20want%20to%20download%20%26amp%3B%20install%2C%20it%20doesn't%20immediately%20download%20%26amp%3B%20install%20the%20moment%20it%20detects%20a%20new%20update%20is%20available).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20for%20there%20to%20be%20easily%20found%20info%20on%20what%20the%20KIR%20is%20going%20to%20do.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2429122%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2429122%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20everybody%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Emaybe%20someone%20please%20can%20help%20me%20with%20the%20following%20questions%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Can%20the%20reception%20resp.%20the%20activation%20of%20a%20KIR%20be%20initiated%2Fforced%3F%3CBR%20%2F%3E-%20How%20can%20I%20find%20out%20which%20KIRs%20are%20active%20on%20the%20device%3F%3CBR%20%2F%3E-%20Does%20Microsoft%20provide%20an%20overview%20of%20the%20KIR%20IDs%3F%3CBR%20%2F%3E-%20Does%20a%20device%20that%20has%20paused%20or%20even%20deactivated%20Windows%20updates%20still%20receive%20possible%20rollbacks%3F%3CBR%20%2F%3E-%20What%20about%20systems%20where%20telemetry%20data%20acquisition%2Ftransmission%20has%20been%20deactivated%20using%203rd%20party%20tools%20for%20privacy%20reasons%3F%3CBR%20%2F%3EDo%20they%20still%20receive%20KIRs%20as%20long%20as%20they%20have%20not%20set%20%22AllowExperimentation%22%20to%200%2C%20or%20do%20receive%20such%20systems%20no%20KIRs%20at%20all%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20and%20regards%2C%3CBR%20%2F%3EMartin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2450957%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20Rollback%3A%20Helping%20you%20keep%20Windows%20devices%20protected%20and%20productive%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2450957%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20questions%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F822011%22%20target%3D%22_blank%22%3E%40mfessler%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20we%E2%80%99ve%20already%20outlined%20in%20the%20blog%2C%20we%20sometimes%20share%20Group%20Policies%20intended%20for%20Enterprises%20in%20the%20Known%20Issue%20Activation%20KB%20article%20associated%20with%20a%20rollback.%20These%20Group%20Policy%20objects%20can%20be%20used%20to%20configure%2Fcontrol%20rollbacks%3B%20that%20said%2C%20at%20present%20we%20don%E2%80%99t%20have%20a%20consumer-centric%20solution%20for%20configuring%20or%20enumerating%20rollbacks.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20is%20no%20technical%20overview%20of%20KIR%20ID%E2%80%99s%20being%20made%20available%20either%3B%20these%20ID%E2%80%99s%20are%20implementation%20details%20and%20aren%E2%80%99t%20part%20of%20the%20publicly%20available%20information.%20In%20the%20future%2C%20we%20may%20change%20the%20implementation%20approach%20to%20use%20something%20else%20besides%20the%20ID%E2%80%99s%2C%20change%20the%20way%20the%20ID%E2%80%99s%20are%20used%20and%20so%20on%20%E2%80%93%20and%20if%20we%20ever%20make%20such%20changes%2C%20we%E2%80%99ll%20ensure%20that%20published%20Group%20Policies%20remain%20in%20working%20order.%20As%20a%20general%20approach%20we%20don%E2%80%99t%20have%20plans%20to%20go%20into%20the%20details%20of%20these%20ID%E2%80%99s%20at%20present.%20%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20Windows%20Update%20(WU)%20is%20disabled%2C%20machines%20would%20indeed%20stop%20receiving%20Known%20Issue%20Rollbacks.%20Telemetry%20is%20an%20entirely%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fprivacy%2Fconfigure-windows-diagnostic-data-in-your-organization%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Edifferent%20lever%3C%2FA%3E%20that%20only%20affects%20whether%20Windows%20sends%20telemetry%20to%20Microsoft%20or%20not%3B%20when%20a%20machine%20is%20configured%20to%20disable%20telemetry%20from%20being%20sent%20to%20Microsoft%2C%20then%20we%20won%E2%80%99t%20receive%20any%20telemetry%20related%20to%20rollbacks%20either.%20That%20said%2C%20such%20machines%20would%20continue%20receiving%20(or%20not%20receiving)%20Known%20Issue%20Rollbacks%20depending%20on%20whether%20WU%20is%20enabled%20on%20those%20machines%20(or%20not).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20the%20rollbacks%20to%20be%20meaningful%2C%20the%20rollback-metadata%20must%20be%20interpreted%20in%20the%20context%20of%20a%20system%20that%20has%20installed%20the%20corresponding%20(problematic)%20Update.%20If%20a%20system%20doesn%E2%80%99t%20have%20the%20corresponding%20update%2C%20the%20rollback-metadata%20is%20benign%20does%20nothing%20further.%20OTOH%20if%20a%20machine%20acquires%20the%20affected%20Update%20(either%20through%20WU%20or%20some%20other%20channel)%20%3CEM%3Eafter%3C%2FEM%3E%20the%20rollback-metadata%20has%20been%20obtained%2C%20the%20rollback%20will%20go%20into%20effect%20as%20soon%20as%20the%20corresponding%20Update%20is%20installed.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20Group%20Policies%20we%20supply%20with%20rollbacks%20also%20work%20the%20same%20way%3B%20machines%20without%20the%20corresponding%20Update%20can%20be%20pre-configured%20with%20the%20Group%20Policy%20if%20administrators%20would%20prefer%20to%20do%20so%2C%20and%20the%20rollback%20itself%20would%20go%20into%20effect%20as%20soon%20as%20the%20corresponding%20Update%20appears%20on%20the%20systems.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECan%20you%20clarify%20your%20question%20about%20%E2%80%9CAllowExperimentation%E2%80%9D%20-%20what%20setting%20is%20this%20question%20about%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20this%20helps!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Mar 26 2021 01:34 PM
Updated by: