I can tell you from copious personal experience that diagnosing and pinpointing trouble can be difficult and time-consuming. But that puts an interesting burden on users to figure out what’s working and what’s not.
I agree with MS that on principle such tools are best avoided. Instead I see it as a warning against “unsupported methods” that some developers use. I don’t see what MS is doing here as a general injunction against such efforts. That said, I do indeed enjoy tinkering with Windows. With apologies to Hamlet (and Shakespeare), the real question is how much, how often and what kinds of tweaks Windows users can safely make to their own installations? I’m of the opinion that “less is more” because it involves fewer things that could go wrong, and fewer such things to keep track of. This could make life extremely interesting for related tech support operations. Notice that MS puts the onus for figuring things out if Windows doesn’t work properly with such a third-party tool on that tool’s developer. If you are using StartAllBack, you might be able to prevent this issue by updating to the latest version (v3.5.6 or later). If your Windows device is already experiencing this issue, you might need to contact customer support for the developer of the app you are using. Workaround: We recommend uninstalling any third-party UI customization app before installing KB5022913 to prevent this issue.
These types of apps often use unsupported methods to achieve their customization and as a result can have unintended results on your Windows device. The known affected third-party UI customization apps are ExplorerPatcher and StartAllBack. These third-party apps might cause errors with explorer.exe that might repeat multiple times in a loop. Here’s what the announcement says, verbatim (emphasis mine, for easy identification of possible offenders in the first paragraph emphasis in the second paragraph is Microsoft’s):Īfter installing KB5022913 or later updates, Windows devices with some third-party UI customization apps might not start up. Of course, neither option is perfect but sacrifices are sometimes necessary here in Windows-World. Uninstall the update, and keep using the third-party tool. Remove the third-party tool, and continue forward with the update.Ģ. If an update breaks a third-party tool, users have two choices:ġ.
If KB5022913 May Break Customization Tools, Then What? When MS released its “Moment 2” updates on February 28, it announced that KB5022913 may break customization tools in common use. Ditto for adding functionality missing but desired in Windows. Others refuse, and turn to third-party tools to bring back bits and pieces of prior capability that MS has removed. Some people learn to live with Windows and make the best of it.
0 kommentar(er)
