Let’s find out now: Deleting software is not normal for a Windows update. It is designed to install updates, without changing the software already on your system.
At least, not updated Assumed To remove software. From March, however, if you run Server 2022 (and only that version) RDgateway Broker service, monthly incremental updates have removed that service. This behavior is not normal; This is a bug.
As Microsoft noted in the Microsoft 365 admin dashboard: “We have received reports that after installing KB5005575 or later updates on Windows Server 2022 Standard Edition, the role of Remote Desktop Services Connection Broker and supporting services may be unexpectedly deleted. We have expedited the investigation and are working on a solution. Note: Windows Server 2022 Datacenter version and other versions of Windows Server are not affected by this issue. “
Microsoft is researching the problem and will eventually fix the bug.
The main thing to remember is that this behavior is not normal.
Patches should not be removed by any user
If there is a third party security product or application that locks certain files at boot time, the system will reboot after the update using a temporary profile. This can be confusing. Instead of booting into the blue screen of death, the system will only boot to the point where you think Microsoft has removed the applications. Tell-Tell Sign: When the system boots into an empty user profile where your customization is no longer there.
Normally, a second reboot should restore the normal user profile. If not, there are 7 steps to return to the original profile In the Askwoody forum, users set BTBS steps:
- At the command prompt, type “wmic useraccount get name, sid” and press Enter.
- View your username and note its SID – usually a number out of 1000 for the average user.
- Open the registry editor “regedit”.
- Navigate to “Computer \ HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows NT \ CurrentVersion \ Profilelist”
- Look for your SID. If there [are] Two entries (like xxxx-1001 and xxxx-1001.bak) then your problem is the same as my experience. “.bak” entry is your real ‘good’ account. Non-.bak entry is a temporary account.
You can fix this by:
- Delete entry Except “.bak” (or renaming it “.bak2” or something else).
- Remove “.bak” from the remaining entries.
- Log on / off and it should be fixed. If it is fixed and you change its name [without .bak] Enter step 1, you should delete it now instead of deleting it.
Windows 10 and 11 versions are now ready for ‘extended deployment’
All of these patching issues are important because Microsoft is now making Windows 10 21H2 widely available to users. You want to make sure you click Start> Settings> System> About and you scroll down to confirm 21H2. If you are not, use the InControl tool to review whether you have set a registry key to block 21H2. (As of May 10, support for the Windows 10 version 20H2 service has ended, which is why it is important to remove it now.)
Extensive installation means that there is no major hardware problem to block the installation considering finalizing a version of Microsoft Windows.
And as of May 17, Windows 11 was all set for extensive deployment. (Although Microsoft has hinted that Windows 11 is “complete”, I still consider it a breakthrough.)
Requires time to install feature release
When you release a feature or install an update on Windows 11, give the machine some time to get the update. If your hardware is offline rather than 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 to run any updates. Then after the feature release has been installed, give your hardware time to file rendex and upgrade. (And after you install the updates, review your core applications so they’re all working.)
Reminder: If you have an SSD as your booting hard drive, updates will be smooth This will ensure that you have a good experience running Windows 10.
Most patches are actually well behaved
When patches cause problems, they make headlines in the technology industry. Most of the time, though, the patches do not cause side effects. Most Microsoft users will not see any known issues listed in the Heath Release Dashboard. But there are times when patches cause problems.
If, after installing an update, you have an unexpected side effect, uninstall the update. When the problem is gone, update Is The problem. If it doesn’t go away, the patch is probably not the root cause of what’s going wrong. At the same time, if someone reports a problem, the symptom may not occur at your workstation.
The bottom line is that patches should not be avoided forever. In fact, past updates have triggered avoidance issues, which has led to an increase in Microsoft updates. It has been found that users often skip an update – and this leads to further problems.
Copyright © 2022 IDG Communications, Inc.