Let’s just get this: A Windows update does not usually remove software. It is designed to install the update, not to change software that is already in place on your system.
At least not updates supposed software removal. Since March, however, if you run the RDgateway brokerage service on Server 2022 (and that version only), the cumulative monthly updates have removed that service. This behavior is not normal; this is a bug.
As Microsoft notes in the Microsoft 365 Administration toolkit: “We have received reports that after installing KB5005575 or later updates to Windows Server 2022 Standard Edition, the role of Remote Desktop Connection Broker and support services could be unexpectedly removed. We have expedited an investigation and are working on a solution. Note: This issue does not affect the Windows Server 2022 Datacenter edition and other versions of Windows Server. ”
Microsoft is researching the issue and will eventually fix the bug.
The most important thing to remember is that this behavior is not normal.
Patches should not bother a user, either
If there is a third – party security product or application that keeps certain files locked during startup, the system will restart after an update using a temporary profile. This can be confusing. Instead of starting the blue screen of death, the system will only start to the point where you think Microsoft has removed applications. The signal: when the system hits a clean user profile you no longer have your customization.
- In Command Prompt, type “wmic useraccount get name, sid” and press Enter.
- Search for your username and SID note – usually a number in the 1000s for regular users.
- Open registry editor “regedit.”
- Navigate to “PC HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion Profilelist”
- Search for SID. If so [are] two entries (e.g. xxxx-1001 and xxxx-1001.bak) then your query is as I was. The “.bak” entry is your default ‘good’ account. The temporary account is the non-.bak entry.
You can fix this by:
- Delete the entry sin the “.bak” (or rename it as “.bak2” or something else).
- Remove the “.bak” from the remaining entry.
- Log off / on and it should be set. If it’s fixed and you renamed the [without .bak] enter at step 1, instead of deleting it you should now delete it.
Windows 10 and 11 versions now ready for ‘wide deployment’
All of these patch issues are important because Microsoft is doing it now Windows 10 21H2 widely available to users. You’ll want to make sure you click Start> Settings> System> Under, and scroll down to make sure you’re 21H2. If not, use the Control tool to review whether you have a registration key set to block to 21H2. (As of May 10, support for Windows 10 version 20H2 service ended, which is why it’s important to move now.)
Wide deployment means that Microsoft considers a version of Windows complete with no major hardware issues to block the installation.
And as of May 17, all of Windows 11 was considered ready for wide deployment. (Although Microsoft has announced that Windows 11 is “finished,” I think it’s still a work in progress.)
Feature releases require time to install
When you install a feature release or update on Windows 11, give yourself some time for the machine to get the update. If your hardware is more offline than it is online, you will often find that it is not getting updates. So keep it online for a while to make sure it checks with Microsoft for any updates. Then after the feature release is installed, give your hardware time to re-index files and process the upgrade. (And review your main applications after you install updates to make sure they work.)
Reminder: updates will go smoother if you have have an SSD as your boot hard drive. This will ensure that you have a good running experience using Windows 10.
Most patches are actually behavioral
When patches cause issues, they gather headlines in the technology industry. Most of the time, however, patches do not cause side effects. Most Microsoft users will not see any of the known issues documented in the Heath release panel. But there are times when patches cause problems.
If, after installing an update, you have an unexpected side effect, uninstall the update. If the issue goes away, update yes the question. If it does not disappear, the patch is probably not the root cause of what is wrong. At the same time, if someone reports a problem, the symptom may not occur on your workstation.
The bottom line is that patches should not be avoided forever. In fact, skipping updates in the past has prompted issues, namely Microsoft cumulative updates. It was found that users skipped an update too often – and that this later led to problems.
Copyright © 2022 IDG Communications, Inc.
After Windows update, what should you expect?
Source link After Windows update, what should you expect?