Is Microsoft getting violent with Windows eleven?

• The comparison
• News & Updates
• Is Microsoft getting violent with Windows eleven?

            Acá hay un pequeño secreto sucio que los administradores de red no desean que sepas: cuando afirmas “algo sucedió” en tu computadora, probablemente no te creamos.  Va a jurar que no hizo click en nada, presionó ningún botón o bien hizo solo una cosa.  Como administradores aburridos, vamos a estar conforme en que las computadoras son malas y, con frecuencia, hacen las cosas de forma espontánea.

But often we are convinced that you clicked on something and what happened was self-inflicted. Naturally, we could blame the inconvenience on something Microsoft did, while saying, "You really did click on something." (Often, only when we can see what you see on your computer system, or examine the log files, can we truly determine what happened.) So there are times when enough people describe related behaviors often enough that we truly believe something is going on. Case in point: Microsoft's update behavior. Let's start with Microsoft introducing KB5005463, the Health Check PC app, on Windows XNUMX machines. It is still installed on computers that do not have the necessary processor to accept Windows XNUMX. To add insult to injury, the Computer Health tool cannot be uninstalled. via the normal update history panel; you need to search for apps and features to locate it and remove it from your system. This is not a proposed update, it is an update that is obviously being pushed. Since most of the users surely do not use a computer that is compatible with Windows XNUMX, adding the tool only erases that fact for us. He just seems a bit, well, cheeky. Now there are the interesting reports I've seen about installing Windows XNUMX on systems where a user hasn't approved the installation. (Yes, there have been cases where people have signed up for the Microsoft Insider program and installed Windows XNUMX. It seems that the user has approved the update without realizing it. But in other cases, the trigger for installing Windows XNUMX is much less obvious. I wrote last week about how you can go back to Windows XNUMX if you somehow got Windows XNUMX and don't want to keep it. And I also urged anyone and everyone who inadvertently received Windows XNUMX to contact me. There have been a number of responses from readers; in one case, the banner read: "Windows XNUMX starts installing without user intervention." Another user claimed that he clicked the "Check for updates" button, which caused Windows XNUMX to install. And that's where my recommendation lies for those who don't want updates, and Windows XNUMX in particular, to disrupt their computing experience. I have a rule when it comes to patches: never click the 'Check for updates' option in Windows XNUMX. This really means that if there are updates ready to be installed, go ahead and install them as well. It can be confusing, especially for those used to Windows XNUMX where you can check for updates and just check for fixes. In Windows XNUMX, unless you have set deferrals for features, every time you click "Check for updates", you will receive updates that Microsoft considers "Previous View Updates". Most of the time, these previous view updates are not harmful.

Advice for IT professionals

For IT administrators who want to make sure their users can't delete their settings and also install Windows Eleven, keep in mind that if your machines are managed by Windows Software Update Services, SCCM, or other patch management tools, Windows Eleven won't work. he's going to do it. it will not be offered to your managed systems. You must make a concerted effort to incorporate Windows eleven into these environments. But in this work-from-home era, where certain computers aren't managed and patched via Windows Update, you can make one more adjustment to your remote fleet. A Microsoft registry key can remove access to the Check for updates button. You can extract a registry key that will suppress access to the Check for updates button so that end users cannot inadvertently click it:

HKEY_Local_Machine HKEY_Local_Machine

Registry path HKEY_LOCAL_MACHINE SOFTWARE Policies Microsoft Windows WindowsUpdate

Value name SetDisableUXWUAccess

REG_DWORD Value Type

Enabled value 1 (Note that you will need to add this dword registry key or have it added using your registry implementation tools.) The Check for Updates button will now be greyed out. If you want to re-enable it, simply remove the SetDisableUXWUAccess key and the button will be accessible again.

Microsoft The Check for updates button in Windows XNUMX can be disabled. For business users who want to install Windows XNUMX, I advise you to wait at least a few months for the bugs to be resolved. Now is the time to try Windows XNUMX, not to embed it. Microsoft hosts its annual Ignite IT Professional conference this week, with many sessions focusing on using, deploying, and managing Windows XNUMX systems. Most of the sessions are being recorded and will be on demand for later viewing. This will be a good time to start checking out each and every Ignite Windows XNUMX session to get more information and start testing Windows XNUMX. If you are a user who inadvertently received Windows XNUMX and did not click anything, I would ask you again to contact me at [email protected]; I would really like to see what happened. Windows eleven is meant to be offered, not pushed, to qualified computers.

<p>Copyright © dos mil veintiuno IDG Communications, Inc.</p>