Windows 10 – a 7-year-old OS – is still having problems with the desktop and taskbar
- Reference: 1668711613
- News link: https://www.theregister.co.uk/2022/11/17/microsoft_windows_10_fix/
- Source link:
According to Redmond, users "might experience an error in which the desktop or taskbar might momentarily disappear, or your device might become unresponsive." The issue affects PCs running Windows 10 versions 22H2, 21H2, 21H1, and 20H2, the company [1]wrote on its Windows Health Dashboard.
Microsoft didn't outline the exact cause but notes it was related to the KB5016688 220820_03051 cumulative update and later.
[2]
The software giant is using its Known Issue Rollback (KIR) feature – which enables IT administrators to roll back the unwanted changes of an update – to resolve the problem, adding that it could take up to 24 hours for the fix to reach non-managed business systems and consumer devices. Restarting the device may accelerate the timeframe.
[3]
[4]
Organizations that use enterprise-managed devices can install and configure a special Group Policy by going to "Computer Configuration" and then "Administrative Templates" and "Group Policy name."
If the resolution doesn't work, users can try restarting the Windows device, according to Microsoft.
[5]
The latest fix comes after a number of other problems [6]were resolved this week.
Microsoft over the last week addressed issues in Windows 10 and 11 systems caused when users installed the KB5019509 update, leaving some unable to reconnect to the Direct Access feature after temporarily losing connectivity with the network or transitioning between Wi-Fi network or access points.
[7]Qualcomm faces fresh competition in world of Arm-based Windows PCs
[8]Microsoft warns Direct Access on Windows 10 and 11 could be anything but
[9]OpenPrinting keeps old printers working – even on Windows
[10]Windows breaks under upgraded IceXLoader malware
The company also used the KIR tool for that fix.
In addition, updates issued November 8 or later for particular Windows Server systems caused problems with the Kerberos authentication protocol, including with Group Managed Service Accounts, domain user sign-ins, remote desktop connections using domain users, access share folders on workstations, file shares on servers, and printer connections. ®
Get our [11]Tech Resources
[1] https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22h2#your-desktop-or-taskbar-might-momentarily-disappear-or-might-become-unresponsive
[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2Y3a9B5I59v6cy8nBUktrmgAAAEU&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Y3a9B5I59v6cy8nBUktrmgAAAEU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33Y3a9B5I59v6cy8nBUktrmgAAAEU&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44Y3a9B5I59v6cy8nBUktrmgAAAEU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22h2#your-desktop-or-taskbar-might-momentarily-disappear-or-might-become-unresponsive
[7] https://www.theregister.com/2022/11/16/qualcomm_arm_windows/
[8] https://www.theregister.com/2022/11/15/microsoft_bug_direct_access/
[9] https://www.theregister.com/2022/11/10/openprinting_keeps_old_printers_working/
[10] https://www.theregister.com/2022/11/10/icexloader_malware_microsoft_users/
[11] https://whitepapers.theregister.com/
Exceptional service
WithFingersCrossed = True;
try { System.Update(); }
catch (SystemBorkedException) { KnownIssueRollback(); }
finally { // Do it the right way. }
Re: Exceptional service
Not quite right
WithFingersCrossed = True;
Do
{
try { System.Update(); }
catch (SystemBorkedException) { KnownIssueRollback(); }
finally { // Do it the right way. }
}
Until bPissed_off==true
Install Linux
Re: Exceptional service
Well done on the one-upmanship.
Re: Exceptional service
Depends - which leg are you standing on?
That's because it's shit
And Microsoft don't know how to fix it. Nearly 40 years of security failure.
The software giant is using its Known Issue Rollback (KIR) feature...
I'd assumed that the two paragraphs about KIR and use of Group Policies would just be copy and pasted verbatim into these articles, but no, they are slightly different each time.
Thank heavens for that bit of editing, or we'd never be able to tell these MS stories apart.
Re: The software giant is using its Known Issue Rollback (KIR) feature...
Yeah, that part is really weird. [1]Whoever wrote the article was really not in the mood for work. Maybe a MS-QA employee?
[1] https://www.theregister.com/Author/Jeff-Burt
Kerberos problem confirmed
Quite a number of domain controllers in our companies hand showed the little kerberos problem. Not funny.
We should get a statistic of fixed bugs vs. new bugs...
Whatever...
"Microsoft didn't outline the exact cause..."
Because when my system locks up I always think... I don't need to know why... :-/
Microsoft users are the best.