Resolved Explorer column widths too wide

Hard to describe this one in the title.

If I open explorer to view my files (using "Details"), most columns are now defaulting to 170 pixels as a column width. I can make the columns wider, but no less than 170 pixels.

This means for "Status" column in OneDrive there's a huge waste of window width. For [file] size, almost as bad, and Date column uses twice as much as is necessary.
I can increase the length by dragging the column width and making it wider, and double-clicking on the right edge of the column heading will shrink it back - but only to the 170 pixel value.
If I go into "Choose Details" and change the width to be less e.g. 120 pixels, it has no effect ie reverts to 170.

[Sorry, can't include an image to show exactly what I see]

If I go to a folder I haven't opened in Explorer for a while, I get narrower columns (e.g. 90 pixels), but the moment I do anything to touch a column that column goes out to 170 pixels!

Any ideas on how to remove this minimum setting?

 

Hi Ludwig, I've read reports that suggest Windows Cumulative Update (KB5026446) may be causing all sorts of odd problems.
Check your Updates/History and if it has been installed, try an uninstall to see if that corrects your problem.
(Remember to Shut down and Reboot after making any changes).

 

Thanks for the tip.

I opened Windows update to uninstall KB5026446 .. but instead it's waiting to be installed. I might risk installing it to see if that corrects it. I may end up removing it if any of the other "odd problems" surface, as you suggest.

Additional Info:
Have just realised I hadn't checked for the problem with another user on this same machine. So I've now logged into two others on this same machine - neither have the problem. I guess that means it's something in the local user registry of one user that's got corrupted?

Is there a known place in the registry where I could 'reset' the explorer column widths somehow?

 

retiredlearner:
A reboot (2 actually) made no difference, so I applied KB5026446 anyway.

All seems to have come right No idea why, but thanks for looking at the problem

Hopefully other things don't come to bite because of the update.

 

Thanks for the news it's working OK.