Help! kb5127936 has made my taskbar and tabs in programs unresponsive

Under 25h2 all works well. When the preview patch or 26h2 went into service, my taskbar randomly becomes unresponsive and the File and Edit tabs also. I reverted from 26h2 to 25h2 and everything was fine. the preview 5127935 went in and corrupted things, so I took it out and paused updates for the 5 weeks ahead. I have had extensive chats with Microsoft and there is no admission of a problem and yet Microsoft states the an explorer reset will fix it. So they know about the freezing. That by the way does not work. One must log out and in or reboot to temporarily reboot.

Now, my machine, bought in 2022 was actually made in 2018. The pandemic shortened the supply at Staples. I have an HP 590 machine, with a generation 8 processor that is supported by windows 11. It was intended for windows 10 and in the end has worked well with win 11. Drivers though are 2018. But these problems seem to be one of two things... a change in architecture that end life of my machine or an update with bad code that reflects what is also in an in-place system overwrite. I am told to do it and then by other tech to wait.. So I am in limbo. I don't think that it is my machine sfc and dism report no problems and it IS kb5127936 to causes this, that is 100% proven.

One of the above Tutorials may help you.

Welcome to the forum, tsoilihoi! Glad to have you here.
You are definitely not alone or losing your mind on this one. The taskbar and menu freezing behavior you are describing is a known quirk that can happen when File Explorer's modern shell infrastructure clashes with specific cumulative updates—especially preview builds like KB5127936.
Since SFC and DISM are coming up clean, your system files are completely healthy. This is purely a software/update compatibility bug, and it has nothing to do with your 8th-generation Intel processor or your machine reaching its "end of life."
Since restarting Explorer only provides a temporary band-aid, here are the most effective ways to handle this until Microsoft issues a permanent fix in a later patch:

1. Pause Updates and Roll Back (Recommended)
Since you already isolated KB5127936 as the 100% verified culprit, the cleanest solution is to stay rolled back on the stable branch.

• Go to Settings > Windows Update > Update history > Uninstall updates.
• Locate KB5127936, click Uninstall, and let the PC reboot.
• Once back in, click Pause updates on the main Windows Update screen. You can expand the pause period up to 5 weeks. This gives Microsoft time to bake a fix into the next mandatory Patch Tuesday cycle, bypassing this broken preview build entirely.

2. Flush the Component Store & Reset Windows Update
Sometimes, residual cache from a skipped or broken preview update corrupts subsequent update logic. Before attempting any future upgrade to 26H2, try wiping the update cache completely:

1. Open Command Prompt as Administrator.
2. Stop the update services by running these commands one by one (press Enter after each):
   cmd
   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver
   
   Use code with caution.
   
   
3. Rename the cache folders so Windows is forced to rebuild clean ones:
   cmd
   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
   ren C:\Windows\System32\catroot2 catroot2.old
   Use code with caution.
   
   
4. Restart the services:
   cmd
   net start wuauserv
   net start cryptSvc
   net start bits
   net start msiserver
   Use code with caution.
   

3. Hold Off on the In-Place Upgrade
Your tech contact who advised you to wait is giving you the right advice for now. An In-Place System Overwrite replaces system files but preserves your underlying user configuration and registry app mappings. If the bug is tied to how the modern shell architecture interacts with your older (but fully supported) 2018 OEM drivers, an in-place upgrade right now might just carry the frozen taskbar symptom straight over into 26H2.
The Bottom Line: Keep updates paused for the 5-week block. Microsoft frequently pulls or overwrites problematic preview builds when the formal, mandatory monthly cumulative update drops.

Welcome again, and let us know if rolling back and resetting the update cache stabilizes things for you!

Apologies for the messed-up formatting in my previous post! The forum editor bunched the Command Prompt steps together.
To run those reset commands properly, open Command Prompt as Administrator and execute them one line at a time, pressing Enter after each:
Step 1: Stop the update services

cmd
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver

Use code with caution.

Step 2: Rename the cache folders

cmd
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
Use code with caution.

Step 3: Restart the services

cmd
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
Use code with caution.

Hopefully, this layout is much easier to follow!

AmericanPharaoh said:

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old

Click to expand...

If it's been run more than once, both folders will already exist.

I would add the following two lines before the rename...

if exist c:\windows\SoftwareDistribution.old rd /s /q c:\windows\SoftwareDistribution.old
if exist c:\windows\System32\catroot2.old rd /s /q c:\windows\System32\catroot2.old

Then, you can put all the commands in a .bat file, and run it (as Administrator) whenever you need to.